Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup problems #36

Closed
bcamac opened this issue Feb 26, 2015 · 3 comments
Closed

Setup problems #36

bcamac opened this issue Feb 26, 2015 · 3 comments
Assignees
Labels

Comments

@bcamac
Copy link

bcamac commented Feb 26, 2015

Following the wiki (https://corpwiki.appnexus.com/display/engineering/How+To+Use+The+%27schema%27+Script) and got to the point of 'schema rebuild' which fails with:

Bringing all the way down
Downgraded

Bringing all the way back up
Running alter: 137823105930-init-up.sql
An exception has occurred... Sorry. You should file a ticket in
our issue tracker: http://github.com/appnexus/schema-tool/issues

Error: 2, No such file or directory

Anyway to get more details about which file/directory its looking for?
BTW, the file 137823105930-init-up.sql does exist in the directory.

@JohnMurray
Copy link
Contributor

@bcamac You could try running the command with the -v option.

Additionally, it doesn't seem like it's running any of the down alters. Have any been applied yet? If not, you could try running with schema up and see how that works. The tool uses the actual mysql and postgres binaries to perform it's operations (aside from reading the current DB state) so it might be that it cannot find the correct binary. Could you run the following commands for me (and share the results):

  • which mysql
  • which psql

Also, could you share the contents of your config.json?

@JohnMurray JohnMurray self-assigned this Feb 27, 2015
@JohnMurray JohnMurray added the bug label Feb 27, 2015
@bcamac
Copy link
Author

bcamac commented Feb 27, 2015

Your instincts were correct. Turned out neither mysql nor psql were in the shell's path (its a new machine setup). After adding it to the path schema tool proceeds past that point.
schema rebuild --force then worked (a few errors but its ok).
Problem solved. Thanks for your assistance.

@bcamac bcamac closed this as completed Feb 27, 2015
@JohnMurray
Copy link
Contributor

@bcamac glad all is working now. I'll add a ticket to provide more helpful error messages for this particular error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants