Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MySQL server has gone away (Task storagePods/quickStats) #151

Closed
fireheadman opened this issue Feb 10, 2020 · 4 comments
Closed

MySQL server has gone away (Task storagePods/quickStats) #151

fireheadman opened this issue Feb 10, 2020 · 4 comments
Assignees
Labels
Milestone

Comments

@fireheadman
Copy link

Expected Behavior

Getting exceptions in the module every few min... (same exception)

Current Behavior

image

Possible Solution

No clue on what is causing this...

Steps to Reproduce (for bugs)

running the sudo icingacli vspheredb daemon run --debug command and watching it for a min or two will show the exception

Your Environment

  • VMware vCenter®/ESXi™-Version: v6.7.x

  • Version/GIT-Hash of this module:
    image

  • Icinga Web 2 version: v2.7.3-1

  • Operating System and version: RHEL7.7

  • Webserver, PHP versions: Apache v2.4.6-90, PHP7.1.30-2

@mrgohin
Copy link

mrgohin commented Mar 4, 2020

Hi,

Short search on the internet brought me to the point that maybe your max_allowed_packet size is to low.

Greets,

@fireheadman
Copy link
Author

I've seen this mentioned before...
my current setting is
max_allowed_packet = 16M

We are pushing right under 4000 service checks and under 400 clients, which would be in my opinion a "small-med" shop. I haven't seen this setting over 16M, so never considered increasing beyond this size.

@Thomas-Gelf
Copy link
Contributor

@fireheadman: in case you just lost the DB connection because of a service restart or similar, this should have been fixed with v1.1.0. Did this happen to you again?

@Thomas-Gelf Thomas-Gelf self-assigned this Apr 29, 2020
@Thomas-Gelf Thomas-Gelf added this to the v1.2.0 milestone Apr 29, 2020
@Thomas-Gelf
Copy link
Contributor

I did some tests with killing connections again and again, implemented some improvement here. Sub-Tasks with failing DB connections will now terminate early

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants