Problem re-stated
From: jack kinnon (jackkinnon_at_yahoo.com)
Date: 11/29/04
- Previous message: Francois Cerbelle: "Re: Grub menu.lst"
- Next in thread: Clive Menzies: "Re: Problem re-stated"
- Reply: Clive Menzies: "Re: Problem re-stated"
- Reply: Sam Watkins: "Re: Problem re-stated"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 29 Nov 2004 02:14:19 -0800 (PST) To: debian-user@lists.debian.org
Hi folks,
I will re-state my problem. I had been running 'stable' for months when I decided to upgrade to 'testing' via the net. I did a apt 'update' followed by a 'dist upgrade'. Because the number of bytes to be downloaded exceeded my volume-based subscription for the month, I had to continue the upgrade the following month when I had accumulated enough volume. But then the system can only boot-up in basic command-line mode, without proper log, and cannot go online.
Using 'scroll-lock', I can read the following message during boot-up.
Starting system log daemon : syslogd
syslogd : cannot create /dev/log : address family not supported by protocol
Upon examining the log files:
/var/log/syslog has only one line as follows:
<date & time> debian syslogd 1.4 #15 restart.
XFree86.0.log is as follows:
_XSERVTransSocketOpen: socket failed for local
.
.
Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't
already running.
For your info, I was running a 2.6.3 kernel which I made from source.
I had checked that 'Unix domain socket' was selected in the kernel config. I had re-make the kernel.
dpkg --configure -a did not throw up any erroneous packages.
Any suggestions pls reply on-list. Thanks.
Jack
---------------------------------
Do you Yahoo!?
The all-new My Yahoo! – Get yours free!
-- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
- Previous message: Francois Cerbelle: "Re: Grub menu.lst"
- Next in thread: Clive Menzies: "Re: Problem re-stated"
- Reply: Clive Menzies: "Re: Problem re-stated"
- Reply: Sam Watkins: "Re: Problem re-stated"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- Re: amanda vs 2.6
... On Thursday 27 November 2003 03:41, Nick Piggin wrote: ... >> to syslogd
until the logging socket buffer fills up. ... command in my script, 'make xconfig'. ...
job as it oversees the fully installed kernel, ... (Linux-Kernel) - Re: filling up UDP socket buffers like mad
... the box starts dropping UDP due to full socket ... 168725 dropped due
to full socket buffers ... named and syslogd are in cron to restart every 15 minutes.
... (freebsd-questions) - Re: Annoying iptables console logging
... getting msgs to console. ... They are sent by kernel. ... containing
both syslogd and klogd, ... (Debian-User) - syslogd socket (was Re: PING: Igor S. , regarding Kerberos v4.)
... a socket and convention requires syslog to use a privileged port. ... syslogd
is also "privilege separated" for security. ... To "disable" the feature of creating
the socket would require ... (comp.unix.bsd.openbsd.misc) - Re: Problem re-stated
... > Starting system log daemon: ... > I had checked that 'Unix domain
socket' was selected in the kernel config. ... (Debian-User)