Hi all,
thanks for your replies. It would appear Solaris syslog doesn't interpret the
wildcard, i.e. local0.*
Instead an entry is required for each logging level in the syslog.conf file,
e.g.
local0.debug
local0.err
.....
Eoin
-----Original Message-----
From: germang#olx.com.ar [mailto:germang#olx.com.ar]On Behalf Of German
Gutierrez :: OLX Operation Center
Sent: 18 February 2010 17:24
To: Mallin, Eoin
Cc: haproxy#formilux.org
Subject: Re: Enabling logging on solaris
This e-mail has been received by the Revenue Internet e-mail service. (IP)
On Thu, Feb 18, 2010 at 2:09 PM, Mallin, Eoin <emallin#revenue.ie> wrote:
>
> Hi all,
> I'm trying to get HAProxy logging enabled on solaris 9. My HAProxy
> configuration file looks as follows:
>
> log 127.0.0.1 local0 info
>
> /etc/syslog.conf now has the following entry
>
> local0.* /haproxy/log/haproxy.log
>
> Is there another step to allow syslog accept socket connections?
>
> Many thanks,
> Eoin
>
>
> Eoin Mallin
> ______________________________________________________________
> ITS Architecture
> Castle View
> Georges Street
> Dublin 2
> VPN: 35379
>
>
Just a hint, try to see if syslog is listening on udp port 514, netstat or, if its installed, lsof -i :514 can help you on that.
-- Germán Gutiérrez OLX Operation Center OLX Inc. Buenos Aires - Argentina Delivering common sense since 1969 <Epoch Fail!>. The Nature is not amiable; It treats impartially to all the things. The wise person is not amiable; He treats all people impartially. No afecta al sitio, no necesita QA. ********************************************************************* Please note that Revenue cannot guarantee that any personal and sensitive data, sent in plain text via standard email, is fully secure. Customers who choose to use this channel are deemed to have accepted any risk involved. The alternative communication methods offered by Revenue include standard post and the option to register for our (encrypted) secure email service. http://www.revenue.ie/en/practitioner/secure-email.html *********************************************************************Received on 2010/02/19 11:00
This archive was generated by hypermail 2.2.0 : 2010/02/19 11:15 CET