Good day!
I've faced a few troubles while upgrading LCG-2.6 to our cluster. YAIM version
was 2.6.0-8, previous version of LCG was 2.4.
1) Shipped MySQL version 4.0.25 refused to start the mysqld -- the daemon
got signal 11 (the OS is SL 304):
-----
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=8388600
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x8c31a30
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Bogus stack limit or frame pointer, fp=0xbfff0e18, stack_bottom=0x1e4, thread_st ack=196608, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x194 is invalid pointer
thd->thread_id=1786060848
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
-----
Tried to recompile release 4.0.25 from the native source -- still the same.
Ended up installing 4.1.14 built from source rpm taken from mysql.org --
it works.
2) The rgma-gin service does not start after reboot on the SE: it was
unable to connect to the port 8080 on the SE. Presumably, tomcat needs to
be on that port, but the original startup sequence is to start rgma-gin
first and only then the tomcat service.
Fixed by setting the chkconfig startup/shutdown sequence numbers for
rgma-gin to be 81 20 instead of 20 80. rgma-gin should be reenabled then
by `chkconfig --level 2345 off` and `chkconfig --level 2345 on`.
The rest of upgrade from 2.4 went smoothly -- thanks for your work, guys!
--
rea
|