Ad Widget

Collapse

1.4.1 & MySQL 3.23 problems

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Gerco
    Junior Member
    • Nov 2006
    • 22

    #1

    1.4.1 & MySQL 3.23 problems

    Hi All,

    I had Zabbix 1.1.4 installed with MySQL 3.23.58 and it worked just fine. Now I upgraded to Zabbix 1.4.1 and ran into some problems. I did a fresh install, since 1.1.4 was just for testing.

    First the schema wouldn't import, that was fixed with a tip from this forum (replacing 'serial' with 'BIGINT NOT_NULL UNIQUE ... etc').

    The second problem I found was that the guest user wasn't found. It was present in the database, the query to find it used the 'div' operator, which apparantly doesn't exist in MySQL 3.23.58. I changed that to '/' and it still didn't work.

    Now I still can't log in, because there is now a problem with the nodeid. This query doesn't give a result:
    mysql> select u.userid,(u.userid/100000000000000),u.alias,u.name,u.surname,u.url,u. refresh from users u where u.alias='admin' and u.passwd='d41d8cd98f00b204e9800998ecf8427e' and (u.userid / 100000000000000)=0.00;
    Empty set (0.01 sec)
    But this one does!:
    mysql> select u.userid,(u.userid/100000000000000),u.alias,u.name,u.surname,u.url,u. refresh from users u where u.alias='admin' and u.passwd='d41d8cd98f00b204e9800998ecf8427e' and (u.userid / 100000000000000)<0.01;
    +--------+----------------------------+-------+--------+---------------+-----+---------+
    | userid | (u.userid/100000000000000) | alias | name | surname | url | refresh |
    +--------+----------------------------+-------+--------+---------------+-----+---------+
    | 1 | 0.00 | Admin | Zabbix | Administrator | | 30 |
    +--------+----------------------------+-------+--------+---------------+-----+---------+
    1 row in set (0.00 sec)
    Apparently, MySQL 3.23 is a little more picky about rounding down floating point values or refuses to compare an integer to a float altogether, I don't know.

    Just changing this query like this won't work, because then a multi-node installation wouldn't work as expected.
Working...