Problems after fresh install 1.8

[ocean]

Hello,
I just completed compiling and installing the current 1.8.3 version of zabbix, using RHEL 5.5 and mysql 5.0.77
I ran the create/schema/mysql.sql and create/data/data.sql and create/data/images_mysql.sql, which seems to go just fine
Starting the frontend, I can connect to the db and finish installation, but then there's a lot of warnings:

# mysql_fetch_array(): supplied argument is not a valid MySQL result resource[/etc/zabbix/db.inc.php:411]
# Error in query [select n.nodeid,min(r.permission) as permission, g.userid from nodes n left join rights r on r.id=n.nodeid and r.type=0 left join users_groups g on r.groupid=g.usrgrpid and g.userid=2 where n.nodeid in (0) group by n.nodeid, g.userid order by nodeid desc, userid desc, permission desc] [Unknown column 'r.type' in 'on clause']

The code in db.inc.php at line 411 is

case "MYSQL":
$result = mysql_fetch_array($cursor);
break;

There are actually various threads on this, at this forum, however those seem to be for previous versions, and then still there is not a solution.
If you have an idea how to solve this, please let me know!
Thanks for reading anyway,
Alex

[ocean]

For example, in this thread sergio.cricca correctly finds that there is no column type in the table rights at all.

So yes, the error message [Unknown column 'r.type' in 'on clause] is correct

But if this was the case in 1.6.1, why do I have these exact same errors in 1.8.3?

[ocean]

Fixed

Okay, still don't know why this is not fixed in this release, or am I the only one running in this problem??

Anyway, the "type" column can be found in the "users" table, so I edit perm.inc.php and changed line 170 to look like this:

' left join (rights r, users u) on r.id=g.groupid and u.type='.RESOURCE_TYPE_GROUP.

and line 334 to look like this:

' from nodes n left join (rights r, users u) on r.id=n.nodeid and u.type= '.RESOURCE_TYPE_NODE.

Maybe this is useful to someone else..

[ocean]

My bad..

.. this is what you get, keeping an old partial install somewhere in the system.

My apologies! Cleaning out every trace of this previous version, and reinstalling the 1.8.3 worked like a charm!