Bekijk de volledige versie : Sytem Time back to 1969...
I have a problem my time goes wrong from time to time-
Wed Dec 31 19:05:31 EST 1969
If I remove syslog.log and reboot
rm /tmp/syslog.log
my time goes back to normal. Looks like I can ping NTP server time.nist.gov...
I was following this http://wl500g.info/showthread.php?t=14885
and it did not help...
Any idea?
Thank you!
I have a problem my time goes wrong from time to time-
Wed Dec 31 19:05:31 EST 1969
If I remove syslog.log and reboot
rm /tmp/syslog.log
my time goes back to normal. Looks like I can ping NTP server time.nist.gov...
I was following this http://wl500g.info/showthread.php?t=14885
and it did not help...
Any idea?
Thank you!
=======
The referenced thread.
So what are your settings for local time, time zone and GMT ?
Darius
avberk avberk is offline
Senior Member
Join Date: Aug 2005
Posts: 255
Seems that if you persist on finding a solution you will find one
Hereby the steps you need to take:
-Open /opt/etc/asterisk/cdr.conf and change 'usegmtime'
to 'no'. e.g.:
[csv]
usegmtime=no ; log date/time in GMT. Default is "no"
loguniqueid=no ; log uniqueid. Default is "no"
loguserfield=no ; log user field. Default is "no"
-ipkg update
-ipkg install tz
-Goto the /opt/share/zoneinfo folder and find
your timezone location. Copy this location to the
folder /etc/localtime. e.g.:
cp /opt/share/zoneinfo/Europe/Amsterdam /etc/localtime
-Open '/usr/local/.files' and add this line:
/etc/localtime
-To make the change permanent, save it to flash:
flashfs save && flashfs commit && flashfs enable
-Restart Asterisk.
See also this link for some background info:
http://www.nslu2-linux.org/wiki/Unslung/TimeZoneUpdate
Reply With Quote
This did not help me!!!
http://wl500g.info/showthread.php?t=14885
This did not help me!!!
http://wl500g.info/showthread.php?t=14885
Ok.
Just let me know your settings for GMT and time zone.
I am running Koppel/Olegs and don't have the asterisk directory created and cdr.conf file .
==
-Open /opt/etc/asterisk/cdr.conf and change 'usegmtime'
to 'no'. e.g.:
==\
So just tell me how did you create and edit it .
Darius
Thanks, I did change all options to "no"
[csv]
usegmtime=no ; log date/time in GMT. Default is "no"
loguniqueid=no ; log uniqueid. Default is "no"
loguserfield=no ; log user field. Default is "no"
and still have this time wrong-
Thu Jan 1 12:55:18 EST 1970
Any idea?
Thanks, I did change all options to "no"
[csv]
usegmtime=no ; log date/time in GMT. Default is "no"
loguniqueid=no ; log uniqueid. Default is "no"
loguserfield=no ; log user field. Default is "no"
and still have this time wrong-
Thu Jan 1 12:55:18 EST 1970
Any idea?
Hi,
what is your settings for NTP in GUI ?
IP Config - Miscellaneous
NTP Server NTP Link
NTP synchronization interval (hours):
In my case system time synchronization is done via remote NTP server every 2 hours.
So when my router is off-line I don't get time synchronization either.
It was strange to me to detect no system time backup facility present on a router.
Darius
Here are my settings:
Enable UPnP? - NO
Time Zone: (GMT-05.00) Eastern Time
NTP Server: time.nist.gov
NTP synchronization interval (hours): 2
this is what i have got: rdate: timeout for time.nist.gov
$ ipkg install rdate
Installing rdate (1.4-2) to /opt/...
Downloading http://ipkg.nslu2-linux.org/feeds/optware/oleg/cross/stable/rdate_1.4-2_mipsel.ipk
Configuring rdate
Successfully terminated.
$ rdate time.nist.gov
rdate: timeout for time.nist.gov
$ ping time.nist.gov
PING time.nist.gov (192.43.244.18): 56 data bytes
84 bytes from 192.43.244.18: icmp_seq=0 ttl=51 time=48.9 ms
84 bytes from 192.43.244.18: icmp_seq=1 ttl=51 time=50.1 ms
But I have no problems with
rdate time-nw.nist.gov
rdate: [time-nw.nist.gov] Tue Jan 13 14:38:53 2009
I will change my NTP Server to time-nw.nist.gov and see what will be happened.
I just fixed my original problem!
Now I run this with cron every hour and it fixes my time!
rdate -s time-nw.nist.gov
Here are my settings:
Enable UPnP? - NO
Time Zone: (GMT-05.00) Eastern Time
NTP Server: time.nist.gov
NTP synchronization interval (hours): 2
this is what i have got: rdate: timeout for time.nist.gov
$ ipkg install rdate
Installing rdate (1.4-2) to /opt/...
Downloading http://ipkg.nslu2-linux.org/feeds/optware/oleg/cross/stable/rdate_1.4-2_mipsel.ipk
Configuring rdate
Successfully terminated.
$ rdate time.nist.gov
rdate: timeout for time.nist.gov
$ ping time.nist.gov
PING time.nist.gov (192.43.244.18): 56 data bytes
84 bytes from 192.43.244.18: icmp_seq=0 ttl=51 time=48.9 ms
84 bytes from 192.43.244.18: icmp_seq=1 ttl=51 time=50.1 ms
But I have no problems with
rdate time-nw.nist.gov
rdate: [time-nw.nist.gov] Tue Jan 13 14:38:53 2009
I will change my NTP Server to time-nw.nist.gov and see what will be happened.
I just fixed my original problem!
Now I run this with cron every hour and it fixes my time!
rdate -s time-nw.nist.gov
My congratulations.
The issue is, some hop servers filter and restrict access to destination servers if your IP is rated poor.
More than 1,5 bln. IP addresses are already subject to rating procedure -
rated good, neutral or poor.
If dynamic or static IP assigned to your router by your ISP is rated poor,
there is a great chance to have your packets dropped.
IP ratings is not blacklisting.
Operation started in 2008 and was examined and tested by me for months.
Free mail like Yahoo is subject to filtering .
One day your mail gets delivered, another day hop servers don't like your IP.
And those in charge of the operation suggest you to contact your mail server administrator to reset your IP rating to neutral.
The issue is IP is assigned by ISP but Yahoo.
Darius