You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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):
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:
The issue gets also "fixed" if I restart manually the pfperf-api service.
To Reproduce
Steps to reproduce the behavior:
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.
The text was updated successfully, but these errors were encountered:
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):
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:
The issue gets also "fixed" if I restart manually the pfperf-api service.
To Reproduce
Steps to reproduce the behavior:
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.
The text was updated successfully, but these errors were encountered: