[Bug 1465220] Re: Only first six DNS search domains are used
** Changed in: ubuntu Status: New = Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1465220 Title: Only first six DNS search domains are used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1465220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1465220] Re: Only first six DNS search domains are used
I've also tried this on an older 12.04.4 LTS release and can reproduce the same behavior. No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04.4 LTS Release:12.04 Codename: precise Out of interest I found an old CentOS 5.3 install and I can again reproduce the same behavior there. So this doesn't appear to be a Ubuntu specific issue. However I've not found any documentation that states that the search domain will only use the first six entries. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1465220 Title: Only first six DNS search domains are used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1465220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1465220] [NEW] Only first six DNS search domains are used
Public bug reported: It appears as though only the first six DNS search domains are used. However this only affects certain commands/functions. One example is ping v's host. Ping will fail whereas host succeeds. PHP also exhibits this behavior. This may suggest some underlying library issue (something in libc6?). Example /etc/resolv.conf: nameserver 192.168.0.1 nameserver 192.168.0.2 search one.local two.local three.local four.local five.local six.local mycompany.local In the above example ping myserver.mycompany.local fails with unknown host. Whereas host myserver.mycompany.local succeeds. It was also found that PHP also has issues when doing name resolution. Changing the order of the search line in /etc/resolv.conf so that mycompany.local is the sixth search entry (or less) resolves the issue: nameserver 192.168.0.1 nameserver 192.168.0.2 search one.local two.local three.local four.local five.local mycompany.local six.local This is not a localized issue or something wrong with the DNS infrastructure. We are using the same search domains and ordering on our Windows server and client machines. This bug has been reproduced on four other Ubuntu 14.04 LTS installs. Additional information gathered from apport-bug against libc6 to assist: == ApportVersion = 2.14.1-0ubuntu3.11 == Architecture = amd64 == Date = Mon Jun 15 10:22:04 2015 == Dependencies = gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.6 == DistroRelease = Ubuntu 14.04 == InstallationDate = Installed on 2015-01-16 (149 days ago) == InstallationMedia = Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) == Package = libc6 2.19-0ubuntu6.6 == PackageArchitecture = amd64 == ProblemType = Bug == ProcEnviron = LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash == ProcVersionSignature = Ubuntu 3.13.0-32.57-generic 3.13.11.4 == SourcePackage = eglibc == Tags = trusty == Uname = Linux 3.13.0-32-generic x86_64 == UpgradeStatus = No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: dns network ** Tags added: dns network -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1465220 Title: Only first six DNS search domains are used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1465220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1465220] Re: Only first six DNS search domains are used
OK, so typically after filing this and then reproducing on an old CentOS install I did some more digging. Issue appears to be that MAXDNSRCH is hard coded to 6 in resolv.h. Not a bug as such but annoying. Also tricky for those of us who have a lot of search domains, quite probably in an enterprise environment where companies have been acquired. For now the only feasible workaround may be to install a local proxy DNS server to workaround this limitation although I've not tried this. Perhaps the init scripts for networking/resolvconf could print a warning if more than six search domains are defined? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1465220 Title: Only first six DNS search domains are used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1465220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 680192] Re: Vidalia was unable to start Tor. Check your settings to ensure the correct name and location of your Tor executable is specified.
This is because tor is starting as a system service. $ ls -l /etc/rc2.d/S20tor lrwxrwxrwx 1 root root 13 May 23 2009 /etc/rc2.d/S20tor - ../init.d/tor When you run Vidalia, tor needs to run tor under your user account. Vidalia tries to start tor but can't, because it's already running. So you need to stop tor before running Vidalia: $ sudo /etc/init.d/tor stop If you don't have the need to run tor at system start up (because you always use Vidalia for example), edit /etc/default/tor and set RUN_DAEMON to no. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/680192 Title: Vidalia was unable to start Tor. Check your settings to ensure the correct name and location of your Tor executable is specified. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 617872] Re: popen2 is deprecated.
Until yesterday I hadn't touched Python but I've attached a patch that corrects /usr/share/pysieved/plugins/dovecot.py and removes the use of popen2() and uses popen from subprocess. The code may not be technically correct but it works for me. Although I do see defunct Python processes after using Roundcube to create/edit filters. I've not checked if the original version did this. Also the location of the sievec binary in dovecot has changed and this is corrected in the patch. And /etc/pysieved.ini should also be changed to reflect this. Should another bug be opened against pysieved in Lucid Lynx regarding the change in sievec binary location? ** Patch added: Remove use of popen2 and use subprocess instead. https://bugs.launchpad.net/ubuntu/+source/pysieved/+bug/617872/+attachment/1491537/+files/dovecot.py.diff -- popen2 is deprecated. https://bugs.launchpad.net/bugs/617872 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 617872] [NEW] popen2 is deprecated.
Public bug reported: Binary package hint: pysieved When starting pysieved: /usr/share/pysieved/plugins/dovecot.py:27: DeprecationWarning: The popen2 module is deprecated. Use the subprocess module. import popen2 ** Affects: pysieved (Ubuntu) Importance: Undecided Status: New -- popen2 is deprecated. https://bugs.launchpad.net/bugs/617872 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 617872] Re: popen2 is deprecated.
# uname -a Linux hexstream 2.6.32-24-generic #39-Ubuntu SMP Wed Jul 28 06:07:29 UTC 2010 i686 GNU/Linux # lsb_release -rd Description:Ubuntu 10.04.1 LTS Release:10.04 # apt-cache policy pysieved pysieved: Installed: 1.0-1 Candidate: 1.0-1 Version table: *** 1.0-1 0 500 http://gb.archive.ubuntu.com/ubuntu/ lucid/universe Packages 100 /var/lib/dpkg/status -- popen2 is deprecated. https://bugs.launchpad.net/bugs/617872 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 489719] [NEW] portblock resource agent script is broken and will not work.
Public bug reported: Binary package hint: heartbeat The portblock resource agent script requires 4 arguements. However the script checks that only (exactly) 3 arguements are passed to it. Therefore when this resource agent is executed, it'll always display the script usage and return 1. In addition, the script exports the OCF_RESKEY_action variable twice and does not export the OCF_RESKEY_protocol variable. Once again this causes the resource agent to fail. Attached is a patch to correct this. ** Affects: heartbeat (Ubuntu) Importance: Undecided Status: New ** Affects: heartbeat (Debian) Importance: Unknown Status: Unknown ** Tags: apport-collected -- portblock resource agent script is broken and will not work. https://bugs.launchpad.net/bugs/489719 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 489719] Re: portblock resource agent script is broken and will not work.
** Attachment added: portblock.patch http://launchpadlibrarian.net/36208202/portblock.patch ** Bug watch added: Debian Bug tracker #538987 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538987 ** Also affects: heartbeat (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538987 Importance: Unknown Status: Unknown -- portblock resource agent script is broken and will not work. https://bugs.launchpad.net/bugs/489719 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 489719] apport-collect data
Architecture: amd64 DistroRelease: Ubuntu 9.10 Package: heartbeat 2.99.2+sles11r9-5ubuntu1 PackageArchitecture: amd64 ProcEnviron: SHELL=/bin/bash LANG=en_GB.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-14.48-server Uname: Linux 2.6.31-14-server x86_64 UserGroups: -- portblock resource agent script is broken and will not work. https://bugs.launchpad.net/bugs/489719 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 489719] Dependencies.txt
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/36208289/Dependencies.txt ** Tags added: apport-collected -- portblock resource agent script is broken and will not work. https://bugs.launchpad.net/bugs/489719 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 392499] [NEW] spine poller terminates with buffer overflow.
Public bug reported: Binary package hint: cacti-spine spine (package: cacti-spine) termines with: *** buffer overflow detected ***: spine terminated I have removed cacti and cacti-spine, purged configs and re-installed. Configured just one host+device to poll using spine and the same issue occurs. Please see attached spine-output.txt for the results of running spine from the CLI with verbosity set at 5 (spine --verbosity=5). Description:Ubuntu 9.04 Release:9.04 cacti-spine: Installed: 0.8.7a-2.3ubuntu1 Candidate: 0.8.7a-2.3ubuntu1 Version table: *** 0.8.7a-2.3ubuntu1 0 500 http://gb.archive.ubuntu.com jaunty/universe Packages 100 /var/lib/dpkg/status Linux noc 2.6.28-13-server #44-Ubuntu SMP Tue Jun 2 08:47:41 UTC 2009 i686 GNU/Linux linux-image-server: Installed: 2.6.28.13.17 Candidate: 2.6.28.13.17 Version table: *** 2.6.28.13.17 0 500 http://gb.archive.ubuntu.com jaunty-updates/main Packages 100 /var/lib/dpkg/status 2.6.28.11.15 0 500 http://gb.archive.ubuntu.com jaunty/main Packages ** Affects: cacti-spine (Ubuntu) Importance: Undecided Status: New ** Tags: buffer cacti cacti-spine overflow spine terminated -- spine poller terminates with buffer overflow. https://bugs.launchpad.net/bugs/392499 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 392499] Re: spine poller terminates with buffer overflow.
** Attachment added: spine-output.txt http://launchpadlibrarian.net/28413801/spine-output.txt -- spine poller terminates with buffer overflow. https://bugs.launchpad.net/bugs/392499 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 176934] Re: killproc routine removes PID file even if HUP is sent to process.
I've had a look at the lsb-base package in Debian unstable and with lsb- base 3.1-24, this bug has been fixed. http://packages.debian.org/changelogs/pool/main/l/lsb/lsb_3.1-24/changelog http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416559 * Don't remove the pidfile in killproc if a signal is specified; the specification does not specify this behavior, and it can cause problems with signals like HUP. (Closes: #416559) * And then, only remove the pidfile if the process is actually dead. (Closes: #410622) The fix in init-functions: if [ -z $sig ]; then pidofproc -p $pidfile $1 /dev/null || rm -f $pidfile fi -- killproc routine removes PID file even if HUP is sent to process. https://bugs.launchpad.net/bugs/176934 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 174466] Re: nagios2 init script has wrong PID file
In fact, looking in to this a bit more I think there is a more serious bug in the init script. A reload appears to to remove the PID file all together causing the issue that Kevin Lamontagne also reported. [EMAIL PROTECTED]:/var/run/nagios2# /etc/init.d/nagios2 start * Starting nagios2 monitoring daemon nagios2[ OK ] [EMAIL PROTECTED]:/var/run/nagios2# ls -l total 4 -rw-r--r-- 1 nagios nagios 6 2007-12-17 12:48 nagios2.pid [EMAIL PROTECTED]:/var/run/nagios2# /etc/init.d/nagios2 reload * Reloading nagios2 monitoring daemon configuration files nagios2 [ OK ] [EMAIL PROTECTED]:/var/run/nagios2# ls -l nagios2.pid ls: nagios2.pid: No such file or directory Note that a reload has removed the nagios2.pid file but the nagios2 process is still running. If you then try another reload, the init script can't find the nagios2.pid file so assumes it's not running but a ps says otherwise: [EMAIL PROTECTED]:/var/run/nagios2# /etc/init.d/nagios2 reload * Reloading nagios2 monitoring daemon configuration files nagios2 * Not running. [fail] [EMAIL PROTECTED]:/var/run/nagios2# ls -l nagios2.pid ls: nagios2.pid: No such file or directory [EMAIL PROTECTED]:/var/run/nagios2# ps aux | grep nagios nagios 19207 0.1 0.1 23628 2124 ?SNsl 12:50 0:00 /usr/sbin/nagios2 -d /etc/nagios2/nagios.cfg Now there are two scenarios. Firstly, if you didn't check with ps and assumed the init script is correct (i..e nagios2 isn't running when it actually is) and start nagios2, you end up with two nagios2 processes running. Or if you try to first run /etc/init.d/nagios2 stop this won't kill the process because there's no PID file (remember it was removed by /etc/init.d/nagios2 reload) and then assume it has been stopped and start it again, you once again end up with two nagios2 processes running. [EMAIL PROTECTED]:/var/run/nagios2# ls -l nagios2.pid ls: nagios2.pid: No such file or directory [EMAIL PROTECTED]:/var/run/nagios2# /etc/init.d/nagios2 stop * Stopping nagios2 monitoring daemon nagios2[ OK ] [EMAIL PROTECTED]:/var/run/nagios2# ps aux | grep nagios2 nagios 19207 0.0 0.6 28688 8116 ?SNsl 12:50 0:00 /usr/sbin/nagios2 -d /etc/nagios2/nagios.cfg [EMAIL PROTECTED]:/var/run/nagios2# /etc/init.d/nagios2 start * Starting nagios2 monitoring daemon nagios2[ OK ] [EMAIL PROTECTED]:/var/run/nagios2# ps aux | grep nagios nagios 19207 0.0 0.6 28688 8116 ?SNsl 12:50 0:00 /usr/sbin/nagios2 -d /etc/nagios2/nagios.cfg nagios 19787 1.0 0.1 22432 1636 ?SNsl 12:57 0:00 /usr/sbin/nagios2 -d /etc/nagios2/nagios.cfg [EMAIL PROTECTED]:/var/run/nagios2# cat nagios2.pid 19787 [EMAIL PROTECTED]:/var/run/nagios2# /etc/init.d/nagios2 stop * Stopping nagios2 monitoring daemon nagios2[ OK ] [EMAIL PROTECTED]:/var/run/nagios2# ps aux | grep nagios2 nagios 19207 0.0 0.6 28688 8116 ?SNsl 12:50 0:00 /usr/sbin/nagios2 -d /etc/nagios2/nagios.cfg I hope this makes sense? ** Summary changed: - nagios2 init script has wrong PID file + nagios2 init script has wrong PID file and incorrectly removes PID file on a reload. -- nagios2 init script has wrong PID file and incorrectly removes PID file on a reload. https://bugs.launchpad.net/bugs/174466 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 174466] Re: nagios2 init script has wrong PID file and incorrectly removes PID file on a reload.
I've had a further look in to this bug and it doesn't actually appear to be an issue with the nagios2 init script. I think the problem is actually in the killproc() sub-routine that's part of /lib/lsb/init- functions (lsb-base). killproc() from /lib/lsb/init-functions (lsb-base) does not check to see what type of signal was sent. If signal 1 is sent (HUP), it removes the PID file. The PID file shouldn't be removed on this action (I may be wrong?). I'll raise another bug against init-functions for lsb-base and see what feedback I get. Anyway, I've attached a patch for the original problem where the nagios2 init script has the wrong PID file, although this isn't a major problem. More for consistency. ** Attachment added: Patch to correct PID file name for consitency. http://launchpadlibrarian.net/10934576/nagios2.init.patch -- nagios2 init script has wrong PID file and incorrectly removes PID file on a reload. https://bugs.launchpad.net/bugs/174466 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 176934] killproc routine removes PID file even if HUP is sent to process.
Public bug reported: Binary package hint: lsb-base Whilst looking in to a bug with nagios2 (see bug #174466), I think there is a bug in the killproc() sub-routine within /lib/lsb/init-functions (from the lsb-base package). If an init script calls this sub-routine to issue a HUP siginal, the PID file is removed. For example: killproc -p $THEPIDFILE $DAEMON 1 This causes an issue because the PID file is removed, even though a HUP is sent to the process and as a result, a future reload (e.g. /etc/init.d/nagios2 reload) causes two daemons to be spawned because the PID file has been removed so the daemon's init script believes the daemon has stopped. Package: lsb-base Priority: required Section: misc Installed-Size: 76 Maintainer: Ubuntu Core Developers [EMAIL PROTECTED] Original-Maintainer: Chris Lawrence [EMAIL PROTECTED] Architecture: all Source: lsb Version: 3.1-23.1ubuntu3 Replaces: lsb-core ( 2.0-6), lsb ( 2.0-6) Depends: sed, ncurses-bin Conflicts: lsb-core ( 2.0-6), lsb ( 2.0-6) Filename: pool/main/l/lsb/lsb-base_3.1-23.1ubuntu3_all.deb Size: 20176 MD5sum: cfcd198d912a3ac8846b58c883c9c14a SHA1: 2dd7a35b92fb105ca4393a418dfcc869eab9b77e SHA256: 3c3fc72e2eb258faed465ce840c6c7601ed681cecb800df0885d741f8fd87d3f Description: Linux Standard Base 3.1 init script functionality The Linux Standard Base (http://www.linuxbase.org/) is a standard core system that third-party applications written for Linux can depend upon. . This package only includes the init-functions shell library, which may be used by other packages' initialization scripts for console logging and other purposes. Bugs: mailto:[EMAIL PROTECTED] Origin: Ubuntu This was noted in gusty. Other releases have not been tested or checked. ** Affects: lsb (Ubuntu) Importance: Undecided Status: New -- killproc routine removes PID file even if HUP is sent to process. https://bugs.launchpad.net/bugs/176934 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 176934] Re: killproc routine removes PID file even if HUP is sent to process.
Attached is a patch that (for me) corrects the above problem in killproc() from /lib/lsb/init-functions. It checks to see what signal type was sent. If the signal type is 1 (HUP), it does not remove the PID file. ** Attachment added: Stop PID from being removed when HUP is sent. http://launchpadlibrarian.net/10934612/init-functions.patch ** Description changed: Binary package hint: lsb-base Whilst looking in to a bug with nagios2 (see bug #174466), I think there is a bug in the killproc() sub-routine within /lib/lsb/init-functions (from the lsb-base package). If an init script calls this sub-routine to issue a HUP siginal, the PID file is removed. For example: killproc -p $THEPIDFILE $DAEMON 1 This causes an issue because the PID file is removed, even though a HUP is sent to the process and as a result, a future reload (e.g. /etc/init.d/nagios2 reload) causes two daemons to be spawned because the PID file has been removed so the daemon's init script believes the daemon has stopped. + + Package: lsb-base + Priority: required + Section: misc + Installed-Size: 76 + Maintainer: Ubuntu Core Developers [EMAIL PROTECTED] + Original-Maintainer: Chris Lawrence [EMAIL PROTECTED] + Architecture: all + Source: lsb + Version: 3.1-23.1ubuntu3 + Replaces: lsb-core ( 2.0-6), lsb ( 2.0-6) + Depends: sed, ncurses-bin + Conflicts: lsb-core ( 2.0-6), lsb ( 2.0-6) + Filename: pool/main/l/lsb/lsb-base_3.1-23.1ubuntu3_all.deb + Size: 20176 + MD5sum: cfcd198d912a3ac8846b58c883c9c14a + SHA1: 2dd7a35b92fb105ca4393a418dfcc869eab9b77e + SHA256: 3c3fc72e2eb258faed465ce840c6c7601ed681cecb800df0885d741f8fd87d3f + Description: Linux Standard Base 3.1 init script functionality + The Linux Standard Base (http://www.linuxbase.org/) is a standard + core system that third-party applications written for Linux can + depend upon. + . + This package only includes the init-functions shell library, which + may be used by other packages' initialization scripts for console + logging and other purposes. + Bugs: mailto:[EMAIL PROTECTED] + Origin: Ubuntu + + This was noted in gusty. Other releases have not been tested or checked. -- killproc routine removes PID file even if HUP is sent to process. https://bugs.launchpad.net/bugs/176934 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 174466] Re: nagios2 init script has wrong PID file.
Just for completeness, I've opened a bug against lsb-base. See bug #176934. ** Summary changed: - nagios2 init script has wrong PID file and incorrectly removes PID file on a reload. + nagios2 init script has wrong PID file. -- nagios2 init script has wrong PID file. https://bugs.launchpad.net/bugs/174466 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 174466] Re: nagios2 init script has wrong PID file
Exactly. It was after a /etc/init.d/nagios2 restart that I noticed we were getting two alerts emailed to us. Process list showed two nagios processes running and after some investigation I traced it back to the PID file problem in the init script. However, I'm not sure why the restart spawns another nagios process? Surely it should be able to read the nagios configuration file and determine the PID file location in the first instance instead of falling back to the hard coded THEPIDFILE='/var/run/nagios2/nagios.pid'? I'll try to find 5 minutes to add a set -x to the init script and see exactly what's going on. -- nagios2 init script has wrong PID file https://bugs.launchpad.net/bugs/174466 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 174466] nagios2 init script has wrong PID file
Public bug reported: Binary package hint: nagios2-common The init script for nagios2 (from nagios2-common) references the wrong PID file. This will only be an issue if the PID file can't be obtained from the nagios.cfg file. Line 118 of /etc/init.d/nagios2: [ -n $THEPIDFILE ] || THEPIDFILE='/var/run/nagios2/nagios.pid' This should read: [ -n $THEPIDFILE ] || THEPIDFILE='/var/run/nagios2/nagios2.pid' (note: nagios2.pid and not nagios.pid) Version information: Package: nagios2-common Priority: optional Section: universe/net Installed-Size: 404 Maintainer: Ubuntu MOTU Developers [EMAIL PROTECTED] Original-Maintainer: Debian Nagios Maintainer Group [EMAIL PROTECTED] Architecture: all Source: nagios2 Version: 2.9-1 This was noted in gusty. ** Affects: nagios2 (Ubuntu) Importance: Undecided Status: New -- nagios2 init script has wrong PID file https://bugs.launchpad.net/bugs/174466 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74052] Missing game directory config files
Public bug reported: In Edgy this package is missing the /usr/share/pennmush/game/ directory. This directory existsed in the dapper (1.8.0p9-1) version. These missing files means that when penn_install is run none of the config softlinks can be created and the server cannot be started. ** Affects: pennmush (Ubuntu) Importance: Undecided Status: Unconfirmed -- Missing game directory config files https://launchpad.net/bugs/74052 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74052] Re: Missing game directory config files
** Description changed: - In Edgy this package is missing the /usr/share/pennmush/game/ directory. + In Edgy (1.8.0p12-1) this package is missing the + /usr/share/pennmush/game/ directory. This directory existsed in the dapper (1.8.0p9-1) version. These missing files means that when penn_install is run none of the config softlinks can be created and the server cannot be started. -- Missing game directory config files https://launchpad.net/bugs/74052 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
