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
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
interactiv
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
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
On Mon, Jun 16, 2014 at 3:12 PM, Jay D Bhatt 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@.service.
> Secondly, "cat /sys/class/t
On Mon, Jun 16, 2014 at 3:27 PM, Mantas Mikulėnas wrote:
> On Jun 16, 2014 2:12 PM, "Jay D Bhatt" 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 "
On Jun 16, 2014 2:12 PM, "Jay D Bhatt" 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"
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
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..n
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
В Fri, 13 Jun 2014 09:18:57 +
Jay D Bhatt пишет:
> 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-Bu
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 t
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.freedeskto
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 /ru
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
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
prop
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 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 bloc
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
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~~~
Informat
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
On Fri, Jun 13, 2014 at 11:01 AM, Kirill Elagin 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`.
__
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
On Fri, Jun 13, 2014 at 9:31 AM, Jay D Bhatt 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
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
~~~
On Fri, Jun 13, 2014 at 9:13 AM, Jay D Bhatt wrote:
> 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 th
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 so
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
On Thu, Jun 12, 2014 at 11:36 AM, Jay D Bhatt 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
> direc
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
On Thu, Jun 12, 2014 at 9:24 AM, Jay D Bhatt 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 wit
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
On Thu, Jun 12, 2014 at 6:44 AM, Jay D Bhatt 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=/bi
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
gi
On Wed, Jun 11, 2014 at 2:04 PM, Jay D Bhatt 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” an
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
35 matches
Mail list logo
