Project

General

Profile

Actions

Support #8394

closed

Foreman doesn't load in dev

Added by Henrik Feldt over 9 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Triaged:
Fixed in Releases:
Found in Releases:

Description

Trying to get foreman to load in dev environment...

Each request takes a little less than a second to get, but after 49 seconds, it seems the POST times out and I'm greeted with 'Invalid Username of Password'.

I've followed the guide for setting up the dev env, running it on ruby 1.9.3 p550 on centos 6.5 x64 with postgresql after running the setup sets of the rakefile as detailed here http://theforeman.org/contribute.html

I'm after being able to assign public IPs (not elastic ones) in EC2/VPC env on AWS. But I failed at the development step here.


Files

Screen Shot 2014-11-13 at 16.21.11.png View Screen Shot 2014-11-13 at 16.21.11.png 384 KB starts loading slowly Henrik Feldt, 11/13/2014 10:23 AM
Screen Shot 2014-11-13 at 16.23.15.png View Screen Shot 2014-11-13 at 16.23.15.png 161 KB doesn't have time to finish loading all assets Henrik Feldt, 11/13/2014 10:23 AM
Screen Shot 2014-11-13 at 16.24.17.png View Screen Shot 2014-11-13 at 16.24.17.png 16.5 KB resulting error msg Henrik Feldt, 11/13/2014 10:24 AM
development.log development.log 993 KB Henrik Feldt, 11/13/2014 10:31 AM
Actions #1

Updated by Ohad Levy over 9 years ago

can you please provide log output? (logs/development.log)

Actions #2

Updated by Ohad Levy over 9 years ago

  • Tracker changed from Bug to Support
  • Priority changed from High to Normal
Actions #3

Updated by Henrik Feldt over 9 years ago

Yup

Actions #4

Updated by Dominic Cleal over 9 years ago

  • Status changed from New to Feedback

Try running rake db:seed to populate the initial admin user. It will print out a username and password.

Actions #5

Updated by Henrik Feldt over 9 years ago

This is its output:

```
[vagrant@foreman vagrant]$ rake db:seed
The Apipie cache is turned off. Enable it and run apipie:cache rake task to speed up API calls.
Workaround for RbVmomi may not work as ComputeResource is already loaded: ComputeResource
Seeding /vagrant/db/seeds.d/03-auth_sources.rb
Seeding /vagrant/db/seeds.d/03-permissions.rb
Seeding /vagrant/db/seeds.d/03-roles.rb
Seeding /vagrant/db/seeds.d/04-admin.rb
Seeding /vagrant/db/seeds.d/05-taxonomies.rb
Seeding /vagrant/db/seeds.d/06-architectures.rb
Seeding /vagrant/db/seeds.d/07-config_templates.rb
Seeding /vagrant/db/seeds.d/08-partition_tables.rb
Seeding /vagrant/db/seeds.d/10-installation_media.rb
Seeding /vagrant/db/seeds.d/11-smart_proxy_features.rb
Seeding /vagrant/db/seeds.d/13-compute_profiles.rb
Seeding /vagrant/db/seeds.d/15-bookmarks.rb
Seeding /vagrant/db/seeds.d/16-mail_notifications.rb
All seed files executed
```

Actions #6

Updated by Dominic Cleal over 9 years ago

It's probably already been run then. Run rake permissions:reset to reset the password, then try logging in with that.

Actions #7

Updated by Henrik Feldt over 9 years ago

Same error

Actions #8

Updated by Anonymous about 7 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF