Re: Fedora 31 will not shut down completely
On Sun, 2019-11-10 at 18:59 -0500, Sam Varshavchik wrote: > I have the grub menu enabled. My poweroff procedure is to do a > reboot, wait until I go back to the grub menu, stop the autoboot > timer, and then hold the power key. This reliably shuts everything > off, without putting stress on the 10-year old HD. It used to be easy to add a grub stanza with a halt command (grub's shutdown and poweroff command). That was useful for those times when you accidentally rebooted instead of shutting down, and would also help with computers that won't shutdown cleanly. -- uname -rsvp Linux 3.10.0-1062.4.1.el7.x86_64 #1 SMP Fri Oct 18 17:15:30 UTC 2019 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ 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
Re: Fedora 31 will not shut down completely
On Mon, 11 Nov 2019 17:35:30 -0500 john.mel...@gmail.com wrote: > It would appear that the problem is somehow related to booting an EFI > partition. Or something that got corrupted during the initial install. (But I certainly have seen older machines where UEFI was very dodgy). ___ 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
Re: Fedora 31 will not shut down completely
one of interesting/left question to me is: why it had been working with the same bios config. on F30 and stopped it on F31 ? ___ 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
Re: Fedora 31 will not shut down completely
On Sun, 2019-11-10 at 13:11 +0800, Ed Greshko wrote: > On 11/10/19 12:56 PM, sixpack13 wrote: > > okay, so we are both liars ! > > fine by me, "endowed" with that "competence" let's fix the OP pain > > ! > > :-) > > > > the priciest questions are (just to put AND remove in one step a > > topic on my list): > > - OP, do have multi-card readers in your box ? > > - do you or does fedora do "magic" mapping with them ? > > - are there still media's the that devices ? > > - maybe, a install dvd, still in the drive, which could prevent > > clean shutdown, somehow ? > > ( last Q. is NOT meant as an attack ...!!!) > > I really don't think any of that is relevant. > > Note the log the OP supplied. > > Nov 08 19:14:18 localhost.localdomain audit[1]: SERVICE_STOP pid=1 > uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 > msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" > hostname=? addr=? termina> > Nov 08 19:14:18 localhost.localdomain systemd[1]: Stopped Monitoring > of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. > Nov 08 19:14:18 localhost.localdomain systemd[1]: lvm2- > monitor.service: Succeeded. > Nov 08 19:14:18 localhost.localdomain lvm[14772]: 3 logical volume(s) > in volume group "fedora_localhost-live" unmonitored > Nov 08 19:14:18 localhost.localdomain lvm[14772]: /dev/sdf: open > failed: No medium found > > > The "Succeeded" and "Stopped Monitoring of LVM2" would indicate that > this phase > has completed. And, the log does have "Reached target Final Step" > > I feel Tom had the best suggestion at this point > > "If you turn off rhgb and quiet on the kernel boot line, > you can (usually) watch lots of messages on the console as > it tries to shutdown" Ok, some progress! I reconfigured the BIOS boot settings to pick the hard drive first, and not an EFI partition. Then I reinstalled Fedora 31 from scratch, updated it and installed the additional packages that I need, and restored home from backup. The machine now shuts down normally. It would appear that the problem is somehow related to booting an EFI partition. This machine is a kickass 2011-vintage Gateway machine, so it may have some kind of EFI shutdown bug. I use it for my daily driver because the i7 processor and motherboard is plenty quick enough and does not have most of the hardware bugs associated with the last n generations of intel design errors. Unfortunately, I cannot update the BIOS, as Gateway is no longer in business. So, I guess I will have to use a non-EFI boot for the forseeable future on this machine. As an aside, I also have 2 older Lenovo machines that boot Fedora 31 in EFI mode just fine. Thanks for helping me out everyone! ___ 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
Re: Fedora 31 will not shut down completely
On 11/11/19 10:21 PM, John Mellor wrote: Ok, I installed the 5.4.0.0-0.rc6.git3.1.fc32 kernel from koji, but no effect on the problem. Next, I guess I can try the rawhide kernel. I also swapped out the nVidia graphics card for an old ATI Cedar card, also to no effect. Another thing you may consider in testing would be to try both systemctl --force poweroff and systemctl --force -force poweroff Note the caution from the systemctl man page When used with halt, poweroff, reboot or kexec, execute the selected operation without shutting down all units. However, all processes will be killed forcibly and all file systems are unmounted or remounted read-only. This is hence a drastic but relatively safe option to request an immediate reboot. If --force is specified twice for these operations (with the exception of kexec), they will be executed immediately, without terminating any processes or unmounting any file systems. Warning: specifying --force twice with any of these operations might result in data loss. Note that when --force is specified twice the selected operation is executed by systemctl itself, and the system manager is not contacted. This means the command should succeed even when the system manager has crashed. -- The key to getting good answers is to ask good questions. ___ 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
Re: Fedora 31 will not shut down completely
On 2019-11-10 3:22 p.m., stan via users wrote: On Sun, 10 Nov 2019 13:17:33 -0500 John Mellor wrote: I'm starting to suspect a broken ACPI change in the newer kernel, but I'm stuck... Sure looks like it is a bug. Try installing the -debug kernel? At the least it should give you more messages. You should probably open a bugzilla against the kernel with your problem if that doesn't pinpoint the problem. As a wild chance you could try installing a rawhide development kernel to see if it has fixed your issue. We are close enough to branch that it should still work. https://koji.fedoraproject.org/koji/buildinfo?buildID=1410333 Download the rpms for your architecture, and install them from the directory they are in with dnf -C install [kernel rpms] Ok, I installed the 5.4.0.0-0.rc6.git3.1.fc32 kernel from koji, but no effect on the problem. Next, I guess I can try the rawhide kernel. I also swapped out the nVidia graphics card for an old ATI Cedar card, also to no effect. ___ 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
Re: Fedora 31 will not shut down completely
John Mellor writes: Turning off rhgb and quiet at boot results in the unquiet shutdown, but no more enlightenment. The screen output looks ok. Doing a "systemctl poweroff" causes the same hang as the normal poweroff from CLI or from GUI. I have not yet tried the suggestion to relabel the whole filesystem. Since this is a fresh install, I would assume that would be unnecessary. The suggestion to hit the escape key does not work in this case. When the system hangs, I have no keyboard or usable screen to debug with, as the system is almost all shutdown. I also forced an fsck per one of the suggestions, to no effect. It still hangs. I'm starting to suspect a broken ACPI change in the newer kernel, but I'm stuck... My old Thinkpad hasn't been able to reliably do an orderly poweroff for something like 6-7 Fedora releases. It does poweroff, but about half the time it doesn't park the HD properly, with the resulting audible complaint. I have the grub menu enabled. My poweroff procedure is to do a reboot, wait until I go back to the grub menu, stop the autoboot timer, and then hold the power key. This reliably shuts everything off, without putting stress on the 10-year old HD. If you cannot figure out your issue, try this alternate process. It's a pain in the neck, but it might get the job done. pgpRRSJpeXSOC.pgp Description: PGP signature ___ 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
Re: Fedora 31 will not shut down completely
> > When the system hangs, I have no keyboard or usable screen to debug > with, as > the system is almost all shutdown. > 1) is a second box and a null modem cable available to setup an serial console ? currently I don't know/I'm unsure how to setup a serial console nowadays (did that years ago). maybe somone here could help ? a short googling: https://docs.fedoraproject.org/en-US/Fedora/22/html/System_Administrators_Guide/sec-GRUB_2_over_Serial_Console.html https://wiki.archlinux.org/index.php/working_with_the_serial_console 2) another thought: systemctl suspend or systemctl hibernate see: man systemctl to maybe trigger some more output of the last "shutdown"(?) sequence (maybe visible in the subsequent wakeup) hibernate needs the UUID of your swap in /etc/default/grub. my one: GRUB_CMDLINE_LINUX="resume=UUID=1fa013bc-d3e2-4382-8e92-df1e5c4d52dc ... rhgb quiet" changes in /etc/default/grub need a run of "sudo grub2-mkconfig ..." 3) is an rawhide kernel an temporary option to test Questions: - what driver is the nvidia graphic card running ? - is the ssd firmware current / maybe power off bugs known ? ___ 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
Re: Fedora 31 will not shut down completely
On 11/10/19 10:17 AM, John Mellor wrote: Turning off rhgb and quiet at boot results in the unquiet shutdown, but no more enlightenment. The screen output looks ok. Would you be able to type out what the last line on the screen is? Doing a "systemctl poweroff" causes the same hang as the normal poweroff from CLI or from GUI. I'm starting to suspect a broken ACPI change in the newer kernel, but I'm stuck... Given that a reboot works fine, I would agree that there is some issue between the kernel and the BIOS. See if there is a BIOS update available for your system. I would suggest filing a kernel bug report, preferably in the upstream kernel bugzilla. If you could find out a narrower range of kernel versions where this started, that would be helpful. Does the installer image you used have the same problem if you shutdown instead of rebooting? If you have the time and internet bandwidth, try booting the F31 netinstall image and see if that has the same shutdown problem. If so, then try the latest F30 live respin. ___ 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
Re: Fedora 31 will not shut down completely
On Sun, 10 Nov 2019 13:17:33 -0500 John Mellor wrote: > I'm starting to suspect a broken ACPI change in the newer kernel, but > I'm stuck... Sure looks like it is a bug. Try installing the -debug kernel? At the least it should give you more messages. You should probably open a bugzilla against the kernel with your problem if that doesn't pinpoint the problem. As a wild chance you could try installing a rawhide development kernel to see if it has fixed your issue. We are close enough to branch that it should still work. https://koji.fedoraproject.org/koji/buildinfo?buildID=1410333 Download the rpms for your architecture, and install them from the directory they are in with dnf -C install [kernel rpms] ___ 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
Re: Fedora 31 will not shut down completely
On 2019-11-09 11:34 a.m., Tom Horsley wrote: On Sat, 09 Nov 2019 11:00:42 -0500 john.mel...@gmail.com wrote: I guess its possible that something is not completing its shutdown step, but it does not appear to be logging that omission. Any idea how to isolate which is the faulty daemon? If you turn off rhgb and quiet on the kernel boot line, you can (usually) watch lots of messages on the console as it tries to shutdown and see things like: A start job is running for shutting down some stupid service stuck on the screen with a timer ticking away. Example: I found dhcpd won't stop in fedora 31 without a huge timeout: https://bugzilla.redhat.com/show_bug.cgi?id=1768604 (supposedly fixed, but not yet in updates). Sorry for the long delay to a reply as it was blocked b/c of size for moderation. Here it is minus the screenshot of the hang. I removed the wireless card in case something with dual-pathing with the wired connection was the problem, and reinstalled from scratch from new media again, in case there was a problem with the new F31 install. This install has no extras other than restoring home from backup, installing the updates and installation and configuration of Thunderbird. It does the same thing, so I'm pretty sure that this is not a faulty installation problem. Turning off rhgb and quiet at boot results in the unquiet shutdown, but no more enlightenment. The screen output looks ok. Doing a "systemctl poweroff" causes the same hang as the normal poweroff from CLI or from GUI. I have not yet tried the suggestion to relabel the whole filesystem. Since this is a fresh install, I would assume that would be unnecessary. The suggestion to hit the escape key does not work in this case. When the system hangs, I have no keyboard or usable screen to debug with, as the system is almost all shutdown. I also forced an fsck per one of the suggestions, to no effect. It still hangs. I'm starting to suspect a broken ACPI change in the newer kernel, but I'm stuck... ___ 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
Re: Fedora 31 will not shut down completely
s/inside/insight/ ___ 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
Re: Fedora 31 will not shut down completely
agreed. more inside in the log files needed. ___ 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
Re: Fedora 31 will not shut down completely
On 11/10/19 12:56 PM, sixpack13 wrote: okay, so we are both liars ! fine by me, "endowed" with that "competence" let's fix the OP pain ! :-) the priciest questions are (just to put AND remove in one step a topic on my list): - OP, do have multi-card readers in your box ? - do you or does fedora do "magic" mapping with them ? - are there still media's the that devices ? - maybe, a install dvd, still in the drive, which could prevent clean shutdown, somehow ? ( last Q. is NOT meant as an attack ...!!!) I really don't think any of that is relevant. Note the log the OP supplied. Nov 08 19:14:18 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termina> Nov 08 19:14:18 localhost.localdomain systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. Nov 08 19:14:18 localhost.localdomain systemd[1]: lvm2-monitor.service: Succeeded. Nov 08 19:14:18 localhost.localdomain lvm[14772]: 3 logical volume(s) in volume group "fedora_localhost-live" unmonitored Nov 08 19:14:18 localhost.localdomain lvm[14772]: /dev/sdf: open failed: No medium found The "Succeeded" and "Stopped Monitoring of LVM2" would indicate that this phase has completed. And, the log does have "Reached target Final Step" I feel Tom had the best suggestion at this point "If you turn off rhgb and quiet on the kernel boot line, you can (usually) watch lots of messages on the console as it tries to shutdown" -- The key to getting good answers is to ask good questions. ___ 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
Re: Fedora 31 will not shut down completely
okay, so we are both liars ! fine by me, "endowed" with that "competence" let's fix the OP pain ! :-) the priciest questions are (just to put AND remove in one step a topic on my list): - OP, do have multi-card readers in your box ? - do you or does fedora do "magic" mapping with them ? - are there still media's the that devices ? - maybe, a install dvd, still in the drive, which could prevent clean shutdown, somehow ? ( last Q. is NOT meant as an attack ...!!!) ___ 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
Re: Fedora 31 will not shut down completely
On 11/10/19 12:22 PM, sixpack13 wrote: I have read more then once in the howto's regarding upgrade that one task is to do an relabeling. I have never seen such recommendation. I'd rather defer to what Dan Walsh has written on the subject: Full relabelling of an SELinux machine should almost never be necessary, Unless you disable SELinux. And none of you would ever do that :^), permissive mode is a much better idea. Running restorecon recursively on a directory is a better and much quicker solution. But sometimes a machine could get so totally corrupted that you have to autorelabel. An admin going crazy with chcon? Every selinux-policy update package includes a limited relabel, although sometimes this is less limited then others. The package update fixes all labels that changed in the update. The selinux-policy package compares the file context file pre install and post install and attempts to relabel the greatest common denominator, if I remember my math terms correctly. Basically if the update package sees label changes in /usr/lib64 it will run a fixfiles /usr/lib64. And to his point, I have never done a relabel after an upgrade or update. The only time I've done a relabel is when I'd been working with non-fedora supplied SW and disabling selinux in order to get it to run at all. After doing that I was well aware of what what I had caused/done. -- The key to getting good answers is to ask good questions. ___ 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
Re: Fedora 31 will not shut down completely
On 11/10/19 10:45 AM, Ed Greshko wrote: I'm not going to spend any time to determine when they do and when they don't. They appear here on multiple systems, with no lvm, OK, I lied. I was curious as to why some the systems here had entries like Nov 07 12:27:42 meimei.greshko.com lvm[43966]: /dev/sde: open failed: No medium found and some did not. The answer was obvious if I took a moment to think about it. It seems HW dependent. The systems where the entries appear have multi-card readers (which I forgot about since nobody uses them) installed which map to /dev/sdX entries. -- The key to getting good answers is to ask good questions. ___ 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
Re: Fedora 31 will not shut down completely
> On 11/10/19 10:25 AM, sixpack13 wrote:
>
> Nope
>
> But the point is,
the point is that I don't run lvm (esp. lvm2-monitor.service) since month/years.
so I was unable to see the OP message like "lvm[14772]: /dev/sdX: open
failed: No medium found" on my box.
therefore it appeared to me like something wrong.
- okay, lesson learned -
...
> ...But since you're not using lvm you may want
> to consider
> disabling lvm2-lvmpolld.socket and lvm2-monitor.service.
>
see above, the second service is dead since month/years, the first after my
last post !
to selinux:
I have read more then once in the howto's regarding upgrade that one task is to
do an relabeling.
if it's definitive necessary, I don't know, but it won't hurt- AFAIK- and it
may exclude one part what could cause the OP pain.
I have NO solution at hand, so I try to exclude things which *may* cause the OP
trouble. Afterwards I'm on the save/saver side and able to cancel one topic of
the/my list of what could it be.
And until one convinces me from the opposite that relabeling hurts here THIS
topic is still valide, independently if I could or could not see AVC in any
log's.
with the/my lack of an/the right solution I'm on the sad side to near it down.
one part of "near it down" is to compare my box with the OP's.
- and avoid to think it's the same: ping @Ed :-) -
My one runs since first day of beta release (search for my thanks message)
through an upgrade without (!) any (obvious[1]) bugs. [2]
so I wonder what is other on the OP's box ?
Okay ?
===
@ALL: Does relabeling hurt ?
ping ${selinux maintainer}
anyone ?
no one ?
Okay, when do we cancel relabeling from the list ?
[1]
I'm somewhat aged and blind - sometimes -
[2]
to be honest, it's somewhat lied !
there is an gnome-extension somewhat filling the journal, but it's not Fedora
itself.
---
The key of good troubleshooting is to stop thinking all fedora boxes are
configured the same.
___
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
Re: Fedora 31 will not shut down completely
On 11/10/19 10:25 AM, sixpack13 wrote: okay, journalctl | grep -i lvm => Nov 08 03:07:27 obelix.fritz.box systemd[1]: lvm2-lvmpolld.socket: Succeeded. Nov 08 03:07:27 obelix.fritz.box systemd[1]: Closed LVM2 poll daemon socket. Nov 08 07:58:17 obelix.fritz.box systemd[1]: lvm2-lvmpolld.socket: Succeeded. Nov 08 07:58:17 obelix.fritz.box systemd[1]: Closed LVM2 poll daemon socket. Nov 09 04:27:58 obelix.fritz.box systemd[1]: lvm2-lvmpolld.socket: Succeeded. Nov 09 04:27:58 obelix.fritz.box systemd[1]: Closed LVM2 poll daemon socket. Nov 09 19:57:28 obelix.fritz.box systemd[1]: lvm2-lvmpolld.socket: Succeeded. Nov 09 19:57:28 obelix.fritz.box systemd[1]: Closed LVM2 poll daemon socket. systemctl | grep -i lvm: => lvm2-lvmpolld.socket loaded active listening LVM2 poll daemon socket any /dev/sdc - /dev/sdf entries here ? Nope But the point is, they can appear and they do appear on multiple systems here which don't have lvm partitions. I'm not going to spend any time to determine when they do and when they don't. They appear here on multiple systems, with no lvm, at shutdown with no problems to poweroff. So, the message are benign, IMO. Most people don't bother to do this. But since you're not using lvm you may want to consider disabling lvm2-lvmpolld.socket and lvm2-monitor.service. As for selinux. Instead of trying to check the logs, it is probably easier to use the GUI sealert to check. So, if there is an selinux issue one can diagnose it. -- The key to getting good answers is to ask good questions. ___ 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
Re: Fedora 31 will not shut down completely
okay, journalctl | grep -i lvm => Nov 08 03:07:27 obelix.fritz.box systemd[1]: lvm2-lvmpolld.socket: Succeeded. Nov 08 03:07:27 obelix.fritz.box systemd[1]: Closed LVM2 poll daemon socket. Nov 08 07:58:17 obelix.fritz.box systemd[1]: lvm2-lvmpolld.socket: Succeeded. Nov 08 07:58:17 obelix.fritz.box systemd[1]: Closed LVM2 poll daemon socket. Nov 09 04:27:58 obelix.fritz.box systemd[1]: lvm2-lvmpolld.socket: Succeeded. Nov 09 04:27:58 obelix.fritz.box systemd[1]: Closed LVM2 poll daemon socket. Nov 09 19:57:28 obelix.fritz.box systemd[1]: lvm2-lvmpolld.socket: Succeeded. Nov 09 19:57:28 obelix.fritz.box systemd[1]: Closed LVM2 poll daemon socket. systemctl | grep -i lvm: => lvm2-lvmpolld.socket loaded active listening LVM2 poll daemon socket any /dev/sdc - /dev/sdf entries here ? ___ 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
Re: Fedora 31 will not shut down completely
On 11/10/19 9:59 AM, sixpack13 wrote: On 11/10/19 3:17 AM, sixpack13 wrote: Those are "normal". If you check your own logs you will see the same thing. there is no need to check my log's regarding lvm entries. here is no lvm running ! so I can't know what is "normal" on lvm boxes. and therefore I underwrote my prev. comment with "just some wild guesses ..." Well [egreshko@meimei ~]$ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda3 484521344 85436228 374403084 19% / /dev/sda1 1408512 239604 1079308 19% /boot /dev/sdb1 503707832 206087100 271964156 44% /home ds6:/volume1/syntegra 2879621632 1119884032 1759635200 39% /syntegra ds6:/volume1/misty 2879621632 1119884032 1759635200 39% /home/egreshko/misty ds6:/volume1/video 2879621632 1119884032 1759635200 39% /home/egreshko/Videos ds6:/volume1/music 2879621632 1119884032 1759635200 39% /home/egreshko/music So, no lvm here right? And from my log at shutdown Nov 06 10:37:31 meimei.greshko.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 06 10:37:31 meimei.greshko.com lvm[462]: /dev/sdf: open failed: No medium found Nov 06 10:37:31 meimei.greshko.com lvm[462]: /dev/sde: open failed: No medium found Nov 06 10:37:31 meimei.greshko.com lvm[462]: /dev/sdd: open failed: No medium found Nov 06 10:37:31 meimei.greshko.com lvm[462]: /dev/sdc: open failed: No medium found Nov 06 10:37:31 meimei.greshko.com lvm[462]: /dev/sdf: open failed: No medium found Nov 06 10:37:31 meimei.greshko.com lvm[462]: /dev/sde: open failed: No medium found Nov 06 10:37:31 meimei.greshko.com lvm[462]: /dev/sdd: open failed: No medium found Nov 06 10:37:31 meimei.greshko.com lvm[462]: /dev/sdc: open failed: No medium found Maybe check your logs just for fun? You can always check to see if you have any AVC messages in the audit logs. Very doubtful it would be selinux. clearing "doubt" may lead to more knowledge, e.g. relabeling want hurt, AFAIK. and afterwards we know definitive what wasn't the right solution and it reduces the number of potential "wild guesses" too, until one come up with the right one. Deal ? Which is why one should check the logs? -- The key to getting good answers is to ask good questions. ___ 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
Re: Fedora 31 will not shut down completely
> On 11/10/19 3:17 AM, sixpack13 wrote: > > Those are "normal". If you check your own logs you will see the same thing. > there is no need to check my log's regarding lvm entries. here is no lvm running ! so I can't know what is "normal" on lvm boxes. and therefore I underwrote my prev. comment with "just some wild guesses ..." > > You can always check to see if you have any AVC messages in the audit logs. > Very doubtful it would be selinux. clearing "doubt" may lead to more knowledge, e.g. relabeling want hurt, AFAIK. and afterwards we know definitive what wasn't the right solution and it reduces the number of potential "wild guesses" too, until one come up with the right one. Deal ? ___ 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
Re: Fedora 31 will not shut down completely
On 11/10/19 12:00 AM, john.mel...@gmail.com wrote: Git it. However, it is not showing any problems that I can see. Excerpt from the log showing a shutdown and subsequent powerup: === excerpt start === ov 08 19:14:18 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-poweroff comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? te> Nov 08 19:14:18 localhost.localdomain systemd[1]: Started Power-Off. Nov 08 19:14:18 localhost.localdomain systemd[1]: systemd-poweroff.service: Succeeded. Nov 08 19:14:18 localhost.localdomain systemd[1]: Reached target Final Step. Nov 08 19:14:18 localhost.localdomain systemd[1]: Reached target Shutdown. Well, a good log would show something like this -- Logs begin at Sun 2019-04-07 00:30:11 CST, end at Sun 2019-11-10 08:54:13 CST. -- Nov 07 12:27:42 meimei.greshko.com systemd-journald[464]: Journal stopped Nov 07 12:27:42 meimei.greshko.com dnsmasq[1561]: exiting on receipt of SIGTERM Nov 07 12:27:42 meimei.greshko.com systemd-shutdown[1]: Sending SIGTERM to remaini ng processes... Nov 07 12:27:42 meimei.greshko.com systemd-shutdown[1]: Syncing filesystems and bl ock devices. Nov 07 12:27:42 meimei.greshko.com kernel: printk: systemd-shutdow: 80 output line s suppressed due to ratelimiting Nov 07 12:27:42 meimei.greshko.com kernel: watchdog: watchdog0: watchdog did not s top! Nov 07 12:27:42 meimei.greshko.com systemd[1]: Set hardware watchdog to 10min. Nov 07 12:27:42 meimei.greshko.com systemd[1]: Hardware watchdog 'iTCO_wdt', versi on 0 Nov 07 12:27:42 meimei.greshko.com systemd[1]: Shutting down. Nov 07 12:27:42 meimei.greshko.com systemd[1]: Reached target Reboot. Nov 07 12:27:42 meimei.greshko.com audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967 295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-reboot comm= "systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 07 12:27:42 meimei.greshko.com audit[1]: SERVICE_START pid=1 uid=0 auid=429496 7295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-reboot comm ="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success ' Nov 07 12:27:42 meimei.greshko.com systemd[1]: Started Reboot. So, you can see after "SERVICE_START" you never got "SERVICE_STOP". Are your results the same if you issue the command "systemctl poweroff"? -- The key to getting good answers is to ask good questions. ___ 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
Re: Fedora 31 will not shut down completely
On 11/10/19 3:17 AM, sixpack13 wrote: It hangs with a frozen window showing a stalled rotating action indicator in Gnome, leaving the power on. Wasn't hitting - I believe - ESC-Key a task to see what's going on on the console. what are sdb - sdf are ? and what does the error "/dev/sdf: open failed: No medium found" mean ? were this error messages in F30 too ? is a file system check needed for sdb -sdf ? => sudo touch /forcefsck and a reboot Those are "normal". If you check your own logs you will see the same thing. might a selinux relabeling help ? => sudo touch /.autorelabel and a reboot You can always check to see if you have any AVC messages in the audit logs. Very doubtful it would be selinux. -- The key to getting good answers is to ask good questions. ___ 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
Re: Fedora 31 will not shut down completely
On Sat, 9 Nov 2019 at 19:18, sixpack13 wrote: > It hangs with a frozen window showing a stalled rotating > > action indicator in Gnome, leaving the power on. > > > > Wasn't hitting - I believe - ESC-Key a task to see what's going on on the > console. > > what are sdb - sdf are ? > and what does the error "/dev/sdf: open failed: No medium > found" mean ? > > were this error messages in F30 too ? > > is a file system check needed for sdb -sdf ? > => sudo touch /forcefsck > and a reboot > > might a selinux relabeling help ? > => sudo touch /.autorelabel > and a reboot > > just some wild guesses ... > > Just to add further (wild guesses ...) as the log seems to suggest everything was successful except the actual power off. So maybe some kind of ACPI bug (you could browse over your jounalctl logs) or maybe a BIOS update is order. ___ 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
Re: Fedora 31 will not shut down completely
It hangs with a frozen window showing a stalled rotating > action indicator in Gnome, leaving the power on. > Wasn't hitting - I believe - ESC-Key a task to see what's going on on the console. what are sdb - sdf are ? and what does the error "/dev/sdf: open failed: No medium found" mean ? were this error messages in F30 too ? is a file system check needed for sdb -sdf ? => sudo touch /forcefsck and a reboot might a selinux relabeling help ? => sudo touch /.autorelabel and a reboot just some wild guesses ... ___ 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
Re: Fedora 31 will not shut down completely
On 11/09/2019 09:56 AM, Anthony F McInerney wrote: Yes i was also wondering when it's hanging, does the escape key work to show the console? Try it and find out. ___ 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
Re: Fedora 31 will not shut down completely
On Sat, 9 Nov 2019 16:56:28 + Anthony F McInerney wrote: > > Yes i was also wondering when it's hanging, does the escape key > > work to > show the console? I run a daemon that is usually sleeping at shutdown. If I don't kill it manually, I get this error. Nothing I've tried does anything. I'll try your suggestion, but I don't think there is anything left at the time this occurs, it's all been terminated. This is just systemd turning off the lights. The setting defaults to 1 minute 30 seconds, but it has a configuration file that allows setting it to whatever value desired. (1 sec? 10 sec?). I can't remember the location, and I had to chain through the systemd documentation (extensive) to find it. But it *is* configurable. ___ 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
Re: Fedora 31 will not shut down completely
On Sat, 9 Nov 2019 at 16:35, Tom Horsley wrote: > On Sat, 09 Nov 2019 11:00:42 -0500 > john.mel...@gmail.com wrote: > > > I guess its possible that something is not completing its shutdown > > step, but it does not appear to be logging that omission. Any idea how > > to isolate which is the faulty daemon? > > If you turn off rhgb and quiet on the kernel boot line, > you can (usually) watch lots of messages on the console as > it tries to shutdown and see things like: > > A start job is running for shutting down some stupid service > > > Yes i was also wondering when it's hanging, does the escape key work to show the console? ___ 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
Re: Fedora 31 will not shut down completely
On Sat, 09 Nov 2019 11:00:42 -0500 john.mel...@gmail.com wrote: > I guess its possible that something is not completing its shutdown > step, but it does not appear to be logging that omission. Any idea how > to isolate which is the faulty daemon? If you turn off rhgb and quiet on the kernel boot line, you can (usually) watch lots of messages on the console as it tries to shutdown and see things like: A start job is running for shutting down some stupid service stuck on the screen with a timer ticking away. Example: I found dhcpd won't stop in fedora 31 without a huge timeout: https://bugzilla.redhat.com/show_bug.cgi?id=1768604 (supposedly fixed, but not yet in updates). ___ 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
Re: Fedora 31 will not shut down completely
On Sat, 2019-11-09 at 23:00 +0800, Ed Greshko wrote: > On 11/9/19 10:42 PM, john.mel...@gmail.com wrote: > > I've had this problem ever since I moved up to Fedora 31 from > > Fedora > > 30. It fails to completely shutdown. It will reboot correctly, > > but > > not shutdown. It hangs with a frozen window showing a stalled > > rotating > > action indicator in Gnome, leaving the power on. > > > > The machine is an older Gateway core-i7 with 32GB ram, the original > > nVidia graphics card, and a larger SSD. Fedora 31 is fully up-to- > > date. > > > > How can I debug and/or fix this problem? Any ideas? > > First try. > > After rebooting, look at the end of the journal for the previous boot > to see if there are any messages > which may show a process hanging. > > You can use > > journalctl -b-1 -r > > The -b-1 says the previous boot log. -r says show in reverse time > order Git it. However, it is not showing any problems that I can see. Excerpt from the log showing a shutdown and subsequent powerup: === excerpt start === ov 08 19:14:18 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-poweroff comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? te> Nov 08 19:14:18 localhost.localdomain systemd[1]: Started Power-Off. Nov 08 19:14:18 localhost.localdomain systemd[1]: systemd-poweroff.service: Succeeded. Nov 08 19:14:18 localhost.localdomain systemd[1]: Reached target Final Step. Nov 08 19:14:18 localhost.localdomain systemd[1]: Reached target Shutdown. Nov 08 19:14:18 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termina> Nov 08 19:14:18 localhost.localdomain systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. Nov 08 19:14:18 localhost.localdomain systemd[1]: lvm2-monitor.service: Succeeded. Nov 08 19:14:18 localhost.localdomain lvm[14772]: 3 logical volume(s) in volume group "fedora_localhost-live" unmonitored Nov 08 19:14:18 localhost.localdomain lvm[14772]: /dev/sdf: open failed: No medium found Nov 08 19:14:18 localhost.localdomain lvm[14772]: /dev/sde: open failed: No medium found Nov 08 19:14:18 localhost.localdomain lvm[14772]: /dev/sdd: open failed: No medium found Nov 08 19:14:18 localhost.localdomain lvm[14772]: /dev/sdc: open failed: No medium found Nov 08 19:14:18 localhost.localdomain lvm[14772]: /dev/sdb: open failed: No medium found Nov 08 19:14:18 localhost.localdomain lvm[14772]: /dev/sdf: open failed: No medium found Nov 08 19:14:17 localhost.localdomain lvm[14772]: /dev/sde: open failed: No medium found Nov 08 19:14:17 localhost.localdomain lvm[14772]: /dev/sdd: open failed: No medium found Nov 08 19:14:17 localhost.localdomain lvm[14772]: /dev/sdc: open failed: No medium found Nov 08 19:14:17 localhost.localdomain lvm[14772]: /dev/sdb: open failed: No medium found Nov 08 19:14:17 localhost.localdomain systemd[1]: Stopped Create Static Device Nodes in /dev. Nov 08 19:14:17 localhost.localdomain systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded. Nov 08 19:14:17 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? > Nov 08 19:14:17 localhost.localdomain kernel: audit: type=1131 audit(1573258457.955:480): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck-root comm="systemd" exe="/usr/lib/systemd/> Nov 08 19:14:17 localhost.localdomain kernel: audit: type=1131 audit(1573258457.955:479): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd> Nov 08 19:14:17 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck-root comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? te> Nov 08 19:14:17 localhost.localdomain systemd[1]: Stopped File System Check on Root Device. Nov 08 19:14:17 localhost.localdomain systemd[1]: systemd-fsck-root.service: Succeeded. Nov 08 19:14:17 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? t> ...skipping... Nov 08 13:43:06 localhost.localdomain kernel: PCI: pci_cache_line_size set to 64 bytes Nov 08 13:43:06 localhost.localdomain kernel: PCI: Using ACPI for IRQ routing Nov 08 13:43:06 localhost.localdomain kernel: Registered efivars operations Nov 08 13:43:06 localhost.localdomain kernel: EDAC MC: Ver: 3.0.0 Nov 08 13:43:06
Re: Fedora 31 will not shut down completely
On 11/9/19 10:42 PM, john.mel...@gmail.com wrote: I've had this problem ever since I moved up to Fedora 31 from Fedora 30. It fails to completely shutdown. It will reboot correctly, but not shutdown. It hangs with a frozen window showing a stalled rotating action indicator in Gnome, leaving the power on. The machine is an older Gateway core-i7 with 32GB ram, the original nVidia graphics card, and a larger SSD. Fedora 31 is fully up-to-date. How can I debug and/or fix this problem? Any ideas? First try. After rebooting, look at the end of the journal for the previous boot to see if there are any messages which may show a process hanging. You can use journalctl -b-1 -r The -b-1 says the previous boot log. -r says show in reverse time order -- The key to getting good answers is to ask good questions. ___ 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
