Recent wbm-virtual-s Update causing Virtual Server Validation to fail (administrative user / php-fpm pool port conflict)

Submitted by exius on Thu, 08/10/2017 - 12:32

Sometime around 5-6 AM GMT-7 today (Aug 8, 2017), I started receiving ** Virtualmin Validation Failed** notification emails every hour.

`

Virtual server validation

website1.org Administration user : Port 9002 is being used by website1 to run unexpected server 'php-fpm: pool website1', Port 9002 is being used by website1 to run unexpected server 'php-fpm: pool website1', Port 9002 is being used by website1 to run unexpected server 'php-fpm: pool website1', Port 9002 is being used by website1 to run unexpected server 'php-fpm: pool website1' website2.com Administration user : Port 9001 is being used by website2 to run unexpected server 'php-fpm: pool website2', Port 9001 is being used by website2 to run unexpected server 'php-fpm: pool website2', Port 9001 is being used by website2 to run unexpected server 'php-fpm: pool website2', Port 9001 is being used by website2 to run unexpected server 'php-fpm: pool website2' `

I noticed that at about 5 hours ago, there had been an automatic package update. In yum, I was able to find the name and time of the package (wbm-virtual-s).

' [root@ ~]# yum history list Loaded plugins: fastestmirror

ID | Command line | Date and time | Action(s) | Altered

834 | -y install wbm-virtual-s | 2017-08-10 05:25 | Update | 1 EE ... '

There is somehow a conflict with the two ports 9001 and 9002, which I am using for my php-fpm pools.

Looking for this issue to be resolved. Thank you.

Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Thu, 08/10/2017 - 12:47

Did you setup FPM using Virtualmin, or manually?

You can turn off these checks (which are supposed to not trigger for Virtualmin-configured ports) at System Settings -> Virtualmin Configuration -> Server administrator permissions -> Can listen on unexpected ports?

Submitted by exius on Thu, 08/10/2017 - 18:48

Hi Jamie,

I had manually set up php-fpm, I believe, before it was introduced as an automatic method in Virtualmin.

Submitted by JamieCameron on Fri, 08/11/2017 - 01:04

In that case, simply turning off this check is probably the best solution.

Submitted by JamieCameron on Fri, 08/11/2017 - 01:04

Status: Active » Fixed

Submitted by IssueBot on Fri, 08/25/2017 - 01:07

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.