Atomicorp

All,

I updated my FC6 server to Fedora 7 (clean install). I then got plesk 8.3 and got it all going. Did the updates and made a local.pp selinux policy.

I got these errors I just can't figure out:


Last login: Sat Dec 29 20:06:26 2007 from 10.0.0.1
[root@server ~]# grep avc /var/log/audit/audit.log | audit2allow -M local
******************** IMPORTANT ***********************
To make this policy package active, execute:

semodule -i local.pp

[root@server ~]# semodule -i local.pp
/etc/selinux/targeted/contexts/files/file_contexts: Multiple different specifications for /var/qmail/queue(/.*)? (system_u:object_r:qmail_spool_t:s0 and system_u:object_r:mail_spool_t:s0).
/etc/selinux/targeted/contexts/files/file_contexts: Multiple different specifications for /var/qmail/control(/.*)? (system_u:object_r:qmail_etc_t:s0 and system_u:object_r:etc_mail_t:s0).
[root@server ~]#

I cant fugure out why its complaining about multiple specs for qmail any ideas how to fix it?

I have seen this on multiple Plesk servers, but we don't use SELinux. Have you checked the file mentioned in the error message? Apparently there are multiple specifications for /var/qmail/control(/.*)? in there.

Hi Breun,

Well there are indeed two sets But I dont have another plesk server to know what is right. Can you tell me what are the correct selinux permissions for /var/qmail/control

I will post yet ANOTHER swsoft bug I found in plesk 8.3 on a clean install.

Pathetic

On a new install try clicking one of your domains to look at logs, you get a horrible:

0: /usr/local/psa/admin/plib/common_func.php3:158
psaerror(string 'LogFilesList->init() failed: filemng failed: filemng: stat failed: Permission denied System error 13: Permission denied')
1: /usr/local/psa/admin/htdocs/domains/logs/log_files.php:122


Hey anyone done a new install to Plesk 8.3 your in for some grief if you want to look at your domains logs.

However I found the fix, they set the wrong permissions inside every single domain in /var/www/vhosts.

The fix inside every single domain in your /var/www/vhosts/domain.name find the directory /statistics

Its been set a foolish 550 chmod, you need to change this to 755

But we are not done, go into your /statistics and find logs

This has been set a foolish 750, preventing Plesk from reading the logs. For this dir I chose a -R and set everything inside logs to 755 and the subdir logs as well.

Meantime can someone please tell me the correct selinux details for /var/qmail/control

You would think with so long between any updates they could atleast get it better

We don't use SELinux, so I have no idea which specification is the right one. Report it to SWsoft, maybe they have an idea?

My statistics dirs are set to 550 and logs dirs are 750 and I have no problems. What is 'foolish' about those modes? Are you sure the problem isn't owner and group? For both dirs the owner should be root and the group should be psaserv. We run CentOS instead of Fedora, but that shouldn't really matter in this case.

I played around and rebuilt all the selinux permissions it fixed that.

I found a post about the issue with plesk 8.3 and the logs. I was logged in as admin and when I went to any domain and hit logs in the panel I got a rude:

0: /usr/local/psa/admin/plib/common_func.php3:158
psaerror(string 'LogFilesList->init() failed: filemng failed: filemng: stat failed: Permission denied System error 13: Permission denied')
1: /usr/local/psa/admin/htdocs/domains/logs/log_files.php:122

I found others who upgraded plesk 8.21 to 8.3 do not have the issue and the chmods are set to 755

The owner and group are correct:

drwxr-xr-x 7 root psaserv 4096 2007-12-30 01:35 statistics
and
drwxr-xr-x 2 root psaserv 4096 2007-12-29 04:30 logs

As far as Fedora 7 goes is setting the wrong chmods. As soon as I reset the chmods on one domain the error went away and I could access the logs.

I give up with swsoft. You have to have support to get a bug looked, seems wrong to me. If its my fault then bill me else dont ask me to pay you to fix the bug.

I argued once and they agreed the watchdog is faulty, it does not work with later spamassassins. Well it was promised to be fixed and its STILL broken.