Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
clamd crash
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo
View previous topic :: View next topic  
Author Message
Vieri
l33t
l33t


Joined: 18 Dec 2005
Posts: 879

PostPosted: Sat Jan 27, 2018 5:14 pm    Post subject: clamd crash Reply with quote

Hi,

I've never had issues with clamd, but recently I had 2 crashes.
This is the latest log:

Code:

Fri Jan 26 19:31:21 2018 -> ERROR: accept() failed:
Fri Jan 26 19:31:21 2018 -> ERROR: accept() failed:
Fri Jan 26 19:31:21 2018 -> ERROR: accept() failed:
Fri Jan 26 19:31:21 2018 -> ERROR: accept() failed:
Fri Jan 26 19:31:21 2018 -> ERROR: accept() failed:
Fri Jan 26 19:31:21 2018 -> ERROR: accept() failed:
Fri Jan 26 19:31:21 2018 -> ERROR: accept() failed:
Fri Jan 26 19:31:21 2018 -> ERROR: accept() failed:
Fri Jan 26 19:31:42 2018 -> instream(127.0.0.1@39470): Can't create new file ERROR
Fri Jan 26 19:31:42 2018 -> instream(127.0.0.1@39474): Can't create new file ERROR
Fri Jan 26 19:31:46 2018 -> Reading databases from /var/lib/clamav
Fri Jan 26 19:31:46 2018 -> ERROR: reload db failed: Can't duplicate file descriptor
Fri Jan 26 19:31:46 2018 -> Terminating because of a fatal error.
Fri Jan 26 19:31:46 2018 -> Pid file removed.
Fri Jan 26 19:31:46 2018 -> --- Stopped at Fri Jan 26 19:31:46 2018
Fri Jan 26 19:31:46 2018 -> Socket file removed.


If I restart clamd, then all's fine for a while.
However, this is my second crash, and the first one was Friday morning.

Freshclam is not complaining, and it keeps updating the db.

What should I be looking for?

I have clamav version:
pp-antivirus/clamav-0.99.2-r1::gentoo

So I tried to update it (app-antivirus/clamav-0.99.3-r1), but first I tried to update portage (I have sys-apps/portage-2.3.6::gentoo), as suggest by an "emerge --sync":

Code:
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

sys-apps/portage:0

  (sys-apps/portage-2.3.20:0/0::gentoo, ebuild scheduled for merge) pulled in by
    sys-apps/portage (Argument)

  (sys-apps/portage-2.3.6:0/0::gentoo, installed) pulled in by
    >=sys-apps/portage-2.3.0_rc[python_targets_python2_7(-),python_targets_python3_4(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (app-portage/repoman-2.3.1:0/0::gentoo, installed)
                                                                                                                                                                                                                                                                                                                   
    sys-apps/portage[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)] required by (app-portage/gentoolkit-0.3.3:0/0::gentoo, installed)
                                                                                                                                                                                                                                                                                                                                                             


It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously.  If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.


The following packages are causing rebuilds:

  (sys-libs/zlib-1.2.11-r1:0/1::gentoo, ebuild scheduled for merge) causes rebuilds for:
    (dev-db/mariadb-10.1.29:0/18::gentoo, ebuild scheduled for merge)
    (media-libs/tiff-4.0.8:0/0::gentoo, ebuild scheduled for merge)
    (dev-libs/libxml2-2.9.7:2/2::gentoo, ebuild scheduled for merge)
    (media-libs/libpng-1.6.29:0/16::gentoo, ebuild scheduled for merge)
    (media-libs/openjpeg-2.3.0:2/7::gentoo, ebuild scheduled for merge)
    (dev-lang/python-3.4.5-r1:3.4/3.4m::gentoo, ebuild scheduled for merge)
    (dev-lang/python-2.7.14-r1:2.7/2.7::gentoo, ebuild scheduled for merge)
    (net-misc/openssh-7.5_p1-r4:0/0::gentoo, ebuild scheduled for merge)
    (app-text/ghostscript-gpl-9.21:0/0::gentoo, ebuild scheduled for merge)
  (app-arch/bzip2-1.0.6-r8:0/1::gentoo, ebuild scheduled for merge) causes rebuilds for:
    (dev-lang/python-2.7.14-r1:2.7/2.7::gentoo, ebuild scheduled for merge)
    (dev-lang/python-3.4.5-r1:3.4/3.4m::gentoo, ebuild scheduled for merge)

The following keyword changes are necessary to proceed:
 (see "package.accept_keywords" in the portage(5) man page for more details)
# required by portage (argument)
=sys-apps/portage-2.3.20 ~amd64


What does this mean exactly, and what should I do next?
I never told Gentoo to install an "unstable" portage package, so why is it trying to do so?
Which other package requires portage 2.3.20?

So I'm not upgrading clamav yet.

In the meantime, here's the first occurrence of the clamav error messages:

Code:
Fri Jan 26 08:34:21 2018 -> SelfCheck: Database status OK.
Fri Jan 26 08:44:23 2018 -> SelfCheck: Database status OK.
Fri Jan 26 08:54:25 2018 -> SelfCheck: Database status OK.
Fri Jan 26 09:04:25 2018 -> SelfCheck: Database status OK.
Fri Jan 26 09:14:25 2018 -> SelfCheck: Database status OK.
Fri Jan 26 09:15:53 2018 -> instream(127.0.0.1@46048): Can't create new file ERROR
Fri Jan 26 09:15:53 2018 -> instream(127.0.0.1@46068): Can't create new file ERROR
Fri Jan 26 09:15:53 2018 -> instream(127.0.0.1@46088): Can't create new file ERROR
Fri Jan 26 09:15:53 2018 -> instream(127.0.0.1@46096): Can't create new file ERROR
Fri Jan 26 09:15:54 2018 -> instream(127.0.0.1@46108): Can't create new file ERROR
Fri Jan 26 09:15:54 2018 -> instream(127.0.0.1@46124): Can't create new file ERROR
Fri Jan 26 09:15:54 2018 -> instream(127.0.0.1@46128): Can't create new file ERROR
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:55 2018 -> instream(127.0.0.1@46194): Can't create new file ERROR
Fri Jan 26 09:15:56 2018 -> instream(127.0.0.1@46242): Can't create new file ERROR
Fri Jan 26 09:15:56 2018 -> instream(127.0.0.1@46390): Can't create new file ERROR
Fri Jan 26 09:15:56 2018 -> instream(127.0.0.1@46438): Can't create new file ERROR
Fri Jan 26 09:15:56 2018 -> instream(127.0.0.1@46458): Can't create new file ERROR
Fri Jan 26 09:15:56 2018 -> instream(127.0.0.1@46470): Can't create new file ERROR
Fri Jan 26 09:15:56 2018 -> instream(127.0.0.1@46496): Can't create new file ERROR
Fri Jan 26 09:15:56 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:56 2018 -> ERROR: accept() failed: �u�c
Fri Jan 26 09:15:56 2018 -> ERROR: accept() failed: �u�c


Any ideas?

Thanks,

Vieri
Back to top
View user's profile Send private message
fedeliallalinea
Administrator
Administrator


Joined: 08 Mar 2003
Posts: 30914
Location: here

PostPosted: Sat Jan 27, 2018 5:27 pm    Post subject: Re: clamd crash Reply with quote

Vieri wrote:
What does this mean exactly, and what should I do next?
I never told Gentoo to install an "unstable" portage package, so why is it trying to do so?
Which other package requires portage 2.3.20?

Why you want update to a keyworded portage? Latest stable version is 2.3.19-r1, try to update to it (I think you are in gentoo stable)
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
Vieri
l33t
l33t


Joined: 18 Dec 2005
Posts: 879

PostPosted: Sat Jan 27, 2018 5:37 pm    Post subject: Re: clamd crash Reply with quote

fedeliallalinea wrote:

Why you want update to a keyworded portage?


I don't. Take a look at this:

Code:
# grep -ri portage /etc/portage/*     
/etc/portage/bin/post_sync:for f in /etc/portage/postsync.d/* ; do
/etc/portage/make.conf:# Please consult /usr/share/portage/config/make.conf.example for a more
/etc/portage/make.conf:PORTDIR="/usr/portage"
/etc/portage/make.conf:PORTAGE_NICENESS=10
/etc/portage/make.conf:PORTAGE_BINHOST="http://inf-bl07/gentoo/binary-amd64"
/etc/portage/make.conf.catalyst:# Please consult /usr/share/portage/config/make.conf.example for a more
/etc/portage/make.conf.catalyst:PORTDIR="/usr/portage"
/etc/portage/postsync.d/q-reinitialize:[ -x /usr/bin/q ] && /usr/bin/q -r ${PORTAGE_QUIET:+-q}
/etc/portage/repo.postsync.d/example:# Example /etc/portage/repo.postsync.d script. Make it executable (chmod +x) for
/etc/portage/repo.postsync.d/example:# Portage to process it.
/etc/portage/repo.postsync.d/example:# With portage-2.2.16 and newer, all repo.postsync.d hooks will be called multiple
/etc/portage/repo.postsync.d/example:# Older versions of Portage support syncing only one repository.
/etc/portage/repo.postsync.d/example:# Portage assumes that a hook succeeded if it exits with 0 code. If no
/etc/portage/repos.conf/gentoo.conf:location = /usr/portage
/etc/portage/repos.conf/gentoo.conf:sync-uri = rsync://rsync.gentoo.org/gentoo-portage
/etc/portage/repos.conf/local.conf:location = /usr/local/portage


Gentoo portage tries to pull in an unstable portage version when I merely type "emerge --ask portage"....

I don't understand why.
Back to top
View user's profile Send private message
bunder
Bodhisattva
Bodhisattva


Joined: 10 Apr 2004
Posts: 5934

PostPosted: Sun Jan 28, 2018 5:04 am    Post subject: Reply with quote

what are the permissions on /var/lib/clamav ?
Back to top
View user's profile Send private message
fedeliallalinea
Administrator
Administrator


Joined: 08 Mar 2003
Posts: 30914
Location: here

PostPosted: Sun Jan 28, 2018 7:03 am    Post subject: Re: clamd crash Reply with quote

Vieri wrote:
Gentoo portage tries to pull in an unstable portage version when I merely type "emerge --ask portage"....

Try with command
Code:
# emerge -1 =sys-apps/portage-2.3.19-r1

_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
Vieri
l33t
l33t


Joined: 18 Dec 2005
Posts: 879

PostPosted: Sun Jan 28, 2018 9:01 am    Post subject: Reply with quote

bunder wrote:
what are the permissions on /var/lib/clamav ?

Code:

drwxr-xr-x  2 postfix  postfix

Code:
# grep User /etc/clamd.conf
User postfix
# grep Owner /etc/freshclam.conf
DatabaseOwner postfix


That's because I use a local socket for postfix/mimedefang communication with clamav:
Code:
# grep MIMEDefang /etc/clamd.conf
LocalSocket /var/spool/MIMEDefang/clamd.sock


However, I'd like to use clamd via tcp/ip from a c-icap module (TCPSocket 3310).

c-icap.conf does not define a "user", so it runs as the user who launched it, ie. "root".

Code:
# ps aux | grep c-icap
root     19494  0.0  0.0 152980  2356 ?        Sl   09:59   0:00 /usr/libexec/c-icap
root     19523  0.0  0.0 357752  4076 ?        S    09:59   0:00 /usr/libexec/c-icap
root     19604  0.0  0.0 152980  2356 ?        Sl   09:59   0:00 /usr/libexec/c-icap
root     19621  0.0  0.0 152980  2356 ?        Sl   09:59   0:00 /usr/libexec/c-icap
root     19685  0.0  0.0 152980  2356 ?        Sl   09:59   0:00 /usr/libexec/c-icap
root     19732  0.0  0.0 152980  2356 ?        Sl   09:59   0:00 /usr/libexec/c-icap
root     19785  0.0  0.0 152980  2356 ?        Sl   09:59   0:00 /usr/libexec/c-icap
root     19800  0.0  0.0 152980  2356 ?        Sl   09:59   0:00 /usr/libexec/c-icap
root     19824  0.0  0.0 152980  2356 ?        Sl   09:59   0:00 /usr/libexec/c-icap
root     19887  0.0  0.0 152980  2356 ?        Sl   09:59   0:00 /usr/libexec/c-icap
root     19910  0.0  0.0 152980  2356 ?        Sl   09:59   0:00 /usr/libexec/c-icap
root     26073  0.0  0.0  62824  4524 ?        Ss   Jan26   0:09 /usr/libexec/c-icap
Back to top
View user's profile Send private message
Vieri
l33t
l33t


Joined: 18 Dec 2005
Posts: 879

PostPosted: Sun Jan 28, 2018 9:04 am    Post subject: Re: clamd crash Reply with quote

fedeliallalinea wrote:

Try with command
Code:
# emerge -1 =sys-apps/portage-2.3.19-r1


So is this a possible bug in Gentoo portage?
I mean, there's no point in specifying the actual version I want by hand. I want "emerge --ask portage" to emerge the portage version for my system (ie. the latest "stable" version).
I guess I'll bring the issue up in bugs.gentoo.org.
Back to top
View user's profile Send private message
fedeliallalinea
Administrator
Administrator


Joined: 08 Mar 2003
Posts: 30914
Location: here

PostPosted: Sun Jan 28, 2018 9:24 am    Post subject: Re: clamd crash Reply with quote

Vieri wrote:
So is this a possible bug in Gentoo portage?.

I don't know, but I never see this problem before
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum