It was going so well, then

Things started going a little wacky a few weeks ago. All has run fine for years with minimal issues. But then I noticed the sunrise/sunset was not telling me if it was daylight anymore. Then I lost the roomnode receiver. When I say lost, the serial data stopped displaying in XFX viewer. So I power cycled the HAH. Now the time is out by hours as though it isn't checking with the nntp pool anymore. Maybe it's dropped off the network but no, I can still connect via ethernet.

My DNS address has changed as I have a new broadband router, so I have corrected that via the webserver. 

Member for

14 years 5 months

mark_baldwin

5 years 6 months ago

To add a little more info, I'm running the portable version on a BeagleBone. I have tried to upgrade to the latest firmware but I get a reply from the git pull command that the git is not a repository. Is this something I should worry about too?

Member for

16 years 10 months

brett

5 years 6 months ago

I was able to clone the portable branch without any issue like this:

# git clone --branch portable https://github.com/dbzoo/hah.git

Regarding time sources.  Depending your OS distribution you are either using NTP or CHRONY.
Each is configured differently and you should not have both setup - pick one.
If NTP is running you can see the upstream stratums likes this:
# ntpq -p
To sync the clock you can do this.  Once in sync ntpd will maintain the drift.
# ntpdate -b pool.ntp.org
For chrony its like this:
# chronyc tracking

Member for

14 years 5 months

mark_baldwin

5 years 6 months ago

If I try to sync the clock I get this error message

Error resolving pool.ntp.org: Name or service not known (-2)

26 Jan 04:40:07 ntpdate[1070]: Can't find host pool.ntp.org: Name or service not known (-2)

26 Jan 04:40:07 ntpdate[1070]: no servers can be used, exiting

I am still suspecting the dns isn't working

Member for

16 years 10 months

brett

5 years 6 months ago

That's a DNS issue check your /etc/resolv.conf file.
Normaly it points to your router so it can cache requests/responses you can point it directly at google.

nameserver 8.8.8.8

Member for

14 years 5 months

mark_baldwin

5 years 6 months ago

Sorted it now thanks Brett. The /etc/resolv.conf gets overwritten on mine so had to edit the interfaces file. Got the right dns set now, The other issue ws a faulty USB-TTL converter of the base node. Sorted that and replaced the batteries in the roomnodes (they had all been sending repeat 'moved' messages and expecting a reply, but base node wasn't working)

All up and running again. 

Thanks again for your help Brett. The problem with it running so well for so long is the memory :)

Any update on Derek?

Member for

16 years 10 months

brett

5 years 6 months ago

Glad its sorted.   I was chatting with Derek regularly up until his accident but I've had no direct contact since then.