Results 1 to 4 of 4

Thread: mysql log error: [Warning] option 'max_join_size': unsigned value xxx adjusted to yyy

Hybrid View

  1. #1
    Join Date
    Dec 2008
    Location
    Perak, Malaysia
    Posts
    21
    Rep Power
    6

    Default mysql log error: [Warning] option 'max_join_size': unsigned value xxx adjusted to yyy

    My OS - CentOS5.3 32bit
    3 machine - LDAP, mailbox, smtp

    Before, i use zcs-5.0.11_GA_2695.RHEL5 and upgrade to zcs-5.0.18_GA_3011.RHEL5. I found out in mysql_error.log & logger_mysql_error.log got warning messege.

    mysql_error.log (before upgrade)
    ========================

    090711 20:18:58 mysqld started
    090711 20:18:58 InnoDB: Started; log sequence number 0 2232850312
    090711 20:18:58 [Note] /opt/zimbra/mysql/libexec/mysqld: ready for connections.
    Version: '5.0.51a-log' socket: '/opt/zimbra/db/mysql.sock' port: 7306 Source distribution
    090711 20:21:36 [Note] /opt/zimbra/mysql/libexec/mysqld: Normal shutdown

    090711 20:21:36 InnoDB: Starting shutdown...
    090711 20:21:38 InnoDB: Shutdown completed; log sequence number 0 2232850332
    090711 20:21:38 [Note] /opt/zimbra/mysql/libexec/mysqld: Shutdown complete

    090711 20:21:38 mysqld ended

    mysql_error.log (after upgrade)
    ========================

    090711 20:26:33 mysqld started
    090711 20:26:33 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
    090711 20:26:33 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
    090711 20:26:34 InnoDB: Started; log sequence number 0 2232850332
    090711 20:26:34 [Note] /opt/zimbra/mysql/libexec/mysqld: ready for connections.
    Version: '5.0.67-log' socket: '/opt/zimbra/db/mysql.sock' port: 7306 Source distribution
    090711 20:26:59 [Note] /opt/zimbra/mysql/libexec/mysqld: Normal shutdown

    090711 20:26:59 InnoDB: Starting shutdown...
    090711 20:27:01 InnoDB: Shutdown completed; log sequence number 0 2232850589
    090711 20:27:01 [Note] /opt/zimbra/mysql/libexec/mysqld: Shutdown complete

    090711 20:27:01 mysqld ended

    090711 20:30:34 mysqld started
    090711 20:30:34 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
    090711 20:30:34 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
    090711 20:30:35 InnoDB: Started; log sequence number 0 2232850589
    090711 20:30:35 [Note] /opt/zimbra/mysql/libexec/mysqld: ready for connections.
    Version: '5.0.67-log' socket: '/opt/zimbra/db/mysql.sock' port: 7306 Source distribution
    090711 20:49:34 [Note] /opt/zimbra/mysql/libexec/mysqld: Normal shutdown

    090711 20:49:34 InnoDB: Starting shutdown...
    090711 20:49:36 InnoDB: Shutdown completed; log sequence number 0 2233251228
    090711 20:49:36 [Note] /opt/zimbra/mysql/libexec/mysqld: Shutdown complete

    090711 20:49:36 mysqld ended

    logger_mysql_error.log (before upgrade)
    ========================
    Starting mysqld daemon with databases from /opt/zimbra/logger/db/data
    090711 20:15:31 mysqld started
    090711 20:15:32 InnoDB: Started; log sequence number 0 43655
    090711 20:15:32 [Note] /opt/zimbra/logger/mysql/libexec/mysqld: ready for connections.
    Version: '5.0.51a-log' socket: '/opt/zimbra/logger/db/mysql.sock' port: 7307 Source distribution
    090711 20:17:19 [Note] /opt/zimbra/logger/mysql/libexec/mysqld: Normal shutdown

    090711 20:17:19 InnoDB: Starting shutdown...
    090711 20:17:20 InnoDB: Shutdown completed; log sequence number 0 43655
    090711 20:17:20 [Note] /opt/zimbra/logger/mysql/libexec/mysqld: Shutdown complete

    STOPPING server from pid file /opt/zimbra/logger/db/mysql.pid
    090711 20:17:20 mysqld ended
    090711 20:17:20 mysqld ended

    logger_mysql_error.log (after upgrade)
    ========================
    Starting mysqld daemon with databases from /opt/zimbra/logger/db/data
    090711 20:26:46 mysqld started
    090711 20:26:46 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
    090711 20:26:46 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
    090711 20:26:46 InnoDB: Started; log sequence number 0 43655
    090711 20:26:46 [Note] /opt/zimbra/logger/mysql/libexec/mysqld: ready for connections.
    Version: '5.0.67-log' socket: '/opt/zimbra/logger/db/mysql.sock' port: 7307 Source distribution
    090711 20:27:21 [Note] /opt/zimbra/logger/mysql/libexec/mysqld: Normal shutdown

    090711 20:27:21 InnoDB: Starting shutdown...
    090711 20:27:21 InnoDB: Shutdown completed; log sequence number 0 43655
    090711 20:27:21 [Note] /opt/zimbra/logger/mysql/libexec/mysqld: Shutdown complete

    STOPPING server from pid file /opt/zimbra/logger/db/mysql.pid
    090711 20:27:21 mysqld ended
    090711 20:27:21 mysqld ended


    Starting mysqld daemon with databases from /opt/zimbra/logger/db/data
    090711 20:30:33 mysqld started
    090711 20:30:33 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
    090711 20:30:33 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
    090711 20:30:33 InnoDB: Started; log sequence number 0 43655
    090711 20:30:33 [Note] /opt/zimbra/logger/mysql/libexec/mysqld: ready for connections.
    Version: '5.0.67-log' socket: '/opt/zimbra/logger/db/mysql.sock' port: 7307 Source distribution
    090711 20:49:38 [Note] /opt/zimbra/logger/mysql/libexec/mysqld: Normal shutdown

    090711 20:49:40 InnoDB: Starting shutdown...
    090711 20:49:41 InnoDB: Shutdown completed; log sequence number 0 43655
    090711 20:49:41 [Note] /opt/zimbra/logger/mysql/libexec/mysqld: Shutdown complete

    STOPPING server from pid file /opt/zimbra/logger/db/mysql.pid
    090711 20:49:41 mysqld ended
    090711 20:49:41 mysqld ended



    sqlMigration.log
    ============
    Sat Jul 11 20:26:44 2009: SELECT value FROM config WHERE name = 'db.version'
    Sat Jul 11 20:26:45 2009: 53
    Sat Jul 11 20:26:56 2009: SELECT value FROM config WHERE name = 'db.version'
    Sat Jul 11 20:26:57 2009: 5
    Sat Jul 11 20:26:57 2009: SELECT value FROM config WHERE name = 'redolog.version'
    Sat Jul 11 20:26:57 2009: 1.23
    Sat Jul 11 20:26:58 2009: SELECT value FROM config WHERE name = 'redolog.version'
    Sat Jul 11 20:26:58 2009: 1.23
    Sat Jul 11 20:26:58 2009: Verified redolog version 1.23.
    Sat Jul 11 20:26:58 2009: Updating Redolog schema version from 1.23 to 1.24.
    Sat Jul 11 20:26:58 2009: UPDATE zimbra.config SET value = '1.24' WHERE name = 'redolog.version';

    Sat Jul 11 20:27:14 2009: SELECT value FROM config WHERE name = 'db.version'
    Sat Jul 11 20:27:14 2009: 5
    Sat Jul 11 20:27:14 2009: Verified schema version 5.
    Sat Jul 11 20:27:14 2009: Modifying postfix_qid size
    Sat Jul 11 20:27:14 2009: alter table raw_logs modify postfix_qid VARCHAR(25);
    alter table mta modify qid VARCHAR(25);

    Sat Jul 11 20:27:19 2009: SELECT value FROM config WHERE name = 'db.version'
    Sat Jul 11 20:27:20 2009: 5
    Sat Jul 11 20:27:20 2009: Verified schema version 5.
    Sat Jul 11 20:27:20 2009: Updating logger DB schema version from 5 to 6.
    Sat Jul 11 20:27:20 2009: UPDATE zimbra_logger.config SET value = '6' WHERE name = 'db.version';

    ================================================== ========

    what is this mean?
    090711 20:30:33 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295

    What is the problem?

    FYI, during the upgrading i skip doing zmdbintegrityreport. But after upgrade, i run /opt/zimbra/libexec/zmdbintegrityreport -m and /opt/zimbra/libexec/zmdbintegrityreport -l. No error or warning message found.

  2. #2
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    25

    Default

    Welcome to the forums

    Nothing really to worry about as it is only a warning. If you wish you could go into MySQL and then under each of the databases run a check against each of the tables and repair where necessary. Alternatively you can do the following
    Code:
    su - zimbra
    zmlocalconfig -s | grep zimbra_mysql_password | awk '{ print $3 }'
    _then using that password you can run_
    mysqlcheck --defaults-file=/opt/zimbra/conf/my.cnf --socket=/opt/zimbra/db/mysql.sock -u zimbra -p zimbra

  3. #3
    Join Date
    Dec 2008
    Location
    Perak, Malaysia
    Posts
    21
    Rep Power
    6

    Default

    Quote Originally Posted by uxbod View Post
    Welcome to the forums

    Nothing really to worry about as it is only a warning. If you wish you could go into MySQL and then under each of the databases run a check against each of the tables and repair where necessary. Alternatively you can do the following
    Code:
    su - zimbra
    zmlocalconfig -s | grep zimbra_mysql_password | awk '{ print $3 }'
    _then using that password you can run_
    mysqlcheck --defaults-file=/opt/zimbra/conf/my.cnf --socket=/opt/zimbra/db/mysql.sock -u zimbra -p zimbra
    [zimbra@mbs1 root]$ /opt/zimbra/mysql/bin/mysqlcheck --defaults-file=/opt/zimbra/conf/my.cnf --socket=/opt/zimbra/db/mysql.sock -u zimbra -p zimbra
    Enter password:
    zimbra.config OK
    zimbra.current_volumes OK
    zimbra.deleted_account OK
    zimbra.jiveExtComponentConf OK
    zimbra.jiveGroupProp OK
    zimbra.jiveGroupUser OK
    zimbra.jiveID OK
    zimbra.jiveOffline OK
    zimbra.jivePrivacyList OK
    zimbra.jivePrivate OK
    zimbra.jiveProperty OK
    zimbra.jiveRemoteServerConf OK
    zimbra.jiveRoster OK
    zimbra.jiveRosterGroups OK
    zimbra.jiveSASLAuthorized OK
    zimbra.jiveUserProp OK
    zimbra.jiveVCard OK
    zimbra.jiveVersion OK
    zimbra.mailbox OK
    zimbra.mailbox_metadata OK
    zimbra.mucAffiliation OK
    zimbra.mucConversationLog OK
    zimbra.mucMember OK
    zimbra.mucRoom OK
    zimbra.mucRoomProp OK
    zimbra.out_of_office OK
    zimbra.scheduled_task OK
    zimbra.service_status OK
    zimbra.table_maintenance OK
    zimbra.volume OK

    How to check database? what the command?

  4. #4
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    25

    Default

    That has just checked the Zimbra database. You will need to go into mysql and type show databases to get the list of the mailbox ones aswell.

Similar Threads

  1. Errors installing Outlook Connector
    By Tim G in forum Zimbra Connector for Outlook
    Replies: 57
    Last Post: 05-05-2011, 03:27 PM
  2. Zimbra fails after working for 2 weeks
    By Linsys in forum Administrators
    Replies: 10
    Last Post: 10-07-2008, 01:42 AM
  3. Error Installing Outlook Connector
    By DanO in forum Zimbra Connector for Outlook
    Replies: 17
    Last Post: 08-28-2007, 10:35 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •