1 |
On Saturday 04 August 2007 11:21, Mick wrote: |
2 |
> On Tuesday 17 July 2007 10:52, Alessandro del Gallo wrote: |
3 |
> > Mick ha scritto: |
4 |
> > > On Monday 16 July 2007 10:26, Alessandro del Gallo wrote: |
5 |
> > >> Mick ha scritto: |
6 |
> > >>> Hi All, |
7 |
> > >>> |
8 |
> > >>> I noticed on a box of mine that hald won't start: |
9 |
> > >>> ========================================== |
10 |
> > >>> # /etc/init.d/hald restart |
11 |
> > >>> * Starting Hardware Abstraction Layer daemon ... [ !! ] |
12 |
> > >>> ========================================== |
13 |
> > >>> |
14 |
> > >>> Confusingly, the logs don't show anything. How do I troubleshoot |
15 |
> > >>> this? |
16 |
> > >> |
17 |
> > >> I had the same problem: |
18 |
> > >> |
19 |
> > >> hald was sucking 99% cpu, removables devices didn't work |
20 |
> > >> and launching hald from terminal with the option "hald --daemon=no |
21 |
> > >> --verbose=yes" i discovered it was on a infinite loop echo-ing |
22 |
> > >> something about rules so I got in /etc/udev/rules.d |
23 |
> > >> and found (by probing one by one) 99-libgphoto2.rules that |
24 |
> > >> was HALS's murder. |
25 |
> > > |
26 |
> > > Thank you Alessandro, what do you mean by probing - how did you probe |
27 |
> > > them? |
28 |
> > |
29 |
> > moving it to /tmp and restart hald, |
30 |
> > becouse the error I got when launching |
31 |
> > # hald --daemon=no --verbose=yes |
32 |
> > is "Unhandled Rule (0)" |
33 |
> > so deleting the rules (delete de rule, start hald, if it doesn't |
34 |
> > works put the rule back , and move another) from etc/udev/rules.d |
35 |
> > I debugged the problem, the bad rule was owned by gphoto2 |
36 |
> |
37 |
> I've had a chance to get back to this machine and this is what it is |
38 |
> showing: ========================================== |
39 |
> # hald --daemon=no --verbose=yes |
40 |
> 11:16:08.930 [I] hald.c:533: hal 0.5.9 |
41 |
> 11:16:08.931 [I] hald.c:598: Will not daemonize |
42 |
> 11:16:08.945 [I] hald_dbus.c:4807: local server is listening at |
43 |
> unix:abstract=/var/run/hald/dbus-1LzyssbMzl,guid=faadd829b7aaff57dce0510046 |
44 |
>b451e8 11:16:09.174 [I] hald_runner.c:299: Runner has pid 31241 |
45 |
> 11:16:09.180 [W] ci-tracker.c:200: Could not get uid for connection: |
46 |
> org.freedesktop.DBus.Error.NameHasNoOwner Could not get UID of |
47 |
> name 'org.freedesktop.DBus': no such name |
48 |
> 11:16:09.181 [E] hald_dbus.c:4462: Cannot get caller info for |
49 |
> org.freedesktop.DBus |
50 |
> Runner started - allowed paths |
51 |
> are '/usr/libexec:/usr/lib/hal/scripts:/usr/bin' |
52 |
> 11:16:09.196 [I] hald_runner.c:180: runner connection is 0x8096988 |
53 |
> 11:16:09.330 [I] mmap_cache.c:251: cache mtime is 1184442336 |
54 |
> *** [DIE] osspec.c:watch_fdi_files():349 : Unable to initialize inotify: |
55 |
> Function not implemented |
56 |
> ========================================== |
57 |
> |
58 |
> What do you make of this? |
59 |
|
60 |
I removed /usr/share/hal and tried to remerge it. It complained that I "MUST" |
61 |
compile pciutils without the zlib flag. Not sure why pciutils has the zlib |
62 |
flag as a default, but if it is causing a problem with hal shouldn't it be |
63 |
removed? |
64 |
|
65 |
Anyway, after masking zlib for pciutils and remerging both packages it now |
66 |
seems to be working again . . . |
67 |
|
68 |
Thanks for your suggestions. |
69 |
-- |
70 |
Regards, |
71 |
Mick |