Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.With a fresh git clone I am getting this error on one of my sites which has recently been updated. I cannot debug further than running --debug which doesn't show much info.
drush --debug
Bootstrap to phase 0. [0 sec, 2.12 MB] [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drush() [0.01 sec, 2.25 MB] [bootstrap]
Cache HIT cid: 6.0-dev-commandfiles-0-bd168dad386781832950a73b3d4bbbec [0.01 sec, 2.27 MB] [debug]
Unknown engine type outputformat [0.03 sec, 4.56 MB] [error]
Unknown engine type outputformat [0.03 sec, 4.61 MB] [error]
Unknown engine type outputformat [0.03 sec, 4.63 MB] [error]
Unknown engine type outputformat [0.03 sec, 4.64 MB] [error]
Unknown engine type outputformat [0.04 sec, 5.04 MB] [error]
Bootstrap to phase 0. [0.04 sec, 5.64 MB] [bootstrap]
Unknown engine type outputformat [0.04 sec, 5.89 MB] [error]
Unknown engine type outputformat [0.04 sec, 5.94 MB] [error]
Unknown engine type outputformat [0.04 sec, 5.96 MB] [error]
Unknown engine type outputformat [0.04 sec, 5.97 MB] [error]
Unknown engine type outputformat [0.05 sec, 6.37 MB] [error]
Bootstrap to phase 0. [0.06 sec, 5.65 MB] [bootstrap]
Found command: help (commandfile=core) [0.06 sec, 5.66 MB] [bootstrap]
Unknown engine type outputformat [0.06 sec, 5.91 MB] [error]
Unknown engine type outputformat [0.06 sec, 5.97 MB] [error]
Unknown engine type outputformat [0.06 sec, 5.98 MB] [error]
Unknown engine type outputformat [0.06 sec, 6 MB] [error]
Unknown engine type outputformat [0.06 sec, 6.39 MB] [error]
Command dispatch complete [0.07 sec, 5.68 MB] [notice]
Peak memory usage was 7.04 MB [0.07 sec, 5.67 MB]
Comments
Comment #1
greg.1.anderson CreditAttribution: greg.1.anderson commentedA lot of people are going to run into this -- I should have figured out a way to fix it.
The theoretical solution is
drush cc drush; unfortunately, the error above causes that command to fail before the cc drush can run to fix the problem.The temporary workaround is
rm -rf $HOME/.drush/cache. I should find a more permanent solution, so folks can pull 8.x-6.x without getting wedged.Comment #2
greg.1.anderson CreditAttribution: greg.1.anderson commentedIf you read this before you pull, running
drush cc drushjust beforegit pullshould also do the trick.Comment #3
likewhoa CreditAttribution: likewhoa commentedno, i didn't get to run cc all before the pull but the workaround works, thanks.
Comment #4
greg.1.anderson CreditAttribution: greg.1.anderson commentedFixed in 50f0c0e; it is now safe to pull 8.x-6.x again.
If you are already experiencing this error, pull again, and the problem should go away.