-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Resolved] All websites that use Apache (Nginx forwards requests to Apache) show 502 Bad Gateway after upgrade #372
Comments
@SandakovMM Do you have any ideas about that problem/bug? |
After another attempt with the migration script 1.4.3, the same error occurred again. Short Solution: Apache Module watchdog was not enabled after Upgrade to AlmaLinux 8. After careful analysis, I found that the Apache service had not started and was in an error state. I checked the status of the Apache service on AlmaLinux 8 with the following command: systemctl status httpd After this service could not be set to the status "Active: active (running)" even after a restart, I checked the log file: cat /etc/httpd/logs/error_log The output provided a clue as to what the problem was: [Sun Oct 27 20:53:29.495534 2024] [lbmethod_heartbeat:notice] [pid 93807:tid 140021804460352] AH02282: No slotmem from mod_heartmonitor [Sun Oct 27 20:53:29.617938 2024] [proxy_hcheck:crit] [pid 93807:tid 140021804460352] AH03262: mod_watchdog is required After the command to monitor the ports on which Apache must listen also produced no output: netstat -tunap | grep httpd I found it on the Internet: https://support.plesk.com/hc/en-us/articles/12377651410839-Unable-to-start-Apache-on-a-Plesk-server-AH02093-mod-watchdog-is-required After I applied this KB article (Tools & Settings --> Apache Webserver --> check the watchdog box), the problem was solved. By the way, temporarily disabling and re-enabling nginx reverse proxy didn't help before finding a solution. The problem remained. Nevertheless, this test may be helpful for one or the other, so I am also linking this KB article: nginx status: /usr/local/psa/admin/sbin/nginxmng --status |
Hello @fbroen |
same here. Any solution? |
[Fri Jan 03 19:19:19.036427 2025] [lbmethod_heartbeat:notice] [pid 47337:tid 140689681946944] AH02282: No slotmem from mod_heartmonitor |
This trick is worked:
|
The upgrade from CentOS 7.9 to AlmaLinux 8 went smoothly. The upgrade tool also did not indicate any problems. After the upgrade was complete, all websites that only used NGINX in proxy mode were no longer accessible. Only the websites that only used NGINX worked.
We have already tried to check for errors and repair them using the Plesk "Diagnostics & Repair" function. No improvement or change could be found here.
We also tried to follow these instructions, which also did not work: https://support.plesk.com/hc/en-us/articles/12377559249559-Site-does-not-work-on-PHP-FPM-handler-on-Plesk-server-503-service-unavailable
We also checked fail2ban. All server IP addresses are on the whitelist. We also deleted/activated all blocked IP addresses again for testing purposes.
Attached are screenshots of the problem and the errors.
I hope there is a quick fix for this. I had to reset the server to a snapshot before the upgrade.
Best regards
Falk
The text was updated successfully, but these errors were encountered: