On Mon, Sep 27, 2004 at 11:58:12AM +0200, Stefan Goessling-Reisemann wrote:
> Hello List!
>
> I have not gotten any response to my problem (see below), so I take the
> liberty to ask my questions once more. I hope you do not feel offended.
>
> Best regards, STefan
>
> ---------- Forwarded message ----------
> Date: Wed, 22 Sep 2004 11:09:04 +0200
> From: Stefan Gößling-Reisemann <debian-user@lists.debian.org>
>
> Dear List,
>
> at the beginning of September I did an "apt-get update" and "apt-get
> upgrade" on a Woody installation. The upgraded packages were (IIRC)
> libpng2/3 and rsync. Exactly on that day tripwire stopped working, i.e. it
> delivers a segmentation fault. The rest of the system seemed to work fine
> at first, until I discovered recently that also dpkg creates a segfault.
>
> The system was setup by two CS students at our university, so I don't know
> all the details of the installation. I know that they have compiled their
> own kernel (2.4.19). They claim to have added two extra drivers (as
> modules) (via-rhine.c:v1.10-LK1.1.14 and sundance.c:v1.01b 17-Jan-2002).
> But aren't these part of the 2.4.19 source??
Hi,
are you aware that many of these packages are awailable IN debian or at
most available as backports. The whole point of using debian is the
quality assurance. And most packages(samba,kernel and maybe the rhine
module) have adequet default configurations. This would make upgrades
easiser and assure that you can track further problems.
Also, check the debian-user archives and the bug track system
(bugs.debian.org/PKGNAME) for hints. Also, give a trace of the command
like with 'script' or 'CMD > logfile'.
-Kev
>
> The tripwire package is also compiled from sources (version 2.3.1.2), as
> is the samba suite (version 2.2.9). All the rest is standard Woody, as far
> as I know.
>
> I have done an strace of a call to tripwire and dpkg, they end with the
> following lines:
>
> strace of tripwire
> ==================
>
> read(3, "# /etc/nsswitch.conf\n#\n# Example"..., 4096) = 465
> read(3, "", 4096) = 0
> close(3) = 0
> munmap(0x40076000, 4096) = 0
> --- SIGSEGV (Segmentation fault) ---
> write(2, "Software interrupt forced exit: "..., 51) = 51
> munmap(0x40077000, 4096) = 0
> _exit(8) = ?
>
>
> strace of dpkg
> ==============
>
> mremap(0x4018f000, 1007616, 1011712, MREMAP_MAYMOVE) = 0x4018f000
> mremap(0x4018f000, 1011712, 1015808, MREMAP_MAYMOVE) = 0x4018f000
> mremap(0x4018f000, 1015808, 1019904, MREMAP_MAYMOVE) = 0x4018f000
> mremap(0x4018f000, 1019904, 1024000, MREMAP_MAYMOVE) = 0x402b2000
> --- SIGSEGV (Segmentation fault) ---
> +++ killed by SIGSEGV +++
>
>
> I have run memcheck for around 3 hours (6 passes) with no errors. I have
> also done an fsck on all partitions (except swap).
>
> Any ideas where to look? How would I further analyse the problem?
>
> Best regards and thanks to everyone willing to help,
> Stefan (debian @ goessling . de)
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
--
(__)
(oo)
/------\/
/ | ||
* /\---/\
~~ ~~
...."Have you mooed today?"...
Attachment:
signature.asc
Description: Digital signature