Zabbix credentials are not valid in config for zabbix server

Bug #1348537 reported by Anastasia Palkina
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Anastasia Palkina

Bug Description

"build_id": "2014-07-23_02-01-14",
"ostf_sha": "c1b60d4bcee7cd26823079a86e99f3f65414498e",
"build_number": "347",
"auth_required": false,
"api": "1.0",
"nailgun_sha": "f5775d6b7f5a3853b28096e8c502ace566e7041f",
"production": "docker",
"fuelmain_sha": "74b9200955201fe763526ceb51607592274929cd",
"astute_sha": "fd9b8e3b6f59b2727b1b037054f10e0dd7bd37f1",
"feature_groups": ["mirantis"],
"release": "5.1",
"fuellib_sha": "fb0e84c954a33c912584bf35054b60914d2a2360"

1. Create new environment (CentOS, simple mode)
2. Add controller, compute, zabbix
3. Start deployment. It was successful
4. I successfully login to zabbix dashboard
5. But there is many errors in zabbix.log (node-21):

2014-07-25 09:19:39 ERR

 [Z3005] query failed: [2006] MySQL server has gone away [select i.itemid,i.key_,h.host,i.type,i.history,i.hostid,i.value_type,i.delta,i.units,i.multiplier,i.formula,i.state,i.valuemapid,i.trends,i.data_type from hosts h,items i where h.hostid=i.hostid and h.status=0 and i.status=0 and i.state=0 and ((h.host='node-19.domain.tld' and i.key_='memcache[cmd_get]') or (h.host='node-19.domain.tld' and i.key_='memcache[cmd_set]'))]

2014-07-25 09:08:21 ERR

 [Z3005] query failed: [2006] MySQL server has gone away [select hostid,key_,state,filter,error,lifetime from items where itemid=501]

2014-07-25 09:08:19 ERR

 [Z3005] query failed: [2006] MySQL server has gone away [select hostid,key_,state,filter,error,lifetime from items where itemid=499]

If you restart zabbix it dies (see screen)

And error appears in logs:

2014-07-25 09:39:29 CRIT

 One child process died (PID:16454,exitcode/signal:255). Exiting ...

Tags: zabbix
Revision history for this message
Anastasia Palkina (apalkina) wrote :
Revision history for this message
Anastasia Palkina (apalkina) wrote :
Changed in fuel:
assignee: Fuel Library Team (fuel-library) → Aleksandr Didenko (adidenko)
Revision history for this message
Aleksandr Didenko (adidenko) wrote :

Can't reproduce it on #367 ISO:

{
    "api": "1.0",
    "astute_sha": "aa5aed61035a8dc4035ab1619a8bb540a7430a95",
    "auth_required": true,
    "build_id": "2014-07-28_10-30-48",
    "build_number": "367",
    "feature_groups": [
        "mirantis",
        "experimental"
    ],
    "fuellib_sha": "d1c7f67b3cf51978d3178c8666ea398f2477dcb5",
    "fuelmain_sha": "9adfbf5a52cedbdd16ec1a74f6c44c5b3419b87c",
    "nailgun_sha": "83cc9ed44ebc8dd97248483b6d414ebbc4cff3c0",
    "ostf_sha": "8c328521b1444f22c50463b9432193e20ed33813",
    "production": "docker",
    "release": "5.1"
}

> One child process died (PID:16454,exitcode/signal:255). Exiting ...

This is expected behavior, such record always appears when you restart zabbix_server. Also according to the logs from your snapshot zabbix_server was able to successfully start on node-21 after restart.

> If you restart zabbix it dies (see screen)

Restarted, dashboard and zabbix_server work fine.

> query failed: [2006] MySQL server has gone away

This might be cause by load spikes during deployment. After deployment is finished, zabbix_server worked for more than 2.5 hours on my env without a single alert in logs.

If you can reproduce it, please provide access to the live env with broken zabbix.

Changed in fuel:
status: New → Incomplete
assignee: Aleksandr Didenko (adidenko) → Anastasia Palkina (apalkina)
Revision history for this message
Anastasia Palkina (apalkina) wrote :

Cannot reproduced on ISO #369
"build_id": "2014-07-29_02-01-14", "ostf_sha": "9c0454b2197756051fc9cee3cfd856cf2a4f0875", "build_number": "369", "auth_required": true, "api": "1.0", "nailgun_sha": "98ea1ce54f4d084e2533c7ea23aa98551f955ec5", "production": "docker", "fuelmain_sha": "2379783517e4830868f66b5fbab512eec4695679", "astute_sha": "aa5aed61035a8dc4035ab1619a8bb540a7430a95", "feature_groups": ["mirantis", "experimental"], "release": "5.1", "fuellib_sha": "851b29ac6434c1671078ef293bb25a04dc492f49"}

Changed in fuel:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.