# Icinga2 director - Unable to detect your Icinga 2 Core version (DeployFormsBug7530.php:71)

**URL:** <https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851>\
**Category:** Icinga Director\
**Tags:** director, icinga2\
**Created:** [July 2, 2020, 9:39am UTC](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851 "2020-07-02T09:39:55Z")\
**Posts on this page:** 18\
**Page:** 2

<div class="post-metadata">

**Author:** ![Kevi\_N](https://community.icinga.com/letter_avatar_proxy/v4/letter/k/85e7bf/32.png) [@Kevi\_N](https://community.icinga.com/u/Kevi_N)\
**Post date:** [July 2, 2020, 12:02pm UTC](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851/21 "2020-07-02T12:02:51Z")

</div>

You´re god! I was found upgrading schema (in /usr/share/icinga2-ido-mysql/schema/upgrade), here is 2.11.0.sql file… but how to upgrade it?

Do you want to see content of this file?

---

<div class="post-metadata">

**Author:** ![Kevi\_N](https://community.icinga.com/letter_avatar_proxy/v4/letter/k/85e7bf/32.png) [@Kevi\_N](https://community.icinga.com/u/Kevi_N)\
**Post date:** [July 2, 2020, 12:06pm UTC](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851/22 "2020-07-02T12:06:15Z")

</div>

I updated it by this command:  
**mysql -u root -p icingadb \< /usr/share/icinga2-ido-mysql/schema/upgrade/2.11.0.sql**

And now is everything working!!  
Thanks a lot!!!

---

<div class="post-metadata">

**Author:** ![Kevi\_N](https://community.icinga.com/letter_avatar_proxy/v4/letter/k/85e7bf/32.png) [@Kevi\_N](https://community.icinga.com/u/Kevi_N)\
**Post date:** [July 2, 2020, 12:08pm UTC](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851/23 "2020-07-02T12:08:03Z")

</div>

But… this error is still here… ☹  
 ![image](https://community.icinga.com/uploads/default/original/2X/0/0a7de2b77144675f206960578fc9d618056ccce7.png)

---

<div class="post-metadata">

**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:** [July 2, 2020, 12:13pm UTC](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851/24 "2020-07-02T12:13:34Z")

</div>

Did you upgrade icingaweb2 as well?

---

<div class="post-metadata">

**Author:** ![Kevi\_N](https://community.icinga.com/letter_avatar_proxy/v4/letter/k/85e7bf/32.png) [@Kevi\_N](https://community.icinga.com/u/Kevi_N)\
**Post date:** [July 2, 2020, 12:15pm UTC](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851/25 "2020-07-02T12:15:23Z")

</div>

It look´s icingaweb2 is on the newest version…

```auto

root@vps-d03436bb:~# apt upgrade icingaweb2
Reading package lists... Done
Building dependency tree
Reading state information... Done
icingaweb2 is already the newest version (2.8.1-1.stretch).
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

```

So… Yes, I did.

---

<div class="post-metadata">

**Author:** ![Kevi\_N](https://community.icinga.com/letter_avatar_proxy/v4/letter/k/85e7bf/32.png) [@Kevi\_N](https://community.icinga.com/u/Kevi_N)\
**Post date:** [July 2, 2020, 12:38pm UTC](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851/26 "2020-07-02T12:38:36Z")

</div>

So… yes, I did make upgrade to new version of icingaweb2. Or what is the newest version?

---

<div class="post-metadata">

**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:** [July 2, 2020, 12:44pm UTC](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851/27 "2020-07-02T12:44:23Z")

</div>

2.8.1 is the newest version. I’ve found [this](https://community.icinga.com/t/unable-to-detect-your-icinga-2-core-version/2749) issue, maybe you have a similar error?

---

<div class="post-metadata">

**Author:** ![Kevi\_N](https://community.icinga.com/letter_avatar_proxy/v4/letter/k/85e7bf/32.png) [@Kevi\_N](https://community.icinga.com/u/Kevi_N)\
**Post date:** [July 2, 2020, 12:49pm UTC](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851/28 "2020-07-02T12:49:31Z")

</div>

I´ve found this issue too, but I have error php71 and on this issue is error php70… But thanks.  
I don´t really know, how to fix it ☹

BTW… what I must add to etc/hosts?  
Maybe this is the reason?

Or this?

 ![image](https://community.icinga.com/uploads/default/original/2X/f/f1e2d65ae44a4796dfd1e3cd45ec83ecb4cd95e3.png)

---

<div class="post-metadata">

**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:** [July 2, 2020, 12:56pm UTC](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851/29 "2020-07-02T12:56:29Z")

</div>

When you configure fqdn stead of ip addresses you need any kind of name resolution. One option is to put your fqdn into `/etc/hosts`.  
The last error indicates name resolution is not working or api port is not open.  
What is the result of `ping vps...` (please insert your fqdn).

---

<div class="post-metadata">

**Author:** ![Kevi\_N](https://community.icinga.com/letter_avatar_proxy/v4/letter/k/85e7bf/32.png) [@Kevi\_N](https://community.icinga.com/u/Kevi_N)\
**Post date:** [July 2, 2020, 12:58pm UTC](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851/30 "2020-07-02T12:58:05Z")

</div>

I´m so sorry… but what is fqdn?

---

<div class="post-metadata">

**Author:** ![Kevi\_N](https://community.icinga.com/letter_avatar_proxy/v4/letter/k/85e7bf/32.png) [@Kevi\_N](https://community.icinga.com/u/Kevi_N)\
**Post date:** [July 2, 2020, 1:21pm UTC](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851/31 "2020-07-02T13:21:18Z")

</div>

Or how can I open API port?

---

<div class="post-metadata">

**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:** [July 2, 2020, 1:35pm UTC](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851/32 "2020-07-02T13:35:36Z")

</div>

> [@Kevi\_N](#):
>
> I´m so sorry… but what is fqdn?

hostname incl. domain name in your case `vps...ovh.net`

---

<div class="post-metadata">

**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:** [July 2, 2020, 1:37pm UTC](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851/33 "2020-07-02T13:37:28Z")

</div>

> [@Kevi\_N](#):
>
> Or how can I open API port?

By enabling the feature api (which you did already). You can verfiy using `netstat -tln | grep 5665` the result should look like

> tcp 0 0 0.0.0.0:5665 0.0.0.0:\* LISTEN

---

<div class="post-metadata">

**Author:** ![Kevi\_N](https://community.icinga.com/letter_avatar_proxy/v4/letter/k/85e7bf/32.png) [@Kevi\_N](https://community.icinga.com/u/Kevi_N)\
**Post date:** [July 2, 2020, 1:47pm UTC](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851/34 "2020-07-02T13:47:35Z")

</div>

Thanks, I will try it.

I have 2 VPS servers and I must do the same steps on the second VPS, but I find a problem ☹

I do everything like on the first server.

```auto
root@vps-834c60cb:~# apt update
Ign:1 http://deb.debian.org/debian stretch InRelease
Hit:2 http://security.debian.org stretch/updates InRelease
Hit:3 http://deb.debian.org/debian stretch-updates InRelease
Hit:4 http://packages.icinga.com/debian icinga-stretch InRelease
Hit:5 http://deb.debian.org/debian stretch Release
Hit:6 https://packages.sury.org/php stretch InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
root@vps-834c60cb:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up icinga2-common (2.11.4-1.stretch) ...
Job for icinga2.service failed because the control process exited with error code.
See "systemctl status icinga2.service" and "journalctl -xe" for details.
invoke-rc.d: initscript icinga2, action "start" failed.
● icinga2.service - Icinga host/service/network monitoring system
   Loaded: loaded (/lib/systemd/system/icinga2.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/icinga2.service.d
           └─limits.conf
   Active: failed (Result: exit-code) since Thu 2020-07-02 13:46:15 UTC; 11ms ago
  Process: 26664 ExecStart=/usr/sbin/icinga2 daemon --close-stdio -e ${ICINGA2_ERROR_LOG} (code=exited, status=203/EXEC)
  Process: 26657 ExecStartPre=/usr/lib/icinga2/prepare-dirs /etc/default/icinga2 (code=exited, status=0/SUCCESS)
 Main PID: 26664 (code=exited, status=203/EXEC)

Jul 02 13:46:15 vps-834c60cb systemd[1]: Starting Icinga host/service/network monitoring system...
Jul 02 13:46:15 vps-834c60cb systemd[1]: icinga2.service: Main process exited, code=exited, status=203/EXEC
Jul 02 13:46:15 vps-834c60cb systemd[1]: Failed to start Icinga host/service/network monitoring system.
Jul 02 13:46:15 vps-834c60cb systemd[1]: icinga2.service: Unit entered failed state.
Jul 02 13:46:15 vps-834c60cb systemd[1]: icinga2.service: Failed with result 'exit-code'.
dpkg: error processing package icinga2-common (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 icinga2-common
E: Sub-process /usr/bin/dpkg returned an error code (1)

```

---

<div class="post-metadata">

**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:** [July 2, 2020, 1:49pm UTC](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851/35 "2020-07-02T13:49:42Z")

</div>

> [@Kevi\_N](#):
>
> `dpkg: error processing package icinga2-common (--configure):`

You have an error in your configuration. Check with `icinga2 daemon -C`

---

<div class="post-metadata">

**Author:** ![Kevi\_N](https://community.icinga.com/letter_avatar_proxy/v4/letter/k/85e7bf/32.png) [@Kevi\_N](https://community.icinga.com/u/Kevi_N)\
**Post date:** [July 2, 2020, 1:54pm UTC](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851/36 "2020-07-02T13:54:00Z")

</div>

I want, but it doesn´t work… ☹

```auto
root@vps-834c60cb:~# icinga2 daemon -C
-bash: /usr/sbin/icinga2: No such file or directory

```

---

<div class="post-metadata">

**Author:** ![tom-i](https://community.icinga.com/user_avatar/community.icinga.com/tom-i/32/4243_2.png) [@tom-i](https://community.icinga.com/u/tom-i)\
**Post date:** [June 4, 2021, 12:09pm UTC](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851/37 "2021-06-04T12:09:57Z")

</div>

Hi man,  
how did you solve this? I have similar problem:

- Unable to detect your Icinga 2 Core version (DeployFormsBug7530.php:71) message appear after click on Deploy changes.

I’ve updated / reinstalled all icinga packages from stretch to buster.  
Changed 755 permissions and add icingadirector to correct groups which is mentioned here:

> <https://github.com/Icinga/icingaweb2-module-director/issues/2024#issuecomment-616604751>
>
> \## Expected Behavior
> 
> Director module has to check the environment variable in… the web config.
> 
> \## Current Behavior
> 
> The director background daemon has the error "DB configuration not valid"
> 
> Icinga Director requires configration at /etc/icingaweb2. 
> Seems like the environment variable ICINGAWEB\_CONFIGDIR set in the web configuration is not read by the director module.
> 
> \## Possible Solution
> 
> Create a symlink at /etc/icingaweb2 to the config dir.
> 
> \## Steps to Reproduce (for bugs)
> 
> \## Your Environment
> \* Director version (System - About): 1.7.2
> \* Icinga Web 2 version and modules (System - About): 2.7.3
> \* Icinga 2 version (\`icinga2 --version\`): 2.11.2
> \* Operating System and version: CentOS 7.7
> \* Webserver, PHP versions:
> 
> Hi,
> 
> I´ve just noticed a bug in the icinga director module when updating icingaweb2.
> Please read above.
> 
> Thanks

But still same issue.

One weird think I’ve found is in `journalctl -f -u icinga-director`  
`Jun 04 13:06:45 icinga icingadirector[341]: Zend_Db_Adapter_Exception in /usr/share/icingaweb2/library/vendor/Zend/Db/Adapter/Pdo/Abstract.php:145 with message: SQLSTATE[HY000] [2002] No such file or directory <- PDOException in /usr/share/icingaweb2/library/vendor/Zend/Db/Adapter/Pdo/Abstract.php:124 with message: SQLSTATE[HY000] [2002] No such file or directory`

Another weird messages from icinga logs:

```auto
2021-06-04T13:27:10+02:00 - ERROR - RuntimeException in /usr/share/icingaweb2/modules/director-2020-09-05/library/Director/Core/RestApiClient.php:84 with message: No CURL extension detected, it must be installed and enabled
#0 /usr/share/icingaweb2/modules/director-2020-09-05/library/Director/Core/RestApiClient.php(185): Icinga\Module\Director\Core\RestApiClient->request(String, String, NULL)
#1 /usr/share/icingaweb2/modules/director-2020-09-05/library/Director/Core/CoreApi.php(403): Icinga\Module\Director\Core\RestApiClient->get(String)
#2 /usr/share/icingaweb2/modules/director-2020-09-05/library/Director/Web/Widget/InspectPackages.php(99): Icinga\Module\Director\Core\CoreApi->getPackages()
#3 /usr/share/icingaweb2/modules/director-2020-09-05/library/Director/Web/Widget/InspectPackages.php(33): Icinga\Module\Director\Web\Widget\InspectPackages->getPackages(Object(Icinga\Module\Director\Objects\IcingaEndpoint))
#4 /usr/share/icingaweb2/modules/director-2020-09-05/application/controllers/InspectController.php(181): Icinga\Module\Director\Web\Widget\InspectPackages->getContent(Object(Icinga\Module\Director\Objects\IcingaEndpoint), NULL, NULL, NULL
#5 /usr/share/icingaweb2/library/vendor/Zend/Controller/Action.php(507): Icinga\Module\Director\Controllers\InspectController->packagesAction()
#6 /usr/share/php/Icinga/Web/Controller/Dispatcher.php(76): Zend_Controller_Action->dispatch(String)
#7 /usr/share/icingaweb2/library/vendor/Zend/Controller/Front.php(937): Icinga\Web\Controller\Dispatcher->dispatch(Object(Icinga\Web\Request), Object(Icinga\Web\Response))
#8 /usr/share/php/Icinga/Application/Web.php(300): Zend_Controller_Front->dispatch(Object(Icinga\Web\Request), Object(Icinga\Web\Response))
#9 /usr/share/php/Icinga/Application/webrouter.php(99): Icinga\Application\Web->dispatch()
#10 /usr/share/icingaweb2/public/index.php(4): require_once(String)
#11 {main}
2021-06-04T13:27:30+02:00 - ERROR - RuntimeException in /usr/share/icingaweb2/modules/director-2020-09-05/library/Director/Core/RestApiClient.php:84 with message: No CURL extension detected, it must be installed and enabled
#0 /usr/share/icingaweb2/modules/director-2020-09-05/library/Director/Core/RestApiClient.php(185): Icinga\Module\Director\Core\RestApiClient->request(String, String, NULL)
#1 /usr/share/icingaweb2/modules/director-2020-09-05/library/Director/Core/CoreApi.php(380): Icinga\Module\Director\Core\RestApiClient->get(String)
#2 /usr/share/icingaweb2/modules/director-2020-09-05/application/controllers/InspectController.php(148): Icinga\Module\Director\Core\CoreApi->getStatus()
#3 /usr/share/icingaweb2/library/vendor/Zend/Controller/Action.php(507): Icinga\Module\Director\Controllers\InspectController->statusAction()
#4 /usr/share/php/Icinga/Web/Controller/Dispatcher.php(76): Zend_Controller_Action->dispatch(String)
#5 /usr/share/icingaweb2/library/vendor/Zend/Controller/Front.php(937): Icinga\Web\Controller\Dispatcher->dispatch(Object(Icinga\Web\Request), Object(Icinga\Web\Response))
#6 /usr/share/php/Icinga/Application/Web.php(300): Zend_Controller_Front->dispatch(Object(Icinga\Web\Request), Object(Icinga\Web\Response))
#7 /usr/share/php/Icinga/Application/webrouter.php(99): Icinga\Application\Web->dispatch()
#8 /usr/share/icingaweb2/public/index.php(4): require_once(String)
#9 {main}

```

---

<div class="post-metadata">

**Author:** ![tom-i](https://community.icinga.com/user_avatar/community.icinga.com/tom-i/32/4243_2.png) [@tom-i](https://community.icinga.com/u/tom-i)\
**Post date:** [June 4, 2021, 12:59pm UTC](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851/38 "2021-06-04T12:59:20Z")

</div>

Allowing `php7.3` in Apache solve this issue.

[Previous page](https://community.icinga.com/t/icinga2-director-unable-to-detect-your-icinga-2-core-version-deployformsbug7530-php-71/4851.md?page=1)
