PDA

View Full Version : Multiple streams on Linux server


donsmada
14th August 2007, 04:50
I have read several other posts that are similar to my request here but they all come from the view point of using my home PC as the original stream source.

I rent a linux server and I currently have shoutcast running fine there. I wanna add another stream to this same linux server.

I have tried just copying my current shoutcast and changing the name from shoutcast to PIRadio and changed port from 8000 to 9000.

and that is as far as I got.....

any advice on how to proceed from here

TY Don

Nick@ss
14th August 2007, 06:22
what more do you want to know?

change the name to sc_serv2

if you start both servers all will be fine

donsmada
14th August 2007, 18:37
When I do rename sc_serv to sc_serv2 I would start it with the following command correct?

./sc_serv2 sc_serv.conf "

Will this automactically understand that I am wanting a whole new server and broadcaster playing or do I need to rename the following also:

sc_serv.conf
sc_trans.conf
sc_trans_linux

If I do rename sc_trans_linux how will it know to use the renamed sc_trans_2.conf instead of the orginal sc_trans.conf

I do understand that I will have to use the new names when staring each and that I can not use the same port as the orginal.

Sawg
14th August 2007, 19:54
Don't rename the executables. Just need multiple configs.
cp sc_serv.conf sc_serv2.conf
[Edit sc_serv2.conf accordingly]

Then launch the server with the config as the paramater:
./sc_serv sc_serv.conf
./sc_serv sc_serv2.conf

Make sure PortBase is off by at least 2.

Same idea for sc_trans.

donsmada
14th August 2007, 20:16
Originally posted by Sawg
Don't rename the executables. Just need multiple configs.
cp sc_serv.conf sc_serv2.conf
[Edit sc_serv2.conf accordingly]

Then launch the server with the config as the paramater:
./sc_serv sc_serv.conf
./sc_serv sc_serv2.conf

Make sure PortBase is off by at least 2.

This makes complete sense to me and I understand it 100%.

My next question deals with what you said about sc_trans. I have been using the command ./sc_trans_linux & to start my sc_trans.

You said not to rename the executables, so do I use the same command ./sc_trans_linux but add sc_trans2.conf to it like the ./sc_serv sc_serv2.conf command?

Sawg
14th August 2007, 21:42
Never used sc_trans, but I think it still takes the config as a parameter as well, defaults to sc_trans.conf if there isn't a parameter passed.

donsmada
14th August 2007, 21:51
:)
I am back to where I started. I do appreciated the help thou. I am going to proceed with what has been mentioned here and go from there.

I will report back here but in the mean time futher comments are welcome.

If you don't use sc_trans how does sc_serv know where to get the playlist from?

fc*uk
14th August 2007, 22:02
sc_trans does require a config file to run or it will default to sc_trans.conf.

Therefore, you need to do the same for sc_trans as you did for sc_serv. Use two different config files and start sc_trans twice.

If you do not use sc_trans, you simply need something to shout to sc_serv. Anything that will transcode audio and send it to a specified port will do...

donsmada
14th August 2007, 22:50
SWEET! WE got it up and working. I will post my steps here in a few. I wanna make sure I get them in a coherent layout for others to use in the furture.

again, Thanks y'all

donsmada
22nd August 2007, 23:24
Here are the steps I follow when starting up my 2 different streams(this makes more sense if you read the entire thread prior to reading this)

Stream 1 and Stream 2 refer to the different music streams you want to have
the host server is a Linux RedHat server
shoutcast is already install and working correctly
Stream 1 and Stream 2 are accessed via different port numbers (here ports 8000 and 9000 are used)

In this example PUTTY is used to access SSH and with user 'root'

Shoutcast start up for Stream 1 and Stream 2

First log in with PUTTY under root

root / (your password here)

STARTING IT UP (turn on each server)

STEP 1:
use the following command
cd /home/shoutcast
to access shoutcast

If Stream 1 is already playing skip to step 4

STEP 2:
now set up shoutcast server to remain running when PUTTY is closed
use the following command
chmod +x sc_serv

STEP 3:
now start up Stream 1 server
use the following command
./sc_serv
(at this point there is only 1 server running for Shoutcast; Stream 1)

visit your IP:8000/index.html to check that Stream 1's server is up and running (note that nothing is streamed at this point as long as you get a page up that is not a "page can't be found error" then you should be good at this point)

now exit out of PUTTY and reopen it and log back in and repeat Step 1 then proceed with STEP 4

STEP 4:
now start up Stream 2's server
(note: "sc_serv_pi.conf" refers to config file I set up for my stream 2 by editting "sc_serv.conf" and saving it as "sc_serv_pi.conf")
use the following command
./sc_serv sc_serv_pi.conf
(at this point there are 2 servers running for Shoutcast, Stream 1 and 2)


visit your IP:9000/index.html to check that Stream 2's server is up and running (note that nothing is streamed at this point as long as you get a page up that is not a "page can't be found error" then you should be good at this point)

now exit out of PUTTY and reopen it and log back in and repeat Step 1 then proceed with STEP 5

STEP 5 (turning on the broadcaster for Stream 1):
now that Stream 1 server is running we need to give it files to stream
use the following commands
cd ./sc_trans_040
then
./sc_trans_linux &

now at this point everything should be up and running for Stream 1

again visit your IP:8000/index.html and if everything is working right you should be able to click on the LISTEN link and here the stream

now exit out of PUTTY and reopen it and log back in and repeat Step 1 then proceed with STEP 6

STEP 6 (turning on the broadcaster for Stream 2):
now that Stream 2's server is running we need to give it files to stream
use the following commands
cd ./sc_trans_040
then
(note: "sc_trans_pi.conf" refers to config file I set up for my stream 2 by editting "sc_trans.conf" and saving it as "sc_trans_pi.conf")
./sc_trans_linux sc_trans_pi.conf &

now at this point everything should be up and running for Stream 2

again visit your IP:9000/index.html and if everything is working right you should be able to click on the LISTEN link and here the stream


By no means am I an expert but I think I have a good grasp on this so if you have any questions either PM me or post it here

fc*uk
22nd August 2007, 23:25
:up: