Hi,
On Wed, 01 Oct 2008, Luis Montes wrote:
I wasn't able to authenticate on a text terminal either, so I couldn't
run top to see what was going on. The disks weren't really spinning much
either.
Then about ten minutes later something freed up, and I'm in now. No
idea what it was, but
Is it possible that the primary DNS server is not responding and a timeout must
occur each lookup before switching to the alternate? This type of external wait
delay would not be affected by the speed of the 8x2GHZ system.
--- On Thu, 10/2/08, Gavin McCullagh [EMAIL PROTECTED] wrote:
From:
On Thu, 02 Oct 2008, Mickey Moore wrote:
Is it possible that the primary DNS server is not responding and a
timeout must occur each lookup before switching to the alternate? This
type of external wait delay would not be affected by the speed of the
8x2GHZ system.
Sounds very plausible
Gavin McCullagh wrote:
Hi,
On Wed, 01 Oct 2008, Luis Montes wrote:
Agreed. Can you look back through /var/log/syslog and /var/log/messages
during the time and see if there's anything that might indicate the source
of the issue?
One possibility might be a rogue process hogging all
Reiner Schmid wrote:
My system was crawling. too.
Perhaps you can
install speedometer to test the speed of eth0 (or eth1)
and test the connection between server and clients with
speedometer -rx eth0 -tx eth0
I removed thenetwork manager and avahi-autoip to get a better connection.
Do
On Thu, Oct 2, 2008 at 10:17 AM, Luis Montes [EMAIL PROTECTED] wrote:
Looks like there's been over 5000 errors like this:
Oct 1 09:32:24 192.168.0.61 kernel: [152372.345437] end_request: I/O
error, dev nbd0, sector 200314
since yesterday morning.
Sounds like a hard drive error/sector
Charles, nbd is the Network Block Device - although the I/O error
message is reminiscent of a physical hard drive failure or bad sectors,
this is a different deal.
Charles Austin wrote:
On Thu, Oct 2, 2008 at 10:17 AM, Luis Montes [EMAIL PROTECTED] wrote:
Looks like there's been over
For some reason ubuntu is blocking one of our IP addresses from accessing
its web pages, which means whenever I want to make a download or access
the ubunut or edubuntu forums I need to use another public IP.
I tried contacting their technical people via the whois information but
haven't had a
Luis,
This might sound trivial, but I'm not sure if you'd mentioned you'd
completely rebuilt your chroot from scratch as a troubleshooting step.
Are you using the complete Edubuntu i386 install, or is it only the i386
kernel you're using? You'd mentioned in your first post that you were
using
Thanks for the reply, this does look similar.
However, it's a normal 32-bit i386 install with the server kernel to
address more ram. No 64bit binaries anywhere on the system.
I thought about going 64 bit but decided against it because of adobe flash.
The chroot was built fresh after the install
10 matches
Mail list logo
