GUI times out if I go to Nodes List
kpiti
23 Posts
November 24, 2023, 6:31 pmQuote from kpiti on November 24, 2023, 6:31 pmHi,
I seem to have a problem with displaying the Manage nodes submenu. Everything else seems to be working ok, this one returns ngnix 504 Gateway Time-out. It's happening on all MGR nodes. I've tried to restart petasan-admin and it's been like this since v3.1.0, we've upgraded to v3.2.1 and it's still the same. In nginx log I get
2023/11/24 19:00:18 [error] 3480#3480: *123 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.12.13.203, server: 10.12.13.53, request: "GET /node/list HTTP/1.1", upstream: "http://127.0.0.1:5002/node/list", host: "localhost:13013", referrer: "https://localhost:13013/"
I can see some python running on port 5002:
# netstat -plnt | grep 5002
tcp 0 0 127.0.0.1:5002 0.0.0.0:* LISTEN 2881/python3
so it's not for no listening.. Couldn't find anything related in petasan.log either.
I don't know since when it's down. I did remove a dead disk by hand and am waiting for a replacement one some 2 weeks ago, didn't work at the time..
As said, everything else seems to be working, health is OK... Pointers welcome..
Cheers,
Jure
Hi,
I seem to have a problem with displaying the Manage nodes submenu. Everything else seems to be working ok, this one returns ngnix 504 Gateway Time-out. It's happening on all MGR nodes. I've tried to restart petasan-admin and it's been like this since v3.1.0, we've upgraded to v3.2.1 and it's still the same. In nginx log I get
2023/11/24 19:00:18 [error] 3480#3480: *123 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.12.13.203, server: 10.12.13.53, request: "GET /node/list HTTP/1.1", upstream: "http://127.0.0.1:5002/node/list", host: "localhost:13013", referrer: "https://localhost:13013/"
I can see some python running on port 5002:
# netstat -plnt | grep 5002
tcp 0 0 127.0.0.1:5002 0.0.0.0:* LISTEN 2881/python3
so it's not for no listening.. Couldn't find anything related in petasan.log either.
I don't know since when it's down. I did remove a dead disk by hand and am waiting for a replacement one some 2 weeks ago, didn't work at the time..
As said, everything else seems to be working, health is OK... Pointers welcome..
Cheers,
Jure
GUI times out if I go to Nodes List
kpiti
23 Posts
Quote from kpiti on November 24, 2023, 6:31 pmHi,
I seem to have a problem with displaying the Manage nodes submenu. Everything else seems to be working ok, this one returns ngnix 504 Gateway Time-out. It's happening on all MGR nodes. I've tried to restart petasan-admin and it's been like this since v3.1.0, we've upgraded to v3.2.1 and it's still the same. In nginx log I get
2023/11/24 19:00:18 [error] 3480#3480: *123 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.12.13.203, server: 10.12.13.53, request: "GET /node/list HTTP/1.1", upstream: "http://127.0.0.1:5002/node/list", host: "localhost:13013", referrer: "https://localhost:13013/"
I can see some python running on port 5002:
# netstat -plnt | grep 5002
tcp 0 0 127.0.0.1:5002 0.0.0.0:* LISTEN 2881/python3
so it's not for no listening.. Couldn't find anything related in petasan.log either.
I don't know since when it's down. I did remove a dead disk by hand and am waiting for a replacement one some 2 weeks ago, didn't work at the time..
As said, everything else seems to be working, health is OK... Pointers welcome..
Cheers,
Jure
Hi,
I seem to have a problem with displaying the Manage nodes submenu. Everything else seems to be working ok, this one returns ngnix 504 Gateway Time-out. It's happening on all MGR nodes. I've tried to restart petasan-admin and it's been like this since v3.1.0, we've upgraded to v3.2.1 and it's still the same. In nginx log I get
2023/11/24 19:00:18 [error] 3480#3480: *123 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.12.13.203, server: 10.12.13.53, request: "GET /node/list HTTP/1.1", upstream: "http://127.0.0.1:5002/node/list", host: "localhost:13013", referrer: "https://localhost:13013/"
I can see some python running on port 5002:
# netstat -plnt | grep 5002
tcp 0 0 127.0.0.1:5002 0.0.0.0:* LISTEN 2881/python3
so it's not for no listening.. Couldn't find anything related in petasan.log either.
I don't know since when it's down. I did remove a dead disk by hand and am waiting for a replacement one some 2 weeks ago, didn't work at the time..
As said, everything else seems to be working, health is OK... Pointers welcome..
Cheers,
Jure