Broker and Linking log not generating- SDL Tridion 2009 SP-1

Question

I want to generate the Broker and Linking log in debug mode. I made the following changes in cd_broker_conf.XML and CD_LINK_CONFIG.XML

<Logger Level="debug">
  <FileLogger Level="debug" Location="D:/Tridion/log/cd_broker.log" 
                            MaximumFileSize="5M" NumberOfFiles="5"/>
</Logger>
<Logger Level="debug">
  <FileLogger Level="debug" Location="d:/tridion/log/cd_link.log" 
                            MaximumFileSize="5M" NumberOfFiles="5"/>
</Logger>

But still I cannot see the respective logs, for linking Could you please suggest what steps do I need to take. Note in our deployer server following services are running.

1. Tridion Monitoring Service
2. Tridion Content deployer
3. Tridion Cache Channel service

Looking forward for reply..

Answer 1

Looking at some posts on the good old Tridion Forums, I suspect that it is the format of your XML that needs tweaking.

First of all, I think that the file paths to the log files are case sensitive. You may want to double-check these.

Also, it appears that your slashes should go the other way. Taken from the Forums here (login required):

<?xml version="1.0" encoding="UTF-8"?>
<Configuration Version="5.4">
    <Global>
        <Logging>
            <Logger Level="error">
                <FileLogger Level="error" Location="C:\tridion\log\cd_broker.log"/>
                <!-- <ConsoleLogger Level="debug" Trace="false"/> -->
            </Logger>
        </Logging>
        ...
    </Global>
...
</Configuration>

Answer 2

If the configuration file contains errors like incorrect naming of attributes or non closed tags etc., then the respective service cannot determine where to log to. In that case the logging is diverted to the default logfile called TRIDION.LOG which is written in the Windows Temp directory.

Usually it can be found in C:\Windows\Temp.

Look for that file and see what errors are mentioned in there and solve them. Then after fixing the config files, yu can remove the errors from the TRIDION.LOG file or delete it and restart the Content Delivery services. Your TRIDION.LOG file should now remain empty (or in case you deleted it, it should not be generated at all).