[ZBX-10259] cmdline parameter severely limited for proc.num, proc.mem, proc.cpu.util on Solaris Created: 2016 Jan 13  Updated: 2020 Feb 11  Resolved: 2016 May 07

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G), Documentation (D)
Affects Version/s: None
Fix Version/s: None

Type: Incident report Priority: Major
Reporter: Sandis Neilands (Inactive) Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: proc.cpu.util, proc.mem, proc.num, solaris
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Solaris


Issue Links:
Duplicate
is duplicated by ZBX-8081 Solaris procfs parsing is reading tru... Closed

 Description   

On Solaris we get the process's command line from /proc/pid/psinfo as struct psinfo. There are several issues with this approach.

1. pr_psargs member is only 80 bytes. Longer command lines are truncated by kernel.
2. The buffer contains the command line as it was when the process was started. It is not updated with up-to-date status information as set by zabbix_agentd, postgres and other long-running daemons.

/usr/ucb/ps looks directly at the process' memory to get up-to-date process titles.

Not sure if this is the approach that we want to take in Zabbix. We should document these limitations though.



 Comments   
Comment by Martins Valkovskis [ 2016 Apr 12 ]

Documented in footnotes for these items on Solaris:

https://www.zabbix.com/documentation/3.0/manual/appendix/items/supported_by_platform#footnotes

Please review.

sandis.neilands CLOSED.

Comment by Sandis Neilands (Inactive) [ 2016 Apr 12 ]

(1) Shouldn't we mention these limitations in https://www.zabbix.com/documentation/3.0/manual/config/items/itemtypes/zabbix_agent ?

martins-v I thought about it a bit. My opinion is that better not. First of all, that would mean pasting the same into three cells (and totalling four places in documentation). If we change this, then four notes to remove. Also in the agent page we do not state if the item is supported on a specific platform at all. So checking 'Items supported by platform' is a bit of a must anyway.

sandis.neilands The counter argument could be that we have platform specifics in Zabbix agent items page when they affect item's behaviour.

To me the items supported by platform page gives "yes"/"no" answer of whether an item is supported on platform at all. The Zabbix agent items page then tells me how the item is supported.

What if we included this limitation in the cmdline notes page? It is already linked from all relevant items. And mention this page in the footnote in items supported by platform page?

martins-v We could... but why? We have this issue in the status of a major bug. Then let's fix it... and we will not have to document it at all

sandis.neilands It was decided to document this now since this issue was encountered in production environment. Whether there will be a software correction depends on product management. CLOSED.

Comment by Sandis Neilands (Inactive) [ 2016 Apr 12 ]

(2) The notes about cmdline (https://www.zabbix.com/documentation/3.0/manual/appendix/items/proc_mem_num_notes) are Linux specific. This could be emphasized in items description page.

martins-v RESOLVED IN https://www.zabbix.com/documentation/3.0/manual/config/items/itemtypes/zabbix_agent

sandis.neilands CLOSED.

Generated at Thu May 29 10:33:53 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.