Meteohub 5.0q - Time sync failed "no servers reachable"

Discussion of the Meteohub software package

Moderator: Mattk

Post Reply
MeteoSheeva
Fresh Boarder
Fresh Boarder
Posts: 11
Joined: Mon Jan 17, 2011 4:55 pm
Location: Germany

Meteohub 5.0q - Time sync failed "no servers reachable"

Post by MeteoSheeva » Tue Jul 26, 2016 12:27 am

Hello,

I realized that after a reboot there is a problem with the time sync on my meteohub installation.
This is causing the recalculation to stop, as the time is not set correctly.
On the 24th of July I could not get any time from the NTP-servers at all.
So I have set it manually.

Since 24th of July I was still running on 4.9y. But even here I was facing this issue some weeks ago.

This is part of my NTP-log:

Code: Select all

 10 Jul 18:42:10 ntpd[1315]: frequency initialized 13.127 PPM from /var/spool/ntp.drift
10 Jul 18:45:25 ntpd[1315]: synchronized to 195.145.119.188, stratum 2
10 Jul 18:45:25 ntpd[1315]: kernel time sync status change 0001
10 Jul 20:52:11 ntpd[1315]: Deleting interface #4 eth0, fd00::250:43ff:fe01:40de#123, interface stats: received=0, sent=0, dropped=0, active_time=7801 secs
 1 Jan 01:00:37 ntpd[1480]: frequency initialized 10.913 PPM from /var/spool/ntp.drift
 1 Jan 01:02:06 ntpd[1480]: ntpd exiting on signal 15
 1 Jan 01:00:45 ntpd[1533]: frequency initialized 10.913 PPM from /var/spool/ntp.drift
 1 Jan 01:00:45 ntpd[1533]: getaddrinfo: "noquery" invalid host address, ignored
 1 Jan 01:05:50 ntpd[1533]: ntpd exiting on signal 15
 1 Jan 01:00:34 ntpd[1277]: frequency initialized 10.913 PPM from /var/spool/ntp.drift
 1 Jan 01:09:01 ntpd[1277]: ntpd exiting on signal 15
 1 Jan 01:00:34 ntpd[1279]: frequency initialized 10.913 PPM from /var/spool/ntp.drift
24 Jul 01:53:01 ntpd[1279]: synchronized to 138.201.145.130, stratum 2
24 Jul 01:53:59 ntpd[1279]: time reset +58.068518 s
24 Jul 01:53:59 ntpd[1279]: kernel time sync status change 0001
24 Jul 02:00:31 ntpd[1279]: synchronized to 130.149.17.21, stratum 1
24 Jul 10:44:20 ntpd[1279]: no servers reachable
24 Jul 11:27:53 ntpd[1279]: synchronized to 130.149.17.21, stratum 1
24 Jul 11:27:53 ntpd[1279]: kernel time sync status change 4001
24 Jul 11:36:26 ntpd[1279]: kernel time sync status change 0001
24 Jul 12:10:37 ntpd[1279]: kernel time sync status change 4001
24 Jul 13:18:53 ntpd[1279]: kernel time sync status change 0001
24 Jul 13:53:04 ntpd[1279]: kernel time sync status change 4001
24 Jul 18:25:16 ntpd[1279]: no servers reachable
I have changed the NTP-servers already, but this has no effect.
I changed twice to different servers and made a reboot after each change.
I could not get any time sync.

System:
Meteohub 5.0q running on Sheevaplug

Current NTP-setup:
NTP1: ntps1-0.cs.tu-berlin.de
NTP2: 1.pool.ntp.org

Is this a known problem?
Thanks for any help you can provide.
"The thing about quotes on the internet is you can not confirm their validity"
                                                                                     - Abraham Lincoln

MeteoSheeva
Fresh Boarder
Fresh Boarder
Posts: 11
Joined: Mon Jan 17, 2011 4:55 pm
Location: Germany

Re: Meteohub 5.0q - Time sync failed "no servers reachable"

Post by MeteoSheeva » Mon Aug 15, 2016 8:48 pm

No one with the same experience?

This is really an issue for me beacause I am facing some power cuts trough the year.
With this problem of time sync the recomputation starts not after an reboot because the time is not set correctly.

Today (15.08.2016) at 19:11 I had an power cut.
As you can see the sync via NTP took quite a while :(

NTP-log

Code: Select all

2 Sep 14:22:23 ntpd[1336]: frequency initialized 12.776 PPM from /var/spool/ntp.drift
 2 Sep 15:38:18 ntpd[1336]: synchronized to 130.149.17.21, stratum 1
15 Aug 20:27:59 ntpd[1336]: time reset +503383781.757844 s
15 Aug 20:27:59 ntpd[1336]: kernel time sync status change 0001
15 Aug 20:37:21 ntpd[1336]: synchronized to 130.149.17.21, stratum 1
meteohub-log

Code: Select all

logger (02.09.2000 14:21:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:22:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:23:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:24:31): System date not properly set. Please set date and time correctly before data logging can start.
wmr928fulleval(02.09.2000 14:25:02): recomputation of weather data started.
logger (02.09.2000 14:25:31): System date not properly set. Please set date and time correctly before data logging can start.
wmr928fulleval(02.09.2000 14:26:07): recomputation of weather data finished: 30131682 records processed in 0 seconds ( records per second)
logger (02.09.2000 14:26:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:27:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:28:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:29:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:30:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:31:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:32:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:33:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:34:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:35:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:36:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:37:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:38:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:39:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:40:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:41:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:42:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:43:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:44:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:45:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:46:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:47:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:48:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:49:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:50:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:51:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:52:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:53:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:54:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:55:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:56:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:57:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:58:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 14:59:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:00:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:01:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:02:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:03:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:04:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:05:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:06:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:07:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:08:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:09:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:10:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:11:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:12:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:13:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:14:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:15:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:16:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:17:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:18:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:19:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:20:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:21:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:22:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:23:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:24:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:25:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:26:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:27:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:28:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:29:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:30:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:31:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:32:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:33:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:34:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:35:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:36:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (02.09.2000 15:37:31): System date not properly set. Please set date and time correctly before data logging can start.
logger (15.08.2016 20:28:13): data logger (version 5.0q, build 1628) started.
logger (15.08.2016 20:28:14): connect station 0 (WMR-200 via USB HID).
logger (15.08.2016 20:31:03): station 0 (WMR-200), wrong checksum (6436 vs computed 03e2) for sensor model d4  in byte sequence: d4 16 04 15 0f 08 10 00 00 d1 d7 10 05 15 0f 08 10 00 bf 00 36 64
logger (15.08.2016 20:36:26): station 0 (WMR-200), wrong checksum (080f vs computed 0263) for sensor model d6  in byte sequence: d6 0d 0a 15 0f 08 10 f8 23 0a 15 0f 08
logger (15.08.2016 20:36:32): station 0 (WMR-200), wrong checksum (150a vs computed 03d8) for sensor model d7  in byte sequence: d7 10 0a 15 0f 08 10 91 c7 00 2a 46 d3 10 0a 15
logger (15.08.2016 20:37:11): station 0 (WMR-200), wrong checksum (d125 vs computed 0125) for sensor model d5  in byte sequence: d5 0a 0a 15 0f 08 10 00 25 d1
logger (15.08.2016 20:38:23): station 0 (WMR-200), wrong checksum (0064 vs computed 03dc) for sensor model d7  in byte sequence: d7 10 d1 d7 10 0c 15 0f 08 10 00 bf 00 36 64 00
As soon as the time is set correctly I have to manually start the recomputation.
This was in the past never a problem.
"The thing about quotes on the internet is you can not confirm their validity"
                                                                                     - Abraham Lincoln

User avatar
YJB
Platinum Boarder
Platinum Boarder
Posts: 387
Joined: Thu Feb 19, 2009 5:53 pm
Location: Venhuizen, Netherlands
Contact:

Re: Meteohub 5.0q - Time sync failed "no servers reachable"

Post by YJB » Wed Aug 17, 2016 9:04 am

Hi,

Not sure if this is related, but I used to have issues with time as well. I added the following to the root crontab, which essentially forces the timesync every hour:

Code: Select all

1 * * * * /usr/sbin/ntpdate -u 0.pool.ntp.org 1.pool.ntp.org >> /tmp/ntpdate.log 2>&1
hope this helps.

MeteoSheeva
Fresh Boarder
Fresh Boarder
Posts: 11
Joined: Mon Jan 17, 2011 4:55 pm
Location: Germany

Re: Meteohub 5.0q - Time sync failed "no servers reachable"

Post by MeteoSheeva » Wed Aug 17, 2016 10:49 pm

Is this complicated to implement? I am not that familiar with Linux-stuff :)
"The thing about quotes on the internet is you can not confirm their validity"
                                                                                     - Abraham Lincoln

User avatar
YJB
Platinum Boarder
Platinum Boarder
Posts: 387
Joined: Thu Feb 19, 2009 5:53 pm
Location: Venhuizen, Netherlands
Contact:

Re: Meteohub 5.0q - Time sync failed "no servers reachable"

Post by YJB » Wed Aug 17, 2016 10:55 pm

I guess it's not too difficult, but obviously you will need to be careful.

Normally one edits the crontab with "crontab -e"

If you add the line exactly as I did specify, it will sync the time every hour at xx:01

fh_cologne
Fresh Boarder
Fresh Boarder
Posts: 4
Joined: Thu Nov 29, 2012 3:01 pm

Re: Meteohub 5.0q - Time sync failed "no servers reachable"

Post by fh_cologne » Thu Aug 18, 2016 10:18 pm

I have exactly the same problem. Is there any other solution? It worked fine in the past years...

MeteoSheeva
Fresh Boarder
Fresh Boarder
Posts: 11
Joined: Mon Jan 17, 2011 4:55 pm
Location: Germany

Re: Meteohub 5.0q - Time sync failed "no servers reachable"

Post by MeteoSheeva » Sun Jul 23, 2017 5:54 pm

For me the problem is still unsolved.
Today I was working on the meteohub to fix some corrupted measurement data and update to the latest version.

Now I can watch live that there is not time sync and the start of collecting data is stopping :(

Code: Select all

 1 Jan 01:00:36 ntpd[1485]: frequency initialized -3.695 PPM from /var/spool/ntp.drift
 1 Jan 01:00:41 ntpd[1485]: getaddrinfo: "noquery" invalid host address, ignored
 1 Jan 01:01:58 ntpd[1485]: ntpd exiting on signal 15
 1 Jan 01:00:35 ntpd[1485]: frequency initialized -3.695 PPM from /var/spool/ntp.drift
 1 Jan 01:00:35 ntpd[1485]: getaddrinfo: "noquery" invalid host address, ignored
 1 Jan 01:02:16 ntpd[1485]: ntpd exiting on signal 15
 1 Jan 01:00:36 ntpd[1485]: frequency initialized -3.695 PPM from /var/spool/ntp.drift
 1 Jan 01:00:36 ntpd[1485]: getaddrinfo: "noquery" invalid host address, ignored

@YJB
How can I access the crontab to add any additional code?
"The thing about quotes on the internet is you can not confirm their validity"
                                                                                     - Abraham Lincoln

User avatar
YJB
Platinum Boarder
Platinum Boarder
Posts: 387
Joined: Thu Feb 19, 2009 5:53 pm
Location: Venhuizen, Netherlands
Contact:

Re: Meteohub 5.0q - Time sync failed "no servers reachable"

Post by YJB » Sat Aug 05, 2017 8:49 am

As said earlier, "crontab -e" allows you to modify the crontab.

Post Reply