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

ValueError: badly formed hexadecimal UUID string and not valid salt #65

Open
lokalhorstkme opened this issue Dec 11, 2022 · 1 comment

Comments

@lokalhorstkme
Copy link

lokalhorstkme commented Dec 11, 2022

Could not get misp container to running state. Could you please give me a hint where my error in docker-compose.yml is?

using the original github docker-compose.yml
MISP_BASEURL: http://localhost:8080
MISP_UUID: 0a674a5a-c4cb-491d-80cf-5adb48b5c1cd # Please change for production
MISP_ORG: Testing org # Please change for production
MISP_MODULE_URL: http://misp-modules
MISP_EMAIL: ahoj@example.com # Please change for production

docker-compose start
Starting mysql ... done
Starting redis ... done
Starting misp-modules ... done
Starting misp ... done_

docker-compose ps
Name Command State Ports
misp /usr/local/bin/docker-entr ... Exit 1
misp-modules /home/misp-modules/.local/ ... Up (health: starting) 6666/tcp
misp-mysql docker-entrypoint.sh mariadbd Up 3306/tcp
misp-redis docker-entrypoint.sh redis ... Up 6379/tcp

Logs:
misp | Warning: 'SECURITY_SALT' environment variable should be at least 32 chars long
misp | Traceback (most recent call last):
misp | File "/usr/local/bin/misp_create_configs.py", line 398, in
misp | main()
misp | File "/usr/local/bin/misp_create_configs.py", line 352, in main
misp | uuid.UUID(variables["MISP_UUID"])
misp | File "/usr/lib64/python3.9/uuid.py", line 177, in init
misp | raise ValueError('badly formed hexadecimal UUID string')
misp | ValueError: badly formed hexadecimal UUID string
misp exited with code 1

@ondj
Copy link
Contributor

ondj commented Dec 21, 2022

Hello, thanks for report! Can you please try it with latest version? At least MISP should give you much better error message, because currently I don't understand why this doesn't work.

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

No branches or pull requests

2 participants