Error when run "icingacli reporting schedule run"

   icinga2 - The Icinga 2 network monitoring daemon (version: r2.10.4-1)

System information:
Platform: Ubuntu
Platform version: 18.04.2 LTS (Bionic Beaver)
Kernel: Linux
Kernel version: 4.15.0-51-generic
Architecture: x86_64

Build information:
Compiler: GNU 7.3.0
Build host: b2ecadfb68ab

Application information:

General paths:
Config directory: /etc/icinga2
Data directory: /var/lib/icinga2
Log directory: /var/log/icinga2
Cache directory: /var/cache/icinga2
Spool directory: /var/spool/icinga2
Run directory: /run/icinga2

Old paths (deprecated):
Installation root: /usr
Sysconf directory: /etc
Run directory (base): /run
Local state directory: /var

Internal paths:
Package data directory: /usr/share/icinga2
State path: /var/lib/icinga2/icinga2.state
Modified attributes path: /var/lib/icinga2/modified-attributes.conf
Objects path: /var/cache/icinga2/icinga2.debug
Vars path: /var/cache/icinga2/icinga2.vars
PID path: /run/icinga2/icinga2.pid

“I’m trying to install Reporting module, get the below-mentioned error”
ERROR: PDOException in /usr/share/icingaweb2/modules/ipl/vendor/ipl/sql/src/Connection.php:314 with message: SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘reporting.schedule’ doesn’t exist

Followed this link for installation “https://icinga.com/docs/reporting/latest/

Seems like the schema wasnt imported.

If you log in the database, do you see any tables under the reporting database? If empty, try importing the schema again as in the docs:

mysql -p -u root reporting < schema/mysql.sql

Take notice that the path is relative and you need to actually go to “/usr/share/icingaweb2/modules/reporting” or wherever IcingaWeb is installed.

Cheers,
George

1 Like

Thanks a lot, My mistake i was referring to this file till “/usr/share/icinga2-ido-mysql/schema/mysql.sql”
Now its working fine.
I can see SLA for overall system.
What if i want to limit this SLA to specific hostgroup ? Let’s say “critical_servers”.
Can this be done ?

Thanks for the help, Info was available to achieve on filtering SLA after i made mistake.

Now it’s working smooth for me :slight_smile:

2 Likes