Hi Chaps, hoping to find a resolution here. I also found a bit of a big in the Amazon Cloudstack script, I think.
But first, here's my problem: I've followed the step by step instruction to setup Wowza on EC2, as per the very helpful Amazon Developer guide. Problem is, now that I have this up and running, when I try to login I get this error:
Wowza Streaming Engine Manager could not connect to the Wowza Steaming Engine (http://localhost:8087). Verify that the Wowza Streaming Engine service has started and is running.
So to confirm, I can get to the login page, and have the correct username and password as per the output from when the AIM package was setup. Perhaps the error is around the "localhost" setting? Maybe that should be pointing to my actual server instead?
So here's the BUG I found! Clearly, the older version of your product required port 8086 to be used to connect to the Streamengine. In version 4 though, it's 8088. Trouble is, as part of the AIM setup, it only opens up port ranges 8084-8086! Whoops... once you edit this to go up to 8088, viola! You can connect.
May need to let them know, being a "free" user, AMZ don't value my opinion enough to give me access to support / forums...
Anyway, help much appreciated please. I'm very green at this stuff.
My server is here:
EDIT1: managed to putty into the install, noticed that both the services were stopped. Ran the /.startup.sh script, "seeems" like it is running, however still won't allow me to login. Reviewing the execution, this is at the top of the script:
Configure logging: file:///usr/local/WowzaStreamingEngine/conf/log4j.properties
ERROR server comment - ServerUtils.loadServerListener: Error creating <ServerListener> (com.wowza.wms.plugin.mediacache.impl.MediaCacheServerListener) : java.lang.ClassNotFoundException: com.wowza.wms.plugin.mediacache.impl.MediaCacheServerListener|at java.net.URLClassLoader$1.run(URLClassLoader.java:366)|at java.net.URLClassLoader$1.run(URLClassLoader.java:355)|at java.security.AccessController.doPrivileged(Native Method)|at java.net.URLClassLoader.findClass(URLClassLoader.java:354)|at java.lang.ClassLoader.loadClass(ClassLoader.java:425)|
EDIT2: rebooted the instance to see if that may restore things. Here's an excerpt from the logs, it looks like the services simply start, but stop shortly after:
***** script output start *****
Tuning Wowza Streaming Engine: m3.large
Disk Capacity [/media/ephemeral0]: 29G
MediaCache: MediaCacheStore/MaxSize: 20G
***** script output stop *****
Wowza Streaming Engine 4 for Amazon EC2: Setting file permissions
[ OK ]
WowzaStreamingEngine started PID1481)
[ OK ]
WowzaStreamingEngineManager started PID1509)
Starting crond: [ OK ]
Starting atd: [ OK ]
Starting jexec servicesRunning cloud-init user-scripts (none found)[ OK ]
Amazon Linux AMI release 2013.09
Kernel 3.4.76-65.111.amzn1.x86_64 on an x86_64
ip-172-31-12-231 login: /dev/fd/11: line 1: /sbin/plymouthd: No such file or directory
initctl: Event failed
Stopping atd: [ OK ]
Waiting for process (1509) to exit...
[ OK ]
Stopping sshd: [ OK ]
Shutting down sm-client: [ OK ]
Shutting down sendmail: [ OK ]
Shutting down vsftpd: [ OK ]
Stopping crond: [ OK ]
Shutting down ntpd: [ OK ]
Stopping block device availability: Deactivating block devices:
[ OK ]
Stopping system message bus: [ OK ]
Stopping auditd: [10204.772846] type=1305 audit(1396013450.125:127): audit_pid=0 old=1212 auid=4294967295 ses=4294967295 res=1
[ OK ]
[10204.876352] type=1305 audit(1396013450.229:128): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 res=1
Shutting down system logger: [ OK ]
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
Sending all processes the TERM signal... [ OK ]
Sending all processes the KILL signal... [ OK ]
Saving random seed: [ OK ]
Unmounting file systems: [ OK ]
init: Re-executing /sbin/init
[10207.625923] EXT4-fs (xvda1): re-mounted. Opts: (null)
Please stand by while rebooting the system...
[10207.762221] Restarting system.