cockpit not config in tumbleweed
Guys, Was hoping to get cockpit working in Tumbleweed, but when I went to enable it to run it I get this message systemctl enable cockpit The unit files have no installation config (WantedBy=, RequiredBy=, Also=, Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Cockpit is running on 9090, but when you log in, you get a white page. lycanthrope:/etc/cockpit # zypper search cockpit Loading repository data... Reading installed packages... S | Name | Summary | Type ---+--------------------------+------------------------------------------------------------------------------+-------- i+ | cockpit | Web Console for Linux servers | package i | cockpit-bridge | Cockpit bridge server-side component | package | cockpit-devel | Development files for for Cockpit | package i+ | cockpit-doc | Cockpit deployment and developer guide | package | cockpit-kdump | Cockpit user interface for kernel crash dumping | package i+ | cockpit-machines | Cockpit user interface for virtual machines | package i+ | cockpit-networkmanager | Cockpit user interface for networking, using NetworkManager | package i+ | cockpit-packagekit | Cockpit user interface for packages | package i+ | cockpit-pcp | Cockpit PCP integration | package i | cockpit-podman | Cockpit component for Podman containers | package i+ | cockpit-storaged | Cockpit user interface for storage, using udisks | package i | cockpit-system | Cockpit admin interface package for configuring and troubleshooting a system | package | cockpit-tests | Tests for Cockpit | package i+ | cockpit-ws | Cockpit Web Service | package i+ | microos_cockpit | Web based remote system managemet | pattern i+ | patterns-microos-cockpit | Web based remote system managemet | package -- Terror PUP a.k.a Chuck "PUP" Payne ----------------------------------------- Discover it! Enjoy it! Share it! openSUSE Linux. ----------------------------------------- openSUSE -- Terrorpup openSUSE Ambassador/openSUSE Member skype,twiiter,identica,friendfeed -- terrorpup freenode(irc) --terrorpup/lupinstein Register Linux Userid: 155363 openSUSE Community Member since 2008.
Never mind, it wasn't clear that cockpit.socket need to be enable, and not cockpit. Sorry. On Sun, Sep 5, 2021 at 1:06 AM Chuck Payne <terrorpup@gmail.com> wrote:
Guys,
Was hoping to get cockpit working in Tumbleweed, but when I went to enable it to run it I get this message
systemctl enable cockpit
The unit files have no installation config (WantedBy=, RequiredBy=, Also=, Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified.
Cockpit is running on 9090, but when you log in, you get a white page.
lycanthrope:/etc/cockpit # zypper search cockpit Loading repository data... Reading installed packages...
S | Name | Summary | Type
---+--------------------------+------------------------------------------------------------------------------+-------- i+ | cockpit | Web Console for Linux servers | package i | cockpit-bridge | Cockpit bridge server-side component | package | cockpit-devel | Development files for for Cockpit | package i+ | cockpit-doc | Cockpit deployment and developer guide | package | cockpit-kdump | Cockpit user interface for kernel crash dumping | package i+ | cockpit-machines | Cockpit user interface for virtual machines | package i+ | cockpit-networkmanager | Cockpit user interface for networking, using NetworkManager | package i+ | cockpit-packagekit | Cockpit user interface for packages | package i+ | cockpit-pcp | Cockpit PCP integration | package i | cockpit-podman | Cockpit component for Podman containers | package i+ | cockpit-storaged | Cockpit user interface for storage, using udisks | package i | cockpit-system | Cockpit admin interface package for configuring and troubleshooting a system | package | cockpit-tests | Tests for Cockpit | package i+ | cockpit-ws | Cockpit Web Service | package i+ | microos_cockpit | Web based remote system managemet | pattern i+ | patterns-microos-cockpit | Web based remote system managemet | package
-- Terror PUP a.k.a Chuck "PUP" Payne ----------------------------------------- Discover it! Enjoy it! Share it! openSUSE Linux. ----------------------------------------- openSUSE -- Terrorpup openSUSE Ambassador/openSUSE Member skype,twiiter,identica,friendfeed -- terrorpup freenode(irc) --terrorpup/lupinstein Register Linux Userid: 155363
openSUSE Community Member since 2008.
-- Terror PUP a.k.a Chuck "PUP" Payne ----------------------------------------- Discover it! Enjoy it! Share it! openSUSE Linux. ----------------------------------------- openSUSE -- Terrorpup openSUSE Ambassador/openSUSE Member skype,twiiter,identica,friendfeed -- terrorpup freenode(irc) --terrorpup/lupinstein Register Linux Userid: 155363 openSUSE Community Member since 2008.
participants (1)
-
Chuck Payne