[Bug 1222274] [NEW] Incorrect upstart-job configuration
Public bug reported: Ubuntu: 12.04.3 LTS Package: Installed: 0.2.0-7ubuntu1.2 From: http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages Expected Behavior: Correct configuration, no boot-time warning Incorrect Behavior: 1) initctl check-config complains about a bogus event emitted, in rpcbind-boot.conf 2) Invalid warnings about the .xdr files occur at boot time Verbose Summary & Explanation (below): There are multiple problems with the current upstart-job for rpcbind. The first is that the upstart job events are incorrectly defined per the manual. The second, is that upon boot rpcbind will complain of two missing files, /run/rpcbind/rpcbind.xdr and /run/rpcbind/portmap.xdr The files changed (patch should be attached) provided fixes to both of these problems. The solution is to include the correct line, and to not start with -w on boot, since -w implies a 'warmstart' which only makes sense if the rpcbind has recently been running. Instead, only run with -w when both files are present - both files should be created when the rpcbind terminates, by default. Note: The patch is for the source package downloaded using: 'apt-get source rpcbind' Note 2: there is a related bug in Debian, using init.d, not upstart: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620800 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rpcbind 0.2.0-7ubuntu1.2 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Sat Sep 7 18:21:01 2013 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rpcbind UpgradeStatus: Upgraded to precise on 2012-05-14 (481 days ago) mtime.conffile..etc.init.portmap.conf: 2013-09-07T18:16:00.121056 mtime.conffile..etc.init.rpcbind.boot.conf: 2013-09-06T23:12:01.614469 ** Affects: rpcbind (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise rpcbind upstart-job ** Patch added: "generated diff patch using dpkg-diffs" https://bugs.launchpad.net/bugs/174/+attachment/3808219/+files/patch.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/174 Title: Incorrect upstart-job configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222274] Re: Incorrect upstart-job configuration
** Description changed: Ubuntu: 12.04.3 LTS Package: Installed: 0.2.0-7ubuntu1.2 From: http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages Expected Behavior: Correct configuration, no boot-time warning - Incorrect Behavior: - 1) initctl check-config complains about a bogus event emitted, in rpcbind-boot.conf - 2) Invalid warnings about the .xdr files occur at boot time + Incorrect Behavior: + 1) initctl check-config complains about a bogus event emitted, in rpcbind-boot.conf + 2) Invalid warnings about the .xdr files occur at boot time Verbose Summary & Explanation (below): There are multiple problems with the current upstart-job for rpcbind. The first is that the upstart job events are incorrectly defined per the manual. The second, is that upon boot rpcbind will complain of two missing files, /run/rpcbind/rpcbind.xdr and /run/rpcbind/portmap.xdr The files changed (patch should be attached) provided fixes to both of these problems. The solution is to include the correct line, and to not start with -w on boot, since -w implies a 'warmstart' which only makes sense if the rpcbind has recently been running. Instead, only run with -w when both files are present - both files should be created when the rpcbind terminates, by default. Note: The patch is for the source package downloaded using: 'apt-get source rpcbind' + Note 2: there is a related bug in Debian, using init.d, not upstart: + + http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620800 + ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rpcbind 0.2.0-7ubuntu1.2 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Sat Sep 7 18:21:01 2013 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MarkForUpload: True ProcEnviron: - TERM=xterm - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: rpcbind UpgradeStatus: Upgraded to precise on 2012-05-14 (481 days ago) mtime.conffile..etc.init.portmap.conf: 2013-09-07T18:16:00.121056 mtime.conffile..etc.init.rpcbind.boot.conf: 2013-09-06T23:12:01.614469 ** Description changed: Ubuntu: 12.04.3 LTS Package: Installed: 0.2.0-7ubuntu1.2 From: http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages Expected Behavior: Correct configuration, no boot-time warning Incorrect Behavior: 1) initctl check-config complains about a bogus event emitted, in rpcbind-boot.conf 2) Invalid warnings about the .xdr files occur at boot time Verbose Summary & Explanation (below): There are multiple problems with the current upstart-job for rpcbind. The first is that the upstart job events are incorrectly defined per the manual. The second, is that upon boot rpcbind will complain of two missing files, /run/rpcbind/rpcbind.xdr and /run/rpcbind/portmap.xdr The files changed (patch should be attached) provided fixes to both of these problems. The solution is to include the correct line, and to not start with -w on boot, since -w implies a 'warmstart' which only makes sense if the rpcbind has recently been running. Instead, only run with -w when both files are present - both files should be created when the rpcbind terminates, by default. Note: The patch is for the source package downloaded using: 'apt-get source rpcbind' Note 2: there is a related bug in Debian, using init.d, not upstart: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620800 + Also documented as an issue here: + + http://unix.stackexchange.com/questions/13437/rpcbind-warning-on-boot + ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rpcbind 0.2.0-7ubuntu1.2 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Sat Sep 7 18:21:01 2013 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rpcbind UpgradeStatus: Upgraded to precise on 2012-05-14 (481 days ago) mtime.conffile..etc.init.portmap.conf: 2013-09-07T18:16:00.121056 mtime.conffile..etc.init.rpcbind.boot.conf: 2013-09-06T23:12:01.614469 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/174 Title: Incorrect upstart-job configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/174/+subscriptions -- ubuntu-bugs mailing list ub
[Bug 1222291] [NEW] Excessive disk thrashing on triggering gtk-update-icon-cache
Public bug reported: Platform: Ubuntu 12.04.3 LTS Version Information: Installed: 0.12-1ubuntu2 Candidate: 0.12-1ubuntu2 Version table: *** 0.12-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages Expected Behavior: No system freeze on updating the icon cache Actual Behavior: Inconvenient system hangs whenever an application updates the icon cache through e.g. updates. Extended Description: Any time an application is updated, or added, which uses icons stored in /usr/share/icons/hicolor, dpkg updated the icon cache through the triggering process. The command being run is gtk-update-icon-cache --force, which according to the manual rebuilds the entire icon cache. Whenever this command is run, a slowdown of the entire system occurs, and does not relent until the cache is rebuilt. Instead, run it with --validate. A patch (in diff format) is attached which is intended to replace the package maintainer's script in debian/postinstall. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: hicolor-icon-theme 0.12-1ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Sat Sep 7 19:59:06 2013 Dependencies: EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: hicolor-icon-theme UpgradeStatus: Upgraded to precise on 2012-05-14 (481 days ago) ** Affects: hicolor-icon-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug patch precise ** Patch added: "patch.diff" https://bugs.launchpad.net/bugs/191/+attachment/3808300/+files/patch.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/191 Title: Excessive disk thrashing on triggering gtk-update-icon-cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1167622] Re: Cannot change EFI variables using efibootmgr (raring regression)
*** This bug is a duplicate of bug 1173423 *** https://bugs.launchpad.net/bugs/1173423 I think I may have this issue as well, running Kubuntu 13.04, here's my bios id: dmidecode -s bios-version 7ACN24WW uname -r 3.8.0-19-generic lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 13.04 Release:13.04 Codename: raring Symptoms: efibootmgr -c -l 'EFI\package\BOOT.EFI' and variants of the above command produce the aforementioned dmesg output about errors writing to nvram. Hope this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1167622 Title: Cannot change EFI variables using efibootmgr (raring regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1167622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1173423] Re: Kernel fails to update EFI vars, rendering system unbootable [P8P67 PRO REV 3.1, BIOS 1904 08/15/2011]
Repost, didn't see the duplicate status on: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1167622 I think I may have this issue as well, running Kubuntu 13.04, here's my bios id: dmidecode -s bios-version 7ACN24WW uname -r 3.8.0-19-generic lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 13.04 Release: 13.04 Codename: raring Symptoms: efibootmgr -c -l 'EFI\package\BOOT.EFI' and variants of the above command produce the aforementioned dmesg output about errors writing to nvram. Hope this helps. Is this fix supposed to be live or not? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1173423 Title: Kernel fails to update EFI vars, rendering system unbootable [P8P67 PRO REV 3.1, BIOS 1904 08/15/2011] To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1173423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 973951] Re: package mysql-server-5.5 5.5.22-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Well, I had this issue too, looks like launchpad doesn't let me submit a
bug.
My 'fix' is less of a fix, but here's my feedback:
'Ubuntu version: 12.04.2 LTS (Kubuntu)
Specific package version: 5.5.22-0ubuntu1
Expected behavior: Install should succeed, job should start
Actual behavior: Install does not succeed, job cannot start
There is an issue with the upstart script in /etc/init/mysql.conf.
Please find attached my 'fixes'. Please note that these fixes contain
extra notes, and are not considered patch material, e.g. I have
commented out offending code, and I have commented out a function which
needs to be included.
In summary:
Problem #1
mysqld_get_param does not exist. This must be included, or replaced with the
line used in the file.
Problem #2
An assumption is made that the data dir exists on a seperate partition. If this
is not the case, the upstart script will fail to launch.
Problem #3
Thanks to these issue, the mysql-server cannot be configured from the package
manager, as the upstart job fails, causing the install to fail to succeed.
Result:
After I made the changes seen in the attached file, the problems went away.
This file needs some polish however, including detecting whether or not the
user has a seperate partition or not.'
my /etc/init/mysql.conf (there are/were multiple issues):
# MySQL Service
description "MySQL Server"
author "Mario Limonciello "
start on runlevel [2345]
stop on starting rc RUNLEVEL=[016]
respawn
respawn limit 2 5
env HOME=/etc/mysql
umask 007
# The default of 5 seconds is too low for mysql which needs to flush buffers
kill timeout 300
#mysqld_get_param() {
# /usr/sbin/mysqld --print-defaults \
# | tr " " "\n" \
# | grep -- "--$1" \
# | tail -n 1 \
# | cut -d= -f2
#}
pre-start script
# priority can be overriden and "-s" adds output to stderr
ERR_LOGGER="logger -p daemon.err -t /etc/init/mysql.conf -i"
#Sanity checks
[ -r $HOME/my.cnf ]
[ -d /var/run/mysqld ] || install -m 755 -o mysql -g root -d /var/run/mysqld
/lib/init/apparmor-profile-load usr.sbin.mysqld
# check for diskspace shortage
datadir=`/usr/sbin/mysqld --print-defaults | tr " " "\n" | grep --
"--datadir" | tail -n 1 | cut -d= -f2`
#if LC_ALL=C BLOCKSIZE= df --portability $datadir/. | tail -n 1 | awk '{
exit ($4<4096) }'; then
# echo "$0: ERROR: The partition with $datadir is too full!" >&2
# echo"ERROR: The partition with $datadir is too full!" |
$ERR_LOGGER
# exit 1
#fi
end script
exec /usr/sbin/mysqld
post-start script
for i in `seq 1 30` ; do
/usr/bin/mysqladmin --defaults-file="${HOME}"/debian.cnf ping && {
exec "${HOME}"/debian-start
# should not reach this line
exit 2
}
statusnow=`status`
if echo $statusnow | grep -q 'stop/' ; then
exit 0
elif echo $statusnow | grep -q 'respawn/' ; then
exit 1
fi
sleep 1
done
exit 1
end script
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973951
Title:
package mysql-server-5.5 5.5.22-0ubuntu1 failed to install/upgrade:
subprocess installed post-installation script returned error exit
status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/973951/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
