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

["Dan" <dan@xxxxxxxxxxxxx>]

> A bit over a week ago we applied the RaQ2-en-Update-OS-3.0.pkg
>
> Since then a serious email problem has occured. About once ever
> working day
> the /var/spool/mail directory gets filled with *.lock and .*pop* files
> and the users cant read their mail.
>
> The maillog has the following type of error:
>
> in.qpopper[13552]: steven at dg-1-p18.winshop.com.au
> (210.8.124.27): -ERR [SYS/TEMP] maillock error 4: '/var/spool/mail/steven'
>
>
> The only solution is to reboot the Raq2 and delete all the *lock
> and .*pop* files immediately.
>
>
> Can anyone tell me how to remove the RaQ2-en-Update-OS-3.0.pkg
> and wind the system back to a stable state?
>

Ernie:

[root admin]# /var/lib/cobalt/uninstallers/RaQ2-en-Update-OS-3.0.uninst

Before you try that:

Does OS 3.0 update show up in your list of installed software on the RaQ2
GUI?

Found these posts that may relate.

http://list.cobalt.com/pipermail/cobalt-users/2000-August/018234.html
http://list.cobalt.com/pipermail/cobalt-users/2000-August/018326.html
http://list.cobalt.com/pipermail/cobalt-users/2000-August/018335.html

If you want to try what is suggested in there, read the cautions regarding
Qpopper 2.53.
http://www.hideaway.net/bugtraq/may/291.html
Most sites removed downloads of 2.53 but I did manage to find one via
www.google.com (let me know if you need it.)

Are you running RaQ2-POP-before-SMTP-1.2? That stopped working tonite on my
RaQ2 and I uninstalled it.
[root admin]# /var/lib/cobalt/uninstallers/pop-before-smtp-1.2.uninst
then clicked on "Install Software" in the GUI. Like a miracle <smile>
RaQ2-en-Update-OS Release 3.0 suddenly appeared in the list of installed
updates where it was missing.
Cobalt had recommended, (before I had the .lock problem), that I install the
OS3.0 update via the GUI again.),
I then installed RaQ2-POP-before-SMTP-1.2-4.pkg and POP b4 SMTP began
working again.

Waiting until tomorrow to see if the .lock files appear again. I hadn't seen
the .pop file problem in /var/spool/mail.

--
Dan Kriwitsky