Novell Error Logs
Favorite Rating: Why is my ndsd.log file growing so large?This document (7008927) is provided subject to the disclaimer at the end of this document. Environment Novell eDirectory 8.8 for Linux Situation While reviewing disk space utilization on linux, it was identified that the /var partition was 100% full. In drilling through the file system (with the help of du -h --max-depth=1), it was identified that the /var/opt/novell/eDirectory/log directory was using the lion's share of the partition.Additionally, the http://www.novell.com/documentation/nw6p/?page=/documentation/nw6p/adminenu/data/a2fet9f.html /etc/opt/novell/eDirectory/conf/nds.conf contained the following parameter: n4u.server.log-levels=LogInfo Resolution The quickest way to reverse this logging is to: remove the setting n4u.server.log-levels=LogInfo stop ndsd (rcndsd stop) move or delete ndsd.log (if you move it, insure it's to a different disk partition) either reboot the host or restart ndsd (rcndsd start) Additional Information The n4u.server.log-levels=LogInfo setting will log quite a bit of http://www.novell.com/support/kb/doc.php?id=7008927 eDirectory information into ndsd.log. The additional information will look very similar to the info one would see in ndstrace. More information on this setting can be found in the eDirectory documentation (Configuring Error Logging).Note: you cannot just delete the ndsd.log while ndsd is running as ndsd expects to always find the file. If ndsd.log, or any other ndsd file is missing, the process will close down the DIB with a -6038 error to protect the database from corruption. For more information, please see https://www.novell.com/support/kb/doc.php?id=7008704 DisclaimerThis Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND. Document ID:7008927Creation Date:30-JUN-11Modified Date:07-AUG-15NetIQeDirectory Did this document solve your problem? Provide Feedback © Micro Focus Careers Legal close Feedback Print Full Simple Request a Call Follow Us Facebook YouTube Twitter LinkedIn Newsletter Subscription RSS
follows: Create these files. See Creating Log and Error Files for information. View information contained in the log and error files. See Viewing a Log File and Viewing an Error File for information. Change the location of these files. See Setting the Location of Backup Log and Error Files for information. Delete these files. See Deleting the Log Files for information. 3.6.1 Creating Log and Error Files If you do not know what is on the media, or you have lost or deleted the log and error files, you can re-create them. Ensure that you have met the prerequisites detailed in Section 3.1, Prerequisites for Performing SBCON Tasks. To create a log or error file, see Section 3.7, Creating Session Files. 3.6.2 Viewing a Log File This task lets allows you to view your log file for backup and restore information. The log file is created on the host server the first time data is backed up or restored and contains details about the session. Ensure that you have met the prerequisites detailed in Section 3.1, Prerequisites for Performing SBCON Tasks. From the SBCON Main Menu, select Log File Administration > View a Log File. If necessary, set the location of the log and error files for a backup session. (This option is not supported for a restore session.) To set the location, use one or more of the following methods: Press Enter to accept the default location, and then go to Step 3. Press Insert to select from a list of network directories, select a directory, then press Esc to return to the previous window, and then go to Step 3. To change the directory, delete the existing directory path and type a new one, then go to Step 3. You can also press Insert during this process to select existing parts of the path from a list. The backup log displays all supported name space types. The creator name space is the first in the group and a right-angle bracket (>) appears next to it. If you have linked UNIX files, SBCON retains both symbolic and har