Hi,

On Fri, Aug 27, 2010 at 11:27:33AM -0400, Turlapati, Sreenivasa wrote:
> Hi,
> 
> We compiled the HAProxy on AIX 5.3 successfully and ran few tests with basic 
> front-end  & back-end configuration.

cool.

> But the issue we got was with the logging, we were not able to log any 
> message even after we add the below lines to syslog.conf
> 
> local0.debug            /var/log/haproxy_0.log  rotate size 100k files 2
> local1.debug            /var/log/haproxy_1.log  rotate size 100k files 2
> local0.notice           /var/log/haproxy_n0.log rotate size 100k files 2
> local1.notice           /var/log/haproxy_n1.log rotate size 100k files 2

I'm not surprized. Unix sockets for logs work on about half of the
systems, because half of them use DGRAM and the other half STREAM.
Haproxy uses DGRAM. So if this does not work, you simply need the
classical UDP on port 514.

> And as per the information we got, we need to add SYSLOGD="-r"  to 
> /etc/default/syslogd file and we were unable to locate this file in our AIX 
> environment. Could you help us in AIX , for which file we need to add SYSLOGD 
> options?

The only think I could think of would be to check in "man syslogd" or
"man syslog", in order to find the correct option to make syslogd listen
on UDP. You will then probably find references to the config file to
change if any. If the daemon is started from a specific script, it is
possible that you have to modify the script to pass an option to syslogd.

Alternatively if using the default AIX's syslogd is too complicated to set
up, you could install your own syslogd. After all, you managed to build
haproxy, now that your build environment is ready, simply build syslog-ng
and it will be a *lot* better. It won't even require running as root.

Regards,
Willy


Reply via email to