Station setup
  • Vote Up0Vote Down Francis XavierFrancis Xavier
    Posts: 10Member
    When setting up a station I get the following error: 

    Can not connect to the streaming server
    could not write data to host: Connection refused in write()

    image

    I have checked my server as well and port 8000 is open.  I thought it may have to do with the directory that vintagetalk.us is pointed to in apache which is different from the airtime install directory. It appears to be a permissions problem but I cant seem to find why its not able to initiate the server.
    Post edited by Francis Xavier at 2012-07-24 21:57:43
  • 17 Comments sorted by
  • Vote Up0Vote Down Martin KonecnyMartin Konecny
    Posts: 1,860Member
    Try looking through 

    /var/log/airtime/pypo-liquidsoap/ls_script.liq
    /var/log/airtime/pypo/pypo.log

    for clues
    Airtime Pro Hosting: http://airtime.pro
  • Vote Up0Vote Down Martin KonecnyMartin Konecny
    Posts: 1,860Member
    You can also try "airtime-test-stream" utility.

    This will help you troubleshoot connecting to your server.

    Run with the -h option to see options.
    Airtime Pro Hosting: http://airtime.pro
  • Vote Up0Vote Down Francis XavierFrancis Xavier
    Posts: 10Member
    This is what I am getting: 

    Protocol: shoutcast
    Host: localhost
    Port: 8000
    User: source
    Password: hackme
    Mount: test

    Outputting to shoutcast streaming server. You should be able to hear a monotonous tone on 'http://localhost:8000/test'. Press ctrl-c to quit.
    There was an error with your stream configuration. Please review your configuration and run this program again. Use the -h option for help


    The pypo logs dont help much.  

    I think the problem is with the initial install.  From what I read Airtalk/liquidsoap are just not friendly, although it is possible, with Shoutcast.  I think it may be a problem with lame not being compiled with the install.  I checked the liquidsoap plugins and lame was missing.  When I tried to install it it says it relies on another version of liquidsoap: 

    The following packages have unmet dependencies:
     liquidsoap-plugin-lame : Depends: liquidsoap (= 1.0.0-4build1) but 1.0.1~precise~sfo-1 is to be installed

    Honestly Icecast is more robust.  The only real reason I want to use Shoutcast is because of their nicely laid out yellowpages.  Icecast fails at yp and I am not even sure how it is retrieving tags, or how to edit them or send more accurate ones then it is getting.  


  • Vote Up0Vote Down Fred PercevaultFred Percevault
    Posts: 53Member
    I fully agree when you wrote "
    I want to use Shoutcast is because of their nicely laid out yellowpages"
    That's the most important benefit of Shoutcast.
    it pull a lot of listeners to your stream (depending your stream quality, of course)
    Since Shoutcast V2 you msut use sc_trans V2 to be listed in the yellowpages
    (as far I remember)
    Icecast YP are just crappy
  • Vote Up0Vote Down Martin KonecnyMartin Konecny
    Posts: 1,860Member
    Reply to @Francis+Xavier:

    I think the problem is with the initial install.  From what I read Airtalk/liquidsoap are just not friendly, although it is possible, with Shoutcast.  I think it may be a problem with lame not being compiled with the install.  I checked the liquidsoap plugins and lame was missing.  When I tried to install it it says it relies on another version of liquidsoap: 

    The following packages have unmet dependencies:
     liquidsoap-plugin-lame : Depends: liquidsoap (= 1.0.0-4build1) but 1.0.1~precise~sfo-1 is to be installed

    Honestly Icecast is more robust.  The only real reason I want to use Shoutcast is because of their nicely laid out yellowpages.  Icecast fails at yp and I am not even sure how it is retrieving tags, or how to edit them or send more accurate ones then it is getting.  
     

    You shouldn't have to do any of that; Airtime works with Shoutcast out of the box. Please check your settings again as many Airtime users are using Shoutcast with no problem and no special configuration steps.
    Airtime Pro Hosting: http://airtime.pro
  • Vote Up0Vote Down Martin KonecnyMartin Konecny
    Posts: 1,860Member
    Reply to @Francis+Xavier:

    Try:

    airtime-test-stream -v -o shoutcast -P "yourport" -p "yourpassword"

    without the double quotes for the values. The "-v" will tell us exactly why it couldn't connect. 
    Airtime Pro Hosting: http://airtime.pro
  • Vote Up0Vote Down Francis XavierFrancis Xavier
    Posts: 10Member
    Here is the output.  From what I understand this is the password contained in the stream info in liquidsoap.dfg  

    I should note too, I changed the port here to port 9000 so it is different from the icecast stream and the one I posted above.  

    Protocol: shoutcast
    Host: localhost
    Port: 9000
    User: source
    Password: notarealpassword
    Mount: test

    Outputting to shoutcast streaming server. You should be able to hear a monotonous tone on 'http://localhost:9000/test'. Press ctrl-c to quit.
    airtime-liquidsoap 'output.shoutcast(%mp3, host="localhost", port = 9000, user= "source", password = "notarealpassword", mount="test",  sine())'
    At line 1, char 17: the variable output.shoutcast used here has not been
      previously defined.
    There was an error with your stream configuration. Please review your configuration and run this program again. Use the -h option for help
     
    Post edited by Francis Xavier at 2012-07-28 22:41:19
  • Vote Up0Vote Down Martin KonecnyMartin Konecny
    Posts: 1,860Member
    Ok this is a bug with our airtime-test-stream and shoutcast.

    I've patched the problem. Please right click on the following link and select "Save As"


    Now in the terminal on your system, go to the directory where you downloaded the file and type

    mv airtime-test-stream.py /usr/lib/airtime/utils/

    Then run the airtime-test-stream command I gave in the previous post.
    Airtime Pro Hosting: http://airtime.pro
  • Vote Up0Vote Down Francis XavierFrancis Xavier
    Posts: 10Member
    Here is the latest output: 

    Protocol: shoutcast
    Host: localhost
    Port: 9000
    User: source
    Password: fakepw
    Outputting to shoutcast streaming server. You should be able to hear a monotonou                                           s tone on 'http://localhost:9000/test'. Press ctrl-c to quit.
    airtime-liquidsoap /usr/lib/airtime/pypo/bin/liquidsoap_scripts/library/pervasiv                                           es.liq 'output.shoutcast(%mp3, host="localhost", port = 9000, user= "source", pa                                           ssword = "donthackme", sine())'
    2012/07/29 00:15:54 >>> LOG START
    2012/07/29 00:15:54 [protocols.external:3] Didn't find "ufetch".
    2012/07/29 00:15:54 [protocols.external:3] Found "/usr/bin/wget".
    2012/07/29 00:15:54 [main:3] Liquidsoap 1.0.1
    2012/07/29 00:15:54 [main:3] Using: graphics=[distributed with Ocaml] pcre=6.2.3                                            dtools=0.3.0 duppy=0.4.2 duppy.syntax=0.4.2 cry=0.2.2 mm=0.2.0 xmlplaylist=0.1.                                           3 ogg=0.4.3 vorbis=0.6.1 mad=0.4.4 flac=0.1.1 flac.ogg=0.1.1 dynlink=[distribute                                           d with Ocaml] lame=0.3.1 alsa=0.2.1 ao=0.2.0 taglib=0.2.0 camomile=0.8.3 portaud                                           io=0.2.0 pulseaudio=0.1.2 ladspa=0.1.4 camlimages=4.0.0
    2012/07/29 00:15:54 [dynamic.loader:3] Could not find dynamic module for aacplus                                            encoder.
    2012/07/29 00:15:54 [dynamic.loader:2] Could not load plugins in directory /usr/                                           local/lib/liquidsoap/1.0.1/plugins.
    2012/07/29 00:15:54 [frame:3] Using 44100Hz audio, 25Hz video, 44100Hz master.
    2012/07/29 00:15:54 [frame:3] Frame size must be a multiple of 1764 ticks = 1764                                            audio samples = 1 video samples.
    2012/07/29 00:15:54 [frame:3] Targetting 'frame.duration': 0.04s = 1764 audio sa                                           mples = 1764 ticks.
    2012/07/29 00:15:54 [frame:3] Frames last 0.04s = 1764 audio samples = 1 video s                                           amples = 1764 ticks.
    2012/07/29 00:15:54 [threads:3] Created thread "generic queue #1".
    2012/07/29 00:15:54 [threads:3] Created thread "generic queue #2".
    2012/07/29 00:15:54 [output(dot)shoutcast:3] Connecting mount / for source@local                                           host...
    2012/07/29 00:15:54 [output(dot)shoutcast:2] Connection failed: could not write                                            data to host: Connection refused in write()
    2012/07/29 00:15:54 [output(dot)shoutcast:3] Will try again in 3.00 sec.
    2012/07/29 00:15:54 [threads:3] Created thread "wallclock_main" (1 total).
    2012/07/29 00:15:54 [clock.wallclock_main:3] Streaming loop starts, synchronized                                            with wallclock.
    2012/07/29 00:15:58 [output(dot)shoutcast:3] Connecting mount / for source@localhost...
    2012/07/29 00:15:58 [output(dot)shoutcast:2] Connection failed: could not write data to host: Connection refused in write()
    2012/07/29 00:15:58 [output(dot)shoutcast:3] Will try again in 3.00 sec.

  • Vote Up0Vote Down Martin KonecnyMartin Konecny
    Posts: 1,860Member
    Have you tried changing user name to "admin"? That appears to be the default user name for shoutcast.
    Airtime Pro Hosting: http://airtime.pro
  • Vote Up0Vote Down Francis XavierFrancis Xavier
    Posts: 10Member
    Yea it still gives that error that it cannot write data to host.  

    Actually let me correct myself.  I have the username set to admin but when I run the script it says the username is "source".  I edited it directly in liquidsoap.cfg for s2 which is the shoutcast source.

    s2_bitrate = 48
    s2_host = "vintagetalk.us"
    s2_port = 9000
    s2_output = "shoutcast"
    s2_user = "admin"


    Post edited by Francis Xavier at 2012-07-29 00:32:21
  • Vote Up0Vote Down Martin KonecnyMartin Konecny
    Posts: 1,860Member
    Have you been able to use any other software to connect to the shoutcast
    server?
    On Jul 29, 2012 12:26 AM, "Francis Xavier" <<br />airtime-support@lists.sourcefabric.org> wrote:

    > Yea it still gives that error that it cannot write data to host.
    >
    >
    Airtime Pro Hosting: http://airtime.pro
  • Vote Up0Vote Down Martin KonecnyMartin Konecny
    Posts: 1,860Member
    Also, looking at your website, shoutcast appears to be listening on port 8000. Might want to try changing that setting as well.
    Airtime Pro Hosting: http://airtime.pro
  • Vote Up0Vote Down Francis XavierFrancis Xavier
    Posts: 10Member
    Yea I havent updated anything on the site regarding SC but thanks for the heads up.  
    I havent tried anything else.  I have always used shoutcast on CentOS but I really love this software and I want to try to see it through.  I set up an separate box with ubuntu just for this. Its something I would buy.  

    I had to add the username directly to the liquidsoap.cfg because on the airtime stream config there is no field for the username. 


    Post edited by Francis Xavier at 2012-07-29 00:49:50
  • Vote Up0Vote Down Francis XavierFrancis Xavier
    Posts: 10Member
    I havent used anything else to try to connect to shoutcast yet.  What I cant seem to figure out and maybe you can shed some light on is what these problems are.

    Can anyone explain what the server is trying to do here and what files I need to edit to change settings?

    regardless of the username I run this with it always fails.  I have tried "admin" as well for the username.


    2012/07/29 00:15:54 [output(dot)shoutcast:3] Connecting mount / for source@local                                           host...
    2012/07/29 00:15:54 [output(dot)shoutcast:2] Connection failed: could not write                                            data to host: Connection refused in write()


  • Vote Up0Vote Down Martin KonecnyMartin Konecny
    Posts: 1,860Member
    I'm pretty sure either shoutcast isn't running or it's not running where you expect it.

    I get the same error message when I try running airtime-test-stream and I point it at the wrong address. Try point airtime-test-stream at your live shoutcast server (the one running on port 8000).
    Airtime Pro Hosting: http://airtime.pro
  • Vote Up0Vote Down Francis XavierFrancis Xavier
    Posts: 10Member
    I have an icecast server running on port 8000 and what I did to get around all of this was I have set up a separate shoutcast server locally on port 8001 as a relay. I am just relaying my icecast station to it.  I really like icecast and I'm not going to fight with it just in order to do it through airtime.  I am trying to fix a bunch of other little issues which are more important.  


Add a Comment