FIND it! <div><br></div><div>dpkg-reconfigure -plow --force redmine</div><div><br></div><div>follow verbose steps, now in config dialos u can see that in usernames said "Mysql" and its using pgsql backend.. this was minor mistake.. so change db name redmine_default to redmine (by removing lIinstance var) in postinst script (lines: 175 aprox)</div>
<div><br></div><div>this its due in postgresql by default when user connect assumes a equal db name exist for users , so postinst scritp when connect user redmine this cant due redmine database dont exist, event redmine_default (in default instace case) its the db to use.. </div>
<div><br></div><div>the right solution its to modifi conection from dbconfig common to use a specific database name in conection processs.<br><br><div class="gmail_quote">On Wed, Aug 8, 2012 at 1:28 PM, PICCORO McKAY Lenz <span dir="ltr"><<a href="mailto:mckaygerhard@gmail.com" target="_blank">mckaygerhard@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>now i will test postgresql backen (i not tested due some space need)</div><div>for that i run "dpkg-reconfigure -plow redmine" and respont all quiestion using postgres wihtout none security and xxx user with xxx password, testin connection results ok event by localhost or socket, so its clear that problem are betweet redmine or debian's dbconfig script due fails populating db but not previously conections</div>
</div><div><br></div><div>I could, I managed to reproduce the error with sqlite backend, the only difference between before and after, its that ruby 1.9.1 devel package were instaled. Let me explain:</div><div><br></div>
<div>
1) I installed redmine all depends in clean env, but using sqlite backend (that installed before perectly) and event fails, even I did not realize that bundler had installed so then ruby 1.9.1 also, (bundler now depends of), but i had installed with devel ruby1.9.1-dev also.</div>
<div><br></div><div>2) so then i revise all changelog and bug reports and notice some issues about gems and rack, so additional depends installed in a repackaging of rails 2.3.14 result that must be : ruby-rack> = 1.4 and rubygems> = 1.8 explicitly, as it still had the rubygems 1.6 from unstable, this fixes the first problem reported, but i put previosly in redmine file config/boot.rb a "require 'thread'" line after RAILS_ROOT related, this are mandatory i tested without and in some cases faild redmine to install.</div>
<div><br></div><div>3) after notice had installed ruby bundler so then ruby 1.9.1, then uninstall all ruby 1.9.1 (so i must uninstall bundler), removing ruby1.9.1-dev solved the problem and install redmine perfect with sqlite or mysql backend if all of those topics are exactly as i said. There's something whit db:migrating that relies on ruby 1.9 ...</div>
<div><br></div><div>4) then removes and purge all redmine, so repeat install ruby1.9.1-dev and redmine and installs fine</div><div>5) then removes and reinstall but first with bundler installed failds.</div><div>6) some try after, i cant reproduce this case...</div>
<div><br></div><div>So then if in upgrade redmine from squeeze to wheeze ruby 1.9.1 are installed, upgrades will fail!!!! this bug its very famous in debian over net, seee google search related ...</div><div><br></div><div>
with postgres: when i reconfigure, i setup postgres to ask in every conection the password (and dbconfig has stored also) result that:</div><div><br></div><div><div><div>Creating config file /etc/redmine/default/database.yml.new with new version</div>
<div>Password for user postgres: </div><div>creating postgres user redmine: Password for user postgres: </div><div>already exists.</div><div>resetting password: Password for user postgres: </div><div>success.</div><div>
Password for user postgres: </div><div>creating database redmine_default: Password for user postgres: </div><div>already exists.</div><div>dbconfig-common: flushing administrative password</div><div>Populating database for redmine instance "default".</div>
<div>This may take a while.</div><div>NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01.</div><div>Gem.source_index called from /usr/share/redmine/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21.</div>
<div>Please install RDoc 2.4.2+ to generate documentation.</div><div>rake aborted!</div><div>server closed the connection unexpectedly</div><div><span style="white-space:pre-wrap"> </span>This probably means the server terminated abnormally</div>
<div><span style="white-space:pre-wrap"> </span>before or while processing the request.</div><div><br></div><div>Tasks: TOP => db:migrate => environment</div><div>(See full trace by running task with --trace)</div>
<div>Error when running rake db:migrate, check database configuration.</div><div>exit: 295: Illegal number: -1</div></div></div><span class="HOEnZb"><font color="#888888"><div><br></div><div><br></div><div><br></div>-- <br>
<font color="#888888">Lenz McKAY Gerardo (PICCORO)</font><div>
<font color="#888888"><a href="http://qglochekone.blogspot.com" target="_blank">http://qglochekone.blogspot.com</a></font></div><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><font color="#888888">Lenz McKAY Gerardo (PICCORO)</font><div><font color="#888888"><a href="http://qglochekone.blogspot.com" target="_blank">http://qglochekone.blogspot.com</a></font></div>
<br>
</div>