Bug#618660: dovecot-imapd: imapd starts too early at boot on host with IPv4 and IPv6.
Hello Marco, The host with the issue has static IPv4 + IPv6. /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet static address 172.20.1.8 netmask 255.255.255.0 network 172.20.1.0 broadcast 172.20.1.255 gateway 172.20.1.2 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 172.20.1.2 dns-search home.elysium-os.nl iface eth0 inet6 static address 2001:610:779::8 netmask 64 gateway 2001:610:779::2 An other host provides the IPv6 connectivity with the internet using SixXS. ( www.sixxs.net ) Kind regards, Marcel On 27 Mar 2011, at 23:00, Marco Nenciarini wrote: On 17/03/2011 12:17, Marcel Koopmans wrote: Package: dovecot-imapd Version: 1:1.2.15-4 Severity: important Tags: ipv6 It seems that dovecot starts while IPv6 is not configured yet at boot time. Logging: Mar 17 11:47:00 styx dovecot: bind(2001:610:779::8, 143) failed: Cannot assign requested address Mar 17 11:47:00 styx dovecot: Fatal: listen(2001:610:779::8, 143) failed: Cannot assign requested address I can manually start dovecot-imapd without an issue a few seconds later. Which kind of IPv6 connectivity do you have? Regards, Marco -- - |Marco Nenciarini| Debian/GNU Linux Developer - Plug Member | | mnen...@prato.linux.it | http://www.prato.linux.it/~mnencia | - Key fingerprint = FED9 69C7 9E67 21F5 7D95 5270 6864 730D F095 E5E4 Marcel Koopmans Elysium Open Systems Wijdstraat 23 3421AJ Oudewater Tel:0348-560210 GSM:06-51174110 email: marcel.koopm...@elysium-os.nl -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#618660: dovecot-imapd: imapd starts too early at boot on host with IPv4 and IPv6.
Package: dovecot-imapd Version: 1:1.2.15-4 Severity: important Tags: ipv6 It seems that dovecot starts while IPv6 is not configured yet at boot time. Logging: Mar 17 11:47:00 styx dovecot: bind(2001:610:779::8, 143) failed: Cannot assign requested address Mar 17 11:47:00 styx dovecot: Fatal: listen(2001:610:779::8, 143) failed: Cannot assign requested address I can manually start dovecot-imapd without an issue a few seconds later. -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dovecot-imapd depends on: ii dovecot-common 1:1.2.15-4 secure mail server that supports m ii libc6 2.11.2-10Embedded GNU C Library: Shared lib ii libldap-2.4-2 2.4.23-7 OpenLDAP libraries ii libssl0.9.8 0.9.8o-4squeeze1 SSL shared libraries dovecot-imapd recommends no packages. dovecot-imapd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548156: grub-installer: No grub2 when using gpt partition schema
Hello Felix, Thanks for the quick reply. --- Why I think GRUB Legacy was chossen... # dpkg -l | grep grub ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy version) ii grub-common 1.96+20080724-16 GRand Unified Bootloader, version 2 (common files) part from /var/log/apt/term.log Log started: 2009-09-24 11:23:26 Selecting previously deselected package grub-common. (Reading database ... 12091 files and directories currently installed.) Unpacking grub-common (from .../grub-common_1.96+20080724-16_amd64.deb) ... Selecting previously deselected package grub. Unpacking grub (from .../grub_0.97-47lenny2_amd64.deb) ... Processing triggers for man-db ... Setting up grub-common (1.96+20080724-16) ... Setting up grub (0.97-47lenny2) ... Log ended: 2009-09-24 11:23:27 --- You are right about the disk size 2 TiB, we passed the 2 GiB a little while ago. --- I'll try again creating the Reserved BIOS boot area. With kind regards, Marcel Felix Zielcke wrote: Am Donnerstag, den 24.09.2009, 10:05 +0200 schrieb Marcel D.A. Koopmans: Package: grub-installer Severity: important I use 2 disks with GPT partition schemes On those I create 2 RAID-1 partitions RAID #1 ( mirror ) contains /boot RAID #2 ( mirror ) contains LVM with other partitions Using these settings no longer gives me the option of selecting GRUB2 - this is the real bug If your /boot is on GPT you got never asked that question, because GRUB Legacy just doestn't support it. So this isn't at all a bug. By the way GRUB 2 is now the default for everyone, though that question should still be asked in expert mode and if GRUB Legacy can handle /boot. And GRUB Legacy fails as it cannot handle /boot on mdadm with gpt partition schemes. Why do you think GRUB Legacy was choosen by grub-installer? The syslog would be useful, escpecially the grub-installer part. I thing this is an important bug as we soon have 2 gibibyte disks and the default msdos partition scheme cannot address those! You mean 2 TiB, not 2 GiB. If you use GPT you must create on all disks where your /boot is, a `Reserved BIOS boot area', then shown as biosgrub. A few MiBs are enough. They don't need to be all exactly the same size and they don't need to be at the same sectors on the disks. And you must create the RAID over a partition not over the whole disk, even with msdos partition scheme. I just tried it myself with todays amd64 businesscard. 100 MiB for biosgrub, rest for RAID 1 for an ext4 / It installed fine, though grub-installer still used `grub-install (hd0)' instead of (md0) attachment: marcel_koopmans.vcf
Bug#350260: Please remove this bug report
Dear Nagios maintainer group, This bug report can be removed. The extended host information is stored in the database not in the file. This was a misunderstanding on my part. with kind regards, Marcel Marcel Koopmans Elysium Open Systems begin:vcard fn:Marcel Koopmans n:Koopmans;Marcel org:Elysium Open Systems adr:;;Palmstraat 42;Heerlen;;6413 RC;the Netherlands email;internet:[EMAIL PROTECTED] tel;work:+31 (0)45-52223213 x-mozilla-html:FALSE url:http://www.elysium-os.nl version:2.1 end:vcard
Bug#350260: Nagios extented host info
Package:nagios-pgsql Version:1.3-cvs.20050402-2.sarge.1 It seems that nagios-pqsql is compiled without the --with-template-extinfo flag. Due to this I cannot set many options within Nagios. Looking at the compilation report I see that the plain text storage version does have it set. The mysql version also seems to have this flag missing. Debian version : 3.1 with kind regards, Marcel Marcel Koopmans Elysium Open Systems begin:vcard fn:Marcel Koopmans n:Koopmans;Marcel org:Elysium Open Systems adr:;;Palmstraat 42;Heerlen;;6413 RC;the Netherlands email;internet:[EMAIL PROTECTED] tel;work:+31 (0)45-52223213 x-mozilla-html:FALSE url:http://www.elysium-os.nl version:2.1 end:vcard
Bug#326928: Incorrect spelling in name
Package: libccid Version: 0.9.3-1 in file /usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Info.plist KANN mIDentity should be KAAN mIDentity with kind regards, Marcel Marcel Koopmans Elysium Open Systems -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
