Grakn error on docker install
See original GitHub issueThis is the latest git pull on Ubuntu 18.
Ran command sudo docker-compose up (–compatibility didn’t work for me)
I should also mention I am running this on the same box I have MISP installed.
opencti_1 | Waiting Grakn to launch...
worker-import_1 | INFO:root:Message (type=stix2-bundle, delivery_tag=51) processed, thread terminated
worker-import_1 | INFO:root:Processing a new message (type=stix2-bundle, delivery_tag=52), launching a thread...
worker-import_1 | INFO:root:Importing a marking-definition
worker-import_1 | ERROR:root:An unexpected error occurred: { ('Connection aborted.', BrokenPipeError(32, 'Broken pipe')) }
worker-import_1 | INFO:root:Message (type=stix2-bundle, delivery_tag=51) processed, thread terminated
worker-import_1 | INFO:root:Processing a new message (type=stix2-bundle, delivery_tag=52), launching a thread...
worker-import_1 | INFO:root:Marking definitions imported in: 0secs
worker-import_1 | INFO:root:Importing a identity
worker-import_1 | ERROR:root:An unexpected error occurred: { ('Connection aborted.', BrokenPipeError(32, 'Broken pipe')) }
worker-import_1 | INFO:root:Message (type=stix2-bundle, delivery_tag=52) processed, thread terminated
worker-import_1 | INFO:root:Processing a new message (type=stix2-bundle, delivery_tag=53), launching a thread...
worker-import_1 | INFO:root:Importing a marking-definition
worker-import_1 | ERROR:root:An unexpected error occurred: { ('Connection aborted.', BrokenPipeError(32, 'Broken pipe')) }
worker-import_1 | INFO:root:Message (type=stix2-bundle, delivery_tag=52) processed, thread terminated
worker-import_1 | INFO:root:Processing a new message (type=stix2-bundle, delivery_tag=53), launching a thread...
worker-import_1 | INFO:root:Marking definitions imported in: 0secs
worker-import_1 | INFO:root:Importing a identity
worker-import_1 | ERROR:root:An unexpected error occurred: { ('Connection aborted.', BrokenPipeError(32, 'Broken pipe')) }
Thanks!
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
vaticle typedb - How to create a grakn schema right after ...
When you add command in your service definition, existing command of the image (originally, grakn-docker.sh ) got replaced.
Read more >Troubleshoot Docker Engine installation
Diagnose and resolve error messages related to the Docker Engine installation. ... This error may indicate: The Docker daemon isn't running on your...
Read more >New error installing (docker) - Google Groups
Creating a new AtoM installation from docker, I got this new error message: creating libtool appending configuration tag "CXX" to libtool
Read more >Unraid upgrade
Upgrade GitLab using Docker Engine. To upgrade GitLab that was installed ...Basically turn off docker, VMs and anything else that uses the cache...
Read more >iReady-Overload. It's the worst education tool anyone could ...
Add a description, image, and links to the iready-hack topic page so that ... I-ready overload 0. cupiditys/iReady-Overload. aeg i30 error reset docker...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@richard-julien thank you so much for your patience!!!
I ran
ctrl-a-d to exit screen
… this is really cool! For whatever reason it’s working now… no idea why, but I’ll take it.
Got a problems with the MISP connector but I’ll start another ticket with that one.
Again, very cool and thank you!
You can access the logs with the command
docker logs [CONTAINER_ID]You can obtain the CONTAINER_ID with the command
docker psUse the docker logs command to get all the logs of the grakn container, it could be useful to know exactly why Grakn cant start.