Snapshot of EC2 Wowza AMI, logs folder missing

[confusedUser]

Hello,

I have started a community Wowza AMI (ID ami-79834b10). I then used AMI tools and created a snapshot and uploaded on to S3. The snapshot AMI would report the Logs folder missing. The path '/usr/local/WowzaMediaServer/logs' is missing. The logs folder is a shortcut link to '/media/ephemeral0/WowzaMediaServer/logs' but that is missing as well.

Does anyone know why when creating a snapshot AMI, the logs folder is missing and is there anyway I can get it back?

Thanks.

[ianbeyer]

Was this based on an existing Wowza AMI? If so, check that your ephemeral storage is correctly mounted - the logs and content directories are mounted on the ephemeral storage rather than the base instance storage.

-Ian

[ianbeyer]

Was this based on an existing Wowza AMI? If so, check that your ephemeral storage is correctly mounted - the logs and content directories are mounted on the ephemeral storage rather than the base instance storage.

-Ian

[confusedUser]

Yes this was based on an existing Wowza AMI (ID ami-79834b10). When I start my snapshot instance, '/media/ephemeral0/WowzaMediaServer/logs' does not exist. How do I check if is correctly mounted?

[confusedUser]

This is actually based on Wowza Media Server 3, posted on Wowza Media 2 forum by mistake.

[rrlanham]

I think you want to bundle a new AMI, not snapshot. Try the AWS console. Select a running instance, then select "Bundle Instance (S3 AMI)" from the Instance Actions list.

Richard

[confusedUser]

I used the AMI tools from Amazon and used 'ec2-bundle-vol' command which "create an AMI from an existing installation volume and bundle it". I did that process and the AMI seems to be missing the Wowza logs.

Are you saying I can do the same thing using the AWS console without using the AMI tools?

[rrlanham]

Yes, try that.

Richard

[confusedUser]

I started an instance, and the option "Bundle Instance (S3 AMI)" is not highlighted. I can't choose that option. Is there a reason?

[rrlanham]

Select a running instance, then select "Bundle Instance (S3 AMI)" from the "Instance Actions" list.

Richard