wowza startup seems fine but longer streaming over port 1935

[chrisanderson]

i hate asking for help, but i'm somewhat stumped. i'm running wowza 1.5.3 on centos. it was streaming for a while, i then setup wowza to run as a service which seemed to go fine. however i'm unable to get videos to stream over port 1935, i also don't get the welcome text from wowza if i try going to ipaddress:1935. if i try to startup wowza manually it fails to bind to port 1935 seeming to prove that the service is already running. also using the command to kill the service works too. i'll post a recent log to let you see if there are any obvious problems. it looks good to me though.

thanks a ton for any help.

#Version: 1.0
#Start-Date: 2008-09-10 19:46:23 CDT
#Software: Wowza Media Server Pro 1.5.3 build7825
#Date: 2008-09-10
#Fields: x-severity	x-category	x-event	date	time	c-client-id	c-ip	c-port	cs-bytes	sc-bytes	x-duration	x-sname	x-stream-id	sc-stream-bytes	cs-stream-bytes	x-file-size	x-file-length	x-ctx	x-comment
INFO	server	server-start	2008-09-10	19:46:23	-	-	-	-	-	0.662	-	-	-	-	-	-	Wowza Media Server Pro Unlimited 1.5.3 build7825	-
INFO	server	comment	2008-09-10	19:46:23	-	-	-	-	-	0.67	-	-	-	-	-	-	-	Serial number: XXXXX-XXXXX-XXXXX-XXXXX-AY8T3
INFO	server	comment	2008-09-10	19:46:23	-	-	-	-	-	0.671	-	-	-	-	-	-	-	Maximum connections: Unlimited
INFO	server	comment	2008-09-10	19:46:23	-	-	-	-	-	0.674	-	-	-	-	-	-	-	Hardware Available Processors: 1
INFO	server	comment	2008-09-10	19:46:23	-	-	-	-	-	0.676	-	-	-	-	-	-	-	Hardware Physical Memory: 1248MB/2019MB
INFO	server	comment	2008-09-10	19:46:23	-	-	-	-	-	0.677	-	-	-	-	-	-	-	Hardware Swap Space: 2047MB/2047MB
INFO	server	comment	2008-09-10	19:46:23	-	-	-	-	-	0.678	-	-	-	-	-	-	-	Max File Descriptor Count: 4096
INFO	server	comment	2008-09-10	19:46:23	-	-	-	-	-	0.683	-	-	-	-	-	-	-	Open File Descriptor Count: 30
INFO	server	comment	2008-09-10	19:46:23	-	-	-	-	-	0.683	-	-	-	-	-	-	-	OS Name: Linux
INFO	server	comment	2008-09-10	19:46:23	-	-	-	-	-	0.684	-	-	-	-	-	-	-	OS Version: 2.6.9-67.0.22.EL
INFO	server	comment	2008-09-10	19:46:23	-	-	-	-	-	0.685	-	-	-	-	-	-	-	OS Architecture: i386
INFO	server	comment	2008-09-10	19:46:23	-	-	-	-	-	0.686	-	-	-	-	-	-	-	Java Name: Java HotSpot(TM) Client VM
INFO	server	comment	2008-09-10	19:46:23	-	-	-	-	-	0.687	-	-	-	-	-	-	-	Java Vendor: Sun Microsystems Inc.
INFO	server	comment	2008-09-10	19:46:23	-	-	-	-	-	0.688	-	-	-	-	-	-	-	Java Version: 10.0-b23
INFO	server	comment	2008-09-10	19:46:23	-	-	-	-	-	0.689	-	-	-	-	-	-	-	Java Home: /usr/java/jre1.6.0_07
INFO	server	comment	2008-09-10	19:46:23	-	-	-	-	-	0.69	-	-	-	-	-	-	-	Java Max Heap Size: 762MB
INFO	server	comment	2008-09-10	19:46:23	-	-	-	-	-	0.691	-	-	-	-	-	-	-	Java Architecture: 32
INFO	server	comment	2008-09-10	19:46:23	-	-	-	-	-	0.722	-	-	-	-	-	-	-	CMDInterface now listening: [any]:8083
INFO	vhost	vhost-start	2008-09-10	19:46:24	-	-	-	-	-	0.799	-	-	-	-	-	-	_defaultVHost_	-
INFO	server	comment	2008-09-10	19:46:24	-	-	-	-	-	0.8	-	-	-	-	-	-	-	vhost home directory: /usr/local/WowzaMediaServerPro
INFO	vhost	comment	2008-09-10	19:46:24	-	-	-	-	-	1.39	-	-	-	-	-	-	_defaultVHost_	RTMP/RTMPT bind attempt ([any]:1935)
INFO	vhost	comment	2008-09-10	19:46:24	-	-	-	-	-	1.396	-	-	-	-	-	-	_defaultVHost_	Bind successful ([any]:1935)
INFO	vhost	vhost-stop	2008-09-10	19:47:39	-	-	-	-	-	76.477	-	-	-	-	-	-	_defaultVHost_	-
INFO	server	server-stop	2008-09-10	19:47:39	-	-	-	-	-	76.482	-	-	-	-	-	-	-	-

[charlie]

The logs look fine. It is very strange that you can't get to port 1935. I would try the following:

1. Reboot the server (always a good thing to try)
2. On the CentOS box, try executing the command:
   

   get http://localhost:1935

   See if it generates a file with the version number

I am not sure what else to try. It should just work. Very strange.

Charlie

[chrisanderson]

thanks for the fast reply, i didn't mention it in my last post but i've rebooted the server a few times during testing. each time the service seems to start up fine. i'm pretty new to centos and linux in general. i'm getting an error from bash stating that get isn't a known command. thanks again. i'll be doing some testing too, i've got a buddy i may try to work with tomorrow who's a whiz in linux management. hopefully i can figure this out quick.

[rogerlittin]

I think you will find it is a permissions problem.

On Centos(RedHat) the wowza service stores a lock file & pid file in /var/run/

I think from memory that the wowza user does't have the right permissions on the files in /var/run or the files are when created are owned by a user other than wowza.

Your buddy should be able to sort it out for you.

Even if you kill the server with the kill command, the files remain so it wont restart properly.

[chrisanderson]

thanks a ton for the info, you've given me the only path i have for the moment.

[chrisanderson]

this may be an error that doesn't really affect anything but thought i would check.

[root@pro ~]# service WowzaMediaServerPro start
/etc/init.d/WowzaMediaServerPro: line 60: kill: (3081) - No such process
WowzaMediaServerPro is already running (3081): stopping
WowzaMediaServerPro: starting                              [  OK  ]

the service was already running, but i was just testing it out. i've tried it a few more times since then (starting the service when it's already running), and haven't seen the same error again.

also if i telnet localhost 1935 it seems to connect fine. i'm thinking it may be a permissions bug too, my friend is pretty tied up today and this weekend. any advice on fixing up my permissions is welcome. thanks for all the help. if i have to wait until monday to get my friends help i think i should be alright.

[chrisanderson]

well i'm relieved. posting the fix for my problem just in case anyone else runs into the same thing. turns out port 1935 was blocked on the dedicated server (i'm almost positive it was open at some point, not sure how it became blocked). i had to edit iptables. located @ /etc/sysconfig/iptables. added the line:

-A INPUT -p tcp -m tcp --dport 1935 -j ACCEPT

saved iptables and restarted iptables:

service iptables restart

i know these instructions leave out some detail but hopefully it'll be enough to help anyone who may run into the same problem. i know it's basic for the rest of you guys, but was foreign land for me . thanks for the help and time you guys put in to help me out.

[jhector02]

I am trying to do video streaming on demand but I still not get it. I did follow the instructions of this forum,: first I modify [install-dir]/config/server.xml, where I did place the ip address. It looks like this:
<CommandInterface>
<HostPort>
<IpAddress>192.168.1.64</IpAddress>
<Port>8083</Port>
</HostPort>

Then I did the same with [install-dir]/config/vhosts.xml

After that, I modify [install-dir]/config/application.xml, where I place the storage dir. Looks like this

<Streams>
<StreamType>default</StreamType>
<StorageDir>${com.wowza.wms.AppHome}/content</StorageDir>
<Properties>

Then, I create folder in [install-dir]/applications/, I call it "test",

I stored the videos to be streaming in: [install-dir]/content

After all, I test this using an example of the example folder, and it works with simplestreamingvideo example, but when I try to plug it to a flv player like the jw flv player, it doesn´t work. This is the code I am using in jw flv player:

<script type="text/javascript">
var s1 = new SWFObject("player.swf","ply","328","20","","#FFFFF F");
s1.addParam("allowfullscreen","true");
s1.addParam("allowscriptaccess","always");
s1.addParam("flashvars","fullscreen=true&streamer= rtmp://192.168.1.64/test&file=video1");
s1.write("container");
</script>


am I right or I am missing something?

by the way, I am using windows and the video is in flv format.

please somebody help me!!

Thanks

Juan