Bug#702374: postfix: get message Relay Access Denied, when using SASL

2013-03-05 Thread Danny ter Haar
Package: postfix
Version: 2.9.6-1
Severity: grave
Justification: renders package unusable



-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages postfix depends on:
ii  adduser3.113+nmu3
ii  cpio   2.11+dfsg-0.1
ii  debconf [debconf-2.0]  1.5.49
ii  dpkg   1.16.9
ii  libc6  2.13-38
ii  libdb5.1   5.1.29-5
ii  libsasl2-2 2.1.25.dfsg1-6
ii  libsqlite3-0   3.7.15.2-1
ii  libssl1.0.01.0.1e-1
ii  lsb-base   4.1+Debian9
ii  netbase5.0
ii  ssl-cert   1.0.32

Versions of packages postfix recommends:
ii  python  2.7.3-4

Versions of packages postfix suggests:
ii  bsd-mailx [mail-reader]  8.1.2-0.2006cvs-1
pn  dovecot-common   none
ii  libsasl2-modules 2.1.25.dfsg1-6
ii  mutt [mail-reader]   1.5.21-6.2
ii  postfix-cdb  2.10.0-1
pn  postfix-doc  none
pn  postfix-ldap none
pn  postfix-mysqlnone
ii  postfix-pcre 2.10.0-1
pn  postfix-pgsqlnone
ii  procmail 3.22-20
pn  resolvconf   none
ii  sasl2-bin2.1.25.dfsg1-6
pn  ufw  none

-- debconf information:
* postfix/mailname: dth.net
  postfix/tlsmgr_upgrade_warning:
  postfix/retry_upgrade_warning:
  postfix/relayhost:
* postfix/procmail: true
  postfix/bad_recipient_delimiter:
  postfix/rfc1035_violation: false
* postfix/mynetworks: localhost,85.159.113.100
  postfix/sqlite_warning:
* postfix/protocols: all
* postfix/recipient_delim: +
* postfix/main_mailer_type: Internet Site
  postfix/kernel_version_warning:
* postfix/chattr: false
* postfix/root_address:
  postfix/mydomain_warning:
* postfix/destinations: dth.net,ix.dth.net,localhost
  postfix/not_configured:
* postfix/mailbox_limit: 0


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#589633: munin-node: [trivial] typo in warning/error text spesifics in /usr/sbin/munin-run

2010-07-19 Thread Danny ter Haar
Package: munin-node
Version: 1.4.5-1
Severity: minor
Tags: lenny

Solution:
s/spesifics/specifics/

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages munin-node depends on:
ii  adduser   3.112  add and remove users and groups
ii  gawk  1:3.1.7.dfsg-5 GNU awk, a pattern scanning and pr
ii  libnet-server-perl0.97-1 An extensible, general perl server
ii  lsb-base  3.2-23.1   Linux Standard Base 3.2 init scrip
ii  munin-common  1.4.5-1network-wide graphing framework (c
ii  perl  5.10.1-13  Larry Wall's Practical Extraction 
ii  procps1:3.2.8-9  /proc file system utilities

Versions of packages munin-node recommends:
ii  libnet-snmp-perl  5.2.0-4Script SNMP connections

Versions of packages munin-node suggests:
ii  acpi1.5-2displays information on ACPI devic
ii  ethtool 1:2.6.34-2   display or change Ethernet device 
ii  hdparm  9.27-2   tune hard disk parameters for high
pn  libcache-cache-perl none   (no description available)
ii  libcrypt-ssleay-perl0.57-2   Support for https protocol in LWP
ii  libdbd-mysql-perl   4.015-1  Perl5 database interface to the My
ii  libdbd-pg-perl  2.17.1-2 Perl DBI driver for the PostgreSQL
pn  liblwp-useragent-determ none   (no description available)
pn  libnet-irc-perl none   (no description available)
ii  libnet-ssleay-perl  1.36-1   Perl module for Secure Sockets Lay
ii  libtext-csv-xs-perl 0.73-1   Perl C/XS module to process Comma-
ii  libwww-perl 5.836-1  Perl HTTP/WWW client/server librar
ii  libxml-simple-perl  2.18-3   Perl module for reading and writin
ii  lm-sensors  1:3.1.2-6utilities to read temperature/volt
ii  logtail 1.3.10   Print log file lines that have not
pn  munin   none   (no description available)
pn  munin-java-plugins  none   (no description available)
ii  munin-plugins-extra 1.4.5-1  network-wide graphing framework (u
ii  mysql-client-5.1 [mysql 5.1.48-1 MySQL database client binaries
ii  net-tools   1.60-23  The NET-3 networking toolkit
pn  python  none   (no description available)
pn  rubynone   (no description available)
ii  smartmontools   5.39.1+svn3077-1 control and monitor storage system

-- 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#589633: munin-node: [trivial] typo in warning/error text spesifics in /usr/sbin/munin-run

2010-07-19 Thread Danny ter Haar
On Mon, 2010-07-19 at 08:37 -0400, Holger Levsen wrote:
 tags 589633 - lenny
 # 1.4.5-1 is not in lenny
 tags 589633 + unreproducable
 thanks
 
 Hi Danny,
 
 I cant find that typo:
 
 ~/Projects/munin/trunk$ rgrep spesifics .
 ~/Projects/munin/trunk
 
 ~/Projects/munin/squeeze$ rgrep  spesifics .|grep -v svn
 ~/Projects/munin/squeeze$ 
 
 $ LANG=C grep spesi $(dpkg -L munin-node)
 grep: /var/log/munin: Permission denied
 grep: /etc/munin/plugin-conf.d: Permission denied
 grep: /etc/munin/plugin-conf.d/munin-node: Permission denied
 $
 
 $ dpkg -l munin-node|grep munin
 ii  munin-node   1.4.5-1  
  
 network-wide graphing framework (node)
 
 
 cheers,
   Holger

Strange:
r...@firewall:/var/cache/apt/archives# grep -i spesifics  /usr/sbin/mu
munin-node munin-node-configure
munin-node-configure-snmp  munin-run
r...@firewall:/var/cache/apt/archives# grep -i
spesifics  /usr/sbin/munin-run 
warn Something wicked happened while reading \$sconffile
\. Check the previous log lines for spesifics.;
warn Something wicked happened while reading
\$servicedir/$file\. Check the previous log lines for spesifics.;
r...@firewall:/var/cache/apt/archives# dpkg -S /usr/sbin/munin-run
munin-node: /usr/sbin/munin-run
r...@firewall:/var/cache/apt/archives# dpkg -l munin-node
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ NameVersion Description
+++-===-===-==
ii  munin-node  1.2.6-10~lenny2 network-wide
graphing framework (node)
r...@firewall:/var/cache/apt/archives# ls -l munin*  
-rw-r--r-- 1 root src 661884 Dec  5  2009
munin-node_1.2.6-10~lenny2_all.deb
-rw-r--r-- 1 root src  73412 Dec  5  2009
munin-plugins-extra_1.2.6-10~lenny2_all.deb


1.2.6-10-lenny2 seems to be current in stable according to
http://packages.debian.org/lenny/munin-node

So what am i doing different than you  ? :-)

Danny




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#589633: munin-node: [trivial] typo in warning/error text spesifics in /usr/sbin/munin-run

2010-07-19 Thread Danny ter Haar
Quoting Holger Levsen (hol...@layer-acht.org):

the machine in question ( a firewall) has no mail installed.
So the bug report was made from another machine running sid, 
That might have added to the confusion.
I should have made that clear in my description.

But the bug is really there in lenny !

-- 
life is what happens to you while you’re busy making other plans - John Lennon



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#428107: xmms: eats a _lot_ of memory listening to a radio stream

2007-06-08 Thread Danny ter Haar
Package: xmms
Version: 1:1.2.10+20070601-1
Severity: serious
Justification: unkown



-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.21-1-vserver-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xmms depends on:
ii  libasound21.0.13-2   ALSA library
ii  libaudiofile0 0.2.6-6Open-source version of SGI's audio
ii  libc6 2.5-10 GNU C Library: Shared libraries
ii  libesd-alsa0 [libesd0]0.2.36-3   Enlightened Sound Daemon (ALSA) - 
ii  libgl1-mesa-glx [libgl1]  6.5.2-5A free implementation of the OpenG
ii  libglib1.21.2.10-17  The GLib library of C routines
ii  libgtk1.2 1.2.10-18  The GIMP Toolkit set of widgets fo
ii  libice6   1:1.0.3-2  X11 Inter-Client Exchange library
ii  libmikmod23.1.11-a-6 A portable sound library
ii  libogg0   1.1.3-2Ogg Bitstream Library
ii  libsm62:1.0.3-1  X11 Session Management library
ii  libvorbis0a   1.1.2.dfsg-1.2 The Vorbis General Audio Compressi
ii  libvorbisfile31.1.2.dfsg-1.2 The Vorbis General Audio Compressi
ii  libx11-6  2:1.0.3-7  X11 client-side library
ii  libxext6  1:1.0.3-2  X11 miscellaneous extension librar
ii  libxi61:1.0.1-4  X11 Input extension library
ii  libxxf86vm1   1:1.0.1-2  X11 XFree86 video mode extension l
ii  zlib1g1:1.2.3-15 compression library - runtime

Versions of packages xmms recommends:
ii  unzip 5.52-9 De-archiver for .zip files

-- no debconf information


After listening for a couple of days to his stream:
http://ic.1980s.fm:80/80s128k.ogg
xmms is eating almost 40% of the memory on my workstation


ps axuw
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
dth   8241  0.4 39.2 854400 803068 ?   SLl  Jun05  20:26 xmms

Stopping xmms doesn't release the memory, exiting xmms however DOES.
I _think_ this is not how it should be.

Danny


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#421924: Acknowledgement (segfaults at fresh amd64 etch install)

2007-05-03 Thread Danny ter Haar
build from debian sources: same problem

Enabled  -g in the Makefile 
Ran the program with gdb:

---

Starting program: /usr/src/procinfo-18/procinfo 

Program received signal SIGSEGV, Segmentation fault.
0x00407d3b in first_page (sl=500) at procinfo.c:555
555 if (irq_label[i][0] == 0)



Remains strange that it sometimes does work and sometimes it doesn't

Danny


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#310368: mdadm: breaks during apt-get dist-upgrade

2005-05-27 Thread Danny ter Haar
Quoting martin f krafft ([EMAIL PROTECTED]):
 Certainly not, but are you sure that the arrays weren't degraded
 beforehand?

Hmm.. machine rebooted on the 23th..
from kern.log:

May 23 05:50:24 localhost kernel: devfs_mk_dev: could not append to parent for 
md/0
May 23 05:50:24 localhost kernel: md: Autodetecting RAID arrays.
May 23 05:50:24 localhost kernel: md: autorun ...
May 23 05:50:24 localhost kernel: md: considering sdb5 ...
May 23 05:50:24 localhost kernel: md:  adding sdb5 ...
May 23 05:50:24 localhost kernel: md: sdb3 has different UUID to sdb5
May 23 05:50:24 localhost kernel: md: sdb2 has different UUID to sdb5
May 23 05:50:24 localhost kernel: md: sdb1 has different UUID to sdb5
May 23 05:50:24 localhost kernel: md:  adding sda5 ...
May 23 05:50:24 localhost kernel: md: sda3 has different UUID to sdb5
May 23 05:50:24 localhost kernel: md: sda2 has different UUID to sdb5
May 23 05:50:24 localhost kernel: md: sda1 has different UUID to sdb5
May 23 05:50:24 localhost kernel: devfs_mk_dev: could not append to parent for 
md/3
May 23 05:50:24 localhost kernel: md: created md3
May 23 05:50:24 localhost kernel: md: bindsda5
May 23 05:50:24 localhost kernel: md: bindsdb5
May 23 05:50:24 localhost kernel: md: running: sdb5sda5
May 23 05:50:24 localhost kernel: md: kicking non-fresh sdb5 from array!
May 23 05:50:24 localhost kernel: md: unbindsdb5
May 23 05:50:24 localhost kernel: md: export_rdev(sdb5)
May 23 05:50:24 localhost kernel: md: md3: raid array is not clean -- starting 
background reconstruction
May 23 05:50:24 localhost kernel: raid1: raid set md3 active with 1 out of 2 
mirrors
May 23 05:50:24 localhost kernel: md: considering sdb3 ...
May 23 05:50:24 localhost kernel: md:  adding sdb3 ...
May 23 05:50:24 localhost kernel: md: sdb2 has different UUID to sdb3
May 23 05:50:24 localhost kernel: md: sdb1 has different UUID to sdb3
May 23 05:50:24 localhost kernel: md:  adding sda3 ...
May 23 05:50:24 localhost kernel: md: sda2 has different UUID to sdb3
May 23 05:50:24 localhost kernel: md: sda1 has different UUID to sdb3
May 23 05:50:24 localhost kernel: devfs_mk_dev: could not append to parent for 
md/2
May 23 05:50:24 localhost kernel: md: created md2
May 23 05:50:24 localhost kernel: md: created md2
May 23 05:50:24 localhost kernel: md: bindsda3
May 23 05:50:24 localhost kernel: md: bindsdb3
May 23 05:50:24 localhost kernel: md: running: sdb3sda3
May 23 05:50:24 localhost kernel: md: kicking non-fresh sdb3 from array!
May 23 05:50:24 localhost kernel: md: unbindsdb3
May 23 05:50:24 localhost kernel: md: export_rdev(sdb3)
May 23 05:50:24 localhost kernel: raid1: raid set md2 active with 1 out of 2 
mirrors
May 23 05:50:24 localhost kernel: md: considering sdb2 ...
May 23 05:50:24 localhost kernel: md:  adding sdb2 ...
May 23 05:50:24 localhost kernel: md: sdb1 has different UUID to sdb2
May 23 05:50:24 localhost kernel: md:  adding sda2 ...
May 23 05:50:24 localhost kernel: md: sda1 has different UUID to sdb2
May 23 05:50:24 localhost kernel: devfs_mk_dev: could not append to parent for 
md/1
May 23 05:50:24 localhost kernel: md: created md1
May 23 05:50:24 localhost kernel: md: bindsda2
May 23 05:50:24 localhost kernel: md: bindsdb2
May 23 05:50:24 localhost kernel: md: running: sdb2sda2
May 23 05:50:24 localhost kernel: md: kicking non-fresh sdb2 from array!
May 23 05:50:24 localhost kernel: md: unbindsdb2
May 23 05:50:24 localhost kernel: md: export_rdev(sdb2)
May 23 05:50:24 localhost kernel: raid1: raid set md1 active with 1 out of 2 
mirrors
May 23 05:50:24 localhost kernel: md: considering sdb1 ...
May 23 05:50:24 localhost kernel: md:  adding sdb1 ...
May 23 05:50:24 localhost kernel: md:  adding sda1 ...
May 23 05:50:24 localhost kernel: md: created md0
May 23 05:50:24 localhost kernel: md: bindsda1
May 23 05:50:24 localhost kernel: md: bindsdb1
May 23 05:50:24 localhost kernel: md: running: sdb1sda1
May 23 05:50:24 localhost kernel: md: kicking non-fresh sdb1 from array!
May 23 05:50:24 localhost kernel: md: unbindsdb1
May 23 05:50:24 localhost kernel: md: export_rdev(sdb1)
May 23 05:50:24 localhost kernel: raid1: raid set md0 active with 1 out of 2 
mirrors
May 23 05:50:24 localhost kernel: md: ... autorun DONE.

It seems you are right!
It had been running on one disk for a couple of days ! :-(
Somehow only after the upgrade the mail-warning kicked in.

Sorry to have bothered you ...

Danny

-- 
innovation is the enemy of the status quo - it puts people out of business



Bug#310368: mdadm: breaks during apt-get dist-upgrade

2005-05-26 Thread Danny ter Haar
Quoting martin f krafft ([EMAIL PROTECTED]):
 This is ugly, but only aestethically speaking.

so only a warning !?

 You setup looks weird. mdadm.conf contains /dev/md0 and you are
 already using /dev/md/d0p6 (partitionable arrays).

How about this one:

usenetgateway (amd64 with scsi controller  disks)

--

[APT-GET DIST-UPGRADE]

Preparing to replace mdadm 1.9.0-3 (using .../mdadm_1.9.0-4_amd64.deb) ...
Stopping RAID monitor daemon: mdadm -F.
Unpacking replacement mdadm ...
Setting up mdadm (1.9.0-4) ...
Starting raid devices: done.
Starting RAID monitor daemon: mdadm -F.

[here i received email about degraded raid arrays]

newsgate:~# cat /proc/mdstat
Personalities : [raid1] [multipath]
md1 : active raid1 sda2[0]
  6835584 blocks [2/1] [U_]

md2 : active raid1 sda3[0]
  3903680 blocks [2/1] [U_]

md3 : active raid1 sda5[0]
  9767424 blocks [2/1] [U_]

md0 : active raid1 sda1[0]
  979840 blocks [2/1] [U_]

unused devices: none

[config file was still there]

newsgate:~# cat /etc/mdadm/mdadm.conf
DEVICE partitions
ARRAY /dev/md3 level=raid1 num-devices=2 
UUID=308b94ec:b43cb586:660a8b7f:7dfd73fe
   devices=/dev/sda5,/dev/sdb5
ARRAY /dev/md2 level=raid1 num-devices=2 
UUID=c6462239:ab3eef96:3e8d00e3:0c4937b0
   devices=/dev/sda3,/dev/sdb3
ARRAY /dev/md1 level=raid1 num-devices=2 
UUID=e3f28ee7:b969f517:2a287ca6:f8a604fd
   devices=/dev/sda2,/dev/sdb2
ARRAY /dev/md0 level=raid1 num-devices=2 
UUID=825a6fe4:15c554b2:13e7c8a6:8a0e2106
   devices=/dev/sda1,/dev/sdb1
newsgate:~# mdadm -a /dev/md0 /dev/sdb1
mdadm: hot added /dev/sdb1
newsgate:~# mdadm -a /dev/md1 /dev/sdb2
mdadm: hot added /dev/sdb2
newsgate:~# mdadm -a /dev/md2 /dev/sdb3
mdadm: hot added /dev/sdb3
newsgate:~# mdadm -a /dev/md3 /dev/sdb5
mdadm: hot added /dev/sdb5

newsgate:~# cat /proc/mdstat 
Personalities : [raid1] [multipath] 
md1 : active raid1 sdb2[2] sda2[0]
  6835584 blocks [2/1] [U_]
  [==..]  recovery = 71.5% (4888576/6835584) finish=0.6min 
speed=48282K/sec
md2 : active raid1 sdb3[2] sda3[0]
  3903680 blocks [2/1] [U_]
resync=DELAYED
md3 : active raid1 sdb5[2] sda5[0]
  9767424 blocks [2/1] [U_]
resync=DELAYED
md0 : active raid1 sdb1[1] sda1[0]
  979840 blocks [2/2] [UU]
  
unused devices: none

It's now rebuilding.
*i* don't think it's normal that dist upgrade suddenly kicks half the
disks offline, or am i missing something ?!

Kind regards,

Danny
-- 
innovation is the enemy of the status quo - it puts people out of business







- End forwarded message -

-- 
innovation is the enemy of the status quo - it puts people out of business



!DSPAM:4296ae40141838186613631!




-- 
innovation is the enemy of the status quo - it puts people out of business



Bug#310368: mdadm: breaks during apt-get dist-upgrade

2005-05-24 Thread Danny ter Haar
Quoting Steve Langasek ([EMAIL PROTECTED]):
 Can you tell us what version of mdadm you had installed prior to this?

I just upgraded my machine and this happened:

Preparing to replace mdadm 1.9.0-2.3 (using .../mdadm_1.9.0-3_i386.deb) ...
Stopping RAID monitor daemon: mdadm -F.
Unpacking replacement mdadm ...

[SNIP]

Setting up mdadm (1.9.0-3) ...
Starting raid devices: mdadm: failed to add /dev/sdb to /dev/md0: Device or 
resource busy
mdadm: failed to add /dev/sda to /dev/md0: Device or resource busy
mdadm: /dev/md0 assembled from 0 drives - not enough to start the array.
done.
Starting RAID monitor daemon: mdadm -F.

-

Huh ?!

zaphod:# cat /etc/mdadm/mdadm.conf 
DEVICE partitions
ARRAY /dev/md0 level=raid1 num-devices=2 
UUID=7e58424c:c4bb377c:74c22ff7:1911f1e2
   devices=/dev/sda,/dev/sdb

zaphod:# mount
/dev/md/d0p1 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/md/d0p5 on /usr type ext3 (rw)
/dev/md/d0p6 on /var type ext3 (rw)
/dev/md/d0p7 on /extra type xfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/md/d0p8 on /extra/home/staff type xfs 
(rw,loop=/dev/loop3,gpgkey=/root/keyfile.gpg,encryption=AES128)

zaphod:# cat /proc/mdstat
Personalities : [raid1] 
md_d0 : active raid1 sdb[1] sda[0]
  80043200 blocks [2/2] [UU]
  
unused devices: none
-
Definatly something fishy in _my_ eyes!

Danny

-- 
4 questions of life: What is sacred?  What is the spirit made of?
What is worth living for?  And what is worth dying for?
The answer to all, is LOVE.



Bug#310368: mdadm: breaks during apt-get dist-upgrade

2005-05-23 Thread Danny ter Haar
Quoting Steve Langasek ([EMAIL PROTECTED]):
 Can you tell us what version of mdadm you had installed prior to this?

nope, sorry

it's a pitty that apt/dpkg doesn't write this info to a log file !
I couldn't scroll back for enough!


-- 
4 questions of life: What is sacred?  What is the spirit made of?
What is worth living for?  And what is worth dying for?
The answer to all, is LOVE.



Bug#310368: mdadm: breaks during apt-get dist-upgrade

2005-05-23 Thread Danny ter Haar
Quoting Steve Langasek ([EMAIL PROTECTED]):
 tags 310368 = moreinfo unreproducible
 severity 310368 important
 thanks
 
 I've verified that there is no code path in this package that would cause
 /etc/mdadm/mdadm.conf to be removed on upgrade, so I don't really see how
 this can be the package's fault.  It could be the fault of some previous,
 broken version of mdadm that you had installed before this upgrade.
 
 Other than the missing /etc/mdadm/mdadm.conf file, did the installation of
 the package actually fail?

nope, but one of our other servers (a usenet spool server) kernel
paniced yesterday and it's only because it has a serial console and a
normal ide disk to start from that we could revive it.
I do agree that probably a previous mdadm upgrade probably barfed and
only after panic/reboot we found out it was br0ken.

Regards,

Danny
-- 
4 questions of life: What is sacred?  What is the spirit made of?
What is worth living for?  And what is worth dying for?
The answer to all, is LOVE.