Re: systemd-resolved floods the logs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jan 6, 2021, at 4:15 AM, Sam Varshavchik wrote:
> Jerome Lille writes:
> 
> > On Tue, 2021-01-05 at 18:10 -0500, Sam Varshavchik wrote:
> > > Chris Murphy writes:
> > >
> > > > On Tue, Jan 5, 2021 at 10:32 AM Chris Murphy
> > > > <lists@xxxxxxxxxxxxxxxxx> wrote:
> > > > >
> > > > > Maybe this bug:
> > > >
> > > > https://github.com/systemd/systemd/issues/13432
> > >
> > > "opened this issue on Aug 29, 2019"
> > >
> > > I would not expect this to be fixed any time soon. The only solution
> > > is:
> > >
> > > systemctl stop systemd-resolved
> > > systemctl disable systemd-resolved
> > > rm -f /etc/resolv.conf
> > > ln -s ../run/NetworkManager/no-stub-resolv.conf /etc/resolv.conf
> > >
> > > Hopefully, this fix will not stop working in the future, either.
> >
> > Thanks for the suggestion. With those changes the flooding of the logs
> > went away. I can connect to the VPN and name resolution works.
> >
> > BUT, I got five different SELinux errors instead
> >
> > rpmdb was denied read access on resolv.conf
> > rpcbind was denied name_bind access on port 64866
> > chronyd was denied getattr access on no-stub-resolv.conf
> > gnome-shell was denied getattr access on no-stub-resolv.conf
> > geoclue was denied getattr access on no-stub-resolv.conf
> 
> Hm, looks like I've been getting some of these selinux errors too, but  
> haven't noticed it.
> 
> Created bug 1913276 to fix no-stub-resolv.conf, the selinux policy needs to  
> be fixed.


Thanks for opening that bug.

Note that my outbound e-mail was being blocked by this. I am using postfix for outbound and the smtp alerts were triggering for each outbound e-mail attempt and were just queuing up until I did "sudo setenforce 0". I verified that new outbound mail was sent after that and I also "pushed" the queue with "postqueue -f" and watched the log as it drained.

I might just switch back to the regular setup so that I can have selinux enabled while waiting for the fix to this.


-- 
 Doug Herr
fedoraproject.org@xxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux