1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

psa dead but subsys locked

Discussion in 'Plesk for Linux - 8.x and Older' started by verybad, Apr 4, 2006.

  1. verybad

    verybad Guest

    My business partner has been playing with the server and plesk cp does not start. All domains and email is working fine. We just cannot access the control panel vis :8443, we get a 404 error.

    oneandone our provider has looked into it and said....

    Plesk would fail to start due to Dr Web errors. We added a comment in the file located "psa". To view this file type;

    vi /etc/init.d/psa

    #service_after_psa="drwebd" <---- Put a # so the line gets ignored. If you remove the # plesk does not even start and complains about Dr Web Key

    The command is: /etc/init.d/psa start

    [root@server subsys]# /etc/init.d/psa start
    Starting named: named: already running [FAILED]
    Starting psa-spamassassin service: [ OK ]
    /usr/local/psa/admin/bin/httpsdctl start: httpd started
    Starting Plesk: [ OK ] <----- Plesk starts
    [root@server subsys]# /etc/init.d/psa status <----- Check the status
    psa dead but subsys locked <----- Locked?

    Reseach on the following: "psa dead but subsys locked" it seems to be a common subject.

    We unsure what to do next, can anyone help us?

    Thanks in advance.
  2. Philippe@

    Philippe@ Guest


    login ssh

    go to /var/lock/subsys

    rm psa

    /etc/init.d/psa restart


    /etc/init.d/psa stopall


    /etc/init.d/psa start
  3. NightMan

    NightMan Guest

    how did you solve this? I am having the same issue.