Current User: Guest Login Register
Please consider registering


Register? | Lost Your Password?

Search Forums:


 






Minimum search word length is 4 characters – Maximum search word length is 84 characters
Wildcard Usage:
*  matches any number of characters    %  matches exactly one character

clamAV won't start – error loading shared library: libpthread.so.0

Reply to Post Add a New Topic
UserPost

3:57 pm
November 28, 2010


Ginger

Member

posts 14

Hi All,

Installed clamav. Won't start:

# /sbin/service clamd start
Starting Clam AntiVirus Daemon: clamd: error while loading shared libraries: libpthread.so.0: cannot open shared object file: No such file or directory
                                                           [FAILED]

 

When I ask yum about libpthread, yum says it is installed:

yum provides libpthread.so.0

glibc-2.5-49.el5_5.7.i686 : The GNU libc libraries.
Repo        : installed
Matched from:
Other       : Provides-match: libpthread.so.0

 

Any ideas?

 

Thanks,

 

Ginger

1:16 am
November 29, 2010


Ginger

Member

posts 14

Hi All,

Everything is now working fairly well.

I have SELinux turned on, and would like to keep it on.

ClamAV only finds the library when I turn SELinux down to permissive.

What should I change to keep SELinux on, and allow ClamAV access to libpthread.so.0 ?

 

Any ideas?

 

Thanks,

Ginger

3:31 pm
December 2, 2010


Ginger

Member

posts 14

If anyone wants to run SELinux, then you will need to be "Creating Custom SELinux Policy Modules with audit2allow"

Brief overview of steps:

  1. Turn on SELinux (using system-config-securitylevel) and set it on 'Permissive'. 'Permissive' allows all prohibited actions to take place and logs them to /var/log/audit/audit.log
  2. Setup your entire email server setup and get it working. This will add entries to the audit.log
  3. Write your custom policies using grep and audit2allow to read audit.log 

You can find instructions on writing a SELinux policy here: http://wiki.centos.org/HowTos/SELinux

You might want to write different policies for postfixlocal, dovecotlocal, etc., or you might just want to write one policy for mailserverlocal

It is a relatively simple process to write a policy, once you realize that what you are doing is using audit2allow to read the audit.log and generate a policy.

My understanding of SELinux is that if you can get it working smoothly, it does make your system more secure. If you turn it off, it is less secure. Where is the official white paper from Red Hat that recommends turning off SELinux as an alternative that is just as secure as having it running? If it were just as secure to turn SELinux off, Red Hat would not bother to have it as part of their standard distribution…

 

Perhaps Consultant can write a tutorial that comes as a final step: "Creating Custom SELinux Policy Modules with audit2allow"

 

Ginger

Reply to Post

Reply to Topic:
clamAV won't start – error loading shared library: libpthread.so.0

Guest Name (Required):

Guest Email (Required):

Smileys
Confused Cool Cry Embarassed Frown Kiss Laugh Smile Surprised Wink Yell
Post New Reply

Guest URL (required)

Math Required!
What is the sum of:
4 + 12
   


About the Linux Mail Server Setup and Howto Guide Forum

Forum Timezone: America/New_York

Most Users Ever Online: 60

Currently Online:
11 Guests

Currently Browsing this Topic:
1 Guest

Forum Stats:

Groups: 2
Forums: 5
Topics: 343
Posts: 1062

Membership:

There are 966 Members
There have been 91 Guests

There is 1 Admin

Top Posters:

shanmugasundaram s – 46
Kendermin – 15
Ginger – 14
bighorn – 14
iron_michael86 – 12
Raminda – 11

Recent New Members: waveney, achal, niesul14, hesaum, sreevinodss, nasonov

Administrators: consultant (353 Posts)