Hey,
Still having issues with horde on a few servers. Stuck on the lang selection screen. Have tryed the normal horde fixes, repair db, resethorde, upcp --force, forced pear, makecpphp etc..etc... hordes test.php seems alright.
Regardless when I click to log in to horde, my mysql panics, here is the error message. Mysql restarts and I'm prompted with the lang selection screen again... I have tryed using a blank my.cnf but no change.
Anyone else haivng this problem or can help me with another avenue to travel?
--------------------------
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=157286400
read_buffer_size=1044480
max_used_connections=2
max_connections=500
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1175596 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
060912 17:36:02 mysqld restarted
Still having issues with horde on a few servers. Stuck on the lang selection screen. Have tryed the normal horde fixes, repair db, resethorde, upcp --force, forced pear, makecpphp etc..etc... hordes test.php seems alright.
Regardless when I click to log in to horde, my mysql panics, here is the error message. Mysql restarts and I'm prompted with the lang selection screen again... I have tryed using a blank my.cnf but no change.
Anyone else haivng this problem or can help me with another avenue to travel?
--------------------------
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=157286400
read_buffer_size=1044480
max_used_connections=2
max_connections=500
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1175596 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
060912 17:36:02 mysqld restarted