torodb / stampede

The ToroDB solution to provide better analytics on top of MongoDB and make it easier to migrate from MongoDB to SQL
https://www.torodb.com/stampede/
GNU Affero General Public License v3.0
1.77k stars 120 forks source link

Have an issue using the `docker-compose` distribution of Stampede #181

Closed rychkog closed 7 years ago

rychkog commented 7 years ago

Hello!

Trying to run your docker-compose distribution, but have following in the terminal

mongodb_1          | 2017-05-15T05:44:21.280+0000 I REPL     [rsSync] transition to primary complete; database writes are now permitted
postgres_1         | FATAL:  role "torodb" does not exist
torodb-stampede_1  | 
torodb-stampede_1  | Connection to PostgreSQL Fatal error while ToroDB was starting: Was passed main parameter 'root' but no main parameter was defined:Fatal error while ToroDB was starting: Was passed main parameter 'root' but no main parameter was defined database Fatal error while ToroDB was starting: Was passed main parameter 'root' but no main parameter was defined with user postgres has failed!
torodb-stampede_1  | 
torodb-stampede_1  | Please, check PostgreSQL is running and, if connecting with TCP, the password for user postgres is correctly configured in /root/.pgpass
torodb-stampede_1  | Remember to set file permission correctly to 0600:
torodb-stampede_1  | chmod 0600 /root/.pgpass
torodb-stampede_1  | 
torodb-stampede_1  | To specify a user different than postgres to setup ToroDB Stampede specify it with environment variable ADMIN_USER:
torodb-stampede_1  | export ADMIN_USER=<PostgreSQL's administrator user name>
wiki_torodb-stampede_1 exited with code 1

As a consequence - cannot connect to the postgres using torodb user and torod database. All what I did is: 1) downloaded docker-compose.yml (as described in https://www.torodb.com/stampede/docs/1.0.0-beta2/installation/docker/) 2) executed docker-compose up

teoincontatto commented 7 years ago

Hi @rychkog !

Thanks for spotting this bug. We found a typo in the docker entry point script that was added accidentally somewhere in docker package deploy process.

We created an hotfix #182 to solve the issue and re-deployed the working package. Now it should work.