Cockpit installation gone awry

imamouse111 · 13. April 2019

So this is my first time posting here; normally I just lurk and anytime I have a problem I find the solution on a thread, but I've run into an issue that I can't solve so simply. I've even Googled the error and literally only got a single search result.

After following this video from Techno Dad Life, I got to the point of starting Cockpit with sudo systemctl start cockpit, which returned the error A dependency job for cockpit.service failed. See 'journalctl -xe' for details.. I have included a screenshot of that error, as well as the output of systemctl status cockpit.

I tried running the journalctl -xe command and it opened a massive log that I am unable to post the entirety of here since it's so long.

Here is the output of journalctl | grep cockpit:

Spoiler anzeigen

Apr 12 19:10:29 PLEXSERV groupadd[20864]: group added to /etc/group: name=cockpit-ws, GID=125
Apr 12 19:10:29 PLEXSERV groupadd[20864]: group added to /etc/gshadow: name=cockpit-ws
Apr 12 19:10:29 PLEXSERV groupadd[20864]: new group: name=cockpit-ws, GID=125
Apr 12 19:10:29 PLEXSERV useradd[20868]: new user: name=cockpit-ws, UID=115, GID=125, home=/nonexisting, shell=/bin/false
Apr 12 19:10:29 PLEXSERV usermod[20873]: change user 'cockpit-ws' password
Apr 12 19:10:29 PLEXSERV chage[20878]: changed password expiry for cockpit-ws
Apr 12 19:10:30 PLEXSERV systemd[1]: cockpit.socket: Failed to listen on sockets: Address already in use
Apr 12 19:10:31 PLEXSERV systemd[1]: cockpit.socket: Unit entered failed state.
Apr 12 19:36:48 PLEXSERV systemd[1]: cockpit.socket: Failed to listen on sockets: Address already in use
Apr 12 19:36:48 PLEXSERV systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Apr 12 19:36:48 PLEXSERV systemd[1]: cockpit.socket: Unit entered failed state.
Apr 12 19:37:09 PLEXSERV sudo[25402]: root : TTY=pts/1 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl start cockpit
Apr 12 19:37:09 PLEXSERV systemd[1]: cockpit.socket: Failed to listen on sockets: Address already in use
Apr 12 19:37:09 PLEXSERV systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Apr 12 19:37:09 PLEXSERV systemd[1]: cockpit.socket: Unit entered failed state.
Apr 12 19:40:42 PLEXSERV systemd[1]: cockpit.socket: Failed to listen on sockets: Address already in use
Apr 12 19:40:42 PLEXSERV systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Apr 12 19:40:42 PLEXSERV systemd[1]: cockpit.socket: Unit entered failed state.
Apr 12 19:41:49 PLEXSERV systemd[1]: cockpit.socket: Failed to listen on sockets: Address already in use
Apr 12 19:41:49 PLEXSERV systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Apr 12 19:41:49 PLEXSERV systemd[1]: cockpit.socket: Unit entered failed state.
Apr 12 20:15:06 PLEXSERV systemd[1]: cockpit.socket: Failed to listen on sockets: Address already in use
Apr 12 20:15:06 PLEXSERV systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Apr 12 20:15:06 PLEXSERV systemd[1]: cockpit.socket: Unit entered failed state.
Apr 12 20:34:01 PLEXSERV systemd[1]: cockpit.socket: Failed to listen on sockets: Address already in use
Apr 12 20:34:01 PLEXSERV systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Apr 12 20:34:01 PLEXSERV systemd[1]: cockpit.socket: Unit entered failed state.
Apr 12 22:23:43 PLEXSERV systemd[1]: cockpit.socket: Failed to listen on sockets: Address already in use
Apr 12 22:23:43 PLEXSERV systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Apr 12 22:23:43 PLEXSERV systemd[1]: cockpit.socket: Unit entered failed state.
Apr 12 22:36:50 PLEXSERV systemd[1]: cockpit.socket: Failed to listen on sockets: Address already in use
Apr 12 22:36:50 PLEXSERV systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Apr 12 22:36:50 PLEXSERV systemd[1]: cockpit.socket: Unit entered failed state.
Apr 12 22:49:34 PLEXSERV sudo[421]: root : TTY=pts/3 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl status cockpit
Apr 12 22:50:13 PLEXSERV sudo[525]: root : TTY=pts/3 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl status cockpit
Apr 12 22:50:48 PLEXSERV sudo[608]: root : TTY=pts/3 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/apt-get install cockpit-ws
Apr 12 22:51:23 PLEXSERV sudo[683]: root : TTY=pts/3 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl start cockpit
Apr 12 22:51:23 PLEXSERV systemd[1]: cockpit.socket: Failed to listen on sockets: Address already in use
Apr 12 22:51:23 PLEXSERV systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Apr 12 22:51:23 PLEXSERV systemd[1]: cockpit.socket: Unit entered failed state.
Apr 13 07:56:36 PLEXSERV sudo[16981]: root : TTY=pts/3 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl start cockpit
Apr 13 07:56:36 PLEXSERV systemd[1]: cockpit.socket: Failed to listen on sockets: Address already in use
Apr 13 07:56:36 PLEXSERV systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Apr 13 07:56:36 PLEXSERV systemd[1]: cockpit.socket: Unit entered failed state.
Apr 13 07:56:49 PLEXSERV sudo[17027]: root : TTY=pts/3 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl status cockpit
Apr 13 08:28:46 PLEXSERV sudo[25161]: root : TTY=pts/3 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl status cockpit
Apr 13 08:43:56 PLEXSERV sudo[27775]: root : TTY=pts/3 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl start cockpit
Apr 13 08:43:56 PLEXSERV systemd[1]: cockpit.socket: Failed to listen on sockets: Address already in use
Apr 13 08:43:56 PLEXSERV systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Apr 13 08:43:56 PLEXSERV systemd[1]: cockpit.socket: Unit entered failed state.

I'm not sure what else y'all might need from me. Let me know.

Thanks in advance for any help!

imamouse111 · 13. April 2019

Just realized a Docker container that I'm running is using port 9090. Could that be what's causing this error?

imamouse111 · 13. April 2019

OMG facepalm. That's what it was. I switched the port for the docker container and ran systemctl start cockpit and it started right up!

Jetzt mitmachen!