vicidial.org

Hello everyone.

Dahdi is installed on the server but I'm getting a "There is a time synchronization problem with your system, please tell your system administrator" error.

Looks like this is because there is no dahdi_dummy module. This is the output of "lsmod | grep dahd" command:
dahdi 225082 0
crc_ccitt 1717 1 dahdi

modprobe dahdi_dummy does not help.

Has anyone faced such problem?

HI,

Login into Admin and go on Report page. Below page click on "+" and see which time showing difference. All time(PHP, Mysql and Server) should be same. From report you will get idea that which one is not working or difference.

You can check below things.

1. PHP time in php.ini file
2. Run "

Code: Select all

tzselect

" command and select your time zone.
3.

Code: Select all

ntpd

installed and running on your server. If its not installed then run

Code: Select all

yum install ntp*

and then

Code: Select all

service ntpd start

.

udy786 wrote:Login into Admin and go on Report page. Below page click on "+" and see which time showing difference. All time(PHP, Mysql and Server) should be same. From report you will get idea that which one is not working or difference.

Thank you for the answer.
I have watched the Report page and found out that Server time is not running. When I update the page both php and MySQL times increase but Server time stays the same (but when I type "date" in the terminal I get correct value). Do you have an idea what that means and how to fix it?

I've also checked server timezone and php.ini (both set to Europe/Moscow) and installed ntpd. Same problem.

http://striker24x7.blogspot.in/2012/10/time-synchronization-error-vicidial.html?m=1


You can follow above link.

kisenok1989 wrote:Hello everyone.

Dahdi is installed on the server but I'm getting a "There is a time synchronization problem with your system, please tell your system administrator" error.

Looks like this is because there is no dahdi_dummy module. This is the output of "lsmod | grep dahd" command:
dahdi 225082 0
crc_ccitt 1717 1 dahdi

modprobe dahdi_dummy does not help.

Has anyone faced such problem?

This error can result from two possible major issues:
1) Time is not synced between two servers (ntp service should be set up in a cluster to allow all servers to subscribe to the same time service, preferably with one of the Vicidial servers being the master and iBurst in use so the others trust it implicitly).
2) timestamps are not being recorded by agent screens continually polling their web servers. This usually results from packets being dropped due to poor network communications between the agent's web browser and the Vicidial Web server

Neither of these is related to dahdi in any way. If dahdi is not loaded, meetme rooms will not work. But dahdi is no longer a separate module as it was with zap (zt_dummy), and is no longer visible.

Thanks everyone.

udy786 wrote:http://striker24x7.blogspot.in/2012/10/time-synchronization-error-vicidial.html?m=1
You can follow above link.

Tried all the steps in the blog. Unfortunetely it did't help.

williamconley wrote:2) timestamps are not being recorded by agent screens continually polling their web servers. This usually results from packets being dropped due to poor network communications between the agent's web browser and the Vicidial Web server

Didn't quite understand the problem can be caused by slow internet connection?
My agent page is continually requesting the server. This is the server responce.

Every request takes from 300 to 400 ms.

screen -list

how many are running?

williamconley wrote:screen -list

how many are running?

Here is the output:

Code: Select all

There are screens on:
        3470.ASTVDadapt (Detached)
        3480.ASTconf3way        (Detached)
        3267.astshell20160327205254     (Detached)
        4764.ASTlisten  (Detached)
        4758.ASTupdate  (Detached)
        4769.ASTVDremote        (Detached)
        4760.ASTsend    (Detached)
        3298.asterisk   (Detached)
        4767.ASTVDauto  (Detached)
9 Sockets in /var/run/screen/S-root.


5127.ASTfastlog missing ...

what do you have for VARactive_keepalives => 12345689 in astguiclient

do you have messages in /var/mail/root?

williamconley wrote:5127.ASTfastlog missing ...

what do you have for VARactive_keepalives => 12345689 in astguiclient

do you have messages in /var/mail/root?

Got lots of repeating messages there. Some of them say:

Code: Select all

problem connecting to "localhost", port 5038: Connection refused at /usr/share/astguiclient/AST_conf_update.pl line 259

Other say:

Code: Select all

Can't locate HTML/Strip.pm in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /usr/share/astguiclient/AST_inbound_email_parser.pl line 5.
BEGIN failed--compilation aborted at /usr/share/astguiclient/AST_inbound_email_parser.pl line 5.

Where can I check VARactive_keepalives => 12345689?

dahdi_dummy was just included in the general dahdi module as a fail-over timing source. So on newer DAHDI installs if the 'dahdi' module is loaded, then dahdi_dummy is loaded as well. If a more suitable hardware timer is also loaded, dahdi will use that instead.

Where can I check VARactive_keepalives => 12345689?
Inside this file
/etc/astguiclient.conf

kisenok1989 wrote:

williamconley wrote:5127.ASTfastlog missing ...

what do you have for VARactive_keepalives => 12345689 in astguiclient

do you have messages in /var/mail/root?

Got lots of repeating messages there. Some of them say:

Code: Select all

problem connecting to "localhost", port 5038: Connection refused at /usr/share/astguiclient/AST_conf_update.pl line 259

Other say:

Code: Select all

Can't locate HTML/Strip.pm in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /usr/share/astguiclient/AST_inbound_email_parser.pl line 5.
BEGIN failed--compilation aborted at /usr/share/astguiclient/AST_inbound_email_parser.pl line 5.

Where can I check VARactive_keepalives => 12345689?

If those message are continually generating (and not just flukes from reboots or pre-installation), you may have a bad install. Try running the mail parser manually:

Code: Select all

perl /usr/share/astguiclient/AST_inbound_email_parser.pl --debugX

Solved
Perl scripts were trying to connect asterisk manager. But it was not set up.

After adding the following code to the /etc/asterisk/manager.conf:

Code: Select all

[general]
enabled = yes
port = 5038
bindaddr = 127.0.0.1

[cron]
secret = blablabla
read = system,call,log,verbose,command,agent,user
write = system,call,log,verbose,command,agent,user
bindaddr = 127.0.0.1


time error disappeared.