Issue Upgrade 17.5.3 to 17.8.11 Plesk pre-upgrade check failed

[ellog]

Hi,

today i just tried to run the upgrade from 17.5.3 to 18.8.11 Stable over the Webgui.

The Plesk pre-upgrade check stops with following warning:

Plesk pre-upgrade check
WARNING: The PAM configuration is in inconsistent state. If you proceed with the installation, the required PAM modules will not be installed. This will cause problems during the authentication. Some PAM services reference the following nonexistent services: system-auth. Check Plesk Help Center for more details.

I tried to follow the kb link but it seems dead.

I had also a view in to the pam.d directory but can't judge if something is wrong:

root@vps007:/etc/pam.d# ls -l

total 120

-rw-r--r-- 1 root root 384 Nov 12 2015 chfn

-rw-r--r-- 1 root root 92 Nov 12 2015 chpasswd

-rw-r--r-- 1 root root 581 Nov 12 2015 chsh

-rw-r--r-- 1 root root 1208 Nov 22 2016 common-account

-rw-r--r-- 1 root root 1208 Nov 22 2016 common-account.pam-old

-rw-r--r-- 1 root root 1281 Nov 29 2016 common-auth

-rw-r--r-- 1 root root 1281 Nov 22 2016 common-auth.pam-old

-rw-r--r-- 1 root root 1501 Nov 29 2016 common-password

-rw-r--r-- 1 root root 1501 Nov 22 2016 common-password.pam-old

-rw-r--r-- 1 root root 1504 Nov 22 2016 common-session

-rw-r--r-- 1 root root 1435 Nov 22 2016 common-session-noninteractive

-rw-r--r-- 1 root root 1435 Nov 22 2016 common-session-noninteractive.pam-old

-rw-r--r-- 1 root root 1471 Nov 22 2016 common-session.pam-old

-rw-r--r-- 1 root root 606 Apr 5 2016 cron

-rw-r--r-- 1 root root 4866 Jan 30 2016 login

-rw-r--r-- 1 root root 92 Nov 12 2015 newusers

-rw-r--r-- 1 root root 520 Mar 16 2016 other

-rw-r--r-- 1 root root 92 Nov 12 2015 passwd

-rw-r--r-- 1 root root 105 Oct 28 2016 plesk_resctrl

-rw-r--r-- 1 root root 46 Oct 29 2016 plesk_usermng_encrypted

-rw-r--r-- 1 root root 243 Jul 26 2017 proftpd

-rw-r--r-- 1 root root 318 Jul 26 2017 proftpd.bak

-rw-r--r-- 1 root root 143 Mar 12 2016 runuser

-rw-r--r-- 1 root root 138 Mar 12 2016 runuser-l

-rw-r--r-- 1 root root 84 Mar 8 2016 samba

-rw-r--r-- 1 root root 2133 Aug 11 2016 sshd

-rw-r--r-- 1 root root 2257 Nov 12 2015 su

-rw-r--r-- 1 root root 239 Aug 17 2016 sudo

-rw-r--r-- 1 root root 251 Oct 5 2016 systemd-user

 

[IgorG]

First of all make sure that you have no installed 3-rd party packages like "xpra" on your server. Remove it if installed.
Also please apply actual PAM configuration via SSH run:

# /usr/sbin/pam-auth-update --force

And run upgrade again.

 

[ellog]

I checked my server and i haven't installed 3-rd party pkg like xpra.

I did the PAM Config by using the command # /usr/sbin/pam-auth-update --force, then i did a reboot a tried again the upgrade. Result is the same as before the pre-upgrade check fails. How can i run that upgrade check per SSH and can is see more in details what the check complaints?

 

[IgorG]

How can i run that upgrade check per SSH and can is see more in details what the check complaints?

Plesk Pre-Upgrade Checker: A tool to identify business logic issues before upgrade or migration

 

[ellog]

thx Igor for your reply, i did the suggested pre check per command line, but it's not much more then from GUI. I still have no indication what is the reason for the warning.

# php -d safe_mode=Off panel_preupgrade_checker.php

[2018-07-16 09:20:09][INFO] Installed Plesk version/build: 17.5.3 Ubuntu 16.04 1705170317.16...

[2018-07-16 09:20:09][INFO] STEP 0: Detect system configuration...
[2018-07-16 09:20:09][INFO] OS: Ubuntu 16.04.4 LTS \n \l
[2018-07-16 09:20:09][INFO] Arch: x86_64
[2018-07-16 09:20:09][INFO] Validating the database password...
[2018-07-16 09:20:09][INFO] Result: OK

[2018-07-16 09:20:09][INFO] Pre-Upgrade analyzer version: 17.8.11.0...
[2018-07-16 09:20:09][INFO] STEP 1: Checking for main IP address...
[2018-07-16 09:20:09][INFO] Result: OK

[2018-07-16 09:20:09][INFO] STEP 2: Checking existence of Plesk user "root" for MySQL database servers...
[2018-07-16 09:20:09][INFO] Result: OK

[2018-07-16 09:20:09][INFO] STEP 3: Checking PAM configuration array consistency...
[2018-07-16 09:20:09][WARNING] The PAM configuration is in inconsistent state. If you proceed with the installation, the required PAM modules will not be installed. This will cause problems during the authentication. Some PAM services reference the following nonexistent services: system-auth. Check hxxp://kb.plesk.com/en/112944 for more details.
[2018-07-16 09:20:09][INFO] Result: WARNING

[2018-07-16 09:20:09][INFO] STEP 4: Checking the /etc/psa/psa.conf file for consistency...
[2018-07-16 09:20:09][INFO] Result: OK

[2018-07-16 09:20:09][INFO] STEP 5: Checking proftpd settings...
[2018-07-16 09:20:09][INFO] Result: OK

[2018-07-16 09:20:09][INFO] STEP 6: Checking the version of the mysqlclient15 package...
[2018-07-16 09:20:09][INFO] Result: OK

[2018-07-16 09:20:09][INFO] STEP 7: Checking NS type records in the Panel DNS template...
[2018-07-16 09:20:09][INFO] Result: OK

[2018-07-16 09:20:09][INFO] STEP 8: Checking the version of MySQL ODBC package...
[2018-07-16 09:20:09][INFO] Result: OK

[2018-07-16 09:20:09][INFO] STEP 9: Checking the 'Interval' parameter in the sw-collectd configuration file...
[2018-07-16 09:20:09][INFO] Result: OK

[2018-07-16 09:20:09][INFO] STEP 10: Checking Apache status...
[2018-07-16 09:20:09][INFO] Result: OK

[2018-07-16 09:20:09][INFO] STEP 11: Checking for a password in my.cnf files...
[2018-07-16 09:20:09][INFO] Result: OK

[2018-07-16 09:20:09][INFO] STEP 12: Detecting if old encrypted passwords are used...
[2018-07-16 09:20:09][INFO] Result: OK

[2018-07-16 09:20:09][INFO] STEP 13: Checking Panel files for the immutable bit attribute...
[2018-07-16 09:20:11][INFO] Result: OK

[2018-07-16 09:20:11][INFO] STEP 14: Checking the possibility to change the owner of files in the DUMP_D directory...
[2018-07-16 09:20:11][INFO] Result: OK

[2018-07-16 09:20:11][INFO] STEP 15: Checking consistency of the IP addresses list in the Panel database...
[2018-07-16 09:20:11][INFO] Result: OK

[2018-07-16 09:20:11][INFO] STEP 16: Checking installed APS applications...
[2018-07-16 09:20:11][INFO] Result: OK

[2018-07-16 09:20:11][INFO] STEP 17: Checking if apsc database tables have InnoDB engine...
[2018-07-16 09:20:11][INFO] Result: OK

[2018-07-16 09:20:11][INFO] STEP 18: Checking for custom web server configuration templates...
[2018-07-16 09:20:11][INFO] Result: OK

[2018-07-16 09:20:11][INFO] STEP 19: Checking symbolic link /usr/local/psa on /opt/psa...
[2018-07-16 09:20:11][INFO] Result: OK

[2018-07-16 09:20:11][INFO] STEP 20: Checking that limits are not exceeded in /proc/user_beancounters...
[2018-07-16 09:20:11][INFO] Result: OK

[2018-07-16 09:20:11][INFO] STEP 21: Checking for limit shmpages......
[2018-07-16 09:20:11][INFO] Result: OK

[2018-07-16 09:20:11][INFO] STEP 22: Detecting if encrypted passwords are used...
[2018-07-16 09:20:11][INFO] Result: OK

[2018-07-16 09:20:11][INFO] STEP 23: Checking table "servers" in database "mysql"...
[2018-07-16 09:20:11][INFO] Result: OK

[2018-07-16 09:20:11][INFO] STEP 24: Checking the availability of Plesk Panel TCP ports...
[2018-07-16 09:20:11][INFO] Result: OK

[2018-07-16 09:20:11][INFO] STEP 25: Checking for available free memory for the upgrade procedure...
[2018-07-16 09:20:11][INFO] Result: OK

Errors found: 0; Warnings found: 1

 

[ellog]

after doing a snapshot and backup, i took the risk and upgraded Plesk to 17.8.11 Update 14.

The upgrade was successful i had during the upgrade as expected for the PAM a warning :

**** Product post-install started.

===> Checking for previous installation ... found.
 Trying to generate default psa SSL Certificate... default certificate already exists
done
 Trying to install PAM module... PAM configuration loaded from (directory="/etc/pam.d", file="/etc/pam.conf"). Configuration contains 29 file(s)
3:a programming/runtime error (PAMServiceError: system-auth)

WARNING!
Some problems are found during install PAM module not successed(see log file: /var/log/plesk/install/plesk_17.8.11_installation.log)

Continue...

 Checking for the group 'psaadm'...
 Trying to add supplementary group 'psaadm' for user 'sw-cp-server'...  already there
 Checking for the group 'lock-manager'...
 Trying to add supplementary group 'lock-manager' for user 'psaadm'...  already there
 Trying to start service mysql... /usr/sbin/mysqld (pid 16435) is running...
done
 Trying to establish test connection... connected
done

**** Product post-install for BASE completed with warnings.

3:a programming/runtime error (PAMServiceError: system-auth)
STOP Bootstrapper 17.8.11 post-install for BASE AT Mon Jul 23 09:48:21 CEST 2018
START Bootstrapper 17.8.11 perform-deferred-actions AT Mon Jul 23 09:48:22 CEST 2018

i have still no good feeling on the warning with PAM, any Idea how to determine the warning?