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

branko · 2016-01-04T16:14:14.865Z

Probably some DNS error.

EDIT: I’m not a networking expert, so I don’t have instructions on troubleshooting that off the top of my head. I could look around, though.

pradeeka · 2016-01-04T16:14:49.482Z

mmm. you mean which side?

branko · 2016-01-04T16:15:28.236Z

My guess is that your ISP’s DNS server is not very fast/reliable.

pradeeka · 2016-01-04T16:21:10.628Z

I have two routers and each one has totally different connections and Internet Service Providers .
4G router - fixed broadband connection (ISP - A)
3G router - connected a dongle with 3G SIM (connection) (ISP - B)

I haven’t ADSL connection to test this.

branko · 2016-01-04T16:23:48.106Z

I tested with 3G a while back and everything was working normally. My ISP can have slow DNS lookups from time to time, though.

pradeeka · 2016-01-04T16:44:02.279Z

I restarted the monitoring manually (LH)

login as: outernet
outernet@192.168.0.1's password:
outernet@outernet:~$ sudo /etc/init.d/S91monitoring restart
Password:
Stopping monitoring: OK
Starting monitoring: OK
outernet@outernet:~$

I’m getting red-dot

Pasted image1366×728 52 KB

branko · 2016-01-04T16:48:49.147Z

Try this:

tail -f /var/log/messages | grep monitor

Leave that on and when you notice it’s locking up again, restart and see if it immediately starts sending.

manishpmathai · 2016-01-04T16:55:14.008Z

Can you post a screenshot of the tuner section from the dashboard ?

pradeeka · 2016-01-04T16:56:38.019Z

Pasted image1366×728 62.6 KB

pradeeka · 2016-01-04T17:09:09.435Z

After restating the LH, I’m continuously getting the red-dot.

manishpmathai · 2016-01-04T17:23:33.867Z

The monitoring script in LH v2.1.000 had an issue (which causes the red-dot) which was fixed in later versions. You should update Lighthouse to the latest image (v2.3.000)

pradeeka · 2016-01-04T17:29:28.235Z

Thanks Manish, ready to update the LH to latest version. Will update on this thread…

pradeeka · 2016-01-04T17:45:36.157Z

Yes. After updating to the latest image, it is now reporting.

Pasted image1366×728 51.8 KB

manishpmathai · 2016-01-04T17:45:43.217Z

That you pradeeka ?

Screenshot from 2016-01-04 23:15:05.png765×564 43.1 KB

pradeeka · 2016-01-04T17:46:13.183Z

yes
EDIT: Then why the ORxPi is not reporting through the same ISP?

branko · 2016-01-04T17:51:11.022Z

Not sure. Anyway, can you tried what I originally suggested? Boot Pi, run the tail command and watch until it stops transmitting then restart monitoring immediately.

Command is

tail -f /var/log/messages | grep monitor

pradeeka · 2016-01-04T17:53:32.417Z

okay. now i’m going to connect my orxpi with the dish again and remove the lighthouse from it. will update soon.

branko · 2016-01-04T17:56:30.821Z

K, thanks.

pradeeka · 2016-01-04T18:10:06.995Z

After booting, my Pi receiver is starting to report automatically without running any of the above commands.

This time I started the Pi with LAN cable attached. Previously I hot plugged it every time. Is this the case?

Pasted image1366×728 52 KB

EDIT: Tomorrow I will try to recreate this issue again and verify. Now time to sleep

branko · 2016-01-04T18:23:14.479Z

pradeeka:

running any of the above commands.

The tail command is for monitoring the logs so you can see when it stops reporting.