RE: Installing axc - need help

["Paul Gale" <groups@xxxxxxxxxxxxxxxx>]

[root@asterisk1 axc]# ps -aux  grep axc
Warning: bad syntax, perhaps a bogus '-'? See
/usr/share/doc/procps-3.2.3/FAQ
root      2805  0.0  2.6 11156 6524 ?        S    17:35   0:01
/usr/bin/perl /us                                        
r/share/axc/axc.pl
root      3839  0.0  2.6 10068 6528 pts/0    S    17:53   0:01
/usr/bin/perl ./a                                         xc.pl
root      4091  0.0  2.6 10268 6528 pts/0    S    17:57   0:01
/usr/bin/perl ./a                                         xc.pl
root      4415  0.0  2.6 10532 6528 pts/0    S    18:00   0:01
/usr/bin/perl ./a                                         xc.pl
root      8195  1.0  2.6 11540 6532 pts/0    S    18:29   0:00
/usr/bin/perl ./a                                         xc.pl
root      8396  0.0  0.2  5128  656 pts/0    S+   18:31   0:00 grep axc

Looks like several versions still running then?

Paul.



-----Original Message-----
From: xap_automation@xxxxxxx [mailto:xap_automation@xxxxxxx] On
Behalf Of Gregg Liming
Sent: 23 March 2006 18:20
To: xap_automation@xxxxxxx
Subject: Re: [xap_automation] Installing axc - need help

Quoting Paul Gale (3/23/06 12:59 PM):
> Running the ps command, I got an error - user name does not exist
>
> Running the axc.pl from the command line seems to hold up for a short
while then fails.
>
> The axs.log does not exist and never seems to have. Is this a problem
with the config or something else? OR - does it get deleted at some stage?
>
> The tail shows:
>
> [root@asterisk1 axc]# tail -f axc.log
> INFO (::init) Completed initialization
> INFO (xAP::Comm): Created xAP send socket on port 3639
> INFO (xAP::Comm): Created xAP listen socket on port 49153
> INFO (::init) Completed initialization
> INFO (xAP::Comm): Created xAP send socket on port 3639
> INFO (xAP::Comm): Created xAP listen socket on port 49153
> INFO (::init) Completed initialization
> INFO (xAP::Comm): Created xAP send socket on port 3639
> INFO (xAP::Comm): Created xAP listen socket on port 49154
> INFO (::init) Completed initialization
>

The only way that the above could ever occur is if you are running
multiple instances of axc--which would definitely cause lots of
problems.  You need to be certain that you don't start a new axc process
if there are existing ones.  The reason for what appears to be multiple
ports is that you have multiple axc processes running.  It is important
that you kill all of the duplicate processes as they will create
problems for you.  I will add some form of process "lock" (e.g.,
use of
pid file) to try to keep this sort of thing happening in the future.
Until then, you'll need to ensure that only one axc instance is ever
running.

Gregg