Pydio is not starting - "Binary logging not possible"

Hello,
I am using a self-compiled version of Cells v4.2.5, from stable branch.
I use a mysql docker image to connect to cells, ran as a systemd user service as follows:

# container-pydio-mysql.service
# autogenerated by Podman 4.5.1
# Tue Jul 18 15:10:54 MDT 2023

[Unit]
Description=Podman container-pydio-mysql.service
Documentation=man:podman-generate-systemd(1)
Wants=network-online.target
After=network-online.target
RequiresMountsFor=%t/containers

[Service]
Environment=PODMAN_SYSTEMD_UNIT=%n
Restart=on-failure
TimeoutStopSec=70
ExecStart=/usr/bin/podman run \
        --cidfile=%t/%n.ctr-id \
        --cgroups=no-conmon \
        --rm \
        --sdnotify=conmon \
        --replace \
        -d \
        --network db-net \
        --ip 10.2.80.2 \
        -p 3306:3306 \
        --name pydio-mysql \
        -e MYSQL_ROOT_PASSWORD=redacted \
        -e MYSQL_DATABASE=cells \
        -e MYSQL_USER=pydio \
        -e MYSQL_PASSWORD=redacted \
        -v /var/storage/express/pydio/mysql:/var/lib/mysql:z mysql:latest mysqld \
        --character-set-server=utf8mb4 \
        --collation-server=utf8mb4_unicode_ci \
        --log-bin
ExecStop=/usr/bin/podman stop \
        --ignore -t 10 \
        --cidfile=%t/%n.ctr-id
ExecStopPost=/usr/bin/podman rm \
        -f \
        --ignore -t 10 \
        --cidfile=%t/%n.ctr-id
Type=notify
NotifyAccess=all

[Install]
WantedBy=default.target

Pydio is ran as a systemctl user service as well:

# container-pydio.service
# autogenerated by Podman 4.5.1
# Tue Jul 18 15:11:17 MDT 2023

[Unit]
Description=Podman container-pydio.service
Documentation=man:podman-generate-systemd(1)
Wants=network-online.target
After=network-online.target
RequiresMountsFor=%t/containers

[Service]
Environment=PODMAN_SYSTEMD_UNIT=%n
Restart=on-failure
TimeoutStopSec=70
ExecStart=/usr/bin/podman run \
        --cidfile=%t/%n.ctr-id \
        --cgroups=no-conmon \
        --rm \
        --sdnotify=conmon \
        --replace \
        -d \
        --network db-net \
        --name pydio \
        -p 8080:8080 \
        -p 33060:33060 \
        -e CELLS_LOG_LEVEL=production \
        -e CELLS_GRPC_EXTERNAL=33060 \
        -e CELLS_EXTERNAL=https://arctos.bear-tetra.ts.net \
        -v synced:/var/cells/data/synced:z \
        -v photos:/var/cells/data/photos:z \
        -v /var/storage/express/pydio/data:/var/cells/data:z \
        -v /var/storage/express/pydio:/var/cells:Z fishetm/cells:latest
ExecStop=/usr/bin/podman stop \
        --ignore -t 10 \
        --cidfile=%t/%n.ctr-id
ExecStopPost=/usr/bin/podman rm \
        -f \
        --ignore -t 10 \
        --cidfile=%t/%n.ctr-id
Type=notify
NotifyAccess=all

[Install]
WantedBy=default.target

The db-net network that both containers are connected to:

[
     {
          "name": "db-net",
          "id": "41bed89eeac1b5f805c9e112c8bba91576f20e9f9077af6d621da6f6174f1b7e",
          "driver": "bridge",
          "network_interface": "cni-podman1",
          "created": "2023-07-31T04:31:58.202126047-06:00",
          "subnets": [
               {
                    "subnet": "10.2.0.0/16",
                    "gateway": "10.2.0.1"
               }
          ],
          "ipv6_enabled": false,
          "internal": false,
          "dns_enabled": false,
          "ipam_options": {
               "driver": "host-local"
          }
     }
]

Here is the error that appears each time Pydio is started:

 ERROR   pydio.server.manager    ✗There was an error while starting:server.Start grpc: service.Start pydio.grpc.user-key: dao.Initialization mysql: Error 1598: Binary logging not possible. Message: An error occurred during flush stage of the commit. 'binlog_error_action' is set to 'ABORT_SERVER'. Server is being stopped.

This causes it to be stuck at “Server is starting”.
To fix this I have tried to add --log-bin to mysql container as can be seen in its config. This worked temporarily, but after the server being off for a period of a few days, the error has returned and does not seem to plan on going away.

Is there a misconfiguration I have made here?
Many thanks,
Collin

Have you tried to disable binary logging?

2 Likes

This was the right solution the whole time. Thank you

1 Like

This topic was automatically closed 11 days after the last reply. New replies are no longer allowed.