Hello,
I have a generic setup of openser 1.0.1 compiled with the PostgreSQL module on Slackware 10.2 and looks like all the modules load right.
When I run it in the no-fork debug mode it works fine. When I set it to fork, it doesn't write the /var/run/openser.pid file and I have a 8 [openser] <defunct> processes running.
I start it like so ./openser -f /etc/openser/openser.conf -P /var/run/openser.pid
Where should I start looking?
ScriptHead
Script Head wrote:
Hello,
I have a generic setup of openser 1.0.1 compiled with the PostgreSQL module on Slackware 10.2 and looks like all the modules load right.
When I run it in the no-fork debug mode it works fine. When I set it to fork, it doesn't write the /var/run/openser.pid file and I have a 8 [openser] <defunct> processes running.
I start it like so ./openser -f /etc/openser/openser.conf -P /var/run/openser.pid
Where should I start looking?
increase the debug level (debug=4) and wath the syslog messages
tail -f /var/log/syslog | grep -v qm_
regards klaus
Ok, I have resolved the <defunct> problem, which was cuased by not having enough available database connections. Alas, openser still doesn't create /var/run/openser.pid file
On 2/27/06, Klaus Darilion klaus.mailinglists@pernau.at wrote:
Script Head wrote:
Hello,
I have a generic setup of openser 1.0.1 compiled with the PostgreSQL module on Slackware 10.2 and looks like all the modules load right.
When I run it in the no-fork debug mode it works fine. When I set it to fork, it doesn't write the /var/run/openser.pid file and I have a 8 [openser] <defunct> processes running.
I start it like so ./openser -f /etc/openser/openser.conf -P /var/run/openser.pid
Where should I start looking?
increase the debug level (debug=4) and wath the syslog messages
tail -f /var/log/syslog | grep -v qm_
regards klaus
-
Klaus Darilion -
Script Head