Issue Access in Plesk not possible - /usr/local/psa/admin/bin/proftpd_control_adapter: Permission denied

[Alexander Liebrecht]

Hello Community and Developers,
on time for Christmas first server problems. I have Centos 7.4, MariaDB 10.2 and Plesk Onyx 17.

Unfortunately, I can not log in to Plesk anymore after changing the FTP password or something else.

Now these hints are shown to me in the frontend.

Unable to read components configuration from the service node: sh: /usr/local/psa/admin/bin/proftpd_control_adapter: Permission denied
Message    Unable to read components configuration from the service node: sh: /usr/local/psa/admin/bin/proftpd_control_adapter: Permission denied
File    Proftpd.php
Line    241
Type    Service_Agent_Exception

It seems the false permissions are set, though I'm sure they're correct.

What outputs do you need to help me?

Thanks in Advance.

 

[IgorG]

Please make sure that you have the same permissions here

# stat /usr/local/psa/admin/sbin/wrapper
File: ‘/usr/local/psa/admin/sbin/wrapper’
Size: 23056 Blocks: 48 IO Block: 4096 regular file
Device: 61h/97d Inode: 109329022 Links: 1
Access: (4110/---s--x---) Uid: ( 0/ root) Gid: ( 1000/ psaadm)

 

[Alexander Liebrecht]

Hi Igor,

Thanks for the Hints and i have this:

stat /usr/local/psa/admin/sbin/wrapper
File: ‘/usr/local/psa/admin/sbin/wrapper’
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: 902h/2306d Inode: 36573951 Links: 1
Access: (4510/-r-s--x---) Uid: ( 0/ root) Gid: ( 1000/ psaadm)
Access: 2017-12-26 13:20:01.009368781 +0100
Modify: 2017-12-25 10:41:37.902242732 +0100
Change: 2017-12-25 13:19:23.202820566 +0100
Birth: -

Is this correct?

Thanks!

 

[IgorG]

Is this correct?

No. You have 4510/-r-s--x--- instead of correct 4110/---s--x--- permission. Fix it with

# chmod 4110 /usr/local/psa/admin/sbin/wrapper

Additionally you have 0 size of this file.
For fixing this issue I suggest you reintstall plesk-service-node-utilities package which contains this file.

 

[Alexander Liebrecht]

Thank you! OK, I just set chmod 4110.

With which SSH commands I can recreate or create the components lists.

It's the file "wrapper" and it's empty. Plesk Upgrade does not work because the Components List can not be retrieved or is empty.


The Plesk update states that the Components List is "empty". I do not know what happens to me all of a sudden.

And unfortunately I still have no permissions on /usr/local/psa/admin/bin/proftpd_control_adapter

Can I still do something else?

Thanks in Advance.

 

[IgorG]

Download this package and install it with

# wget http://autoinstall.plesk.com/PSA_17...ies-17.5.3-cos7.build1705170317.16.x86_64.rpm
# rpm -ivh --force plesk-service-node-utilities-17.5.3-cos7.build1705170317.16.x86_64.rpm

After that check wrapper:

# ll /usr/local/psa/admin/sbin/wrapper
---s--x--- 1 root psaadm 23056 Mar 17 2017 /usr/local/psa/admin/sbin/wrapper

Size shouldn't be 0 and permissions should be correct.

 

[Alexander Liebrecht]

Thanks, you helped me a lot this time, too.

Yes, it was because of the wrapper file and because it was empty.

But now I was able to log into Plesk and make updates.

Unfortunately, updates of the extensions do not work.

For example, I get this error.

ERR [panel] Execution installer has failed with exit code 1, stdout:, stderr: fork/exec /usr/local/psa/admin/sbin/repository: permission denied

What permissions does the / repostory directory have or is it a file?

Thanks in Advance.

 

[IgorG]

Check this file first. It should be:

# ll /usr/local/psa/admin/sbin/repository
-rwxr-x--- 1 root root 223 Mar 17 2017 /usr/local/psa/admin/sbin/repository

And I would suggest you try to fix it with

# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
# plesk repair installation

 

[Alexander Liebrecht]

Thanks for all this.

I was able to get my Plesk working again.

Is that normal that I can only reach the Backup Manager globally? Unfortunately, when I'm back on a domain in Plesk, I can not reach the backup manager for that domain.

But I can do it globally under Tools. Previously, I was able to reach the Backup Manager at every single domain in the backend.

Hm ... very strange!