John Braga
Nuke Active Member
Posts:34
 |
| 09/25/2011 4:05 PM |
|
I have created a 6.01 website, using the standard Dark Knight skin, on Windows Web Server R2. I have checked the logging in IIS and it is pointing to %systemdrive%\inetpub\logs, which I think is the standard location.
But this site is ALSO logging to the Portals folder (portals\_default\logs). This is causing problems because I have a scheduled backup job running at 3am to backup the website folder, and it fails because it can't open the logfile for reading (I think Google Bot is checking the site at that time)
Is this new to Dnn 6? Is there a way I can get it to log somewhere else? Anyone else found this? Is there a setting I have overlooked?
Thanks for any suggestions! |
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 09/25/2011 10:15 PM |
|
If you go to the DotNetNuke website and look for Providers in the Wiki, you will find a short discussion about logging providers.
I actually noticed that one of my sites apparently has the two providers defined, so I have some digging to do.
That doesn't explain why you seem to have file permissions set incorrectly. I would think that you should look at that too |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 09/25/2011 10:15 PM |
|
If you go to the DotNetNuke website and look for Providers in the Wiki, you will find a short discussion about logging providers.
I actually noticed that one of my sites apparently has the two providers defined, so I have some digging to do.
That doesn't explain why you seem to have file permissions set incorrectly. I would think that you should look at that too |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
John Braga
Nuke Active Member
Posts:34
|
| 09/26/2011 3:36 PM |
|
Hi Joe
I have checked permissions. The folders backup utility is running as me, and I am an administrator. This user has full rights to The Portals folder, and its subfolders, so I can only think DNN is denying all other users rights to its log files (site log?, event log?)
It seems strange that DNN is so flexible in so many ways, but there does not seem to be an easy way to direct where the site logging should go?
John B |
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 09/26/2011 3:45 PM |
|
It's the IIS User who creates the files, so maybe that is an issue. The link that I sent suggests that you not use this logging provider, but use the other one. I check a site of mine and web.config has this for the logging: <logging defaultProvider="DBLoggingProvider">
<providers>
<clear />
<add name="DBLoggingProvider" type="DotNetNuke.Services.Log.EventLog.DBLoggingProvider.DBLoggingProvider, DotNetNuke.Provider.DBLoggingProvider" providerPath="~\Providers\LoggingProviders\DBLoggingProvider\" />
</providers>
</logging>
You might want to upgrade your web.config. |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
John Braga
Nuke Active Member
Posts:34
|
| 09/26/2011 4:54 PM |
|
I had forgotten that sitelogs and eventlogs are put in the sql database, not in files.
So who is creating log files in Portals\_Default\logs??? They appear to be line traces generated by IIS (judging by the first line), but I dont understand how IIS could know about the existence of the Portals\Logs folder?? It must be DNN. But which module and why?
|
|
|
|
|
John Braga
Nuke Active Member
Posts:34
|
| 09/26/2011 4:56 PM |
|
Sorry Joe, I sent the last message before seeing your reply about changing logging provider. I will give that a try.
John B |
|
|
|
|
John Braga
Nuke Active Member
Posts:34
|
| 09/26/2011 5:02 PM |
|
Have just checked dbloggingprovider, and my web.config is already set as per your link above
John B |
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 09/26/2011 7:39 PM |
|
Have you tried the DotNetNuke forums? I'm running out of ideas. |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
John Braga
Nuke Active Member
Posts:34
|
| 09/27/2011 2:11 AM |
|
I went to the Dotnetnuke forums last night and Cathal Connolly came back quickly saying it is a new DNN 6 feature, called Log4net (which I see is a well-regarded tool that originated on Apache). He gave me a reference http://www.dotnetnuke.com/Resources...tNuke.aspx and I can turn the feature OFF if I wish. Well, something very useful learnt! Also looks as if I could leave it enabled but move the file location. |
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 09/27/2011 8:01 AM |
|
Thanks for the information, John. Yes, this is a new feature, and one that I had pretty much ignored. For those interested, take a look here: http://www.dotnetnuke.com/Resources...tNuke.aspx It looks like this can be a big help for tracking down problems, especially with the more verbose forms of logging. The basic features: 1. You can control the detail in the file. 2. It's formatted to be read by a human. 3. You control the file sizes and the number that are stored (so this can't fill up your computer's disk drive). I think that you'll be seeing a lot more requests from me for folks to look here rather than in the eventlog. |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
John Braga
Nuke Active Member
Posts:34
|
| 09/28/2011 4:26 AM |
|
I am currently having a problem switching location for this logging. I have changed the dotnetnuke.log4net.config, but the system currently takes no notice... I have put another question on the DNN forums. This is a very useful video http://www.dotnetnuke.com/Resources...rview.aspx that shows the use of the very powerful Log4View utility, tracing to a UDP port. |
|
|
|
|