Old 17th September 2014, 12:45   #1
newbornus
Junior Member
 
Join Date: Feb 2014
Posts: 30
[DNAS GM Build 147] [Linux x86] [Server hangup]

Hello!

After updating to the latest build i've noticed that server hangs up probably when a timeout to yp happens.

The PID is alive but webinterface does not respond and a source also could not connect to the server.
What i see in the log just before a crash is:

2014-09-17 15:06:41 ERROR [YP] Request [http://yp.shoutcast.com:80/yp2] failed, code: 28 [Operation timed out after 30000 milliseconds with 0 bytes received]
2014-09-17 15:13:42 INFO [MAIN] Exiting threads...

I had to move to an old build (from 11-29-2013).
newbornus is offline   Reply With Quote
Old 17th September 2014, 12:50   #2
DrO
 
Join Date: Sep 2003
Posts: 27,873
how on earth are you even getting things to hang in the first place?

though why that error is causing the DNAS to start it's shutdown procedure i really don't know at the moment.

so much for us changing to using libcurl since 2.2.2 to eradicate the YP connectivity issues that plagued the custom solution used previously (which it had apart from what you've now reported and it just randomly giving up the ghost for some other setups) *shrugs*
DrO is offline   Reply With Quote
Old 17th September 2014, 13:00   #3
newbornus
Junior Member
 
Join Date: Feb 2014
Posts: 30
Ok then i'll stay now on the old version of DNAS, it is stable for me =)
Just wanted to test the latest version and found this bug.
newbornus is offline   Reply With Quote
Old 17th September 2014, 13:10   #4
DrO
 
Join Date: Sep 2003
Posts: 27,873
but that defeats the point of what we're trying to achieve with everyone being on a current DNAS version (irrespective of what they were on beforehand) so the platform can be moved on to where it needs to be and to be able to do what users are repeatedly demanding.

so i really could do with more information on what / how you managed to get the DNAS to the state of the YP connection showing a 30 second time out so we can try to replicate it and resolve it.
DrO is offline   Reply With Quote
Old 17th September 2014, 13:53   #5
newbornus
Junior Member
 
Join Date: Feb 2014
Posts: 30
Ok DrO please let me know if additional info is needed from me or some changes happen, i'll then move on to the latest version again..
newbornus is offline   Reply With Quote
Old 17th September 2014, 14:07   #6
DrO
 
Join Date: Sep 2003
Posts: 27,873
what was going on from the machine's side when that issue happened ?

what timezone is the log output related to ?

did it happen as soon as the DNAS was started or did it take a while for the issue to manifest ?
DrO is offline   Reply With Quote
Old 17th September 2014, 15:00   #7
newbornus
Junior Member
 
Join Date: Feb 2014
Posts: 30
i have not noticed something unusual on the machine
timezone is GMT+4 (MSK)

sometimes it happens a few minutes after start, sometimes server works stable for a few days.
i have 2 servers
i have migrated the second one to the latest version, and the 1st is running older one. let's see what will happen on second server.
newbornus is offline   Reply With Quote
Old 17th September 2014, 15:28   #8
DrO
 
Join Date: Sep 2003
Posts: 27,873
ok, so the log time rules out it being something due to YP updates i was deploying last night (which caused some intermittent access issues).

ok, so it's possible that it's related (or even just a manifestation) of the same issue we're already seeing (where the YP handling just drops).

once i've got a working test build (hopefully before the end of the week), i'll pm you with something to try out.

and if there's anything specific which happens when the issue happens that you notice, please do let us know.
DrO is offline   Reply With Quote
Old 30th September 2014, 07:13   #9
newbornus
Junior Member
 
Join Date: Feb 2014
Posts: 30
just got a hangup after 3 days of no troubles server running.

the last messages in log was:
2014-09-30 09:51:50 INFO [RELAY 192.168.174.1:8008/stream1 sid=1] Title update [Chicago - Once In A Lifetime]
2014-09-30 09:51:50 INFO [RELAY 192.168.174.1:8008/stream2 sid=2] Title update [Chicago - Once In A Lifetime]
2014-09-30 09:51:50 INFO [RELAY 192.168.174.1:8008/stream3 sid=3] Title update [Chicago - Once In A Lifetime]
2014-09-30 09:51:50 INFO [RELAY 192.168.174.1:8008/stream4 sid=4] Title update [Chicago - Once In A Lifetime]
2014-09-30 09:51:50 INFO [RELAY 192.168.174.1:8008/stream5 sid=5] Title update [Chicago - Once In A Lifetime]
2014-09-30 09:52:22 ERROR [YP] Request [http://yp.shoutcast.com:80/yp2] failed, code: 28 [Operation timed out after 30001 milliseconds with 0 bytes received]

After i tried to strike ctrl-c, got a message in console:

2014-09-30 10:01:42 INFO [MAIN] Exiting threads...

and then - nothing ... i was forced to manually kill the sc_serv PID.

Any suggestions?
newbornus is offline   Reply With Quote
Old 30th September 2014, 07:17   #10
newbornus
Junior Member
 
Join Date: Feb 2014
Posts: 30
just a notice - i've got 2 servers running on the same host but different VMs
on the other VM i have no such messages or hangups...
newbornus is offline   Reply With Quote
Old 30th September 2014, 12:48   #11
DrO
 
Join Date: Sep 2003
Posts: 27,873
I managed to replicate the locking issue yesterday but am seeing if the fix works correctly across all platform versions (as its been easier to replicate on windows despite most reports being for linux builds). it also looks like the locking issue might be the cause of the yp connectivity failing.
DrO 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