Announcement

Collapse
No announcement yet.

Centreon 3.1 Web Interface Very Slow

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • djtremors
    replied
    Late post but worth mentioning. You need to consider iotop and check disk as well as network performance. It could well be there's too much going on with disk that your IO wait is very high. This is why I don't like how centreon ties it's internals to be localized a lot, ie RRD graphs. I would much prefer that to be a time series on another server. This could be influxdb or opentsdb etc
    But this may not be your issue and as I said, you need to branch out more than using just top.
    I personally use a lot more passive checks than active as it is too expensive to do active checks, even if snmp (still using scripts to do snmp).

    top - 09:17:38 up 5 days, 16:28, 1 user, load average: 0.28, 0.35, 0.38
    Tasks: 90 total, 1 running, 89 sleeping, 0 stopped, 0 zombie
    %Cpu(s): 0.0 us, 0.1 sy, 0.0 ni, 99.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.1 st <---- wa = wait time for IO
    KiB Mem: 504932 total, 336888 used, 168044 free, 2468 buffers
    KiB Swap: 0 total, 0 used, 0 free. 112700 cached Mem

    Leave a comment:


  • boubou
    replied
    Strange.
    All should work perfectly with that!

    I can't understand...

    Leave a comment:


  • matthttam
    replied
    Thank you for the reply and sorry for the delay.

    I did look at Top:
    cpu usage at ~ 1.3 - 5% when idle.
    cpu usage at ~ 2 - 5 % after clicking a host to edit on the page.

    Mem shows 5,924,568k free

    Not sure what ps can really show me. I did a ps aux and scrolled through the list. Nothing is standing out as a problem here.

    [[email protected] html]# rpm -qa | grep centreon
    centreon-broker-2.8.1-5.el6.x86_64
    centreon-engine-daemon-1.4.11-4.el6.x86_64
    centreon-broker-core-2.8.1-5.el6.x86_64
    centreon-connector-1.1.1-2.el6.x86_64
    centreon-broker-cbmod-2.8.1-5.el6.x86_64
    centreon-plugins-2.5.4-2.el6.noarch
    centreon-web-2.5.4-2.el6.noarch
    centreon-common-2.5.4-2.el6.noarch
    centreon-connector-ssh-1.1.1-2.el6.x86_64
    centreon-nagvis-1.1-2.el6.noarch
    centreon-connector-perl-1.1.1-2.el6.x86_64
    centreon-engine-extcommands-1.4.11-4.el6.x86_64
    centreon-broker-storage-2.8.1-5.el6.x86_64
    centreon-broker-cbd-2.8.1-5.el6.x86_64
    centreon-widget-service-monitoring-1.3.2-1.el6.noarch
    centreon-widget-host-monitoring-1.3.2-1.el6.noarch
    centreon-trap-2.5.4-2.el6.noarch
    centreon-plugin-meta-2.5.4-2.el6.noarch
    centreon-base-config-centreon-engine-2.5.4-2.el6.noarch
    centreon-widget-hostgroup-monitoring-1.1.1-2.el6.noarch
    centreon-perl-libs-2.5.4-2.el6.noarch
    centreon-clib-1.4.2-1.el6.x86_64
    centreon-engine-1.4.11-4.el6.x86_64
    centreon-clapi-1.7.1-2.el6.noarch
    centreon-2.5.4-2.el6.noarch
    centreon-widget-graph-monitoring-1.1.0-2.el6.noarch
    centreon-widget-servicegroup-monitoring-1.1.0-1.el6.noarch
    [[email protected] html]# rpm -qa | grep MariaDB
    MariaDB-server-5.5.35-1.x86_64
    MariaDB-compat-5.5.35-1.x86_64
    MariaDB-common-5.5.35-1.x86_64
    MariaDB-client-5.5.35-1.x86_64

    Leave a comment:


  • boubou
    replied
    All should work smoothly with that setup.

    Whats about proc utilization and ram utilisation ? Did you try "top" or ps ?

    Did you upgrade your server after you did a fresh install ?

    Please give us the output of rpm -qa | grep centreon and the output of rpm -qa | grep MariaDB.

    Leave a comment:


  • matthttam
    replied
    Thanks for the reply. I used the CES ISO to install which went really well.

    It is a lower spec machine but it should get the job done:
    Optiplex 780 (late 2009)
    Intel Core 2 Duo at 2.933 Mhz - LGA775 1.2V
    8 GB of RAM

    I want to say the database is returning slowly on certain queries but I don't know how to test for this.

    Leave a comment:


  • boubou
    replied
    How did you install the Centreon3.1 ? Using the CES ISO or using sources ?

    What about the machine specs ? What is the proc and how much ram ?

    You are running a lightweight platform so you shouldn't have speed issues.

    Leave a comment:


  • matthttam
    replied
    I found the following thread that had a similar issue:
    https://forum.centreon.com/showthrea...highlight=slow

    As I mentioned before though, deleting the ib_logfiles did not solve the problem. Does anyone have a suggestion? I have maybe 300 more hosts to add and at this point it is taking too long for each one.

    Leave a comment:


  • matthttam
    started a topic Centreon 3.1 Web Interface Very Slow

    Centreon 3.1 Web Interface Very Slow

    First I just want to say I really like Centreon! Our nagios server (with nconf) died and lost the configs along with it so I started over with Centreon 3.1 and have been configuring it over the past few weeks.

    Unfortunately, load speeds for certain things are going very slow. While one page is generating nothing else will generate either so I am forced to wait for one page at a time while configuring hosts/services/ACL.
    Clicking any host: Generated in 10.597 seconds
    Clicking any Service: Generated in 10.104 seconds
    Clicking any ACL: Generated in 10.261 seconds

    Load speeds for users, commands, notifications and practically anything else in the system is working great! The poller has no lag detected, logging is happening without problems, and notifications are bing sent almost instantly.

    It feels like the more hosts and services I add, the slower these page loads become.

    Is this a known problem? I have been googling and trying things out but nothing is working for me. I have dleted the ib_log files and attempted to adjust the innodb buffer size but this caused mysql to fail when starting with a PID lock file error. Now I have the read and write io settings set to 64. I used this page for instructions http://dba.stackexchange.com/questio...nd-ib-logfile0 but nothing has changed.

    I have 105 hosts and 238 services.

    If anyone could please suggest a solution I would greatly appreciate it!

    Thanks,
    Matt
Working...
X