sathyajackson

i tried to install the same in a fresh machine and i am now getting the below python execption. ===> pulling the docker containers Traceback (most recent call last): File...

Hi thanks for the input. I have already configured the Access_key and secreat_key using aws cli on the same server where i am running trackit. Still when i start the...

Yes I do with start.sh

Yes, I do have that and I even check the credentials and I works fine with aws-cli

I get the following error Traceback (most recent call last): File "./awsenv", line 31, in main(profile, cmd) File "./awsenv", line 16, in main profile_config = get_profile_config(profile) File "./awsenv", line 13,...

sorry for the above statement. Now i got to see what is expected. AWS_CLOUDWATCH_HOME AWS_PATH AWS_AUTO_SCALING_HOME AWS_ELB_HOME AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY

Alrite here you go. ``` ./start.sh ===> checking vm.max_map_count setting ===> updating git submodules Adding existing repo at 'trackit2-client' to the index Adding existing repo at 'trackit-server' to the index...

Yes still cant login here are the logs of docker-compose. ``` WARNING: The AWS_ACCESS_KEY_ID variable is not set. Defaulting to a blank string. WARNING: The AWS_SECRET_ACCESS_KEY variable is not set....

Please ignore my previous comment, I see the elastic search is not running. Let me fix that and update you with the latest logs.

Here you go complete logs from all containers. ``` docker-compose logs -f WARNING: The AWS_ACCESS_KEY_ID variable is not set. Defaulting to a blank string. WARNING: The AWS_SECRET_ACCESS_KEY variable is not...