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

DB_DUMP_PATH not set when using install.sh #2623

Merged
merged 1 commit into from
Sep 16, 2016

Conversation

tiagom62
Copy link
Contributor

Backup errors out when DB_DUMP_PATH is not set.

Starting backup...
Dumping database snipeit...
Backup failed because The dump process failed with exitcode 127 : Command not found : sh: 1: /usr/local/bin/mysqldump: not found
.
Backup completed!

According to https://snipe-it.readme.io/docs/configuration#required-database-settings this is usually '/usr/bin'

Tested on CentOS 7 and Ubuntu 16.04.1 LTS.

Backup errors out when DB_DUMP_PATH is not set. According to https://snipe-it.readme.io/docs/configuration#required-database-settings this is usually '/usr/bin'
@snipe snipe merged commit 08f320b into snipe:develop Sep 16, 2016
@snipe
Copy link
Owner

snipe commented Sep 16, 2016

Thanks!

@tiagom62 tiagom62 deleted the tiagom62-db-dump-path branch September 16, 2016 23:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants