clamd crashed with SIGSEGV in tcpserver()

Bug #288931 reported by KarstenL
This bug report is a duplicate of:  Bug #288942: clamd daemon fails to load. Edit Remove
2
Affects Status Importance Assigned to Milestone
clamav (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: clamav

In Thunderbird i get a ClamAV status named "Connection Problems" with clamdrib 0.2 enablet when i send messages.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/sbin/clamd
NonfreeKernelModules: nvidia
Package: clamav-daemon 0.94.dfsg.1~rc1-0ubuntu1
ProcAttrCurrent: /usr/sbin/clamd (enforce)
ProcCmdline: /usr/sbin/clamd
ProcEnviron: PATH=/sbin:/bin:/usr/sbin:/usr/bin
Signal: 11
SourcePackage: clamav
StacktraceTop:
 tcpserver (copt=0x9485590) at tcpserver.c:76
 main (argc=) at clamd.c:431
Title: clamd crashed with SIGSEGV in tcpserver()
Uname: Linux 2.6.27-7-generic i686
UserGroups: clamsmtp

Tags: apport-crash
Revision history for this message
KarstenL (postbox-surfpost) wrote :
Revision history for this message
Scott Kitterman (kitterman) wrote :

Did you setup clamd to use a tcp socket. You add this to /etc/clamav/clamd.conf:

TCPSocket 3310
TCPAddr localhost

And then restart clamd:

sudo /etc/init.d/clamav-daemon restart

I've installed and run this plugin and cannot reproduce your problem.

Changed in clamav:
status: New → Incomplete
Revision history for this message
KarstenL (postbox-surfpost) wrote : Re: [Bug 288931] Re: clamd crashed with SIGSEGV in tcpserver()

Thank you for a fast answer.

First of all I have to admit that I am a complete newbie to Linux. In
the old days I worked i bit with dos, but from then I just followed the
mainstream and went with the different windows distributions. Along the
line I just had enough, as the windows (vista) seemed to take over my
computer. As I had been using Firefox and Thunderbird for a while, i
decided to go with Linux - in this case ubuntu. (I actually find it a
bit fun to use command lines again...). Well back to my problem:

I already had changed clamd. to a tpc socket.
Now I then tried to restart clamd with

sudo /etc/init.d/clamav-daemon restart

but restart failed and I got this message: Segmentation fault (core
dumped) and at the end of next line (FAIL)
Could the probmem, that I earlier this week, when trying to install
AntiVir also installed Dazuko, withc im not sure I have completely
removed again?

Any suggestions?

Up front I would just say thank you for spending time to solve this for
me...!

Scott Kitterman wrote:
> Did you setup clamd to use a tcp socket. You add this to
> /etc/clamav/clamd.conf:
>
> TCPSocket 3310
> TCPAddr localhost
>
> And then restart clamd:
>
> sudo /etc/init.d/clamav-daemon restart
>
> I've installed and run this plugin and cannot reproduce your problem.
>
> ** Changed in: clamav (Ubuntu)
> Status: New => Incomplete
>
>

Revision history for this message
Scott Kitterman (kitterman) wrote :

I think it could. The Dazuko modules modify your kernel to support on
access file scanning. Unfortunately they are incompatible with the way
Ubuntu builds its kernel.

I looked into trying to get Dazuko into the Ubuntu kernel a few months ago
and concluded it would be very difficult to get them to work correctly.

There is likely a related problem. In Ubuntu we use Apparmor to increase
security by enforcing process separation. Since clamdrib is not part of
the official Ubuntu package repository, we didn't know to consider it in
developing the Apparmor profile for clamav (I have another clamav bug I'm
working that points to this).

I'll work on that and I suggest you use the Launchpad ask a question
function to get help on removing Dazuko.

Revision history for this message
Greg Eden (grege) wrote :

If it helps, as in the original report I too have the nvidia module loaded

Scott Kitterman wrote:
> *** This bug is a duplicate of bug 288942 ***
> https://bugs.launchpad.net/bugs/288942
>
> ** This bug has been marked a duplicate of bug 288942
> clamd daemon fails to load
>
>

--
===================================
Greg Eden
<email address hidden>

Revision history for this message
Scott Kitterman (kitterman) wrote :

It's not relevant. All we need is to figure out the right Apparmor
profile. I doubut if we'll be able to get it fixed before release, but
there is a new clamav release 3 Nov that we are going to try and get into
the intrepid-updates. We've got a good shot for fixing it there.

Revision history for this message
Greg Eden (grege) wrote :

Scott,

Thank you for your help, the aa-complain works fine. I will await a
solution.

AppArmor is more important anyway, clamav is more for the Windows
machines of other people.

:)

Scott Kitterman wrote:
> *** This bug is a duplicate of bug 288942 ***
> https://bugs.launchpad.net/bugs/288942
>
> It's not relevant. All we need is to figure out the right Apparmor
> profile. I doubut if we'll be able to get it fixed before release, but
> there is a new clamav release 3 Nov that we are going to try and get into
> the intrepid-updates. We've got a good shot for fixing it there.
>
>

--
===================================
Greg Eden
<email address hidden>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.