<---- template headericclude ----->
Selected Important Daemons not able to start
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 15 of 15
  1. #1
    Join Date
    Aug 2008
    Location
    Indiana
    Age
    44
    Posts
    11
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Selected Important Daemons not able to start

    Haldaemon, pscd not starting... cannot force to start. Do not start when running service pscd start. Just failed. Boot message is below:


    Remounting root filesystem in read-write mode: [ OK ]
    Mounting local filesystems: [ OK ]
    Enabling /etc/fstab swaps: [ OK ]
    init: ck-log-system-start main process (1207) terminated with status 1
    Entering non-interactive startup
    Starting monitoring for VG vg_Garden: 3 logical volume(s) in volume group "vg_Garden" monitored
    [ OK ]
    Running DKMS auto installation service for kernel 2.6.35.10-74.fc14.x86_64
    Checking kmods exist for 2.6.35.10-74.fc14.x86_64 [ OK ]
    ip6tables: Applying firewall rules: [ OK ]
    ip6tables: Loading additional modules: nf_conntrack_netbios_ns [ OK ]
    iptables: Applying firewall rules: [ OK ]
    iptables: Loading additional modules: nf_conntrack_netbios_ns [ OK ]
    Bringing up loopback interface: [ OK ]
    Bringing up interface Auto_eth0: Device Auto_eth0 does not seem to be present, delaying initialization.
    [FAILED]
    Starting portreserve: [ OK ]
    Starting restorecond: [ OK ]
    Enabling ondemand cpu frequency scaling: [ OK ]
    Starting irqbalance: [ OK ]
    Starting rpcbind: [ OK ]
    Starting system message bus: [ OK ]
    Setting network parameters... [ OK ]
    Starting NetworkManager daemon: [ OK ]
    Starting Avahi daemon... modem-manager: ModemManager (version 0.4-4.git20100720.fc14) starting...
    modem-manager: Loaded plugin Option High-Speed
    modem-manager: Loaded plugin MotoC
    modem-manager: Loaded plugin Longcheer
    modem-manager: Loaded plugin Novatel
    modem-manager: Loaded plugin Option
    modem-manager: Loaded plugin Nokia
    modem-manager: Loaded plugin Huawei
    modem-manager: Loaded plugin Gobi
    modem-manager: Loaded plugin AnyData
    modem-manager: Loaded plugin Ericsson MBM
    modem-manager: Loaded plugin ZTE
    modem-manager: Loaded plugin Sierra
    modem-manager: Loaded plugin Generic
    modem-manager: Loaded plugin SimTech
    modem-manager: (tty/ttyS1): port's parent platform driver is not whitelisted
    modem-manager: (tty/ttyS2): port's parent platform driver is not whitelisted
    modem-manager: (tty/ttyS3): port's parent platform driver is not whitelisted
    modem-manager: (tty/ttyS0): could not get port's parent device
    [ OK ]
    Starting NFS statd: [ OK ]
    Starting RPC idmapd: [ OK ]
    Starting cups: [ OK ]
    Mounting other filesystems: [ OK ]
    Starting HAL daemon: [FAILED]
    Retrigger failed udev events [ OK ]
    nm-dispatcher.action: nm_dispatcher_action: Invalid connection: '(null)' / 'connection setting not found' invalid: 1
    Starting PC/SC smart card daemon (pcscd): [FAILED]
    Starting Winbind services: [ OK ]
    Starting NFS services: [ OK ]
    Starting NFS daemon: [ OK ]
    Starting NFS mountd: [ OK ]
    Starting VirtualBox kernel modules [ OK ]
    Enabling Bluetooth devices:modem-manager: (net/vboxnet0): could not get port's parent device
    Posted by: Waller

  2. #2
    Join Date
    Feb 2009
    Posts
    2,743
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Selected Important Daemons not able to start

    Can you look into the log files in order to find out why haldaemon failed? I guess PC/SD wouldn't be a big problem except when you are using smart cards.

  3. #3
    Join Date
    Aug 2008
    Location
    Indiana
    Age
    44
    Posts
    11
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Selected Important Daemons not able to start

    Where in the log files are you referring? I have looked through there, but don't really know my way around. I do use smart cards quite a bit, so it not working is a large problem.

    ---------- Post added at 08:04 AM ---------- Previous post was at 08:03 AM ----------

    dmesg? sorry for the double reply
    Posted by: Waller

  4. #4
    Join Date
    Jan 2010
    Posts
    8,401
    Mentioned
    22 Post(s)
    Tagged
    0 Thread(s)

    Re: Selected Important Daemons not able to start

    /var/log/messages

    As you guessed, dmesg can also sometimes be useful.

    /var/spool/plymouth/boot.log might have something too.

    Use more /var/spool/plymouth/boot.log---using less gives a lot of peculiar characters, not sure why--that is, the command is

    more /var/spool/plymouth/boot.log

  5. #5
    Join Date
    Aug 2008
    Location
    Indiana
    Age
    44
    Posts
    11
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Selected Important Daemons not able to start

    Log messages a stated in previous reply are attached in ASCII format. Thank you both for the help so far.
    Attached Files Attached Files
    Posted by: Waller

  6. #6
    Join Date
    Aug 2009
    Location
    College Station, TX
    Posts
    502
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Selected Important Daemons not able to start

    The problem with HAL definitely needs to be resolved first.

    Given all the orphaned inodes in the bootlog I would start by verifying that the hal package hasn't been corrupted.

    rpm -V hal
    package-cleanup --problems # requires yum-utils package

    Then you might start hald manually (services start hald) and see if it started: e.g.

    Code:
    $ ps axfu | grep hald
    68        1300  0.0  0.1  15104  2464 ?        Ssl  Jan30   1:20 hald
    root      1301  0.0  0.0   4064  1124 ?        S    Jan30   0:00  \_ hald-runner
    root      1324  0.0  0.0   4136   812 ?        S    Jan30   0:21      \_ hald-addon-input: Listening on /dev/input/event7 /dev/input/event2 /dev/input/event1 /dev/input/event5 /dev/input/event3 /dev/input/event0 /dev/input/event4
    root      1326  0.0  0.0   4136   796 ?        S    Jan30   0:00      \_ /usr/libexec/hald-addon-rfkill-killswitch
    root      1334  0.0  0.0   4132   812 ?        S    Jan30   0:00      \_ /usr/libexec/hald-addon-generic-backlight
    68        1336  0.0  0.0   3704  1024 ?        S    Jan30   0:05      \_ /usr/libexec/hald-addon-acpi
    If it doesn't start (or immediately crashes), you can try something like:

    /usr/sbin/hald --daemon=no --verbose=yes # as root

    which might give some clues as to why it is failing to start.

    SS

  7. #7
    Join Date
    Aug 2008
    Location
    Indiana
    Age
    44
    Posts
    11
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Selected Important Daemons not able to start

    I ran what you suggested, the package cleanup didn't detect problems, but checking hald did:


    16:31:05.829 [I] hald.c:673: hal 0.5.14
    16:31:05.829 [I] hald.c:674: using child timeout 250s
    16:31:05.830 [I] hald.c:739: Will not daemonize
    16:31:05.830 [I] hald_dbus.c:5444: local server is listening at unix:abstract=/var/run/hald/dbus-XS2pq4h8Oo,guid=302443e87ffcba5afbefdcf300000536
    16:31:05.842 [I] hald_runner.c:304: Runner has pid 4235
    Runner started - allowed paths are '/usr/libexec:/usr/libexec/scripts:/usr/bin'
    16:31:05.845 [I] hald_runner.c:184: runner connection is 0xc90bc0
    16:31:05.852 [I] mmap_cache.c:126: Regenerating fdi cache..
    Run started hald-generate-fdi-cache (60000) (0)
    ! full path is '/usr/libexec/hald-generate-fdi-cache', program_dir is '/usr/libexec'
    16:31:05.856 [E] create_cache.c:639: Unable to open fdi cache '/var/cache/hald/fdi-cache~' file for writing: No such file or directory
    16:31:05.856 [E] create_cache.c:709: Error generating fdi cache
    pid 4237: rc=1 signaled=0: /usr/libexec/hald-generate-fdi-cache
    16:31:05.857 [I] mmap_cache.c:104: In regen_cache_cb exit_type=0, return_code=1
    16:31:05.857 [E] mmap_cache.c:153: fdi cache regeneration failed!
    16:31:05.857 [I] mmap_cache.c:156: fdi cache generation done
    16:31:05.857 [I] mmap_cache.c:278: cache mtime is 1296142954
    *** [DIE] mmap_cache.c:di_rules_init():70 : Unable to open cache /var/cache/hald/fdi-cache


    I think I know the problem... a few days ago, I cleared my logs in /var... then I cleared cache... this looks like the problem.... any automated way to solve or will creating the directories and empty files work... I thought cache was only running cache... so this may be a good lesson for me. Ideas?

    ---------- Post added at 04:47 PM ---------- Previous post was at 04:34 PM ----------

    So I created a directory in /var/cache named hald... it then created the fdi-cache, again running in non-daemon mode (/usr/sbin/hald --daemon=no --verbose=yes) I get quite a bit of information here... once I figure out the code box item, I will post it.
    Posted by: Waller

  8. #8
    Join Date
    Aug 2009
    Location
    College Station, TX
    Posts
    502
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Selected Important Daemons not able to start

    A quick test (deleting just the file and then the entire directory) indicates that if you just create the directory, it will recreate the file (at least it did here... exactly the same as before the file was deleted).
    Try this:

    mkdir /var/cache/hald
    chown haldaemon:haldaemon /var/cache/hald
    reboot

    Though I'm not sure why that would be the case here since your 'rpm -V' was clean, whereas I get:

    # rpm -V hal
    missing /var/cache/hald

    if I entirely delete the directory. (???)

    SS

  9. #9
    Join Date
    Aug 2008
    Location
    Indiana
    Age
    44
    Posts
    11
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Selected Important Daemons not able to start

    [code]
    So that was easy
    [\code]

    If you want to see the output, I can send you a 5MB ASCII file.

    trying to own it by hal and reboot now...
    Posted by: Waller

  10. #10
    Join Date
    Aug 2009
    Location
    College Station, TX
    Posts
    502
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Selected Important Daemons not able to start

    Quote Originally Posted by Waller
    If you want to see the output, I can send you a 5MB ASCII file.
    I'll pass. (I got similar when it recreated it here in verbose mode... don't think we need to see it so long as hald starts)

    Just let us know if it works (and mark the thread as SOLVED if it does).

    SS

  11. #11
    Join Date
    Aug 2008
    Location
    Indiana
    Age
    44
    Posts
    11
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Selected Important Daemons not able to start

    So rpm -V hal does give some feedback:

    Code:
    prelink: /usr/libexec/hal-storage-cleanup-all-mountpoints: at least one of file's dependencies has changed since prelinking
    S.?......    /usr/libexec/hal-storage-cleanup-all-mountpoints
    prelink: /usr/libexec/hal-storage-cleanup-mountpoint: at least one of file's dependencies has changed since prelinking
    S.?......    /usr/libexec/hal-storage-cleanup-mountpoint
    prelink: /usr/libexec/hal-storage-closetray: at least one of file's dependencies has changed since prelinking
    S.?......    /usr/libexec/hal-storage-closetray
    prelink: /usr/libexec/hal-storage-eject: at least one of file's dependencies has changed since prelinking
    S.?......    /usr/libexec/hal-storage-eject
    prelink: /usr/libexec/hal-storage-mount: at least one of file's dependencies has changed since prelinking
    S.?......    /usr/libexec/hal-storage-mount
    prelink: /usr/libexec/hal-storage-unmount: at least one of file's dependencies has changed since prelinking
    S.?......    /usr/libexec/hal-storage-unmount
    prelink: /usr/libexec/hald-probe-storage: at least one of file's dependencies has changed since prelinking
    S.?......    /usr/libexec/hald-probe-storage
    prelink: /usr/libexec/hald-probe-volume: at least one of file's dependencies has changed since prelinking
    S.?......    /usr/libexec/hald-probe-volume
    .M.......    /var/cache/hald

    But the package-cleanup found no issues. Tried what you suggested about owning the directory with hald, still no luck. But I think the above may have been what we needed in the first place. How do I do about correct prelinking?
    Last edited by Waller; 2nd February 2011 at 11:22 PM. Reason: Grammar
    Posted by: Waller

  12. #12
    Join Date
    Aug 2009
    Location
    College Station, TX
    Posts
    502
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Selected Important Daemons not able to start

    The prelink warnings aren't a problem, but if you want to clean them up just run /usr/sbin/prelink on the individual files listed (which takes work) or run /etc/cron.daily/prelink to prelink the whole system (takes much longer).

    The 'M' on /var/cache/hald just indicates that the timestamp is different than the .rpm so it isn't a problem either. But to make it go away do:

    Code:
    touch -d "1970-01-01 `rpm -q --dump hal | grep /var/cache/hald | cut -f 3 -d ' '` sec utc" /var/cache/hald/
    (quick, complicated, way) or "yum -y reinstall hal" (longer, easy, way).

    But I don't think either of those should have caused problems. Did hal/pcscd not start on the reboot?

    SS

  13. #13
    Join Date
    Aug 2008
    Location
    Indiana
    Age
    44
    Posts
    11
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Selected Important Daemons not able to start

    I will do as you suggest, but hal and pcscd still don't start. Like I said, I did do a complete cache clean, but thought that was ok to do once in a while...
    Posted by: Waller

  14. #14
    Join Date
    Aug 2008
    Location
    Indiana
    Age
    44
    Posts
    11
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Selected Important Daemons not able to start

    Quote Originally Posted by SiliconSlick
    yum -y reinstall hal (longer, easy, way).
    I tried as suggested and my baby is still giving me no love.

    Noticed this on boot:

    Code:
    Remounting root filesystem in read-write mode:  	[  OK  ]
    Mounting local filesystems:  	[  OK  ]
    Enabling /etc/fstab swaps:  	[  OK  ]
    init: ck-log-system-start main process (1235) terminated with status 1
    Entering non-interactive startup
    Does give you any ideas? I am stuck at this point... but I would really hate to reinstall.

    The ck-log-system-start is from ConsoleKit. I just had to create /var/log/ConsoleKit and it ran from the terminal. Will reboot and update the post.

    ---------- Post added at 08:02 PM ---------- Previous post was at 06:30 PM ----------

    Ok, after rebooting and running yum update for heck of it, I get this new message about hal at boot time

    Code:
    Starting HAL daemon: nm-dispatcher.action: nm_dispatcher_action: Invalid connection: '(null)' / 'connection setting not found' invalid: 1
    	[FAILED]
    Retrigger failed udev events	[  OK  ]
    Can anyone direct me how to start trouble shooting this or correct it?
    Last edited by Waller; 4th February 2011 at 02:02 AM. Reason: Adding more to post
    Posted by: Waller

  15. #15
    Join Date
    Nov 2010
    Location
    Colombia
    Posts
    4
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Selected Important Daemons not able to start

    Did you solve this problem? How? I made the same mistake.

    Nevermind. Using yum -y reinstall hald did work. Thanks.
    Last edited by fabalexbar; 16th May 2011 at 03:27 AM. Reason: Problem solved

Similar Threads

  1. Help on Daemons
    By bhubanmm in forum Programming & Packaging
    Replies: 1
    Last Post: 28th April 2006, 07:15 PM
  2. Disabling daemons at start up
    By yukito in forum Using Fedora
    Replies: 6
    Last Post: 17th December 2005, 02:20 AM
  3. NFS and Daemons
    By tgrier in forum Servers & Networking
    Replies: 4
    Last Post: 11th December 2005, 06:08 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
[[template footer(Guest)]]