|
|
#1 |
|
Guest
Posts: n/a
|
Event log:
<08/12/00@15:41:23> [SHOUTcast] DNAS/win32 v1.666.1 (Jun 8 2000) starting up... <08/12/00@15:41:23> [main] loaded config from C:\Program Files\SHOUTcast\sc_serv.ini <08/12/00@15:41:23> [main] initializing (usermax:32 portbase:8000)... <08/12/00@15:41:23> [main] No ban file found (sc_serv.ban) <08/12/00@15:41:23> [main] No rip file found (sc_serv.rip) <08/12/00@15:41:23> [main] opening source socket <08/12/00@15:41:23> [main] source thread starting <08/12/00@15:41:23> [main] opening client socket <08/12/00@15:41:23> [main] Client Stream thread [0] starting <08/12/00@15:41:23> [main] client main thread starting <08/12/00@15:41:24> [source] listening for connection on port 8001 <08/12/00@15:41:28> [source] connected from 127.0.0.1 <08/12/00@15:41:29> [http:127.0.0.1] REQ:"/index.html" (ShoutcastDSP (Mozilla Compatible)) <08/12/00@15:41:29> [source] icy-name:MIxMan ; icy-genre:Mix of everything <08/12/00@15:41:29> [source] icy-pub:1 ; icy-br:56 ; icy-url:http://www.shoutcast.com <08/12/00@15:41:29> [source] icy-irc:%23shoutcast ; icy-icq:0 ; icy-aim:N%2FA <08/12/00@15:41:30> [dest: 205.188.245.32] starting stream (1/32) <08/12/00@15:41:30> [yp_add] yp.shoutcast.com added me successfully <08/12/00@15:41:30> [dest: 205.188.245.32] connection closed (sent 8192 bytes total) (0/32) Is that supposed to happen? |
|
|
|
#2 |
|
Junior Member
|
Nop, it wasn't. I don't know how to solve it... sorry. :7
------------------ I'm so tired of myself... Ooh god plz take me away... <UL TYPE=SQUARE> <LI> iCQ: 44734186 <LI> iRC: #ThEpLaNeT @ irc.ptnet.org </UL> |
|
|
|
|
|
#3 |
|
Guest
Posts: n/a
|
i get this too. i think it has something to do with a firewall, but i'm not sure. Got a firewall?
anyhow, this doesn't affect the stream at all. I've been having this connection closed problem and still people can listen to the show, it just won't be listed at Shoutcast. |
|
|
|
#4 |
|
Senior Member
|
Actually, it's just part of Shoutcast's security features. When you first start up your stream, that IP address automatically logs on to check that the stream is actually running, then logs off. Perfectly normal and nothing to worry about.
|
|
|
|
![]() |
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|