• 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 sw-engine is not starting after distro upgrade

jradzuweit

Basic Pleskian
After upgrade from Ubuntu 14.04 to 16.04 the sw-engine is not starting. It fails with following message

root@vega:~# systemctl status sw-engine.service
● sw-engine.service - Startup script for Panel sw-engine
Loaded: loaded (/lib/systemd/system/sw-engine.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mo 2017-10-02 14:59:06 CEST; 1min 3s ago
Process: 2548 ExecStopPost=/usr/bin/find /run/lock/lmlib/ -mindepth 1 -delete (code=exited, status=0/SUCCESS)
Process: 2520 ExecStart=/usr/sbin/sw-engine-fpm --fpm-config /etc/sw-engine/sw-engine-fpm.conf -c /usr/local/psa/admin/conf/php.ini --nodaemonize --pid /run/sw-engine.pid (code=exited, status=127)
Main PID: 2520 (code=exited, status=127) Okt 02 14:59:06 vega.radzuweit.eu systemd[1]: Starting Startup script for Panel sw-engine... Okt 02 14:59:06 vega.radzuweit.eu sw-engine-fpm[2520]: /usr/sbin/sw-engine-fpm: symbol lookup error: /usr/sbin/sw-engine-fpm: undefined symbol: _ZNK3APS4Meta14ScreenshotInfo4pathB5cxx11Ev
Okt 02 14:59:06 vega.radzuweit.eu systemd[1]: sw-engine.service: Main process exited, code=exited, status=127/n/a
Okt 02 14:59:06 vega.radzuweit.eu systemd[1]: Failed to start Startup script for Panel sw-engine. Okt 02 14:59:06 vega.radzuweit.eu systemd[1]: sw-engine.service: Unit entered failed state. Okt 02 14:59:06 vega.radzuweit.eu systemd[1]: sw-engine.service: Failed with result 'exit-code'.

The undefined symbol looks like a session key, any idea what the problem is? I already cecked the mentioned config files.
 
I asume I have to switch to Index of /PSA_17.5.3/dist-deb-Ubuntu-16.04-x86_64 , because I have already Onyx 17.5.3 on my machine.
Ok I tried it but then I get a error that one of the package can't be installed because of dependency. Here the related output on my machine

Code:
root@vega:~/Fix-16.04# dpkg -i plesk-librdbmspp_2.0.1-ubuntu16.04.735641.16061715_amd64.deb
(Reading database ... 178997 files and directories currently installed.)
Preparing to unpack plesk-librdbmspp_2.0.1-ubuntu16.04.735641.16061715_amd64.deb ...
Unpacking plesk-librdbmspp (2.0.1-ubuntu16.04.735641.16061715) over (2.0.1-ubuntu16.04.735641.16061715) ...
dpkg: dependency problems prevent configuration of plesk-librdbmspp:
 plesk-librdbmspp depends on libodbc1 (>= 2.3.1); however:
  Version of libodbc1:amd64 on system is 2.2.14p2-5ubuntu5.

dpkg: error processing package plesk-librdbmspp (--install):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.23-0ubuntu9) ...
Errors were encountered while processing:
 plesk-librdbmspp
root@vega:~/Fix-16.04# dpkg -l | grep odbc
ii  libodbc1:amd64                    2.2.14p2-5ubuntu5                          amd64        ODBC library for Unix
ii  odbcinst                          2.2.14p2-5ubuntu5                          amd64        Helper program for accessing odbc ini files
ii  odbcinst1debian2:amd64            2.2.14p2-5ubuntu5                          amd64        Support library for accessing odbc ini files
ii  plesk-libmyodbc                   5.2.7-ubuntu14.04.17031415                 amd64        the MySQL ODBC driver
ii  plesk-php56-odbc                  5.6.31-ubuntu14.04.17070710                amd64        A module for PHP applications that use ODBC databases
ii  plesk-php70-odbc                  7.0.24-ubuntu14.04.17092912                amd64        A module for PHP applications that use ODBC databases

the libodbc is an older version.
 
... so I found the root cause of the problem. During the dist-upgrade the file behind the link /etc/resolv.conf is removed leaves the machine without any dns resolving capability. Very bad, because all following package upgrades are failing and the dist -upgrade is not finished. This is why /etc/os-release states that it is still a 14.04 release..
I the meantime I brought the system up and it is running, but I think I need some time to check if all is working properly.
So here my solution to solve this issue:

  1. Add /run/resolvconf/resolv.conf an put some valid DNS server in it. The link /etc/resolv.conf should work now. Check if you can ping www.google.com, if yes proceed.
  2. Run as root
    Code:
     root@vega:~# apt-get dist-upgrade --fix-missing
    this should complete the dist-upgrade for now. There are some questions during the upgrade, answer the according to your original configuration. One was about your mail server/ or local MTA and the other one about the pam modules.
  3. Reboot the machine
  4. Run
    Code:
    root@vega:~# plesk repair all
    this will fix the Plesk installation an recover your original configuration. There are several questions, I proceeded with the defaults and changed nothing
  5. Reboot the machine.
  6. Check if psa and sw-engine are running with the following commands
    Code:
    root@vega:~# service psa status 
    root@vega:~# service sw-engine status
@plesk: Please update your Dist-Upgrade guide for Ubuntu 14.04->16.04, the current documentation is not sufficient and please check the helper script it might delete the resolv.conf file by accident.

I need to upgrade five more Plesk installations with this combination, Ubuntu 14.04 with Plesk Onyx 17.5.3, but this procedure is not good for production systems. I had now nearly 24 hours downtime for this system!
 
Back
Top