<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>96038</bug_id>
          
          <creation_ts>2005-06-14 00:05 0000</creation_ts>
          <short_desc>metalog: processes hang when writing to /dev/log, e.g. PAM denies login</short_desc>
          <delta_ts>2007-05-19 21:11:04 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Core system</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>critical</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>Martin.vGagern@gmx.net</reporter>
          <assigned_to>pam-bugs@gentoo.org</assigned_to>
          <cc>ka0ttic@gentoo.org</cc>
    
    <cc>pstradomski@gmail.com</cc>
    
    <cc>vapier@gentoo.org</cc>
    
    <cc>zenith@zenith.dk</cc>

      

      
          <long_desc isprivate="0">
            <who>Martin.vGagern@gmx.net</who>
            <bug_when>2005-06-14 00:05:55 0000</bug_when>
            <thetext>OK, this is one of the weirdest bugs I&apos;ve ever seen, so I&apos;ll give you a rather
lengthy description as I&apos;m not too sure about the connections myself.
Actually I had problems to log into my system twice, both times I&apos;m sure it was
pam because multiple services were affected. I&apos;m not sure if those two incidents
are connected, but two unrelated PAM problems seem too much of a coincidence, so
I file one single bug report.

The first thing was, I came to my machine and was locked out: could log into no
console, could not authenticate via ssh, could not even cancel my kde screen
lock. All login atempts simply got stuck. Only Idea I had was to press reset.

The Boot process got stuck while starting Postfix. So reset again, this time
with init=/sbin/sulogin. That worked, luckily, but emerge did not work from this
environment, I&apos;ll paste the trace somewhere down there.
After several reboots I got my system to runlevel 1 with sulogin on the first
vc. Now I think about it, I&apos;m not entirely sure I even tried to log into one of
the other, PAM based login vc&apos;s.

I rsynced and remerged pam and pam-login. etc-update gave me some differences in
system-auth (the path /lib/security/ got removed from modules), which is
surprising because emerge labeld this a remerge, same version, and I&apos;m pretty
sure I did not throw away any new pam configs. After this login did work again.
When going to runlevel 3, NFS got stuck, so I removed this service for the time
being and could reboot successfully.

Today, I suddenly experienced problems using su, and ssh and login as well.
Luckily, I had a root shell open, so I could strace su and find out that it got
stuck in the send call, writing to /dev/log. I checked, /dev/log was a socket
all right. Unfortunately, I did not think to netstat this thing.

After restarting metalog, su and all the other programs suddenly worked all
right. The migration from sysklogd to metalog was a rather recent change to my
system.

Basically there are several issues in this:
1. Why does the send on /dev/log fail?
2. Why were there changes in my configs, as the package version kept te same?
3. PAM should probably respond more gracefully to bad configs, if this was
indeed the problem I experienced.
4. PAM should recover from a logging problem.
5. emerge should work from a init=/sbin/sulogin shell, as should screen.


Reproducible: Didn&apos;t try
Steps to Reproduce:

Actual Results:  
emerge from init=/sbin/sulogin shell:

Traceback (most recent call last):
  File &quot;/usr/bin/emerge&quot;, line 3200, in ?
    mydepgraph.merge(mydepgraph.altlist())
  File &quot;/usr/bin/emerge&quot;, line 1912, in merge
    retval=portage.doebuild(y,&quot;merge&quot;,myroot,self.pkgsettings,edebug)
  File &quot;/usr/lib/portage/pym/portage.py&quot;, line 2721, in doebuild
   
retval=spawnebuild(&quot;install&quot;,actionmap,mysettings,debug,alwaysdep=1,logfile=logfile)
  File &quot;/usr/lib/portage/pym/portage.py&quot;, line 2304, in spawnebuild
   
retval=spawnebuild(actionmap[mydo][&quot;dep&quot;],actionmap,mysettings,debug,alwaysdep=alwaysdep,logfile=logfile)
  File &quot;/usr/lib/portage/pym/portage.py&quot;, line 2304, in spawnebuild
   
retval=spawnebuild(actionmap[mydo][&quot;dep&quot;],actionmap,mysettings,debug,alwaysdep=alwaysdep,logfile=logfile)
  File &quot;/usr/lib/portage/pym/portage.py&quot;, line 2304, in spawnebuild
   
retval=spawnebuild(actionmap[mydo][&quot;dep&quot;],actionmap,mysettings,debug,alwaysdep=alwaysdep,logfile=logfile)
  File &quot;/usr/lib/portage/pym/portage.py&quot;, line 2304, in spawnebuild
   
retval=spawnebuild(actionmap[mydo][&quot;dep&quot;],actionmap,mysettings,debug,alwaysdep=alwaysdep,logfile=logfile)
  File &quot;/usr/lib/portage/pym/portage.py&quot;, line 2320, in spawnebuild
    droppriv=actionmap[mydo][&quot;args&quot;][1],logfile=logfile)
  File &quot;/usr/lib/portage/pym/portage.py&quot;, line 1603, in spawn
    return portage_exec.spawn_bash(mystring,env=env,**keywords)
  File &quot;/usr/lib/portage/pym/portage_exec.py&quot;, line 48, in spawn_bash
    return spawn(args,env=env,opt_name=opt_name,**keywords)
  File &quot;/usr/lib/portage/pym/portage_exec.py&quot;, line 83, in spawn
   
mypid.extend(spawn((&apos;tee&apos;,&apos;-i&apos;,&apos;-a&apos;,logfile),returnpid=True,fd_pipes={0:pr,1:1,2:2}))
TypeError: iteration over non-sequence


Expected Results:  
emerge should work in minimalistic environments.

[I--] [  ] app-admin/metalog-0.8_rc1-r1 (0)
[I--] [  ] sys-apps/pam-login-3.17 (0)
[I--] [  ] sys-fs/udev-058 (0)
[I--] [  ] sys-libs/pam-0.78-r2 (0)

Portage 2.0.51.22-r1 (default-linux/x86/2005.0, gcc-3.4.4, glibc-2.3.5-r0,
2.6.11.10 i686)
=================================================================
System uname: 2.6.11.10 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz
Gentoo Base System version 1.6.12
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
dev-lang/python:     2.3.5, 2.4.1
sys-apps/sandbox:    1.2.9
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5
sys-devel/binutils:  2.16-r1
sys-devel/libtool:   1.5.18
virtual/os-headers:  2.6.11-r1
ACCEPT_KEYWORDS=&quot;x86 ~x86&quot;
AUTOCLEAN=&quot;yes&quot;
CBUILD=&quot;i686-pc-linux-gnu&quot;
CFLAGS=&quot;-march=prescott -O2&quot;
CHOST=&quot;i686-pc-linux-gnu&quot;
CONFIG_PROTECT=&quot;/etc /usr/kde/2/share/config /usr/kde/3.3/env
/usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config
/var/qmail/control&quot;
CONFIG_PROTECT_MASK=&quot;/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d&quot;
CXXFLAGS=&quot;-march=prescott -O2&quot;
DISTDIR=&quot;/usr/portage/distfiles&quot;
FEATURES=&quot;autoconfig distlocks sandbox sfperms strict&quot;
GENTOO_MIRRORS=&quot;http://gentoo.inode.at/ rsync://ftp.snt.utwente.nl/gentoo
ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo
ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo
ftp://ftp.tu-clausthal.de/pub/linux/gentoo/ http://gentoo.oregonstate.edu
http://www.ibiblio.org/pub/Linux/distributions/gentoo&quot;
LINGUAS=&quot;en de&quot;
MAKEOPTS=&quot;-j3&quot;
PKGDIR=&quot;/usr/portage/packages&quot;
PORTAGE_TMPDIR=&quot;/var/tmp&quot;
PORTDIR=&quot;/usr/portage&quot;
PORTDIR_OVERLAY=&quot;/usr/local/portage&quot;
SYNC=&quot;rsync://rsync.de.gentoo.org/gentoo-portage&quot;
USE=&quot;x86 X aac aalib acpi alsa apache2 apm arts auctex avi bash-completion
bcmath berkdb bigger-fonts bitmap-fonts bzip2 bzlib c++ cairo cdparanoia cdr
chroot crypt css cups curl dba dhcp divx4linux dnd doc dts dv dvd emboss encode
escreen esd ethereal exif faad fam fastcgi fbcon ffmpeg fftw flac flatfile
foomaticdb fortran ftp gcc-libffi gcj gd gdbm gif gimp gimpprint gnutls gpm
graphviz gs gtk gtk2 guile imagemagick imlib ipv6 java jpeg junit kde latex ldap
libg++ libwww lirc lzo lzw mad maildir mailwrapper mikmod mime mjpeg mmx motif
mozilla moznocompose mozxmlterm mp3 mpeg mpeg2 mplayer mpm-worker mule mysql
ncurses net network nls no-old-linux nptl odbc ogg oggvorbis opengl operanom2
oss pam pdf pdflib perl php pic pie plotutils png postgres povray procmail
python qt quicktime rdesktop readline real recode samba sasl savedconfig sdl
slang smime sndfile sockets sox spell sse sse2 ssl svga tcltk tcpd tetex threads
tiff tokenizer transcode translator truetype truetype-fonts type1 type1-fonts
unicode usb userlocales utf8 v4l v4l2 vorbis wmf xanim xchattext xemacs xine xml
xml2 xmms xv xvid xvmc zlib linguas_en linguas_de userland_GNU kernel_linux
elibc_glibc&quot;
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>Martin.vGagern@gmx.net</who>
            <bug_when>2005-06-14 04:56:31 0000</bug_when>
            <thetext>OK, as I got no reply to this bug report, I found out that some other services
were stuck as well, namely fetchmail, cron and postfix. As I don&apos;t think they
all use PAM during normal operation, I believe that they all suffered from the
same problems when writing to /dev/log.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>Martin.vGagern@gmx.net</who>
            <bug_when>2005-06-14 07:37:34 0000</bug_when>
            <thetext>Created an attachment (id=61205)
autopsy of a pair of metalog processes

OK, this looks more and more like a metalog-only problem. I just had another
such lockup, decided to reboot my system, and got stuck when starting postfix -
again. So I guess that the inability to successfully start postfix is probably
caused by metalog as well, and all this PAM related issues were more or less
just Problems with metalog.

I just booted into runlevel 1, logged into two consoles, and continued to
runlevel 3. I got another lockup. I found out that &quot;/etc/init.d/metalog
restart&quot; does not kill the previousely running instances, they stay alive. This
gave me the opportunity to find out what happened to them. I attached some
program outputs.

First interesting thing is that both processes listen to /dev/log. It is my
understanding that this is not what the kernel daemon should do, but I might be
wrong there. I guess those other two sockets, 9778 and 9779, are just a pair of
pipes connecting those two processes. The master is stuck in the syscall
&quot;futex&quot;, while the kernel daemon is stuck in the syscall &quot;syslog&quot;.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>Martin.vGagern@gmx.net</who>
            <bug_when>2005-06-14 08:25:58 0000</bug_when>
            <thetext>Created an attachment (id=61208)
maps and status of the stale processes

I forgot to have a look at the maps and status info for attachment 61205.

This tells me that the futex is somewhere in glibc code. And I found that the
syslog call is infact to read messages from the kernel, so this looks like this
process might still work as expected, and it dies respond to a simple kill,
turning it into a zombie.
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>azarah@gentoo.org</who>
            <bug_when>2005-07-05 13:15:46 0000</bug_when>
            <thetext>Possible to try an later kernel or maybe sysklogd or such ?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>Martin.vGagern@gmx.net</who>
            <bug_when>2005-07-05 13:29:22 0000</bug_when>
            <thetext>I did fall back to sysklogd. I&apos;m not too keen to experiment with this system to
see if a new kernel does change anything, since those errors were rather severe
and I don&apos;t think this too lokely. Maybe when I find some more time, or if
someone has a more specific idea what might have caused this problem.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>azarah@gentoo.org</who>
            <bug_when>2005-07-05 13:39:08 0000</bug_when>
            <thetext>Understood.  I asked more to see if we can track it to metalog/kernel/glibc
issue ... is it working with sysklogd btw ?
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>Martin.vGagern@gmx.net</who>
            <bug_when>2005-07-05 13:51:06 0000</bug_when>
            <thetext>Yes, sysklogd never gave me any trouble. So by now I&apos;m rather sure this problem
is at least largely a metabug issue. Maybe I sould change the summary accordingly.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2005-07-05 20:52:42 0000</bug_when>
            <thetext>which version of metalog ?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>Martin.vGagern@gmx.net</who>
            <bug_when>2005-07-06 01:14:16 0000</bug_when>
            <thetext>This is metalog-0.8_rc1-r1, as stated in the original bug report.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>andrewdk@sbcglobal.net</who>
            <bug_when>2005-09-27 09:42:36 0000</bug_when>
            <thetext>I think I&apos;ve run across this bug or something similar to it this morning --
after doing a rebuild of the system -- when I try to login, it prompts for
password, I enter the correct password, and it just sits there for a minute and
then claims timeout. Through SSH, it doesn&apos;t even do that, just sits there
forever. The strange thing is that all of my services started fine, apache is
running and responding -- it&apos;s just that nothing is able to log in. I&apos;m not able
to access the box right now to verify with the init=/sbin/sulogin, but I will do
so asap (approx 1h 30m from now). Reproducable across 2 reboots (had to leave
for school before I solved it..)

Again this is after a complete toolchain/world rebuild with gcc-4.0.1 (which may
be part of the problem) but I&apos;ve got another system (this one I&apos;m using, in
fact) that has been running 100% gcc 4.0.1 for some time with no problems.. both
with metalog.

Again, not sure if this is related to this bug 100% but at least it sounds similar.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>andrewdk@sbcglobal.net</who>
            <bug_when>2005-09-27 11:51:29 0000</bug_when>
            <thetext>Alright folks, I have the answer to this bug I believe.

Check out this section of /etc/metalog.conf:

console logging :
 
 facility = &quot;*&quot;
 command = &quot;/usr/sbin/consolelog.sh&quot;

This is our culprit. My guess is that upon boot, metalog tries to execute that
same script for each line of dmesg and all the rest that it&apos;s missed so fast
that init just refuses the calls to that script from metalog because it&apos;s
basically bombing the system.

The contents of the script called are not exactly complex, nor is it just a
simple echo -- all I know is that disabling the console logging (which it is by
default) fixes the problem for me.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>andrewdk@sbcglobal.net</who>
            <bug_when>2005-09-27 11:56:48 0000</bug_when>
            <thetext>Sorry for the double post here but it seems that some recent version of metalog
changed that /usr/sbin/consolelog.sh script from a simple echo to what it is now
-- which apparently init doesn&apos;t like. _Not only this_, but since this script
may contain customized commands, shouldn&apos;t it be considered a protected config
file? This is one of the reasons why no one caught this right away--because no
one knew it had changed.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2005-09-27 12:01:30 0000</bug_when>
            <thetext>so you&apos;re saying the new dynamic one causes failure but the older one which was
a simple `echo` worked ?

why would the new one fail ?  by the time metalog is launched, /dev should be
populated and at the very least /dev/console should exist ...

if you add &apos;set -x&apos; to the beginning of the script, do you see useful output ?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2006-02-07 17:04:05 0000</bug_when>
            <thetext>metalog 8.0_rc1-r2 should address this</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>andrewdk@sbcglobal.net</who>
            <bug_when>2006-02-12 21:00:21 0000</bug_when>
            <thetext>Mmm, nope. Still eventually denies login.

For example:
perl -e &quot;while (true) { \`logger test\` }&quot;

Let it run for about a second, and you will no longer be able to log into your box, if you have console logging turned on in metalog.conf.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2006-04-19 15:23:44 0000</bug_when>
            <thetext>*** Bug 130497 has been marked as a duplicate of this bug. ***</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>zenith@zenith.dk</who>
            <bug_when>2007-05-19 21:11:04 0000</bug_when>
            <thetext>I just ran into this nasty bug as well.

I think it is related to these other bugs as well:
http://bugs.gentoo.org/show_bug.cgi?id=31277
http://bugs.gentoo.org/show_bug.cgi?id=177424

Namely the last one fixed it for me. The path was wrong, typing in the correct one fixes my problems.

It must be related to metalog, and I simply fail to see how a wrong path to a script should cause the system to be non-working, it is extremely critical!</thetext>
          </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="0"
              isprivate="0"
          >
            <attachid>61205</attachid>
            <date>2005-06-14 07:37 0000</date>
            <desc>autopsy of a pair of metalog processes</desc>
            <filename>metalog.txt</filename>
            <type>text/plain</type>
            <data encoding="base64">IyBwcyAtQyBtZXRhbG9nIC1PIGNtZAogIFBJRCBDTUQgICAgICAgICAgICAgICAgICAgICAgICAg
UyBUVFkgICAgICAgICAgVElNRSBDT01NQU5ECiA5MzA5IG1ldGFsb2cgW01BU1RFUl0gICAgICAg
ICAgICBTID8gICAgICAgIDAwOjAwOjAwIG1ldGFsb2cgW01BU1RFUl0gICAgICAgICAKIDkzMTAg
bWV0YWxvZyBbS0VSTkVMXSAgICAgICAgICAgIFMgPyAgICAgICAgMDA6MDA6MDAgbWV0YWxvZyBb
S0VSTkVMXSAgICAgICAgIAoxOTg4MSBtZXRhbG9nIFtNQVNURVJdICAgICAgICAgICAgUyA/ICAg
ICAgICAwMDowMDowMCBtZXRhbG9nIFtNQVNURVJdICAgICAgICAgCjE5ODgyIG1ldGFsb2cgW0tF
Uk5FTF0gICAgICAgICAgICBTID8gICAgICAgIDAwOjAwOjAwIG1ldGFsb2cgW0tFUk5FTF0gICAg
ICAgICAKCiMgbHMgLWwgL3Byb2MvOTN7MDksMTB9L2ZkCjkzMDkvZmQ6CnRvdGFsIDE1CmxyLXgt
LS0tLS0gIDEgcm9vdCByb290IDY0IEp1biAxNCAxNjoxMyAwIC0+IC9kZXYvbnVsbApsLXd4LS0t
LS0tICAxIHJvb3Qgcm9vdCA2NCBKdW4gMTQgMTY6MTMgMSAtPiAvZGV2L251bGwKbC13eC0tLS0t
LSAgMSByb290IHJvb3QgNjQgSnVuIDE0IDE2OjEzIDEwIC0+IC92YXIvbG9nL3NzaGQvY3VycmVu
dApsLXd4LS0tLS0tICAxIHJvb3Qgcm9vdCA2NCBKdW4gMTQgMTY6MTMgMTEgLT4gL3Zhci9sb2cv
bWFpbC9jdXJyZW50Cmwtd3gtLS0tLS0gIDEgcm9vdCByb290IDY0IEp1biAxNCAxNjoxMyAxMiAt
PiAvdmFyL2xvZy9mZXRjaG1haWwvY3VycmVudApsLXd4LS0tLS0tICAxIHJvb3Qgcm9vdCA2NCBK
dW4gMTQgMTY6MTMgMTMgLT4gL3Zhci9sb2cvY3JvbmQvY3VycmVudApsLXd4LS0tLS0tICAxIHJv
b3Qgcm9vdCA2NCBKdW4gMTQgMTY6MTMgMTQgLT4gL3Zhci9sb2cvcG9zdGZpeC9jdXJyZW50Cmwt
d3gtLS0tLS0gIDEgcm9vdCByb290IDY0IEp1biAxNCAxNjoxMyAyIC0+IC9kZXYvbnVsbApscnd4
LS0tLS0tICAxIHJvb3Qgcm9vdCA2NCBKdW4gMTQgMTY6MTMgMyAtPiBzb2NrZXQ6Wzk3NzZdCmxy
d3gtLS0tLS0gIDEgcm9vdCByb290IDY0IEp1biAxNCAxNjoxMyA0IC0+IHNvY2tldDpbOTc3OF0K
bHJ3eC0tLS0tLSAgMSByb290IHJvb3QgNjQgSnVuIDE0IDE2OjEzIDUgLT4gc29ja2V0Ols5Nzc5
XQpsLXd4LS0tLS0tICAxIHJvb3Qgcm9vdCA2NCBKdW4gMTQgMTY6MTMgNiAtPiAvdmFyL2xvZy9l
dmVyeXRoaW5nL2N1cnJlbnQKbC13eC0tLS0tLSAgMSByb290IHJvb3QgNjQgSnVuIDE0IDE2OjEz
IDcgLT4gL3Zhci9sb2cvY3JpdGljYWwvY3VycmVudApsLXd4LS0tLS0tICAxIHJvb3Qgcm9vdCA2
NCBKdW4gMTQgMTY6MTMgOCAtPiAvdmFyL2xvZy9rZXJuZWwvY3VycmVudApsLXd4LS0tLS0tICAx
IHJvb3Qgcm9vdCA2NCBKdW4gMTQgMTY6MTMgOSAtPiAvdmFyL2xvZy9ldmVyeXRoaW5nL2N1cnJl
bnQKCjkzMTAvZmQ6CnRvdGFsIDYKbHIteC0tLS0tLSAgMSByb290IHJvb3QgNjQgSnVuIDE0IDE2
OjEzIDAgLT4gL2Rldi9udWxsCmwtd3gtLS0tLS0gIDEgcm9vdCByb290IDY0IEp1biAxNCAxNjox
MyAxIC0+IC9kZXYvbnVsbApsLXd4LS0tLS0tICAxIHJvb3Qgcm9vdCA2NCBKdW4gMTQgMTY6MTMg
MiAtPiAvZGV2L251bGwKbHJ3eC0tLS0tLSAgMSByb290IHJvb3QgNjQgSnVuIDE0IDE2OjEzIDMg
LT4gc29ja2V0Ols5Nzc2XQpscnd4LS0tLS0tICAxIHJvb3Qgcm9vdCA2NCBKdW4gMTQgMTY6MTMg
NCAtPiBzb2NrZXQ6Wzk3NzhdCmxyd3gtLS0tLS0gIDEgcm9vdCByb290IDY0IEp1biAxNCAxNjox
MyA1IC0+IHNvY2tldDpbOTc3OV0KCiMgbmV0c3RhdCAteGEgfCBncmVwICc5NzdbNjg5XScKdW5p
eCAgMzEgICAgIFsgXSAgICAgICAgIERHUkFNICAgICAgICAgICAgICAgICAgICA5Nzc2ICAgL2Rl
di9sb2cKdW5peCAgMyAgICAgIFsgXSAgICAgICAgIFNUUkVBTSAgICAgQ09OTkVDVEVEICAgICA5
Nzc5ICAgCnVuaXggIDMgICAgICBbIF0gICAgICAgICBTVFJFQU0gICAgIENPTk5FQ1RFRCAgICAg
OTc3OCAgIAoKIyBzdHJhY2UgLXAgOTMwOQpQcm9jZXNzIDkzMDkgYXR0YWNoZWQgLSBpbnRlcnJ1
cHQgdG8gcXVpdApmdXRleCgweGI3ZmFlZWNjLCBGVVRFWF9XQUlULCAyLCBOVUxMCgojIHN0cmFj
ZSAtcCA5MzEwClByb2Nlc3MgOTMxMCBhdHRhY2hlZCAtIGludGVycnVwdCB0byBxdWl0CnN5c2xv
ZygweDIsIDB4YmZmZmRkNzAsIDB4ODAwCg==
</data>        

          </attachment>
          <attachment
              isobsolete="0"
              ispatch="0"
              isprivate="0"
          >
            <attachid>61208</attachid>
            <date>2005-06-14 08:25 0000</date>
            <desc>maps and status of the stale processes</desc>
            <filename>metalog2.txt</filename>
            <type>text/plain</type>
            <data encoding="base64">PT0+IC9wcm9jLzkzMDkvbWFwcyA8PT0KMDgwNDgwMDAtMDgwNGQwMDAgci14cCAwMDAwMDAwMCAw
ODowMSAxOTgyOTUwICAgIC91c3Ivc2Jpbi9tZXRhbG9nIChkZWxldGVkKQowODA0ZDAwMC0wODA0
ZTAwMCBydy1wIDAwMDA1MDAwIDA4OjAxIDE5ODI5NTAgICAgL3Vzci9zYmluL21ldGFsb2cgKGRl
bGV0ZWQpCjA4MDRlMDAwLTA4MDZmMDAwIHJ3LXAgMDgwNGUwMDAgMDA6MDAgMCAKYjdlOWQwMDAt
YjdlOWUwMDAgcnctcCBiN2U5ZDAwMCAwMDowMCAwIApiN2U5ZTAwMC1iN2ZhYTAwMCByLXhwIDAw
MDAwMDAwIDA4OjAxIDMzMzA3NzQgICAgL2xpYi90bHMvbGliYy0yLjMuNS5zbwpiN2ZhYTAwMC1i
N2ZhYjAwMCAtLS1wIDAwMTBjMDAwIDA4OjAxIDMzMzA3NzQgICAgL2xpYi90bHMvbGliYy0yLjMu
NS5zbwpiN2ZhYjAwMC1iN2ZhYzAwMCByLS1wIDAwMTBjMDAwIDA4OjAxIDMzMzA3NzQgICAgL2xp
Yi90bHMvbGliYy0yLjMuNS5zbwpiN2ZhYzAwMC1iN2ZhZjAwMCBydy1wIDAwMTBkMDAwIDA4OjAx
IDMzMzA3NzQgICAgL2xpYi90bHMvbGliYy0yLjMuNS5zbwpiN2ZhZjAwMC1iN2ZiMTAwMCBydy1w
IGI3ZmFmMDAwIDAwOjAwIDAgCmI3ZmIxMDAwLWI3ZmMwMDAwIHIteHAgMDAwMDAwMDAgMDg6MDEg
MTk2NjQxNSAgICAvdXNyL2xpYi9saWJwY3JlLnNvLjAuMC4xCmI3ZmMwMDAwLWI3ZmMxMDAwIHJ3
LXAgMDAwMGYwMDAgMDg6MDEgMTk2NjQxNSAgICAvdXNyL2xpYi9saWJwY3JlLnNvLjAuMC4xCmI3
ZmMxMDAwLWI3ZmMyMDAwIHJ3LXAgYjdmYzEwMDAgMDA6MDAgMCAKYjdmZTIwMDAtYjdmZWIwMDAg
cnctcCBiN2ZlMjAwMCAwMDowMCAwIApiN2ZlYjAwMC1iODAwMDAwMCByLXhwIDAwMDAwMDAwIDA4
OjAxIDIwNTI2ODIgICAgL2xpYi9sZC0yLjMuNS5zbwpiODAwMDAwMC1iODAwMjAwMCBydy1wIDAw
MDE0MDAwIDA4OjAxIDIwNTI2ODIgICAgL2xpYi9sZC0yLjMuNS5zbwpiZmZlYjAwMC1jMDAwMDAw
MCBydy1wIGJmZmViMDAwIDAwOjAwIDAgCmZmZmZlMDAwLWZmZmZmMDAwIC0tLXAgMDAwMDAwMDAg
MDA6MDAgMCAKCj09PiAvcHJvYy85MzEwL21hcHMgPD09CjA4MDQ4MDAwLTA4MDRkMDAwIHIteHAg
MDAwMDAwMDAgMDg6MDEgMTk4Mjk1MCAgICAvdXNyL3NiaW4vbWV0YWxvZyAoZGVsZXRlZCkKMDgw
NGQwMDAtMDgwNGUwMDAgcnctcCAwMDAwNTAwMCAwODowMSAxOTgyOTUwICAgIC91c3Ivc2Jpbi9t
ZXRhbG9nIChkZWxldGVkKQowODA0ZTAwMC0wODA2ZjAwMCBydy1wIDA4MDRlMDAwIDAwOjAwIDAg
CmI3ZTlkMDAwLWI3ZTllMDAwIHJ3LXAgYjdlOWQwMDAgMDA6MDAgMCAKYjdlOWUwMDAtYjdmYWEw
MDAgci14cCAwMDAwMDAwMCAwODowMSAzMzMwNzc0ICAgIC9saWIvdGxzL2xpYmMtMi4zLjUuc28K
YjdmYWEwMDAtYjdmYWIwMDAgLS0tcCAwMDEwYzAwMCAwODowMSAzMzMwNzc0ICAgIC9saWIvdGxz
L2xpYmMtMi4zLjUuc28KYjdmYWIwMDAtYjdmYWMwMDAgci0tcCAwMDEwYzAwMCAwODowMSAzMzMw
Nzc0ICAgIC9saWIvdGxzL2xpYmMtMi4zLjUuc28KYjdmYWMwMDAtYjdmYWYwMDAgcnctcCAwMDEw
ZDAwMCAwODowMSAzMzMwNzc0ICAgIC9saWIvdGxzL2xpYmMtMi4zLjUuc28KYjdmYWYwMDAtYjdm
YjEwMDAgcnctcCBiN2ZhZjAwMCAwMDowMCAwIApiN2ZiMTAwMC1iN2ZjMDAwMCByLXhwIDAwMDAw
MDAwIDA4OjAxIDE5NjY0MTUgICAgL3Vzci9saWIvbGlicGNyZS5zby4wLjAuMQpiN2ZjMDAwMC1i
N2ZjMTAwMCBydy1wIDAwMDBmMDAwIDA4OjAxIDE5NjY0MTUgICAgL3Vzci9saWIvbGlicGNyZS5z
by4wLjAuMQpiN2ZjMTAwMC1iN2ZjMjAwMCBydy1wIGI3ZmMxMDAwIDAwOjAwIDAgCmI3ZmViMDAw
LWI4MDAwMDAwIHIteHAgMDAwMDAwMDAgMDg6MDEgMjA1MjY4MiAgICAvbGliL2xkLTIuMy41LnNv
CmI4MDAwMDAwLWI4MDAyMDAwIHJ3LXAgMDAwMTQwMDAgMDg6MDEgMjA1MjY4MiAgICAvbGliL2xk
LTIuMy41LnNvCmJmZmViMDAwLWMwMDAwMDAwIHJ3LXAgYmZmZWIwMDAgMDA6MDAgMCAKZmZmZmUw
MDAtZmZmZmYwMDAgLS0tcCAwMDAwMDAwMCAwMDowMCAwIAoKPT0+IC9wcm9jLzkzMDkvc3RhdHVz
IDw9PQpOYW1lOgltZXRhbG9nClN0YXRlOglTIChzbGVlcGluZykKU2xlZXBBVkc6CTg4JQpUZ2lk
Ogk5MzA5ClBpZDoJOTMwOQpQUGlkOgkxClRyYWNlclBpZDoJMApVaWQ6CTAJMAkwCTAKR2lkOgkw
CTAJMAkwCkZEU2l6ZToJMzIKR3JvdXBzOgkKVm1TaXplOgkgICAgMTU0MCBrQgpWbUxjazoJICAg
ICAgIDAga0IKVm1SU1M6CSAgICAgNjcyIGtCClZtRGF0YToJICAgICAxODQga0IKVm1TdGs6CSAg
ICAgIDg0IGtCClZtRXhlOgkgICAgICAyMCBrQgpWbUxpYjoJICAgIDEyMTYga0IKVm1QVEU6CSAg
ICAgIDE2IGtCClRocmVhZHM6CTEKU2lnUG5kOgkwMDAwMDAwMDAwMDAwMDAwClNoZFBuZDoJMDAw
MDAwMDAwMDAxMDAwMApTaWdCbGs6CTAwMDAwMDAwMDAwMTQwMDAKU2lnSWduOgkwMDAwMDAwMDAw
MDAwMDAwClNpZ0NndDoJMDAwMDAwMDAwMDAxNWEwNwpDYXBJbmg6CTAwMDAwMDAwMDAwMDAwMDAK
Q2FwUHJtOgkwMDAwMDAwMGZmZmZmZWZmCkNhcEVmZjoJMDAwMDAwMDBmZmZmZmVmZgoKPT0+IC9w
cm9jLzkzMTAvc3RhdHVzIDw9PQpOYW1lOgltZXRhbG9nClN0YXRlOglTIChzbGVlcGluZykKU2xl
ZXBBVkc6CTg4JQpUZ2lkOgk5MzEwClBpZDoJOTMxMApQUGlkOgk5MzA5ClRyYWNlclBpZDoJMApV
aWQ6CTAJMAkwCTAKR2lkOgkwCTAJMAkwCkZEU2l6ZToJMzIKR3JvdXBzOgkKVm1TaXplOgkgICAg
MTUwNCBrQgpWbUxjazoJICAgICAgIDAga0IKVm1SU1M6CSAgICAgNTA4IGtCClZtRGF0YToJICAg
ICAxNDgga0IKVm1TdGs6CSAgICAgIDg0IGtCClZtRXhlOgkgICAgICAyMCBrQgpWbUxpYjoJICAg
IDEyMTYga0IKVm1QVEU6CSAgICAgIDE2IGtCClRocmVhZHM6CTEKU2lnUG5kOgkwMDAwMDAwMDAw
MDAwMDAwClNoZFBuZDoJMDAwMDAwMDAwMDAwMDAwMApTaWdCbGs6CTAwMDAwMDAwMDAwMDAwMDAK
U2lnSWduOgkwMDAwMDAwMDAwMDAwYTAwClNpZ0NndDoJMDAwMDAwMDAwMDAxNTAwNwpDYXBJbmg6
CTAwMDAwMDAwMDAwMDAwMDAKQ2FwUHJtOgkwMDAwMDAwMGZmZmZmZWZmCkNhcEVmZjoJMDAwMDAw
MDBmZmZmZmVmZgoKIyBraWxsIDkzMTAKCj09PiAvcHJvYy85MzEwL3N0YXR1cyA8PT0KTmFtZToJ
bWV0YWxvZwpTdGF0ZToJWiAoem9tYmllKQpTbGVlcEFWRzoJODglClRnaWQ6CTkzMTAKUGlkOgk5
MzEwClBQaWQ6CTkzMDkKVHJhY2VyUGlkOgkwClVpZDoJMAkwCTAJMApHaWQ6CTAJMAkwCTAKRkRT
aXplOgkwCkdyb3VwczoJClRocmVhZHM6CTEKU2lnUG5kOgkwMDAwMDAwMDAwMDAwMDAwClNoZFBu
ZDoJMDAwMDAwMDAwMDAwMDAwMApTaWdCbGs6CTAwMDAwMDAwMDAwMDQwMDAKU2lnSWduOgkwMDAw
MDAwMDAwMDAwYTAwClNpZ0NndDoJMDAwMDAwMDAwMDAxNTAwNwpDYXBJbmg6CTAwMDAwMDAwMDAw
MDAwMDAKQ2FwUHJtOgkwMDAwMDAwMGZmZmZmZWZmCkNhcEVmZjoJMDAwMDAwMDBmZmZmZmVmZgo=
</data>        

          </attachment>
    </bug>

</bugzilla>