com.apple.time going bonkers

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

com.apple.time going bonkers

The Mac OS X Server Mailing List mailing list
Ever since Apple's automated/forced NTP update, my iMac is dumping these messages into the log (by the millions):

Jan 23 08:59:59 com.apple.time[171]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
Jan 23 08:59:59 com.apple.time[353]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
Jan 23 08:59:59 com.apple.time[171]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
Jan 23 08:59:59 com.apple.time[353]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
Jan 23 08:59:59 com.apple.time[171]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
Jan 23 08:59:59 com.apple.time[353]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
Jan 23 08:59:59 --- last message repeated 17061 times ---
Jan 23 08:59:59 com.apple.time[171]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
Jan 23 08:59:59 com.apple.time[353]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
Jan 23 08:59:59 com.apple.time[171]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
Jan 23 08:59:59 com.apple.time[353]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
Jan 23 08:59:59 com.apple.time[171]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
Jan 23 08:59:59 com.apple.time[353]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
Jan 23 08:59:59 com.apple.time[171]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).

It seems to have a cow transitioning to a new hour. Anybody else seen this?
-Carl



 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list      ([hidden email])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/macos-x-server/lists%2Bs10970n2h62%40n7.nabble.com

This email sent to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: com.apple.time going bonkers

The Mac OS X Server Mailing List mailing list
>Ever since Apple's automated/forced NTP update, my iMac is dumping these messages into the log (by the >millions):

>Jan 23 08:59:59 com.apple.time[171]: Interval maximum value is 946100000 seconds (specified value: >9223372036854775807).
>Jan 23 08:59:59 com.apple.time[353]: Interval maximum value is 946100000 seconds (specified value: >9223372036854775807).


>It seems to have a cow transitioning to a new hour. Anybody else seen this?
>-Carl

You don't by chance have a period at the end of your NTP server name do you? I had heard this was a problem in some versions of the OS. I'm running 10.10.1, have a period at the end of my NTP server, and do not see these log entires.

tom

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list      ([hidden email])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/macos-x-server/lists%2Bs10970n2h62%40n7.nabble.com

This email sent to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: com.apple.time going bonkers

The Mac OS X Server Mailing List mailing list
On Jan 23, 2015, at 6:40 PM, OS X Server Mail List <[hidden email]> wrote:

>> Ever since Apple's automated/forced NTP update, my iMac is dumping these messages into the log (by the >millions):
>
>> Jan 23 08:59:59 com.apple.time[171]: Interval maximum value is 946100000 seconds (specified value: >9223372036854775807).
>> Jan 23 08:59:59 com.apple.time[353]: Interval maximum value is 946100000 seconds (specified value: >9223372036854775807).
>
>> It seems to have a cow transitioning to a new hour. Anybody else seen this?
>> -Carl
>
> You don't by chance have a period at the end of your NTP server name do you? I had heard this was a problem in some versions of the OS. I'm running 10.10.1, have a period at the end of my NTP server, and do not see these log entires.
>
> tom
> _______________________________________________

Thanks, Tom, for the suggestion. There is in fact a period at the end of the NTP server specification. It’s always been there, as we’ve never edited the conf file. Is there any potential harm in removing it?

server time.apple.com.

-Carl



 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list      ([hidden email])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/macos-x-server/lists%2Bs10970n2h62%40n7.nabble.com

This email sent to [hidden email]
Reply | Threaded
Open this post in threaded view
|

RE: com.apple.time going bonkers

The Mac OS X Server Mailing List mailing list
>>> Ever since Apple's automated/forced NTP update, my iMac is dumping these messages into the log (by the >millions):

>>>
>>> Jan 23 08:59:59 com.apple.time[171]: Interval maximum value is 946100000 seconds (specified value: >9223372036854775807).
>>> Jan 23 08:59:59 com.apple.time[353]: Interval maximum value is 946100000 seconds (specified value: >9223372036854775807).
>>>
>>> It seems to have a cow transitioning to a new hour. Anybody else seen this?
>>> -Carl
>
>> You don't by chance have a period at the end of your NTP server name do you? I had heard this was a problem in some versions of the OS. I'm running 10.10.1, have a period at the end of my NTP server, and do not see these log entires.
>>
>> tom
> _______________________________________________

>Thanks, Tom, for the suggestion. There is in fact a period at the end of the NTP server specification. It’s always been >?>there, as we’ve never edited the conf file. Is there any potential harm in removing it?

>server time.apple.com.

Even though the period is normal typically writing a FQDN without it is common. No harm in removing it unless the OS is explicitly looking for it (which in this case I'm not sure if it is or not). You should see it written that way in the date and time prefs pane too. I'd take it out and see if the log errors go away and all services still work. If yes then leave it off if not put it back and deal with the errors for now. As long as NTP is functioning normally you could always have those errors not logged to clear up your logs. After you make the change check both the date and times prefs pane and ntp.conf to make sure they both get updated.

tom


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list      ([hidden email])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/macos-x-server/lists%2Bs10970n2h62%40n7.nabble.com

This email sent to [hidden email]
Reply | Threaded
Open this post in threaded view
|

RE: com.apple.time going bonkers

The Mac OS X Server Mailing List mailing list
>Even though the period is normal typically writing a FQDN without it
>is common. No harm in removing it unless the OS is explicitly
>looking for it (which in this case I'm not sure if it is or not).
>You should see it written that way in the date and time prefs pane
>too. I'd take it out and see if the log errors go away and all
>services still work. If yes then leave it off if not put it back and
>deal with the errors for now. As long as NTP is functioning normally
>you could always have those errors not logged to clear up your logs.
>After you make the change check both the date and times prefs pane
>and ntp.conf to make sure they both get updated.

Dredging my memory, I seem to recall that the final dot was to tell
the parser that this was the end of the name. Without it, it could
have been just a device name and a domain spec could be added after
by the parser.

For example, if a default domain was specified in a mail program, eg,
acme.com, then you could send a message to "fred@sun"

The parser would recognise this was not  a full name, and would add
the default domain giving "[hidden email]."

If the message had been sent to "fred@sun." then the parser would not
have added the domain and would have tried to deliver it directly to
"fred@sun."

And of course "sun" could have dots in it like "[hidden email]"

So for the case above, it would have been delivered  to "[hidden email]"

To make sure it went to the correct address, you should use "[hidden email]."

We manage to survive mainly because there is rarely a default domain
specified in most things, so there is nothing to add to the end.

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list      ([hidden email])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/macos-x-server/lists%2Bs10970n2h62%40n7.nabble.com

This email sent to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: com.apple.time going bonkers

The Mac OS X Server Mailing List mailing list
>>Even though the period is normal typically writing a FQDN without it

>>is common. No harm in removing it unless the OS is explicitly
>>looking for it (which in this case I'm not sure if it is or not).
>>You should see it written that way in the date and time prefs pane
>>too. I'd take it out and see if the log errors go away and all
>>services still work. If yes then leave it off if not put it back and
>>deal with the errors for now. As long as NTP is functioning normally
>>you could always have those errors not logged to clear up your logs.
>>After you make the change check both the date and times prefs pane
>>and ntp.conf to make sure they both get updated.

>Dredging my memory, I seem to recall that the final dot was to tell
>the parser that this was the end of the name. Without it, it could
>have been just a device name and a domain spec could be added after
>by the parser.

>For example, if a default domain was specified in a mail program, eg,
>acme.com, then you could send a message to "fred@sun"

>The parser would recognise this was not  a full name, and would add
>the default domain giving "[hidden email]."

>If the message had been sent to "fred@sun." then the parser would not
>have added the domain and would have tried to deliver it directly to
>"fred@sun."

>And of course "sun" could have dots in it like "[hidden email]"

>So for the case above, it would have been delivered  to "[hidden email]"

>To make sure it went to the correct address, you should use "[hidden email]."

>We manage to survive mainly because there is rarely a default domain
>specified in most things, so there is nothing to add to the end.

Yes the final period is actually needed to specify the end of the domain. Its used mostly when defining domains in DNS, I rarely see it used when specifying FQDN as configuration parameters but the default domain is a good example.

tom

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list      ([hidden email])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/macos-x-server/trice%40greatneck.k12.ny.us

This email sent to [hidden email]

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list      ([hidden email])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/macos-x-server/lists%2Bs10970n2h62%40n7.nabble.com

This email sent to [hidden email]