# Icinga\_ido resource not found, help! **URL:** \ **Category:** Icinga Web\ **Created:** [March 14, 2023, 9:07am UTC](https://community.icinga.com/t/icinga-ido-resource-not-found-help/11613 "2023-03-14T09:07:03Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![DragonNZ](https://community.icinga.com/user_avatar/community.icinga.com/dragonnz/32/6529_2.png) [@DragonNZ](https://community.icinga.com/u/DragonNZ)\ **Post date:** [March 14, 2023, 9:07am UTC](https://community.icinga.com/t/icinga-ido-resource-not-found-help/11613/1 "2023-03-14T09:07:03Z")
Hi, I have installed icinga2 following the guides and everything seems to be working except I am seeing this error throughout the web dashboard (I have pasted at the end of this post) I am struggling to find any reference to this issue. I can’t see any issues in the logs. The feature list is Disabled features: compatlog elasticsearch gelf graphite influxdb influxdb2 livestatus opentsdb perfdata statusdata syslog Enabled features: api checker command debuglog icingadb ido-mysql mainlog notification ido-mysql has all the tables that are in the schema file, and it is enabled and in the log it says that it is connecting. It’s using the user icinga2 on the database icinga2 and has all permissions. If anyone could point me in the right direction it would be most appreciated. Thank you. `Cannot load resource config “icinga\_ido”. Resource does not exist * * * #0 /usr/share/icingaweb2/modules/monitoring/library/Monitoring/Backend/MonitoringBackend.php(208): Icinga\Data\ResourceFactory::getResourceConfig() #1 /usr/share/icingaweb2/modules/monitoring/library/Monitoring/Backend/MonitoringBackend.php(287): Icinga\Module\Monitoring\Backend\MonitoringBackend-\>getResource() #2 /usr/share/icingaweb2/modules/monitoring/library/Monitoring/DataView/DataView.php(55): Icinga\Module\Monitoring\Backend\MonitoringBackend-\>query() #3 /usr/share/icingaweb2/modules/monitoring/library/Monitoring/Backend/MonitoringBackend.php(242): Icinga\Module\Monitoring\DataView\DataView-\>\_\_construct() #4 /usr/share/icingaweb2/modules/monitoring/application/controllers/ListController.php(85): Icinga\Module\Monitoring\Backend\MonitoringBackend-\>from() #5 /usr/share/icingaweb2/library/vendor/Zend/Controller/Action.php(507): Icinga\Module\Monitoring\Controllers\ListController-\>hostsAction() #6 /usr/share/php/Icinga/Web/Controller/Dispatcher.php(76): Zend\_Controller\_Action-\>dispatch() #7 /usr/share/icingaweb2/library/vendor/Zend/Controller/Front.php(937): Icinga\Web\Controller\Dispatcher-\>dispatch() #8 /usr/share/php/Icinga/Application/Web.php(290): Zend\_Controller\_Front-\>dispatch() #9 /usr/share/php/Icinga/Application/webrouter.php(105): Icinga\Application\Web-\>dispatch() #10 /usr/share/icingaweb2/public/index.php(4): require\_once(String) #11 {main}` ---
**Author:** ![rsx](https://community.icinga.com/user_avatar/community.icinga.com/rsx/32/2094_2.png) [@rsx](https://community.icinga.com/u/rsx)\ **Post date:** [March 14, 2023, 10:11am UTC](https://community.icinga.com/t/icinga-ido-resource-not-found-help/11613/2 "2023-03-14T10:11:57Z")
Hi & welcome, You should not enable `icingadb` and `ido-mysql` at the same time. You can only use one of them and the recommendation for new installation is `icingadb`. ---
**Author:** ![DragonNZ](https://community.icinga.com/user_avatar/community.icinga.com/dragonnz/32/6529_2.png) [@DragonNZ](https://community.icinga.com/u/DragonNZ)\ **Post date:** [March 14, 2023, 10:37pm UTC](https://community.icinga.com/t/icinga-ido-resource-not-found-help/11613/3 "2023-03-14T22:37:25Z")
Hi, Thank you! I will disable the ido-mysql and figure my way from there. I would like to monitor the status of a couple of replication slaves running on the MYSQL server, so I was thinking the ido-mysql was another module for that job. ---
**Author:** ![moreamazingnick](https://community.icinga.com/user_avatar/community.icinga.com/moreamazingnick/32/7725_2.png) [@moreamazingnick](https://community.icinga.com/u/moreamazingnick)\ **Post date:** [March 15, 2023, 6:43am UTC](https://community.icinga.com/t/icinga-ido-resource-not-found-help/11613/4 "2023-03-15T06:43:29Z")
You can use Icingadb and ido at the same time. My system currently runs on ido-postgres, ido-mysql and icingadb-mysql. but icingaweb works with only one ido, so i have to switch. I think there is something wrong with your icingaweb2 config, but since you are not telling us what you installed or what guide you followed it is difficult to analyse the issue. So if you start over using a current “guide” and installing icingadb this might solve your current issue but is not helping the cause that your config was broken ---
**Author:** ![rsx](https://community.icinga.com/user_avatar/community.icinga.com/rsx/32/2094_2.png) [@rsx](https://community.icinga.com/u/rsx)\ **Post date:** [March 15, 2023, 6:50am UTC](https://community.icinga.com/t/icinga-ido-resource-not-found-help/11613/5 "2023-03-15T06:50:03Z")
You’re looking for a check plugin which can be found in the [ITL](https://icinga.com/docs/icinga-2/latest/doc/10-icinga-template-library/#mysql) or [here](https://labs.consol.de/nagios/check_mysql_health/) or [here](https://exchange.icinga.com/search?q=mysql) or [here](https://exchange.nagios.org/index.php?option=com_mtree&task=search&Itemid=74&searchword=mysql) ---
**Author:** ![rsx](https://community.icinga.com/user_avatar/community.icinga.com/rsx/32/2094_2.png) [@rsx](https://community.icinga.com/u/rsx)\ **Post date:** [March 15, 2023, 6:50am UTC](https://community.icinga.com/t/icinga-ido-resource-not-found-help/11613/6 "2023-03-15T06:50:49Z")
> [@moreamazingnick](#): > > You can use Icingadb and ido at the same time. Yes, but this does not make sense. ---
**Author:** ![moreamazingnick](https://community.icinga.com/user_avatar/community.icinga.com/moreamazingnick/32/7725_2.png) [@moreamazingnick](https://community.icinga.com/u/moreamazingnick)\ **Post date:** [March 15, 2023, 7:17am UTC](https://community.icinga.com/t/icinga-ido-resource-not-found-help/11613/7 "2023-03-15T07:17:02Z")
this icinga2 setup describes that both features are enabled. nobody knows why but here are some reason this setup could makes sense: - You want to write history in icingadb and ido so you can change at the proper time to from the icingaweb2-module-monitoring to icingadb-web without depending on the migration tool. - you can switch between both worlds in icingaweb2 without any troubles. - you are using an old version of icingaweb2-module-grafana, which does not work on icingadb - you are using api endpoints in icingaweb2 which are not working in icingadb-web but were working fine under the monitoring module Don’t get me wrong, I’m on your side that icingadb is the future and ido is officially deprecated. But actually that got me thinking, [Dragon Nz](https://community.icinga.com/u/DragonNZ) might need to disable the monitoring module in icingaweb2 In addition this thread might help understanding caused the issue: > [@Installation Icinga2 with DB](https://community.icinga.com/t/installation-icinga2-with-db/10138/3): > > I pasted this comment in my shell… works fine… but in my setup screen from icinga2 my installation-assistant tells me “ido schema not found in db”. If I reenter this command to import the schema I get following message under Debian 11.4: “Table host alreadys exists”. Where is the problem? ---
**Author:** ![Matlib](https://community.icinga.com/user_avatar/community.icinga.com/matlib/32/4164_2.png) [@Matlib](https://community.icinga.com/u/Matlib)\ **Post date:** [March 18, 2023, 9:59pm UTC](https://community.icinga.com/t/icinga-ido-resource-not-found-help/11613/8 "2023-03-18T21:59:55Z")
To me this sounds like database connection called _icinga\_ido_ is not defined. Have you or some script deleted it by mistake? Icinga DB and Monitoring may coexist. So do icingadb daemon and IDO. Neither of these have anything to do with database monitoring plugins. ---
**Author:** ![Theking2](https://community.icinga.com/letter_avatar_proxy/v4/letter/t/ecb155/32.png) [@Theking2](https://community.icinga.com/u/Theking2)\ **Post date:** [May 27, 2026, 2:19pm UTC](https://community.icinga.com/t/icinga-ido-resource-not-found-help/11613/9 "2026-05-27T14:19:59Z")
So how to disable icinga\_ido? ---
**Author:** ![apenning](https://community.icinga.com/user_avatar/community.icinga.com/apenning/32/7669_2.png) [@apenning](https://community.icinga.com/u/apenning)\ **Post date:** [May 27, 2026, 2:33pm UTC](https://community.icinga.com/t/icinga-ido-resource-not-found-help/11613/10 "2026-05-27T14:33:55Z")
The [IDO, Icinga Data Output,](https://icinga.com/docs/icinga-2/latest/doc/14-features/#db-ido) is the deprecated database output - either [IdoMySqlConnection](https://icinga.com/docs/icinga-2/latest/doc/09-object-types/#idomysqlconnection) or [IdoPgsqlConnection](https://icinga.com/docs/icinga-2/latest/doc/09-object-types/#idopgsqlconnection). Thus, unless you have explicitly enabled this module, there is nothing to disable. Otherwise, disable the module - `icinga2 feature disable` - and migrate to Icinga DB, either following the [migration guide](https://icinga.com/docs/icinga-db/latest/doc/06-Migration/) or start with a clean database. However, please don’t necrobump three year old threads with such a generic question, but consider starting a new thread.