Troubleshooting and help

If access to the Relution system administrator account has been lost and the password cannot be reset using the configured email address, it is also possible to reset the password from the database. This procedure requires write access to the database server and Relution’s database.

Please try to reset the password via the forgotten password? link before trying to reset it from the database. See this option only as a last resort.

To reset the password, first log in via the command line or an administration tool to connect to the database. Then run the SQL script that is appropriate for the database server.

Reset password via database #

MariaDB/MySQL #

    UPDATE security_user usr
        JOIN security_organization org on org.uuid = usr.organization_uuid
        SET password = SHA1(CONCAT('password123', '{', usr.uuid, '}'))
        WHERE usr.name = 'admin'
        AND org.name = 'system';

Replace password123 with the new desired password.

Microsoft SQL Server #

    UPDATE security_user SET password = LOWER(CONVERT(VARCHAR(40), HASHBYTES('SHA1', CONCAT('password123', '{', usr.uuid, '}')), 2))
        FROM security_organization org
        JOIN security_user usr on usr.organization_uuid = org.uuid
        WHERE usr.name = 'admin'
        AND org.name = 'system';

Replace password123 with the new desired password.

Server does not start #

Please check the log files in the log directory, which is located inside the Relution installation directory.
If the problem cannot be identified independently, please open a support ticket and provide us with the logs.

Log files #

Where to find log files for Docker, Linux, and Windows is described under Relution Logs →.

Performance analysis with Glowroot #

In case of performance problems, Relution support may ask for an analysis using Glowroot. Glowroot records which requests take how long and shows the result in a web interface of its own.

When running in Docker, Glowroot is not part of the image, it is downloaded automatically on startup as soon as RELUTION_ENABLE_GLOWROOT is set:

  relution:
    image: relution/relution:latest
    environment:
      - RELUTION_ENABLE_GLOWROOT=true
      - RELUTION_GLOWROOT_ADMIN_JSON_BASE64=ewogICJ3ZWIiOiB7CiAgICAiYmluZEFkZHJlc3MiOiAiMC4wLjAuMCIKICB9Cn0=
    ports:
      - '4000:4000'

The second variable merely contains the base64 encoded Glowroot configuration {"web": {"bindAddress": "0.0.0.0"}}. Without it, the interface can only be reached from inside the container. After restarting the container it is available on port 4000.

The recordings are kept inside the container and are lost as soon as it is recreated. For the duration of an analysis this is usually sufficient. To keep them, set RELUTION_GLOWROOT_DIR to a directory writable for UID 20001.

To disable it, remove RELUTION_ENABLE_GLOWROOT again and restart the container.

Security notes #

• Install the latest operating system and software updates and security patches
• Use strong passwords for administrator accounts
• Use long passwords for service-to-service communications, Passwords do not need to be used or remembered by humans
• Make sure the user account used to access LDAP has Read-only access
• Do not create accounts with weak passwords such as password or test
• Do not store passwords in files that are globally readable