failed to start on lamp template - main.usr

[markvtc]

I'm just getting started on a new grid, and created a copy of the lamp single server template. I think I configured it properly, entered in the ip addresses etc, although the in_ip and out_ip are the same, but on starting the app, I get message "main.usr failed to start;cleaning up" etc etc

any ideas what I am doing wrong?

[PeterNic]

Mark,

Two ideas off the top of my head:
- IP address conflict (in_ip must be different from out_ip)
- insufficient memory for the gateways

Since you say " in_ip and out_ip are the same", I suspect it is the former.

Regards,
-- Peter

[markvtc]

Changed the ip addresses for in and out, still fails to start at "main.usr failed to start" - there is plenty of memory given (the default settings for the one server lamp stack. I have done nothing to it at all..this is just a copy of the template, then enter the property values and then ran app start. Any ideas?

[PeterNic]

Mark,

Can you look at the grid log (log list n=100) just after the app fails to start? In most cases, appliances that fail to start report the reason for the failure.

Also, please include the grid version (from 'grid info'). Note that some versions of AppLogic had incorrect default and minimum value for the memory of the gateways, make sure there is at least 64M (see hotfix hf2195).

The IP addresses for in and out must be different and not like the addresses of any other gateway; the addresses given must be one of the addresses in the range specified on the dashboard.

Finally, does the gateway fail to start relatively quickly (~30-40sec) or does it try starting for more than a minute and then fails?

If you want to diagnose the failure, you can try starting the application with the --debug option. In that case, when main.usr fails to start, the application will remain running, including the gateway. You will be able to login into it and look around ( (ssh main.usr). Also, you can manually try the interface (ifup eth0); also down it, then log into the out gateway and try pinging the in ip address (after bringing eth0 down in the usr gateway), just in case there is a conflict somewhere (unlikely but worth trying), or the dashboard range is incorrect.

If nothing helps, please submit a ticket to your service provider -- https://helpdesk.3tera.com/ if you have signed up directly with 3Tera. It should be easy to resolve.

I hope this helps.

Regards,
-- Peter