-
Notifications
You must be signed in to change notification settings - Fork 97
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
Crash when running in docker #113
Comments
yes, it uses boot to generate uuids, in this case probably to generate a tag on the To header. Seems like it might be related to this: I'll have to look into this |
Tell me if you need some more logs or debugging. I will try to build from source in the meantime. |
Yes, please let me know if you have an issue building from source on the latest develop branch. I don't expect you would, but let me know. On the docker crash, are you building your own image or using the one at docker.io ? |
I just tested a source build on the same machine, and it crashed in the same way, with the same config. The build itself went fine. I used the one on docker.io. I tried to build from the Dockerfile too, but it failed on build: |
OK, this is vanilla Debian 10 as far as you know, right? |
This is a machine that was dist-upgraded from a vanilla (as far as I know) Debian stretch to Debian buster. Have not tried it on a brand new install of Debian buster. |
I built a vanilla Debian 10 on GCP and sent it both a REGISTER and an INVITE (either would cause uuids to get generated) and was not able to recreate the crash. Can you let me know what you get when you run these commands on your machine
|
Argh, sorry for wasting your time. The meta-package |
No worries! |
By the way, off topic, but is there a community for Drachtio somewhere (IRC, forum...)? |
Great question. No, not at the moment. I was thinking creating one on slack, just have to find time do the part where I can have a link on the website to let people join without manual intervention (from me!) |
When using docker and the latest:
drachtio/drachtio-server:latest
I get the following crash immediately upon receipt of the first SIP message after starting the container.
2020-02-20 12:48:30.638434 processMessageStatelessly - incoming message with call-id 250bd0e165f914a9-1208@127.0.0.1 does not match an existing call leg, processed in thread 140531370149696
2020-02-20 12:48:30.638511 No connected clients found to handle incoming options request
2020-02-20 12:48:30.638565 processNewRequest - No providers available for OPTIONS
Uncaught exception: getrandom
Environment:
Debian 10 Buster
I'm guessing drachtio attempts to generate a tag or uuid of some sort and crashes.
The text was updated successfully, but these errors were encountered: