After I logged in to the page, it showed that the server was disconnected #20644
Comments
|
This isn't obvious -- You only showed the full journal from 14:29 on, but the cockpit action happened 7 minutes before. What would be more interesting is to open cockpit's log in page, then It sounds like either the cockpit-wsinstance crashed or something in your session crashes. More likely the latter, given how many errors your GNOME session login at 14:29 shows.. |
|
@martinpitt Thank you for your reply Starting from 21:00:52, these content appeared. These are all content from 21:00:48 to 21:00:55 |
|
Something very funky happens on your system. It's trying to start all sorts of GNOME services in the cockpit session, and they all fail. That seems to kill the whole session: I don't know what's going on there, sorry. |
|
@martinpitt |
|
Maybe this is the reason. |
|
@martinpitt |
|
@StupidYang I'm glad it's working! However, it still doesn't answer the question why logging into cockpit tries to start anything graphical in the first place.. ❓ But oh well.. 😁 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Explain what happens
Version of Cockpit
cockpit 264-1ubuntu0.22.04.1 cockpit-bridge 264-1ubuntu0.22.04.1 cockpit-machines 265-1 cockpit-networkmanager 264-1ubuntu0.22.04.1 cockpit-packagekit 264-1ubuntu0.22.04.1 cockpit-storaged 264-1ubuntu0.22.04.1 cockpit-system 264-1ubuntu0.22.04.1 cockpit-ws 264-1ubuntu0.22.04.1
Where is the problem in Cockpit?
None
Server operating system
None
Server operating system version
ubuntu 22.04
What browsers are you using?
No response
System log
The text was updated successfully, but these errors were encountered: