[Giorgio Pioda] > Any additional idea? Did you try to check <URL: http://bugs.debian.org/src:cups > to see if anyone already reported the problem? Perhaps it is <URL: http://bugs.debian.org/549050 >? Is there anything in /var/log/syslog when it crashes (for example a segfault message from the kernel?)
If the server got the memory needed, install cups-dbg and run cupsd under valgrind (edit init.d/cups or run it manually, for example using -f). This will give you details about the crash when it happen, but will eat more memory than usual. If the server do not got the memory needed, install cups-dbg and attach to the running cupsd process using "gdb -p $(pidof cupsd)" as root, and press 'c' [enter] on the prompt to let the server continue. When it crashes, press 'bt' [enter] to get a backtrace from the crash. When you know why it crash, report the bug to bugs.debian.org, to make it possible for the developers and package maintainer to track down and fix the bug. In the mean time, you can instead of monit add a cron job for root to restart cupsd when it fail: For example something like this: */1 * * * * if ! kill -0 $(cat /var/run/cups/cupsd.pid) ; then service cups restart; fi But this make it impossible to debug the issue and fix it permanently. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
