Content Management and Capture

Content Management and Capture

Come for answers. Stay for best practices. All we’re missing is you.

 View Only

  • 1.  ICMSERVER.LOG file

    Posted Tue March 12, 2024 07:03 AM

    Hi everyone, I have a CM running in my host.

    The log file  ICMSERVER.LOG is using all the space (18Gb). Do you know if the log can be cleaned up ?[/home/icmadmin] ls -ltr
    total 37509912
    drwxr-xr-x    2 root     system          256 Feb 18 2022  lost+found
    -rwx------    1 icmadmin staff           686 Apr 20 2022  .profile
    -rwxrwxrwx    1 root     system   19205063842 Mar 11 17:46 ICMSERVER.LOG



    ------------------------------
    Claudio Keiji Iwata
    ------------------------------


  • 2.  RE: ICMSERVER.LOG file

    Posted Mon March 18, 2024 03:47 PM

    Hi Claudio,

    Typically this file only grows large with tracing is turned on for the LS or when the server is getting lots of errors.  You should check to make sure LS trace is not to a higher level than is needed.  Typically in a production system, this would be error level. 

    If there are lots of errors being written to the file, you probably want to check on why the errors are happening and address the underlying problem.  Otherwise the file will continue to grow.

    If the information in the file is not needed for debugging or diagnostics, it can be deleted.  CM itself does not require the information in the file unless a case is opened for a problem...



    ------------------------------
    Randy Richardt
    ------------------------------

    Original Message


  • 3.  RE: ICMSERVER.LOG file

    Posted Mon March 25, 2024 11:37 AM

    Hello Claudio,

    as you are on Linux / Unix you should not just delete the file, because the application still continues to write data into this iNode but you cannot see the filename anymore. If you simply want to cleanup the file, you should either configure a new File for Library Server logging in the Sysadmin Client and delete the old one afterwards, or just empty it like this "echo 0 > ICMSERVER.LOG". The 2nd way simply writes a 0 into the file and deletes the complete content written to the file before.

    best regards 
    Frank



    ------------------------------
    Frank Trila
    ------------------------------

    Original Message


  • 4.  RE: ICMSERVER.LOG file

    Posted Tue May 27, 2025 12:30 PM

    Maybe I'm too late.

    But:

    set tracelevel in icmstsyscontrol to 1 will enable logrotate for Library-Server (update icmstsyscontrol set tracelevel=1), so ICMSERVER.log will rotate and never be too full.

    Therefore also MULTIPLETRACEFILES must be set to 1 (update icmstsyscontrol multipletracefiles=1)

    See documentation ICMSTSysControl (System control) - IBM Documentation

    I reccomend logrotate for all Systems, even Test-Systems.

    Tracelevel 1 will shown in CM System Admin Client under Library-Server Configuration as "Basic trace"

    HTH



    ------------------------------
    Frank Schletz
    ------------------------------

    Original Message


  • 5.  RE: ICMSERVER.LOG file

    Posted Thu May 29, 2025 10:40 AM

    Hi Frank,

    We do not recommend using the circular logging in LS currently.  

    Here are the potential issues and the prereq for the multiple LS log in https://www.ibm.com/docs/en/content-manager/8.7.0?topic=settings-icmstsyscontrol-system-control. See below.

    Restriction: Although multiple trace files are supported for the library server, enabling the feature for a heavily used system might result in a deadlock or timeout because of the serialization. Additionally, the multiple trace files do not apply for a trace level of 0. Setting trace level to 0 bypasses the log rotation.

    So 
    1. The feature is only used for debug purposes because it will not be enabled if tracelevel=0.  
    2. It may cause a deadlock or timeout because of the serialization.
    We don't recommend using it in CM, especially in production system. The possible way to use it is that CM support may want to collect debug logs for some incidents and the support team suggests using it.



    ------------------------------
    Randy Richardt
    ------------------------------

    Original Message


Related Content