On Thu, 2009-04-02 at 12:28 +0200, Paul Scheepens wrote: > > Hi, > > Sorry for the "subject" mix-up in my previous 2 posts. > I still have problems with my callresolver though. > > Here some info from sipxcallresolver.log (I was originally only > looking in sipcallresolver.log): > > "2009-04-02T11:18:08.226927 ":DEBUG:cse_hosts: host name localhost, > host port: 5432 > "2009-04-02T11:18:08.227166 ":DEBUG:cse_hosts: host name > gmsipx02.internal.epo.org, host port: 5433 > "2009-04-02T11:18:08.227244 ":DEBUG:Found host other than localhost - > enable HA > "2009-04-02T11:18:08.228446 ":DEBUG:Polling CSE DB every 10 seconds. > "2009-04-02T11:18:08.228601 ":DEBUG:Polling CSE DB every 10 seconds. > "2009-04-02T11:18:08.229234 ":DEBUG:# This file was automatically > generated by sipxcallresolver > client = yes > foreground = yes > CApath = /etc/sipxpbx/ssl/authorities > cert = /etc/sipxpbx/ssl/ssl.crt > key = /etc/sipxpbx/ssl/ssl.key > verify = 2 > debug = 5 > output = /var/log/sipxpbx/sipxstunnel.log > pid = /var/log/sipxpbx/sipxstunnel.pid > > "2009-04-02T11:18:08.229365 ":DEBUG: > [Postgres-1] > accept = 5433 > connect = gmsipx02.internal.epo.org:9300 > > "2009-04-02T11:18:08.229491 ":INFO:Starting /usr/sbin/stunnel with > configuration: /tmp/stunnel-config.7375.0 > "2009-04-02T11:18:11.229533 ":INFO:Stunnel started: 7417 > "2009-04-02T11:18:11.240405 ":DEBUG:Purging CSEs older than Thu Mar 26 > 10:18:11 +0100 2009 > "2009-04-02T11:18:11.244177 ":ERR:Problems with DB connection. > "2009-04-02T11:18:11.244286 ":ERR:Exiting because of error: <server > closed the connection unexpectedly > This probably means the server terminated abnormally > before or while processing the request. > > > "2009-04-02T11:18:11.244448 ":ERR: > /usr/lib/ruby/1.8/DBD/Pg/Pg.rb:111:in `initialize' > /usr/lib/ruby/1.8/DBD/Pg/Pg.rb:55:in `new' > /usr/lib/ruby/1.8/DBD/Pg/Pg.rb:55:in `connect' > /usr/lib/ruby/1.8/dbi.rb:424:in `connect' > /usr/lib/ruby/1.8/dbi.rb:215:in `connect' > /usr/lib/ruby/gems/1.8/gems/sipxcallresolver-2.0.0/lib/db/dao.rb:43:in > `connect' > /usr/lib/ruby/gems/1.8/gems/sipxcallresolver-2.0.0/lib/db/dao.rb:48:in > `test_connection' > /usr/lib/ruby/gems/1.8/gems/sipxcallresolver-2.0.0/lib/call_resolver.rb:44:in > `check_connections' > /usr/lib/ruby/gems/1.8/gems/sipxcallresolver-2.0.0/lib/call_resolver.rb:44:in > `each' > /usr/lib/ruby/gems/1.8/gems/sipxcallresolver-2.0.0/lib/call_resolver.rb:44:in > `check_connections' > /usr/lib/ruby/gems/1.8/gems/sipxcallresolver-2.0.0/lib/main.rb:108:in > `main' > /usr/lib/ruby/gems/1.8/gems/sipxcallresolver-2.0.0/lib/main.rb:127 > [r...@gssipx02 sipxpbx]# > > I can connect to the database I think, this is the output from > Damian's advise: > > r...@gssipx02 sipxpbx]# psql -U postgres -d SIPXCDR > Welcome to psql 8.1.11, the PostgreSQL interactive terminal. > > Type: \copyright for distribution terms > \h for help with SQL commands > \? for help with psql commands > \g or terminate with semicolon to execute query > \q to quit > > SIPXCDR=# > > Also works on the distributed server: > > [r...@gmsipx02 ~]# psql -U postgres -d SIPXCDR > Welcome to psql 8.1.11, the PostgreSQL interactive terminal. > > Type: \copyright for distribution terms > \h for help with SQL commands > \? for help with psql commands > \g or terminate with semicolon to execute query > \q to quit > > SIPXCDR=# > > And from the sipxstunnel.log: > > 2009.04.02 11:18:08 LOG5[7417:3085915856]: stunnel 4.15 on > i686-redhat-linux-gnu with OpenSSL 0.9.8b 04 May 2006 > 2009.04.02 11:18:08 LOG5[7417:3085915856]: Threading:PTHREAD > SSL:ENGINE Sockets:POLL,IPv6 Auth:LIBWRAP > 2009.04.02 11:18:08 LOG5[7417:3085915856]: 8000 clients allowed > 2009.04.02 11:18:11 LOG5[7417:3085912976]: Postgres-1 connected from > 127.0.0.1:50067 > 2009.04.02 11:18:11 LOG3[7417:3085912976]: connect_wait: getsockopt: > Connection refused (111) > 2009.04.02 11:18:11 LOG5[7417:3085912976]: Connection reset: 0 bytes > sent to SSL, 0 bytes sent to socket > 2009.04.02 11:18:11 LOG5[7417:3085915856]: Received signal 15; > terminating > > Any help is welcome.
Check the stunnel configuration on the distributed system and the logs there for errors starting the other end of the tunnel. Confirm that the distributed system does not have the firewall enabled. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
