After restating the ORxPi, the monitoring doesn't get started automatically

Othernet Software
61

Command is now running.

62

Here is the content of the pinglog.txt file. There are no 'NG’s in output.

ORxPi2 v2.3.001 | root@orxpi2:/home/outernet> cat pinglog.txt
13:47:25 OK
13:47:55 OK
13:48:26 OK
13:48:56 OK
13:49:26 OK
13:49:57 OK
13:50:27 OK
13:50:57 OK
13:51:28 OK
13:51:58 OK
13:52:28 OK
13:52:58 OK
13:53:29 OK
13:53:59 OK
13:54:30 OK
13:55:00 OK
13:55:30 OK
13:56:00 OK
13:56:31 OK
13:57:01 OK
13:57:31 OK
13:58:01 OK
13:58:32 OK
13:59:02 OK
13:59:32 OK
14:00:03 OK
14:00:33 OK
14:01:03 OK
14:01:34 OK
14:02:04 OK
14:02:34 OK
14:03:04 OK
14:03:35 OK
14:04:05 OK
14:04:35 OK
14:05:06 OK
14:05:36 OK
14:06:06 OK
14:06:37 OK
14:07:07 OK
14:07:37 OK
14:08:07 OK
14:08:38 OK
14:09:08 OK
14:09:38 OK
14:10:09 OK
14:10:39 OK
14:11:09 OK
14:11:40 OK
14:12:10 OK
14:12:40 OK
14:13:10 OK
14:13:41 OK
14:14:11 OK
14:14:41 OK
14:15:12 OK
14:15:42 OK
14:16:12 OK
14:16:42 OK
14:17:13 OK
14:17:43 OK
14:18:13 OK
14:18:44 OK
14:19:14 OK
14:19:44 OK
14:20:15 OK
14:20:45 OK
14:21:15 OK
14:21:45 OK
14:22:16 OK
14:22:46 OK
14:23:16 OK
14:23:47 OK
14:24:17 OK
14:24:47 OK
14:25:17 OK
14:25:48 OK
14:26:18 OK
14:26:48 OK
14:27:19 OK
14:27:49 OK
ORxPi2 v2.3.001 | root@orxpi2:/home/outernet>

Is my raspberry pi reporting wrong time to the heartbeat?

63

It’s not reporting anything right now.

64

No. I mean the current time of my raspberry pi is different than the time displaying on http://status.outernet.is page (09:46:55). Is it okay?

================================================================================
Monitor
--------------------------------------------------------------------------------
Jan  6 13:21:15 orxpi2 user.info outernet.monitor: Collecting data
Jan  6 13:21:15 orxpi2 user.info outernet.monitor: Connected to socket
Jan  6 13:21:15 orxpi2 user.info outernet.monitor: Connected to socket
Jan  6 13:21:15 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0722029209137 seconds
Jan  6 13:21:15 orxpi2 user.info outernet.monitor: Transmitting buffered data
Jan  6 13:21:15 orxpi2 user.info outernet.monitor: Could not establish connection to http://status.outernet.is/heartbeat/v1/: <urlopen error [Errno 101] Network is unreachable>
Jan  6 13:22:16 orxpi2 user.info outernet.monitor: Collecting data
Jan  6 13:22:16 orxpi2 user.info outernet.monitor: Connected to socket
Jan  6 13:22:16 orxpi2 user.info outernet.monitor: Connected to socket
65

Good catch. It was in the wrong timezone.

1 Like
66

Which time zone should I use?. Is there a way to update the time zone?

67

UTC is fine for more purposes (default)

68

Can you mention how to change the current time zone to UTC?

EDIT: BusyBox shows data as 2015-12-29 and time 01:36:45 CET

ORxPi2 v2.3.001 | root@orxpi2:/home/outernet> time
BusyBox v1.24.1 (2015-12-29 01:36:45 CET) multi-call binary.

Usage: time [-v] PROG ARGS

Run PROG, display resource usage when it exits

        -v      Verbose

When I run the command ls -la /etc/localtime it shows,

ORxPi2 v2.3.001 | root@orxpi2:/home/outernet> ls -la /etc/localtime
lrwxrwxrwx    1 root     root            29 Dec 29 00:47 /etc/localtime -> ../usr/share/zoneinfo/Etc/UTC

EDIT2:
After restarting the monitoring, now the time seems similar with the time displaying on the status.outernet.is page. Also now I can see the green dot.

ORxPi2 v2.3.001 | root@orxpi2:/home/outernet> service monitoring restart
Stopping monitoring: OK
Starting monitoring: OK

ORxPi2 v2.3.001 | root@orxpi2:/home/outernet> tail -f /var/log/messages | grep m
Jan  6 16:27:50 orxpi2 user.info outernet.monitor: Transmitting buffered data
Jan  6 16:27:54 orxpi2 user.info outernet.monitor: Transmission complete, clarin                                                                                        g local buffer
Jan  6 16:28:54 orxpi2 user.info outernet.monitor: Collecting data
Jan  6 16:28:54 orxpi2 user.info outernet.monitor: Connected to socket
Jan  6 16:28:54 orxpi2 user.info outernet.monitor: Connected to socket
Jan  6 16:28:54 orxpi2 user.info outernet.monitor: Finished collecting data in 0                                                                                        .0453910827637 seconds
Jan  6 16:29:54 orxpi2 user.info outernet.monitor: Collecting data
Jan  6 16:29:54 orxpi2 user.info outernet.monitor: Connected to socket
Jan  6 16:29:54 orxpi2 user.info outernet.monitor: Connected to socket
Jan  6 16:29:54 orxpi2 user.info outernet.monitor: Finished collecting data in 0                                                                                        .0391008853912 seconds
Jan  6 16:30:54 orxpi2 user.info outernet.monitor: Collecting data
Jan  6 16:30:54 orxpi2 user.info outernet.monitor: Connected to socket
Jan  6 16:30:54 orxpi2 user.info outernet.monitor: Connected to socket
Jan  6 16:30:54 orxpi2 user.info outernet.monitor: Finished collecting data in 0                                                                                        .040323972702 seconds
Jan  6 16:31:54 orxpi2 user.info outernet.monitor: Collecting data
Jan  6 16:31:54 orxpi2 user.info outernet.monitor: Connected to socket
Jan  6 16:31:54 orxpi2 user.info outernet.monitor: Connected to socket
Jan  6 16:31:55 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0439889431 seconds
Jan  6 16:32:55 orxpi2 user.info outernet.monitor: Collecting data
Jan  6 16:32:55 orxpi2 user.info outernet.monitor: Connected to socket
Jan  6 16:32:55 orxpi2 user.info outernet.monitor: Connected to socket
Jan  6 16:32:55 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0366699695587 seconds
^C
ORxPi2 v2.3.001 | root@orxpi2:/home/outernet>

Pasted image1366×728 52.1 KB