I noticed the audit kernel failed on booting the server so I checked and found there was an update for this package. (P.S I am new to Linux)

When I use the up2date utility and try to install the audit package I get the following error mesage:

There was a fatal RPM install error:The message was: Failed running transaction of packages'file /usr/share/man/man8/auditd.8.gz,OL))from install audit 1.0.14.1.EL4 conflicts with file from package laus-0.1-54RHEL3, (7, 'usr/share/man/man8/auditd.8.gz,OL)).

There seems to be a problem with the current file, my question is, how to go about resolving this problem?, can I just delete the old file and run the update again or is there a specific procedure that needs to be carried out?

Why is this (laus-0.1-54RHEL3) installed or why are you attempting to install the audit 1.0.14.1.EL4 rpm package??? One or the other is wrong. Assuming from your profile that your running RHEL4 then remove the EL3 package (and any other packages from/for EL3);

rpm -e laus-0.1.54RHEL3

If in fact you are running EL3 then update the laus rpm package instead.

A quick check to know which version are you running; cat /etc/*release

If your running EL3 then what did you do to your up2date configuration???

I am running EL4, don't know how ver EL3 got on as ver EL4 was installed from outset, I know there has been a history of outside companies installing software. so can I just delete the ver EL3 file from the folder without causing system problems?

It should have never been installed in the first place, it is for RHEL3 not RHEL4. To be on the safe side of things do first; rpm -e laus-0.1.54RHEL3 --test ;just to make sure nothing else is also wrong. If OK then repeat the command minus the --test switch.


On a side note, no outside vendor should be installing anything without the administrator of the system(s) knowledge and/or permission. As a suggestion change the root password and if needed suspend any outside accounts. The outside vendor that is responsible for the installation of the laus rpm package should be replaced or at the very least put on notice and maybe billed for this. If the outside vendor(s) does not know the difference between RHEL4 and RHEL3 then they may not be the best choice.

FYI: the only way this could have been installed is by someone doing maybe a force install or adding other packages that are not meant for RHEL4;

$ rpm -Uvh laus*.rpm --test
warning: laus-0.1-70RHEL3.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 025e513b
error: Failed dependencies:
liblaus.so.1()(64bit) is needed by laus-0.1-70RHEL3.x86_64
liblaussrv.so.0()(64bit) is needed by laus-0.1-70RHEL3.x86_64


So you might also have a laus-lib package installed also which needs to be removed, might as well check; rpm -qa laus-lib ;and if installed then remove this as well.

I ran the command, rpm -e laus-0.1.54RHEL3 -- test and the response was that the package is not installed, I ran up2date again and tried to install the audit package just to verify the error message and it still comes up with the exact message as in my first post!, any other ideas how I could resolve this issue.

Thanks!

Hmmm........ Lets do one final check please; rpm -qa 'laus*'

If it comes back with nothing then manually install the new audit rpm package;

rpm -Uvh audit-1.0.14-1.EL4*.rpm --force

If it comes back with results then try the command above and then clean/recreate the rpm database, follow the directions here (they are a bit dated but do work);

http://www.rpm.org/hintskinks/repairdb-2003-06/

.

ran rpm -qa 'laus*' returned:

laus-0.1-54RHEL3

So remove it; rpm -e laus

If it fails then try adding the --nodeps switch to the command; rpm -e laus --nodeps

tried both commands and returned:

error: %preun(laus-0.1-54RHEL3.i386) scriptlet failed, exit status 1

Just force the install of the audit rpm package. Looks like a bug in the spec file used to build the laus rpm package is causing a problem.

tried rpm -Uvh audit-1.0.14-1.EL4*.rpm --force
returned

rror: File not found by glob: audit-1.0.14-1.EL4*.rpm

You have to have the file locally, download it or use the rpm command with the full path where (yes URL paths are allowed) the rpm package is located.

This is an example of using rpm with the full path (URL), warning the command is really long as I did all three audit packages;


.