freeswitch_exporter icon indicating copy to clipboard operation
freeswitch_exporter copied to clipboard

time not in sync between system and FS

Open itlevel3 opened this issue 2 years ago • 2 comments

Hello,

Thank you for this exporter, it's been very helpful and we appreciate the work you've put into it. We use the exporter to send FS specific info to NetData.

We see this error in the logs: Jul 21 16:25:36 fs01-redacted.redacted.com freeswitch_exporter-linux-amd64[32698]: 2022/07/21 16:25:36 [warning] time not in sync between system (1658420736) and FreeSWITCH (1658420735)

We've verified that FS and the system are in sync but the error reports they are always 1 second apart.

[redacted@fs01-redacted system]# fs_cli -x 'strftime' ; timedatectl 2022-07-21 16:24:05 Local time: Thu 2022-07-21 16:24:05 UTC Universal time: Thu 2022-07-21 16:24:05 UTC RTC time: Thu 2022-07-21 16:24:05 Time zone: UTC (UTC, +0000) NTP enabled: yes NTP synchronized: yes RTC in local TZ: no DST active: n/a

We've also tried forcing a sync using the following command, but that did not help: fs_cli -x 'fsctl sync_clock'

Have you seen this issue before? Any suggestions? Thank you in advance.

itlevel3 avatar Jul 21 '22 16:07 itlevel3

Hello,

It seems odd especially if you have run fsctl sync_clock. Try running this command:

# while ((42)); do fs_cli -x strftime && date; sleep .2; done
2022-07-21 17:57:01
Thu Jul 21 17:57:01 UTC 2022
2022-07-21 17:57:01
Thu Jul 21 17:57:01 UTC 2022
2022-07-21 17:57:01
Thu Jul 21 17:57:01 UTC 2022
2022-07-21 17:57:02
Thu Jul 21 17:57:02 UTC 2022
2022-07-21 17:57:02
Thu Jul 21 17:57:02 UTC 2022
2022-07-21 17:57:02
Thu Jul 21 17:57:02 UTC 2022
2022-07-21 17:57:02
Thu Jul 21 17:57:02 UTC 2022
2022-07-21 17:57:02
Thu Jul 21 17:57:02 UTC 2022

To see if it's not a sub second delay. Also, try to restart the exporter after you have run sync_clock to make sure the Go program reads the wall clock properly.

florentchauveau avatar Jul 21 '22 18:07 florentchauveau

Hi,

We restarted the exporter after running sync_clock and unfortunately, the issue persists.

RE your suggestion, it could very well be a sub-second delay. The output below shows at least one occurrence where the seconds don't match.

[redacted@fs01-redacted ~]# while ((42)); do fs_cli -x strftime && date; sleep .2; done 2022-07-22 17:02:07 Fri Jul 22 17:02:07 UTC 2022 2022-07-22 17:02:07 Fri Jul 22 17:02:07 UTC 2022 2022-07-22 17:02:08 Fri Jul 22 17:02:08 UTC 2022 2022-07-22 17:02:08 Fri Jul 22 17:02:08 UTC 2022 2022-07-22 17:02:08 Fri Jul 22 17:02:08 UTC 2022 2022-07-22 17:02:08 Fri Jul 22 17:02:08 UTC 2022 2022-07-22 17:02:09 Fri Jul 22 17:02:09 UTC 2022 2022-07-22 17:02:09 Fri Jul 22 17:02:09 UTC 2022 2022-07-22 17:02:09 Fri Jul 22 17:02:09 UTC 2022 2022-07-22 17:02:09 Fri Jul 22 17:02:09 UTC 2022 2022-07-22 17:02:09 Fri Jul 22 17:02:10 UTC 2022 2022-07-22 17:02:10 Fri Jul 22 17:02:10 UTC 2022 2022-07-22 17:02:10 Fri Jul 22 17:02:10 UTC 2022 2022-07-22 17:02:10 Fri Jul 22 17:02:10 UTC 2022 2022-07-22 17:02:10 Fri Jul 22 17:02:10 UTC 2022 2022-07-22 17:02:11 Fri Jul 22 17:02:11 UTC 2022 2022-07-22 17:02:11 Fri Jul 22 17:02:11 UTC 2022 2022-07-22 17:02:11 Fri Jul 22 17:02:11 UTC 2022 2022-07-22 17:02:11 Fri Jul 22 17:02:11 UTC 2022 2022-07-22 17:02:12 Fri Jul 22 17:02:12 UTC 2022 2022-07-22 17:02:12 Fri Jul 22 17:02:12 UTC 2022 2022-07-22 17:02:12 Fri Jul 22 17:02:12 UTC 2022 2022-07-22 17:02:12 Fri Jul 22 17:02:12 UTC 2022 2022-07-22 17:02:13 Fri Jul 22 17:02:13 UTC 2022

itlevel3 avatar Jul 22 '22 17:07 itlevel3