Get Random Stations error using API

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • kar10s
    Junior Member
    • Oct 2010
    • 2

    Get Random Stations error using API

    Hi,
    I am testing Api shoutcast and i am getting frecuently an error with this request to random function.

    http://api.shoutcast.com/station/randomstations?k=[here my devidkey]&limit=100&f=xml

    <response>
    <statusCode>500</statusCode>
    <statusText>Generic Server Error</statusText>
    <statusDetailText>20022</statusDetailText>
    </response>

    other times I obtain a correct response
    <response>
    <statusCode>200</statusCode>
    <statusText>Ok</statusText>
    +<data>
    </data>
    </response>

    I have changed the limit to other values with similar results.

    ¿Do you know why this happens?
    Regards
  • HQ-Gadgets
    Junior Member
    • Nov 2010
    • 4

    #2
    Originally Posted by kar10s View Post
    Do you know why this happens?
    No, but I can confirm this Problem.
    I think it's a Server Problem.

    With Genre=Rock, mt=mp3 and br=128 the Response is mostly a Server Error, a Limit to 20 don't help:
    http://api.shoutcast.com/station/randomstations?k=[devidkey]&f=xml&mt=audio/mpeg&br=128&genre=Rock&limit=20

    Comment

    • HQ-Gadgets
      Junior Member
      • Nov 2010
      • 4

      #3
      Since 1 week the Problems are stronger.

      Now I have up to 99% the Error(Code 20022) Response.



      Please correct the problem soon, otherwise I have to change my Radio App to ICEcast Radio Directory.

      Comment

      • DrO
        • Sep 2003
        • 27868

        #4
        it is known about but we're not progressing on what is leading to the error (i.e. is known where it happens, but not how / why) so i cannot advise on when a resolution to the issue will be. also is it just the randomstations action which is causing you issues?

        -daz
        WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

        Comment

        • HQ-Gadgets
          Junior Member
          • Nov 2010
          • 4

          #5
          Originally Posted by DrO View Post
          also is it just the randomstations action which is causing you issues?

          -daz
          My App only use the randomstation action, but I have tested the genrelist action too, now with the same Problem.

          First I had only Problems with big Pools of Streams(Genre=Rock and Pop, and low Bitrate=128 kbps), but now a simple Request like Genre-List produce the Error.

          http://api.shoutcast.com/legacy/genrelist?k=...

          I think it's a Database and/or Server capacity Problem.

          Comment

          • DrO
            • Sep 2003
            • 27868

            #6
            k, i was only under the impression from what i've been hearing / seeing that it was just the randomstations action which was having issues. most likely it is a hardware / db issue but i'm not able to do much towards the issue (though i've seen what is internally reported when that 20022 error happens and it didn't help much). hopefully it will be sorted out soon...

            -daz
            WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

            Comment

            • mavvy
              Junior Member
              • Jul 2011
              • 6

              #7
              Hi guys, sorry that my first post is a help request too... I'm getting this 20022 error very often (8 errors out of 10 attempts) when requesting the main lists:

              /legacy/genrelist?f=xml&k=myapikey
              /genre/primary?f=xml&k=myapikey

              But it also happens as often when accessing genres directly:

              legacy/genresearch?f=xml&k=myapikey&genre=90s

              Direct access to a station looks very stable. it's just the listings that ersult in this error.

              Do you happen to have a clue by now what could cause this?

              Comment

              • DrO
                • Sep 2003
                • 27868

                #8
                all i know is its being looked into and that's about as much as i know on how it's progressed. if / when i know more then i'll try to remember to post back to this thread (with everything else i'm trying to do, heh).

                -daz
                WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

                Comment

                • mavvy
                  Junior Member
                  • Jul 2011
                  • 6

                  #9
                  thanks daz, crossing my fingers that the devs (or server admins if it's a server/db issue) will find the reason

                  Comment

                  Working...
                  X