Description of problem: lvm2 generates warnings and errors on boot. Version-Release number of selected component (if applicable): lvm2-2.02.161-5.fc25.x86_64 lvm2-libs-2.02.161-5.fc25.x86_64 How reproducible: At every boot. Steps to Reproduce: 1. Reboot the system, look in the log Actual results: lvm: Daemon lvmetad returned error 104 lvm: WARNING: Failed to connect to lvmetad. Falling back to device scanning. systemd: lvm2-lvmetad.socket: Failed to queue service startup job (Maybe the se\ rvice file is missing or not a non-template unit?): Transaction is destructive. systemd: lvm2-lvmetad.socket: Unit entered failed state. lvm: WARNING: Failed to connect to lvmetad. Falling back to device scanning. Expected results: Cleaner log Additional info: This seems to have been the subject of bug 813766, closed on 2013-02-21, for RHEL6, but somehow my F25 system still shows it.
Is this reproducible on every reboot? Please, add "debug" to kernel command line at boot. Then when the system is up and running, run "lvmdump -u -l -s" to collect debug logs and attach it here (the tgz file). Thanks.
I did as requested, looked through the lvdump generated tar.gz archive and couldn't find the lvm error in there. Turns out the error is not during boot, but during shutdown. (I've edited the summary line above to reflect this). There is a line like: Daemon lvmetad returned error 104 and two like: WARNING: Failed to connect to lvmetad. Falling back to device scanning. Not attaching the lvdump but may if it helps (though there's lot of personalized information in there).
If it's at shutdown, it looks like some script is still using LVM commands even after lvmetad is stopped. Could you run the system with the "debug" on kernel command line, then shutdown the system, then run again and then run "journalctl -b-1" (to take the log from previous run, including the shutdown sequence). If you don't want to expose the log here in this bz, you can send it to me directly for analysis. Thanks.
Added debug to command line. Rebooted occasionally, error line doesn't show up all the time, so how reproducible in my original report is wrong. Change that to sometimes. Output of "journalctl -b -N" where N happened to be 2, will be sent to Peter directly.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still shows on every reboot on my F26 boxes. Updating version to 26, so bug isn't EOLed. Will bump to 27 after updating, if it still present.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Hmm, I still see this too.
This is still happening in F30. Logwatch error messages look like: /run/lvm/lvmetad.socket: connect failed: Connection refused: 1 Time(s) Daemon lvmetad returned error 104: 1 Time(s) WARNING: Autoactivation reading from disk instead of lvmetad.: 1 Time(s) WARNING: Failed to connect to lvmetad. Falling back to device scanning.: 2 Time(s) WARNING: Not using lvmetad because cache update failed.: 1 Time(s) WARNING: lvmetad is being updated by another command (pid 613).: 1 Time(s) where the number of times one gets the error and pid numbers vary from machine to machine I'll try getting a debug dump later, but can't really shut either of the boxes where I see this now.
There have been various fixes recently in this area which I believe will improve this situation: https://sourceware.org/git/?p=lvm2.git;a=commit;h=44cfa558437634c15ec6da38507e73b4c86837c1 https://sourceware.org/git/?p=lvm2.git;a=commit;h=0cab341e1d0e8f9089d3c62d3adbec24dfd5e124 https://sourceware.org/git/?p=lvm2.git;a=commit;h=25f231cf06c3938838a64f5b88834d831f45c1c2 These patches are included in lvm v2_03_03 and higher (included in current rawhide and scheduled for Fedora 31 release).
This should be fixed in F31 and above. Do you still see any issues on reboot?
I believe that is correct, i.e. I haven't seen those lvmetad messages in logwatch since updating to F31.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.