I have followed steps as mentioned in the usage section of below page
https://www.drupal.org/project/drupalmoduleupgrader

But when I try to run command in step 2 I get following error
The drush command 'dmu-analyze xxx' could not be found. Run `drush cache-clear drush` to clear the commandfile cache if you have installed new extensions. [error]
Drush was not able to start (bootstrap) the Drupal database.

Hint: This may occur when Drush is trying to:
* bootstrap a site that has not been installed or does not have a configured database. In this case you can select another site with a working database setup by specifying the URI
to use with the --uri parameter on the command line. See `drush topic docs-aliases` for details.
* connect the database through a socket. The socket file may be wrong or the php-cli may have no access to it in a jailed shell. See http://drupal.org/node/1428638 for details.

Anyone please help.

Comments

parth.kukadiya created an issue. See original summary.

HongPong’s picture

Title: dmu-analyze command not found » dmu-analyze command not found / Drush was not able to start (bootstrap) the Drupal database

You may be trying to operate in a directory that is not an active Drupal site. The information on drush status should help you here.

webchick’s picture

Hey @HongPong, thanks for helping out. This is off-topic, but would you like co-maintainer access on this module? :)

HongPong’s picture

Sure! I am still getting the hang of it but I did tune up the documentation today. I have some interest in finding ways to give better error messages if nothing else. (please let me know if anything I put in the doc here is wrong)

https://www.drupal.org/documentation/modules/drupalmoduleupgrader

I have been on a kick lately updating 7 modules to 8 so this would make it more interesting.

Best regards!

webchick’s picture

Docs improvements seem great to me, and you now have the commit bit! Woohoo! :D Thanks so much!

HongPong’s picture

Status: Active » Closed (works as designed)

Alright thank you :)

I am closing this issue as "works as designed" since it is supposed to be run inside an regular Drupal site environment.
parth.kukadiya please reopen if there is some further issue on this matter to consider.

LynetteW’s picture

I had the same message pop-up for me as well, following all the steps in the drupalmoduleupgrader documentation. What I ended up doing was adding mysql path to the environmental variables on my Windows machine. That seemed to fix my problem. How I found that was adding a --debug to drush (drush --debug en drupalmoduleupgrader), because it also seemed like drush en wasn't working either, but other drush commands were.

Drush command was dying on a mysql command.

Hope this will help others.