Closed (fixed)
Project:
Drush
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 May 2009 at 20:33 UTC
Updated:
16 Jun 2009 at 16:00 UTC
I just installed drush on a new server from head and the oh so nice info, sql and other commands didn't work (just gave me back a command prompt). using -v param didn't made any difference. Are they not working for others right now? My head version from a few weeks ago seemed to work fine.
So, I tried to install the alpha release instead, and all the extra goodies were gone. Are they only in head?
Thanks again for the folks working hard on this. I made a drush like bash script for myself to install drupal core (and drush :) and then would use drush after that. This now has that feature ans more. kudos all around!
Comments
Comment #1
frankcarey commentedbtw, dl was working fine (though it did put the module in /default instead of /all)...
Comment #2
moshe weitzman commentedplease be specific. copy what you typed in and what came out. also include contents of `drush help`. also make sure you have wiped all traces of drush_extras and the old drush module.
Comment #3
frankcarey commentedsure, i'll do that now. I figured this might be something obvious.
Comment #4
frankcarey commented6.2.0-aplpha 2 output: no cool extra commands like "info" and "sql" taht i was using in head.
Execute a drush command. Run `drush help [command]` to view command-specific
help.
Examples:
drush dl cck zen Download CCK module and Zen theme.
drush --uri=http://example.com status Show status command for the example.com multi-site.
Options:
-r
, --root=
Drupal root directory to use (default: current directory)
-l , --uri= URI of the drupal site to use (only needed in multisite environments)
-v, --verbose Display all available output
-q, --quiet Hide all output
-y, --yes Assume 'yes' as answer to all prompts
-s, --simulate Simulate all relevant actions (don't actually change the system)
-i, --include A list of paths to search for drush commands
-c, --config Specify a config file to use. See example.drushrc.php
-u, --user Specify a user to login with. May be a name or a number.
-b, --backend Hide all output and return structured data (internal use only).
Commands:
dl Download core Drupal and projects like CCK, Zen, etc.
help Print this help message. Use --filter to limit command list to one command file (e.g. --filter=pm)
status Provides a birds-eye view of the current Drupal installation, if any.
Comment #5
frankcarey commentedhead version (using cvs -up HEAD): there are all the nice goodies
Execute a drush command. Run `drush help [command]` to view command-specific
help.
Examples:
drush dl cck zen Download CCK module and Zen theme.
drush --uri=http://example.com status Show status command for the example.com multi-site.
drush help --pipe A space delimited list of commands
Options:
-r
, --root=
Drupal root directory to use (default: current directory)
-l , --uri= URI of the drupal site to use (only needed in multisite environments)
-v, --verbose Display all available output
-q, --quiet Hide all output
-y, --yes Assume 'yes' as answer to all prompts
-s, --simulate Simulate all relevant actions (don't actually change the system)
-i, --include A list of paths to search for drush commands
-c, --config Specify a config file to use. See example.drushrc.php
-u, --user Specify a user to login with. May be a name or a number.
-b, --backend Hide all output and return structured data (internal use only).
-p, --pipe Emit a compact representation of the command for scripting.
Commands:
test mail Run all tests and mail the results to your team.
test clean Delete leftover tables and files from prior test runs.
enable Enable one or more modules.
disable Disable one or more modules.
uninstall Uninstall one or more modules.
statusmodules Show module enabled/disabled status
refresh Refresh update status information
updatecode Update your project code
update Update your project code and apply any database updates required (update.php)
info Release information for a project
dl Download core Drupal and projects like CCK, Zen, etc.
sql conf Print database connection details.
sql connect A string for connecting to the DB.
sql dump Exports the Drupal DB as SQL using mysqldump.
sql query Execute a query against the site database.
sql load Copy source database to target database.
sql cli Open a SQL command-line interface using Drupal’s credentials.
help Print this help message. Use --filter to limit command list to one command file (e.g. --filter=pm)
cron Run all cron hooks.
updatedb Execute the update.php process from the command line
status Provides a birds-eye view of the current Drupal installation, if any.
script Run php script(s).
cache clear Clear all caches.
watchdog show Shows recent watchdog log messages. Optionally filter for a specific type.
watchdog delete Delete all messages or only those of a specified type.
sync Rsync the Drupal tree to/from another server using ssh.
eval Evaluate arbitrary php code after bootstrapping Drupal.
Comment #6
frankcarey commenteddrush/install/dir/ $ drush sql cli
A Drupal installation directory could not be found [error]
Command sql cli needs a higher bootstrap level to run - you will need invoke drush from a more functional Drupal environment to [error]
run this command.
The command 'drush sql cli' could not be executed.
Gives me an error, but of course it does, cause it's I'm not in my drupal dir and not using any flags
Comment #7
frankcarey commentedmy/drupal/dir$ drush sql cli
returns... nothing...
my/drupal/dir$(blank)
---------------------
my/drupal/dir$ drush help
drush help
Execute a drush command. Run `drush help [command]` to view command-specific
help.
Examples:
drush dl cck zen Download CCK module and Zen theme.
drush --uri=http://example.com status Show status command for the example.com multi-site.
drush help --pipe A space delimited list of commands
Options:
-r
, --root=
Drupal root directory to use (default: current directory)
-l , --uri= URI of the drupal site to use (only needed in multisite environments)
-v, --verbose Display all available output
-q, --quiet Hide all output
-y, --yes Assume 'yes' as answer to all prompts
-s, --simulate Simulate all relevant actions (don't actually change the system)
-i, --include A list of paths to search for drush commands
-c, --config Specify a config file to use. See example.drushrc.php
-u, --user Specify a user to login with. May be a name or a number.
-b, --backend Hide all output and return structured data (internal use only).
-p, --pipe Emit a compact representation of the command for scripting.
Commands:
test mail Run all tests and mail the results to your team.
test clean Delete leftover tables and files from prior test runs.
enable Enable one or more modules.
disable Disable one or more modules.
uninstall Uninstall one or more modules.
statusmodules Show module enabled/disabled status
refresh Refresh update status information
updatecode Update your project code
update Update your project code and apply any database updates required (update.php)
info Release information for a project
dl Download core Drupal and projects like CCK, Zen, etc.
sql conf Print database connection details.
sql connect A string for connecting to the DB.
sql dump Exports the Drupal DB as SQL using mysqldump.
sql query Execute a query against the site database.
sql load Copy source database to target database.
sql cli Open a SQL command-line interface using Drupal’s credentials.
help Print this help message. Use --filter to limit command list to one command file (e.g. --filter=pm)
cron Run all cron hooks.
updatedb Execute the update.php process from the command line
status Provides a birds-eye view of the current Drupal installation, if any.
script Run php script(s).
cache clear Clear all caches.
watchdog show Shows recent watchdog log messages. Optionally filter for a specific type.
watchdog delete Delete all messages or only those of a specified type.
sync Rsync the Drupal tree to/from another server using ssh.
eval Evaluate arbitrary php code after bootstrapping Drupal.
--------------------------
Comment #8
owen barton commentedThese commands need a Drupal site to run at all - as indicated by the error in the HEAD version. Put yourself in the Drupal directory you want, or pass the -r or -l options, and it will work.
Comment #9
frankcarey commentedI realized, but at least is was giving some output
in # 6 i said "Gives me an error, but of course it does, cause it's I'm not in my drupal dir and not using any flags"
I tried it then from my drupal dir and that was represented in comment #7 (my/drupal/dir$)
....
my/drupal/dir$ drush sql cli
returns... nothing...
my/drupal/dir$(blank)
---------------------
my/drupal/dir$ drush help
...
Thanks for the help though. Odd that it give NO output. no errors, nothing. even the -v option gives nothing.
Comment #10
frankcarey commentedto clarify , "drush help" and "drush dl" DO WORK.
Comment #11
frankcarey commentedupdated back to head today. drush sql and others still not working. Drush status works, so it has the info it needs to connect, but "drush sql cli " does nothing, so does "drush sql cli".
$ drush status
Drupal Root : /websites/-snip-/docs
Drupal version : 6.12
Site Path : sites/default
Site URI : http://default
Database Driver : mysqli
Database Hostname : localhost
Database Username : -snip-
Database Name : -snip-
Database Password : -snip-
Database : Connected
Drupal Bootstrap : Successful
Drupal User : Anonymous
I really love the new features. Is there any logging or debug state that I can turn on to get to the bottom of this?
Also, no one gave me an answer yet about the releases not having the new features, is that correct, that they don't have 80% of the new features? (compare comment #4 to #5)
Comment #12
frankcarey commenteduggg. I just installed drush 2.0, again and I have all the commands again, but now NONE of them work except just 'drush'. I get no error, nothing in response. If i go to the drush installation dir (~/.drush/ it will throw an error at least, obviously i'm not in the webroot.. ) Why would it give NO OUTPUT? not even an error??
Comment #13
frankcarey commentedwhen i do drush info -v
drush info -v
Initialized Drupal 6.12 root directory at [notice]
/home/blah/mysite.com
Initialized Drupal site default at sites/default [notice]
but i don't get the info....
Comment #14
frankcarey commenteddrush info -d
Drush bootstrap phase : _drush_bootstrap_drupal_root() [0.014 sec] [bootstrap]
Initialized Drupal 6.12 root directory at [notice]
/home/blah/mysite.com [0.022 sec]
Drush bootstrap phase : _drush_bootstrap_drupal_site() [0.023 sec] [bootstrap]
Initialized Drupal site default at sites/default [0.151 sec] [notice]
Comment #15
frankcarey commented[FIXED]
Turns out that I had errors in my php log file related to the coder modules drush integration. Not what I expected because drush WAS outputting some info.
Related Issues:
#479814: Call to undefined function t() in ...sites/all/modules/coder/coder.drush.inc on line 10
#471874: coder.drush.inc should declare coder as dependency
Thanks to the folks who were trying to help. Others having issues with missing output should remember to check their php error logs and see if anything show up.