|
|||||||
![]() |
|
|
Thread Tools | Search this Thread | Display Modes |
|
|
#1 |
|
Junior Member
Join Date: Oct 2011
Posts: 6
|
flooding syslog with "err=Connection reset by peer.(10054)"
Hello
Have installed DNAS 2 and got this problem. Every time new user connected, this error appears in Windows System Log. Actually there is no problem, the stream plays correctly. But i've tired cleaning windows system log ![]() os is w2k8R2 sp1, DNAS is the latest build for x64 systems. here is the shoutcast log 2011-10-10 14:02:17 I msg:<***> Logger startup 2011-10-10 14:02:17 I msg:<***> version 2.0.0.29 2011-10-10 14:02:17 D msg:<***> 2011-10-10 14:02:17 I msg:*************************************************************** 2011-10-10 14:02:17 I msg:** SHOUTcast Distributed Network Audio Server (DNAS) 2011-10-10 14:02:17 I msg:** Copyright (C) 1999-2011 Nullsoft, Inc. All Rights Reserved. 2011-10-10 14:02:17 I msg:** Use "sc_serv filename.conf" to specify a config file. 2011-10-10 14:02:17 I msg:*************************************************************** 2011-10-10 14:02:17 I msg:[SHOUTcast] DNAS/win64 v2.0.0.29 (Jul 31 2011) starting up... 2011-10-10 14:02:17 I msg:[MAIN] PID: 3216 2011-10-10 14:02:17 I msg:[MAIN] Loaded config from sc_serv_RadioExtreme_local.conf 2011-10-10 14:02:17 I msg:[MAIN] Calculated CPU count is 4 2011-10-10 14:02:17 I msg:[MAIN] Starting 4 network threads 2011-10-10 14:02:17 I msg:[MICROSERVER] Listening for connection on port 9000 2011-10-10 14:02:17 I msg:[MICROSERVER] Listening for connection on port 9001 2011-10-10 14:02:17 I msg:[SRC 127.0.0.1:58423] SHOUTcast 2 source connection. 2011-10-10 14:02:17 I msg:[SRC 127.0.0.1:58423] Password accepted. Stream id is 1 2011-10-10 14:02:17 I msg:[SRC 127.0.0.1:58423 sid=1] stream configuration complete. [ type=SHOUTcast 2 mimeType=audio/mpeg maxPayloadSize=16377 avgBitrate=256000 maxBitrate=256000 desiredBufferSize=60 minimumBufferSize=0 icyName=- icyGenre=Various icyURL=- icyPub=0 ] 2011-10-10 14:02:36 I msg:[DST 10.99.99.50:54786 sid=1] SHOUTcast 1 client connection accepted. BASS/2.4 2011-10-10 14:02:46 E msg:[DST 10.99.99.50:54786 sid=1] Socket error while waiting to send data. err=Connection reset by peer.(10054) 2011-10-10 14:02:46 I msg:[DST 10.99.99.50:54786 sid=1] SHOUTcast 1 client connection closed (10 seconds) [Bytes: 491520] Agent: `BASS/2.4' 2011-10-10 14:02:46 I msg:[DST 10.99.99.50:54787 sid=1] SHOUTcast 1 client connection accepted. BASS/2.4 2011-10-10 14:02:52 I msg:[SRC 127.0.0.1:58423 sid=1] Got complete metadata message type=3902 [384 bytes] id=322 span=1 content= <?xml version="1.0" encoding="UTF-8"?> <metadata><TIT2>My Way (William Orbit remix)</TIT2><TPE1>Limp Bizkit</TPE1><TALB>New Old Songs</TALB><TCON>Other</TCON><TLEN>393707</TLEN><TRCK>15</TRCK><TXXX id="songtype">S</TXXX><TENC>SAM Broadcaster 4.9.0</TENC><TRSN>-</TRSN><WORS>-</WORS><extension><title seq="1">Limp Bizkit - My Way (William Orbit remix)</title></extension></metadata> |
|
|
|
|
|
#2 |
|
Forum King
|
For as long as I've known the new v2 DNAS that error message is normal for a listener disconnect. I think there might maybe be an update some down the line to consolidate, eliminate, or shore-up the message some day. Just keep an eye out. As long as you're up and running there's nothing to worry about.
|
|
|
|
|
|
#3 |
|
Junior Member
Join Date: Oct 2011
Posts: 6
|
ok
hope this will be fixed in future |
|
|
|
|
|
#4 |
|
-
Join Date: Sep 2003
Location: UK
Posts: 22,278
|
there's nothing to fix as that's a valid message displayed on client connection going away as thinktink says. it's actually useful having that message output in the logs as it can help see if someone is doing some dodgy or there's issues going on.
i have made a note of this thread and may consider making changes to what is / isn't logged for those cases in a newer v2 DNAS release (though there's no guarantees). -daz |
|
|
|
|
|
#5 |
|
Junior Member
Join Date: Oct 2011
Posts: 6
|
It would be nice, if this message appears only in TXT log, not Windows EVENT LOG. In previous GUI version of DNAS there was no such a problem. I tried both x86 and x64 versions, no difference to this issue.
Also I watched this more carefully, message appears only on client disconnect. Also I've encountered with some dummy catalogue-like programs for listening internet radio that during listening, second user-session establishing and dropping every 5-10 sec. It will flood the log very fast!!! |
|
|
|
|
|
#6 | |
|
-
Join Date: Sep 2003
Location: UK
Posts: 22,278
|
it will be changed for the next v2 DNAS release so that 10054 errors will not be output to any of the logs for client connections so that it'll just output as
Quote:
-daz |
|
|
|
|
|
|
#7 |
|
Junior Member
Join Date: Oct 2011
Posts: 6
|
Great! Then I'll be waiting for update now )
|
|
|
|
|
|
#8 |
|
Junior Member
Join Date: Oct 2011
Posts: 6
|
still no update?
i'm tired of waiting the patch....
|
|
|
|
|
|
#9 |
|
-
Join Date: Sep 2003
Location: UK
Posts: 22,278
|
it will be released when it is ready and that is not the case at the moment. i probably should have done incremental updates but that's not happened. and as i've only just gotten around to removing a number of other connection 'error' messages in the internal builds, my prior fix would not have made you happy anyway.
-daz |
|
|
|
![]() |
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|