[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [cobalt-users] Raq2 .lock problem after RaQ2-en-Update-OS-3.0.pkg possible bug.



> Heck, you were lucky.
>
> The OS 3.0 upgrade destroyed two of my servers - well, the server still
> works, but with above problems (with POP, relaying) AND I cannot
> create new
> sites nor can I delete existing ones.
>
> One machine was still empty and I restored it immediately,
> however the other
> has 80 sites on it, and I can hardly restore it. Therefore I ask
> - how were
> you able to reinstall the OS 2.0?
>
I went in via Telnet and tried to uninstall OS 3.0. Here's that strange
result.

 [root uninstallers]#
/var/lib/cobalt/uninstallers/RaQ2-en-Update-OS-3.0.uninst
/bin/mv: /usr/local/majordomo/majordomo/request-answer.30update: Not a
directory

That was strange.

I installed RaQ2-All-Security Release 3.0.1-6682
My co-lo host then installed RaQ2-Update-OS Release 2.0 and POP started
working again.
Looking in /usr/docs I saw qpopper 2.53 listed again.
I then re-installed POP-Authenticated SMTP Relaying Release 1.2 and both are
working again.
So, I'm on the phone tomorrow AM with Cobalt to see what's up. I should have
checked the POP b4 SMTP while I had their tech on the phone who had
installed Qpopper 2.53 over the previous 3.0.
--
Dan Kriwitsky