LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Other *NIX Forums > Solaris / OpenSolaris
User Name
Password
Solaris / OpenSolaris This forum is for the discussion of Solaris and OpenSolaris.
General Sun, SunOS and Sparc related questions also go here.

Notices

Reply
 
Search this Thread
Old 07-02-2013, 04:59 AM   #1
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,384

Rep: Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963
syslog-ng service not staying connected with some clients


Howdy y'all!

I've a Solaris 10 server I'm running a syslog-ng (2.0.9) instance on (with syslog-ng clients connecting to it as it goes) and I'm finding that after an apparently random amount of time, many clients stop connecting to it correctly. While 5 or so clients happily sit there with an established connection showing in netstat, 3 or so other clients constantly connect and then disconnect immediately, never managing to send any data to the server. if I restart the server process then these clients happily stay connected. I'm baffled as to why restarting the server will stop the client disconnecting, as syslog is a one way protocol, even over TCP, and it's the client sending the first FIN packet. But that's the cure, restart the server process.... Does this sound like anything anyone could grasp at?
 
Old 07-03-2013, 02:13 PM   #2
TB0ne
Guru
 
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 14,456

Rep: Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538
Quote:
Originally Posted by acid_kewpie View Post
Howdy y'all!

I've a Solaris 10 server I'm running a syslog-ng (2.0.9) instance on (with syslog-ng clients connecting to it as it goes) and I'm finding that after an apparently random amount of time, many clients stop connecting to it correctly. While 5 or so clients happily sit there with an established connection showing in netstat, 3 or so other clients constantly connect and then disconnect immediately, never managing to send any data to the server. if I restart the server process then these clients happily stay connected. I'm baffled as to why restarting the server will stop the client disconnecting, as syslog is a one way protocol, even over TCP, and it's the client sending the first FIN packet. But that's the cure, restart the server process.... Does this sound like anything anyone could grasp at?
I had a similar problem once, and tracked it down to the syslog-ng support of TCP wrappers. Shoving:
Code:
syslog-ng:ALL:ALLOW
..into the hosts.allow file, and bouncing tcpwrappers. Absolutely *ZERO* idea if it'll work for you, but it's worth a shot.
 
Old 07-04-2013, 03:31 AM   #3
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,384

Original Poster
Rep: Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963
well tcpwrappers was updated to say "syslog-ng: ALL" and that's certainly letting all the clients connect at some point. You've got ALLOW in there too though? Isn't that field a command to run on match?
 
Old 07-04-2013, 01:22 PM   #4
TB0ne
Guru
 
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 14,456

Rep: Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538
Quote:
Originally Posted by acid_kewpie View Post
well tcpwrappers was updated to say "syslog-ng: ALL" and that's certainly letting all the clients connect at some point. You've got ALLOW in there too though? Isn't that field a command to run on match?
Well....yes....sorry

Was a bit to vigorous copy/pasting things in.
 
Old 07-05-2013, 09:22 AM   #5
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,384

Original Poster
Rep: Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963
Meh... turns out syslog-ng has a default max of 10 concurrent client connections! DOH!
 
Old 07-05-2013, 09:32 AM   #6
TB0ne
Guru
 
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 14,456

Rep: Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538
Quote:
Originally Posted by acid_kewpie View Post
Meh... turns out syslog-ng has a default max of 10 concurrent client connections! DOH!
Seriously? Where did you find that, and how did you get around it?
 
Old 07-05-2013, 04:11 PM   #7
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,384

Original Poster
Rep: Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963
I found this... http://www.campin.net/syslog-ng/faq.html#max_conn

updated and then used ab to create 1000 connections quite happily.
 
1 members found this post helpful.
Old 07-05-2013, 04:27 PM   #8
TB0ne
Guru
 
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 14,456

Rep: Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538
Nice one. I've not had an issue like that in a while, but I babysit a mixed-bag worth of systems. Could be their 'stock' syslog feeders are disconnecting, and I've gotten lucky, and the TCP wrappers fix was a fluke.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Wifi not staying connected earthnet Linux - Laptop and Netbook 6 03-26-2013 01:01 PM
LXer: The Globe-Trotting Linux Geek: Staying Connected and Working Remotely LXer Syndicated Linux News 0 08-12-2009 08:50 PM
Hidden SSID + Big Trouble connecting or staying connected! sc_3007 Linux - Wireless Networking 4 08-21-2008 07:14 AM
Problems (eth0) staying connected to the Internet specialist125 Linux - Networking 5 06-16-2006 03:01 AM


All times are GMT -5. The time now is 10:47 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration