From mike@boobaz.net Mon Jul 16 13:16:51 2001 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6GKGn0109704 for ; Mon, 16 Jul 2001 13:16:49 -0700 Received: from boobaz.net (c1056043-a.sttln1.wa.home.com [24.10.40.236]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6GKGms04959 for ; Mon, 16 Jul 2001 13:16:48 -0700 Received: from c1056043-a (c1056043-a [24.10.40.236]) by boobaz.net (8.11.1/8.11.1) with ESMTP id f6GKGm601786 for ; Mon, 16 Jul 2001 13:16:48 -0700 Date: Mon, 16 Jul 2001 13:16:48 -0700 (PDT) From: Mike X-Sender: mike@c1056043-a.sttln1.wa.home.com To: UW Linux Group Subject: Re: xfs dead but subsys locked In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII It sounds like you've been hacked! Send me a copy of your "xfs" binary and I'll take a look at it. The message "eth0: Promiscuous mode enabled" indicates that a network sniffer or something is starting up... It's likely that someone broke in and replaced this binary with a network sniffer that gets started at boot. This is precisely why you shouldn't still be running (unpatched) RedHat 6.2!! --------------------------- -=<(| mike@boobaz.net |)>=- On Mon, 16 Jul 2001 at 11:54, Thomas Anderl wrote: |Hi All, | |I'm running RH6.2 and up until this morning, it's been running just fine. |I have it start into X automatically, so I usually turn the machine on, |and come back after a couple of minutes to the X login screen. This time, |however, when I came back, it gave me a console login. | |running startx gives: | | |(many SVGA messages that I'm pretty sure are just info) |_FontTransSocketUNIXConnect: Can't connect: errno = 111 |failed to set default font path 'unix/:-1; |Fatal server error: |could not open default font 'fixed' | |When reporting a problem related to a server crash, please send the full |server output, not just the last messages | |X connection to :0.0 broken (explicit kill or server shutdown) | | | |So I look this up, and it looks like the problem is probably with xfs. I |run: |"/etc/rc.d/init.d/xfs status" |and it tells me: |"xfs dead but subsys locked" | |Some solutions I saw out on the internet that I tried but didn't |work were: | |(1) rm /var/lock/subsys/xfs | |(2) change the port that xfs is using along with the port that X uses to |connect to xfs. | |(3) make sure there is space on both /tmp and /. Well, /tmp is on the |same partition as / and df -m gives: |Filesystem 1M-blocks Used Available Use% Mounted on |/dev/sda1 4918 1300 3368 28% / |/dev/sda6 2602 90 2380 4% /kerry | |so I don't think that space is an issue. | | | |(4) try starting xfs from the command line to see what happens. | |# xfs |eth0: Promiscuous mode enabled. |# ps -aux | grep xfs |# | |So this is what I've tried, with no luck. One thing that I don't think is |related, but I'm not sure: /log/messages contains: | |rpc.lockd: lockdsvc: Connection refused |nfslock: rpc.lockd startup failed | |and a little later... | |portmap: RPC call returned error 111 | | |Any ideas how to get X to start again? | |Thanks, | |Tom | |------------------------------------------------------------------------------- | .