On Sat, 6 Nov 2004 15:57:13 -0500, "Cory Megitt [ClamAV]" <[EMAIL PROTECTED]> wrote:
>Hi All; > >The following command gets run at 2am each night. >/usr/bin/freshclam --quiet -l /var/log/clamav/clam-update.log > > >I always find an email stating the following: > ERROR: Clamd was NOT notified: Can't connect to clamd on 127.0.0.1:3310 >connect(): Connection refused > >How can I fix this? > > In your clamd.conf file, are you set to use a TCP socket or a UNIX socket? Check for these lines in clamd.conf # TCP port address. #TCPSocket 3310 # Path to the local socket. The daemon doesn't change the mode of the # created file (portability reasons). You may want to create it in a directory # which is only accessible for a user running daemon. LocalSocket /var/run/clamav/clamd.sock and these in freshclam.conf # Send the RELOAD command to clamd. NotifyClamd /etc/clamd.conf Next, if you're using a local clamd.sock file like I'm doing, make sure the permissions are "srwxrwxrwx". If you're using the TCPSocket (by commenting out the LocalSocket line and uncommenting the TCPSocket line, make sure your firewall allows local connections to port 3310. If you set up a standard firewall, that port is probably blocked. -- Steve _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
