Page 1 of 1

Why ALL get Log off at 1 am IST ?

PostPosted: Mon Feb 22, 2010 3:03 pm
by gmcust3
Why ALL get Log off at 1:05 am IST ?

What settings need to check to trouble shoot this ?



[root@vici ~]# crontab -l
### recording mixing/compressing/ftping scripts
0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astgu iclient/AST_CRON_audio_1_move_mix.pl
#0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astg uiclient/AST_CRON_audio_1_move_VDonly.pl
#1,4,7,10,13,16,19,22,25,28,31,34,37,40,43,46,49,52,55,58 * * * * /usr/share/ast guiclient/AST_CRON_audio_2_compress.pl --GSM
#2,5,8,11,14,17,20,23,26,29,32,35,38,41,44,47,50,53,56,59 * * * * /usr/share/ast guiclient/AST_CRON_audio_3_ftp.pl --GSM

### keepalive script for astguiclient processes
* * * * * /usr/share/astguiclient/ADMIN_keepalive_ALL.pl

### kill Hangup script for Asterisk updaters
* * * * * /usr/share/astguiclient/AST_manager_kill_hung_congested.pl

### updater for voicemail
* * * * * /usr/share/astguiclient/AST_vm_update.pl

### updater for conference validator
* * * * * /usr/share/astguiclient/AST_conf_update.pl

### flush queue DB table every hour for entries older than 1 hour
11 * * * * /usr/share/astguiclient/AST_flush_DBqueue.pl -q

### fix the vicidial_agent_log once every hour
33 * * * * /usr/share/astguiclient/AST_cleanup_agent_log.pl

### updater for VICIDIAL hopper
* * * * * /usr/share/astguiclient/AST_VDhopper.pl -q

### adjust the GMT offset for the leads in the vicidial_list table
1 1 * * * /usr/share/astguiclient/ADMIN_adjust_GMTnow_on_leads.pl --debug

### reset several temporary-info tables in the database
2 1 * * * /usr/share/astguiclient/AST_reset_mysql_vars.pl

### optimize the database tables within the asterisk database
3 1 * * * /usr/share/astguiclient/AST_DB_optimize.pl

## adjust time on the server with ntp
30 * * * * ntpdate -u ntp.myfloridacity.us 2>/dev/null 1>&2

### VICIDIAL agent time log weekly and daily summary report generation
2 0 * * 0 /usr/share/astguiclient/AST_agent_week.pl
22 0 * * * /usr/share/astguiclient/AST_agent_day.pl

### VICIDIAL campaign export scripts (OPTIONAL)
#32 0 * * * /usr/share/astguiclient/AST_VDsales_export.pl
#42 0 * * * /usr/share/astguiclient/AST_sourceID_summary_export.pl

### remove old recordings more than 7 days old
#24 0 * * * /usr/bin/find /var/spool/asterisk/monitorDONE -maxdepth 2 -type f -m time +7 -print | xargs rm -f

### remove old vicidial logs and asterisk logs more than 2 days old
28 0 * * * /usr/bin/find /var/log/astguiclient -maxdepth 1 -type f -mtime +2 -pr int | xargs rm -f
29 0 * * * /usr/bin/find /var/log/asterisk -maxdepth 3 -type f -mtime +2 -print | xargs rm -f
30 0 * * * /usr/bin/find / -maxdepth 1 -name "screenlog.0*" -mtime +4 -print | x args rm -f
51 5 * * * /etc/webmin/cron/tempdelete.pl
[root@vici ~]#





Anything running at 01:05 Am IST ??

[/quote]

[root@vici ~]# date
Tue Feb 23 01:05:20 IST 2010
[root@vici ~]#

[quote]

Above date should be EST ?

PostPosted: Mon Feb 22, 2010 5:16 pm
by gmcust3
[root@vici ~]# date ; date -u ; /sbin/hwclock --show
Thu Feb 25 02:00:07 IST 2010
Wed Feb 24 20:30:07 UTC 2010
Thu 25 Feb 2010 02:00:07 AM IST -0.112990 seconds
[root@vici ~]#


It happens at 1 am as per System Time.

Please help me.

PostPosted: Wed Feb 24, 2010 3:23 pm
by gmcust3
One of below is creating Issue ??

### adjust the GMT offset for the leads in the vicidial_list table
1 1 * * * /usr/share/astguiclient/ADMIN_adjust_GMTnow_on_leads.pl --debug

### reset several temporary-info tables in the database
2 1 * * * /usr/share/astguiclient/AST_reset_mysql_vars.pl

### optimize the database tables within the asterisk database
3 1 * * * /usr/share/astguiclient/AST_DB_optimize.pl


I am seriously looking for some help and can I comment out above 3 lines in Cron ?

Will that affect my server severely ?

PostPosted: Thu Feb 25, 2010 12:03 pm
by gmcust3
If My local time zone is IST, Do I need below line in cron root ? :

## adjust time on the server with ntp
30 * * * * ntpdate -u ntp.myfloridacity.us 2>/dev/null 1>&2

PostPosted: Thu Feb 25, 2010 2:38 pm
by gmcust3
It happened again :

[root@vici ~]# date ; date -u ; /sbin/hwclock --show
Fri Feb 26 01:06:23 IST 2010
Thu Feb 25 19:36:23 UTC 2010
Fri 26 Feb 2010 01:06:24 AM IST -0.017215 seconds
[root@vici ~]#

and then it gives me TIME SYNC ERROR.

After I reboot , all ok BUT terrible VOICE BREAK UP.

Can anyone throw me some light why it can happen ?

PostPosted: Thu Feb 25, 2010 7:01 pm
by gmcust3
Sorry to bump the topic, so quickly, but I am loosing some good number of sales .

I spoke to CentOS forum admins and here iS what they say about it :

https://www.centos.org/modules/newbb/vi ... 9&forum=37

PostPosted: Fri Feb 26, 2010 3:07 pm
by gmcust3
I changed below line :

### adjust the GMT offset for the leads in the vicidial_list table
1 1 * * * /usr/share/astguiclient/ADMIN_adjust_GMTnow_on_leads.pl --debug

### reset several temporary-info tables in the database
2 1 * * * /usr/share/astguiclient/AST_reset_mysql_vars.pl

### optimize the database tables within the asterisk database
3 1 * * * /usr/share/astguiclient/AST_DB_optimize.pl


TO

### adjust the GMT offset for the leads in the vicidial_list table
1 * * * /usr/share/astguiclient/ADMIN_adjust_GMTnow_on_leads.pl --debug

### reset several temporary-info tables in the database
2 9 * * * /usr/share/astguiclient/AST_reset_mysql_vars.pl

### optimize the database tables within the asterisk database
3 9 * * * /usr/share/astguiclient/AST_DB_optimize.pl


And problem solved.

No idea why it was given at 1 ?