[Dovecot] Dovecot fails after updating MySQL
I just updated MySQL to Server version: 5.5.8 on my FreeBSD-8.2 system. Now Dovecot refuses to run. Prior to this, dovecot had been running for several years without a problem.
This is the output of "dovecot -n"
# 1.2.16: /usr/local/etc/dovecot.conf # OS: FreeBSD 8.2-PRERELEASE amd64 ufs log_path: /var/log/dovecot.log login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_privileged_group: mail mail_location: maildir:/var/mail/vhost/seibercom.net/gerard mail_plugins: expire imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep lda: postmaster_address: postmaster@seibercom.net mail_plugins: sieve sieve_global_path: /usr/local/etc/dovecot/sieve/gerard.sieve sendmail_path: /usr/sbin/sendmail auth default: mechanisms: plain login digest-md5 cram-md5 username_format: %Lu verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: expire: Trash 2 Spam/* 2 expire_dict: proxy::expire dict: expire: mysql:/usr/local/etc/dovecot-dict-expire.conf
The /var/run/dovecot directory looks like this:
drwxr-xr-x 3 root wheel 512B 2011-01-10 18:49:44 EST ./ drwxr-xr-x 15 root wheel 1.0K 2011-01-10 18:49:37 EST ../ srw-rw---- 1 root wheel 0B 2011-01-10 18:49:37 EST auth-client= srw------- 1 vmail vmail 0B 2011-01-10 18:49:37 EST auth-master= srw------- 1 root wheel 0B 2011-01-10 18:49:37 EST auth-worker.34781= srwxrwxrwx 1 root wheel 0B 2011-01-10 18:49:37 EST dict-server= lrwx------ 1 root wheel 27B 2011-01-10 18:49:37 EST dovecot.conf@ -> /usr/local/etc/dovecot.conf drwxr-x--- 2 root dovecot 512B 2011-01-10 18:49:37 EST login/ -rw------- 1 root wheel 6B 2011-01-10 18:49:37 EST master.pid
This is the log file output, updated every second (snippet)
Jan 10 18:42:11 dovecot: Info: Dovecot v1.2.16 starting up Jan 10 18:42:11 dovecot: Error: child 34517 (auth-worker) killed with signal 11 (core not dumped) Jan 10 18:42:11 dovecot: Error: child 34521 (auth-worker) killed with signal 11 (core not dumped)
I have tried deleting and rebuilding dovecot without success. I am at a lose to figure out what the problem is.
-- Jerry ✌ Dovecot.user@seibercom.net
Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header.
I would rather say that a desire to drive fast sports cars is what sets man apart from the animals.
On Jan 10, 2011, at 4:19 PM, Jerry wrote:
I just updated MySQL to Server version: 5.5.8 on my FreeBSD-8.2
system. Now Dovecot refuses to run. Prior to this, dovecot had been running
for several years without a problem.This is the output of "dovecot -n"
# 1.2.16: /usr/local/etc/dovecot.conf # OS: FreeBSD 8.2-PRERELEASE amd64 ufs log_path: /var/log/dovecot.log login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_privileged_group: mail mail_location: maildir:/var/mail/vhost/seibercom.net/gerard mail_plugins: expire imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox- sep lda: postmaster_address: postmaster@seibercom.net mail_plugins: sieve sieve_global_path: /usr/local/etc/dovecot/sieve/gerard.sieve sendmail_path: /usr/sbin/sendmail auth default: mechanisms: plain login digest-md5 cram-md5 username_format: %Lu verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: expire: Trash 2 Spam/* 2 expire_dict: proxy::expire dict: expire: mysql:/usr/local/etc/dovecot-dict-expire.conf
The /var/run/dovecot directory looks like this:
drwxr-xr-x 3 root wheel 512B 2011-01-10 18:49:44 EST ./ drwxr-xr-x 15 root wheel 1.0K 2011-01-10 18:49:37 EST ../ srw-rw---- 1 root wheel 0B 2011-01-10 18:49:37 EST auth- client= srw------- 1 vmail vmail 0B 2011-01-10 18:49:37 EST auth- master= srw------- 1 root wheel 0B 2011-01-10 18:49:37 EST auth- worker.34781= srwxrwxrwx 1 root wheel 0B 2011-01-10 18:49:37 EST dict- server= lrwx------ 1 root wheel 27B 2011-01-10 18:49:37 EST dovecot.conf@ -> /usr/local/etc/dovecot.conf drwxr-x--- 2 root dovecot 512B 2011-01-10 18:49:37 EST login/ -rw------- 1 root wheel 6B 2011-01-10 18:49:37 EST
master.pidThis is the log file output, updated every second (snippet)
Jan 10 18:42:11 dovecot: Info: Dovecot v1.2.16 starting up Jan 10 18:42:11 dovecot: Error: child 34517 (auth-worker) killed with signal 11 (core not dumped) Jan 10 18:42:11 dovecot: Error: child 34521 (auth-worker) killed with signal 11 (core not dumped)
I have tried deleting and rebuilding dovecot without success. I am
at a lose to figure out what the problem is.
What version of mysql were you at before?
Do your mysql logs reveal anything?
Have you turned on mysql query logging?
Can you run the /usr/local/etc/dovecot-sql.conf queries in a mysql
client successfully?
-- Brad
On Tue, Jan 11, 2011 at 3:54 AM, Bradley Giesbrecht < bradley.giesbrecht@gmail.com> wrote:
On Jan 10, 2011, at 4:19 PM, Jerry wrote:
I just updated MySQL to Server version: 5.5.8 on my FreeBSD-8.2 system.
Now Dovecot refuses to run. Prior to this, dovecot had been running for several years without a problem.
Please recompile Dovecot again so that it re-links with the MySQL library. This is a known problem on FreeBSD with the upgrade from MySQL 5.5.7 -> 5.5.8. I believe the port maintainer has also incorporated a fix into the FreeBSD ports.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223
Damn!!
On Tue, Jan 11, 2011 at 2:44 AM, Odhiambo Washington <odhiambo@gmail.com> wrote:
On Tue, Jan 11, 2011 at 3:54 AM, Bradley Giesbrecht < bradley.giesbrecht@gmail.com> wrote:
On Jan 10, 2011, at 4:19 PM, Jerry wrote:
I just updated MySQL to Server version: 5.5.8 on my FreeBSD-8.2 system.
Now Dovecot refuses to run. Prior to this, dovecot had been running for several years without a problem.
Please recompile Dovecot again so that it re-links with the MySQL library. This is a known problem on FreeBSD with the upgrade from MySQL 5.5.7 -> 5.5.8. I believe the port maintainer has also incorporated a fix into the FreeBSD ports.
I all ready did that twice. I completely removed Dovecot before reinstalling it the second time. The prolem still exists. In addition, I am using th version of MySQL that the "port maintainer" supposed fixed. I guess I will have no choice but to return to the older MySQL version. I would be interrested todiscoverif this problem is isolated strictly to FreeBSD + MySQL 5.5.8 however.
-- Jerry
Tell us please, did you tried to rebuild Dovecot with 5.5.8 or with 5.5.8_1 version of MySQL client? I hope that in 5.5.8_1 this bug must fixed already.
2011/1/11 Jerry <dovecot.user@seibercom.net>
On Tue, Jan 11, 2011 at 3:54 AM, Bradley Giesbrecht < bradley.giesbrecht@gmail.com> wrote:
On Jan 10, 2011, at 4:19 PM, Jerry wrote:
I just updated MySQL to Server version: 5.5.8 on my FreeBSD-8.2 system.
Now Dovecot refuses to run. Prior to this, dovecot had been running for several years without a problem.
Please recompile Dovecot again so that it re-links with the MySQL
On Tue, Jan 11, 2011 at 2:44 AM, Odhiambo Washington <odhiambo@gmail.com> wrote: library.
This is a known problem on FreeBSD with the upgrade from MySQL 5.5.7 -> 5.5.8. I believe the port maintainer has also incorporated a fix into the FreeBSD ports.
I all ready did that twice. I completely removed Dovecot before reinstalling it the second time. The prolem still exists. In addition, I am using th version of MySQL that the "port maintainer" supposed fixed. I guess I will have no choice but to return to the older MySQL version. I would be interrested todiscoverif this problem is isolated strictly to FreeBSD + MySQL 5.5.8 however.
-- Jerry
-- Best regards, Maxim V. Kostikov ICQ #115377
Thank you! So it will be better to use 5.5.7 waiting for bugfix.
2011/1/11 Jerry <dovecot.user@seibercom.net>
On Tue, Jan 11, 2011 at 8:47 AM, Maxim Kostikov <max.kostikov@gmail.com> wrote:
Tell us please, did you tried to rebuild Dovecot with 5.5.8 or with 5.5.8_1 version of MySQL client? I hope that in 5.5.8_1 this bug must fixed already.
The latter (5.5.8_1).
-- Jerry
-- Best regards, Maxim V. Kostikov ICQ #115377
On Mon, Jan 10, 2011 at 7:54 PM, Bradley Giesbrecht <bradley.giesbrecht@gmail.com> wrote:
What version of mysql were you at before?
MySQL 5.7.x
Do your mysql logs reveal anything?
No
Have you turned on mysql query logging?
No
Can you run the /usr/local/etc/dovecot-sql.conf queries in a mysql client successfully?
I can manually run MySQL with the queries and they work OK. I will check further into this though.
-- Jerry
The problem is in new buggy MySQL client. I wrote to this list before about it. Roll back to previous version 5.5.7 for a while (server may stills 5.5.8).
Maxim
11.01.2011 2:19 пользователь "Jerry" <dovecot.user@seibercom.net> написал:
I just updated MySQL to Server version: 5.5.8 on my FreeBSD-8.2 system. Now Dovecot refuses to run. Prior to this, dovecot had been running for
several
years without a problem.
This is the output of "dovecot -n"
# 1.2.16: /usr/local/etc/dovecot.conf # OS: FreeBSD 8.2-PRERELEASE amd64 ufs log_path: /var/log/dovecot.log login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_privileged_group: mail mail_location: maildir:/var/mail/vhost/seibercom.net/gerard mail_plugins: expire imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep lda: postmaster_address: postmaster@seibercom.net mail_plugins: sieve sieve_global_path: /usr/local/etc/dovecot/sieve/gerard.sieve sendmail_path: /usr/sbin/sendmail auth default: mechanisms: plain login digest-md5 cram-md5 username_format: %Lu verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: expire: Trash 2 Spam/* 2 expire_dict: proxy::expire dict: expire: mysql:/usr/local/etc/dovecot-dict-expire.conf
The /var/run/dovecot directory looks like this:
drwxr-xr-x 3 root wheel 512B 2011-01-10 18:49:44 EST ./ drwxr-xr-x 15 root wheel 1.0K 2011-01-10 18:49:37 EST ../ srw-rw---- 1 root wheel 0B 2011-01-10 18:49:37 EST auth-client= srw------- 1 vmail vmail 0B 2011-01-10 18:49:37 EST auth-master= srw------- 1 root wheel 0B 2011-01-10 18:49:37 EST auth-worker.34781= srwxrwxrwx 1 root wheel 0B 2011-01-10 18:49:37 EST dict-server= lrwx------ 1 root wheel 27B 2011-01-10 18:49:37 EST dovecot.conf@ -> /usr/local/etc/dovecot.conf drwxr-x--- 2 root dovecot 512B 2011-01-10 18:49:37 EST login/ -rw------- 1 root wheel 6B 2011-01-10 18:49:37 EST master.pid
This is the log file output, updated every second (snippet)
Jan 10 18:42:11 dovecot: Info: Dovecot v1.2.16 starting up Jan 10 18:42:11 dovecot: Error: child 34517 (auth-worker) killed with signal 11 (core not dumped) Jan 10 18:42:11 dovecot: Error: child 34521 (auth-worker) killed with signal 11 (core not dumped)
I have tried deleting and rebuilding dovecot without success. I am at a lose to figure out what the problem is.
-- Jerry ✌ Dovecot.user@seibercom.net
Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header.
I would rather say that a desire to drive fast sports cars is what sets man apart from the animals.
On Tue, Jan 11, 2011 at 5:28 AM, Maxim Kostikov <max.kostikov@gmail.com> wrote:
The problem is in new buggy MySQL client. I wrote to this list before about it. Roll back to previous version 5.5.7 for a while (server may stills 5.5.8).
I will probably have no choice. I was wondering if Timo had any ideas on this however.
-- Jerry
Well, I believe that this is not Dovecot fault so all questions and complains must be addressed to MySQL developers.
2011/1/11 Jerry <dovecot.user@seibercom.net>
On Tue, Jan 11, 2011 at 5:28 AM, Maxim Kostikov <max.kostikov@gmail.com> wrote:
The problem is in new buggy MySQL client. I wrote to this list before about it. Roll back to previous version 5.5.7 for a while (server may stills 5.5.8).
I will probably have no choice. I was wondering if Timo had any ideas on this however.
-- Jerry
-- Best regards, Maxim V. Kostikov ICQ #115377
On Tue, Jan 11, 2011 at 8:44 AM, Maxim Kostikov <max.kostikov@gmail.com> wrote:
Well, I believe that this is not Dovecot fault so all questions and complains must be addressed to MySQL developers.
I would question if that is factually correct. I did have a problem with Postfix; however, after rebuilding Postfix it started working correctly. For some unknown reason, that is not the case with Dovecot. Therefore, until I have seen proof confirming that it is a "MySQL 5.5.8+" problem, I will continue to investigate why only Dovecot seems to be exhibiting this behavior. I do intend to check on the MySQL forum though for a possible solution.
By the way, I have KDE apps that are working fine with this newer version of MySQL also.
-- Jerry
I then turned on some of the logging function in Dovecot and restarted it. I then had Postfix roguery some messages. This is a snippet of the dovecot log. Sorry about the line wrap. I am not using my regular MUA at present.
Jan 11 10:33:19 deliver(root@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(root@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(root@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(root@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(root@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 deliver(root@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 deliver(root@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 deliver(root@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 auth(default): Info: master in: USER 1 root@seibercom.net service=deliver Jan 11 10:33:19 auth(default): Info: master in: USER 1 root@seibercom.net service=deliver Jan 11 10:33:19 auth(default): Info: master in: USER 1 root@seibercom.net service=deliver Jan 11 10:33:19 auth(default): Info: master in: USER 1 root@seibercom.net service=deliver Jan 11 10:33:19 deliver(root@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(root@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 auth(default): Info: master in: USER 1 root@seibercom.net service=deliver Jan 11 10:33:19 dovecot: Error: child 85589 (auth-worker) killed with signal 11 (core not dumped) Jan 11 10:33:19 dovecot: Error: child 85588 (auth-worker) killed with signal 11 (core not dumped) Jan 11 10:33:19 dovecot: Error: child 85580 (auth-worker) killed with signal 11 (core not dumped) Jan 11 10:33:19 deliver(root@seibercom.net): Error: userdb lookup(root@seibercom.net) failed: Internal failure Jan 11 10:33:19 deliver(root@seibercom.net): Error: userdb lookup(root@seibercom.net) failed: Internal failure Jan 11 10:33:19 deliver(root@seibercom.net): Error: userdb lookup(root@seibercom.net) failed: Internal failure Jan 11 10:33:19 deliver(root@seibercom.net): Error: userdb lookup(root@seibercom.net) failed: Internal failure Jan 11 10:33:19 auth(default): Error: worker-server(root@seibercom.net): Aborted: Worker process died unexpectedly Jan 11 10:33:19 auth(default): Info: master out: FAIL 1 Jan 11 10:33:19 auth(default): Error: worker-server(root@seibercom.net): Aborted: Worker process died unexpectedly Jan 11 10:33:19 auth(default): Info: master out: FAIL 1 Jan 11 10:33:19 auth(default): Error: worker-server(root@seibercom.net): Aborted: Worker process died unexpectedly Jan 11 10:33:19 auth(default): Info: master out: FAIL 1 Jan 11 10:33:19 auth(default): Error: worker-server(root@seibercom.net): Aborted: Worker process died unexpectedly Jan 11 10:33:19 auth(default): Info: master out: FAIL 1 Jan 11 10:33:19 dovecot: Error: child 85596 (auth-worker) killed with signal 11 (core not dumped)
I doubt that this will be of any value; however, it cannot hurt to submit it.
-- Jerry
Jerry schreef:
I then turned on some of the logging function in Dovecot and restarted it. I then had Postfix roguery some messages. This is a snippet of the dovecot log. Sorry about the line wrap. I am not using my regular MUA at present.
Jan 11 10:33:19 deliver(root@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(root@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(root@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(root@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(root@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 deliver(root@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 deliver(root@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 deliver(root@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 auth(default): Info: master in: USER 1 root@seibercom.net service=deliver Jan 11 10:33:19 auth(default): Info: master in: USER 1 root@seibercom.net service=deliver Jan 11 10:33:19 auth(default): Info: master in: USER 1 root@seibercom.net service=deliver Jan 11 10:33:19 auth(default): Info: master in: USER 1 root@seibercom.net service=deliver Jan 11 10:33:19 deliver(root@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(root@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 auth(default): Info: master in: USER 1 root@seibercom.net service=deliver Jan 11 10:33:19 dovecot: Error: child 85589 (auth-worker) killed with signal 11 (core not dumped) Jan 11 10:33:19 dovecot: Error: child 85588 (auth-worker) killed with signal 11 (core not dumped) Jan 11 10:33:19 dovecot: Error: child 85580 (auth-worker) killed with signal 11 (core not dumped) Jan 11 10:33:19 deliver(root@seibercom.net): Error: userdb lookup(root@seibercom.net) failed: Internal failure Jan 11 10:33:19 deliver(root@seibercom.net): Error: userdb lookup(root@seibercom.net) failed: Internal failure Jan 11 10:33:19 deliver(root@seibercom.net): Error: userdb lookup(root@seibercom.net) failed: Internal failure Jan 11 10:33:19 deliver(root@seibercom.net): Error: userdb lookup(root@seibercom.net) failed: Internal failure Jan 11 10:33:19 auth(default): Error: worker-server(root@seibercom.net): Aborted: Worker process died unexpectedly Jan 11 10:33:19 auth(default): Info: master out: FAIL 1 Jan 11 10:33:19 auth(default): Error: worker-server(root@seibercom.net): Aborted: Worker process died unexpectedly Jan 11 10:33:19 auth(default): Info: master out: FAIL 1 Jan 11 10:33:19 auth(default): Error: worker-server(root@seibercom.net): Aborted: Worker process died unexpectedly Jan 11 10:33:19 auth(default): Info: master out: FAIL 1 Jan 11 10:33:19 auth(default): Error: worker-server(root@seibercom.net): Aborted: Worker process died unexpectedly Jan 11 10:33:19 auth(default): Info: master out: FAIL 1 Jan 11 10:33:19 dovecot: Error: child 85596 (auth-worker) killed with signal 11 (core not dumped)
I doubt that this will be of any value; however, it cannot hurt to submit it.
just hit the ports tree mysql55-client 5.5.8_2 With the following comment.
Remove any attempts to create a libmysqlclient not linked to a threading library. Restore previous libraries location.
These two changes should fix most of the reported errors.
I think you can try again.
regards, Johan Hendriks
On Tue, Jan 11, 2011 at 4:53 PM, Johan Hendriks <joh.hendriks@gmail.com> wrote:
just hit the ports tree mysql55-client 5.5.8_2 With the following comment.
Remove any attempts to create a libmysqlclient not linked to a threading library. Restore previous libraries location.
These two changes should fix most of the reported errors.
Well, I am off to try it. I will report back later if successful.
-- Jerry
On 11.1.2011, at 15.01, Jerry wrote:
On Tue, Jan 11, 2011 at 5:28 AM, Maxim Kostikov <max.kostikov@gmail.com> wrote:
The problem is in new buggy MySQL client. I wrote to this list before about it. Roll back to previous version 5.5.7 for a while (server may stills 5.5.8).
I will probably have no choice. I was wondering if Timo had any ideas on this however.
I might if someone can produce a gdb backtrace of the crash.
See it here from my previous post http://dovecot.org/pipermail/dovecot/2011-January/056217.html
2011/1/11 Timo Sirainen <tss@iki.fi>
On 11.1.2011, at 15.01, Jerry wrote:
On Tue, Jan 11, 2011 at 5:28 AM, Maxim Kostikov <max.kostikov@gmail.com> wrote:
The problem is in new buggy MySQL client. I wrote to this list before about it. Roll back to previous version 5.5.7 for a while (server may stills 5.5.8).
I will probably have no choice. I was wondering if Timo had any ideas on this however.
I might if someone can produce a gdb backtrace of the crash.
-- Best regards, Maxim V. Kostikov ICQ #115377
participants (6)
-
Bradley Giesbrecht
-
Jerry
-
Johan Hendriks
-
Maxim Kostikov
-
Odhiambo Washington
-
Timo Sirainen