[Bug 189462] Re: slocate cron job fails if /etc/updatedb.conf not found
@Akkana: The slocate package should not depend on mlocate. mlocate was written after slocate, and designed to function identically (with the exception of the update algorithm used by updatedb) to it. Hence, they both use the same /etc/updatedb.conf file. The mlocate package is "complete" and includes this file as it should. The slocate package is simply broken because it does not include a copy of this file as well. Using the version included with the mlocate package should work fine as a workaround, however it's important to know this is simply a side- effect of the packaging and not because there's a dependency there. -- slocate cron job fails if /etc/updatedb.conf not found https://bugs.launchpad.net/bugs/189462 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 189462] Re: slocate cron job fails if /etc/updatedb.conf not found
Regardless of mlocate, this problem exists on servers as well. It also doesn't excuse shipping broken packages, whether they're the default or not. -- slocate cron job fails if /etc/updatedb.conf not found https://bugs.launchpad.net/bugs/189462 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 223706] [NEW] fail2ban does not create /var/run/fail2ban
Public bug reported: Binary package hint: fail2ban I just upgraded from gutsy to hardy, and noticed fail2ban stopped running. Kicking off the daemon manually produces the following: [EMAIL PROTECTED]:~# fail2ban-server 2008-04-28 11:14:24,896 fail2ban.server : INFO Starting Fail2ban v0.8.2 2008-04-28 11:14:24,897 fail2ban.server : ERROR Unable to create PID file: [Errno 2] No such file or directory: '/var/run/fail2ban/fail2ban.pid' Sure enough, if i mkdir /var/run/fail2ban it appears to start working again. Why, then, does the init script not create this directory itself? ** Affects: fail2ban (Ubuntu) Importance: Undecided Status: New -- fail2ban does not create /var/run/fail2ban https://bugs.launchpad.net/bugs/223706 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 222017] [NEW] slocate does not create /etc/updatedb.conf
Public bug reported: Binary package hint: slocate I just upgraded to hardy final, and I received an error message that updatedb was failing to run because it couldn't find /etc/updatedb.conf. Sure enough, it's not there. Wondering if this was just a quirk of the upgrade I did apt-get purge slocate, apt-get install slocate, but the file still isn't created. This would appear to make slocate inherently broken unless I'm missing something. [EMAIL PROTECTED]:~# /etc/cron.daily/slocate slocate: fatal error: load_file: Could not open file: /etc/updatedb.conf: No such file or directory DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.04 DISTRIB_CODENAME=hardy DISTRIB_DESCRIPTION="Ubuntu 8.04" ** Affects: slocate (Ubuntu) Importance: Undecided Status: New -- slocate does not create /etc/updatedb.conf https://bugs.launchpad.net/bugs/222017 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 100019] Re: Segfault in Samba
Acked - it appears to catch the condition gracefully in hardy. [2008/04/06 20:48:13, 0] nmbd/nmbd.c:main(711) Netbios nameserver version 3.0.28a started. Copyright Andrew Tridgell and the Samba Team 1992-2008 [2008/04/06 20:48:13, 0] nmbd/nmbd_subnetdb.c:create_subnets(245) create_subnets: unable to create any subnet from given interfaces. nmbd is terminating [2008/04/06 20:48:13, 0] nmbd/nmbd.c:main(785) ERROR: Failed when creating subnet lists. Exiting. -- Segfault in Samba https://bugs.launchpad.net/bugs/100019 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 158582] Re: ifup will fail if IPv6 has been compiled in the kernel
I researched this a bit more. It appears it's modprobe that is actually broken... modprobe -Q *should* work as intended here, but the modprobe source doesn't seem to implement the -Q flag in practice. I've opened bug 210891 to address this. -- ifup will fail if IPv6 has been compiled in the kernel https://bugs.launchpad.net/bugs/158582 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 210891] [NEW] modprobe -Q does not work
Public bug reported: Binary package hint: module-init-tools The ifupdown package calls modprobe -Q ipv6 (Bug 158582). The manpage suggests this syntax _should_ be correct. Further research shows that the modprobe source actually does not appear to implement -Q. It's listed in the manpage and getopt_long of modprobe.c, but there's no case statement to accept it. This case statement should be added to create the effect already listed in the manpage. ** Affects: module-init-tools (Ubuntu) Importance: Undecided Status: New -- modprobe -Q does not work https://bugs.launchpad.net/bugs/210891 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 158582] Re: ifup will fail if IPv6 has been compiled in the kernel
@Malte: The patch seems to break debuild for me; one of the tests is failing. Does it work for you? -- ifup will fail if IPv6 has been compiled in the kernel https://bugs.launchpad.net/bugs/158582 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 158582] Re: ifup will fail if IPv6 has been compiled in the kernel
+1 This appears to be making my Linode sad. :( -- ifup will fail if IPv6 has been compiled in the kernel https://bugs.launchpad.net/bugs/158582 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 206343] [NEW] checkbashisms incorrectly identifies "source"
Public bug reported: Binary package hint: devscripts The checkbashisms script doesn't recognized when the word "source" is simply appearing in a text string, and reports a problem: [test.sh] #!/bin/sh echo "this is some source $code" $> checkbashisms test.sh possible bashism in /tmp/test.sh line 2 (should be '.', not 'source'): echo "this is some source $code" ** Affects: devscripts (Ubuntu) Importance: Undecided Status: New -- checkbashisms incorrectly identifies "source" https://bugs.launchpad.net/bugs/206343 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 204971] [NEW] ip_always_defrag is invalid
Public bug reported: Binary package hint: procps The current sysctl.conf in Hardy includes this suggestion: # Always defragment packets #net/ipv4/ip_always_defrag = 1 As far as I can tell this is an invalid key... ergo, these couple lines should probably be removed to avoid confusion. ** Affects: procps (Ubuntu) Importance: Undecided Status: New -- ip_always_defrag is invalid https://bugs.launchpad.net/bugs/204971 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 195310] [NEW] horde3 config diff contains invalid backslashes
Public bug reported: Binary package hint: horde3 line 347 of horde3_3.1.4-1.diff.gz contains the following line: printf "\n\$$conf[\'log\'][\'name\'] = \'/var/log/horde/horde3.log\';" >> debian/horde3/etc/horde/horde3/conf.php The backslashes found therein are copied into /etc/horde/horde3/conf.php, and since they are invalid characters for the config, they break the installation. The final product winds up reading like this: conf[\'log\'][\'name\'] = \'/var/log/horde/horde3.log\'; rather than this: conf['log']['name'] = '/var/log/horde/horde3.log'; ** Affects: horde3 (Ubuntu) Importance: Undecided Status: New -- horde3 config diff contains invalid backslashes https://bugs.launchpad.net/bugs/195310 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 192036] [NEW] sa-learn does not preserve file permissions
Public bug reported: Binary package hint: spamassassin I'm running spamassassin 3.2.3-0ubuntu1 (gutsy). The SA daemon runs as an unprivileged user (--groupname=spamd --username=spamd), and therefore it creates its bayes files chown that user: [EMAIL PROTECTED]:~# ls -al .spamassassin/ -rw--- 1 spamd spamd 1269760 Feb 14 20:44 auto-whitelist -rw--- 1 spamd spamd 659456 Feb 14 20:45 bayes_seen -rw--- 1 spamd spamd 5308416 Feb 14 20:45 bayes_toks -rw-r--r-- 1 spamd spamd1487 Aug 1 2007 user_prefs The problem is, the sa-learn utility provides no facility to run as a different user. If sa-learn is run as root, the bayes_toks file becomes chown root, and the daemon loses access to it (not sure why... see below). This creates an awkward combination of file access issues. The sa-learn application needs to run as the spamd user (from cron in my case), but if its host script runs as the unprivileged user it will not have access read/remove mail files from the maildirs. Running the script as root gives it the required access, but breaks the bayes_toks file. There are various ways to work around this issue, but the ones I've come up with seem hackish. Running multiple scripts, or doing a manual chown, causes race conditions. I can see two "good" ways to fix this, both of which should be implemented in sa-learn itself: 1) Give sa-learn the same --groupname/--username options as the daemon has. That way the host script can run as root while sa-learn still runs as the proper user. 2) Rework sa-learn to respect the existing file ownership. I don't really understand why sa-learn changes the ownership of bayes_toks to begin with, so should it be considered a bug, this might be a quick fix. ** Affects: spamassassin (Ubuntu) Importance: Undecided Status: New -- sa-learn does not preserve file permissions https://bugs.launchpad.net/bugs/192036 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 182086] Re: dovecot-common postinst fails for multiple ssl certs
The problem I see here is that the new script will wind up creating X number of certs with the same domain name... a scenario I'm not sure one would see in practice. My config uses separate domains for the imap and pop services (and therefore separate certs), which is why I hit this bug in the first place. I personally think dealing with this level of customization may be out of the scope of what the postinst needs to handle. -- dovecot-common postinst fails for multiple ssl certs https://bugs.launchpad.net/bugs/182086 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 185692] [NEW] pinning negative preferences not preventing installation
Public bug reported: Binary package hint: apt I'm not sure if this is a problem with the documentation, or a problem with the application, however apt is not behaving as expected when pinning negative values. According to man 5 apt_preferences, a Pin-Priority "P < 0 prevents the version from being installed." Now I'll take a package at random and pin it in /etc/apt/preferences: Package: python-tcm Pin: version 0.5.1-0ubuntu4 Pin-Priority: -100 And yet, the package attempts to install: [EMAIL PROTECTED]:/tmp# apt-get -Vs install python-tcm Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: pessulus (2.16.3-0ubuntu1) python-tcm (0.5.1-0ubuntu4) 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Inst python-tcm (0.5.1-0ubuntu4 Ubuntu:7.10/gutsy) Conf python-tcm (0.5.1-0ubuntu4 Ubuntu:7.10/gutsy) The same occurs with a generalized version (Pin: version *). ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- pinning negative preferences not preventing installation https://bugs.launchpad.net/bugs/185692 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 182086] dovecot-common postinst fails for multiple ssl certs
Public bug reported: Binary package hint: dovecot-common The post-inst script for dovecot does not take into account having multiple ssl certs in the configuration. If there are, the script fails as follows: *** Unpacking replacement dovecot-common ... Setting up dovecot-common (1:1.0.5-1ubuntu2.1) ... [: 75: /etc/ssl/certs/cert2.crt: unexpected operator Creating generic self-signed certificate: /etc/ssl/certs/cert1.crt /etc/ssl/certs/cert2.crt /etc/ssl/certs/cert3.crt (replace with hand-crafted or authorized one if needed). Warning : Bad SSL config, can't generate certificate. [: 75: /etc/ssl/certs/cert2.crt: unexpected operator Setting up dovecot-pop3d (1:1.0.5-1ubuntu2.1) ... * Restarting IMAP/POP3 mail server dovecot [ OK ] Setting up dovecot-imapd (1:1.0.5-1ubuntu2.1) ... * Restarting IMAP/POP3 mail server dovecot This appears to be the fault of the following grep not accounting for multiple occurances in postinst: ## SSL Certs # Certs and key file SSL_CERT=$( (grep "ssl_cert_file" /etc/dovecot/dovecot.conf || echo '/etc/ssl/certs/dovecot.pem') | cut -d'=' -f2) SSL_KEY=$( (grep "ssl_key_file" /etc/dovecot/dovecot.conf || echo '/etc/ssl/private/dovecot.pem') | cut -d'=' -f2) I would recommend adding -m 1 to the grep to limit the number of hits returned to one. This wouldn't help if a random one of multiple certs was missing, but it would avoid breakage and serve the same purpose it was intended to serve now. ## SSL Certs # Certs and key file SSL_CERT=$( (grep -m 1 "ssl_cert_file" /etc/dovecot/dovecot.conf || echo '/etc/ssl/certs/dovecot.pem') | cut -d'=' -f2) SSL_KEY=$( (grep -m 1 "ssl_key_file" /etc/dovecot/dovecot.conf || echo '/etc/ssl/private/dovecot.pem') | cut -d'=' -f2) ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New -- dovecot-common postinst fails for multiple ssl certs https://bugs.launchpad.net/bugs/182086 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 179169] clamav-milter init script doesn't check for existing process
Public bug reported: Binary package hint: clamav-milter The init script for clamav-milter doesn't check for existing clamav- milter processes as of version 0.92~dfsg-0build1. As a result, it's possible to run the init script 'start' multiple times successively and spawn multiple daemons running at once. The would seem ill-advised, especially given that file-based controls such as sockets and pid files are in use by default. ** Affects: clamav (Ubuntu) Importance: Undecided Status: New -- clamav-milter init script doesn't check for existing process https://bugs.launchpad.net/bugs/179169 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 157431] Re: Request to version bump proftpd to 1.3.1
Since this version is available under Hardy and there have been no other further updates by the bug reporter, I'm closing this issue as Fixed. ** Changed in: proftpd (Ubuntu) Status: New => Fix Released -- Request to version bump proftpd to 1.3.1 https://bugs.launchpad.net/bugs/157431 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 177489] Re: loss of masters causing bind to become unresponsive
I was mad at myself for losing the strace from the other thread, so I
re-enabled a broken slave zone and recreated the problem (easily).
Here's the tail of an strace from the thread that seems to be hanging on
the ipsec ip, just as it stops responding:
futex(0xb7a8f0f0, FUTEX_WAIT, 943, NULL) = 0
futex(0xb7a8f0b8, FUTEX_WAIT, 2, NULL)= -1 EAGAIN (Resource temporarily
unavailable)
futex(0xb7a8f0b8, FUTEX_WAKE, 1)= 0
gettimeofday({1198079742, 934859}, NULL) = 0
gettimeofday({1198079742, 935156}, NULL) = 0
gettimeofday({1198079742, 935487}, NULL) = 0
futex(0xb7a8f0f0, FUTEX_WAIT, 945, NULL) = 0
futex(0xb7a8f0b8, FUTEX_WAIT, 2, NULL)= -1 EAGAIN (Resource temporarily
unavailable)
futex(0xb7a8f0b8, FUTEX_WAKE, 1)= 0
gettimeofday({1198079742, 948815}, NULL) = 0
gettimeofday({1198079742, 949291}, NULL) = 0
gettimeofday({1198079742, 949505}, NULL) = 0
futex(0xb7a8f0f0, FUTEX_WAIT, 947, NULL) = 0
futex(0xb7a8f0b8, FUTEX_WAIT, 2, NULL)= -1 EAGAIN (Resource temporarily
unavailable)
futex(0xb7a8f0b8, FUTEX_WAKE, 1)= 0
gettimeofday({1198079745, 920414}, NULL) = 0
gettimeofday({1198079745, 920873}, NULL) = 0
gettimeofday({1198079745, 921082}, NULL) = 0
gettimeofday({1198079745, 921309}, NULL) = 0
futex(0xb7a91044, 0x5 /* FUTEX_??? */, 1) = 1
futex(0xb7a91010, FUTEX_WAKE, 1) = 0
gettimeofday({1198079745, 922263}, NULL) = 0
gettimeofday({1198079745, 923564}, NULL) = 0
gettimeofday({1198079745, 923935}, NULL) = 0
sendmsg(32, {msg_name(16)={sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("192.168.5.5")},
msg_iov(1)=[{"+\305\0\0\0\1\0\0\0\0\0\1\3glv\3lan\0\0\6\0\1\0\0)\10\0"...,
36}], msg_controllen=0, msg_flags=0}, 0
And here's the tail of a final thread, which also seems to stop doing anything
during the hang. (The output of the third thread, the one that seems to loop
forever, is in the original post):
read(5, 0xb6a8b174, 8) = -1 EAGAIN (Resource temporarily
unavailable)
select(36, [5 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35], [], NULL, NULL)
= 1 (in [22])
futex(0xb7a8f0f0, 0x5 /* FUTEX_??? */, 1) = 1
futex(0xb7a8f0b8, FUTEX_WAKE, 1) = 0
select(36, [5 20 21 23 24 25 26 27 28 29 30 31 32 33 34 35], [], NULL, NULL) =
1 (in [5])
read(5, "\26\0\0\0\375\377\377\377", 8) = 8
read(5, 0xb6a8b174, 8) = -1 EAGAIN (Resource temporarily
unavailable)
select(36, [5 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35], [], NULL, NULL)
= 1 (in [32])
futex(0xb7a8f0f0, 0x5 /* FUTEX_??? */, 1) = 1
futex(0xb7a8f0b8, FUTEX_WAKE, 1) = 0
select(36, [5 20 21 22 23 24 25 26 27 28 29 30 31 33 34 35], [], NULL, NULL) =
1 (in [5])
read(5, " \0\0\0\375\377\377\377", 8) = 8
read(5, 0xb6a8b174, 8) = -1 EAGAIN (Resource temporarily
unavailable)
select(36, [5 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35], [], NULL, NULL)
= 1 (in [32])
futex(0xb7a8f0f0, 0x5 /* FUTEX_??? */, 1) = 1
futex(0xb7a8f0b8, FUTEX_WAKE, 1) = 0
select(36, [5 20 21 22 23 24 25 26 27 28 29 30 31 33 34 35], [], NULL, NULL) =
1 (in [5])
read(5, " \0\0\0\375\377\377\377", 8) = 8
read(5, 0xb6a8b174, 8) = -1 EAGAIN (Resource temporarily
unavailable)
select(36, [5 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35], [], NULL, NULL)
= 1 (in [34])
select(36, [5 20 21 22 23 24 25 26 27 28 29 30 31 32 33 35], [], NULL, NULL) =
1 (in [35])
select(36, [5 20 21 22 23 24 25 26 27 28 29 30 31 32 33], [], NULL, NULL) = 1
(in [22])
select(36, [5 20 21 23 24 25 26 27 28 29 30 31 32 33], [], NULL, NULL
--
loss of masters causing bind to become unresponsive
https://bugs.launchpad.net/bugs/177489
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 177489] loss of masters causing bind to become unresponsive
Public bug reported:
Binary package hint: bind
Bind lived up to its name this morning. I have a bind server that
effectively serves triple duty providing:
- Public zones
- Private zones (for the lan)
- Recursive lookups and caching for lan hosts
The first two are effectively the same thing except for some ACLs, but
that's really beside the point. Anyway, for the sake of this example,
assume the public zones and private zones are all slave zones. The
public zones load over public ip addresses, while the private (lan)
zones load over an ipsec connection to the master's network.
This morning the ipsec connection went away, as it occasionally does,
and shortly thereafter so did bind. What really boggled me was that
named would become completely unresponsive, even after rebooting the
server, within a couple minutes of startup. It would refuse to do any
lookups, would fail to resolve its own zones, and even failed to respond
to rndc for restarts. Basically, I'd have to kill -9 it, then restart.
It would work for a minute or two, then re-hang.
After poking around for some time, I broke out strace and had a look at
a few of the threads running under named. One thread looked like it was
waiting for input from the master over the down ipsec connection.
Another appeared to be in a bit of an infinite loop of the following:
clock_gettime(CLOCK_REALTIME, {1198072309, 972541645}) = 0
futex(0xb7a72044, FUTEX_WAIT, 1671, {0, 403081355}) = -1 ETIMEDOUT (Connection
t imed out)
gettimeofday({1198072310, 377730}, NULL) = 0
futex(0xb7a72010, FUTEX_WAKE, 1)= 0
clock_gettime(CLOCK_REALTIME, {1198072310, 379388030}) = 0
futex(0xb7a72044, FUTEX_WAIT, 1673, {0, 11452970}) = -1 ETIMEDOUT (Connection
ti med out)
gettimeofday({1198072310, 392700}, NULL) = 0
futex(0xb7a72010, FUTEX_WAKE, 1)= 0
clock_gettime(CLOCK_REALTIME, {1198072310, 394254492}) = 0
futex(0xb7a72044, FUTEX_WAIT, 1675, {0, 77563508}) = -1 ETIMEDOUT (Connection
ti med out)
gettimeofday({1198072310, 473689}, NULL) = 0
futex(0xb7a72010, FUTEX_WAKE, 1)= 0
clock_gettime(CLOCK_REALTIME, {1198072310, 475455403}) = 0
futex(0xb7a72044, FUTEX_WAIT, 1677, {0, 498233597}) = -1 ETIMEDOUT (Connection
t imed out)
gettimeofday({1198072310, 976660}, NULL) = 0
futex(0xb7a72010, FUTEX_WAKE, 1)= 0
clock_gettime(CLOCK_REALTIME, {1198072310, 977375142}) = 0
futex(0xb7a72044, FUTEX_WAIT, 1679, {0, 499284858}) = -1 ETIMEDOUT (Connection
t imed out)
gettimeofday({1198072311, 478563}, NULL) = 0
futex(0xb7a72010, FUTEX_WAKE, 1)= 0
clock_gettime(CLOCK_REALTIME, {1198072311, 480351624}) = 0
futex(0xb7a72044, FUTEX_WAIT, 1681, {0, 498211376}) = ? ERESTART_RESTARTBLOCK
(T o be restarted)
I took the hint and commented out the couple private zones thats required the
master over ipsec. Following that, named has stayed up and running as normal.
Apparently somewhere in the bind code, if it doesn't hear back from a master it
will literally wait forever and stop serving all data. This, imo, is not good.
I also have the following additional observations to add:
- This is not the first time the ipsec connection has gone away, but it's the
first time I've seen this. It may also be the first time ipsec has been down
since upgrading to edgy, so the problem may be new in bind 9.4. It could also
be a bizarre coincidence.
- The public zones, which resolve over public ip addresses, did not cause a
failure even when their master was unreachable. This leads me to believe that
there is something about the way ipsec dealt with bind's queries that was
creating the condition, but I still think it's a condition bind should be able
to deal with.
** Affects: bind (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Binary package hint: bind
Bind lived up to its name this morning. I have a bind server that
- effectively serves triple duty surving:
+ effectively serves triple duty providing:
- Public zones
- Private zones (for the lan)
- Recursive lookups and caching for lan hosts
The first two are effectively the same thing except for some ACLs, but
that's really beside the point. Anyway, for the sake of this example,
assume the public zones and private zones are all slave zones. The
public zones load over public ip addresses, while the private (lan)
zones load over an ipsec connection to the master's network.
This morning the ipsec connection went away, as it occasionally does,
and shortly thereafter so did bind. What really boggled me was that
named would become completely unresponsive, even after rebooting the
server, within a couple m
[Bug 155061] Re: slocate typo: "serach_db"
** Bug watch added: Debian Bug tracker #457004 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457004 ** Also affects: slocate (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457004 Importance: Unknown Status: Unknown -- slocate typo: "serach_db" https://bugs.launchpad.net/bugs/155061 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 155061] Re: slocate typo: "serach_db"
** Changed in: slocate (Ubuntu) Status: New => Confirmed -- slocate typo: "serach_db" https://bugs.launchpad.net/bugs/155061 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 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!
Brian: When the slocate package is installed, it essentially replaces the 'locate' functionality in findutils. It diverts findutils version of /etc/cron.daily/find to /etc/cron.daily/find.notslocate to prevent it from running (cron jobs with a dot in the name do not run). Slocates own /etc/cron.daily/slocate replaces this functionality. Since the script included with slocate is not broken (at least in this regard), anyone who has slocate installed is essentially unaffected by this bug. -- updatedb cron job re-nices wrong process (pid 7 by default)! https://bugs.launchpad.net/bugs/152692 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 174746] Re: package kdebase-data-kde4 4:3.96.0-1ubuntu1 failed to install/upgrade: trying to overwrite `/usr/lib/kde4/share/dbus-1/interfaces/org.kde.FavIcon.xml', which is also in package konque
Confirmed with 3.97.0-1ubuntu2 ** Changed in: kdebase-kde4 (Ubuntu) Status: New => Confirmed -- package kdebase-data-kde4 4:3.96.0-1ubuntu1 failed to install/upgrade: trying to overwrite `/usr/lib/kde4/share/dbus-1/interfaces/org.kde.FavIcon.xml', which is also in package konqueror-kde4 https://bugs.launchpad.net/bugs/174746 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 151331] Re: installer crashes whenever i try to start it from the live cd
*** This bug is a duplicate of bug 151060 *** https://bugs.launchpad.net/bugs/151060 ** This bug has been marked a duplicate of bug 151060 apport-qt crashed with AttributeError in ui_present_report_details() -- installer crashes whenever i try to start it from the live cd https://bugs.launchpad.net/bugs/151331 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 174305] Re: command-not-found package need depends python-gdbm
** Attachment added: "C:\Documents and Settings\Administrator\My Documents\command-not-found.diff" http://launchpadlibrarian.net/10798000/C%3A%5CDocuments%20and%20Settings%5CAdministrator%5CMy%20Documents%5Ccommand-not-found.diff -- command-not-found package need depends python-gdbm https://bugs.launchpad.net/bugs/174305 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 174305] Re: command-not-found package need depends python-gdbm
Also confirmed. -- command-not-found package need depends python-gdbm https://bugs.launchpad.net/bugs/174305 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 174723] Re: Whoops, command-not-found has crashed!
*** This bug is a duplicate of bug 164105 *** https://bugs.launchpad.net/bugs/164105 ** This bug has been marked a duplicate of bug 164105 command-not-found has crashed! -- Whoops, command-not-found has crashed! https://bugs.launchpad.net/bugs/174723 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 165274] Re: kdm-kde4 post-install error
ditto -- kdm-kde4 post-install error https://bugs.launchpad.net/bugs/165274 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 157431] Re: Request to version bump proftpd to 1.3.1
Hardy now features 1.3.1-2ubuntu1. Is this sufficient for closing this request? -- Request to version bump proftpd to 1.3.1 https://bugs.launchpad.net/bugs/157431 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 68735] Re: Module mod-tls.c is missing in the proftpd edgy package
This issue appears to have been explained, and there's been no response to the contrary in several months. ** Changed in: proftpd (Ubuntu) Status: New => Invalid -- Module mod-tls.c is missing in the proftpd edgy package https://bugs.launchpad.net/bugs/68735 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 153996] Re: libdb4.4 in gutsy breaks postgrey and subversion
If you want to avoid installing everything out of gutsy-proposed when doing an apt-upgrade, create the file /etc/apt/preferences with something like the following: Package: libdb4.4 Pin: release a=gutsy-proposed Pin-Priority: 600 Package: * Pin: release a=gutsy-proposed Pin-Priority: 400 -- libdb4.4 in gutsy breaks postgrey and subversion https://bugs.launchpad.net/bugs/153996 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 153996] Re: libdb4.4 in gutsy breaks postgrey and subversion
Ok, sorry for the noise. I think my previous entry may have been a false alarm. It's my theory that, although at the time of the crash the fixed libdb was installed, postgrey may not have been restarted following the upgrade, and may therefore have still had the faulty library loaded. Since the crash and subsequent restart, things have gone smoothly, including a successful cleaning run last night: Dec 2 02:01:12 mail3 postgrey[24320]: cleaning up old logs... Dec 2 02:01:13 mail3 postgrey[24320]: cleaning up old entries... Dec 2 02:01:45 mail3 postgrey[24320]: cleaning main database finished. before: 2273, after: 1316 Dec 2 02:01:47 mail3 postgrey[24320]: cleaning clients database finished. before: 966, after: 725 It's my recommendation to proceed with releasing the fixed version. If anything new should arise, I'll of course report it. -- libdb4.4 in gutsy breaks postgrey and subversion https://bugs.launchpad.net/bugs/153996 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 159472] Re: /etc/cron.daily/find has wrong ionice parameter
This is a dup of 152692 with a more specific title. -- /etc/cron.daily/find has wrong ionice parameter https://bugs.launchpad.net/bugs/159472 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 173489] slocate cron job fails without ioprio_set
Public bug reported: Binary package hint: slocate I have gutsy installed on an openvz virtual machine (from a vps provider). Apparently these VMs do not include the ioprio_set ability, because my slocate cron job fails daily: /etc/cron.daily/slocate: ioprio_set: Operation not permitted I can confirm that the 'ionice' command is effectively useless on this installation, as it pretty much always fails with the above. The cron job needs to find a way around this or else slocate will never be updated without manual intervention. ** Affects: slocate (Ubuntu) Importance: Undecided Status: New -- slocate cron job fails without ioprio_set https://bugs.launchpad.net/bugs/173489 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 153996] Re: libdb4.4 in gutsy breaks postgrey and subversion
Update... One of my two machines running 4.4.20-8.1ubuntu3.1 from gutsy- proposed had another postgrey crash last night. This is the first crash since installing Daniel's db4.4. It would seem that either the proposed package does not fix the issue as well as hoped, or that I've somehow made an error or omission when installing this version. Dec 1 02:21:31 mail3 postgrey[5458]: cleaning up old logs... Dec 1 02:21:31 mail3 postgrey[5458]: cleaning up old entries... Dec 1 02:21:32 mail3 postgrey[5458]: cleaning main database finished. before: 1992, after: 1195 Dec 1 02:21:32 mail3 postgrey[5458]: fatal: Can't call method "txn_commit" on an undefined value at /usr/sbin/postgrey line 223. My other server, also running this release, has not experienced the same problems, but it's also under much less load so perhaps it didn't trigger the same postgrey routines. -- libdb4.4 in gutsy breaks postgrey and subversion https://bugs.launchpad.net/bugs/153996 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 153996] Re: libdb4.4 in gutsy breaks postgrey and subversion
Martin, thanks very much for pushing forward with this fix. My comments are pretty much identical to Jeff Balderson; upgraded from Daniel Haler's release to the gutsy-proposed yesterday and have witnessed no new or recurring problems since. -- libdb4.4 in gutsy breaks postgrey and subversion https://bugs.launchpad.net/bugs/153996 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 172925] postfix upgrade does not add 'retry' service
Public bug reported: Binary package hint: postfix Doing an upgrade from feisty to gusty, postfix gets upgraded from the 2.3.x series to the 2.4.x series. As per the release notes here: ftp://ftp.reverse.net/pub/postfix/official/postfix-2.4.6.RELEASE_NOTES There is a "Major changes - critical" feature added to the 2.4.0 release as follows: -- [Incompat 20061209] The upgrade procedure adds a new "retry" service to the master.cf file. If you make the mistake of copying old Postfix configuration files over the new files, the queue manager may log warnings with: warning: connect to transport retry: Connection refused To fix your master.cf file, use "postfix upgrade-configuration" followed by "postfix reload". -- I discovered after my gutsy upgrade that this feature was *not* added to my master.cf. I don't believe the install procedure gave any warning of this, so it was purely chance that I noticed it in the release notes. Running 'postfix upgrade-configuration' manually did in fact modify my master.cf without causing any problems for my existing config. The upgrade procedure should probably call this function at post-install, or at very minimum, warn the user to run it. ** Affects: postfix (Ubuntu) Importance: Undecided Status: New -- postfix upgrade does not add 'retry' service https://bugs.launchpad.net/bugs/172925 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 153996] Re: libdb4.4 in gutsy breaks postgrey and subversion
Well folks, I've been posting to ubuntu-motu and more recently ubuntu- devel-discuss trying to get some attention for this issue. Clearly it hasn't helped much (except for Daniel building the PPA package for us). I'm really dumbfounded that such a normally progressive distro like Ubuntu is turning a blind eye to high priority breakage. In most cases I wouldn't even take reporting problems out of the bug tracker to mailing lists, but I'm out of ideas. Maybe it's time to consider moving my mail systems back to Debian...? -- libdb4.4 in gutsy breaks postgrey and subversion https://bugs.launchpad.net/bugs/153996 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 163275] dkim-filter docs may have incorrect postfix config
Public bug reported: I'm new to dkim-filter, so hopefully someone with more knowledge can validate this. I've installed the package under gutsy, and am reading /usr/share/doc/dkim-filter/README.Debian.gz Under the section "Notes for Ubuntu specific changes" it is suggested to add milter_macro_daemon_name = SIGNING to main.cf. As I understand it, this macro setting is only meaningful if the dkim- filter daemon is actually watching for macros (the -M flag). As far as I can tell, setting -M in dkim-filter is not done anywhere in ubuntu's package, so adding it to main.cf without also instructing the user to change the default dkim config to include it is pointless. ** Affects: dkim-milter (Ubuntu) Importance: Undecided Status: New -- dkim-filter docs may have incorrect postfix config https://bugs.launchpad.net/bugs/163275 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 163217] thunderbird marks mail as read after a delete
Public bug reported: Binary package hint: thunderbird 2.0.0.8~pre071022+nobinonly-0ubuntu0.7.10 I hate that I can't disable thunderbird marking mail as read, but that's an issue for mozilla to never get around to changing. Anyway, I currently have "Wait 60 seconds before marking messages as read" checked in Advanced>General prefs. (60 is the number I filled in). This seems to work fine when I manually select a message, however if I delete a message, it fails to keep the next message to be selected from being read. - Have 2 unread messages in inbox - Select the newest, hit Delete - Tbird should remove this message, and select and display the next oldest message - The newly selected message is immediately marked as read. Why? No idea. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- thunderbird marks mail as read after a delete https://bugs.launchpad.net/bugs/163217 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 153996] Re: libdb4.4 in gutsy breaks postgrey and subversion
I can also confirm; tested Daniel's PPA version and it's run 48 hours without a crash. First time since the upgrade to gutsy that it's made it over 24 hrs. -- libdb4.4 in gutsy breaks postgrey and subversion https://bugs.launchpad.net/bugs/153996 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 153996] libdb4.4 in gutsy breaks postgrey
Public bug reported: Binary package hint: libdb4.4 libdb4.4 (4.4.20-8.1ubuntu3) in gutsy breaks postgrey severely The postgrey bug for this is here: https://bugs.launchpad.net/ubuntu/+source/postgrey/+bug/135038 Debian developers already determined that this was a problem with libdb4.4, as documented here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441152 ** Affects: db4.4 (Ubuntu) Importance: Undecided Status: New -- libdb4.4 in gutsy breaks postgrey https://bugs.launchpad.net/bugs/153996 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 135038] Re: postgrey fails regularly : "fatal: Can't call method "txn_commit" on an undefined value at /usr/sbin/postgrey line 223."
Why is it taking so long to get a response on this? postgrey is very much broken in gutsy, and Debian already addressed the problem. -- postgrey fails regularly : "fatal: Can't call method "txn_commit" on an undefined value at /usr/sbin/postgrey line 223." https://bugs.launchpad.net/bugs/135038 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 135038] Re: postgrey fails regularly : "fatal: Can't call method "txn_commit" on an undefined value at /usr/sbin/postgrey line 223."
** Changed in: postgrey (Ubuntu) Status: New => Confirmed -- postgrey fails regularly : "fatal: Can't call method "txn_commit" on an undefined value at /usr/sbin/postgrey line 223." https://bugs.launchpad.net/bugs/135038 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 152692] updatedb cron job fails
Public bug reported:
Binary package hint: findutils
I see a couple problems with the /etc/cron.daily/find cron job in the
findutils 4.2.31-1ubuntu2 package (Gutsy RC).
1) There's an extra space in the shebang line (cosmetic)...
#! /bin/sh
2) It's passing a priority to ionice with the -p flag, however according to the
ionice man page, the -p flag specifies a pid. This causes ionice to fail to
run.
cd / && nice -n ${NICE:-10} ionice -c ${IONICE_CLASS:-2} -p
${IONICE_PRIORITY:-7} updatedb
> ioprio_set: No such process
" -p Pass in a process pid to change an already running process. "
** Affects: findutils (Ubuntu)
Importance: Undecided
Status: New
--
updatedb cron job fails
https://bugs.launchpad.net/bugs/152692
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 151850] Re: clamav-milter postfix defaults fail
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=446404 -- clamav-milter postfix defaults fail https://bugs.launchpad.net/bugs/151850 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 151850] Re: clamav-milter postfix defaults fail
There are a couple other issues with the init script that will case it to fail with postfix chroot: - It doesnt give the postfix user any write permissions to the socket (which is dynamically created/destroyed). - There's a race condition where it doesn't wait for the socket file to be created, so the chgrp command actually fails silently. I've made the following modifications which, although not particularly dynamic, make it work properly on my setup: while [ ! -e "$SOCKET_PATH" ]; do sleep 2 done if [ $ret = 0 ] && [ -e "$SOCKET_PATH" ] && [ "$USE_POSTFIX" = 'yes' ]; then chgrp postfix $SOCKET_PATH chmod g+w $SOCKET_PATH fi -- clamav-milter postfix defaults fail https://bugs.launchpad.net/bugs/151850 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 151850] Re: clamav-milter postfix defaults fail
Yes, well my rationale was that if an example is going to be included that one can uncomment and use, it should probably work. :) I can solve the problem fairly simply... I leave the path as suggested, but add an actual socket file name to it: SOCKET=local:/var/spool/postfix/clamav/clamav.ctl I then manually create the clamav directory (as root). My current working system has the clamav dir, plus the socket, owned by clamav and in the postfix group, mode 775. This should be fairly trivial to do with the new init script since it already has a variable specifying postfix. -- clamav-milter postfix defaults fail https://bugs.launchpad.net/bugs/151850 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 151850] clamav-milter postfix defaults fail
Public bug reported: Binary package hint: clamav-milter Testing clamav-milter in Gutsy, 0.91.2-3ubuntu1. The default socket given for postfix is SOCKET=local:/var/spool/postfix/clamav/ (in /etc/defaults/clamav-milter). First of all, this seems weird since it's a directory and not a file name. Regardless, milter startup fails: local:/var/spool/postfix/clamav/: No such file or directory LibClamAV Error: Can't open/create local:/var/spool/postfix/clamav/ Fri Oct 12 01:19:47 2007 -> Stopping ClamAV version 0.91.2, clamav-milter version 0.91.2 Fri Oct 12 01:27:21 2007 -> ClamAV-milter started at Fri Oct 12 01:27:21 2007 What's additionally annoying is that the init script returns OK, even though the daemon didn't start properly. Another point is that the milter init script tries to rm -f the socket file at one point, which fails since the file here is a directory. Even if one changes the directory to a filename (remove the trailing slash), creation still fails with permission denied. Fri Oct 12 01:28:06 2007 -> ClamAV-milter started at Fri Oct 12 01:28:06 2007 local:/var/spool/postfix/clamav: Permission denied LibClamAV Error: Can't open/create local:/var/spool/postfix/clamav Fri Oct 12 01:28:06 2007 -> Stopping ClamAV version 0.91.2, clamav-milter version 0.91.2 ** Affects: clamav (Ubuntu) Importance: Undecided Status: New -- clamav-milter postfix defaults fail https://bugs.launchpad.net/bugs/151850 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 119878] Re: [apport] package smartmontools failed to install/upgrade:
What's the status of this? I ran into the same issue upgrading to gutsy... -- [apport] package smartmontools failed to install/upgrade: https://bugs.launchpad.net/bugs/119878 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 133923] Re: clamav-freshclam cannot save pid
Good to hear it's fixed, however I have an issue with the workaround. I don't know the details of the implementation of /var/run, however it appears to be cleared at reboot. I've already tried to create the directory, but the daemons wind up dying whenever the machine restarts because the directory goes away. I also tried setting them to use the top-level of /var/run, however the permissions don't seem to allow it. -- clamav-freshclam cannot save pid https://bugs.launchpad.net/bugs/133923 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 133924] clamav-milter cannot save pid
Public bug reported: Binary package hint: clamav-milter In a default install of clamav-milter, the init script tries to place the PID file for the milter daemon in /var/run/clamav (/var/run/clamav /clamav-milter.pid), however without clamav-daemon running, the directory is never created, and storing the PID file fails. This causes the daemon to fail to start up: /var/run/clamav: No such file or directory ERROR: Can't save PID in file /var/run/clamav/clamav-milter.pid Stopping ClamAV version 0.90.2, clamav-milter version 0.90.2 /var/run/clamav/clamav-milter.pid: No such file or directory The init script should check for the directory and create it if it does not exist. clamav-milter0.90.2-0ubuntu1 ** Affects: clamav (Ubuntu) Importance: Undecided Status: New -- clamav-milter cannot save pid https://bugs.launchpad.net/bugs/133924 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 133923] clamav-freshclam cannot save pid
Public bug reported: Binary package hint: clamav-freshclam In a default install of clamav-freshclam, /etc/clamav/freshclam.conf tries to place the PID file for the freshclam daemon in /var/run/clamav, however without clamav-daemon running, the directory is never created, and storing the PID file fails. The freshclam package should check for the directory and create it if it does not exist. /etc/clamav/freshclam.conf: PidFile /var/run/clamav/freshclam.pid clamav-freshclam 0.90.2-0ubuntu1 ** Affects: clamav (Ubuntu) Importance: Undecided Status: New -- clamav-freshclam cannot save pid https://bugs.launchpad.net/bugs/133923 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 121823] Outdated option in relay entry for master.cf
Public bug reported: Binary package hint: postfix The fallback_relay parameter was renamed to smtp_fallback_relay in Postfix 2.3. The relay entry in master.cf was not updated to match (-o fallback_relay=), and as a result, routing loops can occur. This is explained in full here: http://groups.google.com/group/list.postfix.users/browse_thread/thread/c265c7dedb795065/cb6b8112ac23b69a ** Affects: postfix (Ubuntu) Importance: Undecided Status: New -- Outdated option in relay entry for master.cf https://bugs.launchpad.net/bugs/121823 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 121823] Re: Outdated option in relay entry for master.cf
A simple corrective patch is attached. It has also been submitted to the postfix-devel list for consideration. ** Attachment added: "C:\Documents and Settings\Administrator\Desktop\master.cf.diff" http://launchpadlibrarian.net/8169916/C%3A%5CDocuments%20and%20Settings%5CAdministrator%5CDesktop%5Cmaster.cf.diff -- Outdated option in relay entry for master.cf https://bugs.launchpad.net/bugs/121823 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 106802] Re: installer allows raid0 on /boot
Saying Raid works is ambiguous; I know for example that Raid 1 works. It's raid 0 that's not working, and I'm not seeing any immediate documentation that suggests otherwise. Can you point to some? -- installer allows raid0 on /boot https://bugs.launchpad.net/bugs/106802 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 78552] Re: /sbin/update-grub complains about being run instead of /usr/sbin/update-grub
The update-grub man page gives the depricated location of /sbin/update- grub. I reported this in bug #107741, but someone felt this was a duplicate, despite the fact that there is no mention of man pages in this bug. The section in question: ## The update-grub script can be ran automagically from the /etc/kernel-img.conf file by adding the following lines: postinst_hook = /sbin/update-grub postrm_hook = /sbin/update-grub ## -- /sbin/update-grub complains about being run instead of /usr/sbin/update-grub https://bugs.launchpad.net/bugs/78552 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 107741] Re: update-grub manpage uses /sbin rather than /usr/sbin
*** This bug is a duplicate of bug 78552 *** https://bugs.launchpad.net/bugs/78552 bug #78552 makes no mention of man pages, and is a lousy duplicate for this bug -- update-grub manpage uses /sbin rather than /usr/sbin https://bugs.launchpad.net/bugs/107741 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 107741] update-grub manpage uses /sbin rather than /usr/sbin
Public bug reported: Binary package hint: grub Just upgraded to feisty and I see /sbin/update-grub is now depricated in favor of /usr/sbin/update-grub. Unfortunately the update-grub manpage still reads: ## The update-grub script can be ran automagically from the /etc/kernel-img.conf file by adding the following lines: postinst_hook = /sbin/update-grub postrm_hook = /sbin/update-grub ## Obviously the location should be changed to reflect the new location. ** Affects: grub (Ubuntu) Importance: Undecided Status: Unconfirmed -- update-grub manpage uses /sbin rather than /usr/sbin https://bugs.launchpad.net/bugs/107741 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 106802] installer allows raid0 on /boot
Public bug reported: I downloaded the alternate cd for 7.04 (http://releases.ubuntu.com/7.04/ubuntu-7.04-beta-alternate-i386.iso) to mess around with the installer. One issue that occurred to me was that it would allow the user to assign /boot to a RAID0 array. This works grandly, right up until you get to the grub-install phase. grub and lilo both fail to install at this point, and the installation is wasted. AFAIK, booting from a raid0 partition created by the installer just isn't possible. It seems fairly trivial logically (without knowing the code behind the installer) that it should be able to check if the current partition is raid0 when trying to assign /boot, and disallow it. This might save some people a bit of confusion and wasted time later on. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- installer allows raid0 on /boot https://bugs.launchpad.net/bugs/106802 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 100019] Re: Segfault in Samba
Well, I seem to have found the problem in the process of gathering the requested info. The smb.conf had been set to eth0, when in the new motherboard, the NIC comes up as eth1. This still has to be a bug; I dont think a segfault is the desired behavior if an interface becomes unavailable, but suffice it to say fixing the interface config has fixed the crashing. -- Segfault in Samba https://bugs.launchpad.net/bugs/100019 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 100019] Segfault in Samba
Public bug reported:
Binary package hint: samba
nmbd has been repeatedly crashing since I upgraded my motherboard and
processor hardware (from a 32 bit duron to a 64 bit sempron). This is
the only error I've encountered following the upgrade, so I don't think
it's the fault of the hardware. The following is the crash output from
one such crash:
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for pid 5988 (/usr/sbin/nmbd).
Below is a backtrace for this process generated with gdb, which shows
the state of the program at the time the error occurred.
If the problem persists, you are encouraged to first install the
samba-dbg package which contains the debugging symbols for samba
binaries. Then, submit the provided information as a bug report to Ubuntu.
For information about the procedure for submitting bug reports, please
see http://www.ubuntulinux.org/support/bugs/document_view
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1212098288 (LWP 5988)]
0xe410 in __kernel_vsyscall ()
#0 0xe410 in __kernel_vsyscall ()
#1 0xb7dae6a3 in waitpid () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7d56281 in strtold_l () from /lib/tls/i686/cmov/libc.so.6
#3 0x080d4b28 in smb_panic2 (why=0x8114018 "internal error",
decrement_pid_count=1) at lib/util.c:1545
#4 0x080d4c59 in smb_panic (why=0x8114018 "internal error") at lib/util.c:1506
#5 0x080c17ac in sig_fault (sig=11) at lib/fault.c:42
#6
#7 find_workgroup_on_subnet (subrec=0x0, name=0x8136458 "WORKGROUP")
at nmbd/nmbd_workgroupdb.c:177
#8 0x08076327 in write_browse_list (t=0, force_write=1)
at nmbd/nmbd_serverlistdb.c:350
#9 0x0806261e in msg_reload_nmbd_services (msg_type=3001, src={pid = 0},
buf=0xbfa72ee0, len=0) at nmbd/nmbd.c:314
#10 0x08062e88 in main (argc=) at nmbd/nmbd.c:597
** Affects: samba (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Segfault in Samba
https://launchpad.net/bugs/100019
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 100018] bug reporting link is panic-action script is broken
Public bug reported: Binary package hint: samba-common The script /usr/share/samba/panic-action is included in the samba-common package (version 3.0.22-1ubuntu4.1 here). When this script is run, the resulting output includes a link to http://www.ubuntulinux.org/support/bugs/document_view for filing bug reports. This link is broken and results in a "page not found" error on the website. ** Affects: samba (Ubuntu) Importance: Undecided Status: Unconfirmed -- bug reporting link is panic-action script is broken https://launchpad.net/bugs/100018 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78008] Re: Typo in installer partitioning
I'm attaching a diff that fixes this typo as well as another in that line (commiting -> committing). I reworded the whole line to make it sound like more fluent english. ** Attachment added: "fix two typos, rephrase for better english" http://librarian.launchpad.net/6899056/qtparted.diff -- Typo in installer partitioning https://launchpad.net/bugs/78008 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 93972] Re: "BSDBSD" typo in portmap.8
Patch to portmap.8 manpage is attached. ** Attachment added: "fix for typo" http://librarian.launchpad.net/6872327/C%3A%5CDocuments%20and%20Settings%5CAdministrator%5CDesktop%5Cportmap.8.diff -- "BSDBSD" typo in portmap.8 https://launchpad.net/bugs/93972 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 93972] "BSDBSD" typo in portmap.8
Public bug reported: Binary package hint: portmap man portmap shows this at the bottom: HISTORY The portmap command appeared in BSDBSD 4.3 ** Affects: portmap (Ubuntu) Importance: Undecided Status: Unconfirmed -- "BSDBSD" typo in portmap.8 https://launchpad.net/bugs/93972 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780] Re: apt-spy does not have ubuntu mirror listing
Open https://launchpad.net/ubuntu/+archivemirrors in FireFox. Right Click>View Page Info>Links>Ctrl+A>Ctrl+C vim /tmp/links [paste from clipboard] sed -i -e '/canonical/d' /tmp/links -e '/launchpad/d' /tmp/links -- apt-spy does not have ubuntu mirror listing https://launchpad.net/bugs/1780 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
