[SFtrack] Commented: (XECS-57) 'sipxproc' is not running in one of the machine in HA set up

["Raghu Venkataramana (JIRA)" <track@xxxxxxxxxxxxxx>]

    [ http://track.sipfoundry.org/browse/XECS-57?page=comments#action_20302 ] 
            
Raghu Venkataramana commented on XECS-57:
-----------------------------------------

I am unable to edit the issue. (I was trying to edit the Summary to indicate 
that the issue is not always reproducible)

The issue seen in this bug is not consistent. Although it was fairly easy for 
us to reproduce the problem on one of the test bed, this problem was not seen 
on the other test bed. 

Even when I try to do the restart process without sipxtools:
wget --no-check-certificate 
https://sipx-brblab.qantom.int:8091//cgi-bin/processmonitor/process.cgi?command=status

I observe one of the following: a) The operation times out after a while or b) 
The operation completes after a long delay. I dont think it has anything to do 
with network connection as I am running the command the same machine

> 'sipxproc' is not running in one of the machine in HA set up
> ------------------------------------------------------------
>
>                 Key: XECS-57
>                 URL: http://track.sipfoundry.org/browse/XECS-57
>             Project: sipXecs
>          Issue Type: Bug
>    Affects Versions: 3.7
>         Environment:  sipxpbx 3.7.0-008169 2007-04-12T01:09:58 
> eagle.pingtel.com
>            Reporter: Archana Hegde
>         Assigned To: Douglas Hubler
>         Attachments: sipx-configuration-sipx-brblab.qantom.int.tar.gz
>
>
> Pre-condition:
> 1)HA set up should be ready.
> Mater machine: sipx-test.qantom.int
> Distributed machine : sipx-brblab.qantom.int
> 2) Manually  modified the file in sipx-brblab.qantom.int :  
> /etc/sipxpbx/httpd-sipxchange-common.conf.in 
> Steps:
> 1)Navigate to sipx-brblab machine and check that all the services are running
> 2)Now  verify that sipproc services are running, by the following command :
> [root@sipx-brblab sipxpbx]# sipxproc
> 3)It gave the following error message:
> warning: peer certificate won't be verified in this SSL session
> /usr/lib/ruby/1.8/timeout.rb:54:in `rbuf_fill': execution expired 
> (Timeout::Error)
>         from /usr/lib/ruby/1.8/timeout.rb:56:in `timeout'
>         from /usr/lib/ruby/1.8/timeout.rb:76:in `timeout'
>         from /usr/lib/ruby/1.8/net/protocol.rb:132:in `rbuf_fill'
>         from /usr/lib/ruby/1.8/net/protocol.rb:116:in `readuntil'
>         from /usr/lib/ruby/1.8/net/protocol.rb:126:in `readline'
>         from /usr/lib/ruby/1.8/net/http.rb:1988:in `read_status_line'
>         from /usr/lib/ruby/1.8/net/http.rb:1977:in `read_new'
>         from /usr/lib/ruby/1.8/net/http.rb:1046:in `request'
>         from /usr/bin/sipxproc:52:in `get_url'
>         from /usr/lib/ruby/1.8/net/http.rb:545:in `start'
>         from /usr/bin/sipxproc:50:in `get_url'
>         from /usr/bin/sipxproc:22:in `process_status'
>         from /usr/bin/sipxproc:123
> 4)Also httpd_error_log displayed the following error:
> [Mon Apr 16 13:15:34 2007] [error] [client 176.25.1.247] malformed header 
> from script. Bad header=PROCESSMGR ERR  0x00000000 F
> AI: process.cgi
> Attachements:
> sipx-configuration-sipx-brblab.qantom.int.tar.gz
> Observations:
> In master machine  sipxproc is working fine

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://track.sipfoundry.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira