System hostname
matthew…
Operating system
Ubuntu Linux 22.04.2
Webmin version
2.021
Usermin version
1.861
Virtualmin version
7.7 Pro
Authentic theme version
20.21
Time on system
Wednesday, July 26, 2023 3:21 PM
Kernel and CPU
Linux 5.15.0-78-generic on x86_64
Processor information
Intel(R) Xeon(R) CPU X5650 @ 2.67GHz, 24 cores
CPU temperatures
Core 1: 30°CCore 2: 36°CCore 3: 37°CCore 9: 37°CCore 10: 38°CCore 11: 35°CCore 1: 40°CCore 2: 39°CCore 3: 40°CCore 9: 32°CCore 10: 40°CCore 11: 39°C
System uptime
32 minutes
Running processes
335
CPU load averages
0.35 (1 min) 0.24 (5 mins) 0.20 (15 mins)
Real memory
2.21 GiB used / 981.89 MiB cached / 62.87 GiB total
Virtual memory
0 bytes used / 7.99 GiB total
Local disk space
22.49 GiB used / 77.27 GiB free / 99.77 GiB total
Package updates
All installed packages are up to date
This is my apache error_file picture.
I have 5 domains that was working on previous OS ubuntu version. Now 3 of them have this error:
Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
the other 2 domains work okay…
Here is what is happening with Apache… my error file
[Wed Jul 26 15:30:17.338139 2023] [proxy_fcgi:error] [pid 1889:tid 140439709537856] [client 23.29.117.20:50988] AH01079: failed to make connection to backend: httpd-UDS
[Wed Jul 26 15:30:17.435448 2023] [proxy:error] [pid 1889:tid 140440086218304] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /var/php-fpm/168944981673940.sock () failed
[Wed Jul 26 15:30:17.435470 2023] [proxy_fcgi:error] [pid 1889:tid 140440086218304] [client 23.29.117.20:57696] AH01079: failed to make connection to backend: httpd-UDS
[Wed Jul 26 15:30:17.444222 2023] [proxy:error] [pid 1890:tid 140439030056512] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /var/php-fpm/168944981673940.sock ( ) failed
[Wed Jul 26 15:30:17.444249 2023] [proxy_fcgi:error] [pid 1890:tid 140439030056512] [client 173.243.124.110:18418] AH01079: failed to make connection to backend: httpd-UDS
[Wed Jul 26 15:30:17.962913 2023] [proxy:error] [pid 1890:tid 140438426076736] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /var/php-fpm/168944981673940.sock () failed
[Wed Jul 26 15:30:17.962938 2023] [proxy_fcgi:error] [pid 1890:tid 140438426076736] [client 209.249.147.72:52520] AH01079: failed to make connection to backend: httpd-UDS
[Wed Jul 26 15:30:18.063786 2023] [proxy:error] [pid 1890:tid 140440086218304] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /var/php-fpm/168944981673940.sock ( ) failed
[Wed Jul 26 15:30:18.063811 2023] [proxy_fcgi:error] [pid 1890:tid 140440086218304] [client 209.249.147.72:17136] AH01079: failed to make connection to backend: httpd-UDS
[Wed Jul 26 15:30:28.179492 2023] [proxy:error] [pid 1889:tid 140438946162240] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /var/php-fpm/168944981673940.sock (*) failed
[Wed Jul 26 15:30:28.179528 2023] [proxy_fcgi:error] [pid 1889:tid 140438946162240] [client 100.69.243.40:17804] AH01079: failed to make connection to backend: httpd-UDS
Joe
July 27, 2023, 2:44am
4
OK, this looks like PHP-FPM service isn’t running, or it’s trying to communicate with the wrong one.
Did you run Re-Check Configuration after you upgraded your system? You have to do that because the versions of everything changed.
Check the status of php-fpm
service (possibly other similarly name services if you have installed other PHP versions).
And, probably want to restart it just to be sure it’s in a happy state, or will give us some errors we can work with.
systemctl restart php-fpm
If the problem persists, check Validate Virtual Servers for any clues.
1 Like
Now I am getting this error for php info
Failed to connect to 208.104.147.195:443 : Connection refused
port 443 ??? the 195 is my correct server ip addr
Answer:
Your Apache is not listening on port 443 . You configured your VirtualHost only for HTTP, not fot HTTPS. Configure a second VirtualHost with Port 443 and your certificates and make sure you have a Listen 443
directive in your Apache config. Your certificates don’t belong in the :80
VirtualHost.
The above was based on wrong information in the question. Whatever you did in the meantime, your server is now rechable via HTTPS.
by the way… all my users from old server .194 are now finally showing up okay. I don’t understand the delay, unless it was a CRON job that imported them into the new server.
These issues have now been resolved for this version of OS only.
system
Closed
September 26, 2023, 12:39pm
9
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.