We’re using 2 servers in production so that we have redundancy for our infobright servers. Things have been working quite well for about a week. Then yesterday on our passive master during a load we got this error in the infobright.log file:
2009-07-06 14:38:42 Internal error: An object unlocked too many times in memory manager.
2009-07-07 09:49:19 Error: Could not open or lock required tables.
During the Load the script got this error from this server:
“Lost connection to MySQL server during query”
I was not able to shut down infobright with the /etc/init.d/mysql-ib stop command. I tried twice and got this error msg in the bh.err file the first time:
90707 9:49:19 [Note] SCHEDULER: Purging queue. 0 events
090707 9:49:21 [Warning] /usr/local/infobright-3.1.1-x86_64/bin/mysqld: Forcing close of thread 6100 user: ‘myuserblah’
But no other errors while I tried to get infobright to shut down. I did the ole kil -9 on the pid. Then I started infobright & stopped it in the normal manner & infobright started & stopped normally.
The server appears to be working fine now.
The primary server loading the same files did not have a problem.
DETAILS:
Master DB server uname -a
Linux primary-db 2.6.24-23-generic #1 SMP Mon Jan 26 01:04:16 UTC 2009 x86_64 GNU/Linux
Secondary DB server uname -a (problem server)
Linux secondary-db 2.6.24-23-generic #1 SMP Wed Apr 1 21:43:24 UTC 2009 x86_64 GNU/Linux
Both are running:
Server version 5.1.14-log
infobright-3.1.1-x86_64
The only difference is one is running infobright from a symlink (primary server):
/usr/local/infobright
The secondary server is running infobright from
/usr/local/infobright-3.1.1-x86_64
Guess I’ll check on the infobright.ini & my-ib.cnf differences.
Thoughts? Shoud I file a bug report?
thanks,
erin

