IBM Security Verify

 View Only

  • 1.  Can't manage reverse proxy log files from LMI

    Posted Sun May 01, 2022 08:08 AM
    Hello,

    We use ISAM 9.0.7.2 with two instances to proxy user traffic. I recently found that I can't manage reverse proxy log files from graphical console (LMI). When I select from the top menu "Secure Web Settings → Manage Reverse Proxy → <any instance> → Troubleshooting → Logging", the error message appears: [!] Sorry, an error occurred. The same message appears if you use the menu "Monitor Analysis and Diagnostics → Logs Manage Reverse Proxy Log Files". Files exist on the disk (checked by creating the support file). Restarting the server doesn't help.
    What could be the reason or at least how to get detailed information of error (from which component of LMI tracing)?


    ------------------------------
    Anatoly
    ------------------------------


  • 2.  RE: Can't manage reverse proxy log files from LMI

    Posted Sun May 01, 2022 04:23 PM

    Anatoly,

     

    The only reason I can think that you might be encountering this issue is if you have run out of disk space on the appliance.  Have you checked the available disk space?  Failing this, I would suggest that you raise a support ticket with IBM so that the support team can investigate further.

     

    Thanks.

     

     

    Scott A. Exton
    Senior Software Engineer
    Chief Programmer - IBM Security Verify Access
    IBM Master Inventor

     

     




    Original Message


  • 3.  RE: Can't manage reverse proxy log files from LMI

    Posted Mon May 02, 2022 01:26 AM
    Scott,

    Thanks for the comments. The problem is definitely not due to disk space, because 19% was originally used. Then trying to find the cause, I deleted the ISAM logs through the terminal (ssh) and the value dropped to 14%.
    Ok, I'll open a ticket. It would be interesting to get a full description of the error, but I don't know which component of LMI tracing needs to be enabled for this.

    ------------------------------
    Anatoly Nazarenko
    ------------------------------

    Original Message