clamav problem in apache error log

roeyy

Verified User
Joined
Nov 7, 2005
Messages
20
hi,

i have a linux apache 2.2.17 server with php 5.2.17
in the error log i see meny lines of :
cannot create mutex /var/tmp/clamav.lock

and when i reset my httpd this line also apper :
RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)

i have the new clamav installed

i did this to secure clients account with this :

Option that can be added to the directadmin.conf if you which to enable this feature:

secure_access_group=access

After enabling this, it applies to any newly created user.
To set it for existing users, run:
echo "action=rewrite&value=secure_access_group" >> /usr/local/directadmin/data/task.queue

What this feature does, is it creates a group called access (assuming you use this value). In this newly created group will be the users apache, nobody and mail. These 3 UID values will be granted permission into the users home directory by means of this access group set on /home/username for Users, and /home/username/domains for Admins and Resellers. The respective path will be set to chmod 710, thus preventing any other user on the system from looking in to that path. Note: If you're running clamd, you must also manually add the clamav user to this group.

the bold is the note that say something about clamav
how can i add it to the group like they say ?

it will solve my problem ?
 
and when i reset my httpd this line also apper :
RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
This is the only part of your post for which I'm responding; I have no experience with running clamav with apache.

This warning means that you've got a CA Certificate (an intermediate Certificate) installed as if it were a server certificate.

Jeff
 
Please do not double-post; I've merged your two threads into one.

Do you need any kind of a Certificate on your apache configuration? If not, then you need to find where it's installed, and just empty the file. That generally should work.

To find where it might be is a little trickier; you need to search for containers using port 443, and find Certificate entries. Start at httpd.conf and go through all included files.

If you can't figure it out you may need to hire someone to do it for you if it's important to get rid of the warning.

Jeff
 
ok . i think this is the place more then the ather forum.

i have few domains that have privet IP with SSL CERT from godaddy.

where should i clean the file ?
this action will not delete the support of SSL to the ather domains that use SSL ?
 
I don't know, because I don't know how it got there. If you don't have the system administration skills to look for it as I mentioned, then perhaps you'll need to hire an administrator to look for it.

I, and others, could do it, looged into your server. I charge for that; perhaps others do not.

(Offering commercial support for DirectAdmin is my core business.)

Jeff
 
Back
Top