RE: [cobalt-users] RaQ 550 Error

["Richard Sidlin" <maillist@xxxxxxxxxxxxxxxxxx>]

OK, I did that and on the next 15 min cycle, in the messages log, it seemed to go through a lot of processes but then when you try
and log into the GUI, it just sits at the login page and also via SSH, after entering Admin as the user and putting in the password,
it just sits there as well. Can't therefore log in.

Any idea what this may be?

 

> -----Original Message-----
> From: cobalt-users-admin@xxxxxxxxxxxxxxx 
> [mailto:cobalt-users-admin@xxxxxxxxxxxxxxx] On Behalf Of Bas van Ecke
> Sent: 28 February 2004 11:40
> To: cobalt-users@xxxxxxxxxxxxxxx
> Subject: RE: [cobalt-users] RaQ 550 Error
> 
> Remove the lock file. See /var/lock
> 
> 
> > Does anyone have any clues on this as after rebuilding it (RAq4r to 
> > 550), this seems to be my only problem.
> >
> > Richard
> >
> >
> >> Subject: [cobalt-users] RaQ 550 Error
> >>
> >> I have these errors in my messages log every 15 mins:
> >>
> >> Feb 24 14:15:00 ns1 swatch[23305]: can't open lockfile:
> >> looking for other swatch tasks Feb 24 14:15:00 ns1
> >> swatch[23305]: can't open lockfile - another swatch 
> process seems to 
> >> be running - exiting
> >>
> >> Apart from Email server and Disk Integrity, no other services are 
> >> available to check in the active monitor.
> >>
> >> How do I cure this please?
> >>
> >> Richard
> >>
> >
> >
> > _____________________________________
> > cobalt-users mailing list
> > cobalt-users@xxxxxxxxxxxxxxx
> > To subscribe/unsubscribe, or to SEARCH THE ARCHIVES, go to:
> > http://list.cobalt.com/mailman/listinfo/cobalt-users
> 
> 
> 
> _____________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To subscribe/unsubscribe, or to SEARCH THE ARCHIVES, go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
> 
> --
> This message has been scanned for viruses and dangerous 
> content by the Help Internet Virus Spam Defence, and is 
> believed to be clean. For details on having your email 
> scanned email support@xxxxxxxxxxxxxxxxxx
>