[Bug 1406105] Re: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS
I verified that the bug is fixed in version 2.1.12+dfsg-1.2ubuntu8.1 and that the upgrade process (restart) works as intended. Thank you very much for your efforts in fixing this bug. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1406105 Title: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+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 1406105] Re: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1406105 Title: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+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 1406105] [NEW] Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS
Public bug reported: The freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS (Trusty Tahr) has a bug in the logrotate script (/etc/logrotate.d/freeradius): The command /etc/init.d/freeradius reload is used for reloading freeradius after its logfile(s) have been rotated. However, in Ubuntu 14.04 LTS freeradius is managed by Upstart, so that the script cannot work (the PID file does not exist). Therefore, the logrotate script should use initctl reload freeradius instead. Please note that this might not work either at the moment, due to bug #1282683. However, when this bug is finally fixed, the command mentioned earlier should work. ** Affects: freeradius (Ubuntu) Importance: Undecided Status: New ** Patch added: Suggested patch for logrotate script https://bugs.launchpad.net/bugs/1406105/+attachment/4288786/+files/freeradius_logrotate.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to freeradius in Ubuntu. https://bugs.launchpad.net/bugs/1406105 Title: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+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 1406105] Re: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS
I just realized that there is a better solution for the logrotate script: By using service freeradius reload, the script will work when Upstart is used but also when the traditional init script is used. ** Patch added: Revised patch for the logrotate script https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+attachment/4288787/+files/freeradius_logrotate.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to freeradius in Ubuntu. https://bugs.launchpad.net/bugs/1406105 Title: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+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 1125611] Re: DKMS brcompat module circular dependency causes broken module
I tested the following packages from precise-proposed on Ubuntu 12.04 LTS (amd64) and they work fine for me: openvswitch-brcompat_1.4.0-1ubuntu1.5 openvswitch-common_1.4.0-1ubuntu1.5 openvswitch-controller_1.4.0-1ubuntu1.5 openvswitch-datapath-dkms_1.4.0-1ubuntu1.5 openvswitch-pki_1.4.0-1ubuntu1.5 openvswitch-switch_1.4.0-1ubuntu1.5 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1125611 Title: DKMS brcompat module circular dependency causes broken module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1125611/+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 1125611] Re: Upgrade to 1.4.0-1ubuntu1.4 breaks brcompat support
I do not think that it is the same bug as originally described in bug #1088160. This bug was an issue with the build system. However, it might be the same problem that that one comment (https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1088160/comments/2) to that bug described. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1125611 Title: Upgrade to 1.4.0-1ubuntu1.4 breaks brcompat support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1125611/+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 1125611] Re: DKMS brcompat module circular dependency causes broken module
I can confirm the the new version (from the PPA) fixes the problem for me. Thank you very much for the quick solution! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1125611 Title: DKMS brcompat module circular dependency causes broken module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1125611/+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 1125611] [NEW] Upgrade to 1.4.0-1ubuntu1.4 breaks brcompat support
Public bug reported: On Ubuntu 12.04.2 LTS, after an automatic upgrade from openvswitch 1.4.0-1ubuntu1.3 to openvswith 1.4.0-1ubuntu1.4 the brcompat support does not work any longer. The brcompat kernel module can be build, installed, and loaded, but openvswitch-brcompatd will not start with the error message: ovs- brcompatd: could not open brcompat socket. Check brcompat kernel module. After a downgrade back to version 1.4.0-1ubuntu1.3 brcompat works again. I think this is essentially the same problem as described here: https://answers.launchpad.net/ubuntu/+source/openvswitch/+question/221334 It might be unrelated, but after the upgrade lsmod does not list the openvswitch module as a dependency of the brcompat module. After downgrading, the dependency is shown again. ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1125611 Title: Upgrade to 1.4.0-1ubuntu1.4 breaks brcompat support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1125611/+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 350936] Re: Should shut down domains on system shutdown
The problem of shutting down the virtual machines consists of two parts: If a init-script is used, libvirtd might be killed, before the shutdown command has been sent to the virtual machines. If the pre-stop script in the libvirt-bin upstart job is used or a new upstart job starting on stopping libvirt-bin is used, the computer is rebooted, the VMs are killed by the sendsigs script. Even if the sendsigs script is modified to not kill the VMs, the reboot or halt script might run before the libvirt-bin upstart job has been stopped. I use the following approach, which works quite well for me: I added a libvirt-shutdown-domains upstart job, which is a task starting on stopping libvirt-bin, thus running before libvirt-bin is stopped. This makes sure that libvirt-bin is not stopped, before the VMs are shutdown. In fact, I also included a runlevel check in the libvirt-shutdown-domains script, so that the VMs are only shutdown, when libvirtd is stopped because of a runlevel change. This allows for libvirtd to be restarted (e.g. when libvirt-bin is upgraded) without having to shutdown all VMs. I also added a init-script running before the sendsigs script, which waits for libvirt-bin to be stopped (or a timeout, whichever occurs first). Thus, sendsigs will not kill VMs and the machine will not be rebooted or powered off, before the VMs have been stopped. The scripts I wrote for this can be found at http://sebastian.marsching.com/wiki/Linux/KVM#Shutdown_virtual_machines_on_host_system_shutdown and some more explanations can be found at http://sebastian.marsching.com/blog/archives/112-KVM-and-Graceful- Shutdown-on-Ubuntu.html. The solution I created is not perfect though because of two issues: 1. The python-libvirt package is needed, because I use a Python script to shutdown the virtual machines. You might want to use a shell script using virsh for that, thus eliminating this dependency. 2. The timeout, after which the shutdown will proceed anyway, is configured at two different places: The init-script and the Python script called by the upstart job. You might want to put both in the same place (e.g. /etc/default/libvirt-bin). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/350936 Title: Should shut down domains on system shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/350936/+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
