# Updating pretty old director results in error: "Director is not configured correctly" **URL:** \ **Category:** Icinga Director\ **Created:** [April 26, 2019, 8:14am UTC](https://community.icinga.com/t/updating-pretty-old-director-results-in-error-director-is-not-configured-correctly/1029 "2019-04-26T08:14:37Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![voddIt](https://community.icinga.com/letter_avatar_proxy/v4/letter/v/51bf81/32.png) [@voddIt](https://community.icinga.com/u/voddIt)\ **Post date:** [April 26, 2019, 8:14am UTC](https://community.icinga.com/t/updating-pretty-old-director-results-in-error-director-is-not-configured-correctly/1029/1 "2019-04-26T08:14:37Z")
Hi folks, I am running a pretty outdated version of the director ( commit 50591213 from Jul’18 ) which I updated yesterday to the latest version of the master-branch ( commit fe53dee2 ). What I did is moving the outdated director-folder in `/usr/share/icingaweb2/modules/` to a save place and clone the repository from github in there (again). That worked so far and the director tells men that `There are 12 pending schema migrations`. When I start the migration-command I get the following error - does anybody know how to fix this? ``` icingacli director migration run --verbose ERROR: RuntimeException in /usr/share/icingaweb2/modules/director/library/Director/Cli/Command.php:114 with message: Director is not configured correctly ``` ---
**Author:** ![dnsmichi](https://community.icinga.com/user_avatar/community.icinga.com/dnsmichi/32/7721_2.png) [@dnsmichi](https://community.icinga.com/u/dnsmichi)\ **Post date:** [April 26, 2019, 8:43am UTC](https://community.icinga.com/t/updating-pretty-old-director-results-in-error-director-is-not-configured-correctly/1029/2 "2019-04-26T08:43:09Z")
Moving from git master to git master is a pretty bad idea, there’s no-one testing this procedure compared to released and tagged versions. I’d try to use 1.6.2 being the latest release instead. Cheers, Michael ---
**Author:** ![voddIt](https://community.icinga.com/letter_avatar_proxy/v4/letter/v/51bf81/32.png) [@voddIt](https://community.icinga.com/u/voddIt)\ **Post date:** [April 26, 2019, 8:59am UTC](https://community.icinga.com/t/updating-pretty-old-director-results-in-error-director-is-not-configured-correctly/1029/3 "2019-04-26T08:59:06Z")
OK, I just recloned the repo and specified the tag for version 1.6.2 but the error stays the same 🙁 BTW: There are only 9 Pending migrations left by now… ---
**Author:** ![dnsmichi](https://community.icinga.com/user_avatar/community.icinga.com/dnsmichi/32/7721_2.png) [@dnsmichi](https://community.icinga.com/u/dnsmichi)\ **Post date:** [April 26, 2019, 9:07am UTC](https://community.icinga.com/t/updating-pretty-old-director-results-in-error-director-is-not-configured-correctly/1029/4 "2019-04-26T09:07:09Z")
No idea, sorry. I don’t use git master for that very reason of breaking things on upgrade. Maybe @tgelf knows more about this specific commit, or changes in git master causing this. Cheers, Michael ---
**Author:** ![mfrosch](https://community.icinga.com/user_avatar/community.icinga.com/mfrosch/32/12_2.png) [@mfrosch](https://community.icinga.com/u/mfrosch)\ **Post date:** [April 26, 2019, 10:46am UTC](https://community.icinga.com/t/updating-pretty-old-director-results-in-error-director-is-not-configured-correctly/1029/5 "2019-04-26T10:46:21Z")
> [@voddIt](#): > > Director is not configured correctly This basically means that no DB connection is configured for Director. Please show us the contents of `/etc/icingaweb2/modules/director/config.ini` The thing is, if your Webinterface is showing pending migrations, but your CLI tool brings this error, there must be something wrong with your setup… How did you install Icinga Web 2, OS Environment, any special paths? ---
**Author:** ![mfrosch](https://community.icinga.com/user_avatar/community.icinga.com/mfrosch/32/12_2.png) [@mfrosch](https://community.icinga.com/u/mfrosch)\ **Post date:** [April 26, 2019, 10:47am UTC](https://community.icinga.com/t/updating-pretty-old-director-results-in-error-director-is-not-configured-correctly/1029/6 "2019-04-26T10:47:18Z")
Or just: Which user is running `icingacli`? Is this user able to read/write `/etc/icingaweb2`? ---
**Author:** ![voddIt](https://community.icinga.com/letter_avatar_proxy/v4/letter/v/51bf81/32.png) [@voddIt](https://community.icinga.com/u/voddIt)\ **Post date:** [April 26, 2019, 10:58am UTC](https://community.icinga.com/t/updating-pretty-old-director-results-in-error-director-is-not-configured-correctly/1029/7 "2019-04-26T10:58:20Z")
Guys, I figured it out. It was in fact a DB-Issue. The standard-User, configured in the backend had no owner-rights on the scheme. Confing the db-owner in the connection-settings (had to make sure director-db is default schema) resulted in success.