Lost foreman 3.14.0 access

Support
1

Hello,

Problem:

  • After the upgrade in 3.14.0 from 3.12.0 we have some issues with the UI and some API call. We lost access, and response is very long. .
  • We had 4 frontend foreman servers before upgraded, there was no issue, even on one host. (More than 3years)
  • the login page is not available sometimes (Proxy Error) and after few times it’s ok.
  • lot of hosts in OutOfSync status,
  • 2000 hosts.

Expected outcome:
Get some idea to fix the issue, get more informations.

Foreman and Proxy versions:

  • Foreman 3.14.0
  • puppetserver version: 8.7.0

Distribution and version:

  • Debian 12 bookworm

Other relevant data:

  • Message when foreman crash on the UI.
    Proxy Error
    The proxy server received an invalid response from an upstream server.
    The proxy server could not handle the request
    Reason. Error reading remote server

** We tried to dig on logs :

  • We checked in production.log it seems, there are no issue happend
  • We checked apache logs, no really messages related to this problem
  • We checked if we have network issue: ( ping, telnet on port … )

Have you some ideas to deal with, or where can we see more details ?
Thanks

image
image951×343 68.8 KB

2

Did you do a direct upgrade from 3.12 to 3.14
Did you make any firewall changes on the host?

What does the below command show?
foreman-maintain service status

4

Thank you for your reply,

Did you do a direct upgrade from 3.12 to 3.14
yes we did

Did you make any firewall changes on the host?
no change to firewall

We are on Debian 12 bookworm, we will install the tools to test the command.
foreman-maintain service status

5

Generally its best to upgrade from verson to the next magor version. Ie 3.12>3.13>3.14. It takes more time but thats the recommended path.

6

If you have a snapshot prior to upgrade. I would restore it then try upgrading from 3.12>3.13>3.14.