[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#190110: libc6: Sub-processes flaking out.



Package: libc6
Version: 2.3.1-14
Severity: normal

I'm not sure this is the right package to file against, but it
feels like the closest thing.

This bug is probably identical to #147183.  That was marked as
"unreproducable" and the thread on the bug indicates that
everyone thought it was a hardware problem.  I am seeing similar
symptoms and have pretty much eliminated the possibility of a
hardware problem.

Symptoms:
    - Sub-processes for "debuild -uc -us" flakes out
      unpredictably.  Sometimes it'll flake at dh_clean,
      sometimes at the .deb creation, sometimes on dh_fixperms,
      etc.  Almost always flakes out, but rarely in the same
      place twice in a row.  Sample output:

  make[2]: Entering directory `/virtual/everybody.org/user/mah/work/deb-src/gnus-CVS/texi'
  /bin/sh ../mkinstalldirs /virtual/everybody.org/user/mah/work/deb-src/gnus-CVS/debian/ognus/usr/share/info
  make[2]: *** wait: No child processes.  Stop.
  make[2]: *** Waiting for unfinished jobs....
  make[2]: *** wait: No child processes.  Stop.
  make[1]: *** [install] Error 2
  make[1]: Leaving directory `/virtual/everybody.org/user/mah/work/deb-src/gnus-CVS'
  make: *** [install] Error 2
  debuild: fatal error at line 456:
  dpkg-buildpackage failed!

    - Apache starts up normally during startup, but after startup
      it can't startup.  Running "strace -o /tmp/t
      /usr/sbin/apache -F" and examining the last bit of the file
      generated shows:

  munmap(0x40018000, 4096)                = 0
  munmap(0x40012000, 4096)                = 0
  semget(1, 4096, 0x873b1e0|0640)         = -1 ENOSYS (Function not implemented)

    - General aggrevation!

So, why am I so sure that this isn't a hardware issue?  I began
seeing this problem on two separate machines.  Both are set to
apt-get from "stable" falling back to "testing" when necessary.
I've upgraded to libc6 from "testing" on both.  That seems to be
when the problems started showing up.

But that isn't proof enough.

In one of the machines, I have a spare disk.  I did new Debian
install on that machine and then did a "dist-upgrade" to
testing.  The new install works flawlessly -- even compiling a
kernel (my test for hardware problems).

Perhaps it is a problem between the keyboard and the chair, but
this feels like a problem in the upgrade process -- perhaps some
dependencies are set wrong.

Ideas?

Mark.

-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux thetick 2.4.18-686 #1 Sat Aug 31 18:44:27 CDT 2002 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages libc6 depends on:
ii  libdb1-compat                 2.1.3-7    The Berkeley database routines [gl



Reply to: