• 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 HELP! Update stuck with Plesk Onyx 17.8.11#1

Sergio Manzi

Sergio Manzi

Regular Pleskian
I'm in troubles...

received email from my system stating that updates were available:
Code: 
The following package updates are available:
- cloud-init 0.7.9-9.el7.centos.6 from updates repo (currently installed version: 0.7.9-9.el7.centos.2 from base repo)
- iptables 1.4.21-18.3.el7_4 from updates repo (currently installed version: 1.4.21-18.2.el7_4 from updates repo)
- libgcc 4.8.5-16.el7_4.2 from updates repo (currently installed version: 4.8.5-16.el7_4.1 from updates repo)
- libgomp 4.8.5-16.el7_4.2 from updates repo (currently installed version: 4.8.5-16.el7_4.1 from updates repo)
- libgudev1 219-42.el7_4.10 from updates repo (currently installed version: 219-42.el7_4.7 from updates repo)
- libstdc++ 4.8.5-16.el7_4.2 from updates repo (currently installed version: 4.8.5-16.el7_4.1 from updates repo)
- libteam 1.25-6.el7_4.3 from updates repo (currently installed version: 1.25-5.el7 from base repo)
- php 5.4.16-43.el7_4.1 from updates repo (currently installed version: 5.4.16-43.el7_4 from updates repo)
- php-cli 5.4.16-43.el7_4.1 from updates repo (currently installed version: 5.4.16-43.el7_4 from updates repo)
- php-common 5.4.16-43.el7_4.1 from updates repo (currently installed version: 5.4.16-43.el7_4 from updates repo)
- php-fpm 5.4.16-43.el7_4.1 from updates repo (currently installed version: 5.4.16-43.el7_4 from updates repo)
- php-gd 5.4.16-43.el7_4.1 from updates repo (currently installed version: 5.4.16-43.el7_4 from updates repo)
- php-mbstring 5.4.16-43.el7_4.1 from updates repo (currently installed version: 5.4.16-43.el7_4 from updates repo)
- php-mysql 5.4.16-43.el7_4.1 from updates repo (currently installed version: 5.4.16-43.el7_4 from updates repo)
- php-pdo 5.4.16-43.el7_4.1 from updates repo (currently installed version: 5.4.16-43.el7_4 from updates repo)
- php-xml 5.4.16-43.el7_4.1 from updates repo (currently installed version: 5.4.16-43.el7_4 from updates repo)
- python-perf 3.10.0-693.21.1.el7 from updates repo (currently installed version: 3.10.0-693.17.1.el7 from updates repo)
- selinux-policy 3.13.1-166.el7_4.9 from updates repo (currently installed version: 3.13.1-166.el7_4.7 from updates repo)
- selinux-policy-targeted 3.13.1-166.el7_4.9 from updates repo (currently installed version: 3.13.1-166.el7_4.7 from updates repo)
- systemd 219-42.el7_4.10 from updates repo (currently installed version: 219-42.el7_4.7 from updates repo)
- systemd-libs 219-42.el7_4.10 from updates repo (currently installed version: 219-42.el7_4.7 from updates repo)
- systemd-sysv 219-42.el7_4.10 from updates repo (currently installed version: 219-42.el7_4.7 from updates repo)
- teamd 1.25-6.el7_4.3 from updates repo (currently installed version: 1.25-5.el7 from base repo)

I proceeded to "Update all" from /admin/pum/updates-list

Now I have a never-ending pop-up telling "1 Tasks in progress... - Updating 23 packages", but... it never ends...

Via ssh I have:
Code: 
# ps awufx | grep pum | grep -v grep
root     12137  0.0  0.0  28464  1788 ?        S    04:11   0:00  \_ /usr/local/psa/admin/bin/pum --update --json -- cloud-init iptables libgcc libgomp libgudev1 libstdc++ libteam php php-cli php-common php-fpm php-gd php-mbstring php-mysql php-pdo php-xml python-perf selinux-policy selinux-policy-targeted systemd systemd-libs systemd-sysv teamd
root     12138  0.9  9.4 963544 178240 ?       S    04:11   0:08      \_ /usr/bin/python -Estt /usr/local/psa/admin/sbin/pum_worker --update --json -- cloud-init iptables libgcc libgomp libgudev1 libstdc++ libteam php php-cli php-common php-fpm php-gd php-mbstring php-mysql php-pdo php-xml python-perf selinux-policy selinux-policy-targeted systemd systemd-libs systemd-sysv teamd

What can I do? Kill pum? Then, maybe, "yum update"?
 
The whole process tree involved is:
Code: 
psaadm   12133  0.0  1.1 272888 22168 ?        Ss   04:11   0:00 /usr/bin/sw-engine -c /usr/local/psa/admin/conf/php.ini /usr/local/
root     12137  0.0  0.0  28464  1788 ?        S    04:11   0:00  \_ /usr/local/psa/admin/bin/pum --update --json -- cloud-init ipta
root     12138  0.5  9.4 963544 178240 ?       S    04:11   0:08      \_ /usr/bin/python -Estt /usr/local/psa/admin/sbin/pum_worker
root     15934  0.0  0.0  11636  1340 ?        S    04:15   0:00          \_ /bin/sh /var/tmp/rpm-tmp.FNIFfk 1
root     15952  0.0  0.0  25236  1812 ?        S    04:15   0:00              \_ systemctl try-restart php-fpm.service
 
Tried restarting php-fpm manually. Bad news:
Code: 
# systemctl restart php-fpm
Job for php-fpm.service failed because the control process exited with error code. See "systemctl status php-fpm.service" and "journalctl -xe" for details.
 
Code: 
# systemctl -l status php-fpm.service
● php-fpm.service - The PHP FastCGI Process Manager
   Loaded: loaded (/usr/lib/systemd/system/php-fpm.service; disabled; vendor preset: disabled)
  Drop-In: /usr/lib/systemd/system/php-fpm.service.d
           └─limit_nofile.conf
   Active: failed (Result: exit-code) since Fri 2018-03-09 04:40:12 GMT; 6min ago
  Process: 19100 ExecStart=/usr/sbin/php-fpm --nodaemonize (code=exited, status=78)
 Main PID: 19100 (code=exited, status=78)

Mar 09 04:40:12 ams301.smz.it systemd[1]: Starting The PHP FastCGI Process Manager...
Mar 09 04:40:12 ams301.smz.it php-fpm[19100]: [09-Mar-2018 04:40:12] ERROR: No pool defined. at least one pool section must be specified in config file
Mar 09 04:40:12 ams301.smz.it php-fpm[19100]: [09-Mar-2018 04:40:12] ERROR: failed to post process the configuration
Mar 09 04:40:12 ams301.smz.it php-fpm[19100]: [09-Mar-2018 04:40:12] ERROR: FPM initialization failed
Mar 09 04:40:12 ams301.smz.it systemd[1]: php-fpm.service: main process exited, code=exited, status=78/n/a
Mar 09 04:40:12 ams301.smz.it systemd[1]: Failed to start The PHP FastCGI Process Manager.
Mar 09 04:40:12 ams301.smz.it systemd[1]: Unit php-fpm.service entered failed state.
Mar 09 04:40:12 ams301.smz.it systemd[1]: php-fpm.service failed.

All sites seems to be up and running (both those using PHP-FPM via nginx and Apache)
 
Thanks Mark!

All I see is the diagnostic from "systemctls status" that states "ERRor. No pool defined.", see above...
 
Oh do you still have that updating pop up in Plesk?

That no pool **** is usually when no domains are assigned to fpm so it won’t start, the Plesk repair web command might fix that.
 
plesk repair web -n

Checking Plesk version .............................................. [OK]

Checking for custom configuration templates
Some custom configuration templates have been found. The custom
templates have higher priority than default templates in case of
configs generation
Please check documentation for details:
https://docs.plesk.com/current/redirect.html?book=advanced-administration-guide-linux&page=68693.htm
................................................................... [WARNING] <=== It's good, assured!!

Checking the JkWorkersFile directive in the Apache configuration .... [OK]

Checking associations between domains and IP addresses .............. [OK]

Checking for corrupted reference between IP collections and
IPaddresses ......................................................... [OK]

Checking for links between APS applications and subscriptions ....... [OK]

Checking for the Zend extension declaraion in php.ini ............... [OK]

Check symbolic links for latest virtual host config files ........... [OK]

Checking for system users home directories consistency .............. [OK]

Checking for records with empty name field in the Configurations table
................................................................... [OK]

Checking for nginx ULIMIT value ..................................... [OK]

Checking for extra configurations in database not owned by any object
................................................................... [OK]

Checking the configuration of Apache modules ........................ [OK]

Repairing web server configuration .................................. [OK]

Checking the usage of PHP handlers .................................. [OK]

Error messages: 0; Warnings: 1; Errors resolved: 0
 
Only this:
Code: 
# cat /var/log/php-fpm/error.log
[09-Mar-2018 04:40:12] ERROR: No pool defined. at least one pool section must be specified in config file
[09-Mar-2018 04:40:12] ERROR: failed to post process the configuration
[09-Mar-2018 04:40:12] ERROR: FPM initialization failed
 
... but all 23 updates are still listed as available.

  • Sites are up...
  • After all tomorrow will be another day ...
  • Going to sleep for a while...

Thanks Mark!
 
You must log in or register to reply here.

Similar threads

K
Issue Plesk Onyx 17.8.11 Update #73 update fails
Replies
4
Views
1K
Karolus
K
I
Issue Unable to install Extensions or update plesk
Replies
4
Views
1K
Maarten.
M
D
Issue Upgrade to Plesk Obsidian 18.0.27 from Plesk Onyx 17.8.11 Update failed
Replies
6
Views
2K
Alan JACKSON687327
A
E
Resolved Plesk & website down after update
Replies
2
Views
2K
Erikmatheus
E
Sergio Manzi
Forwarded to devs Update hung with PHP 5.4.16 by OS vendor FPM application disabled
Replies
6
Views
2K
Sergio Manzi
Sergio Manzi
Back
Top