On Mon, Jun 23, 2014 at 10:28:27AM +0000, Jay D Bhatt wrote: > Hi, > > 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 Once again, systemd only works as PID 1. If you start it from another program, it'll fail. It's strange though that it doesn't give a better error message.
> Perhaps the kernel version is too old (< 3.4?) > 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? Again it says "failed to mount temporary directory". This seems like a signficant problem. You should investigate and fix that. Zbyszek _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
