If memory serves me right, as soon as FreeSWITCH starts it gets the current time of the host and then keeps track of it independently from that point on. Having a date set way back to 1999 seems like the server has a malfunctioning RTC battery.

If you really want to fix this problem temporarily, you might want to run fsctl sync_clock to have FreeSWITCH resync the clock back to the correct time. Of course you can create a bunch of init scripts and have it to grab the correct time from a NTP server and then have FreeSWITCH to start after that.

From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Philippe Le Toquin
Sent: Sunday, March 10, 2013 5:26 PM
To: FreeSWITCH Users Help
Subject: [Freeswitch-users] Freeswitch is showing Incorrect time

Hello,

Not sure why but recently I noticed that Freeswitch is logging data with the wrong date

I noticed it first in the freeswitch log but I can see it also in the log that are display in the cli itself

the computer itself is ok

~# date
Sun Mar 10 20:13:05 EDT 2013

but :

freeswitch@internal> version
FreeSWITCH Version 1.3.13b+git~20130108T204816Z~8e892abdef (git 8e892ab 2013-01-08 20:48:16Z)

freeswitch@internal> strftime
1999-12-31 19:07:40

from freeswtich.log
1999-12-31 19:14:09.460477 [WARNING] sofia_reg.c:1506 SIP auth challenge (REGISTER) on sofia profile 'internal' for [1000@xx.xx.xx.xx] from ip xx.xx.xx.xx


This is right after a reboot since I thought a reboot would may be fix it

where does FS takes its time from?

The last time it was correctly logged was on the 9th of March ! We had a power cut that caused the system to reboot

thanks

/Philippe