bots moved to cockpit-project/bots!
by Sanne Raymaekers
Hello everyone,
So bots moved from cockpit-project/cockpit to the separate github
project: cockpit-project/bots.
How this impacts working on cockpit:
- As bots isn't present any more in cockpit, we added a make target
for convenience: `make bots`. `autogen.sh` will also provide `bots/`.
- Sadly this also means that any open PRs against
cockpit-project/cockpit will need to be rebased on top of master, as
the rebase during testing will fail because of conflicts in `bots/`.
- Projects like starter-kit, cockpit-ostree, cockpit-podman, and
cockpit-composer will continue to work as before. We fixed the
Makefiles to get `bots/` from the new project, all PRs landed already
except for cockpit-composer. If you work on any of these projects, do
`rm -r bots && git pull && make bots`.
Sorry for any inconvenience caused. If you see any funny business
don't hesitate to ping me (Gundersanne on irc) in the #cockpit
channel.
kind regards,
Sanne
4 years, 5 months
unable to log-in to ui
by Albert Szostkiewicz
Hi, I have FreeIPA and Cockpit on the same machine.
Unfortunately, I am unable to login to cockpit.
I have only one keytab: /etc/krb5.keytab (no keytab in /etc/cockpit)
Looks like I have HTTP there already as well
$ ipa service-add HTTP/myserver.mydomain.com(a)MYDOMAIN.COM
ipa: ERROR: service with name "HTTP/myserver.mydomain.com(a)MYDOMAIN.COM" already exists
But cockpit is saying otherwise. Not sure how can I check which keytab file is cocpit trying to read from.
I am also getting 'Unknown certificate' Not sure if there is anything I can/should do about it?
I am not a power user and I would appreciate any suggesions. Thanks!
~~~~
cockpit-ws loaded 1 certificates from /etc/cockpit/ws-certs.d/0-self-signed.cert
cockpit-ws Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
cockpit-ws couldn't read from connection: Peer sent fatal TLS alert: Unknown certificate
cockpit-ws [34B blob data]
cockpit-ws received unknown/invalid credential cookie
cockpit-ws spawning /usr/libexec/cockpit-session
cockpit-ws received authorize challenge
cockpit-ws cockpit-session: gssapi auth failed: Request ticket server HTTP/myserver.mydomain.com(a)MYDOMAIN.COM not found in keytab (ticket kvno 1)
cockpit-ws session initialized
cockpit-ws cockpit-session: authentication-failed Authentication failure
cockpit-ws web service closing
cockpit-session: pam_sss(cockpit:auth): authentication success; logname= uid=0 euid=0 tty= ruser= rhost=10.0.1.4 user=myuser
cockpit-session: pam_ssh_add: Identity added: /home/myuser/.ssh/id_rsa (myuser(a)mydomain.com)
cockpit-session: pam_unix(cockpit:session): session opened for user myuser by (uid=0)
cockpit-ws 3: Permission denied.
cockpit-session: pam_unix(cockpit:session): session closed for user myuser
cockpit-ws cockpit-session: authentication process exited: 256; problem access-denied
cockpit-ws web service closing
cockpit-ws auth is idle
~~~~
~~~~
$ klist -k
Keytab name: FILE:/etc/krb5.keytab
KVNO Principal
---- --------------------------------------------------------------------------
2 host/myserver.mydomain.com(a)MYDOMAIN.COM
2 host/myserver.mydomain.com(a)MYDOMAIN.COM
2 host/myserver.mydomain.com(a)MYDOMAIN.COM
2 host/myserver.mydomain.com(a)MYDOMAIN.COM
2 host/myserver.mydomain.com(a)MYDOMAIN.COM
2 host/myserver.mydomain.com(a)MYDOMAIN.COM
1 nfs/myserver.mydomain.com(a)MYDOMAIN.COM
1 nfs/myserver.mydomain.com(a)MYDOMAIN.COM
1 libvirt/myserver.mydomain.com(a)MYDOMAIN.COM
1 libvirt/myserver.mydomain.com(a)MYDOMAIN.COM
1 vnc/myserver.mydomain.com(a)MYDOMAIN.COM
1 vnc/myserver.mydomain.com(a)MYDOMAIN.COM
~~~~
4 years, 6 months
PCP Alarm Notifications
by Iván Chavero
Hello,
I know that Performance Co-Pilot can send alarms depending on certain
rules and thresholds,
is there any way to make cockpit aware of this alarms?
Thanks!
--
Iván Chavero
Hacker
4 years, 6 months
[Help Wanted] Fedora 31 Talking Points
by Alberto Rodriguez Sanchez
Hi team,
I'm Alberto Rodríguez, and I'm here in the behalf of the Marketing team.
As you should know, we prepare a lists of highlights about each release,
called Talking Points:
Talking points are key highlights of the new release. There are
different types of talking points for different types of people:
general desktop users/everyone, developers, and sysadmins. They are
meant to provide a short, effective answer to the question "What
cool stuff is in the latest release of Fedora?" They are compelling,
not necessarily comprehensive
This points help us, as Marketing team, as well to Ambassadors, to
publicize each release with the news and cool stuff.
For this matter and this release, we have this wiki page:
https://fedoraproject.org/wiki/Fedora_31_talking_points and we will be
happy to include the new things in Fedora 31
You can help us in both ways:
1. Editing the wiki directly with the points.
2. Throwing us the list, and we will put them in the wiki.
Thanks in advance for your help and for your efforts.
Best Regards
4 years, 6 months
Web console restriction
by Louis garcia
My server has four interfaces and I am trying to restrict cockpit to only listen to one of them. I am running fedora 30 with cockpit 202.1. I added listen.conf to systemd as the docs says.
is web console buggy ?
$cat /etc/systemd/system/cockpit.socket.d/listen.conf
[Socket]
ListenStream=
ListenStream=172.16.0.1:9090
When I ssh in I get:
Web console: https://172.16.0.1:9090/ or https://24.51.220.122:9090/
But cockpit only listening on 172.16.0.1:
$ss -lntu
tcp LISTEN 0 128 172.16.0.1:9090 0.0.0.0:*
$ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:ec:ac:cd:65:12 brd ff:ff:ff:ff:ff:ff
inet 24.51.220.122/21 brd 24.51.223.255 scope global dynamic noprefixroute enp1s0
valid_lft 77843sec preferred_lft 77843sec
3: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:ec:ac:cd:65:13 brd ff:ff:ff:ff:ff:ff
inet 172.16.0.1/16 brd 172.16.255.255 scope global noprefixroute enp2s0
valid_lft forever preferred_lft forever
4: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:ec:ac:cd:65:14 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global noprefixroute enp3s0
valid_lft forever preferred_lft forever
5: enp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether 00:ec:ac:cd:65:15 brd ff:ff:ff:ff:ff:ff
4 years, 6 months
System not registered
by ratatouille
Hello!
What is the meaning of registering a system? Can't find any documentation about that.
What is expected to be filled in activation-key and username and password to register
a system? I authenticate to a secondary system with ssh authorized key.
Thank you!
Kind regards
Andreas
4 years, 6 months
cockpit-machines
by George Kirkham
I am new to using Cockpit. When I created a virtual machine I found the following issues;
1) I cannot find a way to add another network device.
2) I cannot find a way to manage (view, add/remove) the sound device (so fundamental).
3) I cannot find a way to manage (view, add/remove) the video device (so fundamental).
4) I cannot find a way to manage (view, add/remove), well any of the virtual hardware devices other than a hard disk drive storage device (the network device can be modified, the cdrom, if one exists can be removed but not re-added).
5) In "Networking" I can add a bridge (this functionality has been removed from Virt-Manager due to the effort to maintain the code), but the bridge is not available in Virtual Machines to be attached to a network device. This is kind of fundamental, or a basic concept, I am so confused why not. I can use virsh to add it, but that is not the point, the UI if it is going to create the bridge, should then add it to the list of virtual devices, or all the user to do so. Virt-Manager used to do this, until bridge creation was removed.
6) Sometimes the virtual cdrom device is available, sometime times it is not visible. It can only be added when the VM is created, after which you can remove it, but you can never attach another dvd/cdrom ISO, or reattach another virtual cdrom drive.
7) there is no way to add a floppy disk drive. A floppy disk drive can be useful for installing specific drivers that can be loaded using floppy disks during the OS installation. For example, virtio drivers for when creating a Windows 10 virtual machine.
8) At first there were 0 Storage Pools, but after creating the VM there were then 2 Storage Pools. I found this a little confusing at the beginning, but did not stop me from creating a VM.
I wonder if I am doing something incorrectly?
4 years, 6 months