Quoting sean finney ([EMAIL PROTECTED]):
> hi alan,
> 
> On Wed, May 24, 2006 at 10:38:16AM -0500, Alan Schwartz wrote:
> > It occurs when my nagios monitoring system is running the check_mysql
> > plugin against this mysql server. That plugin is running as
> > follows:
> > 
> >     check_mysql -H <mysql ip address> -u nagiostest
> 
> hmm... maybe this problem has something to do with the mix of
> libmysqlclient12 and libmysqlclient14 libraries on the system?

It's the same on the other two mysql systems I have, which 
don't exhibit this problem (and are also nagios-monitored,
same setup).

> out of curiosity, if you set up nagios not to start at boot
> time (update-rc.d -f nagios remove), reboot, and then use
> check_mysql from a remote host on the same network, do you
> get the same problem?

I can not reliably replicate the problem by running check_mysql from
the shell on the nagios server, when nagios is not monitoring mysql on
the host (using su nagios -c "check_mysql -H ipaddress -u nagiostest"). 

It appears I can reliably replicate it when nagios runs, but I'm not
sure -- it may be the confluence of nagios's check running at the
same time that spamassassin is connecting to update the bayesian
tables, or similar (which is another key difference between
this system and the others that work -- this is the only one
with spamassassin using sql). On the other hand, the problem seems
to go away when nagios isn't checking mysql, and to reemerge when
it is. (I turned off nagios monitoring of mysql on this system
for a day, and had no problems that day. I turned it back on, and
had a mysql segfault within minutes -- though not at the exact
time of the check_mysql run -- and I can get this behavior
reliably.).

More information on check_mysql's operation: the mysql log shows
a connection, a 'statistics' request, and quit.  mysql_check appears to
call mysql_stat() to do its work, as per this ltrace of mysql_check:

mysql_init(0xbffff820, 0xbffffae4, 0x40017a90, 224, 0) = 0xbffff820
mysql_real_connect(0xbffff820, 0xbffffc08, 0xbffffc1a, 0, 0x804d920) = 
0xbffff820
mysql_stat(0xbffff820, 0xbffffc08, 0xbffffc1a, 0x4006df66, 0) = 0x804e4f0
__strdup(0x804e4f0, 0xbffffc08, 0xbffffc1a, 0x4006df66, 0) = 0x8050568
mysql_error(0xbffff820, 0xbffffc08, 0xbffffc1a, 0x4006df66, 0) = 0xbffff85c
mysql_errno(0xbffff820, 0xbffffc08, 0xbffffc1a, 0x4006df66, 0) = 0
mysql_errno(0xbffff820, 0xbffffc08, 0xbffffc1a, 0x4006df66, 0) = 0
mysql_errno(0xbffff820, 0xbffffc08, 0xbffffc1a, 0x4006df66, 0) = 0
mysql_close(0xbffff820, 0xbffffc08, 0xbffffc1a, 0x4006df66, 0) = 0xbffff820

> are you using any non-sarge packages on your system, btw?

Other than clamav from volatile, I hadn't thought so, but
apt-show-versions finds:

libgtkhtml20 1.0.2-1.woody1 installed: No available version in archive
libisc4 1:9.2.1-2.woody.2 installed: No available version in archive
libnkf-ruby 1.6.7-3woody4 installed: No available version in archive
libtiff3g-dev 3.5.5-6.woody5 installed: No available version in archive
xlib6g 4.1.0-16woody6 installed: No available version in archive
libsasl7 1.5.27-3.1woody5 installed: No available version in archive
libsasl-dev 1.5.27-3.1woody5 installed: No available version in archive
libnmz3 2.0.10-1woody3 installed: No available version in archive
libpgsql2 7.2.1-2woody8 installed: No available version in archive
libswig1.3 1.3.19-1.woody.1 installed: No available version in archive
libdns5 1:9.2.1-2.woody.2 installed: No available version in archive
sasl-bin 1.5.27-3.1woody5 installed: No available version in archive
libtiff3g 3.5.5-6.woody5 installed: No available version in archive

None appear to be involved with mysqld, however.

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
           Alan Schwartz               | Disclaimer: I represent no one
          <[EMAIL PROTECTED]>             |
         Associate Professor           |Life is what happens to you while
   Department of Medical Education     | you're busy making other plans
  University of Illinois at Chicago    |          - J. Lennon
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Attachment: pgpomZHqSQiah.pgp
Description: PGP signature

Reply via email to