Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Error when migrating mariadb database during the latest upgrade to 2.6.9

Aperta
  • Qualcosa non va?
#415 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
docker-compose, mariadb
Ambito
databases, devops

Direzione di ricerca

Inizia riproducendo la migrazione docker-compose sulla configurazione MariaDB segnalata e ispezionando la migrazione non riuscita Application\Migrations\Version20190806130304. Traccia il motivo per cui la colonna language rifiuta i dati delle righe esistenti; il lavoro è completato quando la migrazione termina correttamente senza troncamento.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

I'm unable to login to the wallabag after an update. I ran the database migration command (the one for docker-compose) but I get the following error during the update. Looks like something is unusual about my database that is tripping the migration. Any advice?

[notice] Migrating up to Application\Migrations\Version20230613121354
[notice] Migration Application\Migrations\Version20160401000000 skipped during Execution. Reason: "Database already initialized"
[notice] Migration Application\Migrations\Version20170327194233 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20170405182620 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20170407200919 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20170501115751 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20170511115400 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20170602075214 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20170606155640 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20170824113337 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20171105202000 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20171120163128 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20171125164500 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20190619093534 skipped during Execution. Reason: "Migration can only be executed safely on 'sqlite'."
[error] Migration Application\Migrations\Version20190806130304 failed during Execution. Error: "An exception occurred while executing a query: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'language' at row 631"
01:25:22 CRITICAL [console] Error thrown while running command "doctrine:migrations:migrate --env=prod --no-interaction". Message: "An exception occurred while executing a query: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'language' at row 631" ["exception" => Doctrine\DBAL\Exception\DriverException^ { …},"command" => "doctrine:migrations:migrate --env=prod --no-interaction","message" => "An exception occurred while executing a query: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'language' at row 631"]

In ExceptionConverter.php line 117:

An exception occurred while executing a query: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'language' at row 631

In Exception.php line 28:

SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'language' at row 631

In Connection.php line 71:

SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'language' at row 631

Here is my docker-compose:

version: '3'
services:
wallabag:
image: wallabag/wallabag
container_name: wallabag
restart: unless-stopped
environment:
- MYSQL_ROOT_PASSWORD=[rootpassword]
- SYMFONY__ENV__DATABASE_DRIVER=pdo_mysql
- SYMFONY__ENV__DATABASE_HOST=db
- SYMFONY__ENV__DATABASE_PORT=3306
- SYMFONY__ENV__DATABASE_NAME=wallabag
- SYMFONY__ENV__DATABASE_USER=wallabag
- SYMFONY__ENV__DATABASE_PASSWORD=[password]
- SYMFONY__ENV__DATABASE_CHARSET=utf8mb4
- SYMFONY__ENV__DATABASE_TABLE_PREFIX="wallabag_"
- SYMFONY__ENV__MAILER_HOST=127.0.0.1
- SYMFONY__ENV__MAILER_USER=[email_address]
- SYMFONY__ENV__MAILER_PASSWORD=[password]
- SYMFONY__ENV__FROM_EMAIL=wallabag@domain
- SYMFONY__ENV__DOMAIN_NAME=https://myurl
#- SYMFONY__ENV__DOMAIN_NAME=
ports:
- "8090:80"
volumes:
- /home/mford6/config/wallabag/images:/var/www/wallabag/web/assets/images
healthcheck:
test: ["CMD", "wget" ,"--no-verbose", "--tries=1", "--spider", "http://localhost/api/info"]
interval: 1m
timeout: 3s
depends_on:
- db
- redis
db:
image: mariadb:latest
container_name: mariadb
environment:
- MYSQL_ROOT_PASSWORD=[rootpassword]
volumes:
- /home/mford6/config/wallabag/data:/var/lib/mysql
restart: unless-stopped
healthcheck:
#test: ["CMD", "mysqladmin" ,"ping", "-h", "localhost"]
##test: ["CMD", "mariadb-admin" ,"ping", "-h", "localhost", "--password=[password]"]
##interval: 20s
##timeout: 3s
test: ["CMD", "/usr/local/bin/healthcheck.sh" ,"--innodb_initialized"]

Lingua principale
Shell
Stelle
771
Fork
168
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di wallabag/docker

Tutte le issue di wallabag/docker

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.