|
Tripwire Segmentation Fault
Can someone please help me figure out this problem I'm having with Tripwire, PLEASE!
I did the install from the .bin.tar.gz file as it said. That went fine. I entered my two passphrases - no problems. I get to 'tripwire -m i' and i end up with this: Parsing policy file: ... Generating the database... ***Processing the Unix File System*** Software interrupt forced exit: Segmentation Fault I've been all over the internet looking for help but haven't found anything. If nothing else, can someone tell me how to uninstall this from slackware? I didn't use pkgtool (tried but it was totally unsuccessful) so that's not an option. All help is appreciated!! |
Sorry this is not an answer, but I am running RedHat ES 3.0 and I am getting the exact same error. Please let me know if you resolve this.
Thanks, Rob |
I don't use slack but I see that you're trying to generate the database right? If so, why run the command "'tripwire -m i"? Have you tried issueing this command: "tripwire --init"??
-twantrd |
it's the same thing I believe; at least, they both give the same response. Thanks for your help though.
Still searching............ |
Software interrupt forced exit: Segmentation Fault
Hi,
Setting up the database has been graceful since no segmentation faults occured. When checking back that very database, here was the well known nice message after a few seconds: Software interrupt forced exit: Segmentation Fault How dear could that be ? Well I first asked tripwire to initialize the database on a remote nfs partition ! So I had a try in unmounting it to store database locally, then back to : tripwire --init. Please enter your local passphrase: Parsing policy file: /etc/tripwire/tw.pol Generating the database... *** Processing Unix File System *** Software interrupt forced exit: Segmentation Fault What's up with tripwire.org ? This free soft seems quite messy ! Does it rely on unstable hard disk routines ? do someone have a further hit ? tired for now. |
Join the crowd and don't expect much help around here on this topic. This thread was started a while ago an I've gotten very little response.
If you happen to learn something on the topic, please post it here so I can learn what it is. I'll do the same. |
Uhm. Not a fix, but I would like to point out there's two excellent alternatives around: Aide and Samhain. Both are OSS, up to date, well maintained and have a large userbase.
|
Thanks unSpawn. I'll definitely look into those. It would be great to have the tripwire problem answered but the number one goal is protecting my computers so alternatives are always appreciated.
|
If you made sure you followed ALL the steps wrt building/installing/configuring tripwire, then I spose you could run tripwire from strace with the appropriate arguments and post it, together with your distro details, on the tripwire (developers-)mailinglist (if there is such a list):
"strace -v tripwire tripwire_args 2>&1|tee /tmp/trip_strace.log". |
I am having the same problem. This is what I have found.
>Thanks to Philippe Vogel, who pointed out to me that the reason tripwire doesn't >work in 9.0 is due to gcc 3.x, I figured out that there is no reason why the >tripwire that was shipped with suse 8.2 shouldn't work. > >ftp://ftp.suse.com/pub/suse/i386/8.2....1-25.i586.rpm > >This installs and appears to work perfectly on a Suse 9.0 system. Why the Suse >people don't simply copy the above into the 9.0 tree is quite beyond me, but >for anyone that wants to use tripwire, there's the solution. I'll bring my >cluebat to suse booth at Linux Expo later this month, perhaps that will help... I am using gcc 3.2.2 so this seems like the potential problem. |
I have tripwire installed on another RH9 machine that has gcc 3.2.2 but it also has 2.96 on it.
My next step is to install gcc 2.96 and see if I get a positive result. |
in the README.compile file that is included with Tripwire source it states at the top:
Make sure that you have gcc version 2.96 installed, and make sure that the executables g++ and c++ are in your path and that the first instance of them in your path are indeed the 2.96 binaries. That should fix your problem. |
I came across this thread while looking for answers to the same problem. I also came across this. http://www.frenchfries.net/paul/tripwire/ This worked for me on my slackware 10.0 box. Hope this helps.
-digitalFX |
Hi, I don't know if you guys ever got this problem sorted but I have found that the rpm version of tripwire for RH9 works for RH ES 3.0.
I too was getting the segmentation faults when using the latest version from tripwire.org but once I got the rpm from http://download.fedora.us/fedora/redhat/9/i386/RPMS.os/ I had no problems installing and running # ./twinstall.sh then # tripwire --init Hope this helps. |
Quote:
As far as uninstalling it from Slack, couldn't one just do: $ tar -ztf tripwire*.tgz to get a list of what files were installed, and then undo them manually? I thought that was part of the point of tgz-based package-management. Is that wrong? G |
| All times are GMT -5. The time now is 08:20 PM. |