[Bug 1415651] [NEW] Serious problem with /lib/lsb/init-dunctions.d/01-upstart-lsb
You have been subscribed to a public bug:
Ubuntu server 14.10 with xfce4 desktop
Any attempt to halt samba with either service samba stop or
/etc/init.d/samba stop fails with the following message:
stop: Unknown instance:
Examining /etc/init.d/samba shows that stop issues:
stop)
/etc/init.d/samba-ad-dc stop
/etc/init.d/smbd stop
/etc/init.d/nmbd stop
Running /etc/init.d/smbd stop and /etc/init.d/nmbd stop
manually work properly.
Running /etc/init.d/samba-ad-dc stop produces the error message above
and no processes are haulted. However, I did notice that if I move into
the /etc/init.d directory and issue either samba-ad-dc stop or
./samba-ad-dc stop then the script works and the samba process is
indeed haulted.
I added set -x to the stop of the samba-ad-dc script and observed the
following:
# samba-ad-dc stop
+ PIDDIR=/var/run/samba
+ SAMBAPID=/var/run/samba/samba.pid
+ unset TMPDIR
+ test -x /usr/sbin/samba -a -r /etc/samba/smb.conf
+ . /lib/lsb/init-functions
+ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
+ [ -r /lib/lsb/init-functions.d/01-upstart-lsb ]
+ . /lib/lsb/init-functions.d/01-upstart-lsb
+ unset UPSTART_SESSION
+ _RC_SCRIPT=samba-ad-dc
+ [ -r /etc/init/samba-ad-dc.conf ]
+ which initctl
+ initctl version
+ grep -q upstart
+ exit 0
I restarted samba and then tried the following:
#/etc/init.d/samba-ad-dc stop
+ PIDDIR=/var/run/samba
+ SAMBAPID=/var/run/samba/samba.pid
+ unset TMPDIR
+ test -x /usr/sbin/samba -a -r /etc/samba/smb.conf
+ . /lib/lsb/init-functions
+ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
+ [ -r /lib/lsb/init-functions.d/01-upstart-lsb ]
+ . /lib/lsb/init-functions.d/01-upstart-lsb
+ unset UPSTART_SESSION
+ _RC_SCRIPT=/etc/init.d/samba-ad-dc
+ [ -r /etc/init//etc/init.d/samba-ad-dc.conf ]
+ _UPSTART_JOB=samba-ad-dc
+ [ -r /etc/init/samba-ad-dc.conf ]
+ which initctl
+ initctl version
+ grep -q upstart
+ initctl status samba-ad-dc
+ exec stop samba-ad-dc
stop: Unknown instance:
Note that the functions in /lib/lsb/init-functions are loaded and then
/lib/lsb/init-functions.d/01-upstart-lsb is run. Check out the next
couple of lines. When the fully qualified path /etc/init/samba-ad-dc is
used, this function fails to first properly strip it to its basename
before readding the etc/init/ path component. This causes the
subsequent line:
if [ -r /etc/init/${_RC_SCRIPT}.conf ] which initctl /dev/null \
initctl version 2/dev/null | grep -q upstart
to fail. The unknown instance message must be issued from
/sbin/initctl.
More investigation needs to be done. I will report any additional
information I discover. I see a lot of different bug reports related to
this stop: Unknown instance: message, and I wonder if they are not all
related.
** Affects: samba (Ubuntu)
Importance: Undecided
Status: New
** Tags: bot-comment
--
Serious problem with /lib/lsb/init-dunctions.d/01-upstart-lsb
https://bugs.launchpad.net/bugs/1415651
You received this bug notification because you are a member of Ubuntu Server
Team, which is subscribed to samba in Ubuntu.
--
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 1416003] Re: open-vm-dkms fails to build with latest Precise kernel
Uploaded for Precise. This does not affect any newer versions. ** Changed in: open-vm-tools (Ubuntu) Status: In Progress = Fix Released ** Changed in: open-vm-tools (Ubuntu) Assignee: Luis Henriques (henrix) = (unassigned) ** Changed in: open-vm-tools (Ubuntu) Importance: High = Undecided -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1416003 Title: open-vm-dkms fails to build with latest Precise kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1416003/+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 1292234] Re: qcow2 image corruption on non-extent filesystems (ext3)
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Chris J Arges (arges) ** Changed in: linux (Ubuntu) Importance: Undecided = High ** Changed in: linux (Ubuntu) Status: New = In Progress ** Changed in: qemu (Ubuntu) Status: In Progress = Invalid ** Changed in: qemu (Ubuntu) Assignee: Chris J Arges (arges) = (unassigned) ** Changed in: qemu (Ubuntu) Importance: High = Undecided -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1292234 Title: qcow2 image corruption on non-extent filesystems (ext3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1292234/+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 1415651] Re: Serious problem with /lib/lsb/init-dunctions.d/01-upstart-lsb
** Package changed: ubuntu = samba (Ubuntu) ** Tags added: utopic -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1415651 Title: Serious problem with /lib/lsb/init-dunctions.d/01-upstart-lsb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1415651/+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 1395941] Re: package backuppc 3.3.0-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: backuppc (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to backuppc in Ubuntu. https://bugs.launchpad.net/bugs/1395941 Title: package backuppc 3.3.0-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1395941/+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 1414925] Re: ntpd seems to add offsets instead of subtracting them
** Changed in: ntp (Ubuntu) Assignee: (unassigned) = Liam Young (gnuoy) -- 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/1414925 Title: ntpd seems to add offsets instead of subtracting them To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1414925/+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 1416463] [NEW] MoinMoin tableclass not working
Public bug reported: (python-moinmoin 1.9.7 on Ubuntu 14.04) Tried to creat a class in the .css file for tables without borders, but testing the class in a wiki page, like this: ||tableclass=noborder ... || ... || didn't work. As a workaround I tried to remove the double quotes: ||tableclass=noborder ... || ... || It worked and I had the table without borders. Basically the double quotes create problems to the html code. This bug seems to be already known https://moinmo.in/MoinMoinBugs/1.9.7Table_styles/class%20not%20working I also tried the new moinmoin version 1.9.8 and found that both ways to write the class, with or without double quotes, are working (tableclass=noborder and tableclass=noborder). Is there any chance to get the 1.9.8 into the Ubuntu repos? Thanks! ** Affects: moin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to moin in Ubuntu. https://bugs.launchpad.net/bugs/1416463 Title: MoinMoin tableclass not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/moin/+bug/1416463/+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 1395941] Re: package backuppc 3.3.0-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: backuppc (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to backuppc in Ubuntu. https://bugs.launchpad.net/bugs/1395941 Title: package backuppc 3.3.0-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1395941/+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 1416071] Re: package python-urllib3 1.7.1-1build1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Your /usr/bin/python symlink is incorrect. It needs to point to Python 2, as per PEP 394. Otherwise system scripts will fail, because they expect to find Python 2 there, not Python 3. Have you changed this by hand? So this looks like a local configuration problem, rather than a bug in Ubuntu. You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Since we use this bug tracker to track bugs in Ubuntu, rather than configuration problems, I'm marking this bug as Invalid. This helps us to focus on fixing bugs in Ubuntu. If you believe that this is really a bug, then you may find it helpful to read How to report bugs effectively http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: python-urllib3 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-urllib3 in Ubuntu. https://bugs.launchpad.net/bugs/1416071 Title: package python-urllib3 1.7.1-1build1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-urllib3/+bug/1416071/+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 1403648] Re: Apparmor denies qemu access to a number of important directories.
** Changed in: libvirt (Ubuntu Trusty) Status: Confirmed = Fix Released ** Changed in: libvirt (Ubuntu Utopic) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1403648 Title: Apparmor denies qemu access to a number of important directories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1403648/+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 1416529] Re: package php5-gd 5.5.9+dfsg-1ubuntu4.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1416529 Title: package php5-gd 5.5.9+dfsg-1ubuntu4.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1416529/+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 1292234] Re: qcow2 image corruption on non-extent filesystems (ext3)
** Description changed: + [Impact] + Users of non-extent ext4 filesystems (ext4 ^extents, or ext3 w/ CONFIG_EXT4_USE_FOR_EXT23=y) can encounter data corruption when using fallocate with FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE flags. This seems to be a regression in ext4_ind_remove_space introduced in 4f579ae7, whereas commit 77ea2a4b passes the following test case. + + [Test Case] + 1) Setup ext4 ^extents, or ext3 filesystem with CONFIG_EXT4_USE_FOR_EXT23=y + 2) Create and install a VM using a qcow2 image and store the file on the filesystem + 3) Snapshot the image with qemu-img + 4) Boot the image and do some disk operations (fio,etc) + 5) Shutdown image and delete snapshot + 6) Repeat 3-5 until VM no longer boots due to image corruption, generally this takes a few iterations depending on disk operations. + + + -- + The security team uses a tool (http://bazaar.launchpad.net/~ubuntu- bugcontrol/ubuntu-qa-tools/master/view/head:/vm-tools/uvt) that uses libvirt snapshots quite a bit. I noticed after upgrading to trusty some time ago that qemu 1.7 (and the qemu 2.0 in the candidate ppa) has had stability problems such that the disk/partition table seems to be corrupted after removing a libvirt snapshot and then creating another with the same name. I don't have a very simple reproducer, but had enough that hallyn suggested I file a bug. First off: qemu-kvm 2.0~git-20140307.4c288ac-0ubuntu2 $ cat /proc/version_signature Ubuntu 3.13.0-16.36-generic 3.13.5 $ qemu-img info ./forhallyn-trusty-amd64.img image: ./forhallyn-trusty-amd64.img file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 4.0G cluster_size: 65536 Format specific information: compat: 0.10 Steps to reproduce: 1. create a virtual machine. For a simplified reproducer, I used virt-manager with: OS type: Linux Version: Ubuntu 14.04 Memory: 768 CPUs: 1 Select managed or existing (Browse, new volume) Create a new storage volume: qcow2 Max capacity: 8192 Allocation: 0 Advanced: NAT kvm x86_64 firmware: default 2. install a VM. I used trusty-desktop-amd64.iso from Jan 23 since it seems like I can hit the bug more reliably if I have lots of updates in a dist-upgrade. I have seen this with lucid-trusty guests that are i386 and amd64. After the install, reboot and then cleanly shutdown 3. Backup the image file somewhere since steps 1 and 2 take a while :) 4. Execute the following commands which are based on what our uvt tool does: $ virsh snapshot-create-as forhallyn-trusty-amd64 pristine uvt snapshot $ virsh snapshot-current --name forhallyn-trusty-amd64 pristine $ virsh start forhallyn-trusty-amd64 $ virsh snapshot-list forhallyn-trusty-amd64 # this is showing as shutoff after start, this might be different with qemu 1.5 in guest: sudo apt-get update sudo apt-get dist-upgrade 780 upgraded... shutdown -h now $ virsh snapshot-delete forhallyn-trusty-amd64 pristine --children $ virsh snapshot-create-as forhallyn-trusty-amd64 pristine uvt snapshot $ virsh start forhallyn-trusty-amd64 # this command works, but there is often disk corruption The idea behind the above is to create a new VM with a pristine snapshot that we could revert later if we wanted. Instead, we boot the VM, run apt-get dist-upgrade, cleanly shutdown and then remove the old 'pristine' snapshot and create a new 'pristine' snapshot. The intention is to update the VM and the pristine snapshot so that when we boot the next time, we boot from the updated VM and can revert back to the updated VM. After running 'virsh start' after doing snapshot-delete/snapshot-create- as, the disk may be corrupted. This can be seen with grub failing to find .mod files, the kernel not booting, init failing, etc. This does not seem to be related to the machine type used. Ie, pc- i440fx-1.5, pc-i440fx-1.7 and pc-i440fx-2.0 all fail with qemu 2.0, pc- i440fx-1.5 and pc-i440fx-1.7 fail with qemu 1.7 and pc-i440fx-1.5 works fine with qemu 1.5. Only workaround I know if is to downgrade qemu to 1.5.0+dfsg-3ubuntu5.4 from Ubuntu 13.10. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1292234 Title: qcow2 image corruption on non-extent filesystems (ext3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1292234/+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 1292234] Re: qcow2 image corruption on non-extent filesystems (ext3)
Sent e-mail upstream about this issue: http://marc.info/?l=linux- fsdevelm=142264422605440w=2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1292234 Title: qcow2 image corruption on non-extent filesystems (ext3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1292234/+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 1416529] [NEW] package php5-gd 5.5.9+dfsg-1ubuntu4.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: this error has been realised while updating system automaticly... ProblemType: Package DistroRelease: Ubuntu 14.04 Package: php5-gd 5.5.9+dfsg-1ubuntu4.5 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Thu Jan 29 17:06:22 2015 DuplicateSignature: package:php5-gd:5.5.9+dfsg-1ubuntu4.5:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-01-19 (10 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: php5 Title: package php5-gd 5.5.9+dfsg-1ubuntu4.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: php5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1416529 Title: package php5-gd 5.5.9+dfsg-1ubuntu4.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1416529/+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 1416600] [NEW] I try to install tripwire, then in postfix configuration it freeze
Public bug reported: trying to install tripwire firstime using apt-get, then in postfix window freeze. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: postfix (not installed) ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 AptOrdering: postfix: Install tripwire: Install zend-server-php-5.5: Configure postfix: Configure tripwire: Configure Architecture: amd64 Date: Fri Jan 30 18:10:15 2015 ErrorMessage: subprocess new pre-installation script returned error exit status 5 InstallationDate: Installed on 2015-01-21 (10 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: postfix Title: package postfix (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1416600 Title: I try to install tripwire, then in postfix configuration it freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1416600/+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 1414887] Re: dns query from localnetwork ignored
** Summary changed: - dns query from localnetwork are blocked + dns query from localnetwork ignored -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1414887 Title: dns query from localnetwork ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1414887/+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 1414887] Re: dns query from localnetwork ignored
Ah, thanks Thomas. You lead me to the right direction. As Simon Kelley, the author of dnsmasq said in the new dnsmasq manpag, `local-service` is intended to be set as a default on installation, to allow unconfigured installations to be useful... it will have no effect, but for otherwise-unconfigured installations, it stops dnsmasq from being vulnerable to DNS-reflection attacks, I'm changing this bug report to bear the purpose to have dnsmasq better configured out of box for Ubuntu (14.10+). - First, as suggested by the author of dnsmasq, the `local-service` should be in the default configuration. However, Ubuntu 14.10 doesn't have that: % cat /etc/dnsmasq.conf /etc/dnsmasq.d/network-manager | sed '/^$/d; /^#/d' bind-interfaces - Second, unlike its previous version, Ubuntu 14.10 now starts dnsmasq in a very restricted way. Here is what I found out how dnsmasq is started in Ubuntu 14.10: /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind- interfaces --pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid --listen-address=127.0.1.1 --conf- file=/var/run/NetworkManager/dnsmasq.conf --cache-size=0 --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf- dir=/etc/NetworkManager/dnsmasq.d I.e., that ` --listen-address=127.0.1.1` will willfully ignore any dns queries from localnetwork. This is the exact reason causing the symptom that I reported. I believe this setting should not be there, because 1. for people that need the setting, it is very easy to put it into a conf file under /etc/dnsmasq.d/; 2. however, it will make it very very difficult for people who don't need it to get rid of it unless altering the package installation. 3. Ubuntu should really ship the default setting of `local-service` instead of `listen-address`, because it is a safer default and not invasive in the meantime. it will have no effect but for an otherwise-unconfigured installation. Please consider. Meanwhile, is there any better way to get rid of that ` --listen- address=127.0.1.1`? The least that I want is to altering the package installation. Thanks ** Changed in: dnsmasq (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1414887 Title: dns query from localnetwork ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1414887/+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 1397910] Re: Puppet daemon dies from SIGUSR1 if no certificate
[Expired for puppet (Ubuntu) because there has been no activity for 60 days.] ** Changed in: puppet (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1397910 Title: Puppet daemon dies from SIGUSR1 if no certificate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1397910/+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 1414684] Re: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail)
** Changed in: bsd-mailx (Debian) Status: Unknown = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bsd-mailx in Ubuntu. https://bugs.launchpad.net/bugs/1414684 Title: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bsd-mailx/+bug/1414684/+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 1414684] Re: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail)
FWIW, I am content with the updated USN and agree with Won't Fix. Just wanted to raise the issue here in case I am not the only one bitten by this change. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bsd-mailx in Ubuntu. https://bugs.launchpad.net/bugs/1414684 Title: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bsd-mailx/+bug/1414684/+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 1416027] Re: Removing MAAS from a system is painful
This is how APT work. If you want to remove the dependencies that were automatically installed by 'maas;, you need to: `sudo apt-get autoremove --purge` Well, I understand your point but you'll admit that it's strange to do this: `sudo apt-get purge maas` And after that, to still have MAAS fully installed! I mean, it's okay when a package leaves some libraries installed behind once removed (and I understand it's how API works) but in MAAS' case the *entire service* (region, cluster) is still installed and running after you uninstall the `maas` package. It's really counter-intuitive. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1416027 Title: Removing MAAS from a system is painful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1416027/+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 1416026] Re: Uninstalling MAAS doesn't remove the postgresql DB
Hum, I tested again this morning (and answered yes to the two uninstall questions, as I did before) and this time the DB got removed okay. Maybe it's because the first time, I installed the packages differently (with dpkg -i *.deb). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1416026 Title: Uninstalling MAAS doesn't remove the postgresql DB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1416026/+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 1403648] Re: Apparmor denies qemu access to a number of important directories.
This bug was fixed in the package libvirt - 1.2.8-0ubuntu21 --- libvirt (1.2.8-0ubuntu21) vivid; urgency=medium * d/apparmor/libvirt-qemu: Update the ceph.conf allow rule (LP: #1403648) -- Serge Hallyn serge.hal...@ubuntu.com Fri, 30 Jan 2015 10:02:20 +0100 ** Changed in: libvirt (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1403648 Title: Apparmor denies qemu access to a number of important directories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1403648/+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 1403648] Re: Apparmor denies qemu access to a number of important directories.
Ideally, this would've been: /var/lib/charm/*/ceph.conf r, service name can be different. For example: [534614.823259] type=1400 audit(1422553522.478:143): apparmor=DENIED operation=open profile=libvirt-a7605ca2-0b10-4afa-b25e-3b6a83ae5552 name=/var/lib/charm/az1-compute/ceph.conf pid=43088 comm=qemu- system-x86 requested_mask=r denied_mask=r fsuid=110 ouid=0 ** Changed in: libvirt (Ubuntu Trusty) Status: Fix Released = Confirmed ** Changed in: libvirt (Ubuntu) Status: Fix Released = Confirmed ** Changed in: libvirt (Ubuntu Utopic) Status: Fix Committed = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1403648 Title: Apparmor denies qemu access to a number of important directories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1403648/+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 1416009] Re: Make squid package in 14.04 multithread supported
The affected ubuntu version is 14.04.1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/1416009 Title: Make squid package in 14.04 multithread supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1416009/+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 1416003] Re: open-vm-dkms fails to build with latest Precise kernel
Here's v2 of the debdiff, now with a proper fix. I've also done some testing in a Precise VM. ** Changed in: open-vm-tools (Ubuntu Precise) Status: New = In Progress ** Changed in: open-vm-tools (Ubuntu Precise) Assignee: (unassigned) = Luis Henriques (henrix) ** Changed in: open-vm-tools (Ubuntu Precise) Importance: Undecided = High ** Patch added: open-vm-tools-v2.debdiff https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1416003/+attachment/4308795/+files/open-vm-tools-v2.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1416003 Title: open-vm-dkms fails to build with latest Precise kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1416003/+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 1410398] Re: Make download in pip available
Thank you for your report. This is something that upstream would need to do, not Ubuntu developers. So it really belongs in upstream's bug tracker or some kind of communication upstream, not here. If you want to see this done, you should speak to upstream. Since there's nothing we can do for this in Ubuntu, I'm marking this bug as Invalid in the Ubuntu packaging task. ** Changed in: beautifulsoup4 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to beautifulsoup4 in Ubuntu. https://bugs.launchpad.net/bugs/1410398 Title: Make download in pip available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/beautifulsoup4/+bug/1410398/+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 1393444] Re: machine unit connects to apiserver but stays in agent-state: pending
@sinzui: closing this as invalid, as I later confirmed this to be a MTU issue. ** Changed in: juju-core Status: Triaged = Invalid ** Changed in: juju-core (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1393444 Title: machine unit connects to apiserver but stays in agent-state: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1393444/+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 1416009] Re: Make squid package in 14.04 multithread supported
Thank you for taking the time to report this bug and helping to make Ubuntu better. I understand that you have a single use case here, and that you expect this to just work on 14.04. From the point of view of fixing it though, there are a few different changes required, which need to be treated differently. These are: 1) Create /var/run/squid3 automatically. 2) Drop -N from being specified to squid. 3) Apply change 1) as an update to 14.04. 4) Apply change 2) as an update to 14.04. 1) and 2) would apply to the development release and thus the next LTS. 3) and 4) would apply the change to existing 14.04 users. Our policies require us to do 1) before 3), and 2) before 4), to avoid users experiencing a regression when upgrading to a new release in the future. It also seems to me that you can do all of this on a system by editing /etc/init/squid3. This is a conffile and changing it manually is permitted - the packaging system will endeavour to leave any customisation to this file intact. So an available workaround to all of this is to manually correct /etc/init/squid3. So considering each necessary step individually: For 1) and 2), note that we're hoping to switch to systemd this cycle, so the upstart script will no longer be relevant. I don't see a systemd unit defined, so it will fall back to the init.d script. This makes 1) and 2) quite different to 3) and 4): the former needs to be fixed in /etc/init.d, and the latter in /etc/init. 1) I don't see /var/run/squid3 being created in the init.d script, so it looks like we'll need to fix this in Vivid. 2) It doesn't look like -N is being used, so this shouldn't be a problem in Vivid. 3) If this is required, it is a bug that the upstart script doesn't do this before starting squid. It would be reasonable to fix this in an update to 14.04, but is it worth it? It's for a non-default use case, and you'll need to apply a workaround for 4) anyway (see below). On the other hand, if it turns out that many people are affected by this, it would be valid to issue an update to 14.04 for this. 4) I don't think we can change this in an update to 14.04. It would change behaviour of squid to every existing 14.04 user, and unless further analysis suggests otherwise, I think this would present too big a regression risk to existing users. So I think you will need to apply the workaround as above. So in conclusion: I think we should fix 1) in Vivid. 2) doesn't appear to be required. 3) is reasonable to fix in an update to 14.04, but I'm not sure it's worth it given that users will need to apply a workaround anyway, so unless an objection is made, I propose not to do it. For 4), the only reasonable option is for 14.04 users to apply the workaround. I'll leave this bug open to track 1). ** Changed in: squid (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/1416009 Title: Make squid package in 14.04 multithread supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1416009/+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 1414684] Re: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail)
Thanks for the suggestion, I've added a note to the USN to this effect. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bsd-mailx in Ubuntu. https://bugs.launchpad.net/bugs/1414684 Title: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bsd-mailx/+bug/1414684/+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 1414684] Re: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail)
Bug against Bootmail is here: https://bugs.launchpad.net/ubuntu/+source/bootmail/+bug/1414696 What do you suggest instead? I don't really have a suggestion and I am not disputing that this change was necessary. But the USN description doesn't even mention that specifying sendmail options after -- is no longer supported. After some back and forth (and seriously doubting my own sanity) I inferred that fact from the changelog which mentions a 83-nosendmail.patch. I just wish the USN advertised and documented this change and its full impact better. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bsd-mailx in Ubuntu. https://bugs.launchpad.net/bugs/1414684 Title: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bsd-mailx/+bug/1414684/+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 1414684] Re: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail)
So I think it's a valid concern that this was broken, but the conclusion is that there's nothing that we can do about it since the choice is to leave users vulnerable or to break this edge case. Won't Fix seems appropriate. ** Changed in: bsd-mailx (Ubuntu) Status: New = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bsd-mailx in Ubuntu. https://bugs.launchpad.net/bugs/1414684 Title: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bsd-mailx/+bug/1414684/+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 1414925] [NEW] ntpd seems to add offsets instead of subtracting them
You have been subscribed to a public bug by Robie Basak (racb): ntpd seems to add offsets instead of subtracting them from the running synchronized clock, leading to time running away fast in one direction -- forward if the offset is positive, -- backward if the offset is negative, until the offset reaches its maximum. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Tue Jan 27 08:25:55 2015 InstallationDate: Installed on 2014-02-10 (350 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) KernLog: NtpStatus: ntpq: read: Connection refused ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ntp UpgradeStatus: Upgraded to trusty on 2014-02-18 (342 days ago) modified.conffile..etc.ntp.conf: [modified] mtime.conffile..etc.ntp.conf: 2015-01-27T07:41:51.747605 ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Affects: ntp (CentOS) Importance: Unknown Status: New ** Affects: ntp (Debian) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- ntpd seems to add offsets instead of subtracting them https://bugs.launchpad.net/bugs/1414925 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. -- 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 1414684] Re: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail)
The change was unfortunately needed to properly handle email addresses that start with -. Please file a bug against bootmail. ** Bug watch added: Debian Bug tracker #776498 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776498 ** Also affects: bsd-mailx (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776498 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bsd-mailx in Ubuntu. https://bugs.launchpad.net/bugs/1414684 Title: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bsd-mailx/+bug/1414684/+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 1414684] Re: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail)
I find it disconcerting that a security update completely removes functionality that has been available and expected for many years without providing a proper compatibility layer. Is this really the way to do this? What do you suggest instead? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bsd-mailx in Ubuntu. https://bugs.launchpad.net/bugs/1414684 Title: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bsd-mailx/+bug/1414684/+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 1414684] Re: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail)
Relevant links: http://www.ubuntu.com/usn/usn-2455-1/ http://people.canonical.com/~ubuntu-security/cve/2014/CVE-2014-7844.html ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-7844 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bsd-mailx in Ubuntu. https://bugs.launchpad.net/bugs/1414684 Title: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bsd-mailx/+bug/1414684/+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 1416039] [NEW] Broken apparmor profile
You have been subscribed to a public bug by Robie Basak (racb): I enabled apparmor profile for squid3 by removing symlink in /etc/apparmor.d/disable This broke squid, even squid3 -z was failing with: assertion failed: Kid.cc:39: cpid 0 and I saw the following apparmor message: apparmor=DENIED operation=exec profile=/usr/sbin/squid3 name=/usr/sbin/squid3 pid=23413 comm=squid3 requested_mask=x denied_mask=x fsuid=0 ouid=0 This can be worked around by adding the following line to /etc/apparmor.d/usr.sbin.squid3: /usr/sbin/squid3 ix, ** Affects: squid3 (Ubuntu) Importance: Undecided Status: Confirmed -- Broken apparmor profile https://bugs.launchpad.net/bugs/1416039 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. -- 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
