Page 1 of 1

Another Time synchronization Error post

PostPosted: Wed Sep 16, 2020 3:41 pm
by kjburto
Hello All,

So I have a couple vici servers for different clients and 1 of them keeps getting a time sync error once every 2 weeks or so. The only thing that sticks out to me is the server time is slightly off from the PHP and DB Time (see Below). When I do a reboot everything seems fine for another week or two then it happens again. Can the cmos battery cause this type of time issue? Any suggestions?

SERVER - DESCRIPTION IP ACT LOAD CHAN AGNT DISK TIME VER
NewGen1 Server NewGen1 192.168.1.9 Y / Y / Y 61 - 2% 16 5 16% 2020-09-16 15:34:28 2975
PHP Time 2020-09-16 15:34:29
DB Time 2020-09-16 15:34:29


All screens are running from what I can tell. I have been searching online and in here for something and cannot find any solutions to this issue. Ive had these errors in the past related to ip address changes but this server hasn't had any changes of that sort and none of my other servers are doing anything similar.

NewGen1:~ # screen -ls
There are screens on:
4456.ASTemail (Detached)
4453.ASTVDadFILL (Detached)
4450.ASTfastlog (Detached)
4447.ASTVDadapt (Detached)
4444.ASTVDremote (Detached)
4441.ASTVDauto (Detached)
4438.ASTlisten (Detached)
4435.ASTsend (Detached)
4432.ASTupdate (Detached)
3643.asterisk (Detached)
10 Sockets in /var/run/screens/S-root.


VERSION: 2.14-671a BUILD: 180430-1834
Version: 2.14b0.5
SVN Version: 2975
DB Schema Version: 1543

Re: Another Time synchronization Error post

PostPosted: Wed Sep 16, 2020 4:09 pm
by carpenox
looks like everything is running right, perhaps the db crashes or something every 2 weeks? are you optimizing the db each night?

Re: Another Time synchronization Error post

PostPosted: Fri Sep 18, 2020 2:27 pm
by kjburto
carpenox wrote:looks like everything is running right, perhaps the db crashes or something every 2 weeks? are you optimizing the db each night?


Not that I am aware of. Is there a script I can add to do that?

Re: Another Time synchronization Error post

PostPosted: Fri Sep 18, 2020 5:28 pm
by carpenox
mysqlcheck -p --auto-repair --all-databases

Re: Another Time synchronization Error post

PostPosted: Tue Sep 22, 2020 8:20 am
by kjburto
Thank you

Is this something you should auto run consistently? If so is there a script I can to do so?

Here is one thing that came up in that scan and I'm not sure what it means exactly.


asterisk.vicidial_live_agents OK
asterisk.vicidial_live_chats OK
asterisk.vicidial_live_inbound_agents OK
asterisk.vicidial_log OK
asterisk.vicidial_log_archive OK
asterisk.vicidial_log_extended
warning : Table is marked as crashed and last repair failed
warning : 1 client is using or hasn't closed the table properly
warning : Size of indexfile is: 234990592 Should be: 1024
error : Keyblock size at page -1 is not correct. Block length: 254 key length: 2
Error : Index for table './asterisk/vicidial_log_extended.MYI' is corrupt; try to repair it
error : Corrupt
asterisk.vicidial_log_extended_archive OK



and then the final results:

Repairing tables
asterisk.vicidial_log_extended
info : Wrong bytesec: 0- 0- 0 at 205419488; Skipped
warning : Number of rows changed from 2654216 to 2946554
status : OK