systemctl enable cockpit.socket systemctl start cockpit.socket
There is slight difference on when the service gets activated (on startup vs. on first access), but I guess either way is fine. The documentation indeed mentions the socket way: http://cockpit-project.org/guide/133/startup.html Best regards Martin Sivak On Tue, Mar 13, 2018 at 4:45 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Tue, Mar 13, 2018 at 4:14 PM, Martin Sivak <msivak@redhat.com> wrote:
Hi,
make sure the service is actually started and the firewall is configured properly:
systemctl status cockpit firewall-cmd --list-all
You can make sure all is fine by doing the following:
systemctl enable cockpit systemctl start cockpit firewall-cmd --add-service=cockpit --permanent firewall-cmd --reload
Best regards
Martin Sivak
Actually from what I understood, the "cockpit service" has to remain configured as "static", while the "cockpit socket" has to be enabled. And in cockpit.service unit file in [Unit] section:
Requires=cockpit.socket
So in my case on a plain CentOS server acting as a node I executed:
systemctl enable cockpit.socket systemctl start cockpit.socket
And I verified I could connect to the hypervisor on port 9090 and then also the status of cockpit.service was "active".
In messages:
Mar 13 16:30:29 ov42 systemd: Starting Cockpit Web Service Socket. Mar 13 16:30:29 ov42 systemd: Listening on Cockpit Web Service Socket.
And when I connect with browser to port 9090 some seconds later:
Mar 13 16:30:47 ov42 systemd: Starting Cockpit Web Service... Mar 13 16:30:47 ov42 systemd: Started Cockpit Web Service. Mar 13 16:30:47 ov42 cockpit-ws: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert Mar 13 16:30:47 ov42 cockpit-ws: couldn't read from connection: Error reading data from TLS socket: A TLS fatal alert has been received. Mar 13 16:30:57 ov42 cockpit-session: pam_ssh_add: Failed adding some keys Mar 13 16:30:57 ov42 systemd-logind: New session 3407 of user root. Mar 13 16:30:57 ov42 systemd: Started Session 3407 of user root. Mar 13 16:30:57 ov42 systemd: Starting Session 3407 of user root. Mar 13 16:30:58 ov42 cockpit-ws: logged in user session Mar 13 16:30:58 ov42 cockpit-ws: New connection to session from 10.4.4.12 ...
For further stop/start of cockpit.socket, I see that the start of the cockpit.service is instead immediate when cockpit.socket starts
eg:
Mar 13 16:37:37 ov42 systemd: Starting Cockpit Web Service Socket. Mar 13 16:37:37 ov42 systemd: Listening on Cockpit Web Service Socket. Mar 13 16:37:37 ov42 systemd: Starting Cockpit Web Service... Mar 13 16:37:37 ov42 systemd: Started Cockpit Web Service. Mar 13 16:37:37 ov42 cockpit-ws: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Gianluca