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

Transmission not starting in container #36

Closed
sgtsquiggs opened this issue Oct 29, 2015 · 4 comments
Closed

Transmission not starting in container #36

sgtsquiggs opened this issue Oct 29, 2015 · 4 comments

Comments

@sgtsquiggs
Copy link
Contributor

Not sure what's up, maybe a script is erroring out before it actually starts transmission. Here's the log:

<-- snip -->
STARTING TRANSMISSION
STARTING PORT UPDATER
Transmission startup script complete.
Thu Oct 29 15:07:13 2015 Initialization Sequence Completed
Generating new client id for PIA
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   106  100    14  100    92     15    103 --:--:-- --:--:-- --:--:--   103
Got new port 51575 from pia
transmission auth not required
Fatal: no entropy gathering module detected
Aborted
Fatal: no entropy gathering module detected
Aborted
Checking port...
Fatal: no entropy gathering module detected
Aborted
@sgtsquiggs
Copy link
Contributor Author

Here's what I get when executing transmission-daemon manually:

[/share/Containers/transmission/transmission-home] # docker exec -it transmission /bin/bash
root@61f88f0d6b19:/# exec /usr/bin/transmission-daemon -g ${TRANSMISSION_HOME} -f
Fatal: no entropy gathering module detected
[/share/Containers/transmission/transmission-home] #

@sgtsquiggs
Copy link
Contributor Author

And I've solved this.

root@61f88f0d6b19:/# ln -s /dev/urandom /dev/random
root@61f88f0d6b19:/# exec /usr/bin/transmission-daemon -g ${TRANSMISSION_HOME} --logfile ${TRANSMISSION_HOME}/transmission.log -f
^CClosing transmission session... done.
[/share/Containers/transmission/transmission-home] #

I'll be submitting a PR to symlink /dev/urandom to /dev/random in /etc/transmission/start.sh

@sgtsquiggs
Copy link
Contributor Author

Fatal: no entropy gathering module detected error fixed, but the container still won't successfully launch transmission. I see no errors in the log.

<-- snip -->
Thu Oct 29 15:50:52 2015 /sbin/ip addr add dev tun0 local 10.174.1.6 peer 10.174.1.5
Thu Oct 29 15:50:52 2015 /etc/transmission/start.sh tun0 1500 1542 10.174.1.6 10.174.1.5 init
Updating TRANSMISSION_BIND_ADDRESS_IPV4 to tun0 ip: 10.174.1.6
Generating transmission settings.json from env variables
STARTING TRANSMISSION
Thu Oct 29 15:50:52 2015 Initialization Sequence Completed

If I run transmission in the container manually from a shell, it starts successfully.

[/share/Containers/transmission/transmission-home] # docker exec -it transmission /bin/bash
root@61f88f0d6b19:/# /usr/bin/transmission-daemon -g ${TRANSMISSION_HOME} &
[1] 51
root@61f88f0d6b19:/#

@sgtsquiggs sgtsquiggs reopened this Oct 29, 2015
@sgtsquiggs
Copy link
Contributor Author

False alarm, the original fix does indeed fix this issue. I am just not very familiar with docker.

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

No branches or pull requests

2 participants