need more than 1 value to unpack

[darrynv]

When I run /usr/lib/zabbix/check_apache --config /etc/zabbix/zabbix_agentd.conf

I get

"failed to parse server-status: need more than 1 value to unpack"

RHEL 7.1
Server version: Apache/2.4.6 (Red Hat Enterprise Linux)

Can confirm I can access /server-status from localhost.

[dlbewley]

can you post the output of /server-status?

[darrynv]

http://pastebin.com/sS9wrCvk

Let me know how else I can help?

[gpmidi]

Can you also post a copy of "/server-status?auto"

[NikiN2]

/usr/lib/zabbix/check_apache --config /etc/zabbix/zabbix_agentd.conf -o 127.0.0.1
fix it

[tbjornli]

On Apache 2.4.7 everything works fine, but I encounter the same error on Apache 2.4.18.
Did anyone find a solution to this?

Apache 2.4.7 server-status

Total Accesses: 49002
Total kBytes: 288972
CPULoad: .00188242
Uptime: 89247
ReqPerSec: .54906
BytesPerSec: 3315.6
BytesPerReq: 6038.68
BusyWorkers: 2
IdleWorkers: 11
Scoreboard: __..__._____C._.W_....................................................................................................................................

Apache 2.4.18 server-status

host.domain.tld
ServerVersion: Apache/2.4.18 (Ubuntu) OpenSSL/1.0.2g
ServerMPM: prefork
Server Built: 2016-07-14T12:32:26
CurrentTime: Friday, 28-Oct-2016 20:09:16 CEST
RestartTime: Friday, 28-Oct-2016 20:06:42 CEST
ParentServerConfigGeneration: 1
ParentServerMPMGeneration: 0
ServerUptimeSeconds: 153
ServerUptime: 2 minutes 33 seconds
Load1: 0.00
Load5: 0.16
Load15: 0.30
Total Accesses: 48
Total kBytes: 34
CPUUser: .08
CPUSystem: .02
CPUChildrenUser: 0
CPUChildrenSystem: 0
CPULoad: .0653595
Uptime: 153
ReqPerSec: .313726
BytesPerSec: 227.556
BytesPerReq: 725.333
BusyWorkers: 1
IdleWorkers: 10
Scoreboard: ..._......_.......W....._.........._...__.__..._._....................................................................................................
TLSSessionCacheStatus
CacheType: SHMCB
CacheSharedMemory: 512000
CacheCurrentEntries: 0
CacheSubcaches: 32
CacheIndexesPerSubcaches: 88
CacheIndexUsage: 0%
CacheUsage: 0%
CacheStoreCount: 0
CacheReplaceCount: 0
CacheExpireCount: 0
CacheDiscardCount: 0
CacheRetrieveHitCount: 0
CacheRetrieveMissCount: 0
CacheRemoveHitCount: 0
CacheRemoveMissCount: 0

[tomvanbraeckel]

I can confirm that this, in combination with the --status-version=2.4.13 option, fixed it for me. Thanks for sharing!