• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

New subdomain: psaadm cannot chown anymore

How stupid is that question?!

  • That happens to anyone! Well almost...

    Votes: 1 100.0%
  • Hmm, no worries. But it seams quite stupid.

    Votes: 0 0.0%
  • Oh dear, just another noob!

    Votes: 0 0.0%
  • Get yourself a gun!

    Votes: 0 0.0%

  • Total voters
    1
R

Rainer Koerner

Guest
Hey guys, sorry for that stupid question, but I do need some expert help.

Yesterday I missed a dot in a command:

chown root /* instead of chown root ./*

I stopped the command after 2 secs, however Plesk (8.2.1) gives me a couple of permission issues which I do not understand at all. For example when I try to add a new subdomain:

Internal Plesk error occurred: Unable to execute subdomainmng: subdomainmng: ERROR: Unable to chown /var/www/vhosts/mydomain.com/subdomains/test2: Operation not permitted System error 1: Operation not permitted subdomainmng: Unable to create directory '/var/www/vhosts/mydomain.com/subdomains/test2' System error 1: Operation not permitted

A folder test2 under vhosts/mydomain.com/subdomains is created with ownership of psaadm, however there are no more subfolders.

drwxr-xr-x 2 psaadm psaadm 4096 Apr 28 12:51 test2

So it looks like it brakes down when it tries to chown the new folder. How can that be? Did my misspelled command change anything elemental? Is there a way to restore Plesks ownerships? My biggest problem is that I do not really understand where Plesk has all its files flying around...

I do appreciate each help. Thanks guys!
 
Oh dear, I see what happened. My mispelled command deleted the setuid flag. I reset it on /opt/psa/admin/bin and sbin and here we go, it works again :). Thanks for storming my brain!
 
Back
Top