I am going to upload a fix to the clearly identified problem
of having the same user with overwritten auto-generated
password by dbconfig. (see previous pending tag).
There was another issue described here, that i believe was
that the adapter line in (at least one of) the
On Wed, 16 Jan 2013, Jérémy Lal wrote:
But i can't see how you can end without any database type set...
The more funny thing is that I don’t get asked to select
one, or asked whether I want to reinstall the DB, at all.
Maybe I should purge dbconfig* too… and remove all entries
related to that
On 17/01/2013 09:33, Thorsten Glaser wrote:
On Wed, 16 Jan 2013, Jérémy Lal wrote:
But i can't see how you can end without any database type set...
The more funny thing is that I don’t get asked to select
one, or asked whether I want to reinstall the DB, at all.
Maybe I should purge
Dixi quod…
Maybe I should purge dbconfig* too… and remove all entries
related to that from debconf…
Oh. Now I can’t even purge redmine any more:
[…] Deconfigure database for redmine/instances/default with dbconfig-common?
⇒ Yes
dpkg: error processing redmine (--purge):
On 17/01/2013 10:02, Thorsten Glaser wrote:
rake aborted!
Please install the pgsql adapter: `gem install activerecord-pgsql-adapter`
(cannot load such file -- active_record/connection_adapters/pgsql_adapter)
.../...
So, even after a full purge of redmine, redmine-pgsql and
On 17/01/2013 10:02, Thorsten Glaser wrote:
rake aborted!
Please install the pgsql adapter: `gem install activerecord-pgsql-adapter`
(cannot load such file -- active_record/connection_adapters/pgsql_adapter)
.../...
So, even after a full purge of redmine, redmine-pgsql and
On 17/01/2013 10:02, Thorsten Glaser wrote:
Please install the pgsql adapter: `gem install activerecord-pgsql-adapter`
(cannot load such file -- active_record/connection_adapters/pgsql_adapter)
about that original problem :
could you check the value of adapter in your
On Fri, 11 Jan 2013, Jérémy Lal wrote:
* dpkg-reconfigure -plow redmine
and ask for reinstallation of the database.
root@redmine:~ # dpkg-reconfigure -plow redmine
/usr/sbin/dpkg-reconfigure: redmine is broken or not fully installed
Setting the status to installed doesn’t help either,
so I
On 16/01/2013 13:06, Thorsten Glaser wrote:
On Fri, 11 Jan 2013, Jérémy Lal wrote:
* dpkg-reconfigure -plow redmine
and ask for reinstallation of the database.
root@redmine:~ # dpkg-reconfigure -plow redmine
/usr/sbin/dpkg-reconfigure: redmine is broken or not fully installed
Setting
On Wed, 16 Jan 2013, Jérémy Lal wrote:
Did you change manually /etc/redmine/default/database.yml,
No.
and could you give the output of `debconf-show redmine` ?
root@redmine:~ # debconf-show redmine
* redmine/instances/default/default-language: en
redmine/notify-migration:
There are problems i can reproduce easily when doing :
* purge instances databases
* reconfigure, set instance default, do not install db
* reconfigure, keep instance default, install db
- a succession of warnings from dbconfig, eventually installs
db.
or doing
* reconfigure database using a
On Sun, 16 Dec 2012, Jérémy Lal wrote:
I am working on a fix.
Any news?
In the meantime, I tried to recover myself: look into
/etc/redmine/default/database.yml what was used as
password, connect as postgres to the DB and ALTER ROLE
and set the redmine user’s password to that.
Doesn’t work ☹
On 11/01/2013 17:12, Thorsten Glaser wrote:
On Sun, 16 Dec 2012, Jérémy Lal wrote:
I am working on a fix.
Any news?
I'll try to make config script use the first generated
password if a second database user name is the same as a first
one. But i'm not sure i can even read the first
Hi again,
this is even funnier. On the machine, I have:
# fgrep Value: /var/cache/debconf/passwords.dat
Value:
Value:
Value:
Value:
Value:
So apparently, it lost *all* password information.
# ls -l /etc/redmine/
On Sun, 16 Dec 2012, Jérémy Lal wrote:
The bug comes from configuring two instances with the same db user.
dbconfig-common regenerates a random password when configuring
the second instance, wiping the password set for the first instance
that has already been recorded in database.yml.
Okay,
On 17/12/2012 11:02, Thorsten Glaser wrote:
On Sun, 16 Dec 2012, Jérémy Lal wrote:
The bug comes from configuring two instances with the same db user.
dbconfig-common regenerates a random password when configuring
the second instance, wiping the password set for the first instance
that has
On Mon, 17 Dec 2012, Jérémy Lal wrote:
naively installing two databases with same user should not
screw up the password assigned the first time.
Hmh. I don’t have a second instance, so I don’t even know
the right password ☺ I could probably reset it using psql
though.
It might be considered
The bug comes from configuring two instances with the same db user.
dbconfig-common regenerates a random password when configuring
the second instance, wiping the password set for the first instance
that has already been recorded in database.yml.
Workaround : get the password of the second
On Wed, 12 Dec 2012, Jérémy Lal wrote:
Is there a chance you had config files from an earlier redmine
installation ?
None whatsoever. Let me summarise what I did so far:
I set up a fresh Debian wheezy VM on 29 November,
installed postgresql, redmine, apache2, read through
the Engrish
On 13/12/2012 10:16, Thorsten Glaser wrote:
On Wed, 12 Dec 2012, Jérémy Lal wrote:
Is there a chance you had config files from an earlier redmine
installation ?
None whatsoever. Let me summarise what I did so far:
I set up a fresh Debian wheezy VM on 29 November,
installed postgresql,
On 13/12/2012 10:16, Thorsten Glaser wrote:
On Wed, 12 Dec 2012, Jérémy Lal wrote:
Is there a chance you had config files from an earlier redmine
installation ?
None whatsoever. Let me summarise what I did so far:
I set up a fresh Debian wheezy VM on 29 November,
installed postgresql,
Package: redmine
Version: 1.4.4+dfsg1-1.1
Severity: serious
Justification: Policy 4.2
Today’s dist-upgrade inside wheezy failed. Retrying yields:
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space
I don't reproduce.
Could you check you don't have :
1) incompatible gems (gem list)
2) incompatible redmine plugins (ls /usr/share/redmine/vendor/plugins)
3) custom installed rails (ls -l /usr/share/redmine/vendor/rails)
thank you
Jérémy.
On 12/12/2012 17:24, Thorsten Glaser wrote:
Package:
Jérémy Lal dixit:
I don't reproduce.
Hum. I just installed the packages and not much else (this is a
pretty fresh system used to evaluate redmine).
Could you check you don't have :
1) incompatible gems (gem list)
root@redmine:~ # gem list
*** LOCAL GEMS ***
2) incompatible redmine plugins
Is there a chance you had config files from an earlier redmine
installation ? Do yours have
adapter: postgresql
?
Jérémy.
On 12/12/2012 19:20, Thorsten Glaser wrote:
Jérémy Lal dixit:
I don't reproduce.
Hum. I just installed the packages and not much else (this is a
pretty fresh system
25 matches
Mail list logo
