[vox-tech] Segmentation Fault with RPM --rebuilddb

[Shawn P. Neugebauer]

I don't believe you've said what version of RedHat you're running.
Also, specifically, what version of rpm are you running?
"rpm -q rpm" would suffice.

Assuming it's RedHat 7.x, see:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=73198
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=56524
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=78782
for clues and information.  You should do a few other searches
in bugzilla.  The gist of these bug reports is:  upgrade to rpm 4.1
and try that, re-install if you used ximian or redcarpet or some
other "unsupported" thing, or file bug report---looks like the
guy that's supporting rpm is pretty quick to respond and willing
to look individually at your database.

shawn.

On Friday 03 January 2003 04:16 pm, Richard Crawford wrote:
> On Fri, 2003-01-03 at 11:34, ME wrote:
> > Since it is immediate, and we see no other items in the trace, I would
> > expect it is not a path issue with symlinks. It is sounding more and more
> > like a file problem. Like there is an attempt to open a file (earlier)
> > that is assumed to allready be open (no checking) and now, as we are
> > getting to writing to the file descriptor, it is suddenly found to not be
> > valid, or ? I guess it could be cause by a filesystem problem at the
> > point on disk where one of the files it uses is stored (seems unlikely)
>
> That would be odd...  I have seen no other indications of any problems.
>
> > The suggestion made by Charles Polisher is a good one, and puts you on
> > what I would expect to be a good track. Try to find files used by this
> > process of "rpm --rebuilddb" and move them (backup) to a different
> > location. Then re-run the program to see if it segfaults.
>
> I removed all of the /var/lib/rpm/__db* files, and moved all of the
> files under /var/lib/rpmrebuilddb.* directories to a backup directory.
> Still got a segmentation fault.  I also tried moving all files in
> /var/lib/rpm to a backup directory, and got all sorts of interesting
> errors... before realizing that was the wrong thing to do and I replaced
> the files. ;-)