•  
      request #35881 Docker container not starting because PDO connection can't be created
    Infos
    #35881
    Martin Herbst (dstg)
    2024-01-29 15:39
    2024-01-29 14:10
    37467
    Details
    Docker container not starting because PDO connection can't be created

    I have setup docker compose according to the installation documentation. After updating to the stack to the latest version the web does no longer start.

    The log contains the following messages:

    Start init sequence for Tuleap Community Edition — Dev Build 15.4.99.192
    Create link to persistent storage for /etc/pki/tls/private/localhost.key.pem
    Create link to persistent storage for /etc/pki/tls/certs/localhost.cert.pem
    Create link to persistent storage for /etc/tuleap
    Create link to persistent storage for /root/.tuleap_passwd
    Create link to persistent storage for /var/lib/gitolite
    Create link to persistent storage for /var/lib/tuleap
    Could not create a PDO connection. Please check your username and password.
    Start init sequence for Tuleap Community Edition — Dev Build 15.4.99.192
    Could not create a PDO connection. Please check your username and password.
    

    The configured username and password are correct. I can use the to logon to mysql from the mysql container. Any ideas what could be wrong?

    Docker images
    15.4
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Verified
    Empty
    Attachments
    Empty
    References
    References list is empty

    Follow-ups

    User avatar
    Martin Herbst (dstg)2024-01-29 15:39

    Thanks for the quick answert and your hint. We are managing our containers with Portainer and the DB was already up.

    But the reason for the problem was the limit of user processes. With docker-compose on the command I could see the errors that caused the problem.

    You can close this issue.

    User avatar

    TL;DR docker-compose up -d db first and after logs tell you that the DB is up docker-compose up -d

    It can happen during compose up with contenerized db. Tuleap container assumes that the DB is up, if the db is still starting it aborts.


    • Status changed from New to Verified