Old 9th May 2017, 04:14   #1
BLCR
Junior Member
 
Join Date: Feb 2014
Posts: 43
Sync To Stream error

Can someone explain what causes this error, and what the fix is?

ERROR [SRC xx.xx.xx.xx:xxxxx sid=1] SHOUTcast 1 source disconnected. Unable to sync to the stream. Please check the source is valid and in a supported format.

Thanks!
BLCR is offline   Reply With Quote
Old 9th May 2017, 06:38   #2
jaromanda
Forum King
 
Join Date: Jun 2007
Location: Under the bridge
Posts: 2,256
what are you using to source DNAS?

Is it just me or are shoutcast users getting dumber?
jaromanda is offline   Reply With Quote
Old 9th May 2017, 10:14   #3
BLCR
Junior Member
 
Join Date: Feb 2014
Posts: 43
I believe the customer said they were using SAM.
BLCR is offline   Reply With Quote
Old 11th May 2017, 03:16   #4
jaromanda
Forum King
 
Join Date: Jun 2007
Location: Under the bridge
Posts: 2,256
Yeah, I've heard SAM is utter garbage when it comes to streaming

Is it just me or are shoutcast users getting dumber?
jaromanda is offline   Reply With Quote
Old 23rd May 2017, 11:25   #5
drivehell
Senior Member
 
drivehell's Avatar
 
Join Date: Jun 2002
Location: Denver, Colorado
Posts: 116
The problem keeps occurring for us too. We have to switch to a different bitrate or restart the sc_serv for it to start working again
drivehell is offline   Reply With Quote
Old 24th May 2017, 14:40   #6
drivehell
Senior Member
 
drivehell's Avatar
 
Join Date: Jun 2002
Location: Denver, Colorado
Posts: 116
Happened again today.. This is killing our daily #'s.





Option 1 - to get around the problem I have to turn off the encoder and switch to a different bitrate and connect again which succeeds. After that I can change encoder back to original bitrate and it works.

Option 2 - restart sc_serv

SHOUTcast Server v2.5.1.724/posix(linux x64
on Ubuntu 16.04.1 LTS

sc_serv config:

code:

;DNAS configuration file
;Made with the SHOUTcast 2 Configuration Builder

password=xxxxx
adminpassword=xxxxxx
portbase=8000
requirestreamconfigs=1
logfile=logs/sc_serv242.log
w3clog=logs/sc_serv242_w3c.log
w3cenable=0
publicserver=always
banfile=sc_serv.ban
ripfile=sc_serv.rip
maxuser=250
maxspecialfilesize=115000000
relayconnectretries=0
ratelimit=0

;MAIN CHANNELa
;------------------------
;main mp3
streamid_1=1
streampath_1=/dnbradio_main.mp3
streammaxuser_1=250
streamautodumpusers_1=0
streamallowrelay_1=1
streampublicserver_1=1
streamauthhash_1=xxxxxxx
unique=dnbradio_main.mp3
streambanfile_1=sc_serv.ban
streamlog_1=logs/sc_dnbradio_main.log
streamw3clog_1=logs/sc_dnbradio_main_w3c.log
streamautodumpusers_1=0
;admetricsdebug=1



Attached Thumbnails
Click image for larger version

Name:	Screenshot 2017-05-24 06.22.19.png
Views:	86
Size:	226.6 KB
ID:	53278   Click image for larger version

Name:	Screenshot 2017-05-24 06.20.37.png
Views:	82
Size:	13.0 KB
ID:	53279  
drivehell is offline   Reply With Quote
Old 27th May 2017, 11:11   #7
drivehell
Senior Member
 
drivehell's Avatar
 
Join Date: Jun 2002
Location: Denver, Colorado
Posts: 116
and magically, after days of this happening every few hours, it as stopped.

I can't help but wonder if shoutCAST team is tinkering with their ad platform and causing these issues. If the problem comes back I will start sniffing packets to see what's going on.
drivehell is offline   Reply With Quote
Old 27th May 2017, 12:32   #8
drivehell
Senior Member
 
drivehell's Avatar
 
Join Date: Jun 2002
Location: Denver, Colorado
Posts: 116
Server completely crashed a few minutes ago:

Here are the log entries right before it happened. notice the same error "Unable to sync to the stream"

2017-05-27 14:08:18 ERROR [RELAY 78.47.134.103:13128/dnbradio_darkstep sid=2] Relay source rejected. Unable to sync to the stream. Please check the source is valid and in a supported format.
2017-05-27 14:08:18 INFO [RELAY 78.47.134.103:13128/dnbradio_darkstep sid=2] Connecting to source relay...
2017-05-27 14:08:18 WARN [ADVERT sid=2] Aborting data transfer due to the stream source disconnecting.
** sc_serv CRASH **

sc_serv relaunched (from CRON)

uptime is now showing 20minutes... this was definitely a crash.

and.. the affect on our listeners...
drivehell is offline   Reply With Quote
Old 27th May 2017, 13:04   #9
jaromanda
Forum King
 
Join Date: Jun 2007
Location: Under the bridge
Posts: 2,256
Quote:
Originally Posted by drivehell View Post
The problem keeps occurring for us too. We have to switch to a different bitrate or restart the sc_serv for it to start working again
Are you using SAM Bastardcaster too?

Is it just me or are shoutcast users getting dumber?
jaromanda is offline   Reply With Quote
Old 27th May 2017, 13:15   #10
drivehell
Senior Member
 
drivehell's Avatar
 
Join Date: Jun 2002
Location: Denver, Colorado
Posts: 116
Quote:
Originally Posted by jaromanda View Post
Are you using SAM Bastardcaster too?
The issue mostly likely is on sc_serv side. Even SAM uses the standard LAME encoder.. We are using liquidsoap for another stream and it has the same issues. Additionally, I noticed a relay having the same sync to stream issue -- meaning the relaysource was being rejected with this odd sync to stream error. I believe this is the same issue we had when running our main DNAS on windows. Now the main DNAS is on linux and having the same problem with crashing and sync to stream problems.
drivehell is offline   Reply With Quote
Reply
Go Back   Winamp & SHOUTcast Forums > SHOUTcast > SHOUTcast Technical Support

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump