[Bug 1431581] Re: NIS does not start on 15.04
Update : Just went onto a client NIS server that was running 14.10 and checked the /etc/default/nis file and it was set to master, upgraded to 15.04 and it was changed to NISSERVER=false and all clients couldn't bind. Changed manually back to NISSERVER=master and all is OK. Looks like the upgrade doesn't observe the original settings -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/1431581 Title: NIS does not start on 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1431581/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431581] Re: NIS does not start on 15.04
Thanks Martin - good guess. Oddly, all the machines were working previous (with several slaves), probably for 2+ years with regular updates. Anyway, thanks for the assistance, it's all working now as expected. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/1431581 Title: NIS does not start on 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1431581/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431581] Re: NIS does not start on 15.04
Still not fully resolved ** Changed in: nis (Ubuntu) Status: Fix Released => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/1431581 Title: NIS does not start on 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1431581/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431581] Re: NIS does not start on 15.04
Still not resolved for the reason above -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/1431581 Title: NIS does not start on 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1431581/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431581] Re: NIS does not start on 15.04
Just to confirm I have updated to the official release and although nis does now start without error, the ypserve process does not get started (as described above) meaning that NIS clients work, but NIS server master and slaves do not work properly. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/1431581 Title: NIS does not start on 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1431581/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431581] Re: NIS does not start on 15.04
NIS client now starts correctly: /usr/sbin/ypbind -no-dbus However on our NIS slave the NIS server is not starting: ps -ef | grep ypserv If I start manually> ypserv - it is fine and works as expected: /usr/sbin/ypbind -no-dbus ypserv ypwhich myserver.mydomain.co.uk -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/1431581 Title: NIS does not start on 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1431581/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431581] Re: NIS does not install on 15.04
2 weeks to go an this still has not even been assigned or triaged? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/1431581 Title: NIS does not install on 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1431581/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431581] Re: NIS does not install on 15.04
Looks like this is purely the startup - I start bind manually and it all works fine and dandy. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/1431581 Title: NIS does not install on 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1431581/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1307431] Re: LXC containers fail to start when upgraded to 14.04 LTS
Yes, that works! Many thanks for your help. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1307431 Title: LXC containers fail to start when upgraded to 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1307431/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1307431] Re: LXC containers fail to start when upgraded to 14.04 LTS
When teh container is hung and i execute an lxc-stop (from a different terminal) I see a: mount: cannot mount block device /export/lxc-lib//rootfs read-only Might be connected? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1307431 Title: LXC containers fail to start when upgraded to 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1307431/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1307431] [NEW] LXC containers fail to start when upgraded to 14.04 LTS
Public bug reported: After running 14.04 LTS through beta etc. I updated to teh latest this morning and all was well. I then went into a running container, changed it's sources.list to pint to the trusty repos and upgraded (the container itself was running 13.10). All went well, I restart the container and it hangs on a restart. When I start it in the forground it just hangs : sudo lxc-start -n <4>init: plymouth-upstart-bridge main process (5) terminated with status 1 <4>init: plymouth-upstart-bridge main process ended, respawning <4>init: plymouth-upstart-bridge main process (15) terminated with status 1 <4>init: plymouth-upstart-bridge main process ended, respawning <4>init: ureadahead main process (8) terminated with status 5 <4>init: plymouth-upstart-bridge main process (19) terminated with status 1 <4>init: plymouth-upstart-bridge main process ended, respawning * Stopping Send an event to indicate plymouth is up ...done. * Starting Mount filesystems on boot ...done. * Starting Signal sysvinit that the rootfs is mounted ...done. * Starting Clean /tmp directory ...done. * Stopping Clean /tmp directory ...done. * Starting Populate and link to /run filesystem ...done. * Starting Track if upstart is running in a container ...done. * Stopping Populate and link to /run filesystem ...done. * Starting load fallback graphics devices ...done. * Starting workaround for missing events in container ...done. * Stopping workaround for missing events in container ...done. <4>init: udev-fallback-graphics main process (79) terminated with status 1 * Starting load fallback graphics devices ...fail! * Starting configure network device security ...done. * Starting set console font ...done. <4>init: console-font main process (113) terminated with status 1 * Starting set console font ...fail! * Starting userspace bootsplash ...done. * Starting Initialize or finalize resolvconf ...done. <4>init: setvtrgb main process (126) terminated with status 1 * Stopping userspace bootsplash ...done. * Starting Send an event to indicate plymouth is up ...done. * Starting Mount network filesystems ...done. * Stopping Send an event to indicate plymouth is up ...done. * Stopping Mount network filesystems ...done. * Starting Bridge socket events into upstart ...done. * Starting configure network device ...done. This is in the host syslog: Apr 14 11:48:19 sentinel kernel: [59143.539884] device vethJQQMQG entered promiscuous mode Apr 14 11:48:19 sentinel kernel: [59143.609423] IPv6: ADDRCONF(NETDEV_CHANGE): vethJQQMQG: link becomes ready Apr 14 11:48:19 sentinel kernel: [59143.609526] br0: port 2(vethJQQMQG) entered forwarding state Apr 14 11:48:19 sentinel kernel: [59143.609539] br0: port 2(vethJQQMQG) entered forwarding state Apr 14 11:48:20 sentinel kernel: [59144.885192] type=1400 audit(1397472500.484:38): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default" name="/sys/fs/pstore/" pid=8430 comm="mount" fstype="pstore" srcname="none" flags="rw" Apr 14 11:48:20 sentinel kernel: [59144.885349] type=1400 audit(1397472500.484:39): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default" name="/sys/fs/pstore/" pid=8430 comm="mount" fstype="pstore" srcname="none" flags="ro" Apr 14 11:48:22 sentinel ntpd[2085]: Listen normally on 18 vethJQQMQG fe80::fc93:63ff:feb1:3c5e UDP 123 Apr 14 11:48:22 sentinel ntpd[2085]: peers refreshed Apr 14 11:48:22 sentinel ntpd[2085]: new interface(s) found: waking up resolver ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 Date: Mon Apr 14 11:49:45 2014 InstallationDate: Installed on 2012-09-05 (585 days ago) InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1) SourcePackage: lxc UpgradeStatus: Upgraded to trusty on 2014-02-08 (64 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = br0 lxc.network.flags = up modified.conffile..etc.lxc.default.conf: [modified] mtime.conffile..etc.lxc.default.conf: 2013-03-07T17:09:54.680483 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1307431 Title: LXC containers fail to start when upgraded to 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1307431/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 957957] Re: kvm: 7767: cpu0 unhandled rdmsr: 0xc0010001
I receive these errors, however on my system(s) it is accompanied by a network dropout - Is this not a genuine bug related to debian bug #669184 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669184 [37288.613730] kvm: 2620: cpu0 unhandled rdmsr: 0xc0010001 [37922.460334] nfs: server enterprise.sec-consulting.co.uk not responding, timed out [38059.028832] kvm: 2509: cpu0 unhandled rdmsr: 0xc0010001 [38065.939026] kvm: 2475: cpu0 unhandled rdmsr: 0xc0010001 [38070.609781] kvm: 2539: cpu0 unhandled rdmsr: 0xc0010001 [38150.503415] kvm: 2509: cpu0 unhandled rdmsr: 0xc0010001 [38381.732951] kvm: 2509: cpu0 unhandled rdmsr: 0xc0010001 [38760.128451] nfs: server enterprise.sec-consulting.co.uk not responding, timed out [38808.682890] kvm: 3126: cpu0 unhandled rdmsr: 0xc0010001 Other systems were connected to NFS server and they were fine so i assume dropout was on the KVM host that produced the above logs ** Bug watch added: Debian Bug tracker #669184 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669184 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/957957 Title: kvm: 7767: cpu0 unhandled rdmsr: 0xc0010001 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/957957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 979758] Re: package fails to configure on failing to find /etc/init.d/nis
Very painful issue - system NIS server non functional and whole network is on a go slow (with timeouts), I do not know of a workaround. I tried force etc. but it all still fails. Interestingly nis installed on the clients - just seems to be this server upgrade so it may be a dependency (?) type thing. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/979758 Title: package fails to configure on failing to find /etc/init.d/nis To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/979758/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 979758] Re: package fails to configure on failing to find /etc/init.d/nis
Upgraded 11.10 KVM and NIS host to 12.04: Unpacking nis (from .../nis_3.17-32ubuntu4_amd64.deb) ... invoke-rc.d: unknown initscript, /etc/init.d/nis not found. dpkg: error processing /var/cache/apt/archives/nis_3.17-32ubuntu4_amd64.deb (--unpack): subprocess new pre-installation script returned error exit status 100 Errors were encountered while processing: /var/cache/apt/archives/nis_3.17-32ubuntu4_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/979758 Title: package fails to configure on failing to find /etc/init.d/nis To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/979758/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs