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
When attempting to login to the AdminUI, in some circumstances we observe a "Service Unavailable" error that prevents us from logging into the UI. Any existing sessions in the AdminUI remain valid, but metrics do not appear in any of the graphs for those sessions. When this happens, the logs for the nodes contain a large number of errors of the form server/authentication.go:373 Web session error: http: named cookie not present. The rest of the database continues to work as expected.
The issue is fixed by restarting the CockroachDB node.
To Reproduce
Right before this happened, 1000s of new SQL connections were rapidly opened and closed, as can be seen in this graph of active SQL connections:
However, the Admin UI remained in a broken state for several hours after this flood of connections ended. The only fix was to restart CockroachDB on each node in the cluster.
Environment:
CockroachDB v19.1.4
Server OS: Ubuntu
The text was updated successfully, but these errors were encountered:
DuskEagle
added
the
A-webui
Triage label for DB Console (fka admin UI) issues. Add this if nothing else is clear.
label
Oct 25, 2019
This seems like a duplicate of #42828, which goes into a bit more detail. We don't know exactly what causes this connection to close. In the case I observed here, the cluster was under extremely heavy load due to a bad application deployment, while in the case of #42828 a large amount of ranges were transiently unavailable due to CRDB node crashes which occurred shortly after an upgrade from v19.1.5 to v19.2.1.
Describe the problem
When attempting to login to the AdminUI, in some circumstances we observe a "Service Unavailable" error that prevents us from logging into the UI. Any existing sessions in the AdminUI remain valid, but metrics do not appear in any of the graphs for those sessions. When this happens, the logs for the nodes contain a large number of errors of the form
server/authentication.go:373 Web session error: http: named cookie not present
. The rest of the database continues to work as expected.The issue is fixed by restarting the CockroachDB node.
To Reproduce
Right before this happened, 1000s of new SQL connections were rapidly opened and closed, as can be seen in this graph of active SQL connections:
However, the Admin UI remained in a broken state for several hours after this flood of connections ended. The only fix was to restart CockroachDB on each node in the cluster.
Environment:
The text was updated successfully, but these errors were encountered: