[Bug 1960923] Re: needrestart is being skipped since dpkg has failed
Same here. Fix for me was to manually uninstall linux-firmware-raspi2 first. The new package installed fine after that. Preparing to unpack .../linux-firmware-raspi_6-0ubuntu2_arm64.deb ... Removing 'diversion of /lib/firmware/brcm/brcmfmac43456-sdio.raspberrypi,4-model-b.txt to /lib/firmware/brcm/brcmfmac43456-sdio.raspberrypi,4-model-b.txt.distrib by linux-firmware-raspi2' Removing 'diversion of /lib/firmware/brcm/brcmfmac43456-sdio.txt to /lib/firmware/brcm/brcmfmac43456-sdio.txt.distrib by linux-firmware-raspi2' Removing 'diversion of /lib/firmware/brcm/brcmfmac43436s-sdio.txt to /lib/firmware/brcm/brcmfmac43436s-sdio.txt.distrib by linux-firmware-raspi2' Removing 'diversion of /lib/firmware/brcm/brcmfmac43436-sdio.txt to /lib/firmware/brcm/brcmfmac43436-sdio.txt.distrib by linux-firmware-raspi2' Removing 'diversion of /lib/firmware/cypress/cyfmac43430-sdio.bin to /lib/firmware/cypress/cyfmac43430-sdio.bin.distrib by linux-firmware-raspi2' dpkg-divert: error: rename involves overwriting '/lib/firmware/cypress/cyfmac43430-sdio.bin' with different file '/lib/firmware/cypress/cyfmac43430-sdio.bin.distrib', not allowed dpkg: error processing archive /var/cache/apt/archives/linux-firmware-raspi_6-0ubuntu2_arm64.deb (--unpack): new linux-firmware-raspi package pre-installation script subprocess returned error exit status 2 dpkg-divert: error: mismatch on package when removing 'diversion of /lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-a-plus.txt by linux-firmware-raspi' found 'diversion of /lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-a-plus.txt to /lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-a-plus.txt.distrib by linux-firmware-raspi2' dpkg: error while cleaning up: new linux-firmware-raspi package post-removal script subprocess returned error exit status 2 Preparing to unpack .../linux-firmware-raspi2_6-0ubuntu2_arm64.deb ... Unpacking linux-firmware-raspi2 (6-0ubuntu2) over (6-0ubuntu0~21.10.1) ... Errors were encountered while processing: /var/cache/apt/archives/linux-firmware-raspi_6-0ubuntu2_arm64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960923 Title: needrestart is being skipped since dpkg has failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi/+bug/1960923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888936] [NEW] cifsd deadlocks / CIFS related Oopses
Public bug reported: We're running a server at AWS which collects data from machines over CIFS. This involves a a lot of mounting and umounting of CIFS (about 100 targets with 2 shares each with 10 delay in between). The targets might sometimes become unavailable when they turned of for the weekend or rebooted. The server doing this has to be rebooted every few hours because CIFS connection start to hang and don't recover. The usual symptom is: Jul 24 10:12:59 connector kernel: [ 7765.705409] CIFS: Attempting to mount //172.22.2.112/Meldung Jul 24 10:13:01 connector kernel: [ 7767.689258] CIFS: Attempting to mount //172.22.2.112/Wartung Jul 24 10:13:06 connector kernel: [ 7772.758283] CIFS: Attempting to mount //172.30.113.108/Meldung Jul 24 10:13:06 connector kernel: [ 7773.300475] CIFS: Attempting to mount //172.30.113.108/Wartung Jul 24 10:13:09 connector kernel: [ 7776.364516] CIFS: Attempting to mount //172.30.99.55/Meldung Jul 24 10:13:11 connector kernel: [ .978731] CIFS: Attempting to mount //172.30.99.55/Wartung [...] Jul 24 10:16:13 connector kernel: [ 7960.390529] CIFS VFS: \\172.30.113.108 has not responded in 180 seconds. Reconnecting... Jul 24 10:16:15 connector kernel: [ 7962.468649] CIFS VFS: \\172.30.93.171 has not responded in 180 seconds. Reconnecting... Jul 24 10:16:18 connector kernel: [ 7964.999037] CIFS VFS: \\172.30.99.55 has not responded in 180 seconds. Reconnecting... Jul 24 10:16:31 connector kernel: [ 7977.798821] INFO: task cifsd:26252 blocked for more than 120 seconds. Jul 24 10:16:31 connector kernel: [ 7977.803730] Not tainted 5.4.0-1020-aws #20-Ubuntu Jul 24 10:16:31 connector kernel: [ 7977.808526] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jul 24 10:16:31 connector kernel: [ 7977.820291] cifsd D0 26252 2 0x80004000 Jul 24 10:16:31 connector kernel: [ 7977.820298] Call Trace: Jul 24 10:16:31 connector kernel: [ 7977.820307] __schedule+0x2e3/0x740 Jul 24 10:16:31 connector kernel: [ 7977.820310] ? __switch_to_asm+0x40/0x70 Jul 24 10:16:31 connector kernel: [ 7977.820313] ? __switch_to_asm+0x34/0x70 Jul 24 10:16:31 connector kernel: [ 7977.820315] schedule+0x42/0xb0 Jul 24 10:16:31 connector kernel: [ 7977.820318] rwsem_down_read_slowpath+0x16c/0x4a0 Jul 24 10:16:31 connector kernel: [ 7977.820321] down_read+0x85/0xa0 Jul 24 10:16:31 connector kernel: [ 7977.820324] iterate_supers_type+0x70/0xf0 Jul 24 10:16:31 connector kernel: [ 7977.820411] ? cifs_set_cifscreds.isra.0+0x800/0x800 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820429] cifs_reconnect+0x8a/0xdc0 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820433] ? vprintk_func+0x4c/0xbc Jul 24 10:16:31 connector kernel: [ 7977.820449] cifs_readv_from_socket+0x17a/0x260 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820465] cifs_read_from_socket+0x4c/0x70 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820482] ? allocate_buffers+0x43/0x130 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820497] cifs_demultiplex_thread+0xe1/0xcc0 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820500] kthread+0x104/0x140 Jul 24 10:16:31 connector kernel: [ 7977.820516] ? cifs_handle_standard+0x1b0/0x1b0 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820518] ? kthread_park+0x90/0x90 Jul 24 10:16:31 connector kernel: [ 7977.820520] ret_from_fork+0x22/0x40 Jul 24 10:16:31 connector kernel: [ 7977.820524] INFO: task cifsd:26328 blocked for more than 120 seconds. Jul 24 10:16:31 connector kernel: [ 7977.827503] Not tainted 5.4.0-1020-aws #20-Ubuntu That is, cifsd gets stuck fetching credentials for the reconnect. I'm attaching the full syslog with stack traces from all hung cifsd task (I don't see where the deadlock is there). The mounting/unmounting is done in a privileged Docker container. If we restart that, we usually run into an Oops: Jul 25 07:43:29 connector kernel: [64677.164367] Oops: [#1] SMP NOPTI Jul 25 07:43:29 connector kernel: [64677.164370] CPU: 0 PID: 265452 Comm: cifsd Not tainted 5.4.0-1020-aws #20-Ubuntu Jul 25 07:43:29 connector kernel: [64677.164370] Hardware name: Amazon EC2 t3a.large/, BIOS 1.0 10/16/2017 Jul 25 07:43:29 connector kernel: [64677.164400] RIP: 0010:cifs_reconnect+0x9be/0xdc0 [cifs] Jul 25 07:43:29 connector kernel: [64677.164403] Code: e8 bb 43 0c d5 66 90 48 8b 45 c0 48 8d 55 c0 4c 8d 6d b8 48 39 c2 74 62 49 be 00 01 00 00 00 00 ad de 48 8b 45 c0 4c 8d 78 f 8 <48> 8b 00 48 8d 58 f8 4d 39 ef 74 3d 49 8b 57 10 48 89 50 08 48 89 Jul 25 07:43:29 connector kernel: [64677.218175] RSP: 0018:bf25c0b27cf8 EFLAGS: 00010286 Jul 25 07:43:29 connector kernel: [64677.222539] RAX: RBX: 9cdef66f0800 RCX: 95cd8510 Jul 25 07:43:29 connector kernel: [64677.227607] RDX: bf25c0b27d30 RSI: bf25c0b27d18 RDI: c0aeec18 Jul 25 07:43:29 connector kernel: [64677.232638] RBP: bf25c0b27d70 R08: 0180 R09: Jul 25 07:43:29
[Bug 1888936] Re: cifsd deadlocks / CIFS related Oopses
** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1888936/+attachment/5395685/+files/kern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888936 Title: cifsd deadlocks / CIFS related Oopses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1888936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307665] [NEW] signal entries in audit.log send aa-logprof in infinite loop
Public bug reported: Trusty with apparmor 2.8.95~2430-0ubuntu5 Log entries with operation=signal send aa-logprof into an infinite loop. With LOGPROF_DEBUG=3 I get the following in /var/log/apparmor/logprof.log, then aa-logprof is in busy loop. [...] 2014-04-14 21:02:12,315 - ReadLog - read_log: type=AVC msg=audit(1397430151.932:5592): apparmor=DENIED operation=signal profile=/usr/lib/postfix/master pid=23348 comm=master requested_mask=send denied_mask=send signal=term peer=/usr/lib/postfix/smtp 2014-04-14 21:02:12,315 - ReadLog - read_log: seenmark = True 2014-04-14 21:02:12,315 - ReadLog - parse_log_record: type=AVC msg=audit(1397430151.932:5592): apparmor=DENIED operation=signal profile=/usr/lib/postfix/master pid=23348 comm=master requested_mask=send denied_mask=send signal=term peer=/usr/lib/postfix/smtp 2014-04-14 21:02:12,315 - ReadLog - parse_event: type=AVC msg=audit(1397430151.932:5592): apparmor=DENIED operation=signal profile=/usr/lib/postfix/master pid=23348 comm=master requested_mask=send denied_mask=send signal=term peer=/usr/lib/postfix/smtp Even if logprof doesn't know how to handle these entries, it shouldn't fail in this way - just ignore those lines... (Of course, proper support for those entries would be preferred because it's a PITA to add them manually to profiles). ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307665 Title: signal entries in audit.log send aa-logprof in infinite loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1307665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174537] [NEW] Broken debsums
Public bug reported:
The byobu 5.35-0ubuntu1 deb has wrong md5 sums for three files:
# dpkg -s byobu
Package: byobu
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 543
Maintainer: Dustin Kirkland kirkl...@ubuntu.com
Architecture: all
Version: 5.35-0ubuntu1
Replaces: byobu-extras ( 2.17), screen-profiles ( 2.0),
screen-profiles-extras ( 2.0)
Provides: byobu-extras, screen-profiles, screen-profiles-extras
Depends: debconf (= 0.5) | debconf-2.0, gettext-base, python, python-newt (=
0.52.2-11), tmux (= 1.5) | screen
Recommends: screen, tmux (= 1.5)
Suggests: apport, lsb-release, po-debconf, ttf-ubuntu-font-family (=
0.80-0ubuntu1~medium), update-notifier-common, vim, w3m
Breaks: byobu-extras ( 2.17), screen-profiles ( 2.0),
screen-profiles-extras ( 2.0)
Enhances: screen
Conffiles:
/etc/profile.d/Z97-byobu.sh 4b01a44abbfc795a62d5777617536b89
/etc/byobu/socketdir 774a796c75a097ffd7c5c7492cb39568
/etc/byobu/backend 4d8e6f18b91581878bb89f9d64c37336
Description: powerful, text based window manager and shell multiplexer
Byobu is Ubuntu's text-based window manager based on GNU Screen.
Using Byobu, you can quickly create and move between different windows
over a single SSH connection or TTY terminal, monitor dozens of important
statistics about your system, detach and reattach to sessions later
while your programs continue to run in the background.
Homepage: http://byobu.co
# debsums -s byobu
debsums: changed file /usr/bin/byobu-config (from byobu package)
debsums: changed file /usr/bin/byobu-select-session (from byobu package)
debsums: changed file /usr/lib/byobu/include/ec2instancespricing.py (from byobu
package)
# for i in $(debsums -c byobu) ; do echo -n Expected: ; grep ${i:1}
/var/lib/dpkg/info/byobu.md5sums ; echo -n Actual:; md5sum $i ; done
Expected: 910d29d0b767d5a7116ecb26420170c9 usr/bin/byobu-config
Actual: cfc15cfe982b1e6bb1fee93777bbe375 /usr/bin/byobu-config
Expected: 3297ab72d163f7fa3d4cf12e75823274 usr/bin/byobu-select-session
Actual: 4dba67b05d39b06bf86b98c9a7b2275d /usr/bin/byobu-select-session
Expected: a0a18f17af3bab94a8f567b25356323a
usr/lib/byobu/include/ec2instancespricing.py
Actual: 20b9ebf82cc85c957e951bc6b2bfbf09
/usr/lib/byobu/include/ec2instancespricing.py
** Affects: byobu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174537
Title:
Broken debsums
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1174537/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1160372] Re: Login is not possible
SuSE's fix is here https://build.opensuse.org/request/show/162591 I just rebuilt 3.0.2-1ubuntu1 with their patch, vsftpd works fine now. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/1160372 Title: Login is not possible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1160372/+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 1160372] Re: Login is not possible
SuSE's fix is here https://build.opensuse.org/request/show/162591 I just rebuilt 3.0.2-1ubuntu1 with their patch, vsftpd works fine now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1160372 Title: Login is not possible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1160372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045061] [NEW] Hardcoded chain names and rules need to go away
Public bug reported:
Version: 1.7-3
Hardcoded chain names in the init file are not very helpful as they are
hard to integrate with other software. E.g. shorewall needs
upnp_forward_chain=forwardUPnP
upnp_nat_chain=UPnP
There also should be a way to disable the iptables code in the init file
altogether.
Also, using IP adresses (EXTIP) in the rules doesn't seem very useful
for people who's external IP address changes every 24 hours (e.g. most
German DSL users).
And a minor issue: configure says The MiniUPnP daemon will listen on a
specific interface for requests on your local network. This interface
shouldn't be accessible from the public network. but you actually mean
the external interface name here.
In summary, I suggest:
* The chain names used in the init script should be read from that
/etc/miniupnpd/miniupnpd.conf (upnp_forward_chain and upnp_nat_chain)
* The config process should write the external interface name
(ext_ifname) and the internal listening ip (listening_ip) to
/etc/miniupnpd/miniupnpd.conf. The init script should use the value
from that file.
* -i ${MiniUPnPd_EXTERNAL_INTERFACE} -o ${EXTIP} -a
${MiniUPnPd_LISTENING_IP} needs to go away. Let the daemon use the
values from /etc/miniupnpd/miniupnd.conf instead.
* The iptables rules in /etc/init.d/miniupnpd should not use an external
IP address, only an interface name (ext_ifname)
* /etc/default/minupnpd should get an option to completly disable
iptables code in /etc/init.d/miniupnpd
* The allow rule in /etc/default/miniupnpd.conf must be set through a
config question, the hardcoded 192.168.0.0/16 isn't good enough
** Affects: miniupnpd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1045061
Title:
Hardcoded chain names and rules need to go away
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/miniupnpd/+bug/1045061/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 873865] Re: Upstream logging bug in radvd - Tiny Patch
Fixed in 1:1.8.3-1 for precise. (Oneiric backport: https://launchpad.net/~jk/+archive/oneiric ) ** Changed in: radvd (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/873865 Title: Upstream logging bug in radvd - Tiny Patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/radvd/+bug/873865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 886524] [NEW] admin.pub must be readable for gitolite user
Public bug reported: (gitolite 2.0.3-2) Depending on the umask of the system the admin.pub file created by postinst might not be readable for the gitolite user. This means that gl-setup (which is run as gitolite) might not be able to read the key: === $ dpkg-reconfigure gitolite cp: cannot open `/tmp/tmp.axFdAFtOXV/admin.pub' for reading: Permission denied creating gitolite-admin... Initialized empty Git repository in /srv/gitolite/repositories/gitolite-admin.git/ creating testing... Initialized empty Git repository in /srv/gitolite/repositories/testing.git/ * WARNING * the following users have no pubkeys: admin === Adding 'chown $GITUSER $tmpdir/admin.pub' before running gl-setup fixes the issue. ** Affects: gitolite (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/886524 Title: admin.pub must be readable for gitolite user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitolite/+bug/886524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 780417] Re: debsums error for perl-base 5.10.1-17ubuntu4.1
*** This bug is a duplicate of bug 875466 *** https://bugs.launchpad.net/bugs/875466 ** This bug has been marked a duplicate of bug 875466 Lots of packages shipping with broken md5sums -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/780417 Title: debsums error for perl-base 5.10.1-17ubuntu4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/780417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875466] [NEW] Lots of packages shipping with broken md5sums
Public bug reported: This problem is easily noticeable on oneiric if you install the debsums package and run 'debsums -s' On a server system with only very small set of packages installed, I see broken md5sums for these packages: % sudo debsums -s debsums: changed file /usr/share/doc/libaprutil1-dbd-sqlite3/changelog.Debian.gz (from libaprutil1-dbd-sqlite3 package) debsums: changed file /usr/share/doc/libaprutil1-ldap/changelog.Debian.gz (from libaprutil1-ldap package) debsums: changed file /usr/share/doc/libxcb-render0/changelog.Debian.gz (from libxcb-render0 package) debsums: changed file /usr/share/doc/libxcb-shm0/changelog.Debian.gz (from libxcb-shm0 package) debsums: changed file /usr/share/doc/perl/changelog.Debian.gz (from perl-base package) debsums: changed file /usr/share/doc/racoon/changelog.Debian.gz (from racoon package) On a desktop system you'll see a *lot* more problems. See here for example: http://ubuntuforums.org/showthread.php?t=1859706 (report from another person who noticed the same problem) Some of the wrong checksums are probably caused by including checksums for symlinked files from other packages into md5sums. Example: % ls -l /usr/share/doc/libxcb-shm0/changelog.Debian.gz lrwxrwxrwx 1 root root 30 2011-10-14 21:45 /usr/share/doc/libxcb-shm0/changelog.Debian.gz - ../libxcb1/changelog.Debian.gz % aptitude download libxcb-render0 Get: 1 http://archive.ubuntu.com/ubuntu/ oneiric/main libxcb-render0 amd64 1.7-3 [11.9 kB] Fetched 11.9 kB in 0s (146 kB/s) % dpkg -x libxcb-render0_1.7-3_amd64.deb . % dpkg -e libxcb-render0_1.7-3_amd64.deb % grep changelog.Debian.gz DEBIAN/md5sums 15276f194d3ca77e0c9682105f2f004c usr/share/doc/libxcb-render0/changelog.Debian.gz % md5sum usr/share/doc/libxcb-render0/changelog.Debian.gz md5sum: usr/share/doc/libxcb-render0/changelog.Debian.gz: No such file or directory % ls -l usr/share/doc/libxcb-render0/changelog.Debian.gz lrwxrwxrwx 1 jk jk 30 2011-06-11 01:23 usr/share/doc/libxcb-render0/changelog.Debian.gz - ../libxcb1/changelog.Debian.gz But there are also packages that actually have wrong md5sums for files included in the package. Example: % aptitude download perl-base Get: 1 http://archive.ubuntu.com/ubuntu/ oneiric/main perl-base amd64 5.12.4-4 [1,430 kB] Fetched 1,430 kB in 0s (2,440 kB/s) % dpkg -x perl-base_5.12.4-4_amd64.deb . % dpkg -e perl-base_5.12.4-4_amd64.deb % grep changelog.Debian.gz DEBIAN/md5sums b060dab6fca4e84eceacdefb619fa79b usr/share/doc/perl/changelog.Debian.gz % md5sum usr/share/doc/perl/changelog.Debian.gz ec4b1914bcbe7a3143e0b16f81b9a329 usr/share/doc/perl/changelog.Debian.gz Both of this cases should be fixed. ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875466 Title: Lots of packages shipping with broken md5sums To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/875466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 807153] Re: named does not shut down after service bind9 stop
Same problem on several machines here. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/807153 Title: named does not shut down after service bind9 stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/807153/+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 807153] Re: named does not shut down after service bind9 stop
Same problem on several machines here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/807153 Title: named does not shut down after service bind9 stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/807153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 780417] [NEW] debsums error for perl-base 5.10.1-17ubuntu4.1
Public bug reported: Binary package hint: perl debsums reports an error for /usr/share/doc/perl/changelog.Debian.gz from perl-base_5.10.1-17ubuntu4.1 on Natty: # debsums -s perl-base debsums: changed file /usr/share/doc/perl/changelog.Debian.gz (from perl-base package) # ls -l /usr/share/doc/perl/changelog.Debian.gz -rw-r--r-- 1 root root 1371 2011-04-26 18:13 /usr/share/doc/perl/changelog.Debian.gz # md5sum /usr/share/doc/perl/changelog.Debian.gz 04cd9ca187f26a69a3209503c1556238 /usr/share/doc/perl/changelog.Debian.gz # grep changelog.Debian.gz /var/lib/dpkg/info/perl-base.md5sums c7d9ccbecc91f7b90ea70f36663191c6 usr/share/doc/perl/changelog.Debian.gz apt-get install --reinstall perl-base didn't change anything. ** Affects: perl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/780417 Title: debsums error for perl-base 5.10.1-17ubuntu4.1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719388] Re: semop failed for cookie 0xd4d09ef: incorrect semaphore state during luksOpen
I'm seeing these semaphore errors with a backup-script that uses lvm2 snapshots after upgrading to natty. I think this bug should be reopened and moved to the proper package (lvm2?) and it should probably be merged with bug #753541 May 9 21:21:43 sphere udevd-work[5144]: inotify_add_watch(6, /dev/dm-25, 10) failed: No such file or directory May 9 21:21:47 sphere udevd-work[5144]: inotify_add_watch(6, /dev/dm-22, 10) failed: No such file or directory May 9 21:21:51 sphere udevd-work[5144]: inotify_add_watch(6, /dev/dm-19, 10) failed: No such file or directory May 9 21:21:54 sphere udevd-work[5144]: inotify_add_watch(6, /dev/dm-28, 10) failed: No such file or directory May 9 21:21:58 sphere udevd-work[5144]: inotify_add_watch(6, /dev/dm-31, 10) failed: No such file or directory May 9 21:22:02 sphere udevd-work[5144]: inotify_add_watch(6, /dev/dm-16, 10) failed: No such file or directory May 9 21:22:05 sphere udevd-work[5144]: inotify_add_watch(6, /dev/dm-13, 10) failed: No such file or directory semid 1179650: semop failed for cookie 0xd4d8346: incorrect semaphore state Could not signal waiting process using notification semaphore identified by cookie value 223183686 (0xd4d8346) semid 1179650: semop failed for cookie 0xd4d8346: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223183686 (0xd4d8346) to initialize waiting for incoming notifications. semid 1245186: semop failed for cookie 0xd4d7e40: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223182400 (0xd4d7e40) to initialize waiting for incoming notifications. semid 1277954: semop failed for cookie 0xd4d59e4: incorrect semaphore state Could not signal waiting process using notification semaphore identified by cookie value 223173092 (0xd4d59e4) semid 1277954: semop failed for cookie 0xd4d59e4: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223173092 (0xd4d59e4) to initialize waiting for incoming notifications. semid 1343490: semop failed for cookie 0xd4d451a: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223167770 (0xd4d451a) to initialize waiting for incoming notifications. semid 1376258: semop failed for cookie 0xd4dc3e3: incorrect semaphore state Could not signal waiting process using notification semaphore identified by cookie value 223200227 (0xd4dc3e3) semid 1376258: semop failed for cookie 0xd4dc3e3: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223200227 (0xd4dc3e3) to initialize waiting for incoming notifications. semid 1441794: semop failed for cookie 0xd4dd615: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223204885 (0xd4dd615) to initialize waiting for incoming notifications. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719388 Title: semop failed for cookie 0xd4d09ef: incorrect semaphore state during luksOpen -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 241109] Re: udev races with snaphots?
*** This bug is a duplicate of bug 483890 *** https://bugs.launchpad.net/bugs/483890 Still happens, there's more info in bug 483890. ** This bug has been marked a duplicate of bug 483890 Race conditions when creating multiple LVM2 snapshots * You can subscribe to bug 483890 by following this link: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/483890/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/241109 Title: udev races with snaphots? -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 674704] [NEW] restart udev hangs
Public bug reported:
Binary package hint: udev
On two headless servers restart udev just hangs. When the udev
package gets updated the only way to get aptitude to complete the
upgrade is to kill the 'restart udev' process from the outside.
The last thing 'strace restart udev' shows is:
ocket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC, 0) = 3
connect(3, {sa_family=AF_FILE, path=@/com/ubuntu/upstart}, 22) = 0
fcntl(3, F_GETFL) = 0x2 (flags O_RDWR)
fcntl(3, F_SETFL, O_RDWR|O_NONBLOCK)= 0
geteuid() = 0
getsockname(3, {sa_family=AF_FILE, NULL}, [2]) = 0
poll([{fd=3, events=POLLOUT}], 1, 0)= 1 ([{fd=3, revents=POLLOUT}])
write(3, \0, 1) = 1
sendto(3, AUTH EXTERNAL 30\r\n, 18, MSG_NOSIGNAL, NULL, 0) = 18
poll([{fd=3, events=POLLIN}], 1, -1)= 1 ([{fd=3, revents=POLLIN}])
read(3, OK d71fcfbb5e2671f0f0575cf80..., 2048) = 37
poll([{fd=3, events=POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
sendto(3, NEGOTIATE_UNIX_FD\r\n, 19, MSG_NOSIGNAL, NULL, 0) = 19
poll([{fd=3, events=POLLIN}], 1, -1)= 1 ([{fd=3, revents=POLLIN}])
read(3, AGREE_UNIX_FD\r\n, 2048) = 15
poll([{fd=3, events=POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
sendto(3, BEGIN\r\n, 7, MSG_NOSIGNAL, NULL, 0) = 7
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
sendmsg(3, {msg_name(0)=NULL,
msg_iov(2)=[{l\1\2\1\t\0\0\0\1\0\0\0_\0\0\0\1\1o\0\23\0\0\0/com/ubu..., 112},
{\4\0\0\0udev\0, 9}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 121
poll([{fd=3, events=POLLIN}], 1, 25000) = 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name(0)=NULL,
msg_iov(1)=[{l\2\1\1\\0\0\0\1\0\0\0\17\0\0\0\5\1u\0\1\0\0\0\10\1g\0\1o\0\0...,
2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 66
recvmsg(3, 0x7fffee846a60, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily
unavailable)
sendmsg(3, {msg_name(0)=NULL,
msg_iov(2)=[{l\1\2\1\10\0\0\0\2\0\0\0i\0\0\0\1\1o\0\35\0\0\0/com/ubu...,
128}, {\0\0\0\0\1\0\0\0, 8}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) =
136
poll([{fd=3, events=POLLIN}], 1, -1
I can only reproduce the problem on servers (with sshd, apache2, mysql, ... no
dbus). On desktop installations the restart command works fine.
I first saw the problem on lucid but it still occurs on maverick.
** Affects: udev (Ubuntu)
Importance: Undecided
Status: New
--
restart udev hangs
https://bugs.launchpad.net/bugs/674704
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665912] Re: Fix for #151231 leaves tmpfile fd open in actual job
The difference is that your example redirects both stdout and stderr while mine only redirected stdout. Anyway, your test shows the problem too: 5 - /tmp/tmpfznXN8E shouldn't be there. There's a close missing somewhere in the child. -- Fix for #151231 leaves tmpfile fd open in actual job https://bugs.launchpad.net/bugs/665912 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665912] [NEW] Fix for #151231 leaves tmpfile fd open in actual job
Public bug reported: Binary package hint: cron Maverick with cron 3.0pl1-114ubuntu1 I just upgraded a lucid machine to maverick. Now my backup cronjob spits out lots of warnings like: File descriptor 5 (/tmp/tmpflCpLg8 (deleted)) leaked on lvcreate invocation. Parent PID 7092: /bin/bash File descriptor 5 (/tmp/tmpflCpLg8 (deleted)) leaked on lvcreate invocation. Parent PID 7092: /bin/bash File descriptor 5 (/tmp/tmpflCpLg8 (deleted)) leaked on lvcreate invocation. Parent PID 7092: /bin/bash [...] File descriptor 5 (/tmp/tmpflCpLg8 (deleted)) leaked on lvremove invocation. Parent PID 7092: /bin/bash File descriptor 5 (/tmp/tmpflCpLg8 (deleted)) leaked on lvremove invocation. Parent PID 7092: /bin/bash File descriptor 5 (/tmp/tmpflCpLg8 (deleted)) leaked on lvremove invocation. Parent PID 7092: /bin/bash Thees are harmless but get sent to stderr = I now get a mail with these warnings each time the job runs. (I can't redirect stderr to /dev/null because I don't want to miss real problems). It turns out that this problem was introduced to cron with this patch: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/maverick/cron/maverick/revision/26#do_command.c (included since 3.0pl1-113ubuntu1) The patch makes cron use a tmpfile to fix bug #151231 and http://bugs.debian.org/155109 (where the patch comes from originally). The problem is that the file descriptor for this tmpfile is left open in the child which runs the actual cron job. Test case: $ crontab -l # stdout to log, stderr to mail */1 * * * * /home/jk/test.sh /tmp/stdout.log $ cat /home/jk/test.sh #!/bin/sh echo normal echo warning/error 2 echo ls -al /proc/$$/fd echo # close /tmp/... fd exec 5- ls -al /proc/$$/fd echo normal echo warning/error 2 After the job has run: --- $ cat /tmp/stdout.log normal total 0 dr-x-- 2 jk jk 0 2010-10-24 16:17 . dr-xr-xr-x 7 jk jk 0 2010-10-24 16:17 .. lr-x-- 1 jk jk 64 2010-10-24 16:17 0 - pipe:[2722425] l-wx-- 1 jk jk 64 2010-10-24 16:17 1 - /tmp/stdout.log lr-x-- 1 jk jk 64 2010-10-24 16:17 10 - /home/jk/test.sh lrwx-- 1 jk jk 64 2010-10-24 16:17 2 - /tmp/tmpflc7JPf (deleted) lrwx-- 1 jk jk 64 2010-10-24 16:17 5 - /tmp/tmpflc7JPf (deleted) total 0 dr-x-- 2 jk jk 0 2010-10-24 16:17 . dr-xr-xr-x 7 jk jk 0 2010-10-24 16:17 .. lr-x-- 1 jk jk 64 2010-10-24 16:17 0 - pipe:[2722425] l-wx-- 1 jk jk 64 2010-10-24 16:17 1 - /tmp/stdout.log lr-x-- 1 jk jk 64 2010-10-24 16:17 10 - /home/jk/test.sh lrwx-- 1 jk jk 64 2010-10-24 16:17 2 - /tmp/tmpflc7JPf (deleted) normal --- As you can see, fd 5 points to the tmpfile. It shouldn't be there! (fd 2 is ok) I'm currently using exec 5- as a work-around for my backup cronjob - but that's an ugly fix of course. ** Affects: cron (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Fix for #151231 leave fd open in actual job + Fix for #151231 leaves tmpfile fd open in actual job -- Fix for #151231 leaves tmpfile fd open in actual job https://bugs.launchpad.net/bugs/665912 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665740] [NEW] Missing dependency on dbus
Public bug reported: Binary package hint: computer-janitor computer-janitor (2.0.4-0ubuntu1) seems to depend on dbus although it doesn't specify that. On a minimal maverick installation on a server I got Cannot contact Computer Janitor dbus service; try again. # computer-janitor find Cannot contact Computer Janitor dbus service; try again. # aptitude install dbus [...] # ERROR:dbus.proxies:Introspect error on :1.2:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type=method_call, sender=:1.1 (uid=0 pid=9209 comm=/usr/bin/python) interface=org.freedesktop.DBus.Introspectable member=Introspect error name=(unset) requested_reply=0 destination=:1.2 (uid=0 pid=9211 comm=/usr/bin/python)) removable file:/etc/apache2/apache2.conf.dpkg-old removable file:/etc/apache2/envvars.dpkg-old [...] (Not sure if the introspection error justifies another bug report) ** Affects: computer-janitor (Ubuntu) Importance: Undecided Status: New -- Missing dependency on dbus https://bugs.launchpad.net/bugs/665740 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665786] [NEW] Does not ship upstream's 'helper' file
Public bug reported: Binary package hint: shorewall Maverick's shorewall 4.4.10.1-1 and shorewall6 do not ship with upstream's /usr/share/shorewall/helpers file. The consequence is that if the user sets LOAD_HELPERS_ONLY=Yes in the configuration, some essential helper modules won't be loaded (e.g. nf_conntrack_ftp, nf_nat_ftp, nf_conntrack_sip). This leads to broken and unexpected behavior. ** Affects: shorewall (Ubuntu) Importance: Undecided Status: New -- Does not ship upstream's 'helper' file https://bugs.launchpad.net/bugs/665786 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
ppa2 only changed the postinst script, so the error should have been in ppa1 too. To what does /etc/resolv.conf point and does /var/run/resolvconf exist after booting? -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
I've put a fixed build of resolvconf for maverick on https://launchpad.net/~jk/+archive/ubuntu-fixes (ppa:jk/ubuntu-fixes) The package contains the changes made by Simon Huerlimann and Sander van Grieken. Source code is available via above PPA and https://code.launchpad.net/~jk/ubuntu/maverick/resolvconf/upstart ** Branch linked: lp:~jk/ubuntu/maverick/resolvconf/upstart -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
Sander, looks like a bug inherited from the lucid package. The postinst script must run resolvconf -i instead of resolvconf --enable- updates. I'll upload a fixed package in a few minutes. (The current package should work after start resolvconf, though). -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
The new package is in ppa:jk/ubuntu-fixes now. postinst now runs resolvconf -i if the run dir doesn't exist yet. -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 652674] Re: logprof doesn't handle log messages without denied or requested masks correctly
This is a regression from lucid. I just upgraded one machine to maverick and now aa-logprof spits out thousands of warnings. Jesse's patch looks fine. -- logprof doesn't handle log messages without denied or requested masks correctly https://bugs.launchpad.net/bugs/652674 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
As Anders said, conffiles don't get deleted by default. Do 'dpkg -s resolvconf | grep /etc/init/', you should see that /etc/init/resolvconf.conf is marked as obsolete. -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 608423] Re: [lucid-proposed] post-start script broken
I agree with a7x. This is not fixed at all: Neither in lucid-proposed (a7x's points 1, 2, and 3) nor in maverick (just point 2, 3 as the new maverick package does have a 'sleep 1'). For the record, I did try the lucid-proposed package nevertheless. syslog still reports 'mysql post-start process (...) terminated with status 1'. ** Tags added: verification-failed ** Tags removed: verification-needed ** Changed in: mysql-dfsg-5.1 (Ubuntu Lucid) Status: Fix Released = In Progress ** Changed in: mysql-5.1 (Ubuntu Maverick) Status: Fix Released = In Progress -- [lucid-proposed] post-start script broken https://bugs.launchpad.net/bugs/608423 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 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 608423] Re: [lucid-proposed] post-start script broken
I agree with a7x. This is not fixed at all: Neither in lucid-proposed (a7x's points 1, 2, and 3) nor in maverick (just point 2, 3 as the new maverick package does have a 'sleep 1'). For the record, I did try the lucid-proposed package nevertheless. syslog still reports 'mysql post-start process (...) terminated with status 1'. ** Tags added: verification-failed ** Tags removed: verification-needed ** Changed in: mysql-dfsg-5.1 (Ubuntu Lucid) Status: Fix Released = In Progress ** Changed in: mysql-5.1 (Ubuntu Maverick) Status: Fix Released = In Progress -- [lucid-proposed] post-start script broken https://bugs.launchpad.net/bugs/608423 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 608423] [NEW] post-start script broken
Public bug reported: 5.1.41-3ubuntu12.4 from lucid-proposed has a broken post-start script. After starting mysql, /var/log/syslog says: init: mysql post-start process (11493) terminated with status 1 Looking at the post-start script shows two problems: 1) ret = $? Note the spaces before and after the '='. There should be none! As it is now, it tries to run a command called ret instead of setting a variable. 2) /usr/bin/mysqladmin --defaults-file=$HOME/debian.cnf ping If this returns a non-zero exit status (most likely because mysql isn't fully up yet), the post-script exits immediately! You need a set +e or something else that keeps the post-start script from exiting prematurely if the command returns with something != 0. ** Affects: mysql-dfsg-5.1 (Ubuntu) Importance: Undecided Status: New ** Tags: regression-proposed ** Tags added: regression-proposed -- post-start script broken https://bugs.launchpad.net/bugs/608423 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 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 551130] Re: [SRU] infinite loop in /etc/init/mysql.conf if mysqld is not running.
The new post-start script is broken, see bug #608423 -- [SRU] infinite loop in /etc/init/mysql.conf if mysqld is not running. https://bugs.launchpad.net/bugs/551130 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 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 608423] [NEW] post-start script broken
Public bug reported: 5.1.41-3ubuntu12.4 from lucid-proposed has a broken post-start script. After starting mysql, /var/log/syslog says: init: mysql post-start process (11493) terminated with status 1 Looking at the post-start script shows two problems: 1) ret = $? Note the spaces before and after the '='. There should be none! As it is now, it tries to run a command called ret instead of setting a variable. 2) /usr/bin/mysqladmin --defaults-file=$HOME/debian.cnf ping If this returns a non-zero exit status (most likely because mysql isn't fully up yet), the post-script exits immediately! You need a set +e or something else that keeps the post-start script from exiting prematurely if the command returns with something != 0. ** Affects: mysql-dfsg-5.1 (Ubuntu) Importance: Undecided Status: New ** Tags: regression-proposed ** Tags added: regression-proposed -- post-start script broken https://bugs.launchpad.net/bugs/608423 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551130] Re: [SRU] infinite loop in /etc/init/mysql.conf if mysqld is not running.
The new post-start script is broken, see bug #608423 -- [SRU] infinite loop in /etc/init/mysql.conf if mysqld is not running. https://bugs.launchpad.net/bugs/551130 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379701] Re: command finger outputs incorrect message
Still happens with karmic. -- command finger outputs incorrect message https://bugs.launchpad.net/bugs/379701 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379701] Re: command finger outputs incorrect message
Argh, I meant lucid. -- command finger outputs incorrect message https://bugs.launchpad.net/bugs/379701 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580674] Re: Not stoppable/restartable via initctl
** Changed in: irqbalance (Ubuntu) Status: Fix Released = In Progress -- Not stoppable/restartable via initctl https://bugs.launchpad.net/bugs/580674 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance 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 580674] Re: Not stoppable/restartable via initctl
Reopened. The patch does not completely solve the problem: The pid file doesn't get removed when irqbalance shuts down (missing capabilities?) and the next start fails because of open(...O_CREAT|O_EXCL...). # sudo start irqbalance irqbalance start/running, process 1347 # cat /var/run/irqbalance.pid ; echo 1347 # sudo stop irqbalance irqbalance stop/waiting # ps auxw | grep [i]rqbalance # cat /var/run/irqbalance.pid ; echo 1347 # sudo start irqbalance irqbalance start/spawned, process 1358 # ps auxw | grep [i]rqbalance # tail /var/log/syslog May 26 00:37:58 sphere init: irqbalance main process (1369) terminated with status 1 May 26 00:37:58 sphere init: irqbalance main process ended, respawning May 26 00:37:58 sphere init: irqbalance main process (1371) terminated with status 1 May 26 00:37:58 sphere init: irqbalance main process ended, respawning May 26 00:37:58 sphere init: irqbalance main process (1373) terminated with status 1 May 26 00:37:58 sphere init: irqbalance main process ended, respawning May 26 00:37:58 sphere init: irqbalance main process (1375) terminated with status 1 May 26 00:37:58 sphere init: irqbalance main process ended, respawning May 26 00:37:58 sphere init: irqbalance main process (1377) terminated with status 1 May 26 00:37:58 sphere init: irqbalance respawning too fast, stopped -- Not stoppable/restartable via initctl https://bugs.launchpad.net/bugs/580674 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance 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 580674] Re: Not stoppable/restartable via initctl
** Changed in: irqbalance (Ubuntu) Status: Fix Released = In Progress -- Not stoppable/restartable via initctl https://bugs.launchpad.net/bugs/580674 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580674] Re: Not stoppable/restartable via initctl
Reopened. The patch does not completely solve the problem: The pid file doesn't get removed when irqbalance shuts down (missing capabilities?) and the next start fails because of open(...O_CREAT|O_EXCL...). # sudo start irqbalance irqbalance start/running, process 1347 # cat /var/run/irqbalance.pid ; echo 1347 # sudo stop irqbalance irqbalance stop/waiting # ps auxw | grep [i]rqbalance # cat /var/run/irqbalance.pid ; echo 1347 # sudo start irqbalance irqbalance start/spawned, process 1358 # ps auxw | grep [i]rqbalance # tail /var/log/syslog May 26 00:37:58 sphere init: irqbalance main process (1369) terminated with status 1 May 26 00:37:58 sphere init: irqbalance main process ended, respawning May 26 00:37:58 sphere init: irqbalance main process (1371) terminated with status 1 May 26 00:37:58 sphere init: irqbalance main process ended, respawning May 26 00:37:58 sphere init: irqbalance main process (1373) terminated with status 1 May 26 00:37:58 sphere init: irqbalance main process ended, respawning May 26 00:37:58 sphere init: irqbalance main process (1375) terminated with status 1 May 26 00:37:58 sphere init: irqbalance main process ended, respawning May 26 00:37:58 sphere init: irqbalance main process (1377) terminated with status 1 May 26 00:37:58 sphere init: irqbalance respawning too fast, stopped -- Not stoppable/restartable via initctl https://bugs.launchpad.net/bugs/580674 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581744] [NEW] Purging should not set reset policies/chains if ufw wasn't enabled
Public bug reported: Binary package hint: ufw [ufw_0.30pre1-0ubuntu2 on lucid] ufw's postrm script does the following on purge: for exe in iptables ip6tables do if which $exe /dev/null 21; then $exe -P INPUT ACCEPT 2/dev/null || true $exe -P OUTPUT ACCEPT 2/dev/null || true $exe -P FORWARD ACCEPT 2/dev/null || true $exe -F 2/dev/null || true $exe -X 2/dev/null || true fi done That's completely unexpected if ufw wasn't in use at all and there's another firewall configured (e.g. shorewall/shorewall6). The policies and chains should only be reset if ufw actually was in use. ** Affects: ufw (Ubuntu) Importance: Undecided Status: New -- Purging should not set reset policies/chains if ufw wasn't enabled https://bugs.launchpad.net/bugs/581744 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580674] [NEW] Not stoppable/restartable via initctl
Public bug reported: Binary package hint: irqbalance [irqbalance_0.55+20091017-3ubuntu2 on lucid] irqbalance can not be stopped by upstart. 'stop irqbalance' just says 'Unknown instance'. Note the different PIDs in the log below: 'start irqbalance' says 26320, while the actual running daemon has PID 26321 # stop irqbalance stop: Unknown instance: # ps auxw | grep [i]rqbalance root 26991 0.0 0.0 11276 640 ?Ss 16:28 0:01 /usr/sbin/irqbalance # kill 26991 # ps auxw | grep [i]rqbalance # start irqbalance irqbalance start/running, process 26320 # stop irqbalance stop: Unknown instance: # ps auxw | grep [i]rqbalance root 26321 0.0 0.0 11276 640 ?Ss 21:03 0:00 /usr/sbin/irqbalance ** Affects: irqbalance (Ubuntu) Importance: Undecided Status: New -- Not stoppable/restartable via initctl https://bugs.launchpad.net/bugs/580674 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578030] [NEW] Must be started by upstart to make sure it runs before any networking daemons
Public bug reported: Binary package hint: shorewall shorewall (and shorewall6) should be started by an upstart script in lucid and later. If started from /etc/init.d, shorewall might come up too late. Somebody might have already connected to a service (and may continue communication via an ESTABLISHED rule). On lucid I see at least mysql, vsftpd, and rsyslog starting before shorewall sets up its rules. It probably would be best to use the same start-on events as ufw: ,--- | # Make sure we start before an interface receives traffic | start on (starting network-interface | or starting network-manager | or starting networking) `-- ** Affects: shorewall (Ubuntu) Importance: Undecided Status: New -- Must be started by upstart to make sure it runs before any networking daemons https://bugs.launchpad.net/bugs/578030 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577445] [NEW] apparmor doesn't confine services started by upstart
*** This bug is a security vulnerability *** Public security bug reported: Binary package hint: apparmor [lucid with apparmor 2.5-0ubuntu3] Apparently apparmor profiles get loaded too late in the boot process to confine all processes that have a profile defined. Either /etc/init.d/apparmor should be run earlier or the profiles should be loaded by upstart before all those services which start on local- filesystems get started. I'd rate this problem pretty major, if not even a security problem: It gives users a false impression of security. Some stock services that have profiles defined are unprotected after boot. Also, profiles generated by the user might look fine -- but after the next reboot the protection unexpectedly is gone again. aa-status output after boot: System 1: 2 processes are unconfined but have a profile defined. /usr/sbin/smbd (1082) /usr/sbin/smbd (882) System 2: 6 processes are unconfined but have a profile defined. /usr/sbin/mysqld (1015) /usr/sbin/nmbd (1169) /usr/sbin/nmbd (1162) /usr/sbin/rsyslogd (953) /usr/sbin/smbd (932) /usr/sbin/smbd (1045) System 3: 5 processes are unconfined but have a profile defined. /usr/sbin/mysqld (1193) /usr/sbin/rsyslogd (1164) /usr/sbin/vsftpd (1163) /usr/sbin/vsftpd (1161) /usr/sbin/vsftpd (1162) Manual fix: restart those services after each boot ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Visibility changed to: Public -- apparmor doesn't confine services started by upstart https://bugs.launchpad.net/bugs/577445 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots
Yep, no more messages about symlinks with lucid. I still do see some kind of race condition with lucid, though: May 8 16:24:53 sphere udevd-work[24973]: inotify_add_watch(6, /dev/dm-23, 10) failed: No such file or directory May 8 16:25:04 sphere udevd-work[24973]: inotify_add_watch(6, /dev/dm-32, 10) failed: No such file or directory From the timestamps I'd say this happened while the snapshot made for backup were unmounted and lvremoved. -- Race conditions when creating multiple LVM2 snapshots https://bugs.launchpad.net/bugs/483890 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577165] [NEW] Typo in etc/init/vsftpd.conf
Public bug reported: Binary package hint: vsftpd [ -d /var/run/vsftpd/emply ] || install -m 755 -o root -g root -d /var/run/vsftpd/empty Obviously emply is not the same as empty. ** Affects: vsftpd (Ubuntu) Importance: Undecided Status: New -- Typo in etc/init/vsftpd.conf https://bugs.launchpad.net/bugs/577165 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd 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 577165] Re: Typo in etc/init/vsftpd.conf
** Patch added: vsftpd-upstart.patch http://launchpadlibrarian.net/48017782/vsftpd-upstart.patch -- Typo in etc/init/vsftpd.conf https://bugs.launchpad.net/bugs/577165 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd 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 577165] [NEW] Typo in etc/init/vsftpd.conf
Public bug reported: Binary package hint: vsftpd [ -d /var/run/vsftpd/emply ] || install -m 755 -o root -g root -d /var/run/vsftpd/empty Obviously emply is not the same as empty. ** Affects: vsftpd (Ubuntu) Importance: Undecided Status: New -- Typo in etc/init/vsftpd.conf https://bugs.launchpad.net/bugs/577165 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577165] Re: Typo in etc/init/vsftpd.conf
** Patch added: vsftpd-upstart.patch http://launchpadlibrarian.net/48017782/vsftpd-upstart.patch -- Typo in etc/init/vsftpd.conf https://bugs.launchpad.net/bugs/577165 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
resolvconf (1.45ubuntu1ppa5) karmic; urgency=low
* Use /var/run in resolvonf binary.
-- Simon Huerlimann (CyT) simon.huerlim...@cyt.ch Mon, 03 May 2010
00:27:16 +0200
Why RUN_DIR=${RESOLVCONF_RUNDIR:=/var/run}? Didn't you mean
/var/run/resolvconf?
That's what your postinst and apparmor use.
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots
Good catch, will give it a try. Of course, /lib/udev/rules.d/65-dmsetup.rules isn't a conffile, so changes to it will be lost when the dmsetup package gets upgraded. (Also, this symlink rule isn't in lucid. On the other hand I didn't upgrade any of the machines showing this problem to lucid yet, maybe it's fixed there anyway.) -- Race conditions when creating multiple LVM2 snapshots https://bugs.launchpad.net/bugs/483890 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 573657] [NEW] irqbalance enabled unconditionally, can't be disabled via debconf
Public bug reported: Binary package hint: irqbalance [using 0.55+20091017-3ubuntu2 on lucid] irqbalance gets enabled unconditionally upon installation. The user's answer to the question whether it should be enabled (upon installation or dpkg-reconfigure) gets ignored: ,--- | $ cat /etc/default/irqbalance | #Configuration for the irqbalance daemon | | #Should irqbalance be enabled? | ENABLED=1 | #Balance the IRQs only once? | ONESHOT=0 | $ sudo dpkg-reconfigure -ftext irqbalance | stop: Unknown instance: | Configuring irqbalance | -- | | Enable the irqbalance daemon to balance IRQs on SMP systems and systems with | hyperthreading. | | Would you like to enable irqbalance? n | | | irqbalance can run in one shot mode, where the IRQs are balanced only once. This | is advantageous on hyperthreading systems such as the Pentium 4, which appear to | be SMP systems, but are really one physical CPU. | | Would you like to balance the IRQs once? y | | | irqbalance start/running, process 1496 | $ cat /etc/default/irqbalance | #Configuration for the irqbalance daemon | | #Should irqbalance be enabled? | ENABLED=1 | #Balance the IRQs only once? | ONESHOT=1 `--- = dpkg-reconfigure managed to change the ONESHOT setting but not the ENABLED setting. The problem is caused by a confusion over where to use ENABLED and where ENABLE. I'm attaching a trivial patch which fixes the problem. ** Affects: irqbalance (Ubuntu) Importance: Undecided Status: New -- irqbalance enabled unconditionally, can't be disabled via debconf https://bugs.launchpad.net/bugs/573657 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance 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 573657] Re: irqbalance enabled unconditionally, can't be disabled via debconf
** Patch added: irqbalance.patch http://launchpadlibrarian.net/47256629/irqbalance.patch ** Description changed: Binary package hint: irqbalance [using 0.55+20091017-3ubuntu2 on lucid] irqbalance gets enabled unconditionally upon installation. The user's answer to the question whether it should be enabled (upon installation or dpkg-reconfigure) gets ignored: ,--- - | $ cat /etc/default/irqbalance + | $ cat /etc/default/irqbalance | #Configuration for the irqbalance daemon - | + | | #Should irqbalance be enabled? | ENABLED=1 | #Balance the IRQs only once? | ONESHOT=0 | $ sudo dpkg-reconfigure -ftext irqbalance - | stop: Unknown instance: + | stop: Unknown instance: | Configuring irqbalance | -- - | - | Enable the irqbalance daemon to balance IRQs on SMP systems and systems with + | + | Enable the irqbalance daemon to balance IRQs on SMP systems and systems with | hyperthreading. - | + | | Would you like to enable irqbalance? n - | - | + | + | | irqbalance can run in one shot mode, where the IRQs are balanced only once. This | is advantageous on hyperthreading systems such as the Pentium 4, which appear to | be SMP systems, but are really one physical CPU. - | + | | Would you like to balance the IRQs once? y - | - | + | + | | irqbalance start/running, process 1496 - | $ cat /etc/default/irqbalance + | $ cat /etc/default/irqbalance | #Configuration for the irqbalance daemon - | + | | #Should irqbalance be enabled? | ENABLED=1 | #Balance the IRQs only once? | ONESHOT=1 `--- - = dpkg-reconfigure managed to changed the ONESHOT setting but not the + = dpkg-reconfigure managed to change the ONESHOT setting but not the ENABLED setting. The problem is caused by a confusion over where to use ENABLED and where ENABLE. I'm attaching a trivial patch which fixes the problem. -- irqbalance enabled unconditionally, can't be disabled via debconf https://bugs.launchpad.net/bugs/573657 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance 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 573657] [NEW] irqbalance enabled unconditionally, can't be disabled via debconf
Public bug reported: Binary package hint: irqbalance [using 0.55+20091017-3ubuntu2 on lucid] irqbalance gets enabled unconditionally upon installation. The user's answer to the question whether it should be enabled (upon installation or dpkg-reconfigure) gets ignored: ,--- | $ cat /etc/default/irqbalance | #Configuration for the irqbalance daemon | | #Should irqbalance be enabled? | ENABLED=1 | #Balance the IRQs only once? | ONESHOT=0 | $ sudo dpkg-reconfigure -ftext irqbalance | stop: Unknown instance: | Configuring irqbalance | -- | | Enable the irqbalance daemon to balance IRQs on SMP systems and systems with | hyperthreading. | | Would you like to enable irqbalance? n | | | irqbalance can run in one shot mode, where the IRQs are balanced only once. This | is advantageous on hyperthreading systems such as the Pentium 4, which appear to | be SMP systems, but are really one physical CPU. | | Would you like to balance the IRQs once? y | | | irqbalance start/running, process 1496 | $ cat /etc/default/irqbalance | #Configuration for the irqbalance daemon | | #Should irqbalance be enabled? | ENABLED=1 | #Balance the IRQs only once? | ONESHOT=1 `--- = dpkg-reconfigure managed to change the ONESHOT setting but not the ENABLED setting. The problem is caused by a confusion over where to use ENABLED and where ENABLE. I'm attaching a trivial patch which fixes the problem. ** Affects: irqbalance (Ubuntu) Importance: Undecided Status: New -- irqbalance enabled unconditionally, can't be disabled via debconf https://bugs.launchpad.net/bugs/573657 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 573657] Re: irqbalance enabled unconditionally, can't be disabled via debconf
** Patch added: irqbalance.patch http://launchpadlibrarian.net/47256629/irqbalance.patch ** Description changed: Binary package hint: irqbalance [using 0.55+20091017-3ubuntu2 on lucid] irqbalance gets enabled unconditionally upon installation. The user's answer to the question whether it should be enabled (upon installation or dpkg-reconfigure) gets ignored: ,--- - | $ cat /etc/default/irqbalance + | $ cat /etc/default/irqbalance | #Configuration for the irqbalance daemon - | + | | #Should irqbalance be enabled? | ENABLED=1 | #Balance the IRQs only once? | ONESHOT=0 | $ sudo dpkg-reconfigure -ftext irqbalance - | stop: Unknown instance: + | stop: Unknown instance: | Configuring irqbalance | -- - | - | Enable the irqbalance daemon to balance IRQs on SMP systems and systems with + | + | Enable the irqbalance daemon to balance IRQs on SMP systems and systems with | hyperthreading. - | + | | Would you like to enable irqbalance? n - | - | + | + | | irqbalance can run in one shot mode, where the IRQs are balanced only once. This | is advantageous on hyperthreading systems such as the Pentium 4, which appear to | be SMP systems, but are really one physical CPU. - | + | | Would you like to balance the IRQs once? y - | - | + | + | | irqbalance start/running, process 1496 - | $ cat /etc/default/irqbalance + | $ cat /etc/default/irqbalance | #Configuration for the irqbalance daemon - | + | | #Should irqbalance be enabled? | ENABLED=1 | #Balance the IRQs only once? | ONESHOT=1 `--- - = dpkg-reconfigure managed to changed the ONESHOT setting but not the + = dpkg-reconfigure managed to change the ONESHOT setting but not the ENABLED setting. The problem is caused by a confusion over where to use ENABLED and where ENABLE. I'm attaching a trivial patch which fixes the problem. -- irqbalance enabled unconditionally, can't be disabled via debconf https://bugs.launchpad.net/bugs/573657 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574042] [NEW] Files in /etc should be conffiles
Public bug reported: Binary package hint: ifupdown None of the files installed under /etc are marked as configuration files. User customizations to those files get overwritten without warning when ifupdown is updated. , | $ dpkg -L ifupdown | grep /etc | /etc | /etc/network | /etc/network/if-pre-up.d | /etc/network/if-up.d | /etc/network/if-up.d/upstart | /etc/network/if-down.d | /etc/network/if-down.d/upstart | /etc/network/if-post-down.d | /etc/init.d | /etc/init | /etc/init/network-interface-security.conf | /etc/init/network-interface.conf | /etc/init/networking.conf | /etc/init.d/network-interface-security | /etc/init.d/network-interface | $ dpkg -s ifupdown | Package: ifupdown | Status: install ok installed | Priority: important | Section: admin | Installed-Size: 272 | Maintainer: Ubuntu Core Developers ubuntu-devel-disc...@lists.ubuntu.com | Architecture: i386 | Version: 0.6.8ubuntu29 | Replaces: netbase ( 4.00) | Depends: net-tools, libc6 (= 2.7), debconf (= 1.2.0) | debconf-2.0, upstart-job, lsb-base (= 1.3-9ubuntu3), netbase (= 4.30ubuntu2) | Suggests: iproute, dhcp3-client | dhcp-client, ppp | Breaks: udev ( 136-1) | Description: high level tools to configure network interfaces | This package provides the tools ifup and ifdown which may be used to | configure (or, respectively, deconfigure) network interfaces based on | interface definitions in the file /etc/network/interfaces. | Original-Maintainer: Anthony Towns a...@debian.org ` See also http://www.debian.org/doc/debian-policy/ch-files.html#s-config- files ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New -- Files in /etc should be conffiles https://bugs.launchpad.net/bugs/574042 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569431] [NEW] lucid: multicast RA starvation
Public bug reported: Binary package hint: radvd After upgrading an IPv6 router from karmic to lucid-rc, all hosts (several Linux and OS X boxes) on the internal net lose external IPv6 connectivity after 30 minutes. A little debugging with radvdump dump showed that radvd stops sending multicasts router advertisements after the first few packages = clients lose there default route after the AdvDefaultLifetime setting (default 1800 seconds). Apparently this is a known bug (http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=553696) that for some reason didn't show up with karmic but does with lucid (the radvd package is the same in both distributions currently). I've built Debian's radvd 1.6 package for lucid now (see https://launchpad.net/~jk/+archive/ppa?field.series_filter=lucid). Everything works fine with this version: radvdump shows no signs of RA starvation and clients keep there external IPv6 connectivity. As this problem potentially will affect a lot of people using IPv6, I'd suggest updating radvd to 1.6 for the final lucid release. ** Affects: radvd (Ubuntu) Importance: Undecided Status: New ** Affects: radvd (Debian) Importance: Unknown Status: Unknown ** Tags: regression-potential ** Bug watch added: Debian Bug tracker #553696 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553696 ** Also affects: radvd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553696 Importance: Unknown Status: Unknown ** Tags added: regression-potential -- lucid: multicast RA starvation https://bugs.launchpad.net/bugs/569431 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots
** This bug is no longer a duplicate of bug 444563 rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link -- Race conditions when creating multiple LVM2 snapshots https://bugs.launchpad.net/bugs/483890 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots
Removed the duplicate mark as I'm and others (see https://bugs.launchpad.net/ubuntu/+source/udev/+bug/444563/comments/32 for example) are pretty sure it's a different thing. -- Race conditions when creating multiple LVM2 snapshots https://bugs.launchpad.net/bugs/483890 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 444563] Re: rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link
Has anyone tested whether this is fixed in Lucid? It would be a shame to make an LTS release with this bug. It's slightly frightening to see /var/log/syslog filled by more than 50% by these messages on servers that use snapshots for backups (I have that on some Karmic machines). It might be a harmless race condition but it should be fixed. -- rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link https://bugs.launchpad.net/bugs/444563 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485562] Re: Data loss on ext3, maybe related to data=journal
dmesg2.txt is obviously with a different kernel (the bug report was filed 4 months ago). I can't tell whether the problem still occurs with this kernel, the machine is in production and I won't experiment on it. ** Attachment added: dmesg2.txt http://launchpadlibrarian.net/41626730/dmesg2.txt -- Data loss on ext3, maybe related to data=journal https://bugs.launchpad.net/bugs/485562 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
resolvconf actually should already use /lib/init/rw/resolvconf with /etc/resolvconf/run being a symlink to it. (At least for new installations, for upgraded systems I had to fix this manually). -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 498358] [NEW] bogus curl_setopt(): CURLPROTO_FILE cannot be activated when in safe_mode or an open_basedir is set errors
Public bug reported: Binary package hint: php5 Since yesterday I'm getting lots of bogus error messages from curl_setopt($ch, CURLOPT_CONNECTTIMEOUT_MS, $value) and curl_setopt($ch, CURLOPT_TIMEOUT_MS, $value) on my WordPress blog using php5-curl 5.2.10.dfsg.1-2ubuntu6.3: curl_setopt(): CURLPROTO_FILE cannot be activated when in safe_mode or an open_basedir is set in [...] The problem is described here: http://bugs.php.net/bug.php?id=49531 Apparently it's fixed 5.2.12, here's the patch: http://svn.php.net/viewvc/php/php-src/branches/PHP_5_2/ext/curl/interface.c?r1=287784r2=288598view=patch ** Affects: php5 (Ubuntu) Importance: Undecided Status: New -- bogus curl_setopt(): CURLPROTO_FILE cannot be activated when in safe_mode or an open_basedir is set errors https://bugs.launchpad.net/bugs/498358 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 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 498358] [NEW] bogus curl_setopt(): CURLPROTO_FILE cannot be activated when in safe_mode or an open_basedir is set errors
Public bug reported: Binary package hint: php5 Since yesterday I'm getting lots of bogus error messages from curl_setopt($ch, CURLOPT_CONNECTTIMEOUT_MS, $value) and curl_setopt($ch, CURLOPT_TIMEOUT_MS, $value) on my WordPress blog using php5-curl 5.2.10.dfsg.1-2ubuntu6.3: curl_setopt(): CURLPROTO_FILE cannot be activated when in safe_mode or an open_basedir is set in [...] The problem is described here: http://bugs.php.net/bug.php?id=49531 Apparently it's fixed 5.2.12, here's the patch: http://svn.php.net/viewvc/php/php-src/branches/PHP_5_2/ext/curl/interface.c?r1=287784r2=288598view=patch ** Affects: php5 (Ubuntu) Importance: Undecided Status: New -- bogus curl_setopt(): CURLPROTO_FILE cannot be activated when in safe_mode or an open_basedir is set errors https://bugs.launchpad.net/bugs/498358 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 495707] [NEW] No support for NFLOG -- Please upgrade to ulogd2
Public bug reported: Binary package hint: ulogd ULOG has been declared obsolete in the kernel and it actually has been removed from the IPv6 netfilter code already. The replacement is NFLOG. ulogd-1.* only supports ULOG which makes it quite useless for people with IPv6 firewalls. Please upgrade to ulogd-2.* which also supports NFLOG. http://www.netfilter.org/projects/ulogd/index.html https://git.netfilter.org/cgi-bin/gitweb.cgi?p=ulogd2.git;a=summary ** Affects: ulogd (Ubuntu) Importance: Undecided Status: New -- No support for NFLOG -- Please upgrade to ulogd2 https://bugs.launchpad.net/bugs/495707 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 493801] [NEW] Typo in restart command
Public bug reported: Binary package hint: radvd There's an 'i' missing in /etc/init.d/radvd's restart command: # /etc/init.d/radvd restart Stopping radvd: radvd. /etc/init.d/radvd: 98: nvoke-rc.d: not found # dpkg -l radvd [...] ii radvd1:1.2-1 Router Advertisement Daemon ** Affects: radvd (Ubuntu) Importance: Undecided Status: New -- Typo in restart command https://bugs.launchpad.net/bugs/493801 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 444563] Re: rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link
While doing snapshots for backups I also this occasionally among the other errors: upstart-udev-bridge[25372]: Disconnected from Upstart upstart-udev-bridge main process (25372) terminated with status 1 upstart-udev-bridge main process ended, respawning -- rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link https://bugs.launchpad.net/bugs/444563 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 483890] Re: Race conditions when creating multiple LVM2 snapshots
*** This bug is a duplicate of bug 444563 *** https://bugs.launchpad.net/bugs/444563 I'm not entirely convinced that is a duplicate too. Additionally to the messages already reported I also see upstart-udev-bridge restarting while creating the snapshots from time to time: upstart-udev-bridge[25372]: Disconnected from Upstart init: upstart-udev-bridge main process (25372) terminated with status 1 init: upstart-udev-bridge main process ended, respawning -- Race conditions when creating multiple LVM2 snapshots https://bugs.launchpad.net/bugs/483890 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 483897] Re: Wrong STACK check with custom colors
Here's a simple test plug-in. It just builds a stack from 3 constant values. With the attached version, you'll get errors in /var/log/munin /munin-graph.log: [...] ERROR: First field (f2) of graph [...] b483897 is STACK. STACK can only be drawn after a LINEx or AREA. [...] ERROR: First field (f3) of graph [...] b483897 is STACK. STACK can only be drawn after a LINEx or AREA. If you remove the 3 colour lines from the script (i.e., if you let munin choose the colors itself) the errors go away. As said in the original report, the logic behind the STACK–LINEx/AREA test is broken if fields have custom colors. ** Attachment added: b483897 http://launchpadlibrarian.net/35978243/b483897 -- Wrong STACK check with custom colors https://bugs.launchpad.net/bugs/483897 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin 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 483897] Re: Wrong STACK check with custom colors
Here's a simple test plug-in. It just builds a stack from 3 constant values. With the attached version, you'll get errors in /var/log/munin /munin-graph.log: [...] ERROR: First field (f2) of graph [...] b483897 is STACK. STACK can only be drawn after a LINEx or AREA. [...] ERROR: First field (f3) of graph [...] b483897 is STACK. STACK can only be drawn after a LINEx or AREA. If you remove the 3 colour lines from the script (i.e., if you let munin choose the colors itself) the errors go away. As said in the original report, the logic behind the STACK–LINEx/AREA test is broken if fields have custom colors. ** Attachment added: b483897 http://launchpadlibrarian.net/35978243/b483897 -- Wrong STACK check with custom colors https://bugs.launchpad.net/bugs/483897 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 486127] [NEW] Not preempt-safe
Public bug reported: Binary package hint: apparmor ii apparmor 2.3.1+1403-0ubuntu27.2 User-space parser utility for AppArmor ii linux-source 2.6.31.15.28 Linux kernel source with Ubuntu patches Apparmor in 2.6.31.15.28 (and earlier karmic kernels) apparently is not safe for use with CONFIG_PREEMPT. Kernels with CONFIG_PREEMPT_VOLUNTARY seem to be OK. With CONFIG_PREEMPT I get scheduling while atomic. Sometimes with a non-fatal oops, sometime with a hard crash. Happens both on i386 and x86-64, both with unicore and multicore machines. Example from a single-core i386 machine: [ 49.647818] BUG: scheduling while atomic: named/3964/0x0002 [ 49.648030] Pid: 3964, comm: named Not tainted 2.6.31.4 #1Oct 30 03:29:42 server kernel: [ 49.648030] Call Trace:Oct 30 03:29:42 server kernel: [ 49.648030] [c123f255] ? schedule+0x435/0x4d0 [ 49.648030] [c103f55a] ? commit_creds+0xda/0x160 [ 49.648030] [c100301a] ? work_resched+0x5/0x1a [ 49.648585] __ratelimit: 9 callbacks suppressed [ 49.648599] named[3964]: segfault at 402480 ip 00402480 sp bfb308ac error 4 [ 49.648631] note: named[3964] exited with preempt_count 1 [ 365.576949] BUG: scheduling while atomic: named/5101/0x0003 [ 365.577033] Pid: 5101, comm: named Not tainted 2.6.31.4 #1 [ 365.577033] Call Trace: [ 365.577033] [c123f255] ? schedule+0x435/0x4d0 [ 365.577033] [c103f55a] ? commit_creds+0xda/0x160 [ 365.577033] [c100301a] ? work_resched+0x5/0x1a [ 365.577713] named[5101]: segfault at 3f4480 ip 003f4480 sp bf84877c error 4 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- Not preempt-safe https://bugs.launchpad.net/bugs/486127 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485562] [NEW] Data loss on ext3, maybe related to data=journal
Public bug reported: I'm currently testing a backup scheme on a new karmic installation. The procedure worked flawlessly on jaunty and older Ubuntu/Debian distributions (albeit using hardware RAID on those, the new machine uses a software RAID). With karmic however I'm experiencing data loss (at least on the designated backup partition). The partition in question gets mounted once per hour. The respective entry in /etc/fstab is UUID=7420cd8f-dd47-4fdb-b64e-4fd02f945e43 /srv/backup ext3 noatime,nodiratime,user_xattr,acl,noauto,nodev,nosuid,data=journal 0 2 The partition is an LVM2 logical volume which runs on a single PV on a RAID 1 composed of 2 disks (driver is AHCI). I noticed the data loss because I use sitecopy to push the backups to another machine after each backup run. On about 1 out of 3 backup runs sitecopy complains about a corrupted state file. I didn't check the backups for the integrity yet as I can reproduce the problem with sitecopy alone easily. To reproduce it I do: # cd /srv/backup/backup2l/scripts/ # cp data.1001.all.tar.gpg # change something so sitecopy has something to push # sitecopy -r /srv/backup/backup2l/scripts/.sitecopyrc -p /srv/backup/backup2l/scripts/.sitecopy -q -u backup # cd / # umount /srv/backup # mount /srv/backup # less /srv/backup/backup2l/scripts/.sitecopy/backup In about one out of three runs, the last step step shows a corrupted file: Old contents + rest filled with zeros or a truncated file. dmesg and syslog show nothing. In particular no journal-replay related message. Adding a fsck.ext3 -f /dev/vg0/srv_backup before mounting shows no problem either, still the file gets corrupted every now and then. So far I've discovered two ways to work around the problem: * Don't use data=journal. Both data=writeback and data=ordered seem to work fine * Do less /srv/backup/backup2l/scripts/.sitecopy/backup before the unmount Especially the latter seems to suggest a strange flush problem with the data=journal code in karmic's current x86-64 kernel (2.6.31.15.28). # sudo lvdisplay /dev/vg0/srv_backup --- Logical volume --- LV Name/dev/vg0/srv_backup VG Namevg0 LV UUIDKXZqxv-v8MQ-UD4x-41Vf-2c2t-0wsr-etUNjQ LV Write Accessread/write LV Status available # open 0 LV Size128.00 GB Current LE 32768 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:12 # sudo pvdisplay --- Physical volume --- PV Name /dev/md2 VG Name vg0 PV Size 693.63 GB / not usable 4.12 MB Allocatable yes PE Size (KByte) 4096 Total PE 177567 Free PE 64927 Allocated PE 112640 PV UUID FHAWPv-otHj-jpDD-x35T-nE0Q-13uB-30GuSt # cat /proc/mdstat Personalities : [raid1] md2 : active raid1 sda3[0] sdb3[1] 727318656 blocks [2/2] [UU] md1 : active raid1 sda2[0] sdb2[1] 1052160 blocks [2/2] [UU] md0 : active raid1 sda1[0] sdb1[1] 4192896 blocks [2/2] [UU] unused devices: none ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Data loss on ext3, maybe related to data=journal https://bugs.launchpad.net/bugs/485562 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485562] Re: Data loss on ext3, maybe related to data=journal
** Attachment added: dmesg.txt http://launchpadlibrarian.net/35866621/dmesg.txt -- Data loss on ext3, maybe related to data=journal https://bugs.launchpad.net/bugs/485562 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485562] Re: Data loss on ext3, maybe related to data=journal
** Attachment added: lspci.txt http://launchpadlibrarian.net/35866626/lspci.txt -- Data loss on ext3, maybe related to data=journal https://bugs.launchpad.net/bugs/485562 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485562] Re: Data loss on ext3, maybe related to data=journal
** Attachment added: cpuinfo.txt http://launchpadlibrarian.net/35866630/cpuinfo.txt -- Data loss on ext3, maybe related to data=journal https://bugs.launchpad.net/bugs/485562 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 444563] Re: rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link
(Coming from bug 483890) I only see this happening when creating/removing snapshots for backup not while booting. In addition to rename(/dev//.udev-tmp, /dev//) failed... I also get rmdir(/dev/) failed: Device or resource busy and some error messages when creating the snapshots: Path /dev/DEVTYPE=_disk_ no longer valid for device(253,18) Path /dev/PWD=_/_ no longer valid for device(253,18) Path /dev/DM_STATE_ACTIVE=_1_ no longer valid for device(253,18) Path /dev/SUBSYSTEM=_block_ no longer valid for device(253,18) Path /dev/DM_TABLE_LIVE=_1_ no longer valid for device(253,18) Path /dev/IFS=_ no longer valid for device(253,18) Path /dev/DM_TARGET_COUNT=_1_ no longer valid for device(253,18) Path /dev/UDEV_LOG=_3_ no longer valid for device(253,18) Path /dev/PS1=_# no longer valid for device(253,18) Path /dev/_ no longer valid for device(253,18) Path /dev/PS2=__ no longer valid for device(253,18) Path /dev/DM_TARGET_TYPES=_linear_ no longer valid for device(253,18) Path /dev/DM_STATE=_ACTIVE_ no longer valid for device(253,18) Path /dev/PATH=_/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin_ no longer valid for device(253,18) Path /dev/PS4=_+ no longer valid for device(253,18) Path /dev/OPTIND=_1_ no longer valid for device(253,18) Path /dev/DM_LAST_EVENT_NR=_0_ no longer valid for device(253,18) Path /dev/DM_MAJOR=_253_ no longer valid for device(253,18) Path /dev/MAJOR=_253_ no longer valid for device(253,18) I can get rid of those by pausing a few seconds between creating the individual snapshots. This just leaves the rename/rmdir entries in syslog then. The snapshots seems to work fine but I'm not 100% sure if I really should trust the system. -- rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link https://bugs.launchpad.net/bugs/444563 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 483897] [NEW] Wrong STACK check with custom colors
Public bug reported: Binary package hint: munin When building a STACK with fields that specify a custom color munin- graph erroneously gives this (non-fatal) error: ERROR: First field (\$field\) of graph \$domain\ :: \$name\ :: \$service\ is STACK. STACK can only be drawn after a LINEx or AREA. The problem is that $field_count doesn't get incremented when a field specifies a custom color. An example that shows the problem is http://muninexchange.projects.linpro.no/?search=cid=0pid=274 ** Affects: munin (Ubuntu) Importance: Undecided Status: New -- Wrong STACK check with custom colors https://bugs.launchpad.net/bugs/483897 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin 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 483897] Re: Wrong STACK check with custom colors
1.2.6-13ubuntu3 on karmic. -- Wrong STACK check with custom colors https://bugs.launchpad.net/bugs/483897 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin 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 483890] Re: Race conditions when creating multiple LVM2 snapshots
** Attachment added: btest.sh http://launchpadlibrarian.net/35763242/btest.sh ** Also affects: udev (Ubuntu) Importance: Undecided Status: New -- Race conditions when creating multiple LVM2 snapshots https://bugs.launchpad.net/bugs/483890 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 483890] [NEW] Race conditions when creating multiple LVM2 snapshots
Public bug reported: Binary package hint: lvm2 I'm creating several LVM2 snapshots in quick succession for backup. The attached bash script shows what is done. If I run the script like it is I *always* get error messages on console and in syslog, presumably all coming from udev. The snapshots seem to work fine but I'm a bit uneasy about this. If I add sync; sleep 2; statements between the snapshot commands it gets a bit better, the error messages only show up sporadically then. The system is an update-to-date x86-64 Karmic installation. Here are the error messages from two runs of the test script + entries in syslog: # ./btest.sh pre-backup: creating and mounting snapshots Logical volume backup_root created Logical volume backup_usr created Path /dev/ACTION=_change_ no longer valid for device(253,15) Logical volume backup_home created Path /dev/ACTION=_add_ no longer valid for device(253,21) Path /dev/DEVTYPE=_disk_ no longer valid for device(253,21) Path /dev/PWD=_/_ no longer valid for device(253,21) Path /dev/DM_STATE_ACTIVE=_1_ no longer valid for device(253,21) Path /dev/SUBSYSTEM=_block_ no longer valid for device(253,21) Path /dev/DM_TABLE_LIVE=_1_ no longer valid for device(253,21) Path /dev/IFS=_ no longer valid for device(253,21) Path /dev/DM_TARGET_COUNT=_1_ no longer valid for device(253,21) Path /dev/UDEV_LOG=_3_ no longer valid for device(253,21) Path /dev/_ no longer valid for device(253,21) Logical volume backup_var_log created Path /dev/ACTION=_change_ no longer valid for device(253,20) Path /dev/ACTION=_add_ no longer valid for device(253,24) Logical volume backup_var_spool created Logical volume backup_srv_www created MySQL: flush tables with read lock Logical volume backup_srv_mysql created MySQL: unlock tables pre-backup: snapshots mounted pre-backup: copying svn repos post-backup: unmounting and removing snapshots /dev/ACTION=_add_: stat failed: No such file or directory Path /dev/ACTION=_add_ no longer valid for device(253,33) Path /dev/DEVTYPE=_disk_ no longer valid for device(253,33) Path /dev/PWD=_/_ no longer valid for device(253,33) Path /dev/DM_STATE_ACTIVE=_1_ no longer valid for device(253,33) Logical volume backup_var_spool successfully removed Logical volume backup_var_log successfully removed Logical volume backup_home successfully removed Logical volume backup_srv_www successfully removed Logical volume backup_srv_mysql successfully removed Logical volume backup_usr successfully removed Logical volume backup_root successfully removed post-backup: snapshots removed # ./btest.sh pre-backup: creating and mounting snapshots Logical volume backup_root created Logical volume backup_usr created Path /dev/DEVTYPE=_disk_ no longer valid for device(253,18) Path /dev/PWD=_/_ no longer valid for device(253,18) Path /dev/DM_STATE_ACTIVE=_1_ no longer valid for device(253,18) Path /dev/SUBSYSTEM=_block_ no longer valid for device(253,18) Path /dev/DM_TABLE_LIVE=_1_ no longer valid for device(253,18) Path /dev/IFS=_ no longer valid for device(253,18) Path /dev/DM_TARGET_COUNT=_1_ no longer valid for device(253,18) Path /dev/UDEV_LOG=_3_ no longer valid for device(253,18) Path /dev/PS1=_# no longer valid for device(253,18) Path /dev/_ no longer valid for device(253,18) Path /dev/PS2=__ no longer valid for device(253,18) Path /dev/DM_TARGET_TYPES=_linear_ no longer valid for device(253,18) Path /dev/DM_STATE=_ACTIVE_ no longer valid for device(253,18) Path /dev/PATH=_/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin_ no longer valid for device(253,18) Path /dev/PS4=_+ no longer valid for device(253,18) Path /dev/OPTIND=_1_ no longer valid for device(253,18) Path /dev/DM_LAST_EVENT_NR=_0_ no longer valid for device(253,18) Path /dev/DM_MAJOR=_253_ no longer valid for device(253,18) Path /dev/MAJOR=_253_ no longer valid for device(253,18) Logical volume backup_home created Logical volume backup_var_log created Logical volume backup_var_spool created Logical volume backup_srv_www created MySQL: flush tables with read lock Logical volume backup_srv_mysql created MySQL: unlock tables pre-backup: snapshots mounted pre-backup: copying svn repos post-backup: unmounting and removing snapshots Logical volume backup_var_spool successfully removed Logical volume backup_var_log successfully removed Logical volume backup_home successfully removed Logical volume backup_srv_www successfully removed Logical volume backup_srv_mysql successfully removed Logical volume backup_usr successfully removed Logical volume backup_root successfully removed post-backup: snapshots removed /var/log/syslog: Nov 17 00:00:39 sphere udevd-work[15754]: rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link Nov 17 00:00:40 sphere udevd-work[15096]: rename(/dev//.udev-tmp, /dev//) failed: Invalid cross-device link Nov 17 00:00:42
[Bug 483897] [NEW] Wrong STACK check with custom colors
Public bug reported: Binary package hint: munin When building a STACK with fields that specify a custom color munin- graph erroneously gives this (non-fatal) error: ERROR: First field (\$field\) of graph \$domain\ :: \$name\ :: \$service\ is STACK. STACK can only be drawn after a LINEx or AREA. The problem is that $field_count doesn't get incremented when a field specifies a custom color. An example that shows the problem is http://muninexchange.projects.linpro.no/?search=cid=0pid=274 ** Affects: munin (Ubuntu) Importance: Undecided Status: New -- Wrong STACK check with custom colors https://bugs.launchpad.net/bugs/483897 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 483897] Re: Wrong STACK check with custom colors
1.2.6-13ubuntu3 on karmic. -- Wrong STACK check with custom colors https://bugs.launchpad.net/bugs/483897 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 482629] [NEW] Can't write its pid file
Public bug reported: Binary package hint: uptimed uptimed can't write its pid file (/var/run/uptimed) because user daemon has no write permissions in /var/run. ** Affects: uptimed (Ubuntu) Importance: Undecided Status: New -- Can't write its pid file https://bugs.launchpad.net/bugs/482629 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 172465] Re: Can't create initramfs for module-less kernel
Still happens on Jaunty. -- Can't create initramfs for module-less kernel https://bugs.launchpad.net/bugs/172465 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 313642] Re: [needs packaging] miniupnpd
@komputes: No, miniupnpd is a UPnP and NAT-PMP traversal daemon. Apples' AirPort and TimeCapsule run such a daemon too, not miniupnpd though. (Ubuntu users can already make port forwarding changes on Apple's time capsule. Applications like Pidgin and Transmission speak UPnP and NAT- PMP, they make appropriate mappings while running. If you want to make permanent port forwardings you better use Apple's AirPort Utility.) -- [needs packaging] miniupnpd https://bugs.launchpad.net/bugs/313642 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398272] [NEW] New upstream version
Public bug reported: Dovecot 1.2 with many new features is available now, current version is 1.2.1: http://www.dovecot.org/list/dovecot-news/2009-July/000122.html ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New -- New upstream version https://bugs.launchpad.net/bugs/398272 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot 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 398272] [NEW] New upstream version
Public bug reported: Dovecot 1.2 with many new features is available now, current version is 1.2.1: http://www.dovecot.org/list/dovecot-news/2009-July/000122.html ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New -- New upstream version https://bugs.launchpad.net/bugs/398272 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
