Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wallabag : mySQL root password issue #3113

Closed
pfml opened this issue Jan 18, 2018 · 24 comments
Closed

Wallabag : mySQL root password issue #3113

pfml opened this issue Jan 18, 2018 · 24 comments
Labels

Comments

@pfml
Copy link

pfml commented Jan 18, 2018

For new Package Requests, see the guidelines

Setup

Package Name: Wallabag
Package Version: 2.2.3-2

NAS Model: DS411+
NAS Architecture: Intel Atom D510
DSM version: DSM 6.1.4-15217 Update 5

Expected behavior

Try to install package wallabag on my Syno (php 5.6 & 7.0, MariaD B10 and WebStation enabled)

Actual behavior

Got an error msg : "failed to install "wallabag". Incorrect MySQL root password"
Using phpMyAdmin and MariaDB root password, I'm able to create/delete account

Steps to reproduce

1.
2.
3.

Package log

Check Package Center or /usr/local/{package}/var/

found no log in the mentioned places

Other logs

E.g. /var/log/messages or /var/log/synopkg.log

in /var/log/messages :

2018-01-18T14:55:07+01:00 cezoffnas02 synoscgi_SYNO.Core.Package.Server_1_list[12263]: pkgcurltool.cpp:456 http://packages.missilehugger.com, Failed to request packages, httpResponseCode=404
2018-01-18T15:07:02+01:00 cezoffnas02 synoscgi_SYNO.Core.Package.Installation_1_install[2283]: pkginstall.cpp:466                                                             Failed to run preinst script for wallabag, 1

in /var/log/synopkg.log

2018/01/18 15:07:02     install wallabag 2.2.3-2 Begin preinst
2018/01/18 15:07:02     install wallabag 2.2.3-2 End preinst ret=[1]
2018/01/18 15:07:02     install wallabag 2.2.3-2 Begin /bin/rm -rf /volume1/@tmp/pkginstall
2018/01/18 15:07:28     install wallabag 2.2.3-2 End /bin/rm -rf /volume1/@tmp/pkginstall ret=[0]
2018/01/18 15:07:28     install wallabag 2.2.3-2 failed
@MysteryWoMan
Copy link

Have you tried this? :
Log in on your Synology device using telnet or SSH (with your admin account).

mkdir /usr/syno/mysql
mkdir /usr/syno/mysql/bin 
ln -s /usr/bin/mysql /usr/syno/mysql/bin/mysql

or

mkdir /usr/syno/mysql
mkdir /usr/syno/mysql/bin
ln -s /volume1/@appstore/MariaDB10/usr/bin/mysql /usr/syno/mysql/bin/mysql

#2093 #2217 #2304 #2307

@pfml
Copy link
Author

pfml commented Jan 25, 2018

Many thanks for the reply.
Tried both, without success 😟

Having installed MariaDB10, I made a search in the directories to find the most relevant link to establish. Tried
/volume1/@appstore/MariaDB10/usr/local/mariadb10/bin/mysql
, without success.
Made a try with MariaDB 5 : made a fresh install of the database package, and tried to install wallabag package. It takes a while, but I didn't got any error message. Wallabag is up and running. Will try to made a more thorough test of Wallabag next days.

@sandrotavares
Copy link

Have the same issue on a DS918+ With MariaDB10 and PHPMyAdmin 4.6.6

@Sigawan
Copy link

Sigawan commented Feb 6, 2018

Installation of the wallabag package on the latest DSM 6.1.5 15254 fails with the same error as most other packages hosted at synocommunity 'incorrect mysql root password'

Is any work being done on this generic problem in the years since it was first reported?

@ymartin59 ymartin59 added the dsm 6 label Feb 9, 2018
@pbalthasar
Copy link

Same here (DS416play, DSM 6.1.5, PhpMyAdmin 4.6.6, MariaDB10, Wallabag 2.2.3-2).

@arakeis
Copy link
Contributor

arakeis commented May 7, 2018

try with this :
ln -s /volume1/@appstore/MariaDB10/usr/local/mariadb10/bin/mysql /usr/bin/mysql
and
ln -s /volume1/@appstore/MariaDB10/usr/local/mariadb10/bin/mysqldump /usr/bin/mysqldump

this should walk you a little further

@Sigawan
Copy link

Sigawan commented May 8, 2018

Switched to FreeNAS. Synology units ebay'd off.

@arakeis
Copy link
Contributor

arakeis commented May 29, 2018

found out wallabag is looking for a MySQL connection on 3306, but mariadb10 seemed set up with 3307 by default, anyone knows how to alter the preferences.yml file from wallabag once downloaded ?

@arakeis
Copy link
Contributor

arakeis commented May 30, 2018

with the correct path for mysql and mysqldump + the correct mysql (mariadb10) port set to 3307, my non working package, was able to fix it self. my setup is working !

@astacus27
Copy link

Hi arekeis, what steps did you take exactly to get wallabag working and in what order? Its still a bit unclear to me. Your help is much apreciated because you seem to have found workaround to get wallabag working.

@arakeis
Copy link
Contributor

arakeis commented Jun 8, 2018 via email

@astacus27
Copy link

astacus27 commented Jun 11, 2018 via email

@arakeis
Copy link
Contributor

arakeis commented Jul 2, 2018

Ok, to have it work on a setup with mariadb10 installed (with the 3307 port used)
you must add the previous links to your setup (ssh connection needed) :
ln -s /volume1/@appstore/MariaDB10/usr/local/mariadb10/bin/mysql /usr/bin/mysql
ln -s /volume1/@appstore/MariaDB10/usr/local/mariadb10/bin/mysqldump /usr/bin/mysqldump
(while installing) change the mysql port from two files :
sudo vi /var/services/web/wallabag/app/config/parameters.yml
change : database_port: 3306 => database_port: 3307
sudo vi /volume1/@appstore/wallabag/share/wallabag/app/config/parameters.yml
change : database_port: 3306 => database_port: 3307

I know that the "while installing" is quiet imprecise but that the imperfect way I got it working

@zyphlar
Copy link

zyphlar commented Aug 24, 2018

It would be super cute if the package could be updated with @arakeis 's strings. I've been trying to hack things together like this for days and MySQL straight-up doesn't seem available for the newest DSM so any SynoCommunity MySQL stuff is probably useless on those platforms. Seems like a straightforward fix, but due to code signing we can't do it ourselves (and most people aren't gonna hunt around on their NAS via SSH.)

@lotth
Copy link

lotth commented May 14, 2019

Synology just released a new MariaDB10 version 10.3.11-0054. It now allows changing the default port in the MariaDB10 application. I did not test yet reverting to port 3306 to install Wallabag, but it should help.

@lotth
Copy link

lotth commented May 14, 2019

Well, now database connection seems good but installer fails. From /var/services/web/wallabag/install.log it appears curl_exec and curl_multi_init are missing. Curl extension is activated in Webstation default PHP parameters.

@emo1509
Copy link

emo1509 commented Jul 14, 2019

Ok, to have it work on a setup with mariadb10 installed (with the 3307 port used)
you must add the previous links to your setup (ssh connection needed) :
ln -s /volume1/@appstore/MariaDB10/usr/local/mariadb10/bin/mysql /usr/bin/mysql
ln -s /volume1/@appstore/MariaDB10/usr/local/mariadb10/bin/mysqldump /usr/bin/mysqldump
(while installing) change the mysql port from two files :
sudo vi /var/services/web/wallabag/app/config/parameters.yml
change : database_port: 3306 => database_port: 3307
sudo vi /volume1/@appstore/wallabag/share/wallabag/app/config/parameters.yml
change : database_port: 3306 => database_port: 3307

I know that the "while installing" is quiet imprecise but that the imperfect way I got it working

I followed this advice, and after installation continues with following error -->

Cannot install 'wallabag'
unable to migrate database schema. Please check the log -->
/var/services/web/wallabag/migration.log

In the log I find -->

Migrating up to 20170127093841 from 0

++ migrating 20160410190541

Migration 20160410190541 failed during Execution. Error There is no table with name 'wallabag.wallabag_entry' in the schema.

[Doctrine\DBAL\Schema\SchemaException (10)]
There is no table with name 'wallabag.wallabag_entry' in the schema.

Exception trace:
() at /volume1/web/wallabag/vendor/doctrine/dbal/lib/Doctrine/DBAL/Schema/SchemaException.php:43
Doctrine\DBAL\Schema\SchemaException::tableDoesNotExist() at /volume1/web/wallabag/vendor/doctrine/dbal/lib/Doctrine/DBAL/Schema/Schema.php:197
Doctrine\DBAL\Schema\Schema->getTable() at /volume1/web/wallabag/vendor/ocramius/proxy-manager/src/ProxyManager/GeneratorStrategy/EvaluatingGeneratorStrategy.php(65) : eval()'d code:62
ProxyManagerGeneratedProxy_PM_\Doctrine\DBAL\Schema\Schema\Generated2e01a7af5663aaa6f05dbe19bed007fa->getTable() at /volume1/web/wallabag/vendor/ocramius/proxy-manager/src/ProxyManager/GeneratorStrategy/Eval
uatingGeneratorStrategy.php(65) : eval()'d code:62
ProxyManagerGeneratedProxy_PM_\Doctrine\DBAL\Schema\Schema\Generated2e01a7af5663aaa6f05dbe19bed007fa->getTable() at /volume1/web/wallabag/app/DoctrineMigrations/Version20160410190541.php:35
Application\Migrations\Version20160410190541->up() at /volume1/web/wallabag/vendor/doctrine/migrations/lib/Doctrine/DBAL/Migrations/Version.php:290
Doctrine\DBAL\Migrations\Version->execute() at /volume1/web/wallabag/vendor/doctrine/migrations/lib/Doctrine/DBAL/Migrations/Migration.php:183
Doctrine\DBAL\Migrations\Migration->migrate() at /volume1/web/wallabag/vendor/doctrine/migrations/lib/Doctrine/DBAL/Migrations/Tools/Console/Command/MigrateCommand.php:142
Doctrine\DBAL\Migrations\Tools\Console\Command\MigrateCommand->execute() at /volume1/web/wallabag/vendor/doctrine/doctrine-migrations-bundle/Command/MigrationsMigrateDoctrineCommand.php:55
Doctrine\Bundle\MigrationsBundle\Command\MigrationsMigrateDoctrineCommand->execute() at /volume1/web/wallabag/vendor/symfony/symfony/src/Symfony/Component/Console/Command/Command.php:264
Symfony\Component\Console\Command\Command->run() at /volume1/web/wallabag/vendor/symfony/symfony/src/Symfony/Component/Console/Application.php:853
Symfony\Component\Console\Application->doRunCommand() at /volume1/web/wallabag/vendor/symfony/symfony/src/Symfony/Component/Console/Application.php:200
Symfony\Component\Console\Application->doRun() at /volume1/web/wallabag/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Console/Application.php:80
Symfony\Bundle\FrameworkBundle\Console\Application->doRun() at /volume1/web/wallabag/vendor/symfony/symfony/src/Symfony/Component/Console/Application.php:124
Symfony\Component\Console\Application->run() at /volume1/web/wallabag/bin/console:29

@lxne
Copy link

lxne commented Nov 3, 2019

Well, now database connection seems good but installer fails. From /var/services/web/wallabag/install.log it appears curl_exec and curl_multi_init are missing. Curl extension is activated in Webstation default PHP parameters.

Same problem with MariaDB10 and port set to 3306.

@knapovsky
Copy link

I tried to solve this issue, but there's no success. I'm just going to use docker. My problem is that I cannot uninstall the synology wallabag package. It always gives me 'Incorrect root MySQL password'. Is there a way how to forcefully remove a Synology package?

@GitJamz
Copy link

GitJamz commented Jan 6, 2020

omg what a disaster..
I have latets package of mariaDB 10 and phpmyadmin as well on my synology. And Also get wrong root password with the current wallabag package.
Difference is that I came from docker and that did not work well either.. The official wallabag container runs very bad on a synology.. Unable to fetch most articles and also the container has to run as root.

@Framstag
Copy link

I'm also interested in using Wallabag and get the same error regarding root password. Is anybody actively working on package fixes or am I on my own? It looks like the problem is not a principle problem, but "just" bad adjustment of all the required packages?

@andrewchenshx
Copy link

DS218, DSM 6.2.2-24922 Update 4
same error.

@jshum
Copy link

jshum commented Jul 18, 2020

I've followed the instructions above and I think I got farther than everybody by a bit. But now it's throwing an exception for not being able to finish the migration, because the driver could not be found

(installed mariadb10, phpmyadmin, php56)

  • firstly, it required me to install php56 even though I had php72 installed previously. otherwise, it would say it can't find php56
  • used ln -s to link to mariadb executables
  • changed the port to 3307 while installation is happening
  • but it is now unable to run the migration as it is throwing an exception from PDO it cannot find the driver
  • I think this is due to the fact that php56 doesn't come with the php-mysql driver?
  • I couldn't find a way to force it to use php72. If anyone has thoughts, would really appreciate it?

@publicarray
Copy link
Member

publicarray commented Sep 15, 2020

Hi everyone, I know it's been a long time. If you are still interested in Wallabag and would like to test the latest build It's over here:
#4179. This fixes the existing problems mentioned here.

Please leave any feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests