Strange sudden error in Azuracast

[stoccafisso]

A few days ago I had a somewhat "working" version of Azuracast actually running.

It was one of the apps I temporarily uninstalled to make space for solving the problem with the newly Rocket.Chat log-filling-the-disk problem.

I have now reinstalled Azuracast, but it refuses to start, giving this strange message in the logs

Jan 28 12:45:22 2025-01-28T11:45:22Z
Jan 28 12:45:22 Exception trace:
Jan 28 12:45:22 at /app/code/www/vendor/doctrine/dbal/src/Driver/PDO/Exception.php:28
Jan 28 12:45:22 Doctrine\DBAL\Driver\PDO\Exception::new() at /app/code/www/vendor/doctrine/dbal/src/Driver/PDO/Connection.php:62
Jan 28 12:45:22 Doctrine\DBAL\Driver\PDO\Connection->query() at /app/code/www/vendor/doctrine/dbal/src/Connection.php:772
Jan 28 12:45:22 Doctrine\DBAL\Connection->executeQuery() at /app/code/www/vendor/doctrine/migrations/lib/Doctrine/Migrations/Version/DbalExecutor.php:273
Jan 28 12:45:22 Doctrine\Migrations\Version\DbalExecutor->executeResult() at /app/code/www/vendor/doctrine/migrations/lib/Doctrine/Migrations/Version/DbalExecutor.php:150
Jan 28 12:45:22 Doctrine\Migrations\Version\DbalExecutor->executeMigration() at /app/code/www/vendor/doctrine/migrations/lib/Doctrine/Migrations/Version/DbalExecutor.php:72
Jan 28 12:45:22 Doctrine\Migrations\Version\DbalExecutor->execute() at /app/code/www/vendor/doctrine/migrations/lib/Doctrine/Migrations/DbalMigrator.php:88
Jan 28 12:45:22 Doctrine\Migrations\DbalMigrator->executePlan() at /app/code/www/vendor/doctrine/migrations/lib/Doctrine/Migrations/DbalMigrator.php:54
Jan 28 12:45:22 Doctrine\Migrations\DbalMigrator->executeMigrations() at /app/code/www/vendor/doctrine/migrations/lib/Doctrine/Migrations/DbalMigrator.php:136
Jan 28 12:45:22 Doctrine\Migrations\DbalMigrator->migrate() at /app/code/www/vendor/doctrine/migrations/lib/Doctrine/Migrations/Tools/Console/Command/MigrateCommand.php:219
Jan 28 12:45:22 Doctrine\Migrations\Tools\Console\Command\MigrateCommand->execute() at /app/code/www/vendor/symfony/console/Command/Command.php:279
Jan 28 12:45:22 Symfony\Component\Console\Command\Command->run() at /app/code/www/vendor/symfony/console/Application.php:1049
Jan 28 12:45:22 Symfony\Component\Console\Application->doRunCommand() at /app/code/www/vendor/symfony/console/Application.php:318
Jan 28 12:45:22 Symfony\Component\Console\Application->doRun() at /app/code/www/vendor/symfony/console/Application.php:169
Jan 28 12:45:22 Symfony\Component\Console\Application->run() at /app/code/www/bin/console:12
Jan 28 12:45:22 2025-01-28T11:45:22Z
Jan 28 12:45:22 In Connection.php line 57:
Jan 28 12:45:22
Jan 28 12:45:22 [PDOException (42S21)]
Jan 28 12:45:22 SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'lyrics' 

SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'lyrics'?

What could possibly occupy that column name from....other apps....or something else?

[nebulon]

Maybe there is some initial startup race in the package. Tbh I am not sure if we can recommend using that, given that we have hit a few issues and there was really not much interest by users, and thus it hasn't really reached a stable package state yet.

For a start is this error easily reproducible when reinstalling?