Paul Scheepens wrote: > > Hi Guys, > > I wanted to build a new HA sipx server so I installed a 3.10.1 and yum > updated it to 3.10.3-014144. > Now the callresolver won't start. It fails immediately. > I increased the log level to DEBUG, but the log file is not updated > anymore. > This is the contents although I tried to start/rebooted etc several > times after 13:55 > > [r...@gssipx02 sipxpbx]# cat /var/log/sipxpbx/sipcallresolver.log > "2009-03-31T10:37:15.066819 ":INFO:Stunnel started: 9954 > "2009-03-31T13:54:56.488708 ":INFO:TERM intercepted. Terminating reader > threads. > "2009-03-31T13:54:56.489766 ":ERR:Exiting because of error: "could not > connect to server: Connection refused > Is the server running on host "localhost" and accepting > TCP/IP connections on port 5433? > "
This is a primary server right (callresolver should only be running on a primary server). callresolver won't start unless it can connect to postgress servers on all the systems in HA cluster on which proxy is running This error suggests that postgress is not running on primary server. Or is running but does not accept connections from postgres user. Try: psql -U postgres -d SIPXCDR Is this the only problem that you see? If yes it's probably best to configure everything else and then configure call resolver. The good news is that it's much simpler in 4.0: sipXconfig generates and pushes correct configuration to all servers. [...] D. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
