Issues found so far in 1.6

[xs-]

Long post warning!

I have filed tickets for these issues, posting to inform you all about these.
Severity varies according to issue of course.

Export template nodeX, import on nodeY

On nodeY, configuration -> hosts -> templates -> imported template
The imported template shows IPMI information in the properties, other templates do not.

- Which of the two is normal?
- Can i use this template without consequences?
- How do i fix the 'wrong version' template?

I assume ofcourse that this is a bug, and maps / screens are supposed to support items/triggers from multiple nodes.

n 1.4.6 we created several maps and screens which hold data from multiple nodes (this was done on the master node of course).

In 1.6 they can be viewed (when 'show with subnodes' is selected, which is fine) in the monitoring menu. In the configuration menu however, these maps and screens do not show. I assume this is because the selection method is the same as the monitoring menu (but configuration menu does not have the 'show with subnodes' option, as it should not have).

Can you make it so, that when you are in the configuration menu, and the 'main' node (the node the webinterface is actually using), the selection criteria for maps, screens, etc are less strict? Perhaps add some node selection boxes in the item selection of the screen/map configuration pages.
-----------------------------
The reason why i selected a critical bug, is this;
viewing the described maps / screens is possible, so no biggie, because this keeps working.

But because of the new proxy support in 1.6, i (and i assume other ppl to) an switching several DM nodes to proxies. Because of this i need to change these maps.


Oh, i suspect, the same issue is happening in config -> actions. I am missing some trigger based actions in the view, which i now can't modify.

Distributed monitoring

Items from nodes do not have their 'last check' updated. When looking in latest data for a host monitored by a DM node, the date/time is shown from before the upgrade to 1.6.
Dont know if this might be a bug in the gui, i suspect the server tho.
----------------------------------
Update on issue.

Lastest values are not shown in the GUI (monitoring -> latest values).

Values are not shown for new hosts.
Old values are shown for existing hosts (from before migration to 1.6).

When clicking the graph/history link, data is available.
[ Show » ]
Tom Duijf (xs-) - 23/Sep/08 11:31 AM Update on issue. Lastest values are not shown in the GUI (monitoring -> latest values). Values are not shown for new hosts. Old values are shown for existing hosts (from before migration to 1.6). When clicking the graph/history link, data is available.

make distclean fails / gives errors for some targets.

System authentication method is configured to use LDAP.
There is a group with the 'GUI Access: Internal' flag configured, but it is not used for creating this user.

Normal user creation (administration -> users)
- No Password field is shown (which is correct because LDAP is used.
- All required fields are filled (except the non-existant password field ofcourse)
User creation fails with the error "ERROR: Password should not be empty"
Apparently, the default password 'zabbix' when non-internal auth is used, is not set.


A small note on the side (minor issue, if at all)
When, in the above situation, i add the described group, with the 'GUI Access: Internal' flag on, i still get no password fields.
If this is done for an existing user, the password change button is shown, because of this group.
This is separate from the main issue, but it would be nice (if possible) to fix this.

The user tab in the administration menu always states user is not online.
(last login date is updated correctly tho).

Tried logging out and logging in, no effect, status still No.

I saw this in a host configuration screen, perhaps this is also happening in similar selection boxes.

In the host configuration screen, you can select hostgroups using 2 'boxes' with 2 (move left, move right) buttons.
When you move / select hostgroups, they are not sorted in their destination.

Trivial thing, but its more user friendly when they are sorted.

When using template 'hostgroups' (template groups)

confguration->hosts->templates, default group selection is 'all'. When selecting another group, page reloads but selection is still 'all'.

[MrKen]

Originally Posted by ZBX-464
System authentication method is configured to use LDAP.
There is a group with the 'GUI Access: Internal' flag configured, but it is not used for creating this user.

Normal user creation (administration -> users)
- No Password field is shown (which is correct because LDAP is used.
- All required fields are filled (except the non-existant password field ofcourse)
User creation fails with the error "ERROR: Password should not be empty"
Apparently, the default password 'zabbix' when non-internal auth is used, is not set.


Has this been fixed yet?

I recently upgraded 1.6 to 1.6.1 and I still receive the above error when adding a new user.

To add a new user, I have to go to the authentication tab and change the default authentication to Internal. Then when I go back to the Create User form, there are fields to enter the password. Then, go back and change the default authentication back to ldap.

Regards

MrKen

[xs-]

the problem you describe should be fixed.
Default passwords for non-internal authenticated users is automatically set to 'zabbix' (so the db field restriction doesnt complain).

AFAIK 1.6.1 did not break this.

[ataylo13]

Tagging along on this one. There are a few things here I would like to know when they get fixed.

[MrKen]

ERROR: Password should not be empty

Default authentication is Ldap.

Create User form has no fields to enter a password.

Save new user = ERROR: Password should not be empty


Zabbix 1.6.1

[Aly]

Try to use frontend from pre 1.6.2 from our Nightly build, it contains some fixes related to ldap.

[MrKen]

Try to use frontend from pre 1.6.2 from our Nightly build

Thanks Aly that fixed it.

Also fixed the Users 'Is online?' problem too!