You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
@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?
I did some tests with killing connections again and again, implemented some improvement here. Sub-Tasks with failing DB connections will now terminate early
Expected Behavior
Getting exceptions in the module every few min... (same exception)
Current Behavior
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 exceptionYour Environment
VMware vCenter®/ESXi™-Version: v6.7.x
Version/GIT-Hash of this module:
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
The text was updated successfully, but these errors were encountered: