Technical FAQs

Some technical questions about Centreon

Contents

Centreon Web UI

• Get the version of Centreon Web in UI

Centreon Poller

• Generate a core dump
• Generate more logs for Centreon Broker

---

Centreon Web UI

Get the version of Centreon Web in UI

Go to the page Administration > About and you should get the version of Centreon Web UI and also the commit of the build

---

Centreon Poller

Generate a core dump

This following procedure describes how to configure coredumpctl to retrieve core dumps if a segfault happens.

Activate core dump generation

Before retrieving a core dump, you must configure the system for it to generate core dumps at segfault.

1. Install gdb
2. Uncomment "DumpCore=yes" in "/etc/systemd/system.conf"
3. Replace "DefaultLimitCORE=" by "DefaultLimitCORE=infinity" in "/etc/systemd/system.conf"
4. Add these lines in "/etc/sysctl.conf":

   kernel.core_pattern = |/usr/lib/systemd/systemd-coredump %p %u %g %s %t %e 
   fs.suid_dumpable=2
   

5. Add "LimitCORE=infinity" in "/usr/lib/systemd/system/cbd.service" just after the line "User"
6. Add "LimitCORE=infinity" in "/usr/lib/systemd/system/centengine.service" just after the line "User"
7. Restart systemd to commit the changes:

   sysctl -p 
   systemctl daemon-reexec

Retrieve a core dump

After activating core dumps generation, you must wait for a segfault to occur. You will see them in the system's log "/var/log/messages".

1. List the core dumps:

   coredumpctl list

2. Retrieve the core dump

   coredumpctl -o <filename.core> dump /usr/sbin/centengine

This command will store the last coredump of /usr/sbin/centengine to a file named filename.core.

You can do the same with /usr/sbin/cbd.

Generate more logs for Centreon Broker

You can add a file named "/etc/centreon-broker/log-config.json" containing this:

{
    "console": true,
    "log_path": "/tmp",
    "loggers": [
        {
            "name": "sql",
            "level": "warn"
        }
    ]
}

You have choice between several loggers:

• core
• sql
• bbdo
• tcp
• tls
• lua
• perfdata
• bam

For the level, from the higher level to the lower, you have:

• trace
• debug
• info
• warn
• err
• critical
• off

Here is more complete example of the log-config.json file:

{
    "console": false,
    "log_path": "/tmp",
    "loggers": [
        {
            "name": "sql",
            "level": "debug"
        },
        {
            "name": "bbdo",
            "level": "warn"
        },
        {
            "name": "perfdata",
            "level": "err"
        }
    ]
}

You will then find a log named after the Broker's name into the "/tmp" directory.