How do I turn on Cacti

I’m not sure how to enable cacti or set password in a startup package.

If you are using the Wowza Dynamic Load Balancer you can get an overview of edge usage from the load balancer HTTProvider:

http://[wowza-loadbalancer-address]:1935/loadbalancer?serverInfoXML

See the package readme for instructions for enabling this HTTProvider.

Richard

Yes it is a great data source… even better with this php script to clarify the data:

I push our drupal programmer here to get me some code to:

extract the ip’s from serverInfoXML to build an automatic web page to get the addresses of the origins and all edges, and for each servers bring a JW player window play the streams…

all of this to have a quick check on any servers connections count status and performances…

I also am only seeing network and system graphs, no Wowza graphs. Any suggestions?

And does anybody know how can I enable caciti and change its password with startup package ?

IF there are, I’m not seeing them. It just refers you to cacti.net which talks about a fresh install… I want to use the one that’s already set up.

"For detailed information about Cacti you can read more at: http://www.cacti.net/

Once activated on the Wowza Server it will begin to monitor and track information,"

I assume you mean page 24. I’m also assuming you’re referring to the part where explains how to connect

“http://[public-domain-name]:8080/cacti”

However, this just leads to a connection timed out so I’m assuming that this because cacti is not turned on. Am I missing something?

That was it! I needed to open port 8080.

Thanks for the help!

I am having this problem also with ami-26c62d4f

Can someone please tell me how to get the current connection count? I believe this used to work by browsing to port 1935, but now I just get this:

Wowza Media Server 2 for Amazon EC2 2.1.2 build24878

Got it thanks, would still be nice if we could fix the reporting…any ideas?

I can get it working for sys stats but no wowza infos… seems to be jmx communication buggy!

if i try 2.1.1 ami it’s so easy to get it all working :slight_smile:

but 2.1.2 in no fun!:mad:

i failed on 6 retry from small to large instances…

As described here I get the Network and System graphs, but nothing for Wowza. It has been enabled for about 24 hours now and had over 100 sustained connections (according to /connectioninfo).

Can I PM you the login info?

odd…

if i force my instance to start on us-east-1c … bingo!:slight_smile:

instant reporting (few sec) of my streaming…:smiley:

may be a zone problem?!:confused:

AMI ID: ami-26c62d4f

did someone changed the ami?.. or my brain? it looks ok now after starting 5 instances on Zone a c d… cant get zone b to start!

so… i am happy for now!

Do you know which instance had the problem initially? Could that have been zone B and forcing it out of B fixes that? Or does it need to be not-zone-B and forced into a zone. (clear?)

My instance is in Zone A, but if I remember EC2 correctly, my zones can be different than your zones (hence why they are just given generic letters).

Yup this worked for me as well (and I am using an EIP). Thanks a bunch.

Might take a little while for data to start showing, or set on wrong scale. Assigning ElasticIP after does break Cacti, at least temporarily.

Richard

I can find nothing about Cacti in User Guide. any ideas?

Anatoly

We use wowza EC2 and cacti is enabled and available as a private ami on our s3.

The problem is that on the control panel of cacti, on Default Tree -> Wowza Media Server, on all the graphs we get “nan” on Current, Average and Maximum and the graphs are empty.

We restarted wowza after assigning elastic ip but the problem persists…

Why?