Netty SecureRandom issue about pushy HOT 19 CLOSED

Can you be more specific about when this happens? Is it at startup, shutdown, or during normal operation? Are there any other clues as to what's going on nearby in the log?

from pushy.

…also, what operating system are you using?

EDIT: oops. Missed the "centos 6" bit above. Sorry!

from pushy.

Scratch that; looks like this is a known issue. See netty/netty#2412. A fix has been merged upstream and should be released in Netty 4.0.19.

from pushy.

It is at startup.
will try the Netty 4.0.19 very soon.

Thanks

from pushy.

@patrixgdd We've updated to Netty 4.0.19 in 465777a. Would you mind trying a snapshot from master and seeing if that fixes the problem on your end?

from pushy.

@patrixgdd Just checking in. Did the 4.0.19 update solve this problem for you?

Thanks!

from pushy.

Since I can't reproduce the problem after the 4.0.19 update, I'm going to go ahead and call this fixed. @patrixgdd please post a comment here if you're still having trouble and we'll revisit the issue.

from pushy.

I'm having this problem on a virtual machine (with a possibly slow CPU) with 4.0.19 when Netty starts up. Any idea what's going on?

from pushy.

I found if the port is taken, the issue will be throwed.
you can check with : netstat -tlnp

from pushy.

Interesting. Sounds like this is still an upstream (Netty) issue, though. @neil-mao I'll see if I can get a minimal test case together, unless you'd like to do so.

Thanks for the additional details!

from pushy.

Wait; this doesn't quite make sense now that I'm thinking about it more. @neil-mao which port are you talking about?

from pushy.

I encounter the problem today when run Netty on Intel Atom box.
I use netty for mini http server on the port 19080.

When the problem happened, I saw the netty process is not quit cleanly and the port is taken .
Please see my log:

2014-10-31 22:31:16,398 WARN [io.netty.util.internal.ThreadLocalRandom] 136 - Failed to generate a seed from SecureRandom within 3 seconds. Not enough entrophy?

[agent@localhost wifi2]$ netstat -tlnp
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:19080 0.0.0.0:* LISTEN 6648/java
[agent@localhost wifi2]$ kill 6648

from pushy.

BTW: I am using netty 4.0.20.Final

from pushy.

@neil-mao I'm not sure how relevant that is to this case. It certainly sounds like an issue with Netty, and it might make sense to report it as a bug there. Pushy doesn't actually try to bind to any specific port, though, so I don't think that's the root cause here.

from pushy.

understood. I am not sure how it happed.
I will keep watching and if the issue happed again, I will get the stack.

Thanks

from pushy.

I saw the issue again.

2015-09-15 21:03:28,470 WARN [io.netty.util.internal.ThreadLocalRandom] 136 - Failed to generate a seed from SecureRandom within 3 seconds. Not enough entrophy?

The application is running under ARM cpu.

agent@agentpi:~/agent$ uname -a
Linux agentpi 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux

java -version
java version "1.8.0"
Java(TM) SE Runtime Environment (build 1.8.0-b132)
Java HotSpot(TM) Client VM (build 25.0-b70, mixed mode)

Netty version:
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:35:31 +0200

netty-transport-rxtx.version=4.0.20.Final
netty-transport-rxtx.buildDate=2014-06-12 16:35:31 +0200
netty-transport-rxtx.commitDate=2014-06-12 16:14:48 +0200
netty-transport-rxtx.shortCommitHash=1709113
netty-transport-rxtx.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-transport-rxtx.repoStatus=clean
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:28:52 +0200

netty-common.version=4.0.20.Final
netty-common.buildDate=2014-06-12 16:28:52 +0200
netty-common.commitDate=2014-06-12 16:14:48 +0200
netty-common.shortCommitHash=1709113
netty-common.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-common.repoStatus=clean
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:30:14 +0200

netty-buffer.version=4.0.20.Final
netty-buffer.buildDate=2014-06-12 16:30:14 +0200
netty-buffer.commitDate=2014-06-12 16:14:48 +0200
netty-buffer.shortCommitHash=1709113
netty-buffer.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-buffer.repoStatus=clean
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:31:11 +0200

netty-transport.version=4.0.20.Final
netty-transport.buildDate=2014-06-12 16:31:11 +0200
netty-transport.commitDate=2014-06-12 16:14:48 +0200
netty-transport.shortCommitHash=1709113
netty-transport.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-transport.repoStatus=clean
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:35:03 +0200

netty-codec-socks.version=4.0.20.Final
netty-codec-socks.buildDate=2014-06-12 16:35:03 +0200
netty-codec-socks.commitDate=2014-06-12 16:14:48 +0200
netty-codec-socks.shortCommitHash=1709113
netty-codec-socks.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-codec-socks.repoStatus=clean
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:33:27 +0200

netty-handler.version=4.0.20.Final
netty-handler.buildDate=2014-06-12 16:33:27 +0200
netty-handler.commitDate=2014-06-12 16:14:48 +0200
netty-handler.shortCommitHash=1709113
netty-handler.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-handler.repoStatus=clean
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:32:48 +0200

netty-codec.version=4.0.20.Final
netty-codec.buildDate=2014-06-12 16:32:48 +0200
netty-codec.commitDate=2014-06-12 16:14:48 +0200
netty-codec.shortCommitHash=1709113
netty-codec.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-codec.repoStatus=clean
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:33:59 +0200

netty-codec-http.version=4.0.20.Final
netty-codec-http.buildDate=2014-06-12 16:33:59 +0200
netty-codec-http.commitDate=2014-06-12 16:14:48 +0200
netty-codec-http.shortCommitHash=1709113
netty-codec-http.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-codec-http.repoStatus=clean
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:36:13 +0200

netty-transport-udt.version=4.0.20.Final
netty-transport-udt.buildDate=2014-06-12 16:36:13 +0200
netty-transport-udt.commitDate=2014-06-12 16:14:48 +0200
netty-transport-udt.shortCommitHash=1709113
netty-transport-udt.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-transport-udt.repoStatus=clean
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:35:49 +0200

netty-transport-sctp.version=4.0.20.Final
netty-transport-sctp.buildDate=2014-06-12 16:35:49 +0200
netty-transport-sctp.commitDate=2014-06-12 16:14:48 +0200
netty-transport-sctp.shortCommitHash=1709113
netty-transport-sctp.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-transport-sctp.repoStatus=clean

from pushy.

Firewall blocking the ports causes the issue in redhat. Cleared up by adding ports to the intended interface in firewalld.
firewall-cmd --zone=public --add-port=52489/tcp

Just thought I'd respond with how I fixed it on my system.

from pushy.

http://stackoverflow.com/questions/28173570/conditions-for-lack-of-entophy-in-threadlocalrandom

cat /proc/sys/kernel/random/entropy_avail
391

Normally,It is large number,when the issue happens, it is small,just 29 .

from pushy.

http://askubuntu.com/questions/99144/how-can-i-permantly-increase-the-entropy-avail-level

sudo apt-get install haveged -y

It works for me now. really great.

from pushy.