ftocc

astwatch proccess id not running, hudlite cannot connect

bschaeffer
Posts: 2
Member Since:
2007-12-12

Trixbox Pro.
I cannot get hudlite client to connect.
Within the astwatch.log, I see the following recurring messages with different process id's:
* started v1.48 (09/04/07) up and backgrounded on PID 4497
* bad exit status from '/usr/sbin/asterisk -r -x 'show queues' ':256
* removing stale pid file /vaqr/run/astwatch.pid because PID 4497 is not running

I read through your FAQ on this topic and peformed the following without any luck.

1. confirmed hudlite-server is installed using:
ls /usr/local/fonality/hud/

2. confirmed hudlite is NOT running using:
pgrep "hudlite|saxirc"

3. confirmed astwatch is NOT running using:
ps awx | grep astwatch

4. started astwatch manually using:
/var/adm/bin/astwatch.pl

5. started hudlite manually using:
cd /usr/local/fonality/hud
nice -n 19 ./hudlite-server `cat auth.cfg`

6. confirmed IRC was NOT running using:
ps awx | grep ircd

7. started IRC manually using:
cd /usr/local/
/bin/su ircd -c /usr/local/ircd/bin/ircd

Extension Information:
Extension 2002
web username: sip2002
web password matches extension password in hudlite client
in hud marked as YES



dkullmann
Posts: 73
Member Since:
2007-01-02
Are all processes running after your troubleshooting?

bschaeffer

After your troubleshooting are astwatch, hud, and irc running?

If not:
What error messages do you get when starting them?

If so:
Are you connecting locally or remotely?

Also, if you give me your server ID I can check everything out. Please send it via a PM.

Thanks,
David J Kullmann
tb Pro Support

http://help.trixbox.com



rgil
Posts: 5
Member Since:
2008-01-22
Astwatch not running

HI

I am experiencing the same problem today on server 106808.

Astwatch.pl wont start and gives the following error:

[root@trixbox106808 ~]# /var/adm/bin/astwatch.pl
Segmentation fault
[root@trixbox106808 ~]#

Outbound and internal calls do not work and rebooting does not help.

Here is the error:

-- Executing Macro("SIP/0004132809C1-09b057a8", "stdexten|103|103|SIP/0004132809BF|90") in new stack
-- Executing Set("SIP/0004132809C1-09b057a8", "EXTENSION=103") in new stack
-- Executing AGI("SIP/0004132809C1-09b057a8", "fon://localhost:4574") in new stack
Jan 22 06:07:09 WARNING[3817]: res_agi.c:326 launch_netscript_fonality: Connect to 'fon://localhost:4574' failed: Connection refused
== Spawn extension (macro-stdexten, s, 2) exited non-zero on 'SIP/0004132809C1-09b057a8' in macro 'stdexten'
== Spawn extension (macro-stdexten, s, 2) exited non-zero on 'SIP/0004132809C1-09b057a8'

Please advise, thanks



blovett
Posts: 230
Member Since:
2007-04-26
There was an issue with an

There was an issue with an older release of astwatch, which caused the segmentation faults. An updated build has been released, and pushed out to systems. I have verified that astwatch is now running on your system.

Thanks,

Ben



dkullmann
Posts: 73
Member Since:
2007-01-02
bschaeffer - Are you up yet?

bschaeffer:

Has this problem been resolved on your system? I couldn't connect to it to check at the moment. Please update this thread/PM me if you are still experiencing problems.

Thanks,
David



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.