Cloud Pak for Data

Cloud Pak for Data

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

 View Only
Back to discussions
Expand all | Collapse all

Data management console instantiation fail - redis permission denied

  • 1.  Data management console instantiation fail - redis permission denied

    Posted Thu February 16, 2023 09:34 AM
    Edited by Kristen Park Fri February 17, 2023 09:40 AM

    Hello,

    I instantiated a data management console on my CP4D 4.6.2 yesterday. The installation failed as most pods related to the dmc are in a  crash loop back-off.

    I dug deeper and I think the problem comes from the redis pods.

    Here are the logs for some of the pods in a crash loop back off. The logs are the same for the monitor, explain, admin, dbapi, runsql pods.

    Starting console...
    mkdir: cannot create directory '/mnt/pv/unified_console_data/realconfigs': Permission denied
    mkdir: cannot create directory '/mnt/pv/unified_console_data/reallogs': Permission denied
    touch: cannot touch '/mnt/pv/unified_console_data/reallogs/monitor_3.1.9-164-x86_64_22015-monitor-0/console.token': No such file or directory
    touch: cannot touch '/mnt/pv/unified_console_data/reallogs/monitor_images': No such file or directory
    cat: /mnt/pv/unified_console_data/reallogs/monitor_images: No such file or directory
    /scripts/utils.sh: line 126: /mnt/pv/unified_console_data/reallogs/monitor_images: No such file or directory
    touch: cannot touch '/opt/ibm-datasrvrmgr/logs/messages.log': No such file or directory
    touch: cannot touch '/opt/ibm-datasrvrmgr/logs/repoUtil.0': No such file or directory
    touch: cannot touch '/opt/ibm-datasrvrmgr/logs/status.log': No such file or directory
    touch: cannot touch '/opt/ibm-datasrvrmgr/logs/monitor.0': No such file or directory
    importing redis tls cert
    keytool import cert for REDIS_SERVER_HOST_1
    Warning: use -cacerts option to access cacerts keystore
    Certificate was added to keystore
    no more redis host, exit loop
    FIPS is turned off. The underlying container/cluster does not seem to have FIPS mode enabled.
    Thu Feb 16 08:59:33 UTC 2023 startup begin
    Updating the application server bootstrap properties ...
    Updating the application server environment properties ...
    Updating the applications ...
    Does not find settings for icp4d_enterprise.app.exclude.
    Thu Feb 16 08:59:33 UTC 2023 start the wlp server
    mkdir: cannot create directory '/opt/ibm-datasrvrmgr/logs': File exists
    /opt/ibm-datasrvrmgr/wlp/bin/server: line 1003: /opt/ibm-datasrvrmgr/logs/console.log: No such file or directory
    Starting server dsweb.
    [ps, -p, 214]
    PID TTY TIME CMD
    Exit code for 'ps' command: 1
    Server start error: file lock obtained, and server process is not running.
    Server dsweb start failed. Check server logs for details.
    Start failed. Please try to start manually.
    2023-02-16 08:59:35 : Console started failed!
    They all are linked to a wait-redis container. So I looked into my redis container that are running to see if there was an issue. And there is, in the logs, we have this in repeat.
    # Configuration loaded
    # Can't open the append-only file: Permission denied
    # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
    # Redis version=5.0.14, bits=64, commit=00000000, modified=0, pid=1044, just started
    # Configuration loaded
    # Can't open the append-only file: Permission denied
    # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
    # Redis version=5.0.14, bits=64, commit=00000000, modified=0, pid=1044, just started
    I also have an issue with the nginx pod, here are the logs on repeat in a running container
    Ncat: Version 7.70 ( https://nmap.org/ncat )
    Ncat: Connection to ::1 failed: Connection refused.
    Ncat: Trying next address...
    Ncat: Connection refused.
    Ncat: Version 7.70 ( https://nmap.org/ncat )
    Ncat: Connection to ::1 failed: Connection refused.
    Ncat: Trying next address...
    Ncat: Connection refused.
    Does anyone have a idea as to how what could cause this issue and how to fix it ?



  • 2.  RE: Data management console instantiation fail - redis permission denied

    Posted Wed March 01, 2023 09:15 AM

    Hello,

    I figured out my issue, posting it here if it can help someone else. The issue was that the storage class selected to create the instance was incorrect.

    So deleting the instance and recreating it with the storage class that is used by all other services was the way to go.



    ------------------------------
    Lucile Jerber
    ------------------------------

    Original Message


Related Content