On Fri, Sep 11, 2009 at 11:56 AM, Cuneyt M <[email protected]> wrote:
> Hi Scott, > > I have installed a CentOS ISO pub stable release today (4.0) and get it up > and running. Sipxbridge was functional. > > I did a yum update for the CentOS operating itself early today (before 4.2 > released) to get the latest OS updates. > > When i followed your guide to update to 4.0.2, didnt see any error during > install. > > yum clean all > yum update > service sipxecs restart > (output were all success) > > then i realized sipxbridge failed when i checked with sipxproc. > > Then i use first-run as folowing: > service sipxecs stop > sipxconfig.sh --first-run > service sipxecs start > > > once the service restarted (all ok in output), sipxbridge was in Testing > mode when i checked with sipxproc > > > When i login to webconfig i noticed the following error under details of > failed sipxbridge; > Even though i restarted the system, sipxbridge starts and fails with this. > Messages for SIP Trunking Standard error > > - SipXbridge : Exception caught while running > - org.sipfoundry.sipxbridge.SipXbridgeException: Exception starting web > server > - at > > org.sipfoundry.sipxbridge.SipXbridgeXmlRpcServerImpl.startXmlRpcServer(SipXbridgeXmlRpcServerImpl.java:134) > > - at org.sipfoundry.sipxbridge.Gateway.start(Gateway.java:1007) > - at org.sipfoundry.sipxbridge.Gateway.main(Gateway.java:1362) > - Caused by: java.net.BindException: Address already in use > - at java.net.PlainSocketImpl.socketBind(Native Method) > - at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359) > - at java.net.ServerSocket.bind(ServerSocket.java:319) > - at java.net.ServerSocket.<init>(ServerSocket.java:185) > - at javax.net.ssl.SSLServerSocket.<init>(SSLServerSocket.java:106) > - at > > com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.<init>(SSLServerSocketImpl.java:106) > > - at > > com.sun.net.ssl.internal.ssl.SSLServerSocketFactoryImpl.createServerSocket(SSLServerSocketFactoryImpl.java:72) > > - at org.mortbay.http.SslListener.newServerSocket(SslListener.java:257) > > - at org.mortbay.util.ThreadedServer.open(ThreadedServer.java:477) > - at > > org.sipfoundry.sipxbridge.SipXbridgeXmlRpcServerImpl.startXmlRpcServer(SipXbridgeXmlRpcServerImpl.java:79) > > - ... 2 more > > > Looks like sipxecs stop did not kill the previously running sipxbridge. The previous version had a problem with killing sipxbridge so I changed sipxbridge.sh to kill it cleanly. One of the things that was changed in sixpbridge.sh is the "stop" method of sipxbridge as the previous one was unreliable. Clearly it did not stop well for you. Plese find/kill the sipxbridge process and restart it. This will happen just for the first time. ps auxw | grep Gateway kill -9 pid where pid is the PID of the sipxbridge java process. Regards Ranga > > > _______________________________________________ > sipx-users mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > sipXecs IP PBX -- http://www.sipfoundry.org/ > -- M. Ranganathan
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
