Zee S2 loosing time (hours off)

[Findus]

Result after ntpq -p commando

homeseer@HomeTrollerZeeS2 /etc $ ntpq -p
remote refid st t when poll reach delay offset jitter
============================================================ ==================
Time100.Stupi.S .XFAC. 16 u - 1024 0 0.000 0.000 0.000
hubbard.kohina. .XFAC. 16 u - 1024 0 0.000 0.000 0.000
ntp.jine.se .XFAC. 16 u - 1024 0 0.000 0.000 0.000
ntp2.flashdance .XFAC. 16 u - 1024 0 0.000 0.000 0.000
homeseer@HomeTrollerZeeS2 /etc $

Result, no connection to ntp server.

Try restart ntp, but the same.
Change ntp.conf file.
Manually set pointer to time servers (in Sweden)
Restart ntp
Now!! Date and time is correct!


Homework to myself
Buy a RTC cards!!!
Knowledge in the support department is deficient.

[Rupp]

Homework to myself
Buy a RTC cards!!!

The time is checked approximately every 5 minutes so an RTC card isn't needed unless you have the CPU pegged in this unit. The pegging of the CPU can cause these time loss issues as well and will prevent the checking of the time server.

[Pete]

Just tried it here looking....

home# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 x.ns.gin.ntt.ne 249.224.99.213   2 u   16   64    1   11.464  141.179   0.001
 vimo.dorui.net  209.51.161.238   2 u   15   64    1   31.458  140.660   0.001
 104.156.99.226  204.123.2.72     2 u   14   64    1   56.053  139.452   0.001
 4.53.160.75     142.66.101.13    2 u   14   64    1   16.288  141.370   0.001
 juniperberry.ca 193.79.237.14    2 u   13   64    1  109.314  135.203   0.001
home# ntpq -p 192.168.244.129
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
[B]oGPS_NMEA(0)     .GPS.            0 l    1   16  377    0.000    0.000   0.002[/B]
*4.53.160.75     142.66.101.13    2 u   44   64  377   15.569    2.599   2.062
+linode227395.st 192.5.41.40      2 u   29   64  377   30.052    1.384  31.054

As Rupp mentions you do not need an RTC with battery. That said I did it because I wanted to keep the time when starting HS3 and there are folks doing automation today without any dependencies on the internet.

I use it for my Davis Vantage Pro weather station Cumulus MX software which provides the time to the Davis Vantage Vue console which updates the NOAA, WUN, Personal weather website.

[jhearty]

Brian, you should try the "top -b -n 1" command shown on the linux tools page you started using to see if it looks like your CPU is pegged as Rupp suggests could be the cause of the problem. If it is, start looking at your events to see if you might be triggering on something that is not a moment in time. You can read Randy Prade's Event Clinic articles for more details about that.

John

[bcnorton]

Brian, you should try the "top -b -n 1" command shown on the linux tools page you started using to see if it looks like your CPU is pegged as Rupp suggests could be the cause of the problem. If it is, start looking at your events to see if you might be triggering on something that is not a moment in time. You can read Randy Prade's Event Clinic articles for more details about that.

John

Okay, did it. This is what it said...

running comand top -b -n 1 top - 20:08:32 up 2 days, 27 min, 0 users, load average: 0.02, 0.02, 0.05
Tasks: 90 total, 1 running, 89 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.6 us, 0.2 sy, 0.0 ni, 99.1 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem: 949408 total, 347488 used, 601920 free, 35296 buffers
KiB Swap: 102396 total, 0 used, 102396 free, 125600 cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
24558 root 20 0 4676 2380 2104 R 11.5 0.3 0:00.05 top
9113 root 20 0 105m 68m 20m S 5.8 7.4 53:20.86 mono
1 root 20 0 2148 1364 1260 S 0.0 0.1 0:05.11 init
2 root 20 0 0 0 0 S 0.0 0.0 0:00.05 kthreadd
3 root 20 0 0 0 0 S 0.0 0.0 0:10.37 ksoftirqd/0
5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0H
7 root 20 0 0 0 0 S 0.0 0.0 1:00.42 rcu_preempt
8 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_sched
9 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh
10 root rt 0 0 0 0 S 0.0 0.0 0:00.20 migration/0
11 root rt 0 0 0 0 S 0.0 0.0 0:00.18 migration/1
12 root 20 0 0 0 0 S 0.0 0.0 0:00.48 ksoftirqd/1
14 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/1:0H
15 root rt 0 0 0 0 S 0.0 0.0 0:00.24 migration/2
16 root 20 0 0 0 0 S 0.0 0.0 0:00.40 ksoftirqd/2
18 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/2:0H
19 root rt 0 0 0 0 S 0.0 0.0 0:00.19 migration/3
20 root 20 0 0 0 0 S 0.0 0.0 0:00.35 ksoftirqd/3
22 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/3:0H
23 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 khelper
24 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kdevtmpfs
25 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 netns
26 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 perf
27 root 20 0 0 0 0 S 0.0 0.0 0:00.12 khungtaskd
28 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 writeback
29 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 crypto
30 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
31 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kblockd
32 root 20 0 0 0 0 S 0.0 0.0 1:09.76 kworker/0:1
33 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 rpciod
34 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kswapd0
35 root 20 0 0 0 0 S 0.0 0.0 0:00.00 fsnotify_mark
36 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 nfsiod
42 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kthrotld
43 root 1 -19 0 0 0 S 0.0 0.0 0:00.00 VCHIQ-0
44 root 1 -19 0 0 0 S 0.0 0.0 0:00.00 VCHIQr-0
45 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 VCHIQs-0
46 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 iscsi_eh
47 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 dwc_otg
48 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 DWC Notificatio
50 root 20 0 0 0 0 S 0.0 0.0 0:00.00 VCHIQka-0
51 root 10 -10 0 0 0 S 0.0 0.0 0:00.00 SMIO
52 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 deferwq
54 root 20 0 0 0 0 S 0.0 0.0 0:18.52 kworker/1:1
55 root 20 0 0 0 0 S 0.0 0.0 0:03.81 mmcqd/0
56 root 20 0 0 0 0 S 0.0 0.0 0:01.48 jbd2/mmcblk0p6-
57 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 ext4-rsv-conver
61 root 20 0 0 0 0 S 0.0 0.0 0:13.57 kworker/2:1
181 root 20 0 2892 2204 1672 S 0.0 0.2 0:00.36 udevd
314 root 20 0 2888 1968 1428 S 0.0 0.2 0:00.01 udevd
315 root 20 0 2888 1968 1428 S 0.0 0.2 0:00.00 udevd
567 root 20 0 1684 68 0 S 0.0 0.0 0:18.93 logsave
1197 root 20 0 1684 68 0 S 0.0 0.0 0:19.52 logsave
1544 root 20 0 1756 1052 964 S 0.0 0.1 1:19.66 ifplugd
1546 root 20 0 1756 1164 1076 S 0.0 0.1 0:16.19 ifplugd
1800 nobody 20 0 2024 1412 1288 S 0.0 0.1 0:02.19 thd
1842 root 20 0 29132 2488 2160 S 0.0 0.3 0:21.48 rsyslogd
1980 root 20 0 3832 1916 1724 S 0.0 0.2 0:01.22 cron
2044 messageb 20 0 3184 1368 1136 S 0.0 0.1 0:00.00 dbus-daemon
2107 root 20 0 4904 3480 1760 S 0.0 0.4 0:00.02 dhclient
2165 root 20 0 6224 2772 2344 S 0.0 0.3 0:00.00 sshd
2174 www-data 20 0 6680 1916 1272 S 0.0 0.2 0:10.60 lighttpd
2176 www-data 20 0 19756 9708 8000 S 0.0 1.0 0:00.08 php-cgi
2208 www-data 20 0 19756 1948 240 S 0.0 0.2 0:00.00 php-cgi
2209 www-data 20 0 19756 1948 240 S 0.0 0.2 0:00.00 php-cgi
2210 www-data 20 0 19756 1948 240 S 0.0 0.2 0:00.00 php-cgi
2211 www-data 20 0 19756 1948 240 S 0.0 0.2 0:00.00 php-cgi
2219 root 20 0 3608 2256 1992 S 0.0 0.2 0:00.02 sudo
2224 root 20 0 1700 1116 1036 S 0.0 0.1 0:00.42 startpar
2225 root 20 0 3756 1748 1616 S 0.0 0.2 0:00.01 getty
2226 root 20 0 3756 1696 1564 S 0.0 0.2 0:00.01 getty
2227 root 20 0 3756 1604 1472 S 0.0 0.2 0:00.01 getty
2228 root 20 0 3756 1644 1512 S 0.0 0.2 0:00.01 getty
2229 root 20 0 3756 1704 1572 S 0.0 0.2 0:00.01 getty
2230 root 20 0 3756 1644 1512 S 0.0 0.2 0:00.01 getty
2231 root 20 0 1764 340 288 S 0.0 0.0 0:00.00 autostart_hs
2233 root 20 0 140m 85m 19m S 0.0 9.3 46:12.13 mono
2278 root 20 0 76116 45m 15m S 0.0 4.9 16:11.12 mono
2342 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/1:1H
20635 ntp 20 0 5524 3232 2848 S 0.0 0.3 0:04.67 ntpd
22616 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kworker/2:0
23206 root 20 0 0 0 0 S 0.0 0.0 0:05.34 kworker/3:1
23529 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kworker/1:0
23563 root 20 0 0 0 0 S 0.0 0.0 0:00.39 kworker/u8:0
24024 root 20 0 0 0 0 S 0.0 0.0 0:00.42 kworker/u8:1
24480 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kworker/3:0
24483 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0
24517 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kworker/0:2
24557 root 20 0 1764 364 312 S 0.0 0.0 0:00.02 run_command.sh
24559 root 20 0 1560 276 224 S 0.0 0.0 0:00.00 aha

[rmasonjr]

Those numbers indicate your system is fine. There is very little CPU being consumed.

Sent from my SCH-R970X using Tapatalk

[bcnorton]

Thanks for the translation! I've no idea what that said!

[bcnorton]

I would bet that something is blocking NTP traffic or a DNS issue.
Can you SSH to the box and run:
ntpq -p

(or you can run it from the HS Tools menu)

running comand ntpq -p remote refid st t when poll reach delay offset jitter
============================================================ ==================
+repos.lax-noc.c 216.218.254.202 2 u 375 1024 277 41.518 -1.800 9.559
*tock.usshc.com .GPS. 1 u 401 1024 377 37.482 2.397 8.696
+x.ns.gin.ntt.ne 249.224.99.213 2 u 243 1024 377 9.554 1.042 52.425
+bd.90.caa1.ip4. 133.243.238.243 2 u 259 1024 177 149.126 3.670 12.080

[jhearty]

No problems for that snapshot. Check from time to time to see if the first line has %CPU near 100. You should also read the Event Clinic posts to see if you have any events with triggers that could be causing your CPU to peg.

http://board.homeseer.com/showthread.php?t=173360
http://board.homeseer.com/showthread.php?t=172750 "This trigger is the first to offer a choice that can lead to a runaway event."

Here is the Table of Contents to Randy's posts. All of it is a must read when new to HS3.
http://forums.homeseer.com/showthread.php?t=172984

John

[Pete]

@John-Rob

What does your HS3 Linux commands script look like?

Here my commands run but see this and never use it these days>>>

Running command df -H Filesystem Size Used Avail Use% Mounted on /dev/root 16G 9.0G 6.0G 60% / devtmpfs 506M 0 506M 0% /dev tmpfs 103M 226k 102M 1% /run tmpfs 5.3M 0 5.3M 0% /run/lock tmpfs 205M 13k 205M 1% /run/shm /dev/mmcblk0p1 59M 21M 38M 36% /boot

Think it is using run_command_raw.sh and it looks like this:

#!/bin/sh
echo "Running command $1"

# $1

# echo "%s\n" "$1"
$1

Relating to time sync in general never did like the dependency on the internet for time / automation.

Kind of a kludge with a crutch/dependency to the internet.

Recently modded one Homeseer Intel based tabletop touch screen with an RTC and battery (via a bit of soldering to some GPIO pins).

Attached is an SSH Applet that I include with my base HS3 build these days.

[mstukel]

https://www.cyberciti.biz/faq/linux-...lient-working/ and https://www.howtogeek.com/tips/how-t...e-servers-ntp/