[cobalt-users] Qube 3 Error messages and qube wierdness

[Jason Crouch <lists@xxxxxxxxxxxx>]

Hi all,

Just received this through the mail:

Bareword "SOL_SOC" not allowed while "strict subs" in use at 
/usr/lib/perl5/5.00503/i386-linux/IO/Socket.pm line 258, <STDIN> chunk 
1.
Bareword found where operator expected at 
/usr/lib/perl5/5.00503/i386-linux/IO/Socket.pm line 258, near 
"SOL_SOCET"
Bareword "ET" not allowed while "strict subs" in use at 
/usr/lib/perl5/5.00503/i386-linux/IO/Socket.pm line 258, <STDIN> chunk 
1.
syntax error at /usr/lib/perl5/5.00503/i386-linux/IO/Socket.pm line 258, 
near "SOL_SOCET"
BEGIN failed--compilation aborted at 
/usr/lib/perl5/5.00503/i386-linux/IO/Socket/UNIX.pm line 11, <STDIN> 
chunk 1.


And I note that Active monitor is showing me a bunch of errors, 
including DNS, mail and (at one point) amber lights in memory and disk. 
Rebooting the Qube shows the errors are persistent!  I note that 
fetchmail stuff is not in /etc/fetchmail/ and that named and sendmail 
both refuse to start :(  At one point I had to manually redefine the 
default gw on eth0: ...

I'll be re-installing the system from the recovery disk - but I'm very 
curious as to what can have caused this kind of total screwup ... ?  I 
note that the box did have a a sudden complete power failure (haven'y 
installed the UPS yet, doh!) and I'm wondering if the raid has gone a 
little haywire.

Bare bones Qube 3 with all bluelink patches applied, the only slightly 
odd things that have been happened to it are that it's had its samba 
upgraded to 2.2.3a (for w2k domain support) and its had the ssh pkg 
installed from pkg.nl.cobalt.com.

Any thoughts ... ?