Skip to content
This repository has been archived by the owner on May 30, 2018. It is now read-only.

demon.sh install error #39

Open
bosungs2y opened this issue Nov 9, 2017 · 4 comments
Open

demon.sh install error #39

bosungs2y opened this issue Nov 9, 2017 · 4 comments

Comments

@bosungs2y
Copy link

It can not be installed via kolide-quickstart script.
What is the problem?

Command

./demon.sh simple up

Error Log

Creating kolidequickstart_redis_1 ...
Creating kolidequickstart_mailhog_1 ...
Creating kolidequickstart_mysql_1 ...
Creating kolidequickstart_redis_1
Creating kolidequickstart_mysql_1
Creating kolidequickstart_mysql_1 ... done
Creating kolidequickstart_fleet_1 ...
Creating kolidequickstart_fleet_1 ... done
Waiting for MySQL to accept connections...

Waiting for Fleet server to accept connections.....................................................Error: Kolide failed to start up. Exiting.

docker ps -a

6fba3efc9c97        /kolide/fleet:latest      "sh -c 'echo '\\n' | /"   About a minute ago   Exited (1) About a minute ago                                      kolidequickstart_fleet_1
5fb4f8838bd1        /mysql:5.7                "docker-entrypoint.sh"    About a minute ago   Up About a minute               3306/tcp                           kolidequickstart_mysql_1
f7e9b6ca1784        /mailhog/mailhog:latest   "MailHog"                 About a minute ago   Up About a minute               1025/tcp, 0.0.0.0:8025->8025/tcp   kolidequickstart_mailhog_1
ad174071632d        /redis:3.2.4              "docker-entrypoint.sh"    About a minute ago   Up About a minute               6379/tcp                           kolidequickstart_redis_1
@groob
Copy link
Contributor

groob commented Nov 9, 2017

Note: If you want to enroll the macOS host that this demo is running on you may have to edit the /etc/hosts file as specified in the output when generating the installer.

Did you do this yet? to connect to the fleet server, /etc/hosts should have a fleet entry.

@Maanpreet
Copy link

Maanpreet commented Jan 14, 2018

I'm facing same issue, Can't get it working,

Command
./demo.sh simple up

Starting kolidequickstart_redis_1 ...
Starting kolidequickstart_mysql_1 ...
Starting kolidequickstart_mailhog_1 ... done
Starting kolidequickstart_fleet_1 ... done
Waiting for MySQL to accept connections....
Waiting for Fleet server to accept connections.....................................................Error: Kolide failed to start up. Exiting.

This is what docker compose logs are complaining at the end

mysql_1 | 2018-01-14T00:47:06.782217Z 4 [Note] Aborted connection 4 to db: 'kolide' user: 'kolide' host: '172.18.0.5' (Got an error reading communication packets)
mysql_1 | 2018-01-14T00:47:06.795175Z 5 [Note] Aborted connection 5 to db: 'kolide' user: 'kolide' host: '172.18.0.5' (Got an error reading communication packets)

@ashvinashoke
Copy link

Manpreet, my issue was similar to yours if not the exact same. My Kolide App URL was set to the correct IP and port number, but the security group I had assigned to my EC2 instance wasn't configured properly. After adding my kolide app URL as an inbound rule and assigning an elastic IP to my instance, Kolide was able to start up properly.

@juandanielpujols
Copy link

I made it work doing this:

  1. "docker ps -a" showed an exited container kolidequickstart_fleet_1
  2. "docker logs kolidequickstart_fleet_1" show "# A value must be supplied for --auth_jwt_key. This value is used to create...Consider using the following randomly generated key: tmvRVUPGasdffAYtWuGZ9Rzf"
  3. copy key value
  4. vi kolide.yml, in the auth section paste the key
  5. docker rm -f $(docker ps -a)
  6. ./demo.sh up

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

No branches or pull requests

5 participants