Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-3995

Logs are not sent to STDOUT

    XMLWordPrintable

    Details

      Description

      I've encountered two loosely coupled issues and am interested in contributing to their resolution.

      1. Maxscale Docker images no longer log to stdout after version 2.5.X (difficult to determine, see follow up issue). This is obviously problematic, as this is how Docker aggregates logs. A brief investigation determined that this was due to an entrypoint script.

        [root@0db4086c260e /]# ps -ewwf
        UID        PID  PPID  C STIME TTY          TIME CMD
        root         1     0  0 Jan05 ?        00:01:16 /usr/bin/tini -- docker-entrypoint.sh /bin/sh -c maxscale-start && monit -I
         
        [root@0db4086c260e /]# cat /usr/bin/docker-entrypoint.sh
        #!/bin/bash
         
        function exitMaxScale {
                /usr/bin/monit unmonitor all
                /usr/bin/maxscale-stop
                /usr/bin/monit quit
            }
         
        rm -f /var/run/*.pid
        rsyslogd
         
        trap exitMaxScale SIGTERM
         
        exec "$@" &
         
        wait 
        

        To the best of my understanding, this exists to triage maxscale into a multi-process container (monit managing maxscale and rsyslog). I am not familiar with rsyslog, and consequently cannot comment on its necessity, but ideally logs are sent to stdout to re-enable process logging.

      2. Upon discovery of the aforementioned issue, I began to investigate the github repository to find additional information (e.g. when rsyslog was introduced, its purpose, etc.). My first stop was to identify when the new entrypoint was defined, as that would provide the most contextual information. However, the Dockerfile presented within the repository hasn't been updated in four years (version 2.2). Consequently, it is difficult to perform further investigative efforts or contribute to the project.

      Please advise on how I should proceed.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              esa.korhonen Esa Korhonen
              Reporter:
              wscott William Scott
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:

                  Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.