Quantcast

haldaemon problem

classic Classic list List threaded Threaded
39 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

haldaemon problem

d_j_w46
I'm trying to restart the daemon and get this

[david@reddwarf ~]$ sudo /sbin/service haldaemon restart
Stopping HAL daemon:                                       [FAILED]
Starting HAL daemon:                                       [FAILED]

Is it because I might not have haldaemon in my system.

[david@reddwarf ~]$ sudo rpm -qa | grep haldaemon

This brings up nothing.


Thanks   david

--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: haldaemon problem

tian-5

在 2007-12-07五的 09:47 +1000,david walcroft写道:
> I'm trying to restart the daemon and get this
>
> [david@reddwarf ~]$ sudo /sbin/service haldaemon restart
> Stopping HAL daemon:                                       [FAILED]
> Starting HAL daemon:                                       [FAILED]
>
> Is it because I might not have haldaemon in my system.
Do you have file /etc/init.d/haldaemon ?
>
> [david@reddwarf ~]$ sudo rpm -qa | grep haldaemon
>
> This brings up nothing.
>
>
> Thanks   david
>

--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: haldaemon problem

Todd Zullinger
In reply to this post by d_j_w46
david walcroft wrote:
> I'm trying to restart the daemon and get this
>
> [david@reddwarf ~]$ sudo /sbin/service haldaemon restart
> Stopping HAL daemon:                                       [FAILED]
> Starting HAL daemon:                                       [FAILED]

Look in /var/log/messages for some some clues.

> Is it because I might not have haldaemon in my system.
>
> [david@reddwarf ~]$ sudo rpm -qa | grep haldaemon

No.  The package name isn't haldaemon, it's just hal.  If you didn't
have it installed, you wouldn't have the init script that the service
command runs. :)

You could check with rpm -V that the hal packages aren't messed up (if
there's nothing obvious in the logs):

rpm -V hal hal-libs

--
Todd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
History teaches us that men and nations behave wisely once they have
exhausted all other alternatives.
    -- Abba Eban


--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

attachment0 (554 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: haldaemon problem

Todd Zullinger
In reply to this post by tian-5
tian wrote:
>> [david@reddwarf ~]$ sudo /sbin/service haldaemon restart
>> Stopping HAL daemon:                                       [FAILED]
>> Starting HAL daemon:                                       [FAILED]
>>
>> Is it because I might not have haldaemon in my system.
> Do you have file /etc/init.d/haldaemon ?

If /etc/init.d/haldaemon wasn't present, then the service script would
return:

haldaemon: unrecognized service

--
Todd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If people are good only because they fear punishment, and hope for
reward, then we are a sorry lot indeed.
    -- Albert Einstein


--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

attachment0 (554 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: haldaemon problem

Tod Merley
In reply to this post by d_j_w46
On Dec 6, 2007 3:47 PM, david walcroft <[hidden email]> wrote:

> I'm trying to restart the daemon and get this
>
> [david@reddwarf ~]$ sudo /sbin/service haldaemon restart
> Stopping HAL daemon:                                       [FAILED]
> Starting HAL daemon:                                       [FAILED]
>
> Is it because I might not have haldaemon in my system.
>
> [david@reddwarf ~]$ sudo rpm -qa | grep haldaemon
>
> This brings up nothing.
>
>
> Thanks   david
>
> --
> fedora-list mailing list
> [hidden email]
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>

Hi david walcroft!

To administrate, be root - become so "su".

>From "man hald":

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

BUGS AND DEBUGGING
       Please  send  bug reports to either the distribution or the HAL mailing
       list, see http://lists.freedesktop.org/mailman/listinfo/hal on  how  to
       subscribe.

       First,  to  obtain  useful debug traces you will need to have debuginfo
       packages installed. On a Fedora system this  is  in  the  hal-debuginfo
       package and can be installed via the yum update program.

       Second, shut down the existing hald daemon instance; on a Fedora system
       this is achieved by

       /etc/init.d/haldaemon stop

       After having shut down the daemon, you might want to run

       pkill hald

       to ensure that all the helper processe of hald are killed too. To start
       the HAL daemon, use

       /usr/sbin/hald --daemon=no --verbose=yes

       gdb /usr/sbin/hald

       and then typing

       run --daemon=no --verbose=yes

       at  the  (gdb)  prompt. To capture a back trace, use the bt command and
       attach this to the bug report.

       Please also attach the output of lshal(1) in the bug report if possible
       (it's  not  possible  if the hald daemon crashed). If the nature of the
       bug has to do with hotplugging, attach two outputs of  lshal(1)  -  one
       before the device hotplug event and one after.

SEE ALSO
       udev(7),  dbus-daemon(1),  lshal(1), hal-set-property(1), hal-get-prop-
       erty(1),  hal-find-by-property(1),  hal-find-by-capability(1),  hal-is-
       caller-locked-out(1)

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

Have fun!

Tod

--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: haldaemon problem

antonio montagnani-2
2007/12/7, Tod Merley <[hidden email]>:

> On Dec 6, 2007 3:47 PM, david walcroft <[hidden email]> wrote:
> > I'm trying to restart the daemon and get this
> >
> > [david@reddwarf ~]$ sudo /sbin/service haldaemon restart
> > Stopping HAL daemon:                                       [FAILED]
> > Starting HAL daemon:                                       [FAILED]
> >
> > Is it because I might not have haldaemon in my system.
> >
> > [david@reddwarf ~]$ sudo rpm -qa | grep haldaemon
> >
> > This brings up nothing.
> >
> >
> > Thanks   david
> >
> > --
> > fedora-list mailing list
> > [hidden email]
> > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> >
>
> Hi david walcroft!
>
> To administrate, be root - become so "su".
>
> >From "man hald":
>
> ------------------------------------------------
>
> BUGS AND DEBUGGING
>        Please  send  bug reports to either the distribution or the HAL mailing
>        list, see http://lists.freedesktop.org/mailman/listinfo/hal on  how  to
>        subscribe.
>
>        First,  to  obtain  useful debug traces you will need to have debuginfo
>        packages installed. On a Fedora system this  is  in  the  hal-debuginfo
>        package and can be installed via the yum update program.
>
>        Second, shut down the existing hald daemon instance; on a Fedora system
>        this is achieved by
>
>        /etc/init.d/haldaemon stop
>
>        After having shut down the daemon, you might want to run
>
>        pkill hald
>
>        to ensure that all the helper processe of hald are killed too. To start
>        the HAL daemon, use
>
>        /usr/sbin/hald --daemon=no --verbose=yes
>
>        gdb /usr/sbin/hald
>
>        and then typing
>
>        run --daemon=no --verbose=yes
>
>        at  the  (gdb)  prompt. To capture a back trace, use the bt command and
>        attach this to the bug report.
>
>        Please also attach the output of lshal(1) in the bug report if possible
>        (it's  not  possible  if the hald daemon crashed). If the nature of the
>        bug has to do with hotplugging, attach two outputs of  lshal(1)  -  one
>        before the device hotplug event and one after.
>
> SEE ALSO
>        udev(7),  dbus-daemon(1),  lshal(1), hal-set-property(1), hal-get-prop-
>        erty(1),  hal-find-by-property(1),  hal-find-by-capability(1),  hal-is-
>        caller-locked-out(1)
>
> -----------------------------------------------------------
>
> Have fun!
>
> Tod
>
> --
> fedora-list mailing list
> [hidden email]
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>
I have exactly the same problem if F9T, but I do not find the
hal-debug packege in repos....

--
Antonio Montagnani
Skype : antoniomontag

--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: haldaemon problem

Aaron Konstam
In reply to this post by Tod Merley
On Fri, 2007-12-07 at 01:57 -0800, Tod Merley wrote:

> On Dec 6, 2007 3:47 PM, david walcroft <[hidden email]> wrote:
> > I'm trying to restart the daemon and get this
> >
> > [david@reddwarf ~]$ sudo /sbin/service haldaemon restart
> > Stopping HAL daemon:                                       [FAILED]
> > Starting HAL daemon:                                       [FAILED]
> >
> > Is it because I might not have haldaemon in my system.
> >
> > [david@reddwarf ~]$ sudo rpm -qa | grep haldaemon
> >
> > This brings up nothing.
> >
> >
> > Thanks   david
> >
> > --
> > fedora-list mailing list
> > [hidden email]
> > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> >
>
> Hi david walcroft!
>
> To administrate, be root - become so "su".
su - would be better.
>


> >From "man hald":
>
> ------------------------------------------------
>
> BUGS AND DEBUGGING
>        Please  send  bug reports to either the distribution or the HAL mailing
>        list, see http://lists.freedesktop.org/mailman/listinfo/hal on  how  to
>        subscribe.
>
>        First,  to  obtain  useful debug traces you will need to have debuginfo
>        packages installed. On a Fedora system this  is  in  the  hal-debuginfo
>        package and can be installed via the yum update program.
>
>        Second, shut down the existing hald daemon instance; on a Fedora system
>        this is achieved by
>
>        /etc/init.d/haldaemon stop
>
>        After having shut down the daemon, you might want to run
>
>        pkill hald
>
>        to ensure that all the helper processe of hald are killed too. To start
>        the HAL daemon, use
>
>        /usr/sbin/hald --daemon=no --verbose=yes
>
>        gdb /usr/sbin/hald
>
>        and then typing
>
>        run --daemon=no --verbose=yes
>
>        at  the  (gdb)  prompt. To capture a back trace, use the bt command and
>        attach this to the bug report.
>
>        Please also attach the output of lshal(1) in the bug report if possible
>        (it's  not  possible  if the hald daemon crashed). If the nature of the
>        bug has to do with hotplugging, attach two outputs of  lshal(1)  -  one
>        before the device hotplug event and one after.
>
> SEE ALSO
>        udev(7),  dbus-daemon(1),  lshal(1), hal-set-property(1), hal-get-prop-
>        erty(1),  hal-find-by-property(1),  hal-find-by-capability(1),  hal-is-
>        caller-locked-out(1)
>
> -----------------------------------------------------------
>
> Have fun!
>
> Tod
>
--
=======================================================================
The descent to Hades is the same from every place. -- Anaxagoras
=======================================================================
Aaron Konstam telephone: (210) 656-0355 e-mail: [hidden email]

--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: haldaemon problem

d_j_w46
In reply to this post by tian-5
tian wrote:

> 在 2007-12-07五的 09:47 +1000,david walcroft写�:
>  
>> I'm trying to restart the daemon and get this
>>
>> [david@reddwarf ~]$ sudo /sbin/service haldaemon restart
>> Stopping HAL daemon:                                       [FAILED]
>> Starting HAL daemon:                                       [FAILED]
>>
>> Is it because I might not have haldaemon in my system.
>>    
> Do you have file /etc/init.d/haldaemon ?
>  
>> [david@reddwarf ~]$ sudo rpm -qa | grep haldaemon
>>
>> This brings up nothing.
>>
>>
>> Thanks   david
>>
>>    
>
>  
No I do not have /etc/init.d/haldaemon

david

--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: haldaemon problem

d_j_w46
In reply to this post by Todd Zullinger
Todd Zullinger wrote:

> david walcroft wrote:
>  
>> I'm trying to restart the daemon and get this
>>
>> [david@reddwarf ~]$ sudo /sbin/service haldaemon restart
>> Stopping HAL daemon:                                       [FAILED]
>> Starting HAL daemon:                                       [FAILED]
>>    
>
> Look in /var/log/messages for some some clues.
>
>  
>> Is it because I might not have haldaemon in my system.
>>
>> [david@reddwarf ~]$ sudo rpm -qa | grep haldaemon
>>    
>
> No.  The package name isn't haldaemon, it's just hal.  If you didn't
> have it installed, you wouldn't have the init script that the service
> command runs. :)
>
> You could check with rpm -V that the hal packages aren't messed up (if
> there's nothing obvious in the logs):
>
> rpm -V hal hal-libs
>
>  
No I do not have rpm -V hal hal-libs and no messages in the in the log.

  david

--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: haldaemon problem

d_j_w46
In reply to this post by Tod Merley
Tod Merley wrote:

> On Dec 6, 2007 3:47 PM, david walcroft <[hidden email]> wrote:
>  
>> I'm trying to restart the daemon and get this
>>
>> [david@reddwarf ~]$ sudo /sbin/service haldaemon restart
>> Stopping HAL daemon:                                       [FAILED]
>> Starting HAL daemon:                                       [FAILED]
>>
>> Is it because I might not have haldaemon in my system.
>>
>> [david@reddwarf ~]$ sudo rpm -qa | grep haldaemon
>>
>> This brings up nothing.
>>
>>
>> Thanks   david
>>
>> --
>> fedora-list mailing list
>> [hidden email]
>> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>>
>>    
>
> Hi david walcroft!
>
> To administrate, be root - become so "su".
>
> >From "man hald":
>
> ------------------------------------------------
>
> BUGS AND DEBUGGING
>        Please  send  bug reports to either the distribution or the HAL mailing
>        list, see http://lists.freedesktop.org/mailman/listinfo/hal on  how  to
>        subscribe.
>
>        First,  to  obtain  useful debug traces you will need to have debuginfo
>        packages installed. On a Fedora system this  is  in  the  hal-debuginfo
>        package and can be installed via the yum update program.
>
>        Second, shut down the existing hald daemon instance; on a Fedora system
>        this is achieved by
>
>        /etc/init.d/haldaemon stop
>
>        After having shut down the daemon, you might want to run
>
>        pkill hald
>
>        to ensure that all the helper processe of hald are killed too. To start
>        the HAL daemon, use
>
>        /usr/sbin/hald --daemon=no --verbose=yes
>
>        gdb /usr/sbin/hald
>
>        and then typing
>
>        run --daemon=no --verbose=yes
>
>        at  the  (gdb)  prompt. To capture a back trace, use the bt command and
>        attach this to the bug report.
>
>        Please also attach the output of lshal(1) in the bug report if possible
>        (it's  not  possible  if the hald daemon crashed). If the nature of the
>        bug has to do with hotplugging, attach two outputs of  lshal(1)  -  one
>        before the device hotplug event and one after.
>
> SEE ALSO
>        udev(7),  dbus-daemon(1),  lshal(1), hal-set-property(1), hal-get-prop-
>        erty(1),  hal-find-by-property(1),  hal-find-by-capability(1),  hal-is-
>        caller-locked-out(1)
>
> -----------------------------------------------------------
>
> Have fun!
>
> Tod
>
>  
I read the man "hald" but my problem is I
cannot shutdown hald as shown in my first post.

   david

--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: haldaemon problem

Rick Stevens-2
In reply to this post by d_j_w46
On Sat, 2007-12-08 at 09:25 +1000, david walcroft wrote:

> Todd Zullinger wrote:
> > david walcroft wrote:
> >  
> >> I'm trying to restart the daemon and get this
> >>
> >> [david@reddwarf ~]$ sudo /sbin/service haldaemon restart
> >> Stopping HAL daemon:                                       [FAILED]
> >> Starting HAL daemon:                                       [FAILED]
> >>    
> >
> > Look in /var/log/messages for some some clues.
> >
> >  
> >> Is it because I might not have haldaemon in my system.
> >>
> >> [david@reddwarf ~]$ sudo rpm -qa | grep haldaemon
> >>    
> >
> > No.  The package name isn't haldaemon, it's just hal.  If you didn't
> > have it installed, you wouldn't have the init script that the service
> > command runs. :)
> >
> > You could check with rpm -V that the hal packages aren't messed up (if
> > there's nothing obvious in the logs):
> >
> > rpm -V hal hal-libs
> >
> >  
> No I do not have rpm -V hal hal-libs and no messages in the in the log.

Can you "rpm -qa | grep hal" and see if you have any HAL stuff at all?
You should have at least hal and hal-libs.  If not, then "yum install
hal hal-libs"

----------------------------------------------------------------------
- Rick Stevens, Principal Engineer             [hidden email] -
- CDN Systems, Internap, Inc.                http://www.internap.com -
-                                                                    -
-   Errors have occurred. We won't tell you where or why.  We have   -
-                         lazy programmers.                          -
----------------------------------------------------------------------

--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: haldaemon problem

d_j_w46
In reply to this post by Aaron Konstam
Aaron Konstam wrote:

> On Fri, 2007-12-07 at 01:57 -0800, Tod Merley wrote:
>  
>> On Dec 6, 2007 3:47 PM, david walcroft <[hidden email]> wrote:
>>    
>>> I'm trying to restart the daemon and get this
>>>
>>> [david@reddwarf ~]$ sudo /sbin/service haldaemon restart
>>> Stopping HAL daemon:                                       [FAILED]
>>> Starting HAL daemon:                                       [FAILED]
>>>
>>> Is it because I might not have haldaemon in my system.
>>>
>>> [david@reddwarf ~]$ sudo rpm -qa | grep haldaemon
>>>
>>> This brings up nothing.
>>>
>>>
>>> Thanks   david
>>>
>>> --
>>> fedora-list mailing list
>>> [hidden email]
>>> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>>>
>>>      
>> Hi david walcroft!
>>
>> To administrate, be root - become so "su".
>>    
> su - would be better.
>  
>
>
>  
>> >From "man hald":
>>
>> ------------------------------------------------
>>
>> BUGS AND DEBUGGING
>>        Please  send  bug reports to either the distribution or the HAL mailing
>>        list, see http://lists.freedesktop.org/mailman/listinfo/hal on  how  to
>>        subscribe.
>>
>>        First,  to  obtain  useful debug traces you will need to have debuginfo
>>        packages installed. On a Fedora system this  is  in  the  hal-debuginfo
>>        package and can be installed via the yum update program.
>>
>>        Second, shut down the existing hald daemon instance; on a Fedora system
>>        this is achieved by
>>
>>        /etc/init.d/haldaemon stop
>>
>>        After having shut down the daemon, you might want to run
>>
>>        pkill hald
>>
>>        to ensure that all the helper processe of hald are killed too. To start
>>        the HAL daemon, use
>>
>>        /usr/sbin/hald --daemon=no --verbose=yes
>>
>>        gdb /usr/sbin/hald
>>
>>        and then typing
>>
>>        run --daemon=no --verbose=yes
>>
>>        at  the  (gdb)  prompt. To capture a back trace, use the bt command and
>>        attach this to the bug report.
>>
>>        Please also attach the output of lshal(1) in the bug report if possible
>>        (it's  not  possible  if the hald daemon crashed). If the nature of the
>>        bug has to do with hotplugging, attach two outputs of  lshal(1)  -  one
>>        before the device hotplug event and one after.
>>
>> SEE ALSO
>>        udev(7),  dbus-daemon(1),  lshal(1), hal-set-property(1), hal-get-prop-
>>        erty(1),  hal-find-by-property(1),  hal-find-by-capability(1),  hal-is-
>>        caller-locked-out(1)
>>
>> -----------------------------------------------------------
>>
>> Have fun!
>>
>> Tod
>>
>>    
> --
> =======================================================================
> The descent to Hades is the same from every place. -- Anaxagoras
> =======================================================================
> Aaron Konstam telephone: (210) 656-0355 e-mail: [hidden email]
>
>  
Yes I agree su - is best,but I don't have a hald to work on.
I seem to want the hald package,which one is it.

   david

--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: haldaemon problem

d_j_w46
In reply to this post by Rick Stevens-2
Rick Stevens wrote:

> On Sat, 2007-12-08 at 09:25 +1000, david walcroft wrote:
>  
>> Todd Zullinger wrote:
>>    
>>> david walcroft wrote:
>>>  
>>>      
>>>> I'm trying to restart the daemon and get this
>>>>
>>>> [david@reddwarf ~]$ sudo /sbin/service haldaemon restart
>>>> Stopping HAL daemon:                                       [FAILED]
>>>> Starting HAL daemon:                                       [FAILED]
>>>>    
>>>>        
>>> Look in /var/log/messages for some some clues.
>>>
>>>  
>>>      
>>>> Is it because I might not have haldaemon in my system.
>>>>
>>>> [david@reddwarf ~]$ sudo rpm -qa | grep haldaemon
>>>>    
>>>>        
>>> No.  The package name isn't haldaemon, it's just hal.  If you didn't
>>> have it installed, you wouldn't have the init script that the service
>>> command runs. :)
>>>
>>> You could check with rpm -V that the hal packages aren't messed up (if
>>> there's nothing obvious in the logs):
>>>
>>> rpm -V hal hal-libs
>>>
>>>  
>>>      
>> No I do not have rpm -V hal hal-libs and no messages in the in the log.
>>    
>
> Can you "rpm -qa | grep hal" and see if you have any HAL stuff at all?
> You should have at least hal and hal-libs.  If not, then "yum install
> hal hal-libs"
>
> ----------------------------------------------------------------------
> - Rick Stevens, Principal Engineer             [hidden email] -
> - CDN Systems, Internap, Inc.                http://www.internap.com -
> -                                                                    -
> -   Errors have occurred. We won't tell you where or why.  We have   -
> -                         lazy programmers.                          -
> ----------------------------------------------------------------------
>
>  

Yes I have hal as shown

[david@reddwarf ~]$ sudo rpm -qa | grep hal
hal-libs-0.5.10-1.fc8.i386
hal-0.5.10-1.fc8.i386
hal-devel-0.5.10-1.fc8.i386
hal-info-20071030-1.fc8.noarch
[david@reddwarf ~]$          

Does hald reside in one of these packages.

  david

--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: haldaemon problem

Rick Stevens-2
On Sat, 2007-12-08 at 09:40 +1000, david walcroft wrote:

> Rick Stevens wrote:
> > On Sat, 2007-12-08 at 09:25 +1000, david walcroft wrote:
> >  
> >> Todd Zullinger wrote:
> >>    
> >>> david walcroft wrote:
> >>>  
> >>>      
> >>>> I'm trying to restart the daemon and get this
> >>>>
> >>>> [david@reddwarf ~]$ sudo /sbin/service haldaemon restart
> >>>> Stopping HAL daemon:                                       [FAILED]
> >>>> Starting HAL daemon:                                       [FAILED]
> >>>>    
> >>>>        
> >>> Look in /var/log/messages for some some clues.
> >>>
> >>>  
> >>>      
> >>>> Is it because I might not have haldaemon in my system.
> >>>>
> >>>> [david@reddwarf ~]$ sudo rpm -qa | grep haldaemon
> >>>>    
> >>>>        
> >>> No.  The package name isn't haldaemon, it's just hal.  If you didn't
> >>> have it installed, you wouldn't have the init script that the service
> >>> command runs. :)
> >>>
> >>> You could check with rpm -V that the hal packages aren't messed up (if
> >>> there's nothing obvious in the logs):
> >>>
> >>> rpm -V hal hal-libs
> >>>
> >>>  
> >>>      
> >> No I do not have rpm -V hal hal-libs and no messages in the in the log.
> >>    
> >
> > Can you "rpm -qa | grep hal" and see if you have any HAL stuff at all?
> > You should have at least hal and hal-libs.  If not, then "yum install
> > hal hal-libs"
> >
> > ----------------------------------------------------------------------
> > - Rick Stevens, Principal Engineer             [hidden email] -
> > - CDN Systems, Internap, Inc.                http://www.internap.com -
> > -                                                                    -
> > -   Errors have occurred. We won't tell you where or why.  We have   -
> > -                         lazy programmers.                          -
> > ----------------------------------------------------------------------
> >
> >  
>
> Yes I have hal as shown
>
> [david@reddwarf ~]$ sudo rpm -qa | grep hal
> hal-libs-0.5.10-1.fc8.i386
> hal-0.5.10-1.fc8.i386
> hal-devel-0.5.10-1.fc8.i386
> hal-info-20071030-1.fc8.noarch
> [david@reddwarf ~]$          
>
> Does hald reside in one of these packages.

Yes, /usr/sbin/hald is contained in hal-0.5.10-1.fc8.i386, as is the
/etc/rc.d/init.d/haldaemon script:

[root@bigdog ~]# rpm -ql hal-0.5.10-1.fc8
   (some files...)
/etc/rc.d/init.d/haldaemon
   (more files...)
/usr/sbin/hald
   (more files...)

It should be running in run level 3 and 5, so as root:

        # chkconfig --level 35 haldaemon on

to ensure it's enabled, then if you're in either run level 3 or 5:

        # service haldaemon start

and it should be running.
----------------------------------------------------------------------
- Rick Stevens, Principal Engineer             [hidden email] -
- CDN Systems, Internap, Inc.                http://www.internap.com -
-                                                                    -
-     Never put off 'til tommorrow what you can forget altogether!   -
----------------------------------------------------------------------

--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: haldaemon problem

Todd Zullinger
In reply to this post by d_j_w46
david walcroft wrote:
> No I do not have rpm -V hal hal-libs and no messages in the in the
> log.

David, the rpm -V command above doesn't install anything and will only
report on problems found.  If it ran without any output, it means that
you have hal and hal-libs installed and that all the files from those
package match what was originally installed.  (See man rpm for more
details on verifying packages.)

I would look for error messages in /var/log/messages to see why
you seem to be getting errors starting the haldaemon service.  You
could open to terminals and run "tailf /var/log/messages" to watch the
messages logfile in real time.  Hit return a few times to add some
blank space.  This makes it easy to see new lines.

In another terminal, run "service haldaemon restart" and watch for any
errors or warnings in the first terminal.

--
Todd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
He who will not reason is a bigot; he who cannot is a fool; and he who
dares not is a slave.
    -- Sir William Drummond, Academical Questions


--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

attachment0 (554 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: haldaemon problem

d_j_w46
Todd Zullinger wrote:

> david walcroft wrote:
>  
>> No I do not have rpm -V hal hal-libs and no messages in the in the
>> log.
>>    
>
> David, the rpm -V command above doesn't install anything and will only
> report on problems found.  If it ran without any output, it means that
> you have hal and hal-libs installed and that all the files from those
> package match what was originally installed.  (See man rpm for more
> details on verifying packages.)
>
> I would look for error messages in /var/log/messages to see why
> you seem to be getting errors starting the haldaemon service.  You
> could open to terminals and run "tailf /var/log/messages" to watch the
> messages logfile in real time.  Hit return a few times to add some
> blank space.  This makes it easy to see new lines.
>
> In another terminal, run "service haldaemon restart" and watch for any
> errors or warnings in the first terminal.
>
>  
Pardon my ignorance but what are my options.

rpm {-V|--verify} [select-options] [verify-options]

    david


--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: haldaemon problem

d_j_w46
david walcroft wrote:

> Todd Zullinger wrote:
>> david walcroft wrote:
>>  
>>> No I do not have rpm -V hal hal-libs and no messages in the in the
>>> log.
>>>    
>>
>> David, the rpm -V command above doesn't install anything and will only
>> report on problems found.  If it ran without any output, it means that
>> you have hal and hal-libs installed and that all the files from those
>> package match what was originally installed.  (See man rpm for more
>> details on verifying packages.)
>>
>> I would look for error messages in /var/log/messages to see why
>> you seem to be getting errors starting the haldaemon service.  You
>> could open to terminals and run "tailf /var/log/messages" to watch the
>> messages logfile in real time.  Hit return a few times to add some
>> blank space.  This makes it easy to see new lines.
>>
>> In another terminal, run "service haldaemon restart" and watch for any
>> errors or warnings in the first terminal.
>>
>>  
> Pardon my ignorance but what are my options.
>
> rpm {-V|--verify} [select-options] [verify-options]
>
>    david
>
>
OK I found some more reading and found "rpm -vv"
There was nothing about 'hal'

  david

--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: haldaemon problem

Tod Merley
On Dec 8, 2007 3:37 PM, david walcroft <[hidden email]> wrote:

> david walcroft wrote:
> > Todd Zullinger wrote:
> >> david walcroft wrote:
> >>
> >>> No I do not have rpm -V hal hal-libs and no messages in the in the
> >>> log.
> >>>
> >>
> >> David, the rpm -V command above doesn't install anything and will only
> >> report on problems found.  If it ran without any output, it means that
> >> you have hal and hal-libs installed and that all the files from those
> >> package match what was originally installed.  (See man rpm for more
> >> details on verifying packages.)
> >>
> >> I would look for error messages in /var/log/messages to see why
> >> you seem to be getting errors starting the haldaemon service.  You
> >> could open to terminals and run "tailf /var/log/messages" to watch the
> >> messages logfile in real time.  Hit return a few times to add some
> >> blank space.  This makes it easy to see new lines.
> >>
> >> In another terminal, run "service haldaemon restart" and watch for any
> >> errors or warnings in the first terminal.
> >>
> >>
> > Pardon my ignorance but what are my options.
> >
> > rpm {-V|--verify} [select-options] [verify-options]
> >
> >    david
> >
> >
> OK I found some more reading and found "rpm -vv"
> There was nothing about 'hal'
>
>
>   david
>
> --
> fedora-list mailing list
> [hidden email]
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>

Hi david walcroft!

What Todd Zullinger suggested using "tailf" is very cool.  Thank you
Todd for helping Tod with his ability to troubleshoot Linux!

Looking at the thread I believe we know:

1. Hal IS on your system.
2. Hal has trouble stopping and starting.

FWIW - most of the following suggestions come from a Google search on
"Starting HAL daemon: [FAILED]".

First, lets see if we have any of hal running.  Running "aux | grep
hal" as ROOT on my system yields the following:

[root@localhost tod]# ps aux | grep hal
68        2022  0.0  0.5   4920  2904 ?        Ss   15:48   0:01 hald
root      2023  0.0  0.1   3084   932 ?        S    15:48   0:00 hald-runner
68        2034  0.0  0.1   2072   792 ?        S    15:48   0:00
hald-addon-keyboard: listening on /dev/input/event1
68        2035  0.0  0.1   2072   792 ?        S    15:48   0:00
hald-addon-keyboard: listening on /dev/input/event4
68        2038  0.0  0.1   2072   788 ?        S    15:48   0:00
hald-addon-keyboard: listening on /dev/input/event5
68        2040  0.0  0.1   2072   788 ?        S    15:48   0:00
hald-addon-keyboard: listening on /dev/input/event6
68        2041  0.0  0.1   2072   792 ?        S    15:48   0:00
hald-addon-keyboard: listening on /dev/input/event7
root      2071  0.0  0.1   3148   972 ?        S    15:48   0:00
/usr/libexec/hald-addon-cpufreq
68        2072  0.0  0.1   2072   788 ?        S    15:48   0:00
hald-addon-acpi: listening on acpi kernel interface /proc/acpi/event
root      2086  0.0  0.1   3136   872 ?        S    15:48   0:02
hald-addon-storage: polling /dev/sr0 (every 2 sec)
root     21780  0.0  0.1   4008   716 pts/3    S+   17:34   0:00 grep hal

Next, set SELinux to "Permissive" and try restarting hal.  On my
system with SELinux "Enforceing" I get:

[root@localhost tod]# /sbin/service haldaemon restart
Stopping HAL daemon:                                     [  OK  ]
Starting HAL daemon:                                       [  OK  ]

If that yeilds good results go back into "System > Administration >
SELinux Management" and when the "SELinux Administration" window comes
up set it back to "Enforceing" and also hit the "Relable on next
reboot" check box.  Reboot and repeat the test as shown above.

Beyond that I would make a directory in my "/home/me/Documents" called
"hal" and copy to it /var/log/"messages", "dmesg", and "secure" to the
new directory - change the permissions and  ownership of the copied
files to be used my you as the normal user, and then use your favorite
word processor to browse them and do searches on "hal" within them.

Good Hunting!

Tod

--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: haldaemon problem

Tod Merley
My bad!

On Dec 8, 2007 6:14 PM, Tod Merley <[hidden email]> wrote:
>

>
> First, lets see if we have any of hal running.  Running "aux | grep
> hal" as ROOT on my system yields the following:
>

The above should read:


First, lets see if we have any of hal running.  Running "ps aux | grep
hal" as ROOT on my system yields the following:

Cheers!

Tod

--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: haldaemon problem

Todd Zullinger
In reply to this post by d_j_w46
david walcroft wrote:
>> Pardon my ignorance but what are my options.
>>
>> rpm {-V|--verify} [select-options] [verify-options]

A little further down in the rpm manpage, the select-options and
verify-options are given:

   select-options
        [PACKAGE_NAME] [-a,--all] [-f,--file FILE]
        [-g,--group GROUP] {-p,--package PACKAGE_FILE]
        [--fileid MD5] [--hdrid SHA1] [--pkgid MD5] [--tid TID]
        [--querybynumber HDRNUM] [--triggeredby PACKAGE_NAME]
        [--whatprovides CAPABILITY] [--whatrequires CAPABILITY]

...

   verify-options
        [--nodeps] [--nofiles] [--noscripts]
        [--nodigest] [--nosignature]
        [--nolinkto] [--nomd5] [--nosize] [--nouser]
        [--nogroup] [--nomtime] [--nomode] [--nordev]

Further down that that, the PACKAGE SELECTION OPTIONS and VERIFY
OPTIONS sections got into more detail about each of these options.

For the purposes of finding out whether something was wrong with your
hal or hal-libs packages, you don't need any particular options except
for the command I suggested (rpm -V hal hal-libs).  That command will
verify that the packages hal and hal-lib are installed and that the
contents of those packages matches what was installed by rpm
originally.

> OK I found some more reading and found "rpm -vv"
> There was nothing about 'hal'

rpm -vv will just show the help if run by itself.  Were you adding
some other options in addition to -vv?

As I see it, to determine what you're having a problem starting and
stopping the hal daemon, you want to first verify that the hal
packages are installed and that they match what was installed by rpm
(using the rpm -V command above).  If that command produces no output,
then all should be well with your install.  The next step would be to
see if there is any information in the system logs about the failures.
Step 3: ??  Step 4: Profit! :)

--
Todd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Whenever 'A' attempts by law to impose his moral standards upon 'B',
'A' is most likely a scoundrel.
    -- H. L. Mencken


--
fedora-list mailing list
[hidden email]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

attachment0 (554 bytes) Download Attachment
12
Loading...