In the WowzaMediaServerForEC2_UsersGuide.pdf it says "Cacti is included in the Wowza AMIs but is turned off by default."
Does anyone know how to turn it on?
In the WowzaMediaServerForEC2_UsersGuide.pdf it says "Cacti is included in the Wowza AMIs but is turned off by default."
Does anyone know how to turn it on?
There are instructions in that guide.
Richard
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,"
Look on page 23 of this Guide:
http://www.wowzamedia.com/resources/...UsersGuide.pdf
RichardMonitoring the Wowza Media Server on EC2 using Cacti
Introduction
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?
Make sure port tcp port 8080 is open in your Security group, that might be your problem. Then follow these steps:
RichardGetting started with Cacti
1) Open TCP port 8080 (instructions for opening ports are above in the „Testing your Instance‟ section.
2) GoTo URL: http://[public-domain-name]:8080/cacti
3) Login as:
User Name: admin
Password: password
4) In the left hand column under the „Management‟ section click the link for „Devices‟
5) On the „Management: Devices” page click the „Localhost‟ device in the „Description‟ column.
6) Uncheck the „Disable Host‟ setting in the „General Host Options‟ section of the page. Then click the „Save‟ button at the bottom of the page.
Your server is now collecting data and can be viewed on the „Graph‟ tab. Because Cacti only collects data once every 60 seconds it will take a few minutes before your data will appear in the graphs.
That was it! I needed to open port 8080.
Thanks for the help!
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
but 2.1.2 in no fun!
i failed on 6 retry from small to large instances....
Which AMIs have you tried?
Richard
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