Page 1 of 1

3.2.3 crash after linking

Posted: Fri Feb 17, 2006 1:21 am
by RePas
Hi boys and girls,

i am a owner of a IRCD-Network with 1 Hub (irc.nrw1....) und 3 leafs.
All IRCD´s are running with 3.2.3 and on differend Server .

When i compile my leaf Nr.3 (irc.nrw2...) i got some messages:

../lib/tre-parse.c: In function 'tre_expand_macro':
../lib/tre-parse.c:99: warning: pointer targets in passing argument 1 of 'strlen' differ in signedness
../lib/tre-parse.c:99: warning: pointer targets in passing argument 1 of 'strlen' differ in signedness
../lib/tre-parse.c:99: warning: pointer targets in passing argument 2 of '__builtin_strcmp' differ in signedness
../lib/tre-parse.c:99: warning: pointer targets in passing argument 2 of '__builtin_strcmp' differ in signedness
../lib/tre-parse.c:99: warning: pointer targets in passing argument 1 of 'strlen' differ in signedness
../lib/tre-parse.c:99: warning: pointer targets in passing argument 2 of '__builtin_strcmp' differ in signedness
../lib/tre-parse.c:99: warning: pointer targets in passing argument 2 of '__builtin_strcmp' differ in signedness
../lib/tre-parse.c:99: warning: pointer targets in passing argument 2 of 'strncmp' differ in signedness
../lib/tre-parse.c: In function 'tre_parse_bracket_items':
../lib/tre-parse.c:354: warning: pointer targets in passing argument 2 of '__builtin_strncpy' differ in signedness
../lib/tre-parse.c: In function 'tre_parse':
../lib/tre-parse.c:1369: warning: pointer targets in passing argument 1 of 'strlen' differ in signedness


Is there something wrong with the shell-Server ?
Or is it a clock problem between nrw1 and nrw2 ?
The Shell-Provider doesnt know it. :(


The irc.nrw2... starts without problems :
~/Unreal3.2.3$ ./unreal start
Starting UnrealIRCd
_ _ _ ___________ _____ _
| | | | | |_ _| ___ \/ __ \ | |
| | | |_ __ _ __ ___ __ _| | | | | |_/ /| / \/ __| |
| | | | '_ \| '__/ _ \/ _` | | | | | / | | / _` |
| |_| | | | | | | __/ (_| | |_| |_| |\ \ | \__/\ (_| |
\___/|_| |_|_| \___|\__,_|_|\___/\_| \_| \____/\__,_|
v3.2.3
using TRE 0.7.2 (GPL)
using OpenSSL 0.9.8a 11 Oct 2005
using zlib 1.2.3

* Loading IRCd configuration ..
* Configuration loaded without any problems ..
* Loading tunefile..
* Initializing SSL.
* Dynamic configuration initialized .. booting IRCd.
---------------------------------------------------------------------

But irc.nrw2... crashed by linking and i got messages from the Hub :
[ 17.02.06 - 01:18:04 ] -irc.nrw1.xxx.net- *** Notice -- (link) Secure link irc.nrw1.xxx.net -> irc.nrw2.xxx.net[@xxx.xxx.30.200.33077] established (SSLv3-AES256-SHA-256bits)
-
[ 17.02.06 - 01:18:04 ] -irc.nrw1.xxx.net- (link) Secure link irc.nrw2.xxx.net -> irc.nrw1.xxx.net[@xxx.xxx.31.200.0] established (SSLv3-AES256-SHA-256bits)
-
[ 17.02.06 - 01:18:04 ] -irc.nrw1.xxx.net- *** Notice -- Link irc.nrw2.xxx.net -> irc.nrw1.xxx.net is now synced [secs: 0 recv: 0.511 sent: 10.562]
-
[ 17.02.06 - 01:18:04 ] -irc.nrw1.xxx.net- *** Notice -- Link irc.nrw2.xxx.net is running Protocol u2305 while we are running 2306!
-
[ 17.02.06 - 01:18:04 ] -irc.nrw1.xxx.net- *** Global -- Closing link: Write error: Connection reset by peer - irc.nrw2.xxx.net[xxx.xxx.30.200]
-
[ 17.02.06 - 01:18:08 ] -irc.nrw1.xxx.net- *** Notice -- (link) Secure link irc.nrw1.xxx.net -> irc.nrw2.xxx.net[@xxx.xxx.30.200.44921] established (SSLv3-AES256-SHA-256bits)
-
[ 17.02.06 - 01:18:08 ] -irc.nrw1.xxx.net- (link) Secure link irc.nrw2.xxx.net -> irc.nrw1.xxx.net[@xxx.xxx.31.200.0] established (SSLv3-AES256-SHA-256bits)
-
[ 17.02.06 - 01:18:08 ] -irc.nrw1.xxx.net- *** Notice -- Link irc.nrw2.xxx.net -> irc.nrw1.xxx.net is now synced [secs: 0 recv: 0.511 sent: 10.562]
-
[ 17.02.06 - 01:18:09 ] -irc.nrw1.xxx.net- *** Notice -- Link irc.nrw2.xxx.net is running Protocol u2305 while we are running 2306!
-
[ 17.02.06 - 01:18:09 ] -irc.nrw1.xxx.net- Exiting ssl client irc.nrw2.xxx.net[@xxx.xxx.30.200.44921]: SSL_read(): Underlying syscall error


There is no Error in ircd.log .


thx 4 help

PS: Sorry 4 my bad english^^

greetz


RePas

Posted: Fri Feb 17, 2006 1:53 am
by Stealth
Upgrade to 3.2.4, this has been fixed