Page 1 of 2 12 LastLast
Results 1 to 10 of 48

Thread: 9.10 Upstart Breaks Cron,Cups,SSH, etc...

Hybrid View

  1. #1
    Join Date
    Dec 2006
    Beans
    78

    Exclamation Karmic 9.10 w/ Upstart - Cron,Cups,SSH,Samba, etc... not started during boot

    Hi,

    Running 9.10 now, but having problems with many of my background services.

    * Cups service no longer starts at boot
    * SSHd service no longer starts at boot
    * Cron jobs are not being run
    * Samba file shares and/or printers not initialized correctly at startup.

    HELP! What is the deal with Upstart? How can I get it to run my system services again?

    Is there a master thread for using Upstart? Does rcconf, invoke-rc.d, and other utilities still work?

    ------
    Update ...

    I originally thought this was fixed, but now I see that my services (CUPS, cron) still do not startup on boot. Can anyone confirm this and provide a workaround?
    Last edited by cmcginty; December 11th, 2009 at 05:03 AM.

  2. #2
    Join Date
    Dec 2006
    Beans
    1,133
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: 9.10 Upstart Breaks Cron,Cups,SSH, etc...

    I would like to see some good documentation for upstart too. However, one of the goals of upstart is that services like cups and sshd do not need to start at boot but only when actually needed. So if you were going to print something, cups would start at that time. How they get it to work for printing over a lan I don't know.

    I haven't looked at KKs init system but I believe it still has the sysv compatibility layer to run the older style /etc/init.d scripts. Take a look in in some of the /usr/share/doc directories, you may find some info there.
    There are no dumb questions, just dumb answers.

  3. #3
    Join Date
    Dec 2006
    Beans
    78

    Re: 9.10 Upstart Breaks Cron,Cups,SSH, etc...

    I think cron is working alright now. I had to re-install my local crontab file with:

    Code:
    crontab -e
    and then making a change and saving it. Still no luck on the other services. If I run:

    Code:
    sudo invoke-rc.d service restart
    then the service will start correctly. I'd rather have this run automatically.

  4. #4
    Join Date
    Dec 2006
    Beans
    78

    Re: 9.10 Upstart Breaks Cron,Cups,SSH, etc...

    Should I be worried about this output?

    Code:
    sudo dpkg-reconfigure cups
     * Stopping Common Unix Printing System: cupsd                                                                   [ OK ] 
    insserv: warning: script 'S07powernowd.early' missing LSB tags and overrides
    insserv: warning: script 'atd' missing LSB tags and overrides
    insserv: warning: script 'gdm' missing LSB tags and overrides
    insserv: warning: script 'hal' missing LSB tags and overrides
    insserv: warning: script 'ufw' missing LSB tags and overrides
    insserv: warning: script 'dbus' missing LSB tags and overrides
    insserv: warning: script 'cron' missing LSB tags and overrides
    insserv: warning: current start runlevel(s) (0) of script `halt' overwrites defaults (empty).
    insserv: warning: script 'gssd' missing LSB tags and overrides
    insserv: warning: script 'udev' missing LSB tags and overrides
    insserv: warning: script 'cryptdisks-enable' missing LSB tags and overrides
    insserv: warning: current start runlevel(s) (0 6) of script `umountfs' overwrites defaults (empty).
    insserv: warning: script 'sreadahead' missing LSB tags and overrides
    insserv: warning: script 'acpid' missing LSB tags and overrides
    insserv: warning: script 'dmesg' missing LSB tags and overrides
    insserv: warning: script 'statd' missing LSB tags and overrides
    insserv: warning: script 'rsyslog-kmsg' missing LSB tags and overrides
    insserv: warning: script 'network-manager' missing LSB tags and overrides
    insserv: warning: script 'udevmonitor' missing LSB tags and overrides
    insserv: warning: script 'rsyslog' missing LSB tags and overrides
    insserv: warning: script 'avahi-daemon' missing LSB tags and overrides
    insserv: warning: script 'module-init-tools' missing LSB tags and overrides
    insserv: warning: script 'udevtrigger' missing LSB tags and overrides
    insserv: warning: script 'rpc_pipefs' missing LSB tags and overrides
    insserv: warning: script 'apport' missing LSB tags and overrides
    insserv: warning: current stop runlevel(s) (1) of script `policykit' overwrites defaults (empty).
    insserv: warning: current start runlevel(s) (0 6) of script `wpa-ifupdown' overwrites defaults (empty).
    insserv: warning: script 'idmapd' missing LSB tags and overrides
    insserv: warning: script 'procps' missing LSB tags and overrides
    insserv: warning: current start runlevel(s) (6) of script `reboot' overwrites defaults (empty).
    insserv: warning: current start runlevel(s) (0 6) of script `sendsigs' overwrites defaults (empty).
    insserv: warning: current start runlevel(s) (0 6) of script `umountroot' overwrites defaults (empty).
    insserv: warning: script 'usplash' missing LSB tags and overrides
    insserv: warning: script 'anacron' missing LSB tags and overrides
    insserv: warning: current start runlevel(s) (0 6) of script `networking' overwrites defaults (empty).
    insserv: warning: script 'udev-finish' missing LSB tags and overrides
    insserv: warning: script 'hwclock' missing LSB tags and overrides
    insserv: warning: script 'portmap' missing LSB tags and overrides
    insserv: warning: current start runlevel(s) (0 6) of script `umountnfs.sh' overwrites defaults (empty).
    insserv: warning: script 'powernowd.early' missing LSB tags and overrides
    insserv: There is a loop between service rsyslog and hwclock if stopped
    insserv:  loop involving service hwclock at depth 4
    insserv:  loop involving service sysklogd at depth 3
    insserv: There is a loop between service rsyslog and sysklogd if started
    insserv:  loop involving service sysklogd at depth 3
    insserv:  loop involving service hwclock at depth 2
    insserv:  loop involving service rsyslog at depth 4
    insserv: There is a loop between service hwclock and sysklogd if stopped
    insserv:  loop involving service rsyslog at depth 5
    insserv: exiting without changing boot order!
     * Starting Common Unix Printing System: cupsd                                                                   [ OK ]

  5. #5
    Join Date
    Dec 2006
    Beans
    78

    Re: 9.10 Upstart Breaks Cron,Cups,SSH, etc...

    I figured out the reason for these issue. After the upgrade, the system left the old package configuration files in the /etc/init.d directory. They need to be cleaned out:

    Code:
    aptitude -F %p search "~c" | xargs sudo dpkg -P
    After that I reinstalled the packages complaining about loop errors:

    Code:
    sudo apt-get install --reinstall kerneloops kerneloops-daemon rsyslog udev
    Then cups can be reinstalled now without errors:

    Code:
    sudo apt-get install --reinstall cups
    Last edited by cmcginty; October 30th, 2009 at 03:15 AM.

  6. #6
    Join Date
    May 2008
    Beans
    31

    Re: 9.10 Upstart Breaks Cron,Cups,SSH, etc...

    What about SSH? My sshd doesn't start on boot, either, after upgrade to 9.10 Karmic.

  7. #7
    Join Date
    Dec 2006
    Beans
    78

    Re: 9.10 Upstart Breaks Cron,Cups,SSH, etc...

    For the last step do:

    Code:
    sudo apt-get install --reinstall openssh-server

  8. #8
    Join Date
    Aug 2007
    Beans
    38

    Re: 9.10 Upstart Breaks Cron,Cups,SSH, etc...

    Upstart makes boot quicker than it was with sysv.

    http://packages.ubuntu.com/karmic/upstart 0.6.3-10
    http://packages.ubuntu.com/karmic-updates/upstart 0.6.3-11
    http://packages.ubuntu.com/lucid/upstart 0.6.3-11build1

    We can see that karmic is currently using upstart 0.6.3-10 which only has the worry of making sure /etc/network/interfaces has auto lo.

    With karmic-updates in /etc/apt/sources.list, then the worry is that upgrading will move karmic users to upstart 0.6.3-11 and to a newer libc6 which(newer libc6) makes it very, very difficult to downgrade upstart because other newer packages depend then on newer lib6. Better karmic users pin their upstart to 0.6.3-10 for a while to keep from falling into the pit when /etc/apt/sources.list contains karmic-updates(synaptic shows checkmark for karmic-updates in repositories).

    Sometimes upstart 0.6.3-11 works; sometimes not. I have a lucid 10.04 desktop live iso from January 12, 2010 (20100112.1) that has 0.6.3-11 and loads dbus, ssh, ifupdown eth0 OK, pulseaudio and gdm work because dbus is there. One could say that upstart 0.6.3-11 is not the problem! Somebody just has to do the scripting to come over to upstart from sysv. I may be able to tarball the /etc/init/ scripting that works there, and copy that over to my crippled no-service installations.

    Some recent gdm scripting has gdm wait for dbus to load. That means our X will never start under gdm and the upstart no-services problem because dbus will never load.

    http://www.mail-archive.com/lucid-ch.../msg04041.html
    January 26, 2010 "convert openssh to upstart"...thus we don't have an upstart problem but only problems with services if they have not been revised to work with upstart!

  9. #9
    Join Date
    Aug 2007
    Beans
    38

    Re: 9.10 Upstart Breaks Cron,Cups,SSH, etc...

    I installed lucid on five hard drives.

    All installs came with /etc/network/interfaces auto lo:

    auto lo
    iface lo inet loopback

    That is NOT a fix because upstart causes so many other problems. I think it's a fine concept but who released upstart 0.6.3-10 as the standard init method when it disables services like ssh and dbus, consequently no audio, maybe no X login? Would someone please make their bank accounts public ?

    upstart 0.6.3.11 or newer does not run ifup -a. upstart never runs services such as dbus or gdm or kdm. No audio! This is killing ubuntu. Normally a bug of this strategic magnitude would be fixed in minutes, not hours, not days or weeks. upstart messes up boot logging so you can't see what's going on(research bootlogd and grub options quiet=1 and kernel opt quiet with NO splash). X is may not load or you may get a hung X load, frozen mouse, sluggish X. You may boot to a console login or just to hung X with frozen mouse.

    I tried pinning upstart to what karmic is using:

    #/etc/apt/preferences
    Package: upstart
    Pin: version 0.6.3-10
    Pin-Priority: 900

    Unfortunately a newer version of libc6 was already in place. apt-get or dpkg wanted to delete a hundred packages that depend on ANY libc6 in order to downgrade upstart and libc6. At least I was asked if I really wanted to do that, and of course I did not. If you are coming from karmic, you have upstart 0.6.3.10 so you have the opportunity to pin that before your upgrade. As long as you stay in karmic, you are frozen at upstart 0.6.3-10 until this too may pass.

    It's possible that some install iso has a way. I did see dbus and audio working with upstart 0.6.3-11, but then ext4 got hosed some way before I could figure out the diff. I don't know if that lucid good upstart install was desktop or alt iso beta2 daily. I'd like to think somebody is making progress. It's only scripting, not hard if those familiar with upstart and udev and inittab/sysvinit would just try. I can't afford food, only coffee and gasoline, so don't lecture me about putting MORE time in on this.

  10. #10
    Join Date
    Jun 2005
    Location
    Hamburg, Germany
    Beans
    360
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: 9.10 Upstart Breaks Cron,Cups,SSH, etc...

    Hi all,

    I stumbled across this thread when my cups service spontaneous didn't start anymore, but could easily started by hand. None of the tricks posted here help. Other problems appeared as well like cpu scaling not taking the default settings.

    When I fiddled with the kernel and boot processes I started to use concurrency to speed up the boot process by running scripts in parallel on the 2 cores of my CPU. That seemed to have screwed it up. After I removed that setting, everything is working again as expected with the last available version on upstart.

    Check the scripts

    Code:
    /etc/init.d/rc
    /etc/default/rcS
    for a line saying

    Code:
    CONCURRENCY=shell
    If you find one, you might want to try and replace it with

    Code:
    CONCURRENCY=none
    and reboot.

    Cheers,

    Riko

Page 1 of 2 12 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •