Results 1 to 3 of 3

Thread: Strange host errors on startup

  1. #1
    Join Date
    Feb 2010
    Posts
    25

    Default Strange host errors on startup

    I'm getting the following two errors when starting up Wowza:

    HTTPUtils.HTTPRequestToByteArray: java.io.FileNotFoundException: http://169.254.169.254/latest/meta-data/public-hostname
    JMXConfig: error: java.net.MalformedURLException: Bad URL path: ${com.wowza.amazonaws.ec2.AWSEC2_METADATA_PUBLIC_HOSTNAME}:8084/jndi/rmi://${com.wowza.amazonaws.ec2.AWSEC2_METADATA_PUBLIC_HOSTNAME}:8085/jmxrmi
    Could it have something to do with the fact that the server is configured with two ip addresses?? Nothing else on it is complaining (even zimbra which is notoriously difficult about these things).

    My hosts file only has localhost:127.0.0.1 and mail.server.com:10.0.0.158

    Wowza is bound to 10.0.0.157 with: <IpAddress>10.0.0.157</IpAddress> in VHost.xml, which in turn is bound to its own external ip.

    I've tried a few regular fixes in the hosts file but nothing seems to work, what can I do to stop these errors? (although they don't seem to affect anything it irks me to have them laying around...)

    This is my ifconfig:
    eth0      Link encap:Ethernet  HWaddr 12:56:29:E0:D7:60  
              inet addr:10.0.0.157  Bcast:10.0.0.255  Mask:255.255.255.0
              inet6 addr: fe80::1056:29ff:fee0:d760/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:67280149 errors:0 dropped:0 overruns:0 frame:0
              TX packets:28027164 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:97585362140 (90.8 GiB)  TX bytes:2940043792 (2.7 GiB)
              Interrupt:27 
    
    eth1      Link encap:Ethernet  HWaddr 12:56:29:DB:66:16  
              inet addr:10.0.0.158  Bcast:10.0.0.255  Mask:255.255.255.0
              inet6 addr: fe80::1056:29ff:fedb:6616/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:408848 errors:0 dropped:0 overruns:0 frame:0
              TX packets:387231 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:79466116 (75.7 MiB)  TX bytes:112427630 (107.2 MiB)
              Interrupt:28 
    
    lo        Link encap:Local Loopback  
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:14163365 errors:0 dropped:0 overruns:0 frame:0
              TX packets:14163365 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0 
              RX bytes:13926094745 (12.9 GiB)  TX bytes:13926094745 (12.9 GiB)

  2. #2

    Default

    Hi,

    It looks like you are launching an instance into Amazon VPC instead of EC2. You get these messages with VPC because it doesn't support all of the variables that wowza normally uses to automatically configure EC2 instances.

    You will have to manually configure your VPC instances.

    Regards,

    Roger.

  3. #3
    Join Date
    Feb 2010
    Posts
    25

    Default

    roger_l, what do I need to configure exactly?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •