Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

After publish to IIS, app does not log to stdout

See original GitHub issue

Steps to reproduce

Target 1.1.1 .net core VS2017. Deploy app to IIS using standard Program.cs–

var host = new WebHostBuilder()
                .UseKestrel()
                .UseUrls("http://localhost:5001")
                .UseContentRoot(Directory.GetCurrentDirectory())
                .UseIISIntegration()
                .UseStartup<Startup>()
                .UseApplicationInsights()
                .Build();

enable logging via published web.config file

stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout"

Expected behavior

Expect log\stdout_xxxx file to be created and updated when server errors occur.

Actual behavior

No file is created, no event in event viewer

Environment data

dotnet --info output: N/A, production IIS machine

Issue Analytics

State:
Created 7 years ago
Reactions:2
Comments:13 (5 by maintainers)

Top GitHub Comments

9reactions

toddlangdoncommented, Sep 8, 2018

I was having this same problem. Verified that web.config had stdoutLogEnabled=“true”, that logs folder existed and app pool identity had write permissions but still no log file. After I manually recycled App Pool it started working - you you might want to try that

8reactions

fernandezjosecommented, Aug 11, 2018

I have everything “in place”, including IIS APPPOOL, however, nothing is being outputted. I am using .Net Core 2.1