[syslog-ng] [Bug 171] Unwanted IP adress Folder

[bugzilla at bugzilla.balabit.com]

https://bugzilla.balabit.com/show_bug.cgi?id=171





--- Comment #5 from JG <julien.groselle at gmail.com>  2012-04-03 11:45:05 ---
I already have resolv.conf and many libs according to https://lists.balabit.hu/pipermail/syslog-ng/2005-January/006908.html

in my chrooted environement i have this :
# l etc/
-rw-r--r-- 1 root root 2,9K  3 avril 08:55 localtime
-rw-r--r-- 1 root root  276  3 avril 08:55 nsswitch.conf
-rw-r--r-- 1 root root    0 14 mars  17:13 passwd
-rw-r--r-- 1 root root   70 14 mars  17:12 resolv.conf
drwxr-xr-x 6 root root 4,0K 30 sept.  2011 syslog-ng

# l lib/
-rw-r--r-- 1 root root 31K  3 avril 08:56 libnss_compat-2.11.3.so
-rw-r--r-- 1 root root 31K  3 avril 08:56 libnss_compat.so.2
-rw-r--r-- 1 root root 23K  3 avril 08:56 libnss_dns-2.11.3.so
-rw-r--r-- 1 root root 23K  3 avril 08:56 libnss_dns.so.2
-rw-r--r-- 1 root root 51K  3 avril 08:56 libnss_files-2.11.3.so
-rw-r--r-- 1 root root 51K  3 avril 08:56 libnss_files.so.2
-rw-r--r-- 1 root root 19K  3 avril 08:56 libnss_hesiod-2.11.3.so
-rw-r--r-- 1 root root 19K  3 avril 08:56 libnss_hesiod.so.2
-rw-r--r-- 1 root root 44K  3 avril 08:56 libnss_ldap.so.2
-rw-r--r-- 1 root root 43K  3 avril 08:56 libnss_nis-2.11.3.so
-rw-r--r-- 1 root root 51K  3 avril 08:56 libnss_nisplus-2.11.3.so
-rw-r--r-- 1 root root 51K  3 avril 08:56 libnss_nisplus.so.2
-rw-r--r-- 1 root root 43K  3 avril 08:56 libnss_nis.so.2

But if i take the problem back, does anyone have a syslog-ng installation with chrooted environnement and TLS on ?
Because before we used TLS (we used stunnel and redirection on localhost) we had not this problem...
Until I have configured Syslog-ng to use native TLS support, this ip address folder appear.

Maybe we have something wrong in our config file...
But we have a generic destination :
destination hosts {
   file("/$HOST/$YEAR-$MONTH/$DAY-$FACILITY-$HOST.log"
   owner(0) group(4) perm(0640) dir_perm(0750) dir_owner(0) dir_group(4) create_dirs(yes));
};

And I don't understand why the server set $HOST with hostname of client for all the filter, and sometimes set $HOST with IP Address for generic filter (but not
all the time)...
It drive me crazy...

Do we have a problem with the communication in between client and server ?

PS : we had a 2.6 installation and we have moved to 3.1 with the same config file. We have just replace the deprecated object...
Do you think the problem could come from this point ?

Regards.


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.