Your message dated Wed, 22 Nov 2017 16:36:43 +0900
with message-id <7eb4939644492a62f9d65c29e14ca...@duckcorp.org>
and subject line Re: redmine: fails to install with remote MySQL server
has caused the Debian Bug report #570179,
regarding redmine: fails to install with remote MySQL server
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
570179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: redmine
Version: 0.9.1-1~bpo50+1
Severity: minor
Hi again,
I am having trouble installing redmine with a remote mysql server. This is a
common
problem with dbconfig-common enabled applications, although I think this
problem is
specific to redmine.
First, i can't fill in the hostname of the remote SQL server or the admin user
during
the initial install. So the only way to get to those prompts is to answer "no"
to the
"dbconfig-common" prompt so it doesn't try to configure the database during the
install and then run dpkg-reconfigure redmine to configure the database.
After answering the prompts in dpkg-reconfigure, I get the following error:
mysql said: ERROR 1133 (42000) at line 1: Can't find any matching row in the
user table
... which is odd, as it's not a permission denied error, it's as if the process
of
initialising the databse user was broken in some way.
When I retry to configure the database, I get prompted for some stuff again and
then it
somehow bypasses that error and tries to setup the database:
dbconfig-common: flushing administrative password
Creating config file /etc/redmine/default/database.yml with new version
Populating database for redmine instance "default".
This may take a while.
rake aborted!
Access denied for user 'redmine'@'192.168.0.117' (using password: YES)
(See full trace by running task with --trace)
Done.
rake aborted!
Access denied for user 'redmine'@'192.168.0.117' (using password: YES)
(See full trace by running task with --trace)
rake aborted!
Access denied for user 'redmine'@'192.168.0.117' (using password: YES)
(See full trace by running task with --trace)
So indeed, it seems like the database user wasn't created properly.
I don't see in the postinst where that task is performed so i can only assume
the
problem lies in dbconfig-common, but I didn't have this kind of problems in
other
applications that I can recall...
Thanks for your attention,
A.
-- System Information:
Debian Release: 5.0.4
APT prefers stable
APT policy: (500, 'stable'), (2, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.18-5-vserver-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages redmine depends on:
ii dbconfig-common 1.8.39 common framework for packaging dat
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii libjs-prototype 1.6.1-1~bpo50+1 JavaScript Framework for dynamic w
ii libjs-scriptaculous 1.8.3-1~bpo50+1 JavaScript library for dynamic web
ii rails 2.2.3-1~bpo50+1 MVC ruby based framework geared fo
ii rake 0.8.7-1~bpo50+1 a ruby build program
ii redmine-mysql 0.9.1-1~bpo50+1 metapackage providing MySQL depend
ii ruby 4.2 An interpreter of object-oriented
ii ruby1.8 1.8.7.72-3lenny1 Interpreter of object-oriented scr
Versions of packages redmine recommends:
pn libapache2-mod-fcgid <none> (no description available)
ii libfcgi-ruby1.8 [libfcgi-ruby 0.8.7-4.1 FastCGI library for Ruby
Versions of packages redmine suggests:
ii apache2-mpm-worker [http 2.2.9-10+lenny6 Apache HTTP Server - high speed th
ii libopenid-ruby 2.1.2debian-1 Ruby library for verifying and ser
pn librmagick-ruby <none> (no description available)
pn libsvn-ruby <none> (no description available)
-- debconf information:
* redmine/instances/default/db/app-user: redmine
redmine/instances/default/passwords-do-not-match:
* redmine/instances/default/default-language: fr
* redmine/instances/default/remote/newhost: mysql.koumbit.net
redmine/instances/default/db/basepath:
redmine/notify-migration:
redmine/old-instances:
redmine/instances/default/upgrade-error: abort
redmine/instances/default/pgsql/changeconf: false
redmine/instances/default/missing-db-package-error: abort
* redmine/instances/default/db/dbname: redmine_default
redmine/instances/default/purge: false
* redmine/current-instances: default
* redmine/instances/default/remote/host: mysql.koumbit.net
redmine/default-language: ${defaultLocale}
redmine/instances/default/pgsql/no-empty-passwords:
redmine/instances/default/dbconfig-upgrade: true
redmine/instances/default/internal/reconfiguring: false
redmine/instances/default/upgrade-backup: true
redmine/instances/default/pgsql/method: unix socket
redmine/instances/default/install-error: retry
* redmine/instances/default/mysql/admin-user: sysusr
redmine/instances/default/database-type: mysql
redmine/instances/default/pgsql/manualconf:
redmine/instances/default/pgsql/authmethod-admin: ident
* redmine/instances/default/mysql/method: tcp/ip
redmine/instances/default/internal/skip-preseed: false
redmine/instances/default/pgsql/admin-user: postgres
redmine/instances/default/remove-error: abort
redmine/instances/default/dbconfig-remove:
* redmine/instances/default/remote/port:
redmine/instances/default/pgsql/authmethod-user:
* redmine/instances/default/dbconfig-install: true
redmine/instances/default/dbconfig-reinstall: false
--- End Message ---
--- Begin Message ---
Version: 3.4.2-1
Quack,
So these remaining errors have been fixed (when asking for a manual
installation).
As for having access to the questions for remote installation,
dbconfig-common hides less common questions by default. You can ask to
have all questions using:
DEBIAN_PRIORITY=low apt-get install redmine-mysql
Since this is a slightly more advanced configuration, I don't think
diverging from the default is necessary.
Thanks for reporting this problem.
\_o<
--
Marc Dequènes
--- End Message ---