Skip to content
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

Odd issue in cluster configuration PF 13.2 #8204

Open
si-prio opened this issue Jul 3, 2024 · 0 comments
Open

Odd issue in cluster configuration PF 13.2 #8204

si-prio opened this issue Jul 3, 2024 · 0 comments

Comments

@si-prio
Copy link

si-prio commented Jul 3, 2024

Describe the bug
After running the cluster for some hours (it is a cluster with 3 servers), when acessing back again to the PF frontend to check or edit some new configuration, the front end just get irresponsive and timeouts, giving error 504.

The errors observed during the issue are just as follows (these logs are obtained from the node 1 of the cluster):

imagem

After some minutes, the docker/service pfperf-api restarts itself (maybe some self healing routine) and after that I am able to access again to the frontend:

imagem

imagem

The issue gets also "fixed" if I restart manually the pfperf-api service.

To Reproduce
Steps to reproduce the behavior:

  1. Sometimes acessing to the frontend or saving a new configuration after some hours, the frontend gets irresponsive.

Additional context
The 3 servers are running Rocky Linux 8.10 with the lastest PF Version 13.2. If you need more logs or info let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant