Hi
As you can see from the systemctl status, the difference is caused due to
the preset rule for cockpit.socket, which is enabled on the node-ng based
system, and disabled on your regular centos based system.
If you take a look at the cockpit postinstall script, you'd see something
like:
On Sat, Dec 23, 2017 at 11:18 AM, Gianluca Cecchi wrote:
> On Fri, Dec 22, 2017 at 10:22 PM, Sandro Bonazzola
> wrote:
>
>>
>>
>> Il 22 Dic 2017 10:12 PM, "Yaniv Kaul" ha scritto:
>>
>>
>>
>> On Dec 22, 2017 7:33 PM, "Gianluca
On Sat, Dec 23, 2017 at 11:18 AM, Gianluca Cecchi wrote:
> On Fri, Dec 22, 2017 at 10:22 PM, Sandro Bonazzola
> wrote:
>
>>
>>
>> Il 22 Dic 2017 10:12 PM, "Yaniv Kaul" ha scritto:
>>
>>
>>
>> On Dec 22, 2017 7:33 PM, "Gianluca
On Fri, Dec 22, 2017 at 10:22 PM, Sandro Bonazzola
wrote:
>
>
> Il 22 Dic 2017 10:12 PM, "Yaniv Kaul" ha scritto:
>
>
>
> On Dec 22, 2017 7:33 PM, "Gianluca Cecchi"
> wrote:
>
> Hello, after upgrading engine and then plain
Il 22 Dic 2017 10:12 PM, "Yaniv Kaul" ha scritto:
On Dec 22, 2017 7:33 PM, "Gianluca Cecchi"
wrote:
Hello, after upgrading engine and then plain CentOS 7.4 host from 4.1 to
4.2, I see in host section if I select line for the host, right click and
On Dec 22, 2017 7:33 PM, "Gianluca Cecchi"
wrote:
Hello, after upgrading engine and then plain CentOS 7.4 host from 4.1 to
4.2, I see in host section if I select line for the host, right click and
host console... That tries to go to the typical 9090 cockpit Port of
Hello, after upgrading engine and then plain CentOS 7.4 host from 4.1 to
4.2, I see in host section if I select line for the host, right click and
host console... That tries to go to the typical 9090 cockpit Port of
node-ng...
Is this an error or in 4.2 the access to host console is for plain OS
7 matches
Mail list logo