Available in the development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-1220

(1) On a 32-bit system agent fails when doing stat() of the log file in a process_log() function, which results in an item becoming NOTSUPPORTED:

[...]
/tmp/zabbix_agentd.log- 26150:20120515:163247.537 In process_log() filename:'/tmp/big.log' lastlogsize:2110251579
/tmp/zabbix_agentd.log: 26150:20120515:163247.537 cannot stat '/tmp/big.log': [75] Value too large for defined data type
/tmp/zabbix_agentd.log- 26150:20120515:163247.537 Active check [log[/tmp/big.log,foobjcode,,1000,skip]] is not supported. Disabled.
[...]

$ ls -l /tmp/big.log
rw-rr- 1 vl vl 2156040848 May 15 16:32 /tmp/big.log

$ ls -lh /tmp/big.log
rw-rr- 1 vl vl 2.1G May 15 16:32 /tmp/big.log

<Sasha> RESOLVED in r27551.

<dimir> CLOSED

Related issue: ZBX-3151

Successfully tested. Log monitoring is working for files over 2GB on 32-bit systems. Also confirm that this fixes vfs.file.size[] report for files over 2GB (was ZBX_UNSUPPORTED before).

(1) This enables general support for files larger than 2GB on Zabbix side (all components), I suggest this be documented as new 2.0 feature.

<richlv> documented in http://www.zabbix.com/documentation/2.0/manual/introduction/whatsnew200 -> RESOLVED
<Sasha> CLOSED

(2) Should be documented DB upgrade patches from 2.0.0rc4 to 2.0.0rc5 in the release notes.

IBM DB2:
ALTER TABLE items ALTER COLUMN lastlogsize SET DATA TYPE bigint
REORG TABLE items

MySQL:
ALTER TABLE items MODIFY lastlogsize bigint unsigned DEFAULT '0' NOT NULL;

Oracle:
ALTER TABLE items MODIFY lastlogsize number(20);

PostgreSQL:
ALTER TABLE items ALTER lastlogsize TYPE numeric(20);

<dimir> While at it, could next info also added?

When upgrading from 2.0.0rc2 to 2.0.0rc3, if proxy is used and proxy uses MySQL:
ALTER TABLE proxy_history MODIFY value longtext NOT NULL;

<Sasha> we supports incremental patches only from version 2.0.0rc4
<Sasha> CLOSED patches will be published in the release notes

Available in version pre-2.0.0 r27570.

Reopening because of regression. After this fix Zabbix will not compile on Solaris (SPARC) anymore.

(3) Disable large file support on 32-bit Solaris.

On a 32-bit Solaris large file support is incompatible with procfs and swapctl. There is a way to do that though by using transitional compilation environment but this has to wait at least till 2.0 is out. See lfcompile64(5) for details.

RESOLVED in svn://svn.zabbix.com/branches/dev/ZBXNEXT-1220

<Sasha> CLOSED
I removed the message on support of large files. The call of AC_SYS_LARGEFILE doesn't guarantee it.

(4) document "(3)"

<dimir>
http://www.zabbix.com/documentation/2.0/manual/appendix/items/large_file_support (new page)
http://www.zabbix.com/documentation/2.0/manual/introduction/whatsnew200#monitoring_of_files_larger_than_2gb (add link to lfs)
http://www.zabbix.com/documentation/2.0/manual/config/items/itemtypes/log_items#overview (add note about lfs)

RESOLVED

<martins-v>CLOSED

Available in version pre-2.0.0 r27637.

to clarify, this is about returning "whatever the agent would use as the 'Hostname' for active checks"

Available in the development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-1188

(1) updated documentation:
http://www.zabbix.com/documentation/1.8/manual/config/items?&#zabbix_agent
http://www.zabbix.com/documentation/1.8/manual/config/items?&#supported_by_platform
http://www.zabbix.com/documentation/2.0/manual/config/items/itemtypes/zabbix_agent#supported_item_keys
http://www.zabbix.com/documentation/2.0/manual/appendix/items/supported_by_platform

Please review.

<martins-v>ok, with small grammar fixes here:
http://www.zabbix.com/documentation/1.8/manual/config/items?&#zabbix_agent
http://www.zabbix.com/documentation/2.0/manual/config/items/itemtypes/zabbix_agent#supported_item_keys

<Sasha> Thanks! CLOSED

(2) Error compiling server:

$ make >/dev/null
../../src/libs/zbxsysinfo/common/libcommonsysinfo.a(common.o): In function `AGENT_HOSTNAME':
common.c.text+0x18b): undefined reference to `CONFIG_HOSTNAME'
collect2: ld returned 1 exit status
make[1]: *** [zabbix_server] Error 1
make: *** [all-recursive] Error 1

<Sasha> RESOLVED in r27184:27186

<dimir> CLOSED

Successfully tested. Please review my small changes in r27189.

<Sasha> CLOSED

Available in versions pre-1.8.13rc1 r27196 and pre-2.0.0rc4 r27198.

We forgot to include the new key to item selection helper.
It's reported as a separate issue ZBX-7037.

Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-863 .

(2) Documentation is yet to fix.

<dimir> Updated:

http://www.zabbix.com/documentation/2.0/manual/appendix/macros/supported_by_location

http://www.zabbix.com/documentation/2.0/manual/appendix/api/host
http://www.zabbix.com/documentation/2.0/manual/appendix/api/host#inventory_fields
http://www.zabbix.com/documentation/2.0/manual/appendix/api/host/create
http://www.zabbix.com/documentation/2.0/manual/appendix/api/host/get
http://www.zabbix.com/documentation/2.0/manual/appendix/api/host/massupdate
http://www.zabbix.com/documentation/2.0/manual/appendix/api/host/update

http://www.zabbix.com/documentation/internal/database_2.0/host_inventory
http://www.zabbix.com/documentation/internal/database_2.0/hosts
http://www.zabbix.com/documentation/internal/database_2.0/items

http://www.zabbix.com/documentation/2.0/manual/appendix/api/changes_1.8_-_2.0?&#host
http://www.zabbix.com/documentation/2.0/manual/installation/upgrade_notes

<dimir> RESOLVED
<sasha> fixed http://www.zabbix.com/documentation/2.0/manual/appendix/api/changes_1.8_-_2.0

<dimir> Thanks, CLOSED

Do we need to fix translations within this issue?

<richlv> if that refers to updating translations for changes made, then no

Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-863

(6) Will fix the 2.0 docs to list only those

that are in 1.8 as deprecated.

<dimir> RESOLVED
<sasha> CLOSED

(7) One last thing, add "inventory_link" parameter to API.

<dimir> Tested, it actually works.
<dimir> RESOLVED http://www.zabbix.com/documentation/2.0/manual/appendix/api/item?&#object_details and example at http://www.zabbix.com/documentation/2.0/manual/appendix/api/item/create?&#create_new_item_for_host_with_host_id_10057_to_update_host_inventory_field_os

<dimir> (on behalf of sasha) CLOSED

Fixed in trunk r21072 .

one more potentially missed variable reported as ZBX-4088

One of the possible solutions is to make the agent (always or only in case of empty string) send Zabbix protocol headers. It will be understood by older servers, proxies, and zabbix_get.

Another possible solution is to introduce a special return value, say, ZBX_EMPTY, in addition to ZBX_NOTSUPPORTED and ZBX_ERROR.

The first solution seems to be more preferred, because someday we will have to introduce Zabbix protocol headers into the passive agent protocol anyway.

how would this affect a userparameter command returning empty string ? would that be supported after this change ?
If a UserParameter returns only whitespace an empty string will be send to the server

Available in dev branch: svn://svn.zabbix.com/branches/dev/ZBXNEXT-780

1) Empty strings are now supported as valid values for both passive and active items
2) UserParams returning only whitespace are now treated as returning empty strings (they were NOT_SUPPORTED before)

Available in pre-1.9.5 r19734.

additionally noted here: http://www.zabbix.com/documentation/2.0/manual/introduction/whatsnew200#ability_to_send_empty_strings

(7) [Documentation]
Here and in the documentation nowhere mentioned that ONLY text items (types of information: Character, Log, Text) are allowed to receive empty value.
I think that it must be mentioned at appropriate documentation page(s)

Some phrases like:
"All items (including user parameters and external checks) can return also only whitespace, setting the return value to an empty string"
sounds not very good regarding on fact that actually NOT all items.
REOPENED

<zalex> CLOSED

The notes about empty strings accepted have been modified to say that it applies to textual items:

http://www.zabbix.com/documentation/2.0/manual/installation/upgrade_notes
http://www.zabbix.com/documentation/2.0/manual/introduction/whatsnew200#ability_to_send_empty_strings
http://www.zabbix.com/documentation/2.0/manual/config/items/itemtypes
http://www.zabbix.com/documentation/2.0/manual/config/items/userparameters

<zalex> Reviewed. Great! Thanks. CLOSED

I upgraded zabbix to 2.0.1 but I missed to see this feature which actually broke part of my production monitoring. Is it possible to have the old behavior back by an option in zabbix agent config? Otherwise I will have to keep the old agent on the machines or keep patching the new one.

Thanks.

For who is interested in reverting this behavior for UserParameters, just change under src/libs/zbxsysinfo/sysinfo.c line94 from EXECUTE_USER_PARAMETER& to EXECUTE_STR&

I think Zabbix Agent should be a bit smarter when handling scripts in UserParameters. I like the fact the you can return empty strings and I see applications where I could take advantage of this feature. But if one doesn't want to report any data because none is available and simply exit the code without any data to stdout, I would expect Zabbix to throw an ZBX_NOTSUPPORTED error.

The reason why I need the old behavior is that I rely on the fact that some plugins cannot provide certain information at a certain time. Because of some logic in the triggers I cannot afford to have an empty item and I'm happy to retain the last valid data received for the item until the information is available again and the items get updated.

I think the best solution is for Zabbix Agent to handle the exit code for the scripts executed via the UserParameters. I guess that if one exit -1, Zabbix could throw the ZBX_NOTSUPPORTED.

Thank you for your understanding.

Keep up the good work!

M

There's also another big change that broke my monitoring.. which is how the MACROS are passed to the zabbix agent. I had a few macros which contained "" since Zabbix would not allow me to have an empty macros.

proc.num[{$APP_NAME},{$APP_USER},,{$APP_FILTER}]

when $APP_FILTER is "", it's passed to the agent as \"\" and since the command line does not contain that it will always report a count of 0 processes.

The old zabbix-agentd would not behave like this.

As a result, I cannot re-define macros as empty in a link of templates.

M

ability to return error state is ZBXNEXT-152
ability to specify empty values for macros might be a new feature request (but please search whether one exists already or not)

The following changes must be implemented:

1) Database changes for table 'scripts', new fields must be added:

FIELD |type |t_integer |'0' |NOT NULL |ZBX_SYNC
FIELD |execute_on |t_integer |'1' |NOT NULL |ZBX_SYNC

type: 0 - script, 1 - IPMI
execute_on (script only): 0 - execute on agent, 1 - execute on Zabbix server

2) User script configuration form must be modified according to provided sketch.

3) Database patch for converting existing IPMI commands to new DB structure

4) Server side must be modified to support execution of scripts by Zabbix agents.

5) Commands executed by Zabbix Agents will be based on system.run[], which can be enabled or disabled by EnableRemoteCommands

6) Server must validate Host Group defined for a Script. If a host is not in the specified host group, the command will not be executed on the host.

7) API methods script.get, script.create and script.update will be updated to support new fields 'type' and 'execute_on'.

does 6 mean ability to specify single group only or multiple groups ?

Just one host group. (6) fixed.

trunk 18311

The following changes must be implemented:

1) Database changes for tables opcommand_hst and opcommand_grp. New fields:

FIELD |type |t_integer |'0' |NOT NULL |ZBX_SYNC
FIELD |scriptid |t_id | |NULL |ZBX_SYNC |3|scripts | |RESTRICT
FIELD |execute_on |t_integer |'0' |NOT NULL |ZBX_SYNC
FIELD |port |t_varchar(64) |'' |NOT NULL |ZBX_SYNC
FIELD |authtype |t_integer |'0' |NOT NULL |ZBX_SYNC
FIELD |username |t_varchar(64) |'' |NOT NULL |ZBX_SYNC
FIELD |password |t_varchar(64) |'' |NOT NULL |ZBX_SYNC
FIELD |publickey |t_varchar(64) |'' |NOT NULL |ZBX_SYNC
FIELD |privatekey |t_varchar(64) |'' |NOT NULL |ZBX_SYNC

type: 0 - script, 1 - IPMI, 2 - SSH, 3 - Telnet, 4 - user script
execute_on: 0 - execute on agent, 1 - execute on Zabbix server

During development process, we decided to change schema requirements:
All new fields are moved to opcommand table leaving opcommand_hst and opcommand_grp only with operation id and hostid/groupid.

other fields have same definition as for table 'items'

2) User script cannot be removed if used for actions. A clear error message should be given.

3) Action permissions must take into account user scripts.If no RW permissions for a user script, the action is not accessible in the GUI.

4) Selection of user scripts in action form should respect permissions.

Can be a security issue if a script is for execution on RW hosts.

5) Action form must be modified according to provided sketch.

6) Database patch for converting existing IPMI commands to new DB structure

7) For Telnet and SSH checks username, password are used for authentication purposes. For SSH authtype, publickey, privatekey can be used as well.

8) Username, password,publickey, privatekey must support user macros. The macros are based on the target host.

9) Server side must be modified to support new command types.

10) Commands executed by Zabbix Agents will be based on system.run[], which can be enabled or disabled by EnableRemoteCommands

11) Server must validate Host Groups defined for a Script. If a host is not in the specified host group, the command will not be executed on the host.

12) API methods action.get, action.create and action.update will be extended to support new opcommand_hst/opcommand_grp fields.

trunk 18964

database changes have not been implemented according to the specification (which in this case probably means that specification was never updated as it was changed during the development...)

was implemented as ZBXNEXT-780

Available in development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-558

Available in version pre1.9.1, r15431.

if multiple ips are configured for agentd listenip, what happens ? is the first one only sent to the server ?

Yes, only the first one.

new feature request about multiple ip addresses submitted as ZBXNEXT-717

Suggestions with regard to the item name are highly welcome.

Merged into pre-2.0 in r14150.

Windows (all)

For eg cpu %

regarding network interfaces, i believe that problem is with the way windows handles network interfaces - zabbix items need interface name, but network interface names are not consistent over windows installations. please correct me if that's wrong, i haven't used windows for a long time now

Windows template has the following items for monitoring the number of processes:

proc.num[]
system[procrunning]
proc_cnt[httpd]

The last two are outdated, undocumented, and not supported.

last two process counting items have been removed for appliance, expected to trickle down to data.sql in next version

templates were redone for 2.0, and windows template now uses lld for network interfaces. all the problems mentioned here should be solved by now

From which version are the items below discontinued? I'm in version 4.0.5, I can delete or disable them, right?

system [procrunning]
proc_cnt [httpd]