vicidial.org

Hi All,

I have had some intermittent troubles with the ASTloop IAX2 trunk not registering. I've had a bit deeper of a look and have noticed that ip_relay doesn't seem to be working quite right. Here is the output of netstat. I'm noticing that the port for one of them isn't correct. I've gone into /usr/share/astguiclient/ip_relay and trying to run the perl relay_control restart/reload or start commands gives me a No such file or directory error. The file is definitely there and I get the same error if I try and run it manually.

The relay_control script isn't working on any of my installs (All vicibox v9.3) but I'm only having the actual ip_relay issue on one server. They are being restarted fine by the keepalive.

Any ideas?

Code: Select all

tcp        0      0 0.0.0.0:41569           0.0.0.0:*               LISTEN      2368/ip_relay
tcp        0      0 0.0.0.0:42569           0.0.0.0:*               LISTEN      2369/ip_relay
tcp        0      0 0.0.0.0:10185           0.0.0.0:*               LISTEN      2367/ip_relay


im going to assume the problem is on the one with the wrong port, and try checking the ip_relay with status and it should be fine....





im not sure why its going to another port, but is that port open on that server when you type "ss -ltnu" ?

Yeah it was definitely the one with the wrong port. relay_control status works fine, it is only relay_control start that isn't working but they do get restarted again through the keepalive script. In saying that, the keepalive doesn't look for the situation if only one ip_relay fails (as in process is killed completely) or if ip_relay is bound to the wrong port, perhaps this is a potential enhancement. Carpenox, if you have a vicibox 9.0+ system, can you try running perl /usr/share/astguiclient/ip_relay/relay_control restart and see if you have the same issue

i do and the app is running, so you can not run it, if you go to the file and try to view it, you will see many lines of "executable code as its being run" pass thru the screen. that isnt the issue, its the port thats the issue. i forget what conf file that is set in, but ive never seen it out of the 45000 range before....so something is definitely wrong there. perhaps Matt or Bill can chime in on this one

The port was a once off, on successive reboots and restarts of ip_relay it works fine, it has just been 2 or 3 days with the issue out of the past 5 months it has been running so not a major, probably a network interface not starting quickly enough. Yeah I'm familiar with the code, I'm a software engineer, nothing astray there. Just strange that the keepalive works fine to restart it (which uses relay_control anyway) but I can't seem to run it manually to restart it.

On further investigation, running the keepalive script manually doesn't restart ip_relay but running it through the crontab does. Maybe I'm missing a bit of linux knowledge here, any idea why this would be?

i believe its because its one of those programs that once its running you cant run it again, try to stop the PID then try

Yep, tried that. I even made a script to run the relay_control imitating the keepalive script which didn't work when I ran it manually but worked fine if I ran it in a cron. Tried running in sh instead of bash. Must be something to do with the cron shell setup.

hit me up on skype, ill try to help you debug it