From: "Massimo S." Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTP id 11992272 for ecs-isp@2rosenthals.com; Mon, 20 Jan 2025 04:09:00 -0500 Received: from [192.168.200.201] (port=57015 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.97.1) (envelope-from ) id 1tZnm6-000000004Bp-1jde for ecs-isp@2rosenthals.com; Mon, 20 Jan 2025 04:08:53 -0500 Received: from mail2.quasarbbs.net ([80.86.52.115]:10039) by mail2.2rosenthals.com with esmtp (Exim 4.97.1) (envelope-from ) id 1tZnlu-000000003wS-105D for ecs-isp@2rosenthals.com; Mon, 20 Jan 2025 04:08:38 -0500 X-SASI-Hits: BODY_SIZE_3000_3999 0.000000, BODY_SIZE_5000_LESS 0.000000, BODY_SIZE_7000_LESS 0.000000, CTE_7BIT 0.000000, HTML_00_01 0.050000, HTML_00_10 0.050000, IN_REP_TO 0.000000, LEGITIMATE_SIGNS 0.000000, MSGID_SAMEAS_FROM_HEX_844412 0.100000, MSG_THREAD 0.000000, NO_CTA_URI_FOUND 0.000000, NO_URI_HTTPS 0.000000, REFERENCES 0.000000, REPLYTO_SAMEAS_FROM 0.000000, SENDER_NO_AUTH 0.000000, SUSP_DH_NEG 0.000000, TO_IN_SUBJECT 0.500000, USER_AGENT 0.000000, __ANY_URI 0.000000, __BANNER_TRUSTED_SENDER 0.000000, __BODY_NO_MAILTO 0.000000, __BODY_VOICEMAIL 0.000000, __BOUNCE_CHALLENGE_SUBJ 0.000000, __BOUNCE_NDR_SUBJ_EXEMPT 0.000000, __CT 0.000000, __CTE 0.000000, __CT_TEXT_PLAIN 0.000000, __DQ_NEG_DOMAIN 0.000000, __DQ_NEG_HEUR 0.000000, __DQ_NEG_IP 0.000000, __FORWARDED_MSG 0.000000, __FROM_DOMAIN_NOT_IN_BODY 0.000000, __FROM_NAME_NOT_IN_ADDR 0.000000, __FROM_NAME_NOT_IN_BODY 0.000000, __FUR_HEADER 0.000000, __HAS_FROM 0.000000, __HAS_MSGID 0.000000, __HAS_REFERENCES 0.000000, __HAS_REPLYTO 0.000000, __HEADER_ORDER_FROM 0.000000, __IN_REP_TO 0.000000, __IOC_PHRASE 0.000000, __MAIL_CHAIN 0.000000, __MIME_BOUND_CHARSET 0.000000, __MIME_TEXT_ONLY 0.000000, __MIME_TEXT_P 0.000000, __MIME_TEXT_P1 0.000000, __MIME_VERSION 0.000000, __MOZILLA_USER_AGENT 0.000000, __MSGID_HEX_844412 0.000000, __NO_HTML_TAG_RAW 0.000000, __PHISH_SPEAR_SUBJ_ALERT 0.000000, __REFERENCES 0.000000, __REPLYTO_SAMEAS_FROM_ACC 0.000000, __REPLYTO_SAMEAS_FROM_ADDY 0.000000, __REPLYTO_SAMEAS_FROM_DOMAIN 0.000000, __SANE_MSGID 0.000000, __SCAN_D_NEG 0.000000, __SCAN_D_NEG2 0.000000, __SCAN_D_NEG_HEUR 0.000000, __SCAN_D_NEG_HEUR2 0.000000, __SUBJ_ALPHA_END 0.000000, __SUBJ_ALPHA_NEGATE 0.000000, __SUBJ_REPLY 0.000000, __TO_IN_SUBJECT 0.000000, __TO_MALFORMED_2 0.000000, __TO_NAME 0.000000, __TO_NAME_DIFF_FROM_ACC 0.000000, __TO_REAL_NAMES 0.000000, __URI_MAILTO 0.000000, __URI_NO_WWW 0.000000, __URI_NS 0.000000, __USER_AGENT 0.000000 X-SASI-Probability: 10% X-SASI-RCODE: 200 X-SASI-Version: Antispam-Engine: 5.1.4, AntispamData: 2025.1.20.82446 X-SASI-Hits: BODY_SIZE_3000_3999 0.000000, BODY_SIZE_5000_LESS 0.000000, BODY_SIZE_7000_LESS 0.000000, CTE_7BIT 0.000000, HTML_00_01 0.050000, HTML_00_10 0.050000, IN_REP_TO 0.000000, LEGITIMATE_SIGNS 0.000000, MSGID_SAMEAS_FROM_HEX_844412 0.100000, MSG_THREAD 0.000000, NO_CTA_URI_FOUND 0.000000, NO_URI_HTTPS 0.000000, REFERENCES 0.000000, REPLYTO_SAMEAS_FROM 0.000000, SUSP_DH_NEG 0.000000, TO_IN_SUBJECT 0.500000, USER_AGENT 0.000000, __ANY_URI 0.000000, __AUTH_RES_PASS 0.000000, __BANNER_TRUSTED_SENDER 0.000000, __BODY_NO_MAILTO 0.000000, __BODY_VOICEMAIL 0.000000, __BOUNCE_CHALLENGE_SUBJ 0.000000, __BOUNCE_NDR_SUBJ_EXEMPT 0.000000, __CT 0.000000, __CTE 0.000000, __CT_TEXT_PLAIN 0.000000, __DQ_NEG_DOMAIN 0.000000, __DQ_NEG_HEUR 0.000000, __DQ_NEG_IP 0.000000, __FORWARDED_MSG 0.000000, __FROM_DOMAIN_NOT_IN_BODY 0.000000, __FROM_NAME_NOT_IN_ADDR 0.000000, __FROM_NAME_NOT_IN_BODY 0.000000, __FUR_HEADER 0.000000, __HAS_FROM 0.000000, __HAS_MSGID 0.000000, __HAS_REFERENCES 0.000000, __HAS_REPLYTO 0.000000, __HEADER_ORDER_FROM 0.000000, __IN_REP_TO 0.000000, __IOC_PHRASE 0.000000, __MAIL_CHAIN 0.000000, __MIME_BOUND_CHARSET 0.000000, __MIME_TEXT_ONLY 0.000000, __MIME_TEXT_P 0.000000, __MIME_TEXT_P1 0.000000, __MIME_VERSION 0.000000, __MOZILLA_USER_AGENT 0.000000, __MSGID_HEX_844412 0.000000, __NO_HTML_TAG_RAW 0.000000, __PHISH_SPEAR_SUBJ_ALERT 0.000000, __REFERENCES 0.000000, __REPLYTO_SAMEAS_FROM_ACC 0.000000, __REPLYTO_SAMEAS_FROM_ADDY 0.000000, __REPLYTO_SAMEAS_FROM_DOMAIN 0.000000, __SANE_MSGID 0.000000, __SCAN_D_NEG 0.000000, __SCAN_D_NEG2 0.000000, __SCAN_D_NEG_HEUR 0.000000, __SCAN_D_NEG_HEUR2 0.000000, __SUBJ_ALPHA_END 0.000000, __SUBJ_ALPHA_NEGATE 0.000000, __SUBJ_REPLY 0.000000, __TO_IN_SUBJECT 0.000000, __TO_MALFORMED_2 0.000000, __TO_NAME 0.000000, __TO_NAME_DIFF_FROM_ACC 0.000000, __TO_REAL_NAMES 0.000000, __URI_MAILTO 0.000000, __URI_NO_WWW 0.000000, __URI_NS 0.000000, __USER_AGENT 0.000000 X-SASI-Probability: 10% X-SASI-RCODE: 200 X-SASI-Version: Antispam-Engine: 5.1.4, AntispamData: 2025.1.20.82446 Received: from [192.168.10.199] (dtp [192.168.10.199]) by srv2 (Weasel v2.9-0001 ) for ; Mon, 20 Jan 2025 10:08:45 -0000 Reply-To: ml@ecomstation.it Subject: Re: [eCS-ISP] ntp day issue To: eCS ISP Mailing List References: Organization: Massimo S. Message-ID: <0bb35197-ea20-d021-6243-1547fe553fe8@ecomstation.it> Date: Mon, 20 Jan 2025 10:08:33 +0100 User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; it-IT; rv:1.7.13) Gecko/20060424 Thunderbird/1.0.8 Mnenhy/0.7.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Language: it-IT Content-Transfer-Encoding: 7bit Il 20/01/2025 07:26, Steven Levine ha scritto: > In , on 01/18/25 > at 11:09 AM, "Massimo S." said: > > Hi Massimo, > >> this tool can run scheduled and not allways in memory? > > Yes, it can be run in one shot mode. See Section IV of os2_ntpd.man. i've seen, but it do not document in details anyway os2_ntpd 193.204.114.232 2 2 ntp server RFC 5905, hour and date is right but how can i be sure? how to make it to save a log? if i want to run it with more IP (INRIM has 3 IP/servers) should i run also os2_ntpd 193.204.114.233 2 2 or is there another way to give it a list? (if i use cfg_data there is no instructions to run it scheduled, or "one shot") > That said, os2_ntpd is an NTP client which is designed to work best > running as a detached daemon. i will run scheduled some times per day thanks massimo >> i've this issue since years >> even when the MTA1 was running on bare metal > >> i run the time sync at each reboot, sometimes it show the date issue i've >> never understand why > > Most of the time sync protocols use UDP, so random, intermittent errors > are to be expected and the time sync applications are expected to deal > with this. > > Here is the tail of the current log > > 2025/01/19 17:14:36: *** Timed Out Waiting on Reply from Server > 1.pool.ntp.org *** 2025/01/19 17:14:38: Poll interval is 16 seconds > 2025/01/19 17:14:51: Poll interval changed to 32 seconds > 2025/01/19 17:16:27: *** Timed Out Waiting on Reply from Server > 1.pool.ntp.org *** 2025/01/19 17:18:02: *** Timed Out Waiting on Reply > from Server 1.us.pool.ntp.org *** 2025/01/19 17:18:35: Poll interval > changed to 64 seconds 2025/01/19 17:19:41: Poll interval changed to 128 > seconds > 2025/01/19 17:21:46: *** Timed Out Waiting on Reply from Server > 2.us.pool.ntp.org *** 2025/01/19 17:23:55: Poll interval changed to 256 > seconds > 2025/01/19 17:28:10: *** Timed Out Waiting on Reply from Server > 0.us.pool.ntp.org *** 2025/01/19 17:53:48: *** Timed Out Waiting on Reply > from Server 2.us.pool.ntp.org *** 2025/01/19 18:36:27: *** Timed Out > Waiting on Reply from Server 1.pool.ntp.org *** 2025/01/19 19:23:23: *** > Timed Out Waiting on Reply from Server 1.us.pool.ntp.org *** 2025/01/19 > 20:23:07: *** Timed Out Waiting on Reply from Server pool.ntp.org *** > 2025/01/19 20:48:43: *** Timed Out Waiting on Reply from Server > 2.us.pool.ntp.org *** 2025/01/19 20:48:44: *** Timed Out Waiting on Reply > from Server 1.pool.ntp.org *** 2025/01/19 20:48:45: *** Timed Out Waiting > on Reply from Server 2.pool.ntp.org *** 2025/01/19 20:52:59: *** Timed Out > Waiting on Reply from Server 2.us.pool.ntp.org *** 2025/01/19 21:01:31: > *** Timed Out Waiting on Reply from Server 0.pool.ntp.org *** 2025/01/19 > 21:22:51: *** Timed Out Waiting on Reply from Server 2.us.pool.ntp.org *** > 2025/01/19 21:39:54: *** Timed Out Waiting on Reply from Server > us.pool.ntp.org *** 2025/01/19 21:52:43: *** Timed Out Waiting on Reply > from Server 2.us.pool.ntp.org *** 2025/01/19 22:14:17: Can not get host > address for "us.pool.ntp.org" 2025/01/19 22:14:34: Can not get host > address for "0.us.pool.ntp.org" 2025/01/19 22:14:51: Can not get host > address for "1.us.pool.ntp.org" 2025/01/19 22:35:24: *** Timed Out Waiting > on Reply from Server 2.pool.ntp.org *** > > Any of the above errors might cause a naive application to set the time > incorrectly. > > Os2_ntpd and the NTP v3 protocol it implements is designed in such a way > that this will not occur. If you are sufficiently curious as to why take > a look at RFC 1305. > > Steven >