Ubuntu 20.04: PHP-FPM configuration error found : No listen directive found in FPM config

SYSTEM INFORMATION
OS type and version Ubuntu 20.04
Webmin version 2.402
Virtualmin version 7.30.8
Webserver version 2.4.41
Related packages SUGGESTED
I am also supporting a multi-php environment using the ondrey repositories.

Hi, I am experiencing the same problem reported for
PHP-FPM configuration error found : No listen directive found in FPM config

For me, I have discovered this issue while performing an upgrade from Ubuntu 20.04 to Ubuntu 24.04. I have 5 nearly identical server configuration, they all exhibit this problem in 20.04, and after upgrading to 24.04 (3 of 5 upgraded so far).

Is there a place to output the php configuration of each site so that resetting each site will be easy? In other words a table of php Options for the server, listing each site’s settings?

I will also report another oddity, in case it’s informative…

When I disable the site, the database password is disabled as well, which is OK. However when the site is re-enabled, the password no longer works. I must reset the password to the same value, selecting the option for mysql native encryption, and then it works.

My uninformed guess is that when the database password is enabled, it uses the newer encryption method.

This means nothing, use the icon in the dashboard to paste your info

Does recheck config show anything?
Disabling and re enabling php I think was a solution not the whole site.

This is from one of the un-upgraded servers, which displays the error for some of the sites.

SYSTEM INFORMATION
OS type and version Ubuntu Linux 20.04.6
Usermin version 2.302
Virtualmin version 7.30.8
Theme version 24.02
Apache version 2.4.41
Package updates All installed packages are up to date

Doesn’t show webmin version for some reason, but what I originally entered is accurate.


The status of your system is being checked to ensure that all enabled features are available and properly configured ..

Your system has 1.92 GiB of memory, which is at or above the Virtualmin recommended minimum of 256 MiB

Apache is installed

Apache does not support HTTP/2 : Missing Apache mod_http2 module

The following CGI script execution modes are available : suexec

The following PHP execution modes are available : fpm fcgid cgi

The following PHP versions are available : 5.6.40 (/usr/bin/php-cgi5.6), 7.2.34 (/usr/bin/php-cgi7.2), 7.3.33 (/usr/bin/php-cgi7.3), 7.4.33 (/usr/bin/php-cgi7.4)

The following PHP-FPM versions are available : 5.6.40 (php5.6-fpm) 7.2.34 (php7.2-fpm) 7.3.33 (php7.3-fpm) 7.4.33 (php7.4-fpm)

Webalizer is installed

Apache is configured to host SSL websites

MySQL 5.7.42 is installed and running

Logrotate is installed

Plugin AWStats reporting is installed

Plugin Protected web directories is installed

Using network interface eth0 for virtual IPs

Default IPv4 address for virtual servers is xx.xxx.xxx.xxx

Default IP address is set to xx.xxx.xxx.xxx, which matches the detected external address

Both user and group quotas are enabled for home and email directories

All commands needed to create and restore backups are installed

The selected package management and update systems are installed

Chroot jails are not available : The Jailkit command jk_init was not found on your system - maybe the jailkit package is not installed?

.. your system is ready for use by Virtualmin

That true, must be a bug.

PHP versions are available : 5.6.40 

That is very old. In fact all the versions are old.

this is also old mysql is now at version 8, It might be an idea to make off site backups of your virtual servers and install a new version of your chosen OS, install virtualmin on the fresh OS then restore your off site backups. The only gotcha here is by default virtualmin installs mariadb rather than mysql, so your databases may not be restored correctly (depends on the database files themselves). As a work around install mysql-server before you install virtualmin

Given they’ve gone out of their way to install a dangerously out of date PHP version, I guess they’re running an old MySQL on purpose. At least MySQL 5.7 is still maintained. PHP decidedly is not and has not been for years.

LOL tell me something I don’t know :slight_smile: But probably not relevant to the problem at hand…

Thank you for this! Upgrading to MySQL 8 is part of the process I am going through, but since the problem at hand happens BEFORE any upgrade is done, the upgrade isn’t relevant to the problem. In one of my test runs for the upgrade, mariadb DID in fact get installed, so now I have a better understanding of why that happened. The method I am using to upgrade MySQL is to delete all libs that specify MySQL 5.7 (5 libs, I think) then remove the repository sources point to 5.7, and then reinstall MySQL. I think mariadb got installed when I selected mysql-server-8 to be installed rather than mysql-server. It only happened once.

Exactly. 3rd party applications still using the original mysql driver (not mysqli). We are trying to get past them for “live” sites. The upgrade process I am currently working on at least gets us past MySQL 5.7 to MySQL 8. We are using the ondrej php repositories, and those still get updates occasionally for php 5.6. I can hold out hope that those updates include some security backports. I have searched for a changelog for those updates but haven’t found any to support my hope.

We have a number of “archive” sites that will likely never be updated past php 5.6. By “archive” I mean a site dedicated to data from a particular year (dating back to 2003) and publicly available but never changed. We have moved most of these sites to a dedicated server so that at some point it will be the only server supporting php 5.6. From that site, we have removed all personal information from the databases so that if it DOES get hacked, nothing of value can be harvested. The world is not a perfect place… :frowning:

Back to the original question:

If not, I’ll copy the contents of the contents of /etc/webmin/virtual-server/domains so I’ll at least be able to find the values in a text editor.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.