- Plesk for Linux
- Plesk for Windows
Unable to open the Updates and Upgrades page or start Plesk Installer in a command-line interface, when another Plesk Installer process is running on a server:
# ps aux | grep install | grep -v grep
root 11451 1.7 0.7 193396 14764 ? S 15:35 0:00 /usr/local/psa/admin/bin/autoinstaller --service-mode --enable-xml-output --ssl-cert /usr/local/psa/admin/conf/httpsd.pem --branch release,stable --web-interface --with-ssl --disable-browser
On Windows Server this can be check using two ways:
In a command prompt with the command:
C:\> wmic process where "caption like '%installer%'" get processId,caption
In Task Manager:
When clicking on Updates and Upgrades in Plesk, the page prompts for a root password or does not open at all with one of the following error messages in a web-browser:
PLESK_INFO: The connection has timed out
PLESK_INFO: Can't connect to backend: No such file or directory
PLESK_INFO: This webpage is not available.
When starting Plesk Installer in a command-line interface, the following message is shown:
CONFIG_TEXT: BUSY: Update operation was locked by another update process.
The following error message may appear in
/var/log/plesk/install/autoinstaller3.log, on Windows Server:
CONFIG_TEXT: Error: Can't start build-in web-server.
Only one instance of Plesk Installer can be launched at a time.
Previously started Plesk Web Installer process (Tools & Settings > Updates and Upgrades) is still running on the server.
By design, if Plesk Web Installer was opened in a web-browser and then closed, its process will still be active in a background and then terminated automatically after 30 minutes of inactivity.
Previously started Plesk Installer process hanged for some reason and could not be terminated automatically.
Another Plesk administrator is using Plesk Installer.
Terminate active Plesk Installer processes to start Plesk Installer.
Note: Before applying the solution below, make sure that other users on the Plesk server are not using Plesk Installer.