Topic: Please help, I have made a BIG boo boo!

[Cyrus Bharda]

Howdy,

Well I was playing around with messagewall and thought I had it down pat on my test server, so installed it on my production server.

Since then my server stopped sending and recieving email, so I thought I'll just uninstall it, but it would not, it would crash in the middle of the uninstall for some reason, tracked it down to BitDefender, uninstalled it and then tried uninstalling it again.

This time it worked, sort of, I had installed these rpms:

e-smith-messagewall-0.1-5cf1.noarch.rpm  
e-smith-messagewall-0.1-5cf6.noarch.rpm
messagewall-1.0.8-1.i386.rpm
firedns-0.1.30-1cf1.i386.rpm    
firestring-0.9.1-1cf1.i386.rpm

And when I went to uninstall the first it worked, but then when I went to uninstall the second one, I got this:

[root@Tyr messagewall]# rpm -e e-smith-messagewall-0.1-5cf6
error: "e-smith-messagewall-0.1-5cf6" specifies multiple packages
[root@Tyr messagewall]# rpm -e e-smith-messagewall-0.1-5cf1
error: package e-smith-messagewall-0.1-5cf1 is not installed
[root@Tyr messagewall]# rpm -e messagewall
error: removing these packages would break dependencies:
        messagewall is needed by e-smith-messagewall-0.1-5cf6
[root@Tyr messagewall]# rpm -e firestring
error: removing these packages would break dependencies:
        firestring is needed by firedns-0.1.30-1cf1
        libfirestring.so   is needed by firedns-0.1.30-1cf1
        libfirestring.so   is needed by messagewall-1.0.8-1
[root@Tyr messagewall]# rpm -e firedns
error: removing these packages would break dependencies:
        libfiredns.so   is needed by messagewall-1.0.8-1

So how do I force it to uninstall the e-smith-messagewall package so I can uninstall the rest of the packages?

Thanks for your time!

Cyrus Bharda

[Charlie Brady]

Cyrus Bharda wrote:

> So how do I force it to uninstall the e-smith-messagewall
> package so I can uninstall the rest of the packages?

You don't need to uninstall the packages, just disable messagewall, and re-enable smtpfront-qmail (or your choice of smtp daemon). If you haven't added a config db entry to disable messagewall (tsk! tsk!) then just delete the files, symlinks or template fragments which start messagewall.

Worry about cleaning up the rpm database later.

Charlie

[Cyrus Bharda]

Got it,

rpm -e --nodeps nameofpackage

did it, whew

Now just have to figure out what messagewall needs to be done to work with BitDefender

Cyrus Bharda

[Cyrus Bharda]

Charlie,

So how do I go about restoring smptfront-qmail to it's default parameters, I have deleted all the messagewall files and rebooted, but I think messagewall changes the listening port for smtpfront-qmail, so now I can recieve, but not send.

Thanks a lot for your help!

Cyrus Bharda

[Cyrus Bharda]

OK, noticed this, anyone care to explain?

[root@Tyr messagewall]# rpm -qa e-smith-messagewall
e-smith-messagewall-0.1-5cf1
e-smith-messagewall-0.1-5cf1
[root@Tyr messagewall]#

Tried this too but didnt help:

[root@Tyr messagewall]# rpm --rebuilddb
[root@Tyr messagewall]# rpm -qa e-smith-messagewall
e-smith-messagewall-0.1-5cf1
e-smith-messagewall-0.1-5cf1
[root@Tyr messagewall]#

Hmmmmmmm really wierd now!

Cyrus Bharda

[Graeme Fleming]

Try /sbin/e-smith/db configuration to list out your setup info - may find what you need here

[Cyrus Bharda]

Graeme,

I dont understand what I am looking at:

[root@Tyr messagewall]# /sbin/e-smith/db configuration
usage:
    /sbin/e-smith/db dbfile keys
    /sbin/e-smith/db dbfile print [key]
    /sbin/e-smith/db dbfile show [key]
    /sbin/e-smith/db dbfile get key
    /sbin/e-smith/db dbfile set key type [prop1 val1] [prop2 val2] ...
    /sbin/e-smith/db dbfile setdefault key type [prop1 val1] [prop2 val2] ...
    /sbin/e-smith/db dbfile delete key
    /sbin/e-smith/db dbfile printtype [key]
    /sbin/e-smith/db dbfile gettype key
    /sbin/e-smith/db dbfile settype key type
    /sbin/e-smith/db dbfile printprop key [prop1] [prop2] [prop3] ...
    /sbin/e-smith/db dbfile getprop key prop
    /sbin/e-smith/db dbfile setprop key prop1 val1 [prop2 val2] [prop3 val3] ...
    /sbin/e-smith/db dbfile delprop key prop1 [prop2] [prop3] ...
[root@Tyr messagewall]#

Is there something else I should be typing in?

Thanks,

Cyrus Bharda

[Cyrus Bharda]

Got it,

the command argument is:

--allmatches

this uninstalls both entries, whew!

Cyrus Bharda