Re: [systemd-devel] systemd not initializing
On Tue, 17.06.14 09:23, Jay D Bhatt (jay.bh...@igate.com) wrote: Hi, From the log I attached previously, I think is log statement saying as below: Starting Login Service... But then , it gets stuck at [ OK ] Reached target Login Prompts. So, I think there would be problem with systemd-login.service file for so? Can anybody point, why there is no move ahead after this statement? A couple of things: a) Please make sure to enable all kernel options listed in README. b) Make sure your kernel is new enough, see README for version requirements. c) Make sure your root image has the correct directories in place so that systemd can mount things on them. d) Read the existing documentation about how to debug things like this: http://freedesktop.org/wiki/Software/systemd/Debugging/#index1h1 Thanks Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
Hi, From the log I attached previously, I think is log statement saying as below: Starting Login Service... But then , it gets stuck at [ OK ] Reached target Login Prompts. So, I think there would be problem with systemd-login.service file for so? Can anybody point, why there is no move ahead after this statement? Thanks, Jay ~~Disclaimer~~~ Information contained and transmitted by this e-mail is confidential and proprietary to IGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailad...@igate.com mailto:mailad...@igate.com. IGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of IGATE. IGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While IGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of softwar e viruses. You should carry out your own virus checks before opening an attachment. To know more about IGATE please visit www.igate.com http://www.igate.com. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
Please, try to ssh into the system when it is stuck and show us the log from `journalctl -b`. Or, alternatively, do as earlier, reboot the stuck system, boot with init=/bin/sh and get the log with `journalctl -b -1`. But ssh is preferred as it will let you troubleshoot the issue further interactively. On Jun 17, 2014 1:23 PM, Jay D Bhatt jay.bh...@igate.com wrote: Hi, From the log I attached previously, I think is log statement saying as below: Starting Login Service... But then , it gets stuck at [ OK ] Reached target Login Prompts. So, I think there would be problem with systemd-login.service file for so? Can anybody point, why there is no move ahead after this statement? Thanks, Jay ~~Disclaimer~~~ Information contained and transmitted by this e-mail is confidential and proprietary to IGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailad...@igate.com mailto: mailad...@igate.com. IGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of IGATE. IGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While IGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of softwar e viruses. You should carry out your own virus checks before opening an attachment. To know more about IGATE please visit www.igate.com http://www.igate.com. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
Hi Andrey, I also think getty is missing. There was no sbin/getty, it was agetty, so I created soft link to make sbin/getty. Secondly, cat /sys/class/tty/console/active was not possible as there was no folders structure inside /sys/. I didn't got your below question I see ssh service - are you able to ssh into it? How do I do ssh into it? Please guide. Other interesting thing I found was systemd rules were not set for ttymxc* . I set the rules for it, since I am using console=ttymxc3. So, now I am again building new rpm of system and generating image and checking out about hanging problem. If you find anything missing, let me know? Thanks, Jay ~~Disclaimer~~~ Information contained and transmitted by this e-mail is confidential and proprietary to IGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailad...@igate.com mailto:mailad...@igate.com. IGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of IGATE. IGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While IGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of softwar e viruses. You should carry out your own virus checks before opening an attachment. To know more about IGATE please visit www.igate.com http://www.igate.com. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
On Jun 16, 2014 2:12 PM, Jay D Bhatt jay.bh...@igate.com wrote: Hi Andrey, I also think getty is missing. There was no sbin/getty, it was agetty, so I created soft link to make sbin/getty. Hmm, I thought getty@.service actually invokes agetty directly, no? Secondly, cat /sys/class/tty/console/active was not possible as there was no folders structure inside /sys/. No tty/console stuff, or absolutely empty? An empty /sys might mean that systemd failed to mount sysfs. (I should re-read the earlier logs you posted.) It's again a kernel option, CONFIG_SYSFS if I remember correctly. I wonder how well udev and systemd even work without sysfs. I didn't got your below question I see ssh service - are you able to ssh into it? How do I do ssh into it? Please guide. By using `ssh root@ip-address`, with the IP address of the device. (Of course that only works if the device has networking configured as well, so not always useful...) Other interesting thing I found was systemd rules were not set for ttymxc* . I set the rules for it, since I am using console=ttymxc3. Hmm, I think systemd automatically starts a getty on the console device too, no? If ttymxc* is common, maybe it would be useful to send a patch for including it along with systemd's default rules... -- Mantas Mikulėnas graw...@gmail.com // sent from phone ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
On Mon, Jun 16, 2014 at 3:27 PM, Mantas Mikulėnas graw...@gmail.com wrote: On Jun 16, 2014 2:12 PM, Jay D Bhatt jay.bh...@igate.com wrote: Hi Andrey, I also think getty is missing. There was no sbin/getty, it was agetty, so I created soft link to make sbin/getty. Hmm, I thought getty@.service actually invokes agetty directly, no? Secondly, cat /sys/class/tty/console/active was not possible as there was no folders structure inside /sys/. Which likely explains why systemd did not auto-start getty on console. No tty/console stuff, or absolutely empty? An empty /sys might mean that systemd failed to mount sysfs. (I should re-read the earlier logs you posted.) It's again a kernel option, CONFIG_SYSFS if I remember correctly. I wonder how well udev and systemd even work without sysfs. I didn't got your below question I see ssh service - are you able to ssh into it? How do I do ssh into it? Please guide. By using `ssh root@ip-address`, with the IP address of the device. (Of course that only works if the device has networking configured as well, so not always useful...) Other interesting thing I found was systemd rules were not set for ttymxc* . I set the rules for it, since I am using console=ttymxc3. Hmm, I think systemd automatically starts a getty on the console device too, no? Sure, by looking in /sys ... If ttymxc* is common, maybe it would be useful to send a patch for including it along with systemd's default rules... ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
On Mon, Jun 16, 2014 at 3:12 PM, Jay D Bhatt jay.bh...@igate.com wrote: Hi Andrey, I also think getty is missing. There was no sbin/getty, it was agetty, so I created soft link to make sbin/getty. systemd already calls agetty, it si just that service is named getty@tty.service. Secondly, cat /sys/class/tty/console/active was not possible as there was no folders structure inside /sys/. I didn't got your below question I see ssh service - are you able to ssh into it? How do I do ssh into it? Please guide. Other interesting thing I found was systemd rules were not set for ttymxc* . Not sure which rules do you mean? I set the rules for it, since I am using console=ttymxc3. So, now I am again building new rpm of system and generating image and checking out about hanging problem. Do you have device node /dev/ttymxc3? If yes, you could try to explicitly enable getty service on it ln -s /usr/lib/systemd/system/getty@.service /etc/systemd/system/default.target.wants/getty@ttymxc3.service This /should/ give you login on console. (Yu ay need to create /etc/systemd/system/default.target.wants directory) Hmm ... but if you do not have sysfs, systemd may not notice that device is now available ... at least coldplugging of devices will definitely *not* work, and console driver is built in, so no getty service still. You need to sort out sysfs issue first. What ls -lR /sys shows? If you find anything missing, let me know? Mantas already commented on other parts. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
Hi Andrey, Mantas, The /sys/ folder is totally empty(no class folder ), ls -lR /sys give output 0, though my CONFIG_SYSFS=y is set in the kernel config parameters. Can you tell me what could be my contents inside /sys/ folder? After creating softlink of agetty to getty inside /sbin, creating below softlink: ln -s /usr/lib/systemd/system/getty@.service /etc/systemd/system/default.target.wants/getty@ttymxc3.service I also changed 99-systemd.rules.in file to add below line in system: SUBSYSTEM==tty, KERNEL==ttymxc*, TAG+=systemd Then I got ahead of Authorization manager, please see the attached log. After giving output [ OK ] Reached target Login Prompts. , it waits for some time and then gives blank screen with just cursor on console ,but no shell prompt or login . I feel, I am still missing something probably inside /sys folder or other things related with prompt or login? Any ideas to check what could I be missing? Thanks, Jay ~~Disclaimer~~~ Information contained and transmitted by this e-mail is confidential and proprietary to IGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailad...@igate.com mailto:mailad...@igate.com. IGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of IGATE. IGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While IGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening an attachment. To know more about IGATE please visit www.igate.com http://www.igate.com. Welcome to Tizen 3.0.0 (Tizen Next)! Starting Collect Read-Ahead Data... Expecting device dev-ttymxc3.device... [ OK ] Listening on Delayed Shutdown Socket. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Created slice Root Slice. [ OK ] Created slice User and Session Slice. [ OK ] Created slice System Slice. [ OK ] Created slice system-serial\x2dgetty.slice. [ OK ] Created slice system-getty.slice. [ OK ] Created slice system-launchpad\x2dpreload.slice. [ OK ] Created slice system-user\x2dsession\x2dlaunch.slice. [ OK ] Reached target Slices. [ OK ] Listening on udev Kernel Socket. [ OK ] Listening on udev Control Socket. [ OK ] Listening on Journal Socket. Starting udev Coldplug all Devices... Starting Create static device nodes in /dev... Starting Initialize the VConf storage... Mounting Debug File System... Starting Journal Service... [ OK ] Started Journal Service. [ OK ] Reached target Swap. Mounting Temporary Directory... [ OK ] Started Collect Read-Ahead Dattmpfs: Bad mount option smackfsroot a. [ OK ] Started Create static device nodes in /dev. [ OK ] Started Initialize the VConf storage. [ OK ] Mounted Debug File System. [FAILED] Failed to mount Temporary Directory. See 'systemctl status tmp.mount' for details. [DEPEND] Dependency failed for security-server-password-set.socket. [DEPEND] Dependency failed for security-server-cookie-get.socket. [DEPEND] Dependency failed for Wrt Security socket. [DEPEND] Dependency failed for security-server-data-share.socket. [DEPEND] Dependency failed for security-server-password-check.socket. [DEPEND] Dependency failed for security-server-privilege-by-pid.socket. [DEPEND] Dependency failed for security-server-get-gid.socket. [DEPEND] Dependency failed for security-server-cookie-check.socket. [DEPEND] Dependency failed for security-server-password-reset.socket. [DEPEND] Dependency failed for security-server-app-privilege-by-name.socket. [ OK ] Started udev Coldplug all Devices. [ OK ] Reached target Paths. [ OK ] Reached target security-server sockets. Starting udev Kernel Device Manager... Starting Setup Virtual Console... Starting Apply Kernel Variables... Starting Load/Save Random Seed... [ OK ] Reached target Local File Systems (Pre). [ OK ] Reached target Local File Systems. Starting Recreate Volatile Files and Directories... Starting Trigger Flushing of Journal to Persistent Storage... [ OK ] Started udev Kernel
Re: [systemd-devel] systemd not initializing
On Fri, 13.06.14 09:18, Jay D Bhatt (jay.bh...@igate.com) wrote: systemd-readahead[1485]: Failed to create fanotify object: Function not implemented Dec 31 18:43:12 192.168.149.68 mount[1616]: mount: wrong fs type, bad option, ba Please enable all kernel options mentioned in systemd's README. THis should fix a big bunch of your problems. Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
Hi, I have CONFIG_TMPFS=y set in kernel, but still it hangs at [ OK ] Started D-Bus System Message Bus. Starting Authorization Manager... Almost all kernel config parameters are set as mentioned in README file of systemd. I tried enable debug-shell.service , it executed perfectly..no output. Then I try systemctl list-jobs –full, it gives output “Failed to get D-Bus connection: No connection to service manager” I also think there could be problem with getty thing, its probably not getting the tty or console and that’s why its creating problems. But I don’t know which files to change to make the getty thing work? Thanks, Jay ~~Disclaimer~~~ Information contained and transmitted by this e-mail is confidential and proprietary to IGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailad...@igate.com mailto:mailad...@igate.com. IGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of IGATE. IGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While IGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening an attachment. To know more about IGATE please visit www.igate.com http://www.igate.com. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
В Fri, 13 Jun 2014 09:18:57 + Jay D Bhatt jay.bh...@igate.com пишет: Sorry, Forgot to send log. I got the previous log by command use `journalctl --boot -1` Please find the log attached. This time the system stopped prior to previous run. This time it stopped at : [ OK ] Started D-Bus System Message Bus. Starting Authorization Manager... What I miss in both your logs is any mention of anything related to getty on any line (serial or whatever). I.e. from normal boot on commodity PC: июн 13 13:21:25 opensuse.site systemd[1]: Starting Getty on tty1... июн 13 13:21:25 opensuse.site systemd[1]: Started Getty on tty1. So your system does not hang - it boots completely, but does not start getty so you cannot login. I see ssh service - are you able to ssh into it? What does cat /sys/class/tty/console/active show on your system? In any case, you can always add service to hardcode getty on console if autodetection fails for you (to enable debugging); do you know how console device is called? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
Hi Mantas, Thanks for your suggestions. I was able to run init=/sbin/init and run systemd but it completed only partially. I changed kernel options pointed by you and I was able to start /sbin/init. I have attached the log. In the log, I still see some [FAILED] parts. Can you suggest how to solve this or how to ignore them? Are they necessary ones? At the end of the log, you can see, It stops forever at [ OK ] Reached target Login Prompts. I think I am still missing something which doesn't complete systemd initialization. Why it gets stuck here? Thanks, Jay ~~Disclaimer~~~ Information contained and transmitted by this e-mail is confidential and proprietary to IGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailad...@igate.com mailto:mailad...@igate.com. IGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of IGATE. IGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While IGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening an attachment. To know more about IGATE please visit www.igate.com http://www.igate.com. Welcome to Tizen 3.0.0 (Tizen Next)! Starting Collect Read-Ahead Data... Expecting device dev-ttymxc3.device... [ OK ] Listening on Delayed Shutdown Socket. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Created slice Root Slice. [ OK ] Created slice User and Session Slice. [ OK ] Created slice System Slice. systemd-readahead[1486]: Failed to create fanotify object: Function not implemented [ OK ] Created slice system-serial\x2dgetty.slice. [ OK ] Created slice system-user\x2dsession\x2dlaunch.slice. [ OK ] Created slice system-launchpad\x2dpreload.slice. [ OK ] Reached target Slices. [ OK ] Listening on udev Kernel Socket. [ OK ] Listening on udev Control Socket. [ OK ] Listening on Journal Socket. Starting udev Coldplug all Devices... Mounting Debug File System... Starting Create static device nodes in /dev... Starting Initialize the VConf storage... Starting Journal Service... [ OK ] Started Journal Service. [ OK ] Reached target Swap. Mounting Temporary Directory... [ OK ] Started Collect Read-Ahead Data. [ OK ] Mounted Debug File System. [ OK ] Started Create static device nodes in /dev. [ OK ] Started Initialize the VConf storage. [FAILED] Failed to mount Temporary Directory. See 'systemctl status tmp.mount' for details. [DEPEND] Dependency failed for security-server-password-reset.socket. [DEPEND] Dependency failed for security-server-password-set.socket. [DEPEND] Dependency failed for security-server-password-check.socket. [DEPEND] Dependency failed for security-server-cookie-check.socket. [DEPEND] Dependency failed for security-server-cookie-get.socket. [DEPEND] Dependency failed for security-server-app-privilege-by-name.socket. [DEPEND] Dependency failed for security-server-privilege-by-pid.socket. [DEPEND] Dependency failed for security-server-get-gid.socket. [DEPEND] Dependency failed for security-server-data-share.socket. [DEPEND] Dependency failed for Wrt Security socket. [ OK ] Started udev Coldplug all Devices. [ OK ] Reached target Paths. [ OK ] Reached target security-server sockets. Starting udev Kernel Device Manager... [ OK ] Reached target Local File Systems (Pre). [ OK ] Reached target Local File Systems. Starting Trigger Flushing of Journal to Persistent Storage... Starting Setup Virtual Console... Starting Load/Save Random Seed... Starting Apply Kernel Variables... Starting Recreate Volatile Files and Directories... [ OK ] Started udev Kernel Device Manager. [ OK ] Started Setup Virtual Console. [ OK ] Started Load/Save Random Seed. [ OK ] Started Apply Kernel Variables. [ OK ] Found device /dev/ttymxc3. [ OK ] Reached target Sound Card. [FAILED] Failed to start Recreate Volatile Files and Directories. See 'systemctl status systemd-tmpfiles-setup.service' for details. Starting Update UTMP
Re: [systemd-devel] systemd not initializing
I logged in shell script using init=/bin/sh and executed journalctl --boot, It says No journal files were found. Failed to set boot id: No such file or directory . I don't get login prompt when I use init=/sbin/init, so tried with init=/bin/sh. Is it correct? Thanks, Jay ~~Disclaimer~~~ Information contained and transmitted by this e-mail is confidential and proprietary to IGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailad...@igate.com mailto:mailad...@igate.com. IGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of IGATE. IGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While IGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of softwar e viruses. You should carry out your own virus checks before opening an attachment. To know more about IGATE please visit www.igate.com http://www.igate.com. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
On Fri, Jun 13, 2014 at 9:31 AM, Jay D Bhatt jay.bh...@igate.com wrote: I logged in shell script using init=/bin/sh and executed journalctl --boot, It says No journal files were found. Failed to set boot id: No such file or directory . I don't get login prompt when I use init=/sbin/init, so tried with init=/bin/sh. Is it correct? Ah, then you would only have logs from the previous boot, not the current one. Also, it seems that the system only logs to /run, not to /var/log. If you're running this on a PC and have a tty9, you could enable debug-shell.service to start an early shell on that terminal. (Could be easily modified for another tty or serial access too.) Otherwise, you'll need to enable persistent logging: - Create a directory /var/log/journal, - and make sure /etc/systemd/journald.conf has either Storage=persistent or Storage=auto (the default). - Then reboot to systemd. - When it hangs, reboot again with init=/bin/sh, - and use `journalctl --boot -1` to get the previous boot's log. -- Mantas Mikulėnas graw...@gmail.com ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
I'm sorry to cut in but that's too interesting to keep just observing.
I guess it was `Failed to _g_et boot id` and it its about
`/proc/sys/kernel/random/boot_id`.
Is that kernel 2.3.15 or what?
{- offtopic
~~~
systemd-readahead[1486]: Failed to create fanotify object: Function not
implemented
~~~
Shouldn't readme mention CONFIG_FANOTIFY?
-}
--
Кирилл Елагин
On Fri, Jun 13, 2014 at 10:31 AM, Jay D Bhatt jay.bh...@igate.com wrote:
I logged in shell script using init=/bin/sh and executed journalctl
--boot, It says No journal files were found. Failed to set boot id: No
such file or directory .
I don't get login prompt when I use init=/sbin/init, so tried with
init=/bin/sh. Is it correct?
Thanks,
Jay
~~Disclaimer~~~
Information contained and transmitted by this e-mail is confidential and
proprietary to IGATE and its affiliates and is intended for use only by the
recipient. If you are not the intended recipient, you are hereby notified
that any dissemination, distribution, copying or use of this e-mail is
strictly prohibited and you are requested to delete this e-mail immediately
and notify the originator or mailad...@igate.com mailto:
mailad...@igate.com. IGATE does not enter into any agreement with any
party by e-mail. Any views expressed by an individual do not necessarily
reflect the view of IGATE. IGATE is not responsible for the consequences of
any actions taken on the basis of information provided, through this email.
The contents of an attachment to this e-mail may contain software viruses,
which could damage your own computer system. While IGATE has taken every
reasonable precaution to minimise this risk, we cannot accept liability for
any damage which you sustain as a result of softwar
e viruses. You should carry out your own virus checks before opening an
attachment. To know more about IGATE please visit www.igate.com
http://www.igate.com.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
On Fri, Jun 13, 2014 at 11:01 AM, Kirill Elagin kirela...@gmail.com wrote: I guess it was `Failed to _g_et boot id` and it its about `/proc/sys/kernel/random/boot_id`. Is that kernel 2.3.15 or what? Oh, never mind, that's probably just because `/proc` is not mounted when `init=/bin/sh`. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
I got the previous log by command use `journalctl --boot -1` Please find the log attached. This time the system stopped prior to previous run. This time it stopped at : [ OK ] Started D-Bus System Message Bus. Starting Authorization Manager... Thanks, Jay ~~Disclaimer~~~ Information contained and transmitted by this e-mail is confidential and proprietary to IGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailad...@igate.com mailto:mailad...@igate.com. IGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of IGATE. IGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While IGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of softwar e viruses. You should carry out your own virus checks before opening an attachment. To know more about IGATE please visit www.igate.com http://www.igate.com. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
Hi Kirill, I got to enable CONFIG_FANOTIFY in kernel, but I think this will not be high priority or blocking thing. Is it blocking thing? Thanks, Jay ~~Disclaimer~~~ Information contained and transmitted by this e-mail is confidential and proprietary to IGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailad...@igate.com mailto:mailad...@igate.com. IGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of IGATE. IGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While IGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening an attachment. To know more about IGATE please visit www.igate.com http://www.igate.com. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
HI Cristian, I got my systemd running but only partly. Though I haven't tried disabling smack and ima, does these effect my initialization(i.e. is disabling necessary), since my systemd log just says failed and moves ahead. Actually currently my system gets stuck at one point, I want to move ahead so, I am trying same. Thanks, Jay ~~Disclaimer~~~ Information contained and transmitted by this e-mail is confidential and proprietary to IGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailad...@igate.com mailto:mailad...@igate.com. IGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of IGATE. IGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While IGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of softwar e viruses. You should carry out your own virus checks before opening an attachment. To know more about IGATE please visit www.igate.com http://www.igate.com. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
No it's definitely not a blocker. You forgot to attach a log your previous message. -- Кирилл Елагин On Fri, Jun 13, 2014 at 1:09 PM, Jay D Bhatt jay.bh...@igate.com wrote: Hi Kirill, I got to enable CONFIG_FANOTIFY in kernel, but I think this will not be high priority or blocking thing. Is it blocking thing? Thanks, Jay ~~Disclaimer~~~ Information contained and transmitted by this e-mail is confidential and proprietary to IGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailad...@igate.com. IGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of IGATE. IGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While IGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening an attachment. To know more about IGATE please visit www.igate.com. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
Thanks. I surely forgot to attach log. Now you can find it attached. Thanks, Jay ~~Disclaimer~~~ Information contained and transmitted by this e-mail is confidential and proprietary to IGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailad...@igate.com mailto:mailad...@igate.com. IGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of IGATE. IGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While IGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening an attachment. To know more about IGATE please visit www.igate.com http://www.igate.com. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
It seems systemd cannot mount /tmp, possibly because the kernel does not have CONFIG_TMPFS=y. I think this is required – while tmp.mount (in-memory /tmp) can be masked, but systemd will always try to mount a tmpfs on /run, for daemons' runtime data. Not sure if that's why it hangs though. Would be nice to check the state from inside – e.g. enable debug-shell.service and check `systemctl list-jobs --full` when it hangs on the next boot... (It runs on tty9; edit the service file if you only have serial console.) Another possible method is to boot a minimal system in either rescue or emergency mode (single or emergency as kernel parameters) and try starting multi-user.target manually... -- Mantas Mikulėnas graw...@gmail.com // sent from phone On Jun 13, 2014 12:19 PM, Jay D Bhatt jay.bh...@igate.com wrote: Sorry, Forgot to send log. I got the previous log by command use `journalctl --boot -1` Please find the log attached. This time the system stopped prior to previous run. This time it stopped at : [ OK ] Started D-Bus System Message Bus. Starting Authorization Manager... Thanks, Jay ~~Disclaimer~~~ Information contained and transmitted by this e-mail is confidential and proprietary to IGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailad...@igate.com mailto: mailad...@igate.com. IGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of IGATE. IGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While IGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening an attachment. To know more about IGATE please visit www.igate.com http://www.igate.com. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
First of all the log is somewhat deformed. You could probably add `--no-pager` or something like this to see the full lines. It's not clear why mounting /tmp fails as I can't see any errors about failing to mount /run and as far as I can tell there should be an error logged in case it fails as /run is MNT_FATAL. Also I've noticed: ~~ Dec 31 18:43:16 192.168.149.68 systemd[1]: Listening on sshd.socket. ~~ so it looks like if you have difficulties with consoles you might try to ssh in. -- Кирилл Елагин On Fri, Jun 13, 2014 at 1:18 PM, Jay D Bhatt jay.bh...@igate.com wrote: Sorry, Forgot to send log. I got the previous log by command use `journalctl --boot -1` Please find the log attached. This time the system stopped prior to previous run. This time it stopped at : [ OK ] Started D-Bus System Message Bus. Starting Authorization Manager... Thanks, Jay ~~Disclaimer~~~ Information contained and transmitted by this e-mail is confidential and proprietary to IGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailad...@igate.com mailto: mailad...@igate.com. IGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of IGATE. IGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While IGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening an attachment. To know more about IGATE please visit www.igate.com http://www.igate.com. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
El 13/06/14 05:19, Jay D Bhatt escribió: Thanks. I surely forgot to attach log. Now you can find it attached. Nope, there is no attached log in your message. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
Am 13.06.2014 16:35, schrieb Cristian Rodríguez: El 13/06/14 05:19, Jay D Bhatt escribió: Thanks. I surely forgot to attach log. Now you can find it attached. Nope, there is no attached log in your message because he sent the attachment one message before and found it useful to drop another one refer to that signature.asc Description: OpenPGP digital signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
On Thu, Jun 12, 2014 at 6:44 AM, Jay D Bhatt jay.bh...@igate.com wrote: Hi Mantas, Thanks for your reply. I tried putting boot options boot options loglevel=6, systemd.log_level=debug Maybe also systemd.log_target=console? I don't remember if that's needed But it got stuck as before. So I added init=/bin/sh to the arguments and removed system.log_level=debug. Then I could have the Shell command line but it gave some messages before giving shell command: Sh: cannot set terminal process group (-1): Inappropriate ioctl for device Sh: no job control in this shell That's normal when booting with init=/bin/sh. I saw that system.log_level=debug does not have any impact here. Also when I gave path of my init file init=/sbin/init, it still hangs as previously. Though my file is present in that path, I don't understand why it does not take it. Maybe it hangs very early... 0. Make sure you have `strace` installed; 1. Boot with init=/bin/sh; 2. Run exactly this in the shell: exec strace -D /sbin/init 3. See where it hangs. Oh, make sure your kernel has CONFIG_FHANDLE enabled, too. I don't have inittab file in /etc/. Is that the reason, since init might not be able to find inittab and gets lost or something. No; systemd does not use that file. It is configuration for SysV init only. -- Mantas Mikulėnas graw...@gmail.com ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
Hi Mantas,
The systemd_loglevel=console doesn't work either. So, I tried the command of
strace which you suggested. I have taken the log of that output. Please find
attached output file.
Can you suggest what could be wrong with init after looking at log?
Thanks,
Jay Bhatt
~~Disclaimer~~~
Information contained and transmitted by this e-mail is confidential and
proprietary to IGATE and its affiliates and is intended for use only by the
recipient. If you are not the intended recipient, you are hereby notified that
any dissemination, distribution, copying or use of this e-mail is strictly
prohibited and you are requested to delete this e-mail immediately and notify
the originator or mailad...@igate.com mailto:mailad...@igate.com. IGATE does
not enter into any agreement with any party by e-mail. Any views expressed by
an individual do not necessarily reflect the view of IGATE. IGATE is not
responsible for the consequences of any actions taken on the basis of
information provided, through this email. The contents of an attachment to this
e-mail may contain software viruses, which could damage your own computer
system. While IGATE has taken every reasonable precaution to minimise this
risk, we cannot accept liability for any damage which you sustain as a result
of software viruses. You should carry out your own virus checks before opening
an attachment. To know more about IGATE please visit www.igate.com
http://www.igate.com.
Process 1530 attached
execve(/sbin/init, [/sbin/init], [/* 5 vars */]) = 0
brk(0) = 0xce000
uname({sys=Linux, node=192.168.149.68, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x2ab02000
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or directory)
open(/etc/ld.so.cache, O_RDONLY|O_CLOEXEC) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=38873, ...}) = 0
mmap2(NULL, 38873, PROT_READ, MAP_PRIVATE, 3, 0) = 0x2ab1a000
close(3)= 0
open(/lib/libsystemd-daemon.so.0, O_RDONLY|O_CLOEXEC) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0|\v\0\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=13572, ...}) = 0
mmap2(NULL, 40968, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x2ab45000
mprotect(0x2ab47000, 28672, PROT_NONE) = 0
mmap2(0x2ab4e000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1000) = 0x2ab4e000
close(3)= 0
open(/lib/libudev.so.1, O_RDONLY|O_CLOEXEC) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\370+\0\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=77492, ...}) = 0
mmap2(NULL, 88120, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x2aba6000
mprotect(0x2abb2000, 32768, PROT_NONE) = 0
mmap2(0x2abba000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xc000) = 0x2abba000
close(3)= 0
open(/lib/libpam.so.0, O_RDONLY|O_CLOEXEC) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0\37\0\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=49652, ...}) = 0
mmap2(NULL, 69956, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x2ab8d000
mprotect(0x2ab96000, 28672, PROT_NONE) = 0
mmap2(0x2ab9d000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x8000) = 0x2ab9d000
close(3)= 0
open(/lib/libcap.so.2, O_RDONLY|O_CLOEXEC) = 3
read(3,
\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\254\21\0\0004\0\0\0..., 512) =
512
fstat64(3, {st_mode=S_IFREG|0755, st_size=17128, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x2ab3a000
mmap2(NULL, 45376, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x2abf7000
mprotect(0x2abfa000, 28672, PROT_NONE) = 0
mmap2(0x2ac01000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x2ac01000
close(3)= 0
open(/lib/libkmod.so.2, O_RDONLY|O_CLOEXEC) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\340'\0\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=84476, ...}) = 0
mmap2(NULL, 90568, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x2abbc000
mprotect(0x2abca000, 28672, PROT_NONE) = 0
mmap2(0x2abd1000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xd000) = 0x2abd1000
close(3)= 0
open(/lib/libdbus-1.so.3, O_RDONLY|O_CLOEXEC) = 3
read(3,
\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\340\24\1\0004\0\0\0..., 512) =
512
fstat64(3, {st_mode=S_IFREG|0755, st_size=236888, ...}) = 0
mmap2(NULL, 253260,
Re: [systemd-devel] systemd not initializing
On Thu, Jun 12, 2014 at 9:24 AM, Jay D Bhatt jay.bh...@igate.com wrote: Hi Mantas, The systemd_loglevel=console doesn't work either. So, I tried the command of strace which you suggested. I have taken the log of that output. Please find attached output file. Hmm, did you use `exec`, and the -D option with strace? Could you try again making sure that both of them are in your command? Also, if you boot with init=/bin/sh and run `echo $$` in the early shell, does it output PID 1 or something else? (systemd is an init system and wants to have PID 1, so stracing it is somewhat harder. In your log, it doesn't even attempt to boot because of different PID, so the log isn't particularly useful.) -- Mantas Mikulėnas graw...@gmail.com ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
Hi Mantas,
I checked the PID by using command 'echo $$' and got reply 1.
I used command: exec trace -D /sbin/init and took the log, which is attached.
In the log , I find lot of (Function not implemented),(No such file or
directory) mentions. It seems difficult to figure out which one might be
causing the problem.
Could you check the log, if you could point out some problem?
Thanks,
Jay
~~Disclaimer~~~
Information contained and transmitted by this e-mail is confidential and
proprietary to IGATE and its affiliates and is intended for use only by the
recipient. If you are not the intended recipient, you are hereby notified that
any dissemination, distribution, copying or use of this e-mail is strictly
prohibited and you are requested to delete this e-mail immediately and notify
the originator or mailad...@igate.com mailto:mailad...@igate.com. IGATE does
not enter into any agreement with any party by e-mail. Any views expressed by
an individual do not necessarily reflect the view of IGATE. IGATE is not
responsible for the consequences of any actions taken on the basis of
information provided, through this email. The contents of an attachment to this
e-mail may contain software viruses, which could damage your own computer
system. While IGATE has taken every reasonable precaution to minimise this
risk, we cannot accept liability for any damage which you sustain as a result
of software viruses. You should carry out your own virus checks before opening
an attachment. To know more about IGATE please visit www.igate.com
http://www.igate.com.
sh-4.2# exec strace -D /sbin/init
Process 1 attached
execve(/sbin/init, [/sbin/init], [/* 4 vars */]) = 0
brk(0) = 0xce000
uname({sys=Linux, node=192.168.149.68, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x2aadc000
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or directory)
open(/etc/ld.so.cache, O_RDONLY|O_CLOEXEC) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=38873, ...}) = 0
mmap2(NULL, 38873, PROT_READ, MAP_PRIVATE, 3, 0) = 0x2abd2000
close(3)= 0
open(/lib/libsystemd-daemon.so.0, O_RDONLY|O_CLOEXEC) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0|\v\0\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=13572, ...}) = 0
mmap2(NULL, 40968, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x2ac47000
mprotect(0x2ac49000, 28672, PROT_NONE) = 0
mmap2(0x2ac5, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1000) = 0x2ac5
close(3)= 0
open(/lib/libudev.so.1, O_RDONLY|O_CLOEXEC) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\370+\0\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=77492, ...}) = 0
mmap2(NULL, 88120, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x2ab3
mprotect(0x2ab3c000, 32768, PROT_NONE) = 0
mmap2(0x2ab44000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xc000) = 0x2ab44000
close(3)= 0
open(/lib/libpam.so.0, O_RDONLY|O_CLOEXEC) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0\37\0\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=49652, ...}) = 0
mmap2(NULL, 69956, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x2ab97000
mprotect(0x2aba, 28672, PROT_NONE) = 0
mmap2(0x2aba7000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x8000) = 0x2aba7000
close(3)= 0
open(/lib/libcap.so.2, O_RDONLY|O_CLOEXEC) = 3
read(3,
\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\254\21\0\0004\0\0\0..., 512) =
512
fstat64(3, {st_mode=S_IFREG|0755, st_size=17128, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x2ab16000
mmap2(NULL, 45376, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x2ab23000
mprotect(0x2ab26000, 28672, PROT_NONE) = 0
mmap2(0x2ab2d000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x2ab2d000
close(3)= 0
open(/lib/libkmod.so.2, O_RDONLY|O_CLOEXEC) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\340'\0\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=84476, ...}) = 0
mmap2(NULL, 90568, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x2ab46000
mprotect(0x2ab54000, 28672, PROT_NONE) = 0
mmap2(0x2ab5b000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xd000) = 0x2ab5b000
close(3)= 0
open(/lib/libdbus-1.so.3, O_RDONLY|O_CLOEXEC) = 3
read(3,
Re: [systemd-devel] systemd not initializing
On Thu, Jun 12, 2014 at 11:36 AM, Jay D Bhatt jay.bh...@igate.com wrote: Hi Mantas, I checked the PID by using command 'echo $$' and got reply 1. I used command: exec trace -D /sbin/init and took the log, which is attached. In the log , I find lot of (Function not implemented),(No such file or directory) mentions. It seems difficult to figure out which one might be causing the problem. Could you check the log, if you could point out some problem? The log looks useful this time; it shows that you're missing two kernel options: name_to_handle_at(0xff9c, 0x96444, 0x7eefb7b8, 0x7eefb844, 0x400) = -1 ENOSYS (Function not implemented) The kernel is missing CONFIG_FHANDLE=y. Your systemd version seems to work without it, but in recent releases it is now required. mount(devtmpfs, /dev, devtmpfs, MS_NOSUID|MS_STRICTATIME, mode=755) = -1 ENODEV (No such device) The kernel is missing CONFIG_DEVTMPFS=y, which is now required. access(/proc/vz, F_OK)= -1 ENOENT (No such file or directory) systemd is trying to detect some container mechanisms; ENOENT is expected on bare hardware. mount(securityfs, /sys/kernel/security, securityfs, MS_NOSUID|MS_NODEV|MS_NOEXEC, NULL) = -1 ENOENT (No such file or directory) mount(smackfs, /sys/fs/smackfs, smackfs, MS_NOSUID|MS_NODEV|MS_NOEXEC|MS_STRICTATIME, smackfsdef=*) = -1 ENOENT (No such file or directory) stat64(/etc/ima/ima-policy, 0x7eefb958) = -1 ENOENT (No such file or directory) open(/sys/fs/smackfs/load2, O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE|O_CLOEXEC, 0666) = -1 ENOENT (No such file or directory) systemd is checking if it should load SMACK or IMA policy; this can be safely ignored if you don't use these security modules. -- Mantas Mikulėnas graw...@gmail.com ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
El 12/06/14 04:51, Mantas Mikulėnas escribió: name_to_handle_at(0xff9c, 0x96444, 0x7eefb7b8, 0x7eefb844, 0x400) = -1 ENOSYS (Function not implemented) systemd is checking if it should load SMACK or IMA policy; this can be safely ignored if you don't use these security modules. Or could build with --disable-ima --disable-smack if none of those features is needed. -- Cristian I don't know the key to success, but the key to failure is trying to please everybody. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
On Wed, Jun 11, 2014 at 2:04 PM, Jay D Bhatt jay.bh...@igate.com wrote: Hi, I am working on the Freescale hardware. I am using u-boot and uImage provided with hardware. When I try to boot the Tizen on my board, It boots u-boot and kernel uImage loads fine. But it stops at “Freeing Init Memory: 244k” and does not do anything. I wanted to know how does the kernel contact systemd for initialization? I checked the kernel configurations and made is suitable for systemd initialization, but still the same problem remains. I don’t get login prompt , so I can’t debug what’s going on during initialization process through sysctl . Could anybody suggest what could I be missing or any help on explanation on how kernel passes command to system initialization? It works the same way as other init systems: If you use an initramfs, the kernel looks for an /init program inside, and executes it as PID 1. (The initramfs /init then mounts real root and exec's /sbin/init found there.) Without an initramfs, the kernel looks for /sbin/init, /etc/init, /bin/init directly on the root filesystem (can be overridden using the init=... option) (The initramfs /init itself can be systemd, though most distros have it as just a shell script.) Try the boot options loglevel=6, systemd.log_level=debug, or init=/bin/sh. -- Mantas Mikulėnas graw...@gmail.com ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd not initializing
Hi Mantas, Thanks for your reply. I tried putting boot options boot options loglevel=6, systemd.log_level=debug But it got stuck as before. So I added init=/bin/sh to the arguments and removed system.log_level=debug. Then I could have the Shell command line but it gave some messages before giving shell command: Sh: cannot set terminal process group (-1): Inappropriate ioctl for device Sh: no job control in this shell I saw that system.log_level=debug does not have any impact here. Also when I gave path of my init file init=/sbin/init, it still hangs as previously. Though my file is present in that path, I don't understand why it does not take it. I don't have inittab file in /etc/. Is that the reason, since init might not be able to find inittab and gets lost or something. Thanks, Jay ~~Disclaimer~~~ Information contained and transmitted by this e-mail is confidential and proprietary to IGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailad...@igate.com mailto:mailad...@igate.com. IGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of IGATE. IGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While IGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of softwar e viruses. You should carry out your own virus checks before opening an attachment. To know more about IGATE please visit www.igate.com http://www.igate.com. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
