Am 04.07.2016 um 11:59 schrieb Diana Scannicchio:
Hello Andreas,
unfortunately we cannot upgrade to versions that are not in the official CERN
release of the OS.
No I did not try the tuning advisors yopu suggested
I noticed that there was a bug report for apparently the same issue
https://dev.ic
Hi Andreas,
thank you, I just run it also on what you call the live server and this is the
output I got
Recommendations
---
General recommendations:
Remove Anonymous User accounts - there are 2 anonymous account
Hi Diana,
both scripts need to be run on the live server.
They try to gather basic statistics and advice for config changes.
There is no use in running them on other machines/vms...
kind regards
2016-07-04 11:59 GMT+02:00 Diana Scannicchio :
> Hello Andreas,
> unfortunately we cannot upgrade
Hello Andreas,
unfortunately we cannot upgrade to versions that are not in the official CERN
release of the OS.
No I did not try the tuning advisors yopu suggested
I noticed that there was a bug report for apparently the same issue
https://dev.icinga.org/issues/10731
and that it was theoretically
Have you tried to usual MySQL tuning advisors?
http://mysqltuner.pl
https://github.com/RootService/tuning-primer
Is it possible to upgrade to a more recent MySQL version? Maybe 5.5 or
better 5.6 or even 5.7?
What about Disk I/O on the host? do you have I/O waits?
2016-07-01 15:45 GMT+02:00 Dia
Hello Antony,
so this is interesting… I stopped icinga2 service and mysqld, I added in the
[mysqld] section of /etc/my.cnf the following two lines
slow-query-log = 1
slow-query-log-file = /var/log/mysql-slow-query.log
Then I touched /var/log/mysql-slow-query.log and change the ownership to my
Hello Antony,
so both the machines (they are identical) have 2 CPU (CPU E5-2620 v3 @ 2.40GHz)
with 6 core per processor, so a total of 12 CPU cores.
I assumed that the test machine is swapping a lot due to MySQL not able to cope.
The majority of the process are run by root and they are on both nod
On Thursday 30 June 2016 at 15:23:19, Diana Scannicchio wrote:
> below you can see what I get by connecting to MySQL as a privileged user and
> asking it to "show processlist” on both the nodes (one running v2.4.10 and
> the second one running v2.3.11. And also the output of top.
Well, the first
Hello Antony,
thank you, so below you can see what I get by connecting to MySQL as a
privileged user and asking it to "show processlist” on both the nodes (one
running v2.4.10 and the second one running v2.3.11.
And also the output of top.
Thank you for any suggestion you can provide me.
Best reg
On Wednesday 29 June 2016 at 15:52:54, Diana Scannicchio wrote:
> We tried few months ago to upgrade to v2.4.1, unfortunately the restart of
> the icinga2 service was hanging forever apparently due to some bad
> interaction with mysql. Once we disabled ido-mysql, it started. We setup
> a test ser
Dear Icinga experts,
in CERN ATLAS experiment we setup our Icinga2 monitoring system using two nodes
configured in High Availability.
The Icinga2 version used is v2.3.11 (see below for more details) and we do have
ido-mysql enabled.
The server is checking 4141 hosts and 83188 services.
We tried
11 matches
Mail list logo
