On Wed, 2006-03-15 at 10:30 +0100, Cristian Livadaru wrote:
I had this same problem a week or two ago and had to downgrade. Two separate systems with very similar configs both showed this behavior. A few messages were logged, then after fifteen minutes or less, no more output. The process was running but nobody was home.
I regret that I didn't bug it, but I just don't have time on the side to deal with it right now.
The system is Debian GNU/Linux, Unstable, on i386.
same for me Debian unstable I can't risc to put back the 1.9.9 version I can just hope it is reproduceable on my testserver which has been upgraded today. I only have a strace of mailq which then hangs while trying to access /dev/log want me to send this? else if the error occours on the testserver I can do watever trace or test you need.
The strace on mailq is useless, I would need the info on syslog-ng itself.
Your testing is greatly appreciated.
I will keep an eye on my testsystem if this happenes there. if not maybee I will install on a weekend where there is not much going on on the production system the version 1.9.9 again and I can try to test it. just give some information on what you need and how I could obtain it.
* an lsof -p <syslog-ng pid>, strace of the hanged process should be enough, * enabling debug symbols, attaching to the process using gdb (gdb -p <pid>) and doing a backtrace (bt command in gdb) would be better, * enabling core dumps before starting syslog-ng, sending a SIGQUIT to it, and sending me the binaries and the core files would be ideal -- Bazsi