I'm trying to setup a very simple 2 system "network"... Both ends are using ngircd (I'm using 0.7.5, the other end is using 0.7.0) I keep getting a rather endless loop of the following in my /var/log/messages:
Dec 23 19:54:21 melvin ngircd[12231]: Accepted connection 1 from 12.241.198.87:49787 on socket 4. Dec 23 19:54:21 melvin ngircd[12231]: Peer announces itself as ngircd-0.7.0 using protocol 2.10/IRC+ (flags: "CZo"). Dec 23 19:54:21 melvin ngircd[12231]: Server "ls.xj220c.net" registered (connection 1, 1 hop - direct link). Dec 23 19:54:21 melvin ngircd[12231]: Enabled link compression (zlib) on connection 1. Dec 23 19:54:21 melvin ngircd[12231]: Server "ls.xj220c.net" unregistered (connection 1): Decompression error! Dec 23 19:54:21 melvin ngircd[12231]: Connection 1 with 12-241-198-87.client.attbi.com:49787 closed (in: 0.1k/0.1k/120%, out: 0.3k/0.3k/81%).
any ideas why it's having an error so quickly?
Hello Anthony!
I'm trying to setup a very simple 2 system "network"... Both ends are using ngircd (I'm using 0.7.5, the other end is using 0.7.0) I keep getting a rather endless loop of the following in my /var/log/messages:
Dec 23 19:54:21 melvin ngircd[12231]: Accepted connection 1 from 12.241.198.87:49787 on socket 4. Dec 23 19:54:21 melvin ngircd[12231]: Peer announces itself as ngircd-0.7.0 using protocol 2.10/IRC+ (flags: "CZo").
Okay, the connecting server announces that it supports link compression (the "Z" flag) ...
Dec 23 19:54:21 melvin ngircd[12231]: Server "ls.xj220c.net" registered (connection 1, 1 hop - direct link). Dec 23 19:54:21 melvin ngircd[12231]: Enabled link compression (zlib) on connection 1.
... and therefore this server enables it.
Dec 23 19:54:21 melvin ngircd[12231]: Server "ls.xj220c.net" unregistered (connection 1): Decompression error! Dec 23 19:54:21 melvin ngircd[12231]: Connection 1 with 12-241-198-87.client.attbi.com:49787 closed (in: 0.1k/0.1k/120%, out: 0.3k/0.3k/81%).
The "Decompression error" message is generated by the Conn_Close() call at src/ngircd/conn-zip.c, line 165. But the more informative syslog message with severity "ALERT" which contains information about the internal state of the compression code is missing here. Is your syslog configured to direct such "alert messages" to another locatin?
any ideas why it's having an error so quickly?
The call to inflate() at src/ngircd/conn-zip.c didn't return with Z_OK but an other result code (which should be logged in the missing line of your log).
Which systems are involved? And which versions of the zlib are used?
Regards Alex
syslog has the following to go along with every failed connction attempt: Dec 23 19:54:21 melvin ngircd[12231]: Decompression error: code -3 (ni=1075248017, ai=20, no=1075241708, ao=2047)!? My end is ngircd 0.7.5 running on linux 2.4.18 with zlib version 1.1.4 The other end is running ngircd 0.7.0 on an unknown version of FreeBSD sadly, I also don't know what version of zlib they're using. (I'll continue attempting to get in touch with the owner of that machine to get such information)
Thank you *very much* for the help you've provided thus far, it is most appreciated.
- Anthony
On Fri, 26 Dec 2003, Alexander Barton wrote:
Hello Anthony!
I'm trying to setup a very simple 2 system "network"... Both ends are using ngircd (I'm using 0.7.5, the other end is using 0.7.0) I keep getting a rather endless loop of the following in my /var/log/messages:
Dec 23 19:54:21 melvin ngircd[12231]: Accepted connection 1 from 12.241.198.87:49787 on socket 4. Dec 23 19:54:21 melvin ngircd[12231]: Peer announces itself as ngircd-0.7.0 using protocol 2.10/IRC+ (flags: "CZo").
Okay, the connecting server announces that it supports link compression (the "Z" flag) ...
Dec 23 19:54:21 melvin ngircd[12231]: Server "ls.xj220c.net" registered (connection 1, 1 hop - direct link). Dec 23 19:54:21 melvin ngircd[12231]: Enabled link compression (zlib) on connection 1.
... and therefore this server enables it.
Dec 23 19:54:21 melvin ngircd[12231]: Server "ls.xj220c.net" unregistered (connection 1): Decompression error! Dec 23 19:54:21 melvin ngircd[12231]: Connection 1 with 12-241-198-87.client.attbi.com:49787 closed (in: 0.1k/0.1k/120%, out: 0.3k/0.3k/81%).
The "Decompression error" message is generated by the Conn_Close() call at src/ngircd/conn-zip.c, line 165. But the more informative syslog message with severity "ALERT" which contains information about the internal state of the compression code is missing here. Is your syslog configured to direct such "alert messages" to another locatin?
any ideas why it's having an error so quickly?
The call to inflate() at src/ngircd/conn-zip.c didn't return with Z_OK but an other result code (which should be logged in the missing line of your log).
Which systems are involved? And which versions of the zlib are used?
Regards Alex
-- Alexander Barton, Freiburg, Germany alex@barton.de, http://www.barton.de/
The other end is running FreeBSD 5.1-RELEASE and the same version of zlib as myself: 1.1.4
On Fri, 26 Dec 2003, Alexander Barton wrote:
Hello Anthony!
I'm trying to setup a very simple 2 system "network"... Both ends are using ngircd (I'm using 0.7.5, the other end is using 0.7.0) I keep getting a rather endless loop of the following in my /var/log/messages:
Dec 23 19:54:21 melvin ngircd[12231]: Accepted connection 1 from 12.241.198.87:49787 on socket 4. Dec 23 19:54:21 melvin ngircd[12231]: Peer announces itself as ngircd-0.7.0 using protocol 2.10/IRC+ (flags: "CZo").
Okay, the connecting server announces that it supports link compression (the "Z" flag) ...
Dec 23 19:54:21 melvin ngircd[12231]: Server "ls.xj220c.net" registered (connection 1, 1 hop - direct link). Dec 23 19:54:21 melvin ngircd[12231]: Enabled link compression (zlib) on connection 1.
... and therefore this server enables it.
Dec 23 19:54:21 melvin ngircd[12231]: Server "ls.xj220c.net" unregistered (connection 1): Decompression error! Dec 23 19:54:21 melvin ngircd[12231]: Connection 1 with 12-241-198-87.client.attbi.com:49787 closed (in: 0.1k/0.1k/120%, out: 0.3k/0.3k/81%).
The "Decompression error" message is generated by the Conn_Close() call at src/ngircd/conn-zip.c, line 165. But the more informative syslog message with severity "ALERT" which contains information about the internal state of the compression code is missing here. Is your syslog configured to direct such "alert messages" to another locatin?
any ideas why it's having an error so quickly?
The call to inflate() at src/ngircd/conn-zip.c didn't return with Z_OK but an other result code (which should be logged in the missing line of your log).
Which systems are involved? And which versions of the zlib are used?
Regards Alex
-- Alexander Barton, Freiburg, Germany alex@barton.de, http://www.barton.de/
-
Alexander Barton -
Anthony Kepler