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

pradeeka · January 4, 2016, 6:31pm

yes, it is running now. I’m sleepng with my laptop

ORxPi2 v2.3.001 | root@orxpi2:/home/outernet> tail -f /var/log/messages | grep m
onitor
Jan  4 18:25:31 orxpi2 user.info outernet.monitor: Finished collecting data in 0                                                                                        .0575609207153 seconds
Jan  4 18:25:31 orxpi2 user.info outernet.monitor: Transmitting buffered data
Jan  4 18:25:35 orxpi2 user.info outernet.monitor: Transmission complete, clarin                                                                                        g local buffer
Jan  4 18:26:35 orxpi2 user.info outernet.monitor: Collecting data
Jan  4 18:26:35 orxpi2 user.info outernet.monitor: Connected to socket
Jan  4 18:26:35 orxpi2 user.info outernet.monitor: Connected to socket
Jan  4 18:26:35 orxpi2 user.info outernet.monitor: Finished collecting data in 0                                                                                        .0411190986633 seconds
Jan  4 18:27:35 orxpi2 user.info outernet.monitor: Collecting data
Jan  4 18:27:35 orxpi2 user.info outernet.monitor: Connected to socket
Jan  4 18:27:35 orxpi2 user.info outernet.monitor: Connected to socket
Jan  4 18:27:35 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0365629196167 seconds
Jan  4 18:28:35 orxpi2 user.info outernet.monitor: Collecting data
Jan  4 18:28:35 orxpi2 user.info outernet.monitor: Connected to socket
Jan  4 18:28:35 orxpi2 user.info outernet.monitor: Connected to socket
Jan  4 18:28:35 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0410718917847 seconds
Jan  4 18:29:35 orxpi2 user.info outernet.monitor: Collecting data
Jan  4 18:29:35 orxpi2 user.info outernet.monitor: Connected to socket
Jan  4 18:29:35 orxpi2 user.info outernet.monitor: Connected to socket
Jan  4 18:29:36 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0586009025574 seconds

branko · January 4, 2016, 6:32pm

LOL

manishpmathai · January 5, 2016, 10:14am

@pradeeka
Hope you haven’t broken your laptop
Is your ORxPi still connected to the router ?

pradeeka · January 5, 2016, 10:21am

Yeah, It is working…

No. I disconnected it today morning and Pi is not up and running now. I will start it again around 8 PM SLST.

pradeeka · January 5, 2016, 2:36pm

Now my ORxPi is up and running. But it is not reporting.

ORxPi2 v2.3.001 | root@orxpi2:/home/outernet> tail -f /var/log/messages | grep m
onitor
Jan  5 14:29:29 orxpi2 user.info outernet.monitor: Collecting data
Jan  5 14:29:29 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 14:29:29 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 14:29:29 orxpi2 user.info outernet.monitor: Finished collecting data in 0                                                                                        .0375258922577 seconds
Jan  5 14:29:29 orxpi2 user.info outernet.monitor: Transmitting buffered data
Jan  5 14:29:29 orxpi2 user.info outernet.monitor: Could not establish connectio                                                                                        n to http://status.outernet.is/heartbeat/v1/: HTTP Error 404: Not Found
Jan  5 14:30:29 orxpi2 user.info outernet.monitor: Collecting data
Jan  5 14:30:29 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 14:30:29 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 14:30:29 orxpi2 user.info outernet.monitor: Finished collecting data in 0.038006067276 seconds
Jan  5 14:30:29 orxpi2 user.info outernet.monitor: Transmitting buffered data
Jan  5 14:30:29 orxpi2 user.info outernet.monitor: Could not establish connection to http://status.outernet.is/heartbeat/v1/: HTTP Error 404: Not Found
Jan  5 14:31:29 orxpi2 user.info outernet.monitor: Collecting data
Jan  5 14:31:29 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 14:31:30 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 14:31:30 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0372400283813 seconds
Jan  5 14:32:30 orxpi2 user.info outernet.monitor: Collecting data
Jan  5 14:32:30 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 14:32:30 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 14:32:30 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0376329421997 seconds
Jan  5 14:32:30 orxpi2 user.info outernet.monitor: Transmitting buffered data
Jan  5 14:32:30 orxpi2 user.info outernet.monitor: Could not establish connection to http://status.outernet.is/heartbeat/v1/: HTTP Error 404: Not Found
Jan  5 14:33:30 orxpi2 user.info outernet.monitor: Collecting data
Jan  5 14:33:30 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 14:33:30 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 14:33:30 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0396299362183 seconds
Jan  5 14:33:30 orxpi2 user.info outernet.monitor: Transmitting buffered data
Jan  5 14:33:30 orxpi2 user.info outernet.monitor: Could not establish connection to http://status.outernet.is/heartbeat/v1/: HTTP Error 404: Not Found

branko · January 5, 2016, 2:38pm

Is that right after boot?

pradeeka · January 5, 2016, 2:42pm

No. reporting doesn’t get started automatically.
I did 4 or 5 restarts.

branko · January 5, 2016, 2:44pm

How do you know it’s not starting automatically?

pradeeka · January 5, 2016, 2:49pm

It only starts when I run the command sudo /etc/init.d/S91monitoring restart.

Am I using incorrect term (reporting or monitoring)? Please correct.

branko · January 5, 2016, 3:11pm

I’m trying to figure out how you know that it’s not starting on boot. What do you do to find out if it’s running?

pradeeka · January 5, 2016, 4:41pm

Yes, monitoring is up and running automatically.Sorry about the confusion.

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

But the issue is that monitoring couldn’t establish the connection with heartbeat.

branko · January 5, 2016, 4:47pm

So ok, we need to know if it never connects, or if it stops connecting after a while.

pradeeka · January 5, 2016, 4:53pm

now it is connected.

Jan  5 16:48:36 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 16:48:36 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0383839607239 seconds
Jan  5 16:49:36 orxpi2 user.info outernet.monitor: Collecting data
Jan  5 16:49:36 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 16:49:36 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 16:49:36 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0371680259705 seconds
Jan  5 16:50:36 orxpi2 user.info outernet.monitor: Collecting data
Jan  5 16:50:36 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 16:50:36 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 16:50:36 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0394809246063 seconds
Jan  5 16:51:36 orxpi2 user.info outernet.monitor: Collecting data
Jan  5 16:51:36 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 16:51:36 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 16:51:36 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0423290729523 seconds

Jan  5 16:53:36 orxpi2 user.info outernet.monitor: Transmitting buffered data
Jan  5 16:53:41 orxpi2 user.info outernet.monitor: Transmission complete, claring local buffer

EDIT:
yes. sometimes stops connecting.

Jan  5 16:56:41 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0513401031494 seconds
Jan  5 16:57:41 orxpi2 user.info outernet.monitor: Collecting data
Jan  5 16:57:41 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 16:57:41 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 16:57:41 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0423941612244 seconds
Jan  5 16:58:41 orxpi2 user.info outernet.monitor: Collecting data
Jan  5 16:58:41 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 16:58:41 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 16:58:41 orxpi2 user.info outernet.monitor: Finished collecting data in 0.04851603508 seconds
Jan  5 16:59:41 orxpi2 user.info outernet.monitor: Collecting data
Jan  5 16:59:41 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 16:59:41 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 16:59:41 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0374619960785 seconds
Jan  5 16:59:41 orxpi2 user.info outernet.monitor: Transmitting buffered data
Jan  5 16:59:46 orxpi2 user.info outernet.monitor: Could not establish connection to http://status.outernet.is/heartbeat/v1/: HTTP Error 400: Bad Request

branko · January 5, 2016, 5:25pm

Once it stops connecting, does it continue to fail to connect indefinitely, or it recovers on its own at some point?

pradeeka · January 5, 2016, 5:30pm

most of the time it fail to connect continually. but rarely connects.

Jan  5 17:23:34 orxpi2 user.info outernet.monitor: Could not establish connection to http://status.outernet.is/heartbeat/v1/: HTTP Error 400: Bad Request
Jan  5 17:24:34 orxpi2 user.info outernet.monitor: Collecting data
Jan  5 17:24:34 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 17:24:34 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 17:24:34 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0405330657959 seconds
Jan  5 17:24:34 orxpi2 user.info outernet.monitor: Transmitting buffered data
Jan  5 17:24:38 orxpi2 user.info outernet.monitor: Could not establish connection to http://status.outernet.is/heartbeat/v1/: HTTP Error 400: Bad Request
Jan  5 17:25:38 orxpi2 user.info outernet.monitor: Collecting data
Jan  5 17:25:38 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 17:25:38 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 17:25:38 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0367519855499 seconds
Jan  5 17:25:38 orxpi2 user.info outernet.monitor: Transmitting buffered data
Jan  5 17:25:42 orxpi2 user.info outernet.monitor: Could not establish connection to http://status.outernet.is/heartbeat/v1/: HTTP Error 400: Bad Request
Jan  5 17:26:42 orxpi2 user.info outernet.monitor: Collecting data
Jan  5 17:26:42 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 17:26:42 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 17:26:42 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0414988994598 seconds
Jan  5 17:26:42 orxpi2 user.info outernet.monitor: Transmitting buffered data
Jan  5 17:26:46 orxpi2 user.info outernet.monitor: Could not establish connection to http://status.outernet.is/heartbeat/v1/: HTTP Error 400: Bad Request
Jan  5 17:27:46 orxpi2 user.info outernet.monitor: Collecting data
Jan  5 17:27:46 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 17:27:46 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 17:27:46 orxpi2 user.info outernet.monitor: Finished collecting data in 0.0410051345825 seconds
Jan  5 17:27:46 orxpi2 user.info outernet.monitor: Transmitting buffered data
Jan  5 17:27:50 orxpi2 user.info outernet.monitor: Transmission complete, claring local buffer
Jan  5 17:28:50 orxpi2 user.info outernet.monitor: Collecting data
Jan  5 17:28:50 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 17:28:50 orxpi2 user.info outernet.monitor: Connected to socket
Jan  5 17:28:50 orxpi2 user.info outernet.monitor: Finished collecting data in 0.043664932251 seconds

branko · January 5, 2016, 5:58pm

Try this:

stop monitoring service
run the following command:

watch "wget http://status.outernet.is/ -O - 2>&1 | head -n4"

This command will continue to ping status.outernet.is and print the first 4 lines of the HTML. If it this fails at some point.

pradeeka · January 5, 2016, 6:14pm

for every ping it shows this. can’t identify any failure.

branko · January 5, 2016, 6:41pm

Let me figure out some way to have it run a bit longer w/o needing human assistance.

branko · January 5, 2016, 6:47pm

Ok, here we go:

watch -n30 'echo $(date +%H:%M:%S) $(ping -c 1 status.outernet.is 2>&1 >/dev/null && echo "OK" || echo "NG") | tee pinglog.txt'

Let this run for 30 minutes or so, maybe longer if you can. It will generate a pinglog.txt file. Check it later and see if it shows NG anywhere.

manishpmathai · January 6, 2016, 11:38am

The last part, tee needs an append flag.

watch -n30 'echo $(date +%H:%M:%S) $(ping -c 1 status.outernet.is 2>&1 >/dev/null && echo "OK" || echo "NG") | tee -a pinglog.txt'