aMule Forum

English => en_Bugs => Topic started by: foreman on April 15, 2009, 08:55:25 AM

Title: aMule crash: OS_Rng: read /dev/urandom operation failed
Post by: foreman on April 15, 2009, 08:55:25 AM

Hello,

i compiled amule 2.2.4 in my debian etch with crypto, geoip, upnp and wxWidget from scratch.

aMule crash with this error:

Code: [Select]

aMule OnExit: Terminating core.
Saving PartFile 13 of 13
All PartFiles Saved.
aMule shutdown completed.
        aMule Version: aMuled 2.2.4 using  v2.8.10

        what(): OS_Rng: read /dev/urandom operation failed with error 0
Terminated after throwing an instance of 'CryptoPP::OS_RNG_Err'
        backtrace:
[2] ?? in amuled [0x805da6d]
[3] wxEntry(int&, wchar_t**) in /usr/local/lib/libwx_baseu-2.8.so.0[0xb7cec7dd]
[4] wxEntry(int&, char**) in /usr/local/lib/libwx_baseu-2.8.so.0[0xb7cec847]
[5] ?? in amuled [0x80549b5]
[6] __libc_start_main in /lib/tls/i686/cmov/libc.so.6[0xb7a38ea8]
[7] wxSockAddress::Clear() in amuled[0x8054321]
I find in this forum and over internet, that i should set the limits.
I done this:

Code: [Select]

/etc/security/limitis.conf:

p2p             soft    nofile          4096
p2p             hard    nofile          4096
(amuled run as user p2p)

But the error still persist, can anyone help me?

Title: Re: aMule crash: OS_Rng: read /dev/urandom operation failed
Post by: foreman on April 17, 2009, 08:29:55 AM

aMule is still crashing, one time in a hour!

Nobody have this problem?

Title: Re: aMule crash: OS_Rng: read /dev/urandom operation failed
Post by: Stu Redman on April 18, 2009, 06:55:20 PM

Looks like broken cryptopp to me. Try compiling cryptopp yourself, or use a precompiled aMule package.

Title: Re: aMule crash: OS_Rng: read /dev/urandom operation failed
Post by: foreman on April 19, 2009, 11:15:14 AM

I combiled cryptopp myself.

I can't use a precompiled package, because it doesn't exist for debian etch.

Regards.

Title: Re: aMule crash: OS_Rng: read /dev/urandom operation failed
Post by: wuischke on April 19, 2009, 11:52:51 AM

When you execute ./cryptest.exe v in the build folder of crypto++, does your compiled version pass all tests?

Title: Re: aMule crash: OS_Rng: read /dev/urandom operation failed
Post by: foreman on April 19, 2009, 04:30:25 PM

This is my test:

Code: [Select]

All tests passed!

Test ended at Sun Apr 19 16:29:36 2009
Seed used was: 1240151366

Regards.

Title: Re: aMule crash: OS_Rng: read /dev/urandom operation failed
Post by: wuischke on April 19, 2009, 05:56:50 PM

You have a successful crypto++ compilation. Is this the same you used for compiling aMule? (crypto++ is afaik statically linked, that's why this is important.)

Regarding your error: If I'm not mistaken, the error code 0 means that no data could be read. (i.e. the error is unrelated to file limits.) But this makes no sense to me, as /dev/urandom can't be empty and hence one should always be able to read something.
Sorry for not being able to help.

Title: Re: aMule crash: OS_Rng: read /dev/urandom operation failed
Post by: GonoszTopi on April 19, 2009, 07:28:37 PM

It might be that the entropy pool is depleted. But just don't ask me why and how to solve ...

Title: Re: aMule crash: OS_Rng: read /dev/urandom operation failed
Post by: foreman on April 20, 2009, 09:32:23 AM

In this case, i suppose that the only solution is to upgrade to lenny.

I saw that the user Vollstrecker made package for debian, i have used his package with etch without any problem.

Regards.