clamd after upgrade to 0.83

[Robert Fitzpatrick]

After doing a portupgrade of clamd from 0.81 to 0.83, the service reports
that it is not running using 'clamav-clamd.sh status'.

esmtp# cd /usr/local/etc
esmtp# rc.d/clamav-clamd.sh status
clamav_clamd is not running.
esmtp# ps -ax|grep clam
781 ?? Ss 0:10.96 /usr/local/sbin/clamd

However, all seems to be fine, postfix 2.1.5, amavisd-new and clamd all
seem to be running and Webmin reports them all as running.

Any thoughts or something I should know regarding the upgrading? I checked
/usr/ports/UPDATING, but nothing regarding this. All conf files are
reflecting the new settings.

--
Robert

[Robert Fitzpatrick]

I do not have anything in /var/run/clamav and that is the location in
clamd.conf for placing the PID file. I cannot connect to the localhost as
well:

esmtp# telnet localhost 3310
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
telnet: Unable to connect to remote host

However, according to the clamd.log, clamav is intercepting viruses. Do you
think it is working and why would I not be able to connect via telnet or
view the pid file if it is?

--
Robert


--On Wednesday, February 23, 2005 8:35 PM +0100 "Daniel S. Haischt"
<me@daniel.stefan.haischt.name> wrote:

> Usually if you are running ClamAV in UNI domain socket mode,
> there should be a UNIX domain socket called 'clamd' in ...
>
> -> /var/run/clamav
>
> Tho - this file can be configured in /usr/local/etc/clamd.conf.
>
> If ClamAv is running in TCP/IP mode it should be possible to
> test whether the server is responding by connecting to its
> TCP/IP port using a telnet client ...
>
> -> telnet localhost 3310
>
> Robert Fitzpatrick schrieb:

>> After doing a portupgrade of clamd from 0.81 to 0.83, the service
>> reports that it is not running using 'clamav-clamd.sh status'.
>>
>> esmtp# cd /usr/local/etc
>> esmtp# rc.d/clamav-clamd.sh status
>> clamav_clamd is not running.
>> esmtp# ps -ax|grep clam
>> 781 ?? Ss 0:10.96 /usr/local/sbin/clamd
>>
>> However, all seems to be fine, postfix 2.1.5, amavisd-new and clamd all
>> seem to be running and Webmin reports them all as running.
>>
>> Any thoughts or something I should know regarding the upgrading? I
>> checked /usr/ports/UPDATING, but nothing regarding this. All conf files
>> are reflecting the new settings.
>>
>> --
>> Robert
>>
>> _______________________________________________
>> [email]freebsd-questions@freebsd.org[/email] mailing list
>> [url]http://lists.freebsd.org/mailman/listinfo/freebsd-questions[/url]
>> To unsubscribe, send any mail to
>> "freebsd-questions-unsubscribe@freebsd.org"

[greg@grokking.org]

Robert Fitzpatrick wrote:

> After doing a portupgrade of clamd from 0.81 to 0.83, the service
> reports that it is not running using 'clamav-clamd.sh status'.
>
> esmtp# cd /usr/local/etc
> esmtp# rc.d/clamav-clamd.sh status
> clamav_clamd is not running.
> esmtp# ps -ax|grep clam
> 781 ?? Ss 0:10.96 /usr/local/sbin/clamd
>
> However, all seems to be fine, postfix 2.1.5, amavisd-new and clamd all
> seem to be running and Webmin reports them all as running.
>
> Any thoughts or something I should know regarding the upgrading? I
> checked /usr/ports/UPDATING, but nothing regarding this. All conf files
> are reflecting the new settings.
>

Check access on the relevant directories. By default, clamav runs as
user 'clamav' but amavisd runs as user 'vscan' so the directories where
the pid, socket AND virus database all need to be reconciled to
whichever user you run these as. I use 'vscan' so I pass the CLAMAVUSER
and CLAMAVGROUP this value when I 'make install' clamav initially. Then,
I add these to /usr/local/etc/pkgtools.conf so that the next portupgrade
doesn't undo it.

Hope that helps,

G

[Robert Fitzpatrick]

Thanks, that explains why postfix is still logging. But clamd is running...

esmtp# ps -ax | grep clam
26441 ?? Ss 0:00.37 /usr/local/sbin/clamd
26467 ?? Is 0:00.00 /usr/local/bin/freshclam --daemon
26494 ?? Is 0:00.00 /usr/local/bin/freshclam --daemon

But still the server thinks it is not and there is no pid file...

esmtp# /usr/local/etc/rc.d/clamav-clamd.sh status
clamav_clamd is not running.
esmtp# ls -la /var/run/clamav/
total 4
drwxr-xr-x 2 clamav clamav 512 Feb 23 21:51 .
drwxr-xr-x 6 root wheel 512 Feb 23 21:51 ..
esmtp#

I even uninstalled and re-installed. Any ideas why this is not reporting as
running?

--
Robert


--On Wednesday, February 23, 2005 9:10 PM +0100 "Daniel S. Haischt"
<me@daniel.stefan.haischt.name> wrote:

> I think the following section in /usr/local/amavisd.conf
> should answer your question:
>
> ### [url]http://www.clamav.net/[/url] - backs up clamd or Mail::ClamAV
> ['ClamAV-clamscan', 'clamscan',
> "--stdout --disable-summary -r --tempdir=$TEMPBASE {}", [0], [1],
> qr/^.*?: (?!Infected Archive)(.*) FOUND$/ ],
>
> Basically if clamd is not running Amavis will execute the
> commandline scanner version of ClamAV. That's the reason why
> you are still getting log entries.
>
> So to sumarize: ClamAV's daemon is not running, thus
> there is neither a PID file nor a UNIX domain socket.
>
> So if you want to use the daemonized version of ClamAV,
> you need to elaborate why the daemon isn't started.
>
> Robert Fitzpatrick schrieb:

>> I do not have anything in /var/run/clamav and that is the location in
>> clamd.conf for placing the PID file. I cannot connect to the localhost
>> as well:
>>
>> esmtp# telnet localhost 3310
>> Trying ::1...
>> telnet: connect to address ::1: Connection refused
>> Trying 127.0.0.1...
>> telnet: connect to address 127.0.0.1: Connection refused
>> telnet: Unable to connect to remote host
>>
>> However, according to the clamd.log, clamav is intercepting viruses. Do
>> you think it is working and why would I not be able to connect via
>> telnet or view the pid file if it is?
>>
>> --
>> Robert
>>
>>
>> --On Wednesday, February 23, 2005 8:35 PM +0100 "Daniel S. Haischt"
>> <me@daniel.stefan.haischt.name> wrote:
>>

>>> Usually if you are running ClamAV in UNI domain socket mode,
>>> there should be a UNIX domain socket called 'clamd' in ...
>>>
>>> -> /var/run/clamav
>>>
>>> Tho - this file can be configured in /usr/local/etc/clamd.conf.
>>>
>>> If ClamAv is running in TCP/IP mode it should be possible to
>>> test whether the server is responding by connecting to its
>>> TCP/IP port using a telnet client ...
>>>
>>> -> telnet localhost 3310
>>>
>>> Robert Fitzpatrick schrieb:
>>>
>>>> After doing a portupgrade of clamd from 0.81 to 0.83, the service
>>>> reports that it is not running using 'clamav-clamd.sh status'.
>>>>
>>>> esmtp# cd /usr/local/etc
>>>> esmtp# rc.d/clamav-clamd.sh status
>>>> clamav_clamd is not running.
>>>> esmtp# ps -ax|grep clam
>>>> 781 ?? Ss 0:10.96 /usr/local/sbin/clamd
>>>>
>>>> However, all seems to be fine, postfix 2.1.5, amavisd-new and clamd all
>>>> seem to be running and Webmin reports them all as running.
>>>>
>>>> Any thoughts or something I should know regarding the upgrading? I
>>>> checked /usr/ports/UPDATING, but nothing regarding this. All conf files
>>>> are reflecting the new settings.
>>>>
>>>> --
>>>> Robert
>>>>
>>>> _______________________________________________
>>>> [email]freebsd-questions@freebsd.org[/email] mailing list
>>>> [url]http://lists.freebsd.org/mailman/listinfo/freebsd-questions[/url]
>>>> To unsubscribe, send any mail to
>>>> "freebsd-questions-unsubscribe@freebsd.org"

>>
>>
>>
>>
>>
>> _______________________________________________
>> [email]freebsd-questions@freebsd.org[/email] mailing list
>> [url]http://lists.freebsd.org/mailman/listinfo/freebsd-questions[/url]
>> To unsubscribe, send any mail to
>> "freebsd-questions-unsubscribe@freebsd.org"