MHMDhub / enterprise-log-search-and-archive

Automatically exported from code.google.com/p/enterprise-log-search-and-archive
0 stars 0 forks source link

Can not perform searches. getting "WARNING: maxed out, dismissing client" in searchd.log #168

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.  search using web interface or connect to sphinx mysql port from command 
line.  mysql -P 9306 -h localhost
2.  watch the /data/elsa/log/searchd.log
3.  I see "WARNING: maxed out, dismissing client" and connection to sphinx 
search refused.

What is the expected output? What do you see instead?

I would like to be able to connect and perform search.

What version of the product are you using? On what operating system?

sphinx 2.0.5  and linux 64bit (slackware 14)

Please provide any additional information below.

This error started appearing only this morning.  I wonder if it is to do with 
number of indexes.  We have low volume logging so I have increated the indexes 
to 800.

Original issue reported on code.google.com by en.chi...@gmail.com on 23 Jul 2013 at 11:57

GoogleCodeExporter commented 8 years ago
What version of ELSA are you on?  This is noted in the /etc/elsa_web.conf file 
under "version."  The issue is that you're receiving too many queries, but 
that's far from a root cause.  There should be some clues in the 
/data/elsa/log/query.log file, which records each Sphinx query.

Original comment by mchol...@gmail.com on 24 Jul 2013 at 6:47

GoogleCodeExporter commented 8 years ago
Thanks, Martin.   Here is the version.  I recently updated.

      "Author" : " mcholste",
      "Date" : " 2013-07-15 12:39:25 +1200 (Mon, 15 Jul 2013)",
      "Rev" : " 973",
      "Sphinx" : "Sphinx 2.0.5-id64-release (r3308)"

I have 4 or 5 saves searches that run every minute.  Other than it should
get only very few queries per day from web interface.   However since the
system is not able to connect sphinx for search, I do not see any logging
in /data/elsa/log/query.log during the problem period.  Here is the chunk
from query.log.  (see the gap between 09:55 and 14:57)

Wed Jul 24 09:55:15.952 2013] 0.000 sec [ext2/4/ext 0 (0,100)] [temp_507,
temp_508, temp_509, temp_510]  ("Crazy Browser") !(anonymous)
[Wed Jul 24 09:55:15.997 2013] 0.000 sec [ext2/4/ext 0 (0,100)] [temp_507,
temp_508, temp_509, temp_510]  ("crazy browser")
[Wed Jul 24 09:55:16.089 2013] 0.001 sec [ext2/4/ext 0 (0,100)] [temp_507,
temp_508, temp_509, temp_510]  (NZST admin by console0 from on vty) !( MSDP\
-5\-PEER_UPDOWN| PIM\-6\-INVALID_RP_JOIN| SYS\-5\-CONFIG_I |
SYS\-6\-LOGGINGHOST_STARTSTOP |"last message repeated 1
time"|Configured|REDUNDANCY\-5\-CA
LENDAR_RATELIMIT |REDUNDANCY\-5\-CONFIGSYNC )
[Wed Jul 24 09:55:16.143 2013] 0.001 sec [ext2/4/ext 0 (0,100)] [temp_507,
temp_508, temp_509, temp_510]  ( NZST 1 admin by console0 from message on re
peated time vty) !(Configured|last)
[Wed Jul 24 09:55:16.193 2013] 0.000 sec [ext2/4/ext 0 (0,100)] [temp_507,
temp_508, temp_509, temp_510]  (NZST)
[Wed Jul 24 14:57:02.771 2013] 0.000 sec [ext2/0/ext 16 (0,9999) @host_id]
[temp_1]
[Wed Jul 24 14:57:02.772 2013] 0.000 sec [ext2/0/ext 1 (0,9999) @class_id]
[temp_1] @host 2621309194
[Wed Jul 24 14:57:02.773 2013] 0.000 sec [ext2/0/ext 1 (0,9999) @class_id]
[temp_1] @host 184483056
[Wed Jul 24 14:57:02.773 2013] 0.000 sec [ext2/0/ext 1 (0,9999) @class_id]
[temp_1] @host 2621309385
[Wed Jul 24 14:57:02.774 2013] 0.000 sec [ext2/0/ext 1 (0,9999) @class_id]
[temp_1] @host 184479777

On Thu, Jul 25, 2013 at 6:48 AM, <
enterprise-log-search-and-archive@googlecode.com> wrote:

Original comment by en.chi...@gmail.com on 24 Jul 2013 at 7:29

GoogleCodeExporter commented 8 years ago
It appears that you are a few revisions behind.  Could please run the 
install.sh node update and install.sh web update commands to get to the current 
version?  I'd like to see if the problem persists then.

Original comment by mchol...@gmail.com on 25 Jul 2013 at 5:41

GoogleCodeExporter commented 8 years ago
Hi Martin,
               Thanks.. It seems to be working fine since I reported the
issue on Jul24th.  If it happens again, I will update elsa and see if it
fixes the issue.

Original comment by en.chi...@gmail.com on 28 Jul 2013 at 7:52

GoogleCodeExporter commented 8 years ago
Good to hear, please reopen the ticket if it happens again.

Original comment by mchol...@gmail.com on 28 Jul 2013 at 11:21