You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Nick Chalko <ni...@chalko.com> on 2004/05/10 21:16:57 UTC
Re: Trouble connecting to brutus
Sam, et al.
Can you take a look at brutus
Noel J. Bergman wrote:
>>>-bash-2.05b$ ssh gump@brutus.apache.org
>>>ssh: connect to host brutus.apache.org port 22: Host is down
>>>-bash-2.05b$ ssh gump@brutus.apache.org
>>>ssh: connect to host brutus.apache.org port 22: Operation timed out
>>>
>>>
>
>brutus is running. I can get to the login prompt on the serial console.
>But that is as far as I can get, since I don't have an account.
>
> --- Noel
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Trouble connecting to brutus
Posted by "Adam R. B. Jack" <aj...@trysybase.com>.
> Brutus is up again. Sam and I found the problem. It simply wasn't
loading
> the network driver, so there was no network connectivity. Thom fixed it.
> We're not sure why, but it *appears* that the debian discover wasn't
finding
> and loading the network driver.
Thanks guys.
Most likely the reboot, but the cron problem I had seems to have gone away
[with no intervention from me]. :-)
I wonder if some of the memory abuse Python Gump/Forrest have been dishing
out is responsible for some of the uglies (with this, cron going belly up,
httpd going belly up.) Nick is going to look at installing Forrest as a
webapp on tomcat here, so we'll vastly reduce the pain being inflicted on
the machine. Hopefully it'll start stabilizing w/o any changes.
regards,
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
RE: Trouble connecting to brutus
Posted by "Noel J. Bergman" <no...@devtech.com>.
Brutus is up again. Sam and I found the problem. It simply wasn't loading
the network driver, so there was no network connectivity. Thom fixed it.
We're not sure why, but it *appears* that the debian discover wasn't finding
and loading the network driver.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org