I packaged our application with same parameters and files as we used for 1.1.x versions and when I am trying to connect console I got  the following error:
 
axp-1.5.3-1(exec-NetworkEmbeddedLogger)# connect console
Hosting environment is not online
 
I found few posts in the website about this issue and they didn¿t seems to resolve this issue.

The packaging command is (activated from build script): (I have used this command for my packages of ver 1.1.x and it seems to be OK)
 
$CiscoBuildFolder/tools/pkg_build.sh --project-dir $CiscoDir/Packaging/NetworkEmbeddedLogger/package --auth-bundle $CiscoBuildFolder/cert/cert_nme/auth_bundle.sig  --private-key  ~/mykey.pem --name 'NetworkEmbeddedLogger' --version $NiceVer.522.$CiscoVer --description 'Network Embedded Logger - 522' --uuid '2cda59cd-901c-4e81-a195-5910f9c9e19b' --source-dir $CiscoDir/Packaging/NetworkEmbeddedLogger/build --disk-wildcard --disk-limit '125000M' --memory-limit '1944M' --cpu-limit '13700' --postinstall 'bin/postinstall.sh' --cap-config 'kern_cap.cfg'
 
2. Output:
 
axp-1.5.3-1# show app-service state
                   APPLICATION                STATE               HEALTH
         NetworkEmbeddedLogger              offline                  ---
axp-1.5.3-1#
 
 
 
 

Thanks Anusha,
I checked the logs and I see the following errors:
 
ERROR get_disk_usage get_disk_usage get_disk_usage Vserver NetworkEmbedd
edLogger does not exist...
 
Could it be the reason ?
 
Thanks,
Andrey
 
 

Hi Andrey,
 
This application offline issue typically occurs due to the following cases:
 
1.  If you are using one of our new SM-700/900 or ISM service modules you need to get new license and also accept the evaluation license agreement - assuming you haven't installed the permanent license.  This step is done by accessing the application context and accepting the license. 
Example:
  app-service <the app>
  SE-Module(config-app)# license evaluation enable AXP-GP-LIC
 
2.  When moving your application from AXP 1.1.x to 1.5.x you should use the 1.5.x sdk to package your application, and request/use the 1.5.x authorization files.
 
3.  If you are specifying a small amount of disk space such as 1 MB, you shoud increase this limit to at least 10 MB.  This issue may also occur if you have created archived files such as tar files and then decompress them which would then exceed the disk limit you've specified.
 
4.  In 1.5.x you can review the logs interactively by typing a command such as 'show log name messages.log interactive' which will give you functionality like Vi for searching ...etc.   Check for errors and warnings.
 
If you are still unable to resolve this issue please create a service request via http://tools.cisco.com/ServiceRequestTool/create/launch.do so that we can may thoroughly invest your case.
 
Thanks,
 
Brett