• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.

Unable to Delete User / Domain Regardless of User

KrazyBob

Regular Pleskian
Upgrading to Plesk 11 and VZ 4 I am unable to first delete a web vault application on the old server. Next I tried to delete a user and that failed. So next I tried to delete the domain and it failed. Next I tried to delete the user and it failed. The Working icon just spins and nothing happens.

Help! LOL.
 
I've had that problem before as well, what I had to do was go into the shell and look for any psa running process and then kill it.

something like
ps aux | grep psa

And then to kill them all programatically
kill -9 `ps aux | grep psa | grep -v grep | awk '{print $2}'`

Then restart psa service since you killed them all

service psa startall
service psa start

Then try again. Sometimes processes get stuck and never complete because they are waiting for previous operations to complete.
 
I've had that problem before as well, what I had to do was go into the shell and look for any psa running process and then kill it.

something like
ps aux | grep psa

And then to kill them all programatically
kill -9 `ps aux | grep psa | grep -v grep | awk '{print $2}'`

Then restart psa service since you killed them all

service psa startall
service psa start

Then try again. Sometimes processes get stuck and never complete because they are waiting for previous operations to complete.

I will try this approach, although I have rebooted the container numerous time. But as I said I will try it your way and maybe learn something at the same time.
 
Code:
[root@server103 ~]# ps auxf | grep psa
root     10057  0.0  0.2  24220  8844 ?        Ss   Mar26   0:17 /usr/local/psa/admin/bin/php /usr/local/psa/admin/bin/modules/watchdog/wdcollect -c /usr/local/psa/etc/modules/watchdog/wdcollect.inc.php
root     10071  0.0  0.0  36352  2748 ?        Ssl  Mar26   8:59 /usr/local/psa/admin/bin/modules/watchdog/monit -Ic /usr/local/psa/etc/modules/watchdog/monitrc
root     19995  0.0  0.2  44112  7432 ?        Ss   Mar27   0:03 /usr/local/psa/admin/bin/httpsd
psaadm    4034  0.1  0.7  52368 27944 ?        S    Apr08   2:06  \_ /usr/local/psa/admin/bin/httpsd
psaadm   21890  0.1  0.5  47764 18352 ?        S    15:31   0:27  \_ /usr/local/psa/admin/bin/httpsd
root     19671  0.0  0.0   6776  1356 ?        S    Apr07   0:21  \_ /usr/local/psa/admin/sbin/pipelog
root     32179  0.0  0.0   5856   812 ?        S    Mar27   0:03 /usr/lib/courier-imap/couriertcpd -address=0 -stderrlogger=/usr/sbin/courierlogger -stderrloggername=imapd -maxprocs=160 -maxperip=80 -pid=/var/run/imapd.pid -nodnslookup -noidentlookup 143 /usr/sbin/imaplogin /usr/lib/courier-imap/authlib/authpsa /usr/bin/imapd Maildir
root     32189  0.0  0.0   5852   808 ?        S    Mar27   0:01 /usr/lib/courier-imap/couriertcpd -address=0 -stderrlogger=/usr/sbin/courierlogger -stderrloggername=imapd-ssl -maxprocs=160 -maxperip=80 -pid=/var/run/imapd-ssl.pid -nodnslookup -noidentlookup 993 /usr/bin/couriertls -server -tcpd /usr/sbin/imaplogin /usr/lib/courier-imap/authlib/authpsa /usr/bin/imapd Maildir
root     13574  0.0  0.0   4884  1904 ?        S    15:01   0:00  \_ /usr/bin/couriertls -server -tcpd /usr/sbin/imaplogin /usr/lib/courier-imap/authlib/authpsa /usr/bin/imapd Maildir
root     20061  0.0  0.0   4884  1900 ?        S    20:13   0:00  \_ /usr/bin/couriertls -server -tcpd /usr/sbin/imaplogin /usr/lib/courier-imap/authlib/authpsa /usr/bin/imapd Maildir
root     23566  0.0  0.0   4876  1888 ?        S    20:24   0:00  \_ /usr/bin/couriertls -server -tcpd /usr/sbin/imaplogin /usr/lib/courier-imap/authlib/authpsa /usr/bin/imapd Maildir
root     23629  0.0  0.0   4876  1900 ?        S    20:25   0:00  \_ /usr/bin/couriertls -server -tcpd /usr/sbin/imaplogin /usr/lib/courier-imap/authlib/authpsa /usr/bin/imapd Maildir
root     24241  0.0  0.0   4876  1900 ?        S    20:30   0:00  \_ /usr/bin/couriertls -server -tcpd /usr/sbin/imaplogin /usr/lib/courier-imap/authlib/authpsa /usr/bin/imapd Maildir
root     32198  0.0  0.0   5856   812 ?        S    Mar27   1:27 /usr/lib/courier-imap/couriertcpd -address=0 -stderrlogger=/usr/sbin/courierlogger -stderrloggername=pop3d -maxprocs=40 -maxperip=4 -pid=/var/run/pop3d.pid -nodnslookup -noidentlookup 110 /usr/sbin/pop3login /usr/lib/courier-imap/authlib/authpsa /usr/bin/pop3d Maildir
root     32207  0.0  0.0   5856   812 ?        S    Mar27   0:20 /usr/lib/courier-imap/couriertcpd -address=0 -stderrlogger=/usr/sbin/courierlogger -stderrloggername=pop3d-ssl -maxprocs=40 -maxperip=4 -pid=/var/run/pop3d-ssl.pid -nodnslookup -noidentlookup 995 /usr/bin/couriertls -server -tcpd /usr/sbin/pop3login /usr/lib/courier-imap/authlib/authpsa /usr/bin/pop3d Maildir
root      7726  0.0  0.1  33992  6948 ?        S    Mar29   0:00 /usr/bin/python2.4 /usr/local/psa/admin/sbin/agent_runner /var/lib/psa/dumps/tmp/2013-03-29-12.20.41.477339
root      9872  0.0  0.1  32964  6928 ?        S    Mar29   0:00 /usr/bin/python2.4 /usr/local/psa/admin/sbin/agent_runner /var/lib/psa/dumps/tmp/2013-03-29-12.27.22.954833

That's not going to work.
 
Not sure I understand, why is it not going to work? You are going to kill off everything PSA is doing, and then restart any services so they would be running.
 
Not sure I understand, why is it not going to work? You are going to kill off everything PSA is doing, and then restart any services so they would be running.

Perhaps I've missed something. How is this any different than restarting the virtuozzo container and thus all PSA's running?
 
In your world it wouldnt be, it would have the same ultimate effect. In my world killing only what you want is way better than killing off everything by a reboot :)
 
Back
Top