Bug#697612: exim4-daemon-light: "MAIN_LOCAL_DOMAINS=@:localhost" seems not to respect "@"
Hi Marc, This is getting even more strange. In short: the wrong behaviour disappeared, and it seems I'm not able to reproduce the bug anymore. I left the office after my last email, and come back this morning. Follows detailed explanation. From: "Marc Haber" I am kind of out of ideas now. Can you dump the output of echo foo | /usr/sbin/exim -d root@devil... here after looking for private data in the debug output? I am still running with Osamu Aoki's workaround (dc_other_hostnames='devilserver.deviltechnologies.com' in update-exim4.conf.conf). [WORKAROUND ON] I executed the command, dumped the output and received the email message. The details are in "tests_with-workaround.tbz", attached. So I removed the workaround, executed update-exim4.conf, restarted exim, and executed echo bar | /usr/sbin/exim -d root@devil The details are in "tests_without-workaround.tbz", attached. To my surprise, now all is working as expected! The message does not get sent to the smarthost. root@devilserver:/etc/exim4# exim -v -bt r...@devilserver.deviltechnologies.com - R: system_aliases for r...@devilserver.deviltechnologies.com R: system_aliases for dgue...@devilserver.deviltechnologies.com R: userforward for dgue...@devilserver.deviltechnologies.com R: procmail for dgue...@devilserver.deviltechnologies.com dgue...@devilserver.deviltechnologies.com <-- r...@devilserver.deviltechnologies.com router = procmail, transport = procmail_pipe - So, I looked around and found that the router rebooted itself during the weekend. I started thinking of a DNS issue, so I tried to reproduce by generating a DNS problem in the network: - root@devilserver:/etc/bind# service bind9 stop Stopping domain name service...: bind9 waiting for pid 1437 to die. root@devilserver:/etc/bind# dig devilserver.deviltechnologies.com ; <<>> DiG 9.7.3 <<>> devilserver.deviltechnologies.com ;; global options: +cmd ;; connection timed out; no servers could be reached root@devilserver:/etc/bind# exim -v -bt r...@devilserver.deviltechnologies.com R: system_aliases for r...@devilserver.deviltechnologies.com R: system_aliases for dgue...@devilserver.deviltechnologies.com R: userforward for dgue...@devilserver.deviltechnologies.com R: procmail for dgue...@devilserver.deviltechnologies.com dgue...@devilserver.deviltechnologies.com <-- r...@devilserver.deviltechnologies.com router = procmail, transport = procmail_pipe root@devilserver:/etc/bind# service exim4 stop Stopping MTA: exim4_listener. root@devilserver:/etc/bind# service exim4 start Starting MTA: exim4. root@devilserver:/etc/bind# exim -v -bt r...@devilserver.deviltechnologies.com R: system_aliases for r...@devilserver.deviltechnologies.com R: system_aliases for dgue...@devilserver.deviltechnologies.com R: userforward for dgue...@devilserver.deviltechnologies.com R: procmail for dgue...@devilserver.deviltechnologies.com dgue...@devilserver.deviltechnologies.com <-- r...@devilserver.deviltechnologies.com router = procmail, transport = procmail_pipe root@devilserver:/etc/bind# - ??? It seems exim does not try to forward the mail to the smarthost, even without a DNS reply!! Now, I purposefully misconfigured the local DNS server (bind). It is in forward-only configuration; all the requests are forwarded to the router. I entered a wrong IP address in /etc/bind/named.conf.options, then started bind: - root@devilserver:/etc/bind# service bind9 start Starting domain name service...: bind9. root@devilserver:/etc/bind# dig devilserver.deviltechnologies.com ; <<>> DiG 9.7.3 <<>> devilserver.deviltechnologies.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39461 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;devilserver.deviltechnologies.com. IN A ;; ANSWER SECTION: devilserver.deviltechnologies.com. 86400 IN A 192.168.200.249 ;; AUTHORITY SECTION: devilserver.deviltechnologies.com. 86400 IN NS devilserver.deviltechnologies.com. ;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Mon Apr 28 09:37:53 2014 ;; MSG SIZE rcvd: 81 root@devilserver:/etc/bind# exim -v -bt r...@devilserver.deviltechnologies.com R: system_aliases for r...@devilserver.deviltechnologies.com R: system_aliases for dgue...@devilserver.deviltechnologies.com R: userforward for dgue...@devilserver.deviltechnologies.com R: procmail for dgue...@devilserver.deviltechnologies.com dgue...@devilserver.deviltechnologies.com <-- r...@devilserver.deviltechnologies.com router = procmail, transport = procmail_pipe root@devilserver:/etc/bind# - Still, working as expected. I am now running with a correct DNS server configuration, and with a correct exim configuration (the same that worked since some years). Now I'm out of ideas, too. Greetings Marc Thanks, Diego tests_without-workaround.tbz Description: Binary data tests_with-workaround.tbz Description: Bin
Bug#697612: exim4-daemon-light: "MAIN_LOCAL_DOMAINS=@:localhost" seems not to respect "@"
- Original Message - From: "Marc Haber" To: "Diego Guella" Cc: <697...@bugs.debian.org>; Sent: Thursday, April 24, 2014 4:47 PM Subject: Re: Bug#697612: exim4-daemon-light: "MAIN_LOCAL_DOMAINS=@:localhost" seems not to respect "@" On Thu, Apr 24, 2014 at 03:27:56PM +0200, Diego Guella wrote: devilserver.deviltechnologies.com. 86400 IN A 192.168.200.249 and 192.168.200.249 is configured as an IP on the local system? Affirmative, sorry to not have dumped information about that: root@devilserver:~# ifconfig -a - eth0 Link encap:Ethernet HWaddr 00:1e:8c:9a:7e:53 inet addr:192.168.200.249 Bcast:192.168.255.255 Mask:255.255.0.0 inet6 addr: fe80::21e:8cff:fe9a:7e53/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3667708 errors:0 dropped:0 overruns:0 frame:0 TX packets:2007886 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2702308765 (2.5 GiB) TX bytes:3549001448 (3.3 GiB) Interrupt:18 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:181856 errors:0 dropped:0 overruns:0 frame:0 TX packets:181856 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:20325408 (19.3 MiB) TX bytes:20325408 (19.3 MiB) - root@devilserver:~# cat /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 192.168.200.249 netmask 255.255.0.0 network 192.168.0.0 broadcast 192.168.255.255 gateway 192.168.200.254 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 192.168.200.254 dns-search deviltechnologies.com - I note now that "dns-nameservers" points to another DNS server (the router). But this has definitely never, ever changed for the life of this Debian installation (some years) Greetings Marc Thanks, Diego -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697612: exim4-daemon-light: "MAIN_LOCAL_DOMAINS=@:localhost" seems not to respect "@"
Hi Marc, and thanks for your reply. Please find my answers inline. - Original Message - From: "Marc Haber" To: "Diego Guella" ; <697...@bugs.debian.org> Cc: Sent: Thursday, April 24, 2014 2:32 PM Subject: Re: Bug#697612: exim4-daemon-light: "MAIN_LOCAL_DOMAINS=@:localhost" seems not to respect "@" Thanks for the comprehensive report. What do your logs say with regard to 1Wcool-0001JR-Kw? root@devilserver:/var/log/exim4# cat mainlog.1 | grep 1Wcool-0001JR-Kw - 2014-04-23 06:29:56 1Wcool-0001JR-Kw <= <> H=2.ip-46-105-16.eu (vps26197.ovh.net) [46.105.16.2] P=esmtp S=7687 id=E1WcooT-0001Hx-3t@devilserver 2014-04-23 06:29:56 1Wcool-0001JR-Kw ** postmas...@devilserver.deviltechnologies.com: Too many "Received" headers - suspected mail loop 2014-04-23 06:29:56 1Wcoom-0001JU-1x <= <> R=1Wcool-0001JR-Kw U=Debian-exim P=local S=667 2014-04-23 06:29:56 1Wcool-0001JR-Kw Frozen (delivery error message) 2014-04-23 06:30:05 1Wcool-0001JR-Kw Message is frozen 2014-04-23 07:00:05 1Wcool-0001JR-Kw Message is frozen 2014-04-23 07:30:05 1Wcool-0001JR-Kw Message is frozen 2014-04-23 07:54:54 1Wcool-0001JR-Kw Message is frozen 2014-04-23 08:24:53 1Wcool-0001JR-Kw Message is frozen 2014-04-23 08:29:42 1Wcool-0001JR-Kw Unfrozen by forced delivery 2014-04-23 08:29:42 1Wcool-0001JR-Kw ** postmas...@devilserver.deviltechnologies.com: Too many "Received" headers - suspected mail loop 2014-04-23 08:29:43 1Wcqgg-0001A1-Pz <= <> R=1Wcool-0001JR-Kw U=Debian-exim P=local S=667 2014-04-23 08:29:43 1Wcool-0001JR-Kw Frozen (delivery error message) 2014-04-23 08:43:53 1Wcool-0001JR-Kw Unfrozen by forced delivery 2014-04-23 08:43:53 1Wcool-0001JR-Kw cancelled by root 2014-04-23 08:43:53 1Wcool-0001JR-Kw Completed - From 08:29:42 on, there are my manual actions to purge the mail queue (this was not the only message frozen, there were 50 or so). In particular, this is where all started (my 2 daily messages from mdadm): root@devilserver:/var/log/exim4# cat mainlog.1 | head -n 25 - 2014-04-23 06:25:06 1Wcok6-pP-1B <= r...@devilserver.deviltechnologies.com U=root P=local S=1031 2014-04-23 06:25:06 1Wcok6-pS-Bo <= r...@devilserver.deviltechnologies.com U=root P=local S=1031 2014-04-23 06:25:07 1Wcok6-pP-1B => r...@devilserver.deviltechnologies.com R=smarthost T=remote_smtp_smarthost H=vps26197.ovh.net [46.105.16.2] X=TLS1.0:RSA_AES_256_CBC_SHA1:32 DN="C=IT,ST=Brescia,L=Rovato,O=Devil Technologies,CN=vps26197.ovh.net,EMAIL=i...@deviltechnologies.com" 2014-04-23 06:25:07 1Wcok6-pP-1B Completed 2014-04-23 06:25:07 1Wcok6-pS-Bo => r...@devilserver.deviltechnologies.com R=smarthost T=remote_smtp_smarthost H=vps26197.ovh.net [46.105.16.2] X=TLS1.0:RSA_AES_256_CBC_SHA1:32 DN="C=IT,ST=Brescia,L=Rovato,O=Devil Technologies,CN=vps26197.ovh.net,EMAIL=i...@deviltechnologies.com" 2014-04-23 06:25:07 1Wcok6-pS-Bo Completed 2014-04-23 06:25:08 1Wcok7-pc-LS <= r...@devilserver.deviltechnologies.com H=2.ip-46-105-16.eu (vps26197.ovh.net) [46.105.16.2] P=esmtp S=1545 id=E1Wcok6-pS-Bo@devilserver 2014-04-23 06:25:08 1Wcok7-pb-LS <= r...@devilserver.deviltechnologies.com H=2.ip-46-105-16.eu (vps26197.ovh.net) [46.105.16.2] P=esmtp S=1545 id=E1Wcok6-pP-1B@devilserver 2014-04-23 06:25:08 1Wcok7-pc-LS => r...@devilserver.deviltechnologies.com R=smarthost T=remote_smtp_smarthost H=vps26197.ovh.net [46.105.16.2] X=TLS1.0:RSA_AES_256_CBC_SHA1:32 DN="C=IT,ST=Brescia,L=Rovato,O=Devil Technologies,CN=vps26197.ovh.net,EMAIL=i...@deviltechnologies.com" 2014-04-23 06:25:09 1Wcok7-pc-LS Completed 2014-04-23 06:25:09 1Wcok7-pb-LS => r...@devilserver.deviltechnologies.com R=smarthost T=remote_smtp_smarthost H=vps26197.ovh.net [46.105.16.2] X=TLS1.0:RSA_AES_256_CBC_SHA1:32 DN="C=IT,ST=Brescia,L=Rovato,O=Devil Technologies,CN=vps26197.ovh.net,EMAIL=i...@deviltechnologies.com" 2014-04-23 06:25:09 1Wcok7-pb-LS Completed 2014-04-23 06:25:09 1Wcok8-ph-O5 <= r...@devilserver.deviltechnologies.com H=2.ip-46-105-16.eu (vps26197.ovh.net) [46.105.16.2] P=esmtp S=2059 id=E1Wcok6-pS-Bo@devilserver 2014-04-23 06:25:09 1Wcok8-pi-Oz <= r...@devilserver.deviltechnologies.com H=2.ip-46-105-16.eu (vps26197.ovh.net) [46.105.16.2] P=esmtp S=2059 id=E1Wcok6-pP-1B@devilserver 2014-04-23 06:25:10 1Wcok8-ph-O5 => r...@devilserver.deviltechnologies.com R=smarthost T=remote_smtp_smarthost H=vps26197.ovh.net [46.105.16.2] X=TLS1.0:RSA_AES_256_CBC_SHA1:32 DN="C=IT,ST=Brescia,L=Rovato,O=Devil Technologies,CN=vps26197.ovh.net,EMAIL=i...@deviltechnologies.com" 2014-04-23 06:25:10 1Wcok8-ph-O5 Completed 2014-04-23 06:25:10 1Wcok8-pi-Oz => r...@devilserver.deviltechnologies.com R=smarthost T=remote_smtp_smarthost H=vps26197.ovh.net [46.105.16.2] X=TLS1.0:RSA_AES_256_
Bug#697612: exim4-daemon-light: "MAIN_LOCAL_DOMAINS=@:localhost" seems not to respect "@"
Package: exim4-daemon-light Version: 4.72-6+squeeze3 Same problem here. The bad news is, this happened from today, with no configuration changes (that I know of) on the server. The server is in production. Local mails to root@localhost and user@localhost are delivered locally without problems, but local mails to r...@devilserver.deviltechnologies.com does get sent to the smarthost. The server configuration is some years old, and it worked perfectly until yesterday! (I get a daily mail from mdadm at 06:25 local time) Today, I found that the mail was bounced and bounced again from my server and the smarthost, and then my server stopped trying, sending this error email message: - Message 1Wcool-0001JR-Kw has been frozen (delivery error message). The sender is <>. The following address(es) have yet to be delivered: postmas...@devilserver.deviltechnologies.com: Too many "Received" headers - suspected mail loop - update-exim4.conf.conf: - dc_eximconfig_configtype='smarthost' dc_other_hostnames='' dc_local_interfaces='' dc_readhost='' dc_relay_domains='' dc_minimaldns='false' dc_relay_nets='' dc_smarthost='vps26197.ovh.net' CFILEMODE='644' dc_use_split_config='false' dc_hide_mailname='false' dc_mailname_in_oh='true' dc_localdelivery='maildir_home' - Some other information: - root@devilserver:/etc/exim4# uname -n devilserver root@devilserver:/etc/exim4# hostname devilserver root@devilserver:/etc/exim4# hostname -f devilserver.deviltechnologies.com root@devilserver:/etc/exim4# grep -v ^# /etc/hosts 127.0.0.1 localhost 192.168.200.249 devilserver.deviltechnologies.com devilserver ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters - I have BIND installed, version 1:9.7.3.dfsg-1~squeeze11 I tried Osamu Aoki's workaround (dc_other_hostnames='devilserver.deviltechnologies.com') and it fixes the problem for me, too. I assume there is some deeply hidden misconfiguration of something other than exim on my server, or in my network. Again, this setup has worked fine for some years. I have a backup of the server configuration of some months ago, and I can double-check for changes in the configuration files. Do somebody know where can I look at? Thanks, Diego -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#698118: asterisk: version 1:1.6.2.9-2+squeeze9 crashes on SIP call, +squeeze6 does not
Package: asterisk Version: 1:1.6.2.9-2+squeeze9 Severity: grave Justification: renders package unusable I have a production, fully working asterisk server. I use many Siemens C470IP cordless phones on the office, they are SIP peers in my asterisk installation. I had "asterisk" and "asterisk-config" version 1:1.6.2.9-2+squeeze6 installed, and all was working nicely. Today, I updated to 1.6.2.9-2+squeeze9 and found out that asterisk seems working, but as soon as I do a SIP call with the cordless, asterisk crashes suddenly. I reverted to 1.6.2.9-2+squeeze6 since this is a production asterisk and I can't have downtimes. This is Debian Stable! A package should not break like this :( Cheers, Diego Guella -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages asterisk depends on: ii adduser3.112+nmu2add and remove users and groups ii asterisk-config1:1.6.2.9-2+squeeze9 Configuration files for Asterisk ii asterisk-core-soun 1.4.19-1 asterisk PBX sound files - English ii dahdi 1:2.2.1.1-1 utilities for using the DAHDI kern ii libasound2 1.0.23-2.1shared library for ALSA applicatio ii libc-client2007e 8:2007e~dfsg-3.1 c-client library for mail protocol ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libcap21:2.19-3 support for getting/setting POSIX. ii libcurl3 7.21.0-2.1+squeeze2 Multi-protocol file transfer libra ii libgcc11:4.4.5-8 GCC support library ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libgmime-2.0-2a2.2.25-2 MIME library ii libgsm11.0.13-3 Shared libraries for GSM speech co ii libiksemel31.2-4 C library for the Jabber IM platfo ii libjack-jackd2-0 [ 1.9.6~dfsg.1-2JACK Audio Connection Kit (librari ii libldap-2.4-2 2.4.23-7.2OpenLDAP libraries ii liblua5.1-05.1.4-5 Simple, extensible, embeddable pro ii libncurses55.7+20100313-5shared libraries for terminal hand ii libnewt0.520.52.11-1 Not Erik's Windowing Toolkit - tex ii libogg01.2.0~dfsg-1 Ogg bitstream library ii libopenais31.1.2-2 Standards-based cluster framework ii libopenr2-31.3.0-2 MFC/R2 (telephony) call setup libr ii libpopt0 1.16-1lib for parsing cmdline parameters ii libpq5 8.4.13-0squeeze1 PostgreSQL C client library ii libpri1.4 1.4.11.3-1Primary Rate ISDN specification li ii libradiusclient-ng 0.5.6-1.1 Enhanced RADIUS client library ii libresample1 0.1.3-3 real-time audio resampling library ii libsdl1.2debian1.2.14-6.1Simple DirectMedia Layer ii libsnmp15 5.4.3~dfsg-2 SNMP (Simple Network Management Pr ii libspandsp20.0.6~pre12-1 Telephony signal processing librar ii libspeex1 1.2~rc1-1 The Speex codec runtime library ii libspeexdsp1 1.2~rc1-1 The Speex extended runtime library ii libsqlite0 2.8.17-6 SQLite shared library ii libss7-1 1.0.2-1 Signalling System 7 (ss7) library ii libssl0.9.80.9.8o-4squeeze13 SSL shared libraries ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii libsybdb5 0.82-7libraries for connecting to MS SQL ii libtiff4 3.9.4-5+squeeze8 Tag Image File Format (TIFF) libra ii libtonezone2.0 1:2.2.1.1-1 tonezone library (runtime) ii libvorbis0a1.3.1-1+squeeze1 The Vorbis General Audio Compressi ii libvorbisenc2 1.3.1-1+squeeze1 The Vorbis General Audio Compressi ii libvpb04.2.52-2 Voicetronix telephony hardware use ii libx11-6 2:1.3.3-4 X11 client-side library ii libxml22.7.8.dfsg-2+squeeze6 GNOME XML library ii unixodbc 2.2.14p2-1ODBC tools libraries ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages asterisk recommends: ii sox 14.3.1-1+b1 Swiss army knife of sound processi Versions of packages asterisk suggests: pn asterisk-dev (no description available) pn asterisk-doc (no description available) pn asterisk-h323 (no description available) -- Configuration
Bug#611537: Bug#643507: not really solved
From: "Vladimir 'φ-coder/phcoder' Serbinenko" On 03.02.2012 13:04, Diego Guella wrote: From: "Vladimir 'φ-coder/phcoder' Serbinenko" Both Colin Watson and I tried to reproduce it or similar problems but couldn't other than on heavily desynced and corrupted disk. If you can supply the test images (just GRUB+kernel) using latest bzr upstream I'd happily fix it, otherwise I don't see what I can do. I need to understand better what you need. Do you need the dd images of all the disks? I think I nailed this bug when doing something completely unrelated. Does commeinting out all insmod gettext workarounds the problem? Yes! I commented 2 lines in /boot/grub/grub.cfg : - set locale_dir=($root)/boot/grub/locale #set lang=it #insmod gettext set timeout=5 ### END /etc/grub.d/00_header ### - and I reached the GRUB menu for the first time, booting from the 3rd disk (one of the disks not used during Debian installation!) I confirm that this workaround solves the issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#611537: Bug#643507: not really solved
From: "Vladimir 'φ-coder/phcoder' Serbinenko" Both Colin Watson and I tried to reproduce it or similar problems but couldn't other than on heavily desynced and corrupted disk. If you can supply the test images (just GRUB+kernel) using latest bzr upstream I'd happily fix it, otherwise I don't see what I can do. I need to understand better what you need. Do you need the dd images of all the disks? This is a summary of the first disk: - root@devilserver:~# fdisk -u -l /dev/sda Disk /dev/sda: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0007982f Device Boot Start End Blocks Id System /dev/sda12048 1953791 975872 82 Linux swap / Solaris Partition 1 does not end on cylinder boundary. /dev/sda2 19537929961062348828416 fd Linux raid autodetect /dev/sda399610624 3907028991 1903709184 fd Linux raid autodetect - Supplying the entire image, even omitting the 3rd partition (/home) is not feasible, both for size (40+GiB) and for security reasons. What I can do for sure is blank out one of the 5 disks, and do whatever you tell me to do on it. Or supply a dd image of the first 2048 sectors of the disk. Or the first sectors of the / partition. Or the files in my /boot directory. I want to remember you this: -When the system works, the "Welcome to GRUB" appears for some milliseconds, then I see the GRUB menu. -When the system does not work (original installation HDDs missing), "Welcome to GRUB" appears for some time, then the system reboots. This is way before loading the kernel. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#611537: Bug#643507: not really solved
From: "Vladimir 'φ-coder/phcoder' Serbinenko" On 18.11.2011 16:47, Diego Guella wrote: Actually, I discovered that the bug is still there for me too, although in has another shape now. I now have a RAID-1 with 4 members, I use 5 HDD and rotate them daily. During the Debian installation, I created a 2-member RAID-1, and later I grew the array to 4 members. If I understand this correctly your RAID never has all the devices connected. This leads to big desync (even writing once to an incomplete RAID causes desync). This is not a proper way to handle array. Frankly, I'm surprised anything works at all under such abuse. I've used my 5 device RAID1 for over 2 years with lenny, and never got those problems. Maybe I'm abusing RAID, but I don't think so. I'd like to understand better what you are talking about "desync". This is what I do (and have done since 2 years with lenny): 4-member RAID1: (a),(b),(c),(d), plus one HDD (e) disconnected from the system. 1.the system is on, 4 HDDs present, RAID1 ok. 2.turn the system off 3.remove HDD (d) from the system (it was /dev/sdd) 4.attach HDD (e) to the system (it will become the new /dev/sdd) 5.power on the system At this point, the RAID1 is in this state: - root@devilserver:~# cat /proc/mdstat Personalities : [raid1] md1 : active raid1 sdb3[2] sdc3[3] sda3[6] 1903708024 blocks super 1.2 [4/3] [U_UU] md0 : active raid1 sdb2[2] sdc2[3] sda2[6] 48827320 blocks super 1.2 [4/3] [U_UU] unused devices: - (md1 is mounted on /home, md0 is mounter on /) 6.add HDD (e) to the RAID1: - root@devilserver:~# mdadm /dev/md0 -a /dev/sdd2 mdadm: re-added /dev/sdd2 root@devilserver:~# mdadm /dev/md1 -a /dev/sdd3 mdadm: re-added /dev/sdd3 - At this point, the RAID1 is in this state: - root@devilserver:~# cat /proc/mdstat Personalities : [raid1] md1 : active raid1 sdd3[5] sdb3[2] sdc3[3] sda3[6] 1903708024 blocks super 1.2 [4/3] [U_UU] resync=DELAYED md0 : active raid1 sdd2[5] sdb2[2] sdc2[3] sda2[6] 48827320 blocks super 1.2 [4/3] [U_UU] [>] recovery = 1.1% (539648/48827320) finish=28.3min speed=28402K/sec unused devices: - When the resync will complete, the RAID1 will be OK again. The disconnected HDD (d) is an emergency copy of the system. I can recover files from it, or even connect it to an identical system and get a working machine in 0 minutes in case of a disaster. Now I'd like to understand: -What's wrong with what I'm doing? Pretend that drive (d) really dies when the system was turned off. What I'm supposed to do in that situation? Pick a new drive (e), connect it to the system, and add it to the RAID1 array. Isn't that the same? I can grow the array to 5-members, the only downside of that is the annoying mail message from mdadm because of "DegradedArray event" at every boot of the machine. I am open to other suggestions, too. Diego -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#611537: Bug#643507: not really solved
Actually, I discovered that the bug is still there for me too, although in has another shape now. I now have a RAID-1 with 4 members, I use 5 HDD and rotate them daily. During the Debian installation, I created a 2-member RAID-1, and later I grew the array to 4 members. What I have now is: -If the first OR the second disk (so, one of the 2 disks I used during Debian installation) are present in the array, then grub boots correctly. -If they are not present, grub shows "Welcome to GRUB", then reboots the machine in an endless loop. Sorry for the previous noise :( Diego -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#611537: Bug#643507: grub-pc: In an mdadm RAID1 area GRUB2 fails to boot from second HDD (at, least in SATA environment) when graphical terminal activated
Good news! I just upgraded grub-common and grub-pc from version 1.98+20100804-14 to version 1.98+20100804-14+squeeze1 (the version in Debian 6.0.3) After the update, I tried to boot from each of my 4 raid1 members, and.. now the system boots! This issue is no longer present for me. Anyone can retest with grub 1.98+20100804-14+squeeze1 and confirm? For me, this bug is resolved, and not found in version 1.98+20100804-14+squeeze1. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#611537:
Same here. Installed Debian Squeeze on a 2-drive RAID1, drives partitioned this way: #fdisk -u -l /dev/sda Disk /dev/sda: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0007982f Device Boot Start End Blocks Id System /dev/sda12048 1953791 975872 82 Linux swap / Solaris Partition 1 does not end on cylinder boundary. /dev/sda2 19537929961062348828416 fd Linux raid autodetect /dev/sda399610624 3907028991 1903709184 fd Linux raid autodetect Partitions: sd*1 used for swap, sd*2 -> /dev/md0 mounted on /, sd*3 -> /dev/md1 mounted on /home. #uname -svrmo Linux 2.6.32-5-amd64 #1 SMP Fri Sep 9 20:23:16 UTC 2011 x86_64 GNU/Linux Booting with sda and sdb connected works, even when they are physically reversed (boot from sdb). Booting with sda *only* works. Booting with sdb *only* does not work. "does not work" means that on the screen I can read: --- GRUB loading. Welcome to GRUB! --- and then, the system reboots. I manually re-installed grub on sdb: #grub-mkdevicemap #grub-install /dev/sdb Installation finished. No errors reported. Does not help. I added a 3rd drive to the raid1 array: #mdadm --grow --raid-devices=3 /dev/md0 #mdadm --grow --raid-devices=3 /dev/md1 #dd if=/dev/sda of=/dev/sdc bs=512 count=1 #sync #partprobe /dev/sdc #mkswap /dev/sdc1 #mdadm /dev/md0 -a /dev/sdc2 #mdadm /dev/md1 -a /dev/sdc3 #grub-mkdevicemap #grub-install /dev/sdc Does not work with this drive too. Set GRUB_TERMINAL=console in /etc/default/grub #update-grub Works. I can live with this workaround, but I would like to understand what's going on here and maybe help to fix this. You can find many users describing this bug on the web, one of these discussions is here: http://ubuntuforums.org/showthread.php?t=1661341 Now I wonder: why is the first installation disc so special? #blkid /dev/sdb1: UUID="edc663a6-6dc1-4d2c-b3a2-c647f96ef3b3" TYPE="swap" /dev/sda1: UUID="85099ddf-ffd0-4694-b03e-c925c6eae411" TYPE="swap" /dev/md0: UUID="e999dede-c6a5-4b0f-8e2a-00019fac4ae3" TYPE="ext4" /dev/md1: UUID="81c5c2bd-d83f-4bca-972c-72d661712337" TYPE="ext4" /dev/sdd1: UUID="ae180f5c-afca-4b0f-8ab3-120e798a15f6" TYPE="swap" /dev/sdd2: UUID="5695a0dc-6720-99cc-2d7a-92775b13bf0b" TYPE="linux_raid_member" LABEL="devilserver:0" /dev/sdd3: UUID="eccfe28c-156a-186f-be31-844598ff6361" TYPE="linux_raid_member" LABEL="devilserver:1" /dev/sdc1: UUID="9dc4f544-4a17-43d5-ad15-2e1d669525c2" TYPE="swap" /dev/sda2: UUID="5695a0dc-6720-99cc-2d7a-92775b13bf0b" LABEL="devilserver:0" TYPE="linux_raid_member" /dev/sda3: UUID="eccfe28c-156a-186f-be31-844598ff6361" LABEL="devilserver:1" TYPE="linux_raid_member" /dev/sdb2: UUID="5695a0dc-6720-99cc-2d7a-92775b13bf0b" LABEL="devilserver:0" TYPE="linux_raid_member" /dev/sdb3: UUID="eccfe28c-156a-186f-be31-844598ff6361" LABEL="devilserver:1" TYPE="linux_raid_member" /dev/sdc2: UUID="5695a0dc-6720-99cc-2d7a-92775b13bf0b" LABEL="devilserver:0" TYPE="linux_raid_member" /dev/sdc3: UUID="eccfe28c-156a-186f-be31-844598ff6361" LABEL="devilserver:1" TYPE="linux_raid_member" The first 2048 512-byte sectors of each disk are identical The first 512-byte sector of sdb2, sdc2, sdd2 are full of 0's The first 512-byte sector of sda2 contains: #dd if=/dev/sda2 of=sda2_sector0.bin bs=512 count=1 # hexdump sda2_sector0.bin 000 804f 804f 0001 804f 0002 804f 0003 010 804f 0004 804f 000c 804f 000d 804f 0018 020 804f 0028 804f 003e 804f 0079 804f 00ab 030 * 200 So I copied this sector into sdb: #dd if=/dev/sda2 of=/dev/sdb2 bs=512 count=1 Tried to boot with sdb only.. no success. -EOUTOFIDEAS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#643507: hylafax-server: Should start after iaxmodem in initscripts
Package: hylafax-server Version: 2:6.0.5-4.1 Severity: important Tags: patch I am using iaxmodem to receive and send faxes from/to Asterisk. The whole thing works OK, BUT: every time I (re)start the system, I need to restart Hylafax manually. Reason: # faxstat -a: --- HylaFAX scheduler on squerisk: Running Modem ttyIAX (+39.030.7242870): Listening to rings from modem --- Cause: faxgetty should be started AFTER iaxmodem. In my system, iaxmodem is in /etc/rc2.d with symlink S21iaxmodem, and hylafax is in /etc/rc2.d with symlink S19hylafax. Resolution: Add Should-Start: iaxmodem to hylafax init script. Patch: --- hylafax 2011-09-27 15:28:44.593528275 +0200 +++ hylafax_new 2011-09-27 15:28:24.118034669 +0200 @@ -9,7 +9,7 @@ # Provides: hylafax # Required-Start:$syslog $remote_fs # Required-Stop: $syslog $remote_fs -# Should-Start: $local_fs $network +# Should-Start: $local_fs $network iaxmodem # Should-Stop: $local_fs $network # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 After patching the init script, run: insserv hylafax hylafax will be moved (on my system) to S23hylafax. This fixes the problem. Best regards, Diego Guella -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages hylafax-server depends on: ii adduser3.112+nmu2add and remove users and groups ii bsd-mailx [mailx] 8.1.2-0.20100314cvs-1 simple mail user agent ii debconf [debconf-2 1.5.36.1 Debian configuration management sy ii exim4-daemon-light 4.72-6+squeeze2 lightweight Exim MTA (v4) daemon ii ghostscript8.71~dfsg2-9 The GPL Ghostscript PostScript/PDF ii hylafax-client 2:6.0.5-4.1 Flexible client/server fax softwar ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libgcc11:4.4.5-8 GCC support library ii libpam0g 1.1.1-6.1 Pluggable Authentication Modules l ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii libtiff-tools 3.9.4-5+squeeze3 TIFF manipulation and conversion t ii libtiff4 3.9.4-5+squeeze3 Tag Image File Format (TIFF) libra ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii psmisc 22.11-1 utilities that use the proc file s ii sed4.2.1-7 The GNU sed stream editor ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime hylafax-server recommends no packages. Versions of packages hylafax-server suggests: pn mgetty (no description available) pn psrip (no description available) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#482012: exim4: TLS incoming connections problems
OK. Got it. The package who messed up my TLS setup with OE was: ca-certificates which was automatically installed when I installed: fetchmail What I did to resolve the problem: 1. remove ca-certificates with aptitude 2. rm /etc/ssl/certs/ca-certificates.crt This is a brutal solution, but I don't need ca-certificates for now. In addition, I can see this with Ethereal: Common-part of the connection: - S> 220 servername\r\n C< EHLO clientname\r\n S> 250-servername Hello clientname [ip]\r\n S> 250-SIZE 52428800\r\n S> 250-PIPELINING\r\n S> 250-STARTTLS\r\n S> 250 HELP\r\n C< STARTTLS\r\n S> 220 TLS go ahead\r\n C< (156 bytes on wire) S> (133 bytes on wire) S> (774 bytes on wire, I can recognize some parts of my self-certificate here) - Then, when ca-certificates is not installed: - S> (77 bytes on wire) S> (60 bytes on wire) S> (91 bytes on wire) C< (87 bytes on wire) S> (206 bytes on wire) and all goes well - When ca-certificates is installed: - S> (1514 bytes on wire, I can see parts of other CA strings there) S> (1514 bytes on wire, I can see parts of other CA strings there) S> (1514 bytes on wire, I can see parts of other CA strings there) S> (1514 bytes on wire, I can see parts of other CA strings there) S> (1514 bytes on wire, I can see parts of other CA strings there) S> (1514 bytes on wire, I can see parts of other CA strings there) S> (1514 bytes on wire, I can see parts of other CA strings there) S> (1514 bytes on wire, I can see parts of other CA strings there) S> (1514 bytes on wire, I can see parts of other CA strings there) S> (1514 bytes on wire, I can see parts of other CA strings there) S> (1514 bytes on wire, I can see parts of other CA strings there) S> (383 bytes on wire, I can see parts of other CA strings there) S> (1514 bytes on wire, I can see parts of other CA strings there) C< [FIN, ACK] C< [SYN] S> [SYN, ACK] C< [ACK] C< EHLO clientname S> (1364 bytes on wire, keeps sending other CA strings) S> (63 bytes on wire) C< [RST, ACK] S> [ACK] S> [SYN] C< [RST, ACK] S> 554 SMTP synchronization error\r\n C< HELO clientname\r\n S> [ACK] S> [RST, ACK] - Hope this helps identifying the problem. Regards, Diego -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#482012: exim4: TLS incoming connections problems
- Original Message -
From: "Marc Haber" <[EMAIL PROTECTED]>
When I last looked, OE was not able to do STARTTLS and required
special configuration to allow smtp-over-tls on Port 465. Exim
requires special configuration to support this. How did you enable
smtp-over-tls?
I installed Debian, then followed these instructions:
http://pkg-exim4.alioth.debian.org/README/README.Debian.html#TLS
1. Generate the cert
2. set MAIN_TLS_ENABLE
3. edit /etc/exim4/exim4.conf.template to add a simple plaintext LOGIN
authenticator with Outlook Express server prompt fix:
-
fixed_login:
driver = plaintext
public_name = LOGIN
server_prompts = Username:: : Password::
server_condition = \
${if and {{eq{$auth1}{username}}{eq{$auth2}{password
.ifndef AUTH_SERVER_ALLOW_NOTLS_PASSWORDS
server_advertise_condition = ${if eq{$tls_cipher}{}{}{*}}
.endif
-
At this point (no SMTPLISTENEROPTIONS and tls_on_connect_ports)
Outlook Express clients from my network can connect and send messages over this
server.
(If that matters, Outlook is on Windows XP SP2, outlook version
6.0.2900.2180.xpsp_sp2_gdr.070227-2254)
Since yesterday many packages went into lenny, I'm not sure if Exim is
the real cause of this problem, maybe it could be gnutls, or something
other.
Where can I get exim 4.69-2 to test it again and see if it works?
You can try pulling an older package from snapshot.debian.net.
Many thanks, I successfully reverted all the exim packages to 4.69-2, but I had
no luck, it doesn't work.
I then reverted libgnutls26 from 2.2.3~rc-1 to 2.2.2-1, but no luck again.
I would suggest a different debugging path though:
(1) verify whether your OE does STARTTLS or smtp-over-ssl
(2) try with a command line client (swaks, gnutls-cli, openssl s_client)
whether your exim actually does what your OE expects it to do
(3) try with a command line server (gnutls-serv, openssl s_server)
whether your OE is able to connect to the server. This might be a
challenge to do with STARTTLS.
Disabling the client certificate request in exim configuration may be
worth a try, too.
Maybe I haven't explained myself well, sorry for that.
I said that my Outlook Express was doing TLS until Friday, when I left the
office.
On Monday, I upgraded this system (let's call this system "vmdeb"), along with other things such installing apache, squirrelmail
spamassassin, and now OE can't do TLS any more.
By the way:
To answer your (1), my OE _does_ STARTTLS (I snarfed it with Ethereal).
What's new is that I found another system, let's call it "realdeb", that was
not upgraded.
I followed the 3 points above (gencert, MAIN_TLS_ENABLE, add plaintext login
authenticator), and now OE/TLS works on "realdeb"!!!
What I would like to know is what is changed that now has broken the TLS setup.
If, for example, we find the package that is changed, looking at his changelog
we can find out the problem
Do you know of any other possible package upgrade related to this issue between
May 16 and May 19?
do you think that installing Apache, Squirrelmail and Spamassassin could have
broken TLS?
Let me know if you need more informations/tests.
Greetings
Marc
Thanks,
Diego
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#482012: exim4: TLS incoming connections problems
Package: exim4 Version: 4.69-5 Severity: normal I was using TLS with an Outlook Express client fine with version 4.69-2. Yesterday, 4.69-5 went into lenny, I upgraded, and now i have these errors: - (from /var/log/exim4/mainlog) TLS error on connection from (hostname) [ipaddress] (gnutls_handshake): Error in the push function. - This blocks here, then Outlook Express have a timeout and closes the connection: - (from /var/log/exim4/mainlog) unexpected disconnection while reading SMTP command from (hostname) [ipaddress] (error: connection reset by peer) - Then, I try again sending the message, but I get: - (from /var/log/exim4/mainlog) TLS error on connection from (hostname) [ipaddress] (gnutls_handshake): A TLS packet with unexpected length was received. - And again blocks here, then Outlook Express times out, and the story begins again from the start... Since yesterday many packages went into lenny, I'm not sure if Exim is the real cause of this problem, maybe it could be gnutls, or something other. Where can I get exim 4.69-2 to test it again and see if it works? -- Package-specific info: Exim version 4.69 #1 built 02-May-2008 12:58:06 Copyright (c) University of Cambridge 2006 Berkeley DB: Berkeley DB 4.6.21: (September 27, 2007) Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc GnuTLS move_frozen_messages Content_Scanning Old_Demime Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql sqlite Authenticators: cram_md5 cyrus_sasl dovecot plaintext spa Routers: accept dnslookup ipliteral iplookup manualroute queryprogram redirect Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp Fixed never_users: 0 Size of off_t: 8 Configuration file is /var/lib/exim4/config.autogenerated # /etc/exim4/update-exim4.conf.conf # # Edit this file and /etc/mailname by hand and execute update-exim4.conf # yourself or use 'dpkg-reconfigure exim4-config' # # Please note that this is _not_ a dpkg-conffile and that automatic changes # to this file might happen. The code handling this will honor your local # changes, so this is usually fine, but will break local schemes that mess # around with multiple versions of the file. # # update-exim4.conf uses this file to determine variable values to generate # exim configuration macros for the configuration file. # # Most settings found in here do have corresponding questions in the # Debconf configuration, but not all of them. # # This is a Debian specific file dc_eximconfig_configtype='internet' dc_other_hostnames='' dc_local_interfaces='' dc_readhost='' dc_relay_domains='' dc_minimaldns='false' dc_relay_nets='' dc_smarthost='' CFILEMODE='644' dc_use_split_config='false' dc_hide_mailname='false' dc_mailname_in_oh='true' dc_localdelivery='maildir_home' mailname:localhost -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages exim4 depends on: ii debconf [debconf-2.0] 1.5.21 Debian configuration management sy ii exim4-base4.69-5+b1 support files for all Exim MTA (v4 ii exim4-daemon-heavy4.69-5+b1 Exim MTA (v4) daemon with extended exim4 recommends no packages. -- debconf information: * exim4/drec: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
