[nos-bbs] Where has the time gone? --SOLVED

[jerome schatten]

Tom et al.

Since there was other stuff that was a bit haywire, I reformatted the card and re-installed the entire OS. Fortunately I had had a backup of the jnos directory on a usb stick, and I was able to re-install else everything from that. Seems all is well again.  Not a very elegant fix, but lI earned a few things along the way and we’re back on the air.
Thanks to all that responded!
jerome

> On Jul 15, 2017, at 22:17, SP2L <SP2L at sp2l.ampr.org> wrote:
> 
> Jerome.
> 
> 
> That looks O.K.
> At least you know that NTP client work as it should.
> I suspect troublemaker might lie in firewall settings.
> 
> Remotely is a bit difficult to find clue for what is going on...
> 
> 
> Best regards.
> Tom - SP2L
> 
> 
> 
> On 16/07/17 00:43, jerome schatten wrote:
>> Tom
>> 
>> OK below is the tests I did.  Essentially I got the status (running); then stopped the service; and the restarted it.  Then I left it running and ran tcpdump on port 123, and there was nothing. So no client/server interchanges at all.
>> 
>> ———————————————cut here-------------------------------
>> pi at raspberrypi:~ $
>> pi at raspberrypi:~ $
>> pi at raspberrypi:~ $ systemctl status ntp.service -l
>> ● ntp.service - LSB: Start NTP daemon
>>    Loaded: loaded (/etc/init.d/ntp)
>>    Active: active (running) since Fri 2017-07-14 15:03:03 PDT; 23h ago
>>   Process: 500 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS)
>>    CGroup: /system.slice/ntp.service
>>            ├─543 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 106:111
>>            └─549 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 106:111
>> pi at raspberrypi:~ $ sudo sytemctl stop ntp.service
>> pi at raspberrypi:~ $ sudo systemctl stop ntp.service
>> pi at raspberrypi:~ $
>> pi at raspberrypi:~ $ sudo systemctl start ntp.service
>> pi at raspberrypi:~ $
>> pi at raspberrypi:~ $ systemctl status ntp.service -l
>> ● ntp.service - LSB: Start NTP daemon
>>    Loaded: loaded (/etc/init.d/ntp)
>>    Active: active (running) since Sat 2017-07-15 14:39:25 PDT; 42s ago
>>   Process: 2683 ExecStop=/etc/init.d/ntp stop (code=exited, status=0/SUCCESS)
>>   Process: 2704 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS)
>>    CGroup: /system.slice/ntp.service
>>            └─2712 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 106:111
>> 
>> —————————————cut here ——————————————————————
>> 
>> So it looks like it’s working.  I reset the time with ‘date’ and brought the machine down and left it for several minutes. Brought the machine back up and I had lost ten minutes.  Looking at tcpdump port 123, I saw no packets at all.
>> 
>> On the pi that’s working OK (the bpq pi), monitoring port 123, I see a transaction betwee client and server periodically as expected.
>> 
>> That’s the story
>> j.
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> On Jul 15, 2017, at 14:28, jerome schatten <romers at shaw.ca> wrote:
>>> 
>>> Let me backtrack a moment…
>>> 
>>> I am able to initially change the time with the ‘date’, but now I see it drops the ten minutes again sometime later. So the answer to your initial question Tom is no, I can’t successfully reset the time with the ‘date’ command.
>>> 
>>> I will look at systemctl as outlined below
>>> j.
>>> 
> 
> -- 
> Tom - SP2L
> ------------------------------------
> It is nice to be important.
> But it is more important to be nice!
>