Re: Problems reinstalling bootloader after a Windows update
On 12/4/21 19:39, Adam Mercer wrote: On Sat, Dec 4, 2021 at 7:12 PM Samuel Sieb wrote: No OS should touch any files it doesn't own in the ESP. Did it really remove the bootloader? A more likely option is that it changed the BIOS boot order. Can you bring up the boot menu? Do you see the Fedora option there? That was my initial thought, so I booted into UEFI and the Windows Boot Manager had been made the default boot option, Fedora was still listed so I selected that. The grub menu came up with all my kernels listed but selecting one just resulted in an error about being unable to find a file or something like that. Also the option in grub for booting into Windows resulted in a similar error. Hence me trying to reinstall the bootloader. This system was originally installed on Fedora 32 or 33 and upgraded so it may be time for a reinstall, I have backups so nothing will be lost apart from time. Cheers Adam Try a USB with Supergrub2 2.04S1 for UEFI to boot your system ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: selinux changes: why?
On 05/12/21 17:49 -0500, Jonathan Billings wrote: On Dec 5, 2021, at 17:11, Nick Urbanik wrote: $ sudo restorecon -rv * Relabeled /etc/cups/client.conf from system_u:object_r:cupsd_etc_t:s0 to system_u:object_r:etc_t:s0 Relabeled /etc/cups/cupsd.conf.default from system_u:object_r:cupsd_etc_t:s0 to system_u:object_r:cupsd_rw_etc_t:s0 Can you tell us what version of the SELinux policy you have? Maybe “rpm -qa | grep selinux”. $ rpm -qa | grep selinux rpm-plugin-selinux-4.17.0-1.fc35.x86_64 dnfdaemon-selinux-0.3.20-7.fc35.noarch libselinux-3.3-1.fc35.x86_64 libselinux-utils-3.3-1.fc35.x86_64 python3-libselinux-3.3-1.fc35.x86_64 container-selinux-2.170.0-2.fc35.noarch fail2ban-selinux-0.11.2-9.fc35.noarch flatpak-selinux-1.12.2-1.fc35.noarch libselinux-3.3-1.fc35.i686 nagios-selinux-4.4.6-6.fc35.noarch snapd-selinux-2.53.2-1.fc35.noarch selinux-policy-35.6-1.fc35.noarch selinux-policy-targeted-35.6-1.fc35.noarch I see a lot of policy change related updates there, as well as stuff in /bin having generic context instead of specific context. Also, how do you update? Command line DNF? PackageKit? GNOME software? Mostly with dnf-automatic, and command-line dnf. -- Nick Urbanik http://nicku.org ni...@nicku.org GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: selinux changes: why?
> On Dec 5, 2021, at 17:11, Nick Urbanik wrote: > > $ sudo restorecon -rv * > Relabeled /etc/cups/client.conf from system_u:object_r:cupsd_etc_t:s0 to > system_u:object_r:etc_t:s0 > Relabeled /etc/cups/cupsd.conf.default from system_u:object_r:cupsd_etc_t:s0 > to system_u:object_r:cupsd_rw_etc_t:s0 Can you tell us what version of the SELinux policy you have? Maybe “rpm -qa | grep selinux”. I see a lot of policy change related updates there, as well as stuff in /bin having generic context instead of specific context. Also, how do you update? Command line DNF? PackageKit? GNOME software? — Jonathan Billings ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: selinux changes: why?
On 05/12/21 09:59 -0500, Jonathan Billings wrote: On Dec 5, 2021, at 05:44, Nick Urbanik wrote: I am regularly having selinux labels changing. This should never happen, but it does quite continuously; many critical executables lose their correct label, preventing me from logging in without a relabel. This is Fedora 35, upgraded over quite a few generations of Fedora. The root file system is ext4 on luks encryption on RAID 1. Any suggestions on how to troubleshoot and determine the cause? I've never had selinux labels decay before. I’ve never heard of this happening except in cases where file systems were mounted in alternate locations and written to. (For example, a chrooted OS mounted on a livecd) Maybe it would help if you showed an example of paths and what context you found them in? Knowing the incorrect context can sometimes help identify what is causing it. $ sudo restorecon -rv * Relabeled /etc/cups/client.conf from system_u:object_r:cupsd_etc_t:s0 to system_u:object_r:etc_t:s0 Relabeled /etc/cups/cupsd.conf.default from system_u:object_r:cupsd_etc_t:s0 to system_u:object_r:cupsd_rw_etc_t:s0 Relabeled /etc/cups/printers.conf from system_u:object_r:cupsd_etc_t:s0 to system_u:object_r:cupsd_rw_etc_t:s0 Relabeled /etc/cups/cupsd.conf.rpmnew from system_u:object_r:cupsd_etc_t:s0 to system_u:object_r:cupsd_rw_etc_t:s0 Relabeled /etc/strongswan/ipsec.secrets from system_u:object_r:ipsec_conf_file_t:s0 to system_u:object_r:ipsec_key_file_t:s0 Relabeled /etc/sysconfig/snapd from system_u:object_r:etc_t:s0 to system_u:object_r:snappy_config_t:s0 $ sudo restorecon -rv * Relabeled /usr/sbin/charon-systemd from system_u:object_r:bin_t:s0 to system_u:object_r:ipsec_exec_t:s0 Relabeled /usr/sbin/chpasswd from system_u:object_r:bin_t:s0 to system_u:object_r:passwd_exec_t:s0 Relabeled /usr/sbin/cryptsetup from system_u:object_r:bin_t:s0 to system_u:object_r:lvm_exec_t:s0 Relabeled /usr/sbin/cupsd from system_u:object_r:bin_t:s0 to system_u:object_r:cupsd_exec_t:s0 Relabeled /usr/sbin/fsck.btrfs from system_u:object_r:bin_t:s0 to system_u:object_r:fsadm_exec_t:s0 Relabeled /usr/sbin/fsck.exfat from system_u:object_r:bin_t:s0 to system_u:object_r:fsadm_exec_t:s0 Relabeled /usr/sbin/groupadd from system_u:object_r:bin_t:s0 to system_u:object_r:groupadd_exec_t:s0 Relabeled /usr/sbin/groupdel from system_u:object_r:bin_t:s0 to system_u:object_r:groupadd_exec_t:s0 Relabeled /usr/sbin/groupmod from system_u:object_r:bin_t:s0 to system_u:object_r:groupadd_exec_t:s0 Relabeled /usr/sbin/grpconv from system_u:object_r:bin_t:s0 to system_u:object_r:admin_passwd_exec_t:s0 Relabeled /usr/sbin/grpunconv from system_u:object_r:bin_t:s0 to system_u:object_r:admin_passwd_exec_t:s0 Relabeled /usr/sbin/keepalived from unconfined_u:object_r:bin_t:s0 to unconfined_u:object_r:keepalived_exec_t:s0 Relabeled /usr/sbin/lpadmin from system_u:object_r:bin_t:s0 to system_u:object_r:lpr_exec_t:s0 Relabeled /usr/sbin/lpc.cups from system_u:object_r:bin_t:s0 to system_u:object_r:lpr_exec_t:s0 Relabeled /usr/sbin/lpinfo from system_u:object_r:bin_t:s0 to system_u:object_r:lpr_exec_t:s0 Relabeled /usr/sbin/lpmove from system_u:object_r:bin_t:s0 to system_u:object_r:lpr_exec_t:s0 Relabeled /usr/sbin/mkfs.btrfs from system_u:object_r:bin_t:s0 to system_u:object_r:fsadm_exec_t:s0 Relabeled /usr/sbin/mkfs.exfat from system_u:object_r:bin_t:s0 to system_u:object_r:fsadm_exec_t:s0 Relabeled /usr/sbin/newusers from system_u:object_r:bin_t:s0 to system_u:object_r:useradd_exec_t:s0 Relabeled /usr/sbin/nmbd from system_u:object_r:bin_t:s0 to system_u:object_r:nmbd_exec_t:s0 Relabeled /usr/sbin/php-fpm from system_u:object_r:bin_t:s0 to system_u:object_r:httpd_exec_t:s0 Relabeled /usr/sbin/pwconv from system_u:object_r:bin_t:s0 to system_u:object_r:admin_passwd_exec_t:s0 Relabeled /usr/sbin/pwunconv from system_u:object_r:bin_t:s0 to system_u:object_r:admin_passwd_exec_t:s0 Relabeled /usr/sbin/rngd from system_u:object_r:bin_t:s0 to system_u:object_r:rngd_exec_t:s0 Relabeled /usr/sbin/smbd from system_u:object_r:bin_t:s0 to system_u:object_r:smbd_exec_t:s0 Relabeled /usr/sbin/sshd from system_u:object_r:bin_t:s0 to system_u:object_r:sshd_exec_t:s0 Relabeled /usr/sbin/strongswan from system_u:object_r:bin_t:s0 to system_u:object_r:ipsec_mgmt_exec_t:s0 Relabeled /usr/sbin/swanctl from system_u:object_r:bin_t:s0 to system_u:object_r:ipsec_mgmt_exec_t:s0 Relabeled /usr/sbin/useradd from system_u:object_r:bin_t:s0 to system_u:object_r:useradd_exec_t:s0 Relabeled /usr/sbin/userdel from system_u:object_r:bin_t:s0 to system_u:object_r:useradd_exec_t:s0 Relabeled /usr/sbin/usermod from system_u:object_r:bin_t:s0 to system_u:object_r:useradd_exec_t:s0 Relabeled /usr/sbin/vipw from system_u:object_r:bin_t:s0 to system_u:object_r:admin_passwd_exec_t:s0 Relabeled /usr/sbin/winbindd from system_u:object_r:bin_t:s0 to system_u:object_r:winbind_exec_t:s0 There are many other examples in /bin, /var/lib, /usr/lib. --
Re: several issues with f34
On 06/12/2021 01:48, Paolo Galtieri wrote: systemctl status ntpd ○ ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: disabled) Active: inactive (dead) Docs: man:ntpd(8) As Tom has already indicated, this is what you'd get if you have both ntpd and chronyd enabled. So, make sure only one time sync service is enabled. -- Did 황준호 die? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
/var/tmp/flatpak
Hello, Why on one machine I have 4 /var/tmp/flatpak-cache-3VUAC1 4 /var/tmp/flatpak-cache-DDS6C1 and on my laptop: 631472 /var/tmp/flatpak-cache-BYZHD1/child-oci-toPwKS/blobs/sha256 631472 /var/tmp/flatpak-cache-PA8XD1/child-oci-wdwUj6/blobs/sha256 631476 /var/tmp/flatpak-cache-8TNND1/child-oci-yQb2Jc/blobs/sha256 631476 /var/tmp/flatpak-cache-BYZHD1/child-oci-toPwKS/blobs 631476 /var/tmp/flatpak-cache-FC7WD1/child-oci-Ir0k8W/blobs/sha256 631476 /var/tmp/flatpak-cache-IO1JD1/child-oci-wUM2oN/blobs/sha256 631476 /var/tmp/flatpak-cache-PA8XD1/child-oci-wdwUj6/blobs 631480 /var/tmp/flatpak-cache-8TNND1/child-oci-yQb2Jc/blobs 631480 /var/tmp/flatpak-cache-FC7WD1/child-oci-Ir0k8W/blobs 631480 /var/tmp/flatpak-cache-IO1JD1/child-oci-wUM2oN/blobs 631480 /var/tmp/flatpak-cache-LU5PD1/child-oci-jL5CqP/blobs/sha256 631484 /var/tmp/flatpak-cache-LU5PD1/child-oci-jL5CqP/blobs 631488 /var/tmp/flatpak-cache-BYZHD1/child-oci-toPwKS 631488 /var/tmp/flatpak-cache-PA8XD1/child-oci-wdwUj6 631492 /var/tmp/flatpak-cache-7K8SD1/child-oci-jBMjKy/blobs/sha256 631492 /var/tmp/flatpak-cache-8TNND1/child-oci-yQb2Jc 631492 /var/tmp/flatpak-cache-BYZHD1 631492 /var/tmp/flatpak-cache-FC7WD1/child-oci-Ir0k8W 631492 /var/tmp/flatpak-cache-IO1JD1/child-oci-wUM2oN 631492 /var/tmp/flatpak-cache-PA8XD1 631496 /var/tmp/flatpak-cache-7K8SD1/child-oci-jBMjKy/blobs 631496 /var/tmp/flatpak-cache-8TNND1 631496 /var/tmp/flatpak-cache-FC7WD1 631496 /var/tmp/flatpak-cache-IO1JD1 631496 /var/tmp/flatpak-cache-LU5PD1/child-oci-jL5CqP 631500 /var/tmp/flatpak-cache-LU5PD1 631508 /var/tmp/flatpak-cache-7K8SD1/child-oci-jBMjKy 631512 /var/tmp/flatpak-cache-7K8SD1 4432148 /var/tmp While both machines must be more or less similar? === Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988| | Room# D114A === ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
On Sun, 05 Dec 2021 20:18:13 +0100 francis.montag...@inria.fr wrote: > Sorry: I was comparing with chronyd Actually that's a good thing to look at. Have you disabled chrony? If not, they will fight over the NTP port. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
On Sun, 05 Dec 2021 19:55:15 +0100 francis.montag...@inria.fr wrote: > I suspect that ntpd is not enabled in the proper "target". > What gives: > systemctl get-default > find /etc/systemd/system -name chronyd.service -ls Sorry: I was comparing with chronyd I meant thus: systemctl get-default find /etc/systemd/system -name ntpd.service -ls What gives also: systemctl cat ntpd.service and: systemctl status systemd-timesyncd.service -- francis ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
Hi On Sun, 05 Dec 2021 09:48:50 -0800 Paolo Galtieri wrote: > Here's the info: > systemctl status ntpd > ○ ntpd.service - Network Time Service > Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; > vendor preset: disabled) > Active: inactive (dead) > Docs: man:ntpd(8) Effectively enabled. > I rebooted the system at 9:37 AM and there is no entry indicating ntpd > was started after this time. I suspect that ntpd is not enabled in the proper "target". What gives: systemctl get-default find /etc/systemd/system -name chronyd.service -ls This should produce, when in multi-user.target: systemctl get-default multi-user.target find /etc/systemd/system -name chronyd.service -ls 29844 4 lrwxrwxrwx 1 root root 39 Nov 11 18:31 /etc/systemd/system/multi-user.target.wants/chronyd.service -> /usr/lib/systemd/system/chronyd.service -- francis ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: several issues with f34
Here's the info: systemctl status ntpd ○ ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: disabled) Active: inactive (dead) Docs: man:ntpd(8) At this point here's the current network config: ifconfig eno1: flags=4163 mtu 1500 inet 192.168.10.66 netmask 255.255.255.0 broadcast 192.168.10.255 inet6 fe80::4741:dbcc:7824:9f5 prefixlen 64 scopeid 0x20 ether 4c:d9:8f:6d:87:21 txqueuelen 1000 (Ethernet) RX packets 1067 bytes 125274 (122.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 725 bytes 95167 (92.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 17 eno2: flags=4099 mtu 1500 ether 4c:d9:8f:6d:87:22 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 18 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 503 bytes 40302 (39.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 503 bytes 40302 (39.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099 mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:ba:c1:00 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 The wifi interface does not exist, at this point I started ntpd sudo systemctl start ntpd ● ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2021-12-05 09:09:37 PST; 2s ago Docs: man:ntpd(8) Process: 3288 ExecStart=/usr/sbin/ntpd -g -N -u ntp:ntp (code=exited, status=0/SUCCESS) Main PID: 3289 (ntpd) Tasks: 2 (limit: 37863) Memory: 11.8M CPU: 52ms CGroup: /system.slice/ntpd.service └─3289 /usr/sbin/ntpd -g -N -u ntp:ntp Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: IO: Listen normally on 3 eno1 192.168.10.66:123 Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: IO: Listen normally on 4 lo [::1]:123 Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: IO: Listen normally on 5 eno1 [fe80::4741:dbcc:7824:9> Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: IO: Listening on routing socket on fd #22 for interfa> Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: SYNC: Found 5 servers, suggest minsane at least 3 Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: INIT: MRU 10922 entries, 13 hash bits, 65536 bytes Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: INIT: Built with OpenSSL 1.1.1k FIPS 25 Mar 2021, 10> Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: INIT: Running with OpenSSL 1.1.1l FIPS 24 Aug 2021, > Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: NTSc: Using system default root certificates. Dec 05 09:09:38 truckin.homenet192-10.com ntpd[3289]: DNS: dns_probe: 0.pool.ntp.org, cast_flags:1, flags:2> I went and looked in /var/log/messages to see if there was anything there that might indicate the problem. What I found is that the only time I see: Dec 5 09:09:37 truckin systemd[1]: Starting Network Time Service... is when I do it manually. I rebooted the system at 9:37 AM and there is no entry indicating ntpd was started after this time. Paolo On 12/4/21 09:38, Ed Greshko wrote: On 05/12/2021 00:27, Paolo Galtieri wrote: This isn't true. I stopped ntpd, stopped the wifi connection and restarted ntpd and ntpd started fine with no wifi connection. It should only need a network connection to synchronize the time. That is why I asked you to provide the output of systemctl status ntpd before you restart manually. That way we may see the error causing it to fail to start initially. Paolo On 12/3/21 10:15, Joe Zeff wrote: On 12/3/21 11:05 AM, Paolo Galtieri wrote: Next issue. This same system is configured to start ntpd at boot, but it doesn't start. I need to start it manually after the system is booted. Of course it doesn't. That service requires a network connection and can't start until you've unplugged your wireless adapter and plugged it back in. Fix that and this issue should solve itself. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guideline
Re: selinux changes: why?
> On Dec 5, 2021, at 05:44, Nick Urbanik wrote: > > I am regularly having selinux labels changing. This should never > happen, but it does quite continuously; many critical executables lose > their correct label, preventing me from logging in without a relabel. > > This is Fedora 35, upgraded over quite a few generations of Fedora. > The root file system is ext4 on luks encryption on RAID 1. > > Any suggestions on how to troubleshoot and determine the cause? I've > never had selinux labels decay before. I’ve never heard of this happening except in cases where file systems were mounted in alternate locations and written to. (For example, a chrooted OS mounted on a livecd) Maybe it would help if you showed an example of paths and what context you found them in? Knowing the incorrect context can sometimes help identify what is causing it. -- Jonathan Billings ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: LUKS on shutdown.
On Sat, Dec 4, 2021 at 11:33 PM Gordon Messmer wrote: > On 12/4/21 19:15, murph nj wrote: > > > > > > Got another opportunity, redirected lsof /home and lsof /other to > > files, and there was no output. > > > Interesting... Is there an error if you try to unmount those yourself? > > Remember, all of the output (and the command line I'm typing on) is immediately erased by the cylon eye, so I'll try (next time it does it) and try to redirect stdout, and stderr to a file, typing blind. > > > I did get output from systemctl-list-jobs (edited lightly) > > > > JOB UNIT TYPE STATE > > 6039 systemd-cryptsetup@luks\x2dshome.service stop running > > 6068 systemd-cryptsetup@luks\x2de8.service stop running > > 6055 systemd-cryptsetup@luks\x2dsother.service stop running > > 6047 systemd-cryptsetup@luks\x2d23.service stop running > > > Home and other make sense given your earlier comment, but what are the > other two? Do the number of entries in /etc/crypttab match the number > of LUKS partitions? (What's in /proc/mounts during the failed shutdown?) > > I think they do line up, I'll do my best to confirm, and get the information from /proc/mounts. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
selinux changes: why?
Dear Folks, I am regularly having selinux labels changing. This should never happen, but it does quite continuously; many critical executables lose their correct label, preventing me from logging in without a relabel. This is Fedora 35, upgraded over quite a few generations of Fedora. The root file system is ext4 on luks encryption on RAID 1. Any suggestions on how to troubleshoot and determine the cause? I've never had selinux labels decay before. -- Nick Urbanik http://nicku.org ni...@nicku.org GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
