FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora User

 
 
LinkBack Thread Tools
 
Old 09-05-2011, 09:33 AM
Xiao Peng Wang
 
Default F15, diskless node, systemctl start tmpfs.device timeout

Hi,


I made a diskless image against Fedora15, during the boot I found it displayed the following error message and went into emergency mode.



The error message:
Starting Relabel all filesystems, if necessary ^[[1;31maborted^[[0m because a dependency failed.

[ 107.607155] systemd[1]: Job fedora-autorelabel.service/start failed with result 'dependency'.

Starting Mark the need to relabel after reboot ^[[1;31maborted^[[0m because a dependency failed.

[ 107.625156] systemd[1]: Job fedora-autorelabel-mark.service/start failed with result 'dependency'.

[ 107.634580] systemd[1]: Job local-fs.target/start failed with result 'dependency'.

[ 107.642615] systemd[1]: Triggering of local-fs.target.

[ 107.650738] systemd[1]: Job var-tmp.mount/start failed with result 'dependency'.

[ 107.658580] systemd[1]: Job fsck@tmpfs.service/start failed with result 'dependency'.

[ 107.666876] systemd[1]: Job tmpfs.device/start failed with result 'timeout'.

Welcome to emergency mode. Use "systemctl default" or ^D to activate default mode.




And when I run the command 'service sshd start' to start the sshd, it displayed the following error message:
[ 8545.884404] udev[2872]: starting version 167

[ 8635.560123] systemd[1]: Job tmpfs.device/start timed out.

[ 8635.565867] systemd[1]: Job fedora-autorelabel.service/start failed with result 'dependency'.

[ 8635.574812] systemd[1]: Job fedora-autorelabel-mark.service/start failed with result 'dependency'.

[ 8635.584217] systemd[1]: Job local-fs.target/start failed with result 'dependency'.

[ 8635.592203] systemd[1]: Triggering of local-fs.target.

[ 8635.600311] systemd[1]: Job var-tmp.mount/start failed with result 'dependency'.

[ 8635.608102] systemd[1]: Job fsck@tmpfs.service/start failed with result 'dependency'.

[ 8635.616355] systemd[1]: Job tmpfs.device/start failed with result 'timeout'.

Welcome to emergency mode. Use "systemctl default" or ^D to activate default mode.


Then I tried to start the tmpfs.device
# systemctl start tmpfs.device
[432039.543362] systemd[1]: Job tmpfs.device/start timed out.

[432039.549335] systemdJob timed out.



Looks like the tmpfs.device was not installed. Did I miss something that depended by system? Any comments are appreciated.




Thanks

Best Regards

----------------------------------------------------------------------

Wang Xiaopeng (王晓朋)

IBM China System Technology Laboratory

Tel: 86-10-82453455

Email: wxp@cn.ibm.com

Address: 28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 09-05-2011, 01:08 PM
Frantisek Hanzlik
 
Default F15, diskless node, systemctl start tmpfs.device timeout

Xiao Peng Wang wrote:
> Hi,
>
> I made a diskless image against Fedora15, during the boot I found it
> displayed the following error message and went into emergency mode.
>
> The error message:
> Starting Relabel all filesystems, if necessary ^[[1;31maborted^[[0m
> because a dependency failed.
> [ 107.607155] systemd[1]: Job fedora-autorelabel.service/start failed
> with result 'dependency'.
> Starting Mark the need to relabel after reboot ^[[1;31maborted^[[0m
> because a dependency failed.
> [ 107.625156] systemd[1]: Job fedora-autorelabel-mark.service/start
> failed with result 'dependency'.
> [ 107.634580] systemd[1]: Job local-fs.target/start failed with result
> 'dependency'.
> [ 107.642615] systemd[1]: Triggering OnFailure= dependencies of
> local-fs.target.
> [ 107.650738] systemd[1]: Job var-tmp.mount/start failed with result
> 'dependency'.
> [ 107.658580] systemd[1]: Job fsck@tmpfs.service/start failed with
> result 'dependency'.
> [ 107.666876] systemd[1]: Job tmpfs.device/start failed with result
> 'timeout'.
> Welcome to emergency mode. Use "systemctl default" or ^D to activate
> default mode.
>
> And when I run the command 'service sshd start' to start the sshd, it
> displayed the following error message:
> [ 8545.884404] udev[2872]: starting version 167
> [ 8635.560123] systemd[1]: Job tmpfs.device/start timed out.
> [ 8635.565867] systemd[1]: Job fedora-autorelabel.service/start failed
> with result 'dependency'.
> [ 8635.574812] systemd[1]: Job fedora-autorelabel-mark.service/start
> failed with result 'dependency'.
> [ 8635.584217] systemd[1]: Job local-fs.target/start failed with
> result 'dependency'.
> [ 8635.592203] systemd[1]: Triggering OnFailure= dependencies of
> local-fs.target.
> [ 8635.600311] systemd[1]: Job var-tmp.mount/start failed with result
> 'dependency'.
> [ 8635.608102] systemd[1]: Job fsck@tmpfs.service/start failed with
> result 'dependency'.
> [ 8635.616355] systemd[1]: Job tmpfs.device/start failed with result
> 'timeout'.
> Welcome to emergency mode. Use "systemctl default" or ^D to activate
> default mode.
> Then I tried to start the tmpfs.device
> # systemctl start tmpfs.device
> [432039.543362] systemd[1]: Job tmpfs.device/start timed out.
> [432039.549335] systemdJob timed out.
> Looks like the tmpfs.device was not installed. Did I miss something that
> depended by system? Any comments are appreciated.
>
>
>
> Thanks
> Best Regards
> ----------------------------------------------------------------------
> Wang Xiaopeng (王晓朋)
> IBM China System Technology Laboratory
> Tel: 86-10-82453455
> Email: wxp@cn.ibm.com
> Address: 28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road, Haidian
> District Beijing P.R.China 100193 !DSPAM:4e6497a4108619485919262!

Emergency mode systemd target is equivalent to runlevel 1 singleuser
mode at SysV init system, thus probably network isn't active and sshd
refuses to run.

I'm not sure, but tmpfs (shm fs) need active swap, which probably isn't
on diskless station.

Another question is, when SELinux is appropriate to run on diskless
station (you may try disable it).

I also saw problem, when dracut was not able start diskless PXE F14
station when LAN default router was down (but it isn't this case).

Or there is just reciprocal proportion principle: when systemd consumes
10x more RAM then SysV init, then he can 10x fewer.
(narrowly, i686 F15 system comsumes 9x more RAM compared to i686 F7
SysVinit on my systems)


Franta Hanzlik
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 09-05-2011, 05:35 PM
Robert Arkiletian
 
Default F15, diskless node, systemctl start tmpfs.device timeout

2011/9/5 Xiao Peng Wang <wxp@cn.ibm.com>:
> Hi,
>
> I made a diskless image against Fedora15, during the boot I found it
> displayed the following error message and went into emergency mode.
>

Not 100% sure but take a look at this

http://fedoraproject.org/wiki/Features/var-run-tmpfs

and also try

systemctl enable NetworkManager-wait-online.service


PS please send posts to the mailing list in plain text


--
Robert Arkiletian
Eric Hamber Secondary, Vancouver, Canada
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 09-06-2011, 02:21 PM
Daniel J Walsh
 
Default F15, diskless node, systemctl start tmpfs.device timeout

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/05/2011 09:08 AM, Frantisek Hanzlik wrote:
> Xiao Peng Wang wrote:
>> Hi,
>>
>> I made a diskless image against Fedora15, during the boot I found
>> it displayed the following error message and went into emergency
>> mode.
>>
>> The error message: Starting Relabel all filesystems, if necessary
>> ^[[1;31maborted^[[0m because a dependency failed. [ 107.607155]
>> systemd[1]: Job fedora-autorelabel.service/start failed with
>> result 'dependency'. Starting Mark the need to relabel after
>> reboot ^[[1;31maborted^[[0m because a dependency failed. [
>> 107.625156] systemd[1]: Job
>> fedora-autorelabel-mark.service/start failed with result
>> 'dependency'. [ 107.634580] systemd[1]: Job local-fs.target/start
>> failed with result 'dependency'. [ 107.642615] systemd[1]:
>> Triggering OnFailure= dependencies of local-fs.target. [
>> 107.650738] systemd[1]: Job var-tmp.mount/start failed with
>> result 'dependency'. [ 107.658580] systemd[1]: Job
>> fsck@tmpfs.service/start failed with result 'dependency'. [
>> 107.666876] systemd[1]: Job tmpfs.device/start failed with
>> result 'timeout'. Welcome to emergency mode. Use "systemctl
>> default" or ^D to activate default mode.
>>
>> And when I run the command 'service sshd start' to start the
>> sshd, it displayed the following error message: [ 8545.884404]
>> udev[2872]: starting version 167 [ 8635.560123] systemd[1]: Job
>> tmpfs.device/start timed out. [ 8635.565867] systemd[1]: Job
>> fedora-autorelabel.service/start failed with result
>> 'dependency'. [ 8635.574812] systemd[1]: Job
>> fedora-autorelabel-mark.service/start failed with result
>> 'dependency'. [ 8635.584217] systemd[1]: Job
>> local-fs.target/start failed with result 'dependency'. [
>> 8635.592203] systemd[1]: Triggering OnFailure= dependencies of
>> local-fs.target. [ 8635.600311] systemd[1]: Job
>> var-tmp.mount/start failed with result 'dependency'. [
>> 8635.608102] systemd[1]: Job fsck@tmpfs.service/start failed
>> with result 'dependency'. [ 8635.616355] systemd[1]: Job
>> tmpfs.device/start failed with result 'timeout'. Welcome to
>> emergency mode. Use "systemctl default" or ^D to activate default
>> mode. Then I tried to start the tmpfs.device # systemctl start
>> tmpfs.device [432039.543362] systemd[1]: Job tmpfs.device/start
>> timed out. [432039.549335] systemdJob timed out. Looks like the
>> tmpfs.device was not installed. Did I miss something that
>> depended by system? Any comments are appreciated.
>>
>>
>>
>> Thanks Best Regards
>> ----------------------------------------------------------------------
>>
>>
Wang Xiaopeng (王晓朋)
>> IBM China System Technology Laboratory Tel: 86-10-82453455 Email:
>> wxp@cn.ibm.com Address: 28,ZhongGuanCun Software Park,No.8 Dong
>> Bei Wang West Road, Haidian District Beijing P.R.China 100193
>> !DSPAM:4e6497a4108619485919262!
>
> Emergency mode systemd target is equivalent to runlevel 1
> singleuser mode at SysV init system, thus probably network isn't
> active and sshd refuses to run.
>
> I'm not sure, but tmpfs (shm fs) need active swap, which probably
> isn't on diskless station.
>
> Another question is, when SELinux is appropriate to run on
> diskless station (you may try disable it).
>
> I also saw problem, when dracut was not able start diskless PXE
> F14 station when LAN default router was down (but it isn't this
> case).
>
> Or there is just reciprocal proportion principle: when systemd
> consumes 10x more RAM then SysV init, then he can 10x fewer.
> (narrowly, i686 F15 system comsumes 9x more RAM compared to i686
> F7 SysVinit on my systems)
>
>
> Franta Hanzlik


Yes since we do not support labeling on NFS, SELinux most likely will
not work in this environment.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5mLGcACgkQrlYvE4MpobOexQCgzPZmNZLa2F roQ38EbhPCYHqX
1dIAn1FrBWgJSXUWRO9++e4sNgKRiNQA
=n91G
-----END PGP SIGNATURE-----
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 09-13-2011, 10:37 AM
Xiao Peng Wang
 
Default F15, diskless node, systemctl start tmpfs.device timeout

Frantisek,



Thanks for your reply.



I tried to link the /lib/systemd/system/default.target to /lib/systemd/system/graphical.target, but the error same.



And you mentioned the swap, I don't know to enable it, could you give me a hint?



I also found the selinux was not installed on the diskless node. Then entry 'SELINUX=disabled' was configured in the /etc/sysconfig/selinux.



I found a way to workaround the starting of sshd.

I commented out the '. /etc/rc.d/init.d/functions' from the sshd control file: /etc/init.d/sshd. Then sshd was started successfully.



Thanks

Best Regards

----------------------------------------------------------------------

Wang Xiaopeng (王晓朋)

IBM China System Technology Laboratory

Tel: 86-10-82453455

Email: wxp@cn.ibm.com

Address: 28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193



Frantisek Hanzlik ---2011-09-05 21:11:35---Xiao Peng Wang wrote: > Hi,



From: Frantisek Hanzlik <franta@hanzlici.cz>

To: Community support for Fedora users <users@lists.fedoraproject.org>

Date: 2011-09-05 21:11

Subject: Re: F15, diskless node, systemctl start tmpfs.device timeout

Sent by: users-bounces@lists.fedoraproject.org







Xiao Peng Wang wrote:

> Hi,

>

> * * I made a diskless image against Fedora15, during the boot I found it

> * * displayed the following error message and went into emergency mode.

>

> * * The error message:

> * * * * Starting Relabel all filesystems, if necessary ^[[1;31maborted^[[0m

> * * * * because a dependency failed.

> * * * * [ 107.607155] systemd[1]: Job fedora-autorelabel.service/start failed

> * * * * with result 'dependency'.

> * * * * Starting Mark the need to relabel after reboot ^[[1;31maborted^[[0m

> * * * * because a dependency failed.

> * * * * [ 107.625156] systemd[1]: Job fedora-autorelabel-mark.service/start

> * * * * failed with result 'dependency'.

> * * * * [ 107.634580] systemd[1]: Job local-fs.target/start failed with result

> * * * * 'dependency'.

> * * * * [ 107.642615] systemd[1]: Triggering of

> * * * * local-fs.target.

> * * * * [ 107.650738] systemd[1]: Job var-tmp.mount/start failed with result

> * * * * 'dependency'.

> * * * * [ 107.658580] systemd[1]: Job fsck@tmpfs.service/start failed with

> * * * * result 'dependency'.

> * * * * [ 107.666876] systemd[1]: Job tmpfs.device/start failed with result

> * * * * 'timeout'.

> * * * * Welcome to emergency mode. Use "systemctl default" or ^D to activate

> * * * * default mode.

>

> * * And when I run the command 'service sshd start' to start the sshd, it

> * * displayed the following error message:

> * * * * [ 8545.884404] udev[2872]: starting version 167

> * * * * [ 8635.560123] systemd[1]: Job tmpfs.device/start timed out.

> * * * * [ 8635.565867] systemd[1]: Job fedora-autorelabel.service/start failed

> * * * * with result 'dependency'.

> * * * * [ 8635.574812] systemd[1]: Job fedora-autorelabel-mark.service/start

> * * * * failed with result 'dependency'.

> * * * * [ 8635.584217] systemd[1]: Job local-fs.target/start failed with

> * * * * result 'dependency'.

> * * * * [ 8635.592203] systemd[1]: Triggering of

> * * * * local-fs.target.

> * * * * [ 8635.600311] systemd[1]: Job var-tmp.mount/start failed with result

> * * * * 'dependency'.

> * * * * [ 8635.608102] systemd[1]: Job fsck@tmpfs.service/start failed with

> * * * * result 'dependency'.

> * * * * [ 8635.616355] systemd[1]: Job tmpfs.device/start failed with result

> * * * * 'timeout'.

> * * * * Welcome to emergency mode. Use "systemctl default" or ^D to activate

> * * * * default mode.

> * * Then I tried to start the tmpfs.device

> * * * * # systemctl start tmpfs.device

> * * * * * * [432039.543362] systemd[1]: Job tmpfs.device/start timed out.

> * * * * * * [432039.549335] systemdJob timed out.

> * * Looks like the tmpfs.device was not installed. Did I miss something that

> * * depended by system? Any comments are appreciated.

>

>

>

> Thanks

> Best Regards

> ----------------------------------------------------------------------

> Wang Xiaopeng (王晓朋)

> IBM China System Technology Laboratory

> Tel: 86-10-82453455

> Email: wxp@cn.ibm.com

> Address: 28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road, Haidian

> District Beijing P.R.China 100193 !DSPAM:4e6497a4108619485919262!



Emergency mode systemd target is equivalent to runlevel 1 singleuser

mode at SysV init system, thus probably network isn't active and sshd

refuses to run.



I'm not sure, but tmpfs (shm fs) need active swap, which probably isn't

on diskless station.



Another question is, when SELinux is appropriate to run on diskless

station (you may try disable it).



I also saw problem, when dracut was not able start diskless PXE F14

station when LAN default router was down (but it isn't this case).



Or there is just reciprocal proportion principle: when systemd consumes

10x more RAM then SysV init, then he can 10x fewer.

(narrowly, i686 F15 system comsumes 9x more RAM compared to i686 F7

SysVinit on my systems)





Franta Hanzlik

--

users mailing list

users@lists.fedoraproject.org

To unsubscribe or change subscription options:

https://admin.fedoraproject.org/mailman/listinfo/users

Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines



--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 09-13-2011, 10:45 AM
Xiao Peng Wang
 
Default F15, diskless node, systemctl start tmpfs.device timeout

Robert,



I don't know what I should do to test the var-run-tmpfs. At least I can touch file in the /var/tmp/.



The service 'NetworkManager-wait-online.service' was not installed on the diskless node. But I found a way to boot the sshd, so I think it was not a network issue.



Thanks

Best Regards

----------------------------------------------------------------------

Wang Xiaopeng (王晓朋)

IBM China System Technology Laboratory

Tel: 86-10-82453455

Email: wxp@cn.ibm.com

Address: 28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193





2011/9/5 Xiao Peng Wang <wxp@xxxxxxxxxx>:

>*Hi,

>

>*I made a diskless image against Fedora15, during the boot I found it

>*displayed the following error message and went into emergency mode.

>



Not 100% sure but take a look at this



http://fedoraproject.org/wiki/Features/var-run-tmpfs



and also try



systemctl enable NetworkManager-wait-online.service





PS please send posts to the mailing list in plain text





--

Robert Arkiletian

Eric Hamber Secondary, Vancouver, Canada

--

users mailing list

users@xxxxxxxxxxxxxxxxxxxxxxx

To unsubscribe or change subscription options:

https://admin.fedoraproject.org/mailman/listinfo/users

Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines



--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 

Thread Tools




All times are GMT. The time now is 01:17 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org