IT_Architect
Verified User
- Joined
- Feb 27, 2006
- Messages
- 1,094
Error: When attempting to launch PHPMyAdmin from the CP for the user domain.
Tab shows: 503 Service Unavailable
Page shows: Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Environment:
- FreeBSD 11.2
- PHP FPM 5.3 (default)
- PHP FPM 7.2 2nd (nobody currently using it)
- MySQL 5.6.42
- Sites work fine
- VM was new on 11/11/2018 w/3GB memory 128GB disk, and only using 16%
- There is no Admin/Reseller/User domain.
History:
- I restored the sites to this server from another server using DA's Admin Backup & Restore earlier.
- I restored another to this server about a week ago from another server. Everything still works. I did add an IP address to the server in the address range.
- I would think I would have tested it when I first set it up, but I'm not positive. I do know that all users receive the same error.
Question:
Before I reinvent the wheel trying the varied ideas from the cures on this site, I thought I'd ask if anyone actually knows what the root cause is before I start doing rituals like updating and recompiling everything and see nothing change, or end up fixing it and never knowing the cause.
Thanks!
Tab shows: 503 Service Unavailable
Page shows: Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Environment:
- FreeBSD 11.2
- PHP FPM 5.3 (default)
- PHP FPM 7.2 2nd (nobody currently using it)
- MySQL 5.6.42
- Sites work fine
- VM was new on 11/11/2018 w/3GB memory 128GB disk, and only using 16%
- There is no Admin/Reseller/User domain.
History:
- I restored the sites to this server from another server using DA's Admin Backup & Restore earlier.
- I restored another to this server about a week ago from another server. Everything still works. I did add an IP address to the server in the address range.
- I would think I would have tested it when I first set it up, but I'm not positive. I do know that all users receive the same error.
Code:
# ps -ax | grep fpm
6592 - Ss 0:19.04 php-fpm53: master process (/usr/local/php53/etc/php-fpm.conf) (php-fpm53)
6594 - Ss 0:01.88 php-fpm72: master process (/usr/local/php72/etc/php-fpm.conf) (php-fpm72)
57331 - S 0:20.93 php-fpm53: pool findlocn (php-fpm53)
57332 - S 0:22.70 php-fpm53: pool findlocn (php-fpm53)
57333 - S 0:24.96 php-fpm53: pool findlocn (php-fpm53)
57840 - S 0:20.11 php-fpm53: pool findlocn (php-fpm53)
58912 - S 0:09.22 php-fpm53: pool findlocn (php-fpm53)
58917 - S 0:22.83 php-fpm53: pool findlocw (php-fpm53)
58918 - S 0:05.21 php-fpm53: pool findlocn (php-fpm53)
58970 - S 0:19.34 php-fpm53: pool findlocw (php-fpm53)
58971 - S 0:18.57 php-fpm53: pool findlocw (php-fpm53)
59369 - S 0:02.05 php-fpm53: pool saveonh (php-fpm53)
59421 - S 0:11.03 php-fpm53: pool findlocw (php-fpm53)
59422 - S 0:09.65 php-fpm53: pool findlocw (php-fpm53)
59454 - S 0:08.42 php-fpm53: pool findlocw (php-fpm53)
59486 - S 0:00.70 php-fpm53: pool saveonh (php-fpm53)
59837 - S 0:01.21 php-fpm53: pool findlocw (php-fpm53)
Question:
Before I reinvent the wheel trying the varied ideas from the cures on this site, I thought I'd ask if anyone actually knows what the root cause is before I start doing rituals like updating and recompiling everything and see nothing change, or end up fixing it and never knowing the cause.
Thanks!
Last edited: