1 |
Hello list, |
2 |
|
3 |
Today my workstation has refused to start consolekit, giving this error: |
4 |
|
5 |
* Starting ConsoleKit daemon ... |
6 |
* start-stop-daemon: did not create a valid pid in `/var/run/ConsoleKit/pid' [ !! ] |
7 |
* ERROR: consolekit failed to start |
8 |
|
9 |
Then of course I can't log in via kdm; but X still detects my keystokes and allows |
10 |
me to switch to a VT. If I boot to a console instead and then startx I've no further |
11 |
problems. |
12 |
|
13 |
The system started up the first time today just fine, but all attempts to restart |
14 |
since then have failed. Here are the things I've tried: |
15 |
|
16 |
1. Downgraded consolekit from 0.4.3 to 0.4.2-r4, even though the upgrade |
17 |
was done on 8 Dec. |
18 |
2. Removed the automounting of my Atom chroot from the default run level; I'd |
19 |
been playing with it and thought it just possible that it had started interfering |
20 |
somehow. |
21 |
3. Run fsck -f on all partitions, having booted my rescue system from a |
22 |
different kernel: no problems found. |
23 |
4. Booted the previous kernel, gentoo-sources-2.6.35-r11, which had been |
24 |
running until late October, instead of the usual 2.6.36-r5. |
25 |
5. Booted ck-sources 2.6.36-r3. |
26 |
6. Checked permissions on /var/run and /var/run/ConsoleKit; nothing suspicious |
27 |
there, and I can touch the pid file myself ok. |
28 |
7. Checked bugzilla for consolekit faults. |
29 |
|
30 |
The only thing I've emerged today is nfs-utils. |
31 |
|
32 |
I can't think of anything else I've changed. On the other hand, the last couple of |
33 |
days I have been working on setting up an nfs and chroot method of maintaining |
34 |
my Atom server box, as described by Neil B. in another thread, in the course of |
35 |
which I may have done something stupid - and my memory is getting |
36 |
embarrassingly fallible these days. |
37 |
|
38 |
Can anyone see anything else I could check? |
39 |
|
40 |
-- |
41 |
Rgds |
42 |
Peter. Linux Counter 5290, 1994-04-23. |