• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Plesk Update Fails

Catia

Basic Pleskian
I got a message that Plesk update failed. I looked through the log file and found several lines that said:
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem

So I ran 'dpkg --configure -a

I get this:
Processing triggers for ureadahead (0.100.0-19) ...
Setting up python3-libapparmor (2.10.95-0ubuntu2.6) ...
Setting up apparmor (2.10.95-0ubuntu2.6) ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults

then it hangs.

Tried running apt-get install -f

I get this:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up apparmor (2.10.95-0ubuntu2.6) ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults

then it hangs.

Can anybody point me in the right direction?
Thanks!
 
Could it be an option for you to remove apparmor, then do the upgrade, then reinstall apparmor?
 
i can confirm im getting the same issues. removing apparmor did not work. Its causing some sort of kernal bug , i fix was supposed to be released but this has had the knock on affect of killing one of my customers sites. im kind of stuck?
 
There are some good, knowledgeable Debian/Ubuntu experts on this forum. If you provide more details in your thread, e.g. exact commands + logs, many times issues like the one described can be solved by them. However, solving this issue with the information provided so far would be magic.
 
Hi Catia and JohnnyType2,

pls. DON'T remove apparmor from your system, just consider to use:

Code:
# /etc/init.d/apparmor stop
# /etc/init.d/apparmor teardown
# update-rc.d -f apparmor remove

Nothing more.

Some Plesk components need apparmor and will try to re-install apparmor with the default configuration, adding only the Plesk component specific additional modifications, which might conflict with several services on your server.

Afterwards, pls make sure to run again "dpkg --configure -a" or/and "apt-get install -f", followed by "aptitude upgrade".
If you experience further issues, pls. try to follow @Peter Debik 's suggestion, to include MORE informations from your command line, logs and used commands.
 
Hi Catia and JohnnyType2,

pls. DON'T remove apparmor from your system, just consider to use:

Code:
# /etc/init.d/apparmor stop
# /etc/init.d/apparmor teardown
# update-rc.d -f apparmor remove

Nothing more.

Some Plesk components need apparmor and will try to re-install apparmor with the default configuration, adding only the Plesk component specific additional modifications, which might conflict with several services on your server.

Afterwards, pls make sure to run again "dpkg --configure -a" or/and "apt-get install -f", followed by "aptitude upgrade".
If you experience further issues, pls. try to follow @Peter Debik 's suggestion, to include MORE informations from your command line, logs and used commands.

everything seemed to work except the last commmand aptitude upgrade

# dpkg --configure -a

Setting up apparmor (2.10.95-0ubuntu2.6) ...

update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults

Setting up python3-apparmor (2.10.95-0ubuntu2.6) ...

Setting up apparmor-profiles (2.10.95-0ubuntu2.6) ...

Setting up dh-apparmor (2.10.95-0ubuntu2.6) ...

Processing triggers for systemd (229-4ubuntu16) ...

Setting up apparmor-utils (2.10.95-0ubuntu2.6) ...

# apt-get install -f

Reading package lists... Done

Building dependency tree

Reading state information... Done

0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.

# aptitude upgrade

-bash: aptitude: command not found



 
Hi JohnnyType2,

# aptitude upgrade

-bash: aptitude: command not found
Well, if you don't have APTITUDE installed on your server, you are not able to use the command "aptitude" ( and the advantages, instead of using "apt-get" or "dpkg". ;) )
Consider to INSTALL aptitude with the example command:

apt-get install aptitude aptitude-common


my issue is now apparmor wont update via the plesk panel?.
No! Why do you think this way? You only DISABLED apparmor and didn't remove the package! ;)
 
Thanks everyone. I finally gave up and called my ISP who put in a ticket to Plesk. They fixed the problem for me. Easy way out, I know, but there was much less cursing this way. ;)
 
i want to fix the package and update, this kernal fault caused a site to break telling me i need to replace apache config....

ive never had anything but trouble from plesk installations. i dont know why i thought this would be any different sheesh,

so installed and upgraded aptitude as you suggested and the result is.

# current status : 0 (-9) upgradable
 
plesk now showing the error from the panel

Internal error ;-P
ERROR: Zend_Db_Adapter_Exception: SQLSTATE[HY000] [2006] MySQL server has gone away (Abstract.php:144)<br />
<br><a href='Help Center' target='_blank'>Search for related Knowledge Base articles</a>

and this via email
Reason: 2017-04-03 06:25:22 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2017-04-03 06:25:22 ERROR: Previous Plesk installer call finished unsuccessfully. PUM will not perform any update operations until Plesk installation is fixed.
2017-04-03 06:25:22 ERROR: Exited with returncode 50.

Ok so after following your instructions all my sites are down due to a MySQL error any idea how i can fix this please?

plesk is stuck in a repair and nothing happening and now i have no access to plesk panel..

all sites now broken the error on trying to access the plesk panel is now...

ERROR: Zend_Db_Adapter_Exception: SQLSTATE[HY000] [2002] No such file or directory

Additionally, an exception has occurred while trying to report this error: Zend_Exception
No entry is registered for key &#039;translate&#039; (Abstract.php:144)
 
Last edited:
Ok so MYSQL is broken and cant get it going. thus plesk is broke and im now having to pay my host to fix this.

thanks for the instruction.... (sarcasm)

i dont know why i was stupid enough not to take a snapshot. The host has tried to get MySQL running but with no luck. I dont know what aptitude did but its made a real mess.

I HATE PLESK!

My host also told me there was absolutely no need to install aptitude and that apparmor and some plesk modules are not compatible anyway.
 
Last edited:
The Same problem occurs here at my side. 2 servers; both installed same way, Ubuntu 16.04 LTS and Plesk Onyx. All was running well until last week Tuesday. After the normal routine automatically update (OS & Plesk) server hung and was down. Got the same failure messages and investigated for a bunch of hours since then, also contacted the Server hoster (STRATO AG) but the folks aren't helpful because of blah blah blah root server. They pointed me to find answers on the web. LOL, good advise, because this morning I found this forum here that some people have the same problem! I was aware that I couldn't be the only idiot on this planet.

Disabled the automatic updates all until this problem is fixed. It seems that one of the updates is corrupt, in the server log was found:

[42266.178894] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:2:4618]

I also ran the automatic repair of Plesk; it didn't show up any problem with all and said OK - all green.

It seems that this is a serious issue what couldn't be solved with trial & error. Have also contacted specialists in Linux OS.

I don't hate Plesk at all, but at the moment I don't like it really well. ;)

So, would be nice if you will post probably the problem solution and what your host provider found out. This thread here is the first I found in general on the web since nearly a week around that problem!

Ok so MYSQL is broken and cant get it going. thus plesk is broke and im now having to pay my host to fix this.

thanks for the instruction.... (sarcasm)

i dont know why i was stupid enough not to take a snapshot. The host has tried to get MySQL running but with no luck. I dont know what aptitude did but its made a real mess.

I HATE PLESK!

Ok so MYSQL is broken and cant get it going. thus plesk is broke and im now having to pay my host to fix this.

thanks for the instruction.... (sarcasm)

i dont know why i was stupid enough not to take a snapshot. The host has tried to get MySQL running but with no luck. I dont know what aptitude did but its made a real mess.

I HATE PLESK!

My host also told me there was absolutely no need to install aptitude and that apparmor and some plesk modules are not compatible anyway.
 
im not glad your having the same issues but im glad im not the only one... so this is not an isolated issue.

let me qualify the hate part. that i had a previous installation of plesk 9.5 that could not be updated as it was corrupt, may i point out corrupt from the start. I let it ride becasue i had several large websites on there, until it came to the point there was so much spam activity i had to move to onyx and it took the hosting company about 3 weeks in total to get it back up and running. so as you can tell im throughly fed up with plesk.

the updates not working did not break plesk or the websites but installing aptitude by following the instructions above have broken MySQL and it wont restart. i don't have access to the console as my host is working on it for a fee...


it looks like my only solution will be to recover the daily plesk backups of my sites individually and recover them to a new server according to my host (at a cost of 190 euro)

i dont understand why plesk would release updates that cause errors like this.
 
Last edited:
Igor, thanks for the notice about directly Plesk support. You are right with this option. We (as an example) rented dedicated servers by our hoster, root servers. Hoster says: we can't give support, because you have root servers, sorry. I tried to get an answer from them in any help, but I did receive only "The web investigation found out ..." LOL. They had more than 30.000 servers in total but directed us to the internet.

Right this morning, I found this forum here what still is excellent! Found others in the last weeks, but like it is always "all could be or not". This forum here seems administrated well to avoid kiddies and other funny things. So, I did try to point out the problem to the hoster first (like it is described on the "get direct access to PLESK") and failed to receive a "how to do" answer. I thought that we aren't the only idiots on this planet who do have that problem. But it seems "fire in sales, forget the rest". Will contact directly the Plesk support, fees what the guys want to have are more as moderate, and it will stop probably the wasted time to find any qualified way on the web to solve this problem. There are always solutions.



I think that an urgent appeal to the Plesk technical support team would cost you less - How to get support directly from Plesk?
 
Igor, thanks for the notice about directly Plesk support. You are right with this option. We (as an example) rented dedicated servers by our hoster, root servers. Hoster says: we can't give support, because you have root servers, sorry. I tried to get an answer from them in any help, but I did receive only "The web investigation found out ..." LOL. They had more than 30.000 servers in total but directed us to the internet.

Right this morning, I found this forum here what still is excellent! Found others in the last weeks, but like it is always "all could be or not". This forum here seems administrated well to avoid kiddies and other funny things. So, I did try to point out the problem to the hoster first (like it is described on the "get direct access to PLESK") and failed to receive a "how to do" answer. I thought that we aren't the only idiots on this planet who do have that problem. But it seems "fire in sales, forget the rest". Will contact directly the Plesk support, fees what the guys want to have are more as moderate, and it will stop probably the wasted time to find any qualified way on the web to solve this problem. There are always solutions.

we pay £10 a month for a plesk licence this includes support from your ISP who is suppose to have trained employees to deal with plesk issues.

Igor, i've tried to follow the instructions to raise a ticket to get direct plesk support but i'm struggling. All these issues are making me feel like an idiot.
 
We ordered new servers in February 2013 with Plesk 12. All run well up to April 2014. Huge websites are running, not small ones with a lot of client traffic, etc. Problems also occur with the updates, not possible. Tried to find a way, no way ahead. So I said, "I will run them as they are". I prayed to whomever that not an energy failure will cut the server from the power grid. ;)
One server was up (the one with most priority) for 1,058 days. We survived the Heartbleed issue and other attacks. But updates on this server could only be done with a massive workflow. This year we decided to have new ones, so we ordered. Two servers new, two servers old. All went well, also with data migration from one to the other server ( an excellent tool from Plesk). After migration was performed entirely, I rebooted the server what was up for 1,058 days, and exactly it happens: server down, no chance to start it. GOSH! The luck was on our side.
We were also not playing around with servers because we do need them for business and not for private gaming or what else ever. I thought: excellent, seems all perfect. Fewer stress times ahead in regards of server admin. New servers running well, Plesk Onyx seems working well, Ubuntu (before we used Suse) run very well. Until last week Tuesday in the mid of the night there was an ambush, what was not on the radar screen! ;)
In 15 years of server admin workflow I learned one: Never touch a running system, and when you touch it, no "trial and error" attempts, it could be worse even than before. And I do know stress what comes up with such issues very well! Sleepless nights, losing hairs and other body parts! :)
im not glad your having the same issues but im glad im not the only one... so this is not an isolated issue.

let me qualify the hate part. that i had a previous installation of plesk 9.5 that could not be updated as it was corrupt, may i point out corrupt from the start. I let it ride becasue i had several large websites on there, until it came to the point there was so much spam activity i had to move to onyx and it took the hosting company about 3 weeks in total to get it back up and running. so as you can tell im throughly fed up with plesk.

the updates not working did not break plesk or the websites but installing aptitude by following the instructions above have broken MySQL and it wont restart. i don't have access to the console as my host is working on it for a fee...


it looks like my only solution will be to recover the daily plesk backups of my sites individually and recover them to a new server according to my host (at a cost of 190 euro)

i dont understand why plesk would release updates that cause errors like this.
 
Back
Top