Officially getting pissed off now. Okay, so it happened again...kinda. The server seems fine, but I'm trying to transfer files to it and BAM down goes the connection. So I actually manage to NX into the box (surprise!) and am able to confirm that / has 15GB free, before BAM, it drops again. Then I just try to ping the server. I'm getting about 70-80% packet loss. Not 100%. Previously I was seeing "no route to host" which I think is a totally different thing. Well, not today.
I notice that my desktop box is the only machine having trouble talking to the server. My laptop is fine. Desktop problem or just lucky? Hard to say--yesterday the desktop was talking to the server fine too. I check my desktop's /var/log/messages, and there are tons of messages about packets from "martian sources". Greeeeeeat. So we're back to the network again, or at least there's a network problem in addition to the other problem. Many of the things I did next may have done nothing to solve the problem, but it felt good to do something. I disabled IPv6 on every device that supported it. I've got one ancient Linksys BEFSR41 router, and I simply don't know how well it deals with IPv6. Maybe it receives X IPv6 packets and then starts screwing with all the traffic on the network, who knows? Every other device should be fine, but it's the lowest common denominator, so that's what I'm doing. Everything gets changed and rebooted, confirmed IPv4-only. Same deal. Laptop is fine. Server seems fine in most respects, except for severe packet loss between it and the desktop. Then /sbin/ifconfig on the desktop tells me I've had one RX overrun on my NIC. Maybe this isn't abnormal, but I don't like it. I happen to have two NICs on the desktop and I so I switch them. Suddenly everything's okay again. Well...for now. I quickly check messages on the server and there's nothing there about martian sources there. ifconfig on the server shows no errors or anything on its NIC. The problem CANNOT have just been on the desktop--the server has been inaccessible from every device on the network before, including the laptop (and with a totally different error--no route to host). So either I played with the hardware for long enough for the gremlins to get a good laugh out of me and scurry away, or something got fixed. Perhaps totally unrelated to the original problem, but something. -- CatBus ------------------------------------------------------------------------ CatBus's Profile: http://forums.slimdevices.com/member.php?userid=7461 View this thread: http://forums.slimdevices.com/showthread.php?t=34229 _______________________________________________ unix mailing list [EMAIL PROTECTED] http://lists.slimdevices.com/lists/listinfo/unix
