The following forum(s) are migrating to a new home on Microsoft Q&A (Preview): Azure App Service - API Apps!

Ask new questions on Microsoft Q&A (Preview).
Interact with existing posts until December 13, 2019, after which content will be closed to all new and existing posts.

Learn More

 none
app service won't start RRS feed

  • Question

  • I have a Azure Linux app service instance that has been running well for weeks not. I went to check on it this morning. SSH to app through azure web ssh. Chdir to log directory and had a bunch of empty logs indicating the app had restarted a bunch of times. Tried to cat a log file and was told the file did not exist even though is is there in ls of directory. So I tried to restart app. Would not start. Messages from docker log indicate it can't find a file it needs (not one of my files) or that my app can't find it's log file (same as when I try to ls, it sees file with directory listing but can't access it). None of my deployment slots are running either. Can't ssh to anything anymore. Docker log:

    2019-09-04 23:35:25.405 INFO  - docker run -d -p 8104:8081 --name vibackend__e394_0_fa2cbed0_msiProxy -e WEBSITE_SITE_NAME=vibackend -e WEBSITE_AUTH_ENABLED=False -e WEBSITE_ROLE_INSTANCE_ID=0 -e WEBSITE_HOSTNAME=vibackend.azurewebsites.net -e WEBSITE_INSTANCE_ID=40246b89542972727ac11c54edceb52d89c7db18f79fd8034ec2ba95cd1d438f -e HTTP_LOGGING_ENABLED=1 appsvc/msitokenservice:1904260237
    2019-09-04 23:35:27.036 INFO  - Starting container for site
    2019-09-04 23:35:27.037 INFO  - docker run -d -p 37151:8000 --name vibackend__e394_0_fa2cbed0 -e WEBSITE_SITE_NAME=vibackend -e WEBSITE_AUTH_ENABLED=False -e WEBSITE_ROLE_INSTANCE_ID=0 -e WEBSITE_HOSTNAME=vibackend.azurewebsites.net -e WEBSITE_INSTANCE_ID=40246b89542972727ac11c54edceb52d89c7db18f79fd8034ec2ba95cd1d438f -e HTTP_LOGGING_ENABLED=1 appsvc/python:3.6_1908051448
    2019-09-04 23:35:29.246 INFO  - Initiating warmup request to container vibackend__e394_0_fa2cbed0_msiProxy for site vibackend__e394
    2019-09-04 23:35:33.110 INFO  - Container vibackend__e394_0_fa2cbed0_msiProxy for site vibackend__e394 initialized successfully and is ready to serve requests.
    2019-09-04 23:35:33.111 INFO  - Initiating warmup request to container vibackend__e394_0_fa2cbed0 for site vibackend__e394
    2019-09-04 23:35:46.752 ERROR - Container vibackend__e394_0_fa2cbed0 for site vibackend__e394 has exited, failing site start
    2019-09-04 23:35:46.755 ERROR - Container vibackend__e394_0_fa2cbed0 didn't respond to HTTP pings on port: 8000, failing site start. See container logs for debugging.
    /home/LogFiles/2019_09_04_RD00155DE2B9BB_msi_docker.log  (https://vibackend.scm.azurewebsites.net/api/vfs/LogFiles/2019_09_04_RD00155DE2B9BB_msi_docker.log)
    /home/LogFiles/webssh/pm2.log  (https://vibackend.scm.azurewebsites.net/api/vfs/LogFiles/webssh/pm2.log)Status_WatchFile :: Error Error: ENOENT: no such file or directory, open '/appsvctmp/status.txt'Status_WatchFile :: Error Error: ENOENT: no such file or directory, open '/appsvctmp/status.txt'Status_WatchFile :: Error Error: ENOENT: no such file or directory, open '/appsvctmp/status.txt'Status_WatchFile :: Error Error: ENOENT: no such file or directory, open '/appsvctmp/status.txt'Status_WatchFile :: Error Error: ENOENT: no such file or directory, open '/appsvctmp/status.txt'Status_WatchFile :: Error Error: ENOENT: no such file or directory, open '/appsvctmp/status.txt'Status_WatchFile :: Error Error: ENOENT: no such file or directory, open '/appsvctmp/status.txt'Status_WatchFile :: Error Error: ENOENT: no such file or directory, open '/appsvctmp/status.txt'Status_WatchFile :: Error Error: ENOENT: no such file or directory, open '/appsvctmp/status.txt'Status_WatchFile :: Error Error: ENOENT: no such file or directory, open '/appsvctmp/status.txt'

    I can't redeploy as that is not working. I can't access the app service file system. I can't think of anything else to do bu create a new app service and start over. Any suggestions?

    Wednesday, September 4, 2019 11:43 PM

Answers

  • Found. Somehow preload_app got turned off in my startup file and that caused a race condition in some setup code.
    • Marked as answer by viincllc Thursday, September 5, 2019 11:56 PM
    Thursday, September 5, 2019 11:56 PM

All replies

  • More info. Using kudu I can see the app's wwwroot. Looks like about 3-4 days ago something started to restart my app every 5 minutes (exactly 5 minutes). I'm guessing that is when the problem started and Azure kept trying to restart things. My log directory has lots of little log files in it now because of the restarts. Maybe a couple hundred though not thousands but I am wondering if I ran out of inodes or something? I shouldn't until I hit thousands of files not hundreds though so this doesn't make much sense.
    Wednesday, September 4, 2019 11:56 PM
  • Found. Somehow preload_app got turned off in my startup file and that caused a race condition in some setup code.
    • Marked as answer by viincllc Thursday, September 5, 2019 11:56 PM
    Thursday, September 5, 2019 11:56 PM
  • Hi vinncllc,

    We are glad you were able to resolve your issue. Thanks for sharing the solution that worked for you. 

    Thanks,

    Grace 

    Friday, September 6, 2019 6:41 PM
    Moderator