<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Mar 13, 2018 at 4:14 PM, Martin Sivak <span dir="ltr"><<a href="mailto:msivak@redhat.com" target="_blank">msivak@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
make sure the service is actually started and the firewall is<br>
configured properly:<br>
<br>
systemctl status cockpit<br>
firewall-cmd --list-all<br>
<br>
You can make sure all is fine by doing the following:<br>
<br>
systemctl enable cockpit<br>
systemctl start cockpit<br>
firewall-cmd --add-service=cockpit --permanent<br>
firewall-cmd --reload<br>
<br>
Best regards<br>
<span class="gmail-HOEnZb"><font color="#888888"><br>
Martin Sivak<br>
</font></span><div class="gmail-HOEnZb"><div class="gmail-h5"><br></div></div></blockquote><div><br></div><div>Actually from what I understood, the "cockpit service" has to remain configured as "static", while the "cockpit socket" has to be enabled.</div><div>And in cockpit.service unit file in [Unit] section:</div><div><br></div><div><div>Requires=cockpit.socket</div></div><div><br></div><div><br></div><div>So in my case on a plain CentOS server acting as a node I executed:</div><div><br></div><div>systemctl enable cockpit.socket</div><div>systemctl start cockpit.socket</div><div><br></div><div>And I verified I could connect to the hypervisor on port 9090 and then also the status of cockpit.service was "active".</div><div><br></div><div>In messages:</div><div><br></div><div><div>Mar 13 16:30:29 ov42 systemd: Starting Cockpit Web Service Socket.</div><div>Mar 13 16:30:29 ov42 systemd: Listening on Cockpit Web Service Socket.</div></div><div><br></div><div>And when I connect with browser to port 9090 some seconds later:</div><div><br></div><div><div>Mar 13 16:30:47 ov42 systemd: Starting Cockpit Web Service...</div><div>Mar 13 16:30:47 ov42 systemd: Started Cockpit Web Service.</div><div>Mar 13 16:30:47 ov42 cockpit-ws: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert</div><div>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.</div></div><div><div>Mar 13 16:30:57 ov42 cockpit-session: pam_ssh_add: Failed adding some keys</div><div>Mar 13 16:30:57 ov42 systemd-logind: New session 3407 of user root.</div><div>Mar 13 16:30:57 ov42 systemd: Started Session 3407 of user root.</div><div>Mar 13 16:30:57 ov42 systemd: Starting Session 3407 of user root.</div><div>Mar 13 16:30:58 ov42 cockpit-ws: logged in user session</div><div>Mar 13 16:30:58 ov42 cockpit-ws: New connection to session from 10.4.4.12</div></div><div>...</div><div><br></div><div>For further stop/start of cockpit.socket, I see that the start of the cockpit.service is instead immediate when cockpit.socket starts</div><div><br></div><div>eg:</div><div><br></div><div><div>Mar 13 16:37:37 ov42 systemd: Starting Cockpit Web Service Socket.</div><div>Mar 13 16:37:37 ov42 systemd: Listening on Cockpit Web Service Socket.</div><div>Mar 13 16:37:37 ov42 systemd: Starting Cockpit Web Service...</div><div>Mar 13 16:37:37 ov42 systemd: Started Cockpit Web Service.</div><div>Mar 13 16:37:37 ov42 cockpit-ws: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert</div></div><div><br></div><div>Gianluca</div><div><br></div><div><br></div><div><br></div></div></div></div>