Here's another question... Does the qmailq user have perms to bind to unix or tcp sockets, if it can't bind a unix or tcp socket, that would be why the crash happens... clamd does not do very good error reporting to the console.... See what perms that the qmailq user has to both /var/run and to /tmp Also maybe use a UID/GID around 100, might give some more perm access, but clamd will have to be able to write to both of those dirs... Otherwise, it can't use it's pidfile, and it can't create a socket for connections to it, the socket isn't really used much unless you're using something like mimedefang or spamassassin, etc, but if using it for email scanning, etc, it is essential....
Brian Read wrote: > At 18:05 27/12/2002, you wrote: > >> On Fri, 27 Dec 2002 16:58:13 +0000 >> Brian Read <[EMAIL PROTECTED]> wrote: >> >> > >> > I am trying to start clamd (from the command line), and it does not >> give me >> > any error messages, but it fails to start, that is it does not >> appear in >> > the ps -ax list. where should I look for an error messages, ort >> what might >> > be the trouble? >> > >> > It was starting yesterday, something seems to have changed. >> >> Please post the log file (LogFile). > > > log file: > > Fri Dec 27 19:24:26 2002 -> +++ Started at Fri Dec 27 19:24:26 2002 > Fri Dec 27 19:24:26 2002 -> Log file size limited to 1048576 bytes. > Fri Dec 27 19:24:26 2002 -> Verbose logging activated. > Fri Dec 27 19:24:26 2002 -> Running as user qmailq (UID 404, GID 401) > Fri Dec 27 19:24:26 2002 -> ERROR: Can't save PID in file > /var/run/clamd.pid > Fri Dec 27 19:24:26 2002 -> Reading databases from /usr/share/clamav > Fri Dec 27 19:24:26 2002 -> Protecting against 7286 viruses. > Fri Dec 27 19:24:26 2002 -> ERROR: bind() error. > [EMAIL PROTECTED] root]# > > Looks as though it might be file properties for /var/run? (there is no > Clamd.pid). > > drwxr-xr-x 9 root root 4096 Dec 27 16:56 run > > is that correct? > > cheers > > Brian > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
