Sponsored Content
Full Discussion: syslog-ng.conf
Operating Systems Solaris syslog-ng.conf Post 302258943 by Tornado on Sunday 16th of November 2008 08:49:22 PM
Old 11-16-2008
I am getting this error now..

On Client:
Quote:
syslog-ng[22409]: Connection broken; time_reopen='10'
syslog-ng[22409]: EOF occurred while idle; fd='10'
On Server:
Quote:
syslog-ng[880]: Number of allowed concurrent connections exceeded; num='10', max='10'
All I can find is this solution.
Quote:
source s_local {
unix-streams ("/dev/log" max-connections(20));
internal();
pipe("/proc/kmsg");
};
The problem is that I am not using unix-streams and max-connections(20) is an option for unix-streams. This is what my source line looks like.
Quote:
source s_local { sun-streams ("/dev/log" door("/var/run/syslog_door")); internal(); };
Anyone know how I can fix this error in my config(using sun-streams) ?


Here is the definition from the config file:
Quote:
# unix-stream
# unix-dgram - These two drivers behave similarly:
# they open the given AF_UNIX socket, and start
# listening on them for messages. unix-stream() is
# primarily used on Linux, and uses SOCK_STREAM
# semantics (connection oriented, no messages are
# lost), unix-dgram() is used on BSDs, and uses
# SOCK_DGRAM semantics, this may result in lost
# local messages, if the system is overloaded.
#
# To avoid denial of service attacks when using
# connection-oriented protocols, the number of
# simultaneously accepted connections should be
# limited. This can be achieved using the
# max-connections() parameter. The default value of
# this parameter is quite strict, you might have to
# increase it on a busy system.
#
# Both unix-stream and unix-dgram has a single
# required positional argument, specifying the
# filename of the socket to create, and several
# optional parameters.


# sun-streams
# Solaris uses its STREAMS API to send messages to
# the syslogd process. You'll have to compile
# syslog-ng with this driver compiled in (see
# ./configure --help).
#
# Newer versions of Solaris (2.5.1 and above), uses a
# new IPC in addition to STREAMS, called door to
# confirm delivery of a message. Syslog-ng supports
# this new IPC mechanism with the door() option.
#
# The sun-streams() driver has a single required
# argument, specifying the STREAMS device to open and
# a single option.
Tornado
 

10 More Discussions You Might Find Interesting

1. Red Hat

syslog.conf

Hi all I have a RedHat Linux AS2.1 server that keep crashing/rebooting and there are no messages in the /var/log/messages file pointing to any problems. I had a look at the /etc/syslog.conf file to see what gets logged to /var/log/messages, but I don't know what else to add. Can anyone tell me... (1 Reply)
Discussion started by: soliberus
1 Replies

2. Linux

SYSLOG.CONF another port

Hi everybody, i have a little problem... I have two server srv01 and srv02. srv02 have a syslogd server onboard and listen on 515... not on 514 (it's busy). How i configure the syslog.conf of srv01 for send logs on srv02:515 ??? Now i have on srv01: *.* @srv02 if i write: *.* ... (0 Replies)
Discussion started by: Zio Bill
0 Replies

3. UNIX for Dummies Questions & Answers

Help confiuring syslog.conf

Hi, We had a hardware problem at work and none of the kernel problems outputted to the log file, just the screen. How can I configure the syslogd.conf file to record kernel events (ie hardware problems) to /dev/console and/var/log/messages. Can I just put: /dev/console /var/log/messages on... (5 Replies)
Discussion started by: mojoman
5 Replies

4. Solaris

Want to know about a entry in syslog.conf

Hi Everyone, I just wanted to know about the below entry in syslog.conf in Solaris 10: kern.notice @destserver Now the log will be redirected to destserver. But I want to know the location on the destserver where this log will be thrown. Thanks in Advance, Deepak (4 Replies)
Discussion started by: naw_deepak
4 Replies

5. UNIX for Advanced & Expert Users

Modifying syslog.conf

I have a RHEL box that I want to be the loghost for all of the other systems on my network and have set up a /logs partitions to hold all of the logs. I've also created a file called current.log that will contain daily logs and created it using the following command: cp /dev/null current.log. ... (4 Replies)
Discussion started by: goose25
4 Replies

6. Shell Programming and Scripting

syslog.conf

How can i configure messages with warn priority to be logged in /var/log/mywarnings.log ? (1 Reply)
Discussion started by: g0dlik3
1 Replies

7. Solaris

best configuration for syslog.conf

I would like to configure the syslog.conf to have a good monitoring information about my system. do you have any idea about best configuration from your experience in your Data Centers BR, (5 Replies)
Discussion started by: maxim42
5 Replies

8. Red Hat

Configuring syslog.conf

Hi, I would like to configure syslog linux client, syslog server is windows server. so adding on linux client in /etc/syslog.conf @hostname will work in the place of directory location. example of /etc/syslog.conf # Log all kernel messages to the console. # Logging much else clutters up... (2 Replies)
Discussion started by: manoj.solaris
2 Replies

9. BSD

Syslog.conf issue

I'm trying to get all ipfw logs going to ipfw.log I've managed that, but ipfw.log is also getting stuff that shows up in system.log !-ipfw *.notice;authpriv,remoteauth,ftp,install,internal.none /var/log/system.log kern.* /var/log/kernel.log... (5 Replies)
Discussion started by: jnojr
5 Replies

10. Solaris

Which are the available entries to forward syslog in syslog.conf?

Hi Community Which are the available entries to forward syslog in syslog.conf i have put *.err;kern.debug;daemon.notice;mail.crit;user.alert;user.emerg;kern.notice;auth.notice;kern.warning @172.16.200.50 and it's not going through.giving error message like below: syslogd:... (2 Replies)
Discussion started by: bentech4u
2 Replies
socklog(8)						      System Manager's Manual							socklog(8)

NAME
socklog - small and secure syslogd replacement for use with runit SYNOPSIS
socklog [-rRU] [unix] [path] socklog [-rR] inet [ip] [port] socklog [-rR] ucspi [args] DESCRIPTION
socklog is run under runit's runsv(8), writing syslog messages it receives from unix domain socket path or an inet udp socket ip:port through a pipe provided by runsv(8) to a svlogd(8) process. socklog can be run as an ucspi application to listen to an unix domain stream socket and for more flexible distributed logging. If the environment variables $UID and/or $GID are present, socklog drops permissions to those ids after creating and binding the socket (not in ucspi mode). socklog converts syslog facility and priority information to names (facility.priority:) as found in /usr/include/syslog.h at compile time if present. On solaris socklog also accepts sun_stream as first argument. Please see the web page for details. UNIX SOCKET
socklog [ unix ] [ path ] Starting socklog with the 1st argument unix, socklog will listen to the unix domain socket path. If path is omitted, the default /dev/log is used. The 1st argument may be omitted, default is unix. INET SOCKET
socklog inet [ ip ] [ port ] Starting socklog with the 1st argument inet, socklog will listen to the inet udp socket ip:port. If ip starts with 0, socklog will bind to all local interfaces. If port is less or equal 1024, socklog must be run by root. port may be omitted, default is 514. ip may be omitted, default is 0. socklog prepends a.b.c.d: to each syslog message it receives, where a.b.c.d is the ip address of the connecting system. UCSPI MODE
socklog ucspi [ args ] Starting socklog with the 1st argument ucspi, socklog will run as an ucspi application. Normally socklog will only be started in ucspi mode by an ucspi server tool, such as tcpsvd(8), tcpserver(1) or unixserver. For each arg, socklog will prepend $arg: to each syslog message, if the environment variable $arg is present (maximum is 8). OPTIONS
-r raw. Write the raw syslog messages (no conversion of facility and priority) to the pipe, additionally to the log messages with sys- log facility and priority converted to names. -R raw only. Same as -r above, but write the raw syslog messages only. -U respect umask. Don't set umask to 0 before creating a unix domain socket, but respect the current setting of umask(2). This option only takes effect in unix mode. SEE ALSO
sv(8), runsvdir(8), runsv(8), svlogd(8), tryto(1), uncat(1), socklog-check(8), tcpsvd(8), nc(1) http://smarden.org/socklog/ http://smarden.org/runit/ AUTHOR
Gerrit Pape <pape@smarden.org> socklog(8)
All times are GMT -4. The time now is 07:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy