I had this issue as well.
I reported to the list several months ago. I thought
I posted the fix as well, perhaps not.
The reason is that SER opens many, many database
connections. I believe 32 connections are opened. So
You have to increase the number of database connections you
handle in the postgres configuration, which defaults to 16
I think.
The setting you need to tweak is
max_connections = 256
in the postgresql.conf file. The database then needs to be
restarted. Note that this setting affects others, both directly
related
to postgres and also the operating system (file descriptors, etc)...
---greg
-----Original Message-----
From: serusers-bounces(a)lists.iptel.org
[mailto:serusers-bounces@lists.iptel.org] On Behalf Of Takefumi Naito
Sent: Monday, July 28, 2003 10:25 AM
To: serusers(a)lists.iptel.org
Subject: [Serusers] PostgreSQL
Thanks a lot for your advise.
I tried to do
$psql -h localhost -p 5432 -U seruser -W ser
Connecting database ser is success.
But in the log file, these following lines appeared
after SER started using /usr/sbin/ser command.
FATAL: Non_superuser connection limit exceeded
LOG: pq_recvbuf:unexpected EOF on client connection
Maybe this is the reason database doesn't work, I think.
It seems SER can't connect to postgres.
What should I do?
Another problem: SER processes don't stop using /usr/sbin/ser stop.
Many SER processes are surviving.
Is it strange?
Most sincerely
Takefumi
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers