Enable debugging on clients

Last post 07-21-2010, 12:10 PM by Dannie. 2 replies.
Sort Posts: Previous Next
  • Enable debugging on clients
    Posted: 07-20-2010, 6:59 AM

    On the Commserv, there is a program "SetLogFileParams.exe" to enable debugging for various parts.

    How can I enable debugging on a client? I have a Tru64 client which takes forever to do a filescan, so I'd like to enable debugging and see what takes so long (truss didn't help me here).

    I enabled "Filescan" under "iDataAgent" on the Commserv, restarted the client, but the logging is exactly the same as with debugging diabled.

    Is there a registry key I can set?


    If it jams, force it.
    If it breaks, it needed replacing anyway.
  • Re: Enable debugging on clients
    Posted: 07-20-2010, 4:14 PM
    • mhz is not online. Last active: 08-20-2019, 5:09 PM mhz
    • Top 500 Contributor
    • Joined on 06-18-2010
    • Oceanport, NJ
    • Novice
    • Points 61

    You can create an empty file on the Tru64 server called, /tmp/DebugAppleDouble.HOOK. This will flood the FileScan.log file with messages showing exactly where the ifind process is as it is processing. If ifind hangs, this will show the filesystem path to where it is stuck.


    Martha
    Customer Engineer Unix/DB
  • Re: Enable debugging on clients
    Posted: 07-21-2010, 12:10 PM

    mhz:

    You can create an empty file on the Tru64 server called, /tmp/DebugAppleDouble.HOOK. This will flood the FileScan.log file with messages showing exactly where the ifind process is as it is processing. If ifind hangs, this will show the filesystem path to where it is stuck.

    Smile thank you. I also found a couple of those /tmp/* thingies in strace and truss. Didn't see this one yet though :)


    If it jams, force it.
    If it breaks, it needed replacing anyway.
The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy