Project

General

Profile

Actions

Defect #5903

closed

There is no "admin" account when fresh install

Added by Sin-young Kang over 14 years ago. Updated over 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-07-18
Due date:
% Done:

0%

Estimated time:
Resolution:
Invalid
Affected version:

Description

I tried fresh install into my VM guest (Ubuntu 10.04), and I cannot login as default administrator account named "admin".

I checked my db after initialized at 1st time, no admin account created.
there is just only "Anonymous" account exist.

Here is my environment
  • Ruby 1.8.7
  • Rails 2.3.5
  • PostgreSQL 8.4.4
Actions #1

Updated by Sin-young Kang over 14 years ago

ah, I missed Redmine version.

It is just fresh 1.0.0 RC, r3858.

Actions #2

Updated by Felix Schäfer over 14 years ago

Have you run RAILS_ENV=production rake redmine:load_default_data?

Actions #3

Updated by Sin-young Kang over 14 years ago

Felix Schäfer wrote:

Have you run RAILS_ENV=production rake redmine:load_default_data?

Sure. I tried clean install almost 10 times.
Currently I'm on working so I'll try again after work.

And it looks also 0.9-stable affecting, I'll test it too.

Actions #4

Updated by Felix Schäfer over 14 years ago

The admin account is created in the migrations, sorry, in fact it's created in the first migration here source:/trunk/db/migrate/001_setup.rb#L288 . Could you try a fresh install on SQLite to see if the problem persists? Do you also have gems installed from apt? There are known problems with gems installed both from apt and manually colliding.

Actions #5

Updated by Sin-young Kang over 14 years ago

Felix Schäfer wrote:

The admin account is created in the migrations, sorry, in fact it's created in the first migration here source:/trunk/db/migrate/001_setup.rb#L288 . Could you try a fresh install on SQLite to see if the problem persists? Do you also have gems installed from apt? There are known problems with gems installed both from apt and manually colliding.

There is no problem, sorry about wrong error.

In my fault, I used rake db:reset instead rake db:migrate,
schema dump doesn't has custom insert syntaxes.

I dropped my postgresql database again, and now good with rake db:migrate.

Actions #6

Updated by Felix Schäfer over 14 years ago

  • Status changed from New to Closed
  • Resolution set to Invalid

No harm done :-)

Actions

Also available in: Atom PDF