out of disk space running webjob

Category: azure websites


Jose Simoes on Fri, 25 Jul 2014 15:05:13


I'm running into this out of disk space error running a few webjobs on a website.

The website is a "shared" one. On the site dashboard the File System Storage shows about 60% free. But after a while running I can't upload new webjobs because the zip upload fails. Also the ones running start failing with a Kudu exception out of disk space.

I connect to the site with an FTP client and I can see that a number of folders with what look timestamps are pilling up there. Even noticed that web jobs that I deleted hours ago have entries there. The folders have an output_log.txt file there. These files have entries such as the following:

[07/25/2014 14:44:38 > b41857: SYS INFO] Status changed to Initializing
[07/25/2014 14:44:41 > b41857: SYS INFO] Run script 'NNNNNNNNNNNNN.exe' with script host - 'WindowsScriptHost'
[07/25/2014 14:44:41 > b41857: SYS INFO] Status changed to Running
[07/25/2014 14:44:43 > b41857: INFO] Executing: 'ZZZZZZZZZZZZZZZZZZZZZZZZZZ' because This was function was programmatically called via the host APIs.
[07/25/2014 14:44:47 > b41857: SYS INFO] Status changed to Success

After manually deleting a bunch of those folders I was able to upload new webjob zips and the ones running resumed working.


- I'm I doing something wrong in my code that is keeping the log files from being purged?

- Is there an issue with websites that don't perform a clean up/purge on the webjobs folders?

- Anything else that I'm missing?




Zain Rizvi on Fri, 25 Jul 2014 17:36:11

In the portal, under the configuration tab, do you have "APPLICATION LOGGING (FILE SYSTEM)" turned on? Those entries look like they're logs generated by the webjobs you're running.

What's the full path to the files you are seeing?

Jose Simoes on Fri, 25 Jul 2014 17:42:34


I have all logging options set to OFF.

As for the paths, follows some examples:



Jim Cheshire on Fri, 25 Jul 2014 20:28:26

Limit the amount of Console.Out and Console.Error because those will be routed to the output logs. You can also modify the WEBJOBS_HISTORY_SIZE and configure the max number of histories you want to keep in output logs. Using this method, you can cut the size of this to almost nothing. :)

To change this, just add an app setting for your site called WEBJOBS_HISTORY_SIZE and set it to the desired size. For example, if you set it to 1, you'll only have one of these folders containing the latest entry. Keep in mind, however, that if you set it to 0, it won't disable logging. It will essentially act as if you haven't set a history limit at all. In other words, don't set it lower than 1. ;)

Jose Simoes on Sat, 26 Jul 2014 02:36:41

Thanks Jim.

That did it! I now have the log size under control.