| View previous topic :: View next topic |
| Author |
Message |
Basilisk
n00b
Joined: 11 May 2011
Posts: 13
|
 Posted: Sun May 15, 2011 7:11 pm Post subject: Problem after migration to baselayout-2 и openrc |
 |
|
I have migrated to baselayout-2 и openrc. I did all steps from manual from news.
However, I got several problems
1.
| Code: |
*Setting up kdm...
*start-stop-daemon: did not create a valid pid in `/var/run/kdm.pid`
* ERROR: could not start the Display Manager
|
| Code: |
* Starting ConsoleKit daemon ...
* start-stop-daemon: did not create a valid pid in `/var/run/ConsoleKit/pid' [ !! ]
* ERROR: consolekit failed to start
|
rc-update
/etc/rc.conf
NB: I have
Although KDE starts I can not run more than one application.
P.S Also I updated KDE to 4.6.3 |
|
| Back to top |
|
 |
Etal
Veteran
Joined: 15 Jul 2005
Posts: 1634
|
| Posted: Mon May 16, 2011 3:24 am Post subject: |
|
|
Have you checked what is happening in /var/run? Is there a /var/run/kdm.pid? Does kdm actually start? (or did you start KDE with startx?)
_________________
“And even in authoritarian countries, information networks are helping people discover new facts and making governments more accountable.”– Hillary Clinton, Jan. 21, 2010 |
|
| Back to top |
|
|
Basilisk
n00b
Joined: 11 May 2011
Posts: 13
|
| Posted: Mon May 16, 2011 6:59 am Post subject: |
|
|
| Etal wrote: | | Have you checked what is happening in /var/run? |
| Etal wrote: | | Is there a /var/run/kdm.pid? Does kdm actually start? (or did you start KDE with startx?) |
There is /var/run/kdm.pid with number(I suppose pid) inside. The file /var/run/Consolekit/pid also exists.
I do nothing to start KDE, so I suppose that it happens due to kdm.
For instance, if I try to start second application I receive the message from plasma environment
| Code: | KDEInit is unable to run "/usr/bin/opera"
Unable to create new process. The maximum number of processes possible or the maximum number of processes that you are allowed to use has been reached. |
my ps -A is here
There are TWO kdm processes. It is strange.
Last edited by Basilisk on Mon May 16, 2011 9:49 am; edited 1 time in total |
|
| Back to top |
|
|
krinn
Advocate
Joined: 02 May 2003
Posts: 3677
|
| Posted: Mon May 16, 2011 7:49 am Post subject: |
|
|
| xdm should be in default runlevel, not boot |
|
| Back to top |
|
|
Basilisk
n00b
Joined: 11 May 2011
Posts: 13
|
| Posted: Mon May 16, 2011 8:22 am Post subject: |
|
|
I changed level for xdm from boot to default. However, noting have changed.
If I do
and then do
| Code: | | /etc/init.d/xdm restart |
I obtain TWO kdm processes in ps -A (and one kdm_greet) |
|
| Back to top |
|
|
krinn
Advocate
Joined: 02 May 2003
Posts: 3677
|
| Posted: Mon May 16, 2011 8:26 am Post subject: |
|
|
2 kdm process would be seeing two KDM, i don't use it, but KDM and KDM-greeter (or name like that) = 2 process for two programs, nothing strange for me.
what about your /var directory, running on a different partition/fs ? |
|
| Back to top |
|
|
Basilisk
n00b
Joined: 11 May 2011
Posts: 13
|
| Posted: Mon May 16, 2011 8:43 am Post subject: |
|
|
| krinn wrote: | 2 kdm process would be seeing two KDM, i don't use it, but KDM and KDM-greeter (or name like that) = 2 process for two programs, nothing strange for me.
|
| Code: |
6157 ? 00:00:00 kdm
6565 ? 00:00:00 kdm
6572 ? 00:00:04 kdm_greeter
|
If it is ok, let it be. I thought that two kdm is wrong(in /var/run/kdm.pid only pid of one of the kdm processes is written, and only one such file exists)
| krinn wrote: |
what about your /var directory, running on a different partition/fs ? |
I have one drive and four partitions(swap, boot, root and home). Root and home partitions both use reiserfs.
Everything worked before updating and migration. |
|
| Back to top |
|
|
krinn
Advocate
Joined: 02 May 2003
Posts: 3677
|
| Posted: Mon May 16, 2011 9:08 am Post subject: |
|
|
doesn't look ok 
i misread you have one kdm + one kdm_greeter running and took them as 2 process, sorry.
try to check your root for filesystem corruption (and space/node free), /var/run looks strange |
|
| Back to top |
|
|
Basilisk
n00b
Joined: 11 May 2011
Posts: 13
|
| Posted: Mon May 16, 2011 9:32 am Post subject: |
|
|
Unfortunately, I do not have external flash drive with me, therefore I can not check /. (I use netbook so I can use only liveFlash-drive).
(I do not know how to check partition which is mounted with write permissions. Is it possible to do disk check of the root directory without live-drive?)
I have 20 GB for root partion and df -h tells me that 8.8 GB are free. |
|
| Back to top |
|
|
krinn
Advocate
Joined: 02 May 2003
Posts: 3677
|
| Posted: Mon May 16, 2011 9:43 am Post subject: |
|
|
shutdown -F -r now
and df -i |
|
| Back to top |
|
|
Basilisk
n00b
Joined: 11 May 2011
Posts: 13
|
| Posted: Mon May 16, 2011 9:52 am Post subject: |
|
|
| Code: |
# df -i
file system Inodes IUsed Ifree IUsed% mounted on
rootfs 0 0 0 - /
/dev/root 0 0 0 - /
rc-svcdir 127532 70 127462 1% /lib/rc/init.d
udev 127532 762 126770 1% /dev
shm 127532 1 127531 1% /dev/shm
/dev/sda4 0 0 0 - /home |
waiting for reiserfsck results |
|
| Back to top |
|
|
Basilisk
n00b
Joined: 11 May 2011
Posts: 13
|
| Posted: Mon May 16, 2011 10:15 am Post subject: |
|
|
| Code: |
Checking internal tree.. finished
Comparing bitmaps.. finished
Checking Semantic tree:
finished
No corruptions found
There are on the filesystem:
Leaves 137464
Internal nodes 927
Directories 49118
Other files 513815
Data bock pointers 3095471 (570724 of them are zero)
Safe links 0 |
It seems that with file system is everything OK |
|
| Back to top |
|
|
krinn
Advocate
Joined: 02 May 2003
Posts: 3677
|
| Posted: Mon May 16, 2011 7:09 pm Post subject: |
|
|
| can show mount result to see everything is mount as it should ? |
|
| Back to top |
|
|
Letharion
Veteran
Joined: 13 Jun 2005
Posts: 1216
Location: Sweden
|
| Posted: Mon May 16, 2011 7:27 pm Post subject: |
|
|
| Just mentioning that on a baselayout upgraded system that works well I also have two kdm's, so that's not a problem. (I don't have the greeter though) |
|
| Back to top |
|
|
Basilisk
n00b
Joined: 11 May 2011
Posts: 13
|
| Posted: Tue May 17, 2011 7:40 am Post subject: |
|
|
| krinn wrote: | | can show mount result to see everything is mount as it should ? |
| Code: | # mount
rootfs on / type rootfs (rw)
/dev/root on / type reiserfs (rw,noatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
rc-svcdir on /lib/rc/init.d type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1024k,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
udev on /dev type tmpfs (rw,nosuid,relatime,size=10240k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime)
/dev/sda4 on /home type reiserfs (rw,noatime)
usbfs on /proc/bus/usb type usbfs (rw,noexec,nosuid,devmode=0664,devgid=85)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
|
And fstab |
|
| Back to top |
|
|
Etal
Veteran
Joined: 15 Jul 2005
Posts: 1634
|
| Posted: Tue May 17, 2011 12:25 pm Post subject: |
|
|
Do the numbers in the pid files match any running processes?
What happens if you stop xdm / consolekit - are the pid files still there?
_________________
“And even in authoritarian countries, information networks are helping people discover new facts and making governments more accountable.”– Hillary Clinton, Jan. 21, 2010 |
|
| Back to top |
|
|
Erdie
Veteran
Joined: 20 May 2004
Posts: 1588
Location: Heidelberg - Germany
|
| Posted: Tue May 17, 2011 3:39 pm Post subject: |
|
|
I see exactly the same problem on my Atom/ION Nettop, but ..
After I kill the process "console-kit-daemin" and delete the file /var/run/Consolekit/pid, I am able to start/stop consolekit via init scripts.
The system does not start up due to the issue described in the initial post but just /etc/init.d/xdm restart" causes the KDE to start. If i try to stop consolekit I get that answer that consolekit does not run even i can see the process .. very strange 
Furthermore:
Pressing the "I" key during startup and just let all processes startup interactively lets the system start flawless ..  |
|
| Back to top |
|
|
Basilisk
n00b
Joined: 11 May 2011
Posts: 13
|
| Posted: Tue May 17, 2011 5:11 pm Post subject: |
|
|
| Etal wrote: | | Do the numbers in the pid files match any running processes? |
Yes, pid number matches to one of the kdm processes. And in the case of console-kit-dae it does match.
| Etal wrote: | | What happens if you stop xdm / consolekit - are the pid files still there? |
If I stop kdm or/and console-kit-dae corresponding files do not change.
| Erdie wrote: | I see exactly the same problem on my Atom/ION Nettop, but ..
After I kill the process "console-kit-daemin" and delete the file /var/run/Consolekit/pid, I am able to start/stop consolekit via init scripts. |
I have tried to repeat it but I was not succeed.
| Erdie wrote: |
The system does not start up due to the issue described in the initial post but just /etc/init.d/xdm restart" causes the KDE to start. If i try to stop consolekit I get that answer that consolekit does not run even i can see the process .. very strange |
In my case although KDE starts it does not work.
With cosole-kit-dae I have the same situation.
| Erdie wrote: |
Furthermore:
Pressing the "I" key during startup and just let all processes startup interactively lets the system start flawless .. |
I tried to do it and obtain the same errors as from the very beginning. |
|
| Back to top |
|
|
krinn
Advocate
Joined: 02 May 2003
Posts: 3677
|
| Posted: Wed May 18, 2011 1:05 am Post subject: |
|
|
 i know i'm lame just saw it
xdm | boot
xdm MUST be at default runlevel, else it might boot while your fs is still RO, hence the "can't create file" error
please just move it to default runlevel, but this time, i'm more confident for success |
|
| Back to top |
|
|
Basilisk
n00b
Joined: 11 May 2011
Posts: 13
|
| Posted: Wed May 18, 2011 5:53 am Post subject: |
|
|
| krinn wrote: | i know i'm lame just saw it
xdm | boot
xdm MUST be at default runlevel, else it might boot while your fs is still RO, hence the "can't create file" error
please just move it to default runlevel, but this time, i'm more confident for success |
I changed level for xdm from boot to default. However, noting have changed.
Also I have problem with consolekit. |
|
| Back to top |
|
|
Etal
Veteran
Joined: 15 Jul 2005
Posts: 1634
|
| Posted: Fri May 20, 2011 10:54 pm Post subject: |
|
|
Since there are at least two of you who have the problem, have you considered filing a bug?
_________________
“And even in authoritarian countries, information networks are helping people discover new facts and making governments more accountable.”– Hillary Clinton, Jan. 21, 2010 |
|
| Back to top |
|
|
jla
n00b
Joined: 29 May 2011
Posts: 1
|
| Posted: Sun May 29, 2011 12:52 pm Post subject: |
|
|
Let me add my version of this problem:
With global useflags policykit and consolekit system worked flawlessly under baselayout 1.
Since upgrading to baselayout 2 and openrc while following the openRC migration guide, at boot I get identical error messages:
*start-stop-daemon: did not create a valid pid in `/var/run/kdm.pid`
*start-stop-daemon: did not create a valid pid in `/var/run/ConsoleKit/pid'
I believe this is related to
http://www.mail-archive.com/gentoo-user@lists.gentoo.org/msg108561.html
Similarly to the quoted thread, I observe the following behaviour:
Stopping the consolekit daemon is not possible as the system claims that it is not running.
Starting the consolekit daemon is not possible as the system claims that it is already running.
ps -ax shows that "console-kit-daemon" is running.
Removing consolekit from the appropriate runlevel and reboot results in:
a) the error message "start-stop-daemon: did not create a valid pid in `/var/run/ConsoleKit/pid'" disappears
b) error message "*start-stop-daemon: did not create a valid pid in `/var/run/kdm.pid`" remains
c) 'ps -ax' still shows that "console-kit-daemon" is running
In _both_ constellations, i.e. with or without consolekit init script being added to appropriate runlevel which I use for graphical login into the kde desktop, the error message "*start-stop-daemon: did not create a valid pid in `/var/run/kdm.pid`" does not prevent kde from starting and kde operates normally for several minutes/hours. However, sporadically kde logs me out instantaneously and displays the login-screen. |
|
| Back to top |
|
|
Anon-E-moose
Veteran
Joined: 23 May 2008
Posts: 1379
Location: Dallas area
|
| Posted: Sun May 29, 2011 1:01 pm Post subject: |
|
|
| Basilisk wrote: | I changed level for xdm from boot to default. However, noting have changed.
If I do
and then do
| Code: | | /etc/init.d/xdm restart |
I obtain TWO kdm processes in ps -A (and one kdm_greet) |
Then the killall seemingly did not kill "all" kdm processes.
Did you do a "ps" after the killall?
BTW the proper way to kill all kdm would be "/etc/init.d/kdm stop", followed by a "start", or do "/etc/init.d/kdm restart"
_________________
Asus m5a99fx, Phenom II X6 - X64-multilib, glibc-2.15-r3, 3.9.1-zen
xorg-server-1.14 - lxde - nouveau
wine-1.5.30, oss4
gcc-4.7.3 CFLAGS="-march=native -O2 -floop-interchange -floop-strip-mine -floop-block -pipe" |
|
| Back to top |
|
|
Anon-E-moose
Veteran
Joined: 23 May 2008
Posts: 1379
Location: Dallas area
|
| Posted: Sun May 29, 2011 1:05 pm Post subject: |
|
|
| jla wrote: | Let me add my version of this problem:
With global useflags policykit and consolekit system worked flawlessly under baselayout 1.
Since upgrading to baselayout 2 and openrc while following the openRC migration guide, at boot I get identical error messages:
*start-stop-daemon: did not create a valid pid in `/var/run/kdm.pid`
*start-stop-daemon: did not create a valid pid in `/var/run/ConsoleKit/pid'
I believe this is related to
http://www.mail-archive.com/gentoo-user@lists.gentoo.org/msg108561.html
Similarly to the quoted thread, I observe the following behaviour:
Stopping the consolekit daemon is not possible as the system claims that it is not running.
Starting the consolekit daemon is not possible as the system claims that it is already running.
ps -ax shows that "console-kit-daemon" is running.
Removing consolekit from the appropriate runlevel and reboot results in:
a) the error message "start-stop-daemon: did not create a valid pid in `/var/run/ConsoleKit/pid'" disappears
b) error message "*start-stop-daemon: did not create a valid pid in `/var/run/kdm.pid`" remains
c) 'ps -ax' still shows that "console-kit-daemon" is running
In _both_ constellations, i.e. with or without consolekit init script being added to appropriate runlevel which I use for graphical login into the kde desktop, the error message "*start-stop-daemon: did not create a valid pid in `/var/run/kdm.pid`" does not prevent kde from starting and kde operates normally for several minutes/hours. However, sporadically kde logs me out instantaneously and displays the login-screen. |
X will start consolekit daemon when it starts up, so I don't think you need to have it activated in runlevel or at least it does on my system.
The "/var/run/kdm.pid" sounds a permission problem, either on "who" runs kdm or "/var/run" itself
OR the old pid files are not being removed, though the messages should be different for that.
When you get the message about no valid pid, do a "ls -l /var/run" or /var/run/ConsoleKit for consolekit
_________________
Asus m5a99fx, Phenom II X6 - X64-multilib, glibc-2.15-r3, 3.9.1-zen
xorg-server-1.14 - lxde - nouveau
wine-1.5.30, oss4
gcc-4.7.3 CFLAGS="-march=native -O2 -floop-interchange -floop-strip-mine -floop-block -pipe" |
|
| Back to top |
|
|
Basilisk
n00b
Joined: 11 May 2011
Posts: 13
|
| Posted: Sun May 29, 2011 5:57 pm Post subject: |
|
|
| Anon-E-moose wrote: | | Basilisk wrote: | I changed level for xdm from boot to default. However, noting have changed.
If I do
and then do
| Code: | | /etc/init.d/xdm restart |
I obtain TWO kdm processes in ps -A (and one kdm_greet) |
Then the killall seemingly did not kill "all" kdm processes.
Did you do a "ps" after the killall?
BTW the proper way to kill all kdm would be "/etc/init.d/kdm stop", followed by a "start", or do "/etc/init.d/kdm restart" |
| Code: |
# ps -A | grep kdm
3101 ? 00:00:00 kdm
3131 ? 00:00:00 kdm
# killall kdm
#ps -A | grep kdm
#
# /etc/init.d/xdm stop
* Stopping kdm... [OK]
#/etc/init.d/xdm stop
* WANING: xdm is already stopped
#/etc/init.d/xdm start
*Starting ConsoleKit daemon...
*start-stop-daemon: /usr/sbin/console-kit-daemon is already running
*ERROR: consolekit failed to start
*Setting up kdm...
acpid: client connected from 15837[0:0]
acpid: 1 client rule loaded
#ps -A | grep kdm
15383 ? 00:00:00 kdm
16227 ? 00:00:00 kdm
16232 ? 00:00:02 kdm_greet
|
I suppose this is the answer to your question.
There is bugs at bugs.gentoo.org http://bugs.gentoo.org/show_bug.cgi?id=368285 |
|
| Back to top |
|
|
|
Other Things Gentoo
