On Mon, Jun 23, 2014 at 12:28 PM, Jay D Bhatt <jay.bh...@igate.com> wrote: > > My systemd stops indefinitely at this point: > > [ OK ] Reached target Login Prompts. > > As Lennart suggested, I looked at my kernel version which is 3.0.35, which > is >= 3.0, so should not give problem for systemd initialization. > > Then I tried bit of debugging and taking logs. > > I put systemd.log_level=debug systemd.log_target=console in my kernel > parameters and took the log. The log is attached,it is detailed one but I am > not able to find the point why it stops there. > > I also put systemd.unit=rescue.target in kernel parameters and removed > initially put systemd.log_level and systemd.log_target parameters. > > It asked me to enter the password, on entering password I got prompt. Then I > tried to run systemd and check it out. Below what output when I ran systemd > in rescue mode. My default service is Weston.service. > > bash-4.2# systemd > > Failed to make us a subreaper: Invalid argument > > Perhaps the kernel version is too old (< 3.4?)
This is the systemd --user mode, the PR_SET_CHILD_SUBREAPER should not be needed in the PID1 mode. But none of us ever tries such old kernels, it might still fail with other features later. > weston.service: main process exited, code=exited, status=1/FAILURE > > Unit weston.service entered failed state. > > I am not able to find reason for not completing systemd operation. Could > anybody let me know the might-be problems? Just the usual suspects: check if CONFIG_FHANDLE, CONFIG_DEVTMPFS, CONFIG_TMPFS are set in your kernel config. Kay _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
