On 09/10/16 20:15, Sam Varshavchik wrote:
> Can't get any more broken than a segfault at startup :-)
>
> Looking at the carnage in /var/log/messages, it broke so bad that even 
> systemd-coredump
> choked on itself, and failed to do whatever it wanted to do. Impressive.
>
> Booted back to 4.6.7 to get things going again. Don't really have much to add 
> to bug
> 1374917, besides the sorry state of affairs from /var/log/messages.
>
> chroot might have something to do with it. I'm running named-chroot.service 

FWIW, I'm also running named-chroot.service and

[egreshko@meimei ~]$ uname -r
4.7.2-201.fc24.x86_64

But unable to reproduce your issue.

[egreshko@meimei ~]$ systemctl status named-chroot.service
● named-chroot.service - Berkeley Internet Name Domain (DNS)
   Loaded: loaded (/usr/lib/systemd/system/named-chroot.service; enabled; 
vendor pre
  Drop-In: /etc/systemd/system/named-chroot.service.d
           └─mynfssetup.conf
   Active: active (running) since Wed 2016-09-07 08:10:11 CST; 3 days ago
 Main PID: 1338 (named)

-- 
You're Welcome Zachary Quinto

Attachment: signature.asc
Description: OpenPGP digital signature

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Reply via email to