• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Plesk Onyx 17.0.17 to 17.5.3 update problem

Eberhard Gierke

Basic Pleskian
Hi Guys,

I have a problem with the update of plesk onyx 17.0.17 # 25 to the version 17.5.3.
Here is the last entry of the update log.

'Setting up plesk-dovecot-imap-driver (17.5.3-ubuntu16.04.build1705170317.16) ...'

After that, it is no longer possible to login in plesk. Nothing works anymore.

Even after a new installation of my server (without the backup of my customer data) the update failed.

Has anyone an idea about this problem?

Operating System: Ubuntu 16.04.2 LTS

In advance for your help many thanks!

Greetings, Eberhard
 
Try to install all available updates with

# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components

and then try upgrade again.
 
Hello Igor,

Many thanks for your quick reply!
But are you sure it will work then? I have no need to reinstall my server again (I have already done three or four times). ;-)

regards, Eberhard
 
Hi Eberhard Gierke,

But are you sure it will work then?
It won't harm you ( or your server! ) to test it, because using the suggested command will not at all change users/customers, postboxes or any other related user/customer data. Even the change from dovecot to courier-imap ( or/and backwards to dovecot ) will not change any user/customer data.


Please consider as well the usage of the Plesk Repair Utility, which helps to investigate and solve common issues/errors/problems:


... and posting the complete repair.log / installation.log from your "/var/log/plesk" - folder will help as well to investigate the root cause of your issues/errors/problems. ;)
 
That sound's good ;-)

Ok, I run the Plesk Repair Tool, see follow...

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[2017-05-11 16:28:39]
[2017-05-11 16:28:39] Checking the Plesk database using the native database server tools
[2017-05-11 16:28:39] .. [OK]
[2017-05-11 16:28:39]
[2017-05-11 16:28:39] Checking the structure of the Plesk database
[2017-05-11 16:28:39] ........................ [OK]
[2017-05-11 16:28:39]
[2017-05-11 16:28:39] Checking the consistency of the Plesk database
[2017-05-11 16:28:39] ...................... [OK]
[2017-05-11 16:28:39]
[2017-05-11 16:28:39] Checking system users
[2017-05-11 16:28:39] ............................................... [OK]
[2017-05-11 16:28:39]
[2017-05-11 16:28:39] Checking Linux system files
[2017-05-11 16:28:41] ......................................... [OK]
[2017-05-11 16:28:41]
[2017-05-11 16:28:41] Checking virtual hosts' file system
[2017-05-11 16:28:41]
[2017-05-11 16:28:41] There are files or directories with suspicious permissions in the
[2017-05-11 16:28:41] root directory of the domain 'xxx.yy' ...................... [WARNING]
[2017-05-11 16:28:41] To see more details, run the command in the verbose mode: plesk repair fs -verbose
[2017-05-11 16:28:41]
[2017-05-11 16:28:41] There are files or directories with suspicious permissions in the
[2017-05-11 16:28:41] root directory of the domain 'xxx.yy' ......................... [WARNING]
[2017-05-11 16:28:41] To see more details, run the command in the verbose mode: plesk repair fs -verbose
[2017-05-11 16:28:41]
[2017-05-11 16:28:41] There are files or directories with suspicious permissions in the
[2017-05-11 16:28:41] root directory of the domain 'xxx.yy' .................. [WARNING]
[2017-05-11 16:28:41] To see more details, run the command in the verbose mode: plesk repair fs -verbose
[2017-05-11 16:28:41]
[2017-05-11 16:28:41] There are files or directories with suspicious permissions in the
[2017-05-11 16:28:41] root directory of the domain 'xxx.yy' ............. [WARNING]
[2017-05-11 16:28:41] To see more details, run the command in the verbose mode: plesk repair fs -verbose
[2017-05-11 16:28:41]
[2017-05-11 16:28:41] There are files or directories with suspicious permissions in the
[2017-05-11 16:28:41] root directory of the domain 'xxx.yy' ...................... [WARNING]
[2017-05-11 16:28:41] To see more details, run the command in the verbose mode: plesk repair fs -verbose
[2017-05-11 16:28:41]
[2017-05-11 16:28:41] Repairing web server configuration
[2017-05-11 16:28:41]
[2017-05-11 16:28:41] Reinstall SSL/TLS certificates and set the default certificate for all IP addresses? [Y/n]
[2017-05-11 16:28:56]
[2017-05-11 16:28:56] Repair server-wide configuration parameters for web servers? [Y/n]
[2017-05-11 16:29:14] Repairing server-wide configuration parameters for web servers ..
[2017-05-11 16:29:20] [OK]
[2017-05-11 16:29:20]
[2017-05-11 16:29:20] Update the file of sharing passwords and permissions of users according to actual information? [Y/n]
[2017-05-11 16:29:36]
[2017-05-11 16:29:36] Repair web server configuration for all domains? [Y/n]
[2017-05-11 16:29:43]
[2017-05-11 16:29:43] Checking the usage of PHP handlers
[2017-05-11 16:29:44] .................................. [OK]
[2017-05-11 16:29:44]
[2017-05-11 16:29:44] Repairing the mail server configuration
[2017-05-11 16:29:44]
[2017-05-11 16:29:44] Reconfigure all domains and mailboxes? [Y/n]
[2017-05-11 16:29:50]
[2017-05-11 16:29:50] Checking the DNS configuration file
[2017-05-11 16:29:51]
[2017-05-11 16:29:51] The NS configuration file '/var/named/run-root/etc/named.conf' is
[2017-05-11 16:29:51] absent ............................................................ [ERROR]
[2017-05-11 16:29:51]
[2017-05-11 16:29:51] Restore the DNS configuration file from '/var/named/run-root/etc/named.conf.default'? [Y/n]
[2017-05-11 16:30:05]
[2017-05-11 16:30:05] Restoring DNS server configuration
[2017-05-11 16:30:05]
[2017-05-11 16:30:05] Synchronize DNS zones with the DNS server? [Y/n]
[2017-05-11 16:30:11] Synchronizing DNS zones with the DNS server .....................
[2017-05-11 16:30:11] [OK]
[2017-05-11 16:30:11]
[2017-05-11 16:30:11] Checking MySQL database servers
[2017-05-11 16:30:11] ..................................... [OK]
[2017-05-11 16:30:11]
[2017-05-11 16:30:11] Repair databases on available servers
[2017-05-11 16:30:11] ............................... [OK]
[2017-05-11 16:30:11]
[2017-05-11 16:30:11] Repair database users on available servers
[2017-05-11 16:30:11] .......................... [OK]
[2017-05-11 16:30:11] Error messages: 1; Warnings: 5; Errors resolved: 0
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------

What do you think about it?

Grüße nach Hamburg ;-)
 
Hi Eberhard Gierke,

IF you see warnings like:
oot directory of the domain 'xxx.yy' ...................... [WARNING]
and the suggestion
To see more details, run the command in the verbose mode: plesk repair fs -verbose
... is there any reason for you, not tu use the recommended command?

To be sure that all possible errors and warnings have been resolved, just run the Plesk Repair a SECOND time afterwards. ;)
Sometimes to have to adjust found issues manually, so if you experience the very same errors/warnings again and again ( when you chossed the "Y" option! ), pls. consider to repair such errors/warnings manually! :)


... which brings us back to your initial issue/problem:
'Setting up plesk-dovecot-imap-driver (17.5.3-ubuntu16.04.build1705170317.16) ...'
Just use the commands:
Code:
plesk installer --select-product-id plesk --select-release-current --install-component courier-imap
followed by
Code:
plesk installer --select-product-id plesk --select-release-current --install-component dovecot
... and you "normally" should not have any more issues as stated in your initial post. ;)
 
Hi UFHH01,

Thanks you for your answer.

Ok, I have now corrected all error. Plesk Repair gives me the following message.

'The ns configuration file' /var/named/run-boot/etc/named.conf 'is absent'

I've checked the path. '/var/named/run-boot/etc/named.conf' does not exist.

Is this a problem, because my system so far works.

If this is not a problem, I will try to update the Plesk Onyx 17.5.3 on the weekend (because of the customers).

Greetings, Eberhard
 
Hi UFHH01,

ok, review...

I have done the follow steps:

# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
plesk installer --select-product-id plesk --select-release-current --install-component courier-imap
plesk installer --select-product-id plesk --select-release-current --install-component dovecot

I have just one question....
How save is the update to Plesk Onyx Version 17.5.3?
I do not want to reinstall my server again.:)

Thanks for your answer!

Wie ist denn das Wetter im hohen Norden??;)

regards,
Eberhard
 
It is safe enough.

Unfortunately this was not safe enough and the same error has happened with the update.
I post the whole update protocol, maybe someone has an idea.

Thank you...
 

Attachments

  • protokoll_update_von_plesk_onyx_17.017_nach_plesk_onyx_17.5.3.txt
    28 KB · Views: 6
Hi Eberhard Gierke,

unfortunately, your log stops at
Code:
Setting up plesk-dovecot-imap-driver (17.5.3-ubuntu16.04.build1705170317.16) ...
Up to there, there are no issues/errors/problems, so pls. consider to inform us a bit further about possible issues/errors/problems, so that people willing to help have a chance to investigate it together with you! ;)
 
Hi UFHH01,

unfortunately, your log stops at

Yes, that's the last entry, after that stops my system :oops:

The problem ist the dovecot-imap-driver. i don't know why.
Because I do not want to reinstall my server twice a week, I change the imap-server from Dovecot to Courier-IMAP.
After that, run's the update to Plesk Onyx 17.5.3 without problems, so the problem is Dovecot.

Maybe someone can report this problem to Odin. I can not do this because I can not open a ticket with my reseller license.o_O
 
Hi Eberhard Gierke,

Odin is no longer responsible for Plesk, because Plesk is now "Plesk"... nothing more. :)

Actually, we have a "Bug - Report" subforum here at the Plesk Community Forum as well, where you can open a bug - report all by yourself and "if confirmed" , then a Plesk Team - Member at this forum will hand the bug - report over to the Plesk developpers. ;)

 
Hello,

I have uptade my Plesk Onyx 17.0.17 to 17.5.3.

Since this update, I every day the server wants to make updates, this version of plesk is not the stable version of Plesk?

Thanks in advence for your reply.

@+
 
Hi ClementSaubois,

this version of plesk is not the stable version of Plesk?
Yes, the current Plesk Onyx 17.5.3 - version IS the ( latest ) STABLE version right now. ;)

I every day the server wants to make updates
I suppose, that you updated/upgraded over your command line ( or your initial update/upgrade over the Plesk Control Panel hasn't been finished correctly ), while you then could experience update - notifications to be displayed over the Plesk Control Panel.

Pls. just head over to your "HOME > Tools & Settings > System Updates" and use the button "Search for Updates". Afterwards ( if no current updates/upgrades are found! ), pls. click again on the "HOME" navigation and your notification should disappear. ;)
 
Back
Top