chroot and hostname resolution problem [was : Re: [syslog-ng]centralized loghost]
can't find ktrace doing 'strace /etc/init.d/syslog-ng start', I can't find something strange, but this kind of things if out of my knowledge. I can send the log if someone could help. Is there someone who is running a chrooted syslog-ng running under a non root user as a log collector without any (hostname resolution) problem ? The jail is correctly configured. I've checked the necessary libs w/ 'ldd syslog-ng' and build the cache with 'ldconfig' (chrooted of course) /etc/nsswitch.conf & /etc/resolv.conf are in the jail too I'm currently running 1.5.21 w/ libol-0.3.3 "Guillaume LACHENAL" <glachenal@on-x.com> Sent by: syslog-ng-admin@lists.balabit.hu 10/30/02 11:14 Please respond to syslog-ng To: syslog-ng@lists.balabit.hu cc: Subject: Re: [syslog-ng]centralized loghost /etc/nsswitch.conf is available in the jail ktrace & truss are command not found on the box, i'll search for it when not chrooted, syslog-ng correctly resolve hostnames. "Ed Ravin" <eravin@panix.com> Sent by: syslog-ng-admin@lists.balabit.hu 10/28/02 17:31 Please respond to syslog-ng To: syslog-ng@lists.balabit.hu cc: Subject: Re: [syslog-ng]centralized loghost Guillaume LACHENAL writes:
As syslog-ng run chrooted, I've copied /etc/resolv.conf & /etc/hosts into the jail. It does not fix the issue
Does your system also require /etc/nsswitch.conf in the chroot? Do a ktrace/truss on the startup in the chroot and see if it finds all the files it needs to do DNS lookups. _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
Guillaume LACHENAL writes:
can't find ktrace
Ah, you must be using Linux. Should have said that up front.
doing 'strace /etc/init.d/syslog-ng start', I can't find something strange,
Look for "file not found" errors or anything else related to file access.
Is there someone who is running a chrooted syslog-ng running under a non root user as a log collector without any (hostname resolution) problem ?
I am - but I have "use_dns(no)" in my config. How about posting the log - make sure there is no private information in it. If it's too huge put it up on the web somewhere and post the URL to the list.
On Tue, Nov 05, 2002 at 05:53:41PM -0500, Ed Ravin wrote:
Guillaume LACHENAL writes:
Hi,
doing 'strace /etc/init.d/syslog-ng start', I can't find something strange,
I don't know about Linux/strace, but on most systems, you would have to use an option to the tracing utility to trace calls of child processes. Looks to me like you are tracing the shell process only. Try to run the syslog-ng BINARY from strace, and look for problems like Ed suggested.
Is there someone who is running a chrooted syslog-ng running under a non root user as a log collector without any (hostname resolution) problem ? I am - but I have "use_dns(no)" in my config.
Same here. I don't see any technical reason why this wouldn't work, unless you are missing resolv libraries (e.g. on Solaris) or supplementary configuration files in the jail. Gregor.
participants (3)
-
Ed Ravin
-
Gregor Binder
-
Guillaume LACHENAL