unable to open configuration file /etc/psa/psa.conf: Permission denied

[lazyd]

After the recent base update for plesk 9.2.3 i get this message in /var/log/messages:

Dec 18 22:05:03 www spam_hook[8961]: unable to open configuration file /etc/psa/psa.conf: Permission denied
Dec 18 22:05:03 www spam_hook[8951]: unable to open configuration file /etc/psa/psa.conf: Permission denied
Dec 18 22:05:03 www spam_hook[8979]: unable to open configuration file /etc/psa/psa.conf: Permission denied

this coincides with receiving the following spam email(s):

DomainKey-Status: bad format
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mydomain.com
X-Spam-Level: ********
X-Spam-Status: Yes, score=8.9 required=7.0 tests=EMPTY_MESSAGE,MISSING_DATE,
MISSING_HB_SEP,MISSING_HEADERS,MISSING_MID,MISSING _SUBJECT,NO_RELAYS,
TVD_SPACE_RATIO autolearn=no version=3.2.5
X-Spam-Report:
* 0.0 MISSING_MID Missing Message-Id: header
* 0.0 MISSING_DATE Missing Date: header
* -0.0 NO_RELAYS Informational: message was not relayed via SMTP
* 2.5 MISSING_HB_SEP Missing blank line between message header and body
* 1.6 MISSING_HEADERS Missing To: header
* 2.9 TVD_SPACE_RATIO BODY: TVD_SPACE_RATIO
* 1.3 MISSING_SUBJECT Missing Subject: header
* 0.6 EMPTY_MESSAGE Message appears to have no textual parts and no
* Subject: text
Received: (qmail 8991 invoked by alias); 18 Dec 2009 22:05:04 +0000
Delivered-To: postmaster@mydomain.com
Subject: ****SPAM****
X-Spam-Prev-Subject: (nonexistent)

 

[Nataliya Zagr]

Hello,

Please, check that you are having the similar permissions and owner for the /etc/psa/psa.conf:

# ls -la /etc/psa/psa.conf
-rw-r--r-- 1 root root 2461 Oct 21 08:02 /etc/psa/psa.conf

Thank you

 

[lazyd]

ls -la /etc/psa/psa.conf

-rw-r--r-- 1 root root 2564 Dec 15 14:31 /etc/psa/psa.conf

Dan

 

[Flachzange]

Today I noticed exactly the same message in my syslog after every spamassassin (spamd) check:

Dec 20 22:09:21 host spam_hook[20122]: unable to open configuration file /etc/psa/psa.conf: Permission denied

permissions seems to be ok:
-rw-r--r-- 1 root root 2474 2009-11-21 13:20 psa.conf

 

[Daniel Geist]

I'm having similar permissions and owner but suffer from the same problem since the last update

-rw-r--r-- 1 root root 2475 Nov 3 02:17 /etc/psa/psa.conf

 

[MeaC]

I have the same problem and the same owner/rights as listed above:
ls -la /etc/psa/psa.conf
-rw-r--r-- 1 root root 2567 2009-11-01 16:46 /etc/psa/psa.conf

Is there any solution or work-around?

 

[MeaC]

The Problem occured with installing the latest hotfix patch (9.2.3 hotfix ??).
The Installer/updater said "success" but the log shows several warnings:

-------------
Preparing to replace psa-imp 4.1.6-debian4.0.build92091009.18 (using .../psa-imp_4.1.6-debian4.0.build92091210.11_amd64.deb) ...
Unpacking replacement psa-imp ...
dpkg: warning - unable to delete old directory `/etc/psa/webmail/horde/conf.d': Directory not empty
dpkg: warning - unable to delete old directory `/etc/psa/webmail/horde/imp': Directory not empty
Preparing to replace psa-ingo 1.1.5-debian4.0.build92091009.18 (using .../psa-ingo_1.1.5-debian4.0.build92091210.11_amd64.deb) ...
Unpacking replacement psa-ingo ...
dpkg: warning - unable to delete old directory `/etc/psa/webmail/horde/ingo': Directory not empty
Preparing to replace psa-kronolith 2.1.8-debian4.0.build92091009.18 (using .../psa-kronolith_2.1.8-debian4.0.build92091210.11_amd64.deb) ...
Unpacking replacement psa-kronolith ...
dpkg: warning - unable to delete old directory `/etc/psa/webmail/horde/kronolith': Directory not empty
Preparing to replace psa-mimp 1.0.2-debian4.0.build92091009.18 (using .../psa-mimp_1.0.2-debian4.0.build92091210.11_amd64.deb) ...
Unpacking replacement psa-mimp ...
dpkg: warning - unable to delete old directory `/etc/psa/webmail/horde/mimp': Directory not empty
Preparing to replace psa-mnemo 2.1.2-debian4.0.build92091009.18 (using .../psa-mnemo_2.1.2-debian4.0.build92091210.11_amd64.deb) ...
Unpacking replacement psa-mnemo ...
dpkg: warning - unable to delete old directory `/etc/psa/webmail/horde/mnemo': Directory not empty
Preparing to replace psa-passwd 3.0.1-debian4.0.build92091009.18 (using .../psa-passwd_3.0.1-debian4.0.build92091210.11_amd64.deb) ...
Unpacking replacement psa-passwd ...
dpkg: warning - unable to delete old directory `/etc/psa/webmail/horde/passwd': Directory not empty
Preparing to replace psa-turba 2.1.7-debian4.0.build92091009.18 (using .../psa-turba_2.1.7-debian4.0.build92091210.11_amd64.deb) ...
Unpacking replacement psa-turba ...
dpkg: warning - unable to delete old directory `/etc/psa/webmail/horde/horde/registry.d': Directory not empty
dpkg: warning - unable to delete old directory `/etc/psa/webmail/horde/horde': Directory not empty
dpkg: warning - unable to delete old directory `/etc/psa/webmail/horde/turba': Directory not empty
dpkg: warning - unable to delete old directory `/etc/psa/webmail/horde': Directory not empty
Preparing to replace psa-updates 9.2.3-debian4.0.build92091009.18 (using .../psa-updates_9.2.3-debian4.0.build92091210.11_all.deb) ...
Unpacking replacement psa-updates ...
Setting up psa-horde (3.1.7-debian4.0.build92091210.11) ...
Trying to start service mysql... done
Trying to establish test connection... connected
done
Trying to generate random password for Horde Web Based mail client...
Setting up psa-hotfix3-9.2.3 (9.2.3-debian4.0.build92091210.11) ...
Trying to replace files and set up right permissions... cp: missing destination file operand after `/opt/psa/tmp/hotfix-92091210.11/'
Try `cp --help' for more information.
done
Unable to get options for atmail webmail

WARNING!
During the register found some problems(see log file: /tmp/psa-hotfix92091210.11.log)

Continue...


Setting up psa-imp (4.1.6-debian4.0.build92091210.11) ...
Trying to start service mysql... done
Trying to establish test connection... connected
done
Trying to restart service apache2... Forcing reload of web server (apache2)... waiting .
done

... and so on...
------------

 

[lazyd]

Tried to post this response yesterday but it has not been approved so thought I would post it again today:

The permissions for my psa.conf is as follows:

ls -la /etc/psa/psa.conf
-rw-r--r-- 1 root root 2564 Dec 15 14:31 /etc/psa/psa.conf

 

[Flachzange]

Even if my first post hast not been published....I probably found the reason:

Check the permissions of /etc/psa and set it to 755 if necessary. Mine was only 744

Regards,
Christoph

 

[lazyd]

Looking at most peoples posts it seems that they have their psa.conf file set to -rw-r--r--

I think this is the same as 644 so are you sure that you should change the permissions on this file to 755 or even 744?

D

 

[Flachzange]

No, I didn't mean the permissions of the file, but rather the one of the directory which contains the file. Here you need 755.

 

[lazyd]

Ok the permissions on this folder are currently as follows:

drwxr-x--- 5 psaadm psaadm 4096 Dec 18 23:25 psa

Which I guess is the same as 750

So to confirm, Is it a good idea to change the permissions on this folder and does it matter if the owner/group is different to the file I am having problems with? i.e.

Dec 18 22:05:03 www spam_hook[8961]: unable to open configuration file /etc/psa/psa.conf: Permission denied

-rw-r--r-- 1 root root 2564 Dec 15 14:31 /etc/psa/psa.conf

 

[mfichtner]

Same problem here:

Dec 31 07:43:36 cgn8 spam_hook[11439]: unable to open configuration file /etc/psa/psa.conf: Permission denied
Dec 31 09:01:51 cgn8 spam_hook[27928]: unable to open configuration file /etc/psa/psa.conf: Permission denied
Dec 31 09:50:54 cgn8 spam_hook[22434]: unable to open configuration file /etc/psa/psa.conf: Permission denied
Dec 31 10:00:14 cgn8 spam_hook[28549]: unable to open configuration file /etc/psa/psa.conf: Permission denied
Dec 31 10:37:32 cgn8 spam_hook[17716]: unable to open configuration file /etc/psa/psa.conf: Permission denied

And this is not just a cosmetic issue. It seems to prevent the server from deleting spam automatically.

It's absolutely amazing how Parallels manages to introduce new, highly annoying bugs with every single release. Don't you guys ever do any regression testing?!

 

[mfichtner]

No, I didn't mean the permissions of the file, but rather the one of the directory which contains the file. Here you need 755.

Thanks, Flachzange. Changing directory permissions does indeed seem to fix the problem.

 

[lazyd]

Okay,

I have changed the permissions on the /etc/psa to 755:

drwxr-xr-x 5 psaadm psaadm 4096 Dec 18 23:25 psa


Will see if this solves the problem.

D.

 

[lazyd]

change permissions

Just checked and it seems that the error message 'unable to open configuration file /etc/psa/psa.conf: Permission denied' has gone. Still getting emails though. Look like this:

DomainKey-Status: bad format
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on www.mydomain.com
X-Spam-Level: ********
X-Spam-Status: Yes, score=8.9 required=7.0 tests=EMPTY_MESSAGE,MISSING_DATE,
MISSING_HB_SEP,MISSING_HEADERS,MISSING_MID,MISSING_SUBJECT,NO_RELAYS,
TVD_SPACE_RATIO autolearn=no version=3.2.5
X-Spam-Report:
* 0.0 MISSING_MID Missing Message-Id: header
* 0.0 MISSING_DATE Missing Date: header
* -0.0 NO_RELAYS Informational: message was not relayed via SMTP
* 2.5 MISSING_HB_SEP Missing blank line between message header and body
* 1.6 MISSING_HEADERS Missing To: header
* 2.9 TVD_SPACE_RATIO BODY: TVD_SPACE_RATIO
* 1.3 MISSING_SUBJECT Missing Subject: header
* 0.6 EMPTY_MESSAGE Message appears to have no textual parts and no
* Subject: text
Received: (qmail 941 invoked by alias); 8 Jan 2010 08:25:02 +0000
Delivered-To: postmaster@mydomain.com
Subject: *****SPAM*****
X-Spam-Prev-Subject: (nonexistent)

 

[2danis2do]

blank emails

I have managed to track down the problem of receiving blank emails to a cron that is run on my sites. Also the other blank emails seem to coincide with when logrotate is run.

Would be great if anyone has an idea why this is happening.

 

[akxak]

Here, I found that 9.3.0 seems to created erronous entries in

/var/qmail/control

me
locals
rcpthost

by removing the top-level-domain part from the main system domain.

It caused 17000 mails as you got until I found the reason and all its occurances.

 

[2danis2do]

Please explain. I am not sure I understand "by removing the top-level-domain part from the main system domain."

D

 

[akxak]

The files mentioned contained (partly among others) the main system domain, like test.de

After the update, the <.de> was vanished and only the second level part <test> remained causing several malfunctions.