I'd really like to know what this turned out to be...
I had an issue a while back where a kernel update caused a server to fail
reboot - something about the combination of SCSI, Software RAID, and Grub. I
had to run a grub script from the console to get it all back up. (Making an
emergency plane ride worthwhile as well as fun!)
The most recent kernel update did not cause any problems.
My advice? Don't host more than about 2-4 hour drive from home...
-Ben
On Friday 24 March 2006 12:41, centos@xxxxxxxxxxxxxxx wrote:
> Hi,
>
> Just upgraded a remote 4.1 server [basically Samba] with yum
> update. Went through the process and every showed OK, when I did
> a restart, the only thing working is ping. I could ping it, but
> that's it.
>
> Could not connect anymore through SSH, could not connect through
> SMB. My smb.conf is still there and it still shows my settings.
> Testparm -L reports the correct info, but nobody can connect.
>
> I now have the server being shipped back. Anybody also having
> problems?
>
> --
> Thanks
> http://www.911networks.com
> When the network has to work
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
--
"The best way to predict the future is to invent it."
- XEROX PARC slogan, circa 1978
