On Wed, 2006-11-22 at 07:29 +0100, Henrik Stoerner wrote:
read(3, "#\n# The hobbitlaunch.cfg file is"..., 131072) = 8992 read(3, "", 131072) = 0 time(NULL) = 1164150324
It dies while processing the hobbitlaunch.cfg file. Could you send me a copy of that file?
Attached
Also, if you could run hobbitlaunch with the --debug option it would help. I don't know how Mandriva decided to do the Hobbit startup, but it would usually be in the ~hobbit/server/hobbit.sh file
/usr/lib/hobbit/server/hobbit.sh, where ~hobbit is /var/lib/hobbit
that you need to add "--debug" to the hobbitlaunch command. No new information added to /var/log/hobbit/hobbitlaunch.log - just the same three lines I always get. Let me try interactive startup rather than running from init.d...
Now, reading through the strace, I think it is dying when reading /etc/hobbit/hobbitlaunch.d/ There are no files there. Let's see what happens when I add one. I'll make it blank for now....
[mcdonalddj at ldap ~]$ sudo touch /etc/hobbit/hobbitlaunch.d/00_test.cfg [mcdonalddj at ldap ~]$ ls -l /etc/hobbit/hobbitlaunch.d/00_test.cfg -rw-r--r-- 1 root root 0 Nov 22 06:41 /etc/hobbit/hobbitlaunch.d/00_test.cfg
And let's start it up again.... Hey, it starts now! Yeah!
Ok, with even a single file in /etc/hobbitlaunch.d, even a blank file, it starts up and life is grand. Now I just have to replicate my old BB configuration and re-write the 300 paging rules, and re-write those parts of my heavily hacked bbmap that I never got working quite right in hobbit 4.1 but never pursued because 4.2 was going to add a new API to gather some of those details. At least that will keep me off the streets for a few days ;-)
As I recall, the hobbitlaunch.d construct was added at Mandriva's request, to make packaging easier. Perhaps adding a comments-only file in that directory, named 00_sample.cfg, would be the quickest way to fix this.