F15 long boot time
 

On a new F15 install replacing F14. The boot process pauses at
"Start LSB: The cups scheduler" for 60 seconds before going on
to the text log-in. I don't know what the cups scheduler is or
what to do with it.

Does anyone know what I need to do to fix this?

Bob
.

--


--
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

F15 long boot time
 

On 05/26/2011 06:05 PM, Bob Goodwin wrote:
> On a new F15 install replacing F14. The boot process pauses at
> "Start LSB: The cups scheduler" for 60 seconds before going on
> to the text log-in. I don't know what the cups scheduler is or
> what to do with it.
>
> Does anyone know what I need to do to fix this?

My boot process often pauses at that point, but it isn't because of cups
(even if that is the last message). It's because of the next message.

Check your boot logs carefully to see what comes after the cups message.

In my case, it is waiting for a NFSv4 mount to come alive. I am not sure
why that takes so long.


- Mike
--
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

F15 long boot time
 

2011/5/27 Dr. Michael J. Chudobiak <mjc@avtechpulse.com>

On 05/26/2011 06:05 PM, Bob Goodwin wrote:

> * * * * *On a new F15 install replacing F14. The boot process pauses at

> * * * * *"Start LSB: The cups scheduler" for 60 seconds before going on

> * * * * *to the text log-in. I don't know what the cups scheduler is or

> * * * * *what to do with it.

>

> * * * * *Does anyone know what I need to do to fix this?



My boot process often pauses at that point, but it isn't because of cups

(even if that is the last message). It's because of the next message.



Check your boot logs carefully to see what comes after the cups message.



In my case, it is waiting for a NFSv4 mount to come alive. I am not sure

why that takes so long.

noauto,comment=systemd.automount in /etc/fstab should help
see*http://www.happyassassin.net/2011/05/12/cute-systemd-trick-of-the-day-auto-mounting-remote-shares/


--
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

F15 long boot time
 

On 05/27/2011 08:27 AM, Jan Willies wrote:

> In my case, it is waiting for a NFSv4 mount to come alive. I am not sure
> why that takes so long.
>
>
> noauto,comment=systemd.automount in /etc/fstab should help

Maybe, but I don't understand why it takes ~30 seconds to establish a
NFSv4 mount. What's the root problem here?

- Mike
--
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

F15 long boot time
 

On Fri, 27 May 2011 08:52:50 -0400
Dr. Michael J. Chudobiak wrote:

> Maybe, but I don't understand why it takes ~30 seconds to establish a
> NFSv4 mount. What's the root problem here?

Well, the root problem is NFS :-).

I don't understand any of what is going on with systemd and network
mounts. I don't timeout, my network mounts simply fail right away:

https://bugzilla.redhat.com/show_bug.cgi?id=692008

(I think that's the bug I'm seeing).

Anyway, I just wrote a couple of shell scripts. One finds all
the NFS mountpoints not marked noauto in the /etc/fstab,
then it invokes the other script in the background, passing
it the name of the mountpoint.

The other script loops calling mount every few seconds as long
as the mounts keeps failing, then when the filesystem is finally
mounted it exits.

I start the first script from rc.local, and now I have reliable
network mounts that don't delay the boot (I've always wanted
an option that would background the mount right away without
timing out once first, now I kind of have one).

Systemd isn't the only system that fails to mount network files.
I have the same problems with upstart on ubuntu virtual machines
as well and have to fix it much the same way.
--
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

F15 long boot time
 

On 27/05/11 08:52, Dr. Michael J. Chudobiak wrote:
> On 05/27/2011 08:27 AM, Jan Willies wrote:
>
>> In my case, it is waiting for a NFSv4 mount to come alive. I am not sure
>> why that takes so long.
>>
>>
>> noauto,comment=systemd.automount in /etc/fstab should help
> Maybe, but I don't understand why it takes ~30 seconds to establish a
> NFSv4 mount. What's the root problem here?
>
> - Mike

The more I mess with this the more confused I become. Everything I
do has changed where the delays occur but the end result is still slow.

Also the nfs system was set up nfs3 I believe, wonder if I need to
change something there. Hate to change anything when it works
perfectly as it is [NFS].

Anyway, presently my fstab is as follows:

[bobg@box6 ~]$ cat /etc/fstab

#
# /etc/fstab
# Created by anaconda on Wed May 25 13:21:58 2011
#
# Accessible filesystems, by reference, are maintained under
'/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8)
for more info
#
/dev/mapper/vg_box6-lv_root / ext4
defaults 1 1
UUID=60fbd9d5-f192-46bf-a0de-59ebaf40b1a7
/boot ext4 defaults 1 2
/dev/mapper/vg_box6-lv_home /home ext4
defaults 1 2
/dev/mapper/vg_box6-lv_swap swap swap
defaults 0 0
tmpfs /dev/shm tmpfs
defaults 0 0
devpts /dev/pts devpts
gid=5,mode=620 0 0
sysfs /sys sysfs
defaults 0 0
proc /proc proc
defaults 0 0

192.168.1.48:/mnt/rfg/ /mnt/srvr1 nfs
noauto,comment=systemd.automount,rw,user 0 0

# 192.168.1.48:/mnt/glg/ /mnt/srvr2 nfs
defaults,rw,user 0 0

# 192.168.1.48:/mnt/mnl/ /mnt/srvr2 nfs
defaults,rw,user 0 0

# 192.168.1.48:/media/SimpleDrive/data/ /mnt/srvr3 nfs
defaults,rw,user 0 0


All I added where the lines for NFS and they have been the same
through several versions of Fedora.

If you see any glaring error let me know, otherwise I will live with
it, Normally I only boot once a day and I'm drinking coffee then ...

Thanks.

Bob

--
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

F15 long boot time
 

On Fri, 2011-05-27 at 11:10 -0400, Bob Goodwin wrote:

>
> All I added where the lines for NFS and they have been the same
> through several versions of Fedora.
>
> If you see any glaring error let me know, otherwise I will live with
> it, Normally I only boot once a day and I'm drinking coffee then ...

Try doing the below command (while already booted up, then reboot after
it's run) and see if this helps any.

systemctl enable NetworkManager-wait-online.service


--
Mike Chambers
Madisonville, KY

"The best town on Earth!"

--
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

F15 long boot time
 

Bob Goodwin <bobgoodwin <at> wildblue.net> writes:

> ...
> # 192.168.1.48:/mnt/glg/ /mnt/srvr2 nfs
^^^^^^^^^^
> ...

> # 192.168.1.48:/mnt/mnl/ /mnt/srvr2 nfs
^^^^^^^^^^
> ....

> ...

Is that what you want ?

JB






--
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

F15 long boot time
 

On 27/05/11 11:24, Mike Chambers wrote:
> On Fri, 2011-05-27 at 11:10 -0400, Bob Goodwin wrote:
>
>>
>> All I added where the lines for NFS and they have been the same
>> through several versions of Fedora.
>>
>> If you see any glaring error let me know, otherwise I will live with
>> it, Normally I only boot once a day and I'm drinking coffee then ...
> Try doing the below command (while already booted up, then reboot after
> it's run) and see if this helps any.
>
> systemctl enable NetworkManager-wait-online.service
>
>


This is a fixed, desktop computer, I hope I've turned off
Network Manager.

Bob


--
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

F15 long boot time
 

On Fri, 2011-05-27 at 09:45 -0400, Tom Horsley wrote:
> On Fri, 27 May 2011 08:52:50 -0400
> Dr. Michael J. Chudobiak wrote:
>
> > Maybe, but I don't understand why it takes ~30 seconds to establish a
> > NFSv4 mount. What's the root problem here?
>
> Well, the root problem is NFS :-).
>
> I don't understand any of what is going on with systemd and network
> mounts. I don't timeout, my network mounts simply fail right away:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=692008
>
> (I think that's the bug I'm seeing).
>
> Anyway, I just wrote a couple of shell scripts. One finds all
> the NFS mountpoints not marked noauto in the /etc/fstab,
> then it invokes the other script in the background, passing
> it the name of the mountpoint.
I had similrar issues, that I never managed to copletely understand. I
now use systemd's automount functionality: I Added
comment=systemd.automount to the options for the NFS mounts and now I
see the first mount fails, but systemd gets back to these mount points
later and then correctly mounts them. Might be worth a try....

--
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