After foreman-1.1stable-3.el5 install, http://ip:3000 can't login use admin/changeme

os: centos 5.8 x86_64
install rpm soft:
rubygem-foremancli-1.0-1.el5
foreman-proxy-1.1stable-1.el5
foreman-mysql-1.1stable-3.el5
foreman-release-1.1stable-3.el5
foreman-console-1.1stable-3.el5
foreman-sqlite-1.1stable-3.el5
foreman-cli-1.1stable-3.el5
foreman-libvirt-1.1stable-3.el5
foreman-installer-1.1.2-1
foreman-ec2-1.1stable-3.el5
foreman-1.1stable-3.el5
foreman-ovirt-1.1stable-3.el5

cd /usr/share/foreman/ && RAILS_ENV=production rake db:migrate

Creat mysql account for foreman

edit /etc/foreman/settings.yaml & /etc/foreman/database.yml

/etc/foreman/settings.yaml
:unattended: true
:login: true
:require_ssl: false
:locations_enabled: false
:organizations_enabled: false
:support_jsonp: false
:puppetconfdir: /etc/puppet
:puppetvardir: /var/lib/puppet

/etc/foreman/database.yml
development:
adapter: sqlite3
database: db/development.sqlite3
pool: 5
timeout: 5000
production:
adapter: mysql
host: localhost
database: foreman
username: xxxx
password: xxxxxx

/etc/init.d/foreman restart
/etc/init.d/foreman-proxy restart
/etc/init.d/puppetmaster restart
access http://ip:3000 ,use admin/changeme can't login

tail /var/log/production.log
Started POST "/users/login" for x.x.x.x at Tue Dec 09 15:11:06 +0800 2014
Processing by UsersController#login as HTML
Parameters: {"commit"=>"Login ?",
"authenticity_token"=>"PNjfoGXOQh2EY8UrNgN6KiscDzhAmL/1wrcHc/bcpUs=",
"login"=>{"login"=>"admin", "password"=>"[FILTERED]"}, "utf8"=>"?"}
invalid user
Redirected to http://x.x.x.x:3000/users/login
Completed 302 Found in 21ms

Started GET "/users/login" for 10.200.39.110 at Tue Dec 09 15:11:06 +0800
2014
Processing by UsersController#login as HTML
Rendered home/_topbar.rhtml (5.2ms)
Rendered users/login.html.erb within layouts/application (14.9ms)
Completed 200 OK in 17ms (Views: 15.9ms | ActiveRecord: 0.3ms)

end

First off, I must point out that Foreman 1.1 is a very, very old
release. Beyond this reply, you're probably not going to get any
support for running it - you're on your own.

We stopped building RPMs for EL5 after 1.1 for various reasons, and I'd
strongly recommend using EL7 or EL6 which have Foreman 1.7.

Not only are you missing out on any kind of help we can give you, you're
missing a huge number of bug fixes, support for all recent Puppet
versions, you're vulnerable to numerous security issues and are of
course, missing lots of cool features.

Please follow Foreman :: Quickstart

As for your issue, you might be able to reset the password by running:

cd ~foreman && RAILS_ENV=production bundle exec rake permissions:reset

(Note to anybody finding this thread - that's only suitable for this old
1.1 installation.)

··· -- Dominic Cleal Red Hat Engineering

On 09/12/14 07:33, zlifate@gmail.com wrote:

os: centos 5.8 x86_64
install rpm soft:
rubygem-foremancli-1.0-1.el5
foreman-proxy-1.1stable-1.el5
foreman-mysql-1.1stable-3.el5
foreman-release-1.1stable-3.el5
foreman-console-1.1stable-3.el5
foreman-sqlite-1.1stable-3.el5
foreman-cli-1.1stable-3.el5
foreman-libvirt-1.1stable-3.el5
foreman-installer-1.1.2-1
foreman-ec2-1.1stable-3.el5
foreman-1.1stable-3.el5
foreman-ovirt-1.1stable-3.el5

cd /usr/share/foreman/ && RAILS_ENV=production rake db:migrate

Creat mysql account for foreman

edit /etc/foreman/settings.yaml & /etc/foreman/database.yml

/etc/foreman/settings.yaml
:unattended: true
:login: true
:require_ssl: false
:locations_enabled: false
:organizations_enabled: false
:support_jsonp: false
:puppetconfdir: /etc/puppet
:puppetvardir: /var/lib/puppet

/etc/foreman/database.yml
development:
adapter: sqlite3
database: db/development.sqlite3
pool: 5
timeout: 5000
production:
adapter: mysql
host: localhost
database: foreman
username: xxxx
password: xxxxxx

/etc/init.d/foreman restart
/etc/init.d/foreman-proxy restart
/etc/init.d/puppetmaster restart
access http://ip:3000 ,use admin/changeme can’t login

tail /var/log/production.log
Started POST “/users/login” for x.x.x.x at Tue Dec 09 15:11:06 +0800 2014
Processing by UsersController#login as HTML
Parameters: {“commit”=>“Login ?”,
“authenticity_token”=>“PNjfoGXOQh2EY8UrNgN6KiscDzhAmL/1wrcHc/bcpUs=”,
“login”=>{“login”=>“admin”, “password”=>"[FILTERED]"}, “utf8”=>"?"}
invalid user
Redirected to http://x.x.x.x:3000/users/login
Completed 302 Found in 21ms

Started GET “/users/login” for 10.200.39.110 at Tue Dec 09 15:11:06
+0800 2014
Processing by UsersController#login as HTML
Rendered home/_topbar.rhtml (5.2ms)
Rendered users/login.html.erb within layouts/application (14.9ms)
Completed 200 OK in 17ms (Views: 15.9ms | ActiveRecord: 0.3ms)

end


You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com
mailto:foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
mailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Hello,

> os: centos 5.8 x86_64

CentOS 5 is not supported, use 6 or 7.

> Creat mysql account for foreman

I'd recommend PostgreSQL as there are performance issues with MySQL.

> access http://ip:3000 ,use admin/changeme can't login

You need to seed your database with a password with
'SEED_ADMIN_PASSWORD' option.

··· -- Later, Lukas #lzap Zapletal

hi
This is backup machine , centos 5.8 x86_64 and foreman 1.1 version can not
change,hey~~~~~

在 2014年12月9日星期二UTC+8下午9时49分39秒,Dominic Cleal写道:

··· > > First off, I must point out that Foreman 1.1 is a very, very old > release. Beyond this reply, you're probably not going to get any > support for running it - you're on your own. > > We stopped building RPMs for EL5 after 1.1 for various reasons, and I'd > strongly recommend using EL7 or EL6 which have Foreman 1.7. > > Not only are you missing out on any kind of help we can give you, you're > missing a huge number of bug fixes, support for all recent Puppet > versions, you're vulnerable to numerous security issues and are of > course, missing lots of cool features. > > Please follow http://theforeman.org/manuals/1.7/quickstart_guide.html > > > As for your issue, you might be able to reset the password by running: > > cd ~foreman && RAILS_ENV=production bundle exec rake permissions:reset > > (Note to anybody finding this thread - that's only suitable for this old > 1.1 installation.) > > -- > Dominic Cleal > Red Hat Engineering > > On 09/12/14 07:33, zli...@gmail.com wrote: > > os: centos 5.8 x86_64 > > install rpm soft: > > rubygem-foremancli-1.0-1.el5 > > foreman-proxy-1.1stable-1.el5 > > foreman-mysql-1.1stable-3.el5 > > foreman-release-1.1stable-3.el5 > > foreman-console-1.1stable-3.el5 > > foreman-sqlite-1.1stable-3.el5 > > foreman-cli-1.1stable-3.el5 > > foreman-libvirt-1.1stable-3.el5 > > foreman-installer-1.1.2-1 > > foreman-ec2-1.1stable-3.el5 > > foreman-1.1stable-3.el5 > > foreman-ovirt-1.1stable-3.el5 > > > > > > cd /usr/share/foreman/ && RAILS_ENV=production rake db:migrate > > > > > > Creat mysql account for foreman > > > > > > edit /etc/foreman/settings.yaml & /etc/foreman/database.yml > > > > /etc/foreman/settings.yaml > > :unattended: true > > :login: true > > :require_ssl: false > > :locations_enabled: false > > :organizations_enabled: false > > :support_jsonp: false > > :puppetconfdir: /etc/puppet > > :puppetvardir: /var/lib/puppet > > > > /etc/foreman/database.yml > > development: > > adapter: sqlite3 > > database: db/development.sqlite3 > > pool: 5 > > timeout: 5000 > > production: > > adapter: mysql > > host: localhost > > database: foreman > > username: xxxx > > password: xxxxxx > > > > > > /etc/init.d/foreman restart > > /etc/init.d/foreman-proxy restart > > /etc/init.d/puppetmaster restart > > access http://ip:3000 ,use admin/changeme can't login > > > > > > tail /var/log/production.log > > Started POST "/users/login" for x.x.x.x at Tue Dec 09 15:11:06 +0800 > 2014 > > Processing by UsersController#login as HTML > > Parameters: {"commit"=>"Login ?", > > "authenticity_token"=>"PNjfoGXOQh2EY8UrNgN6KiscDzhAmL/1wrcHc/bcpUs=", > > "login"=>{"login"=>"admin", "password"=>"[FILTERED]"}, "utf8"=>"?"} > > invalid user > > Redirected to http://x.x.x.x:3000/users/login > > Completed 302 Found in 21ms > > > > > > Started GET "/users/login" for 10.200.39.110 at Tue Dec 09 15:11:06 > > +0800 2014 > > Processing by UsersController#login as HTML > > Rendered home/_topbar.rhtml (5.2ms) > > Rendered users/login.html.erb within layouts/application (14.9ms) > > Completed 200 OK in 17ms (Views: 15.9ms | ActiveRecord: 0.3ms) > > > > > > end > > > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Foreman users" group. > > To unsubscribe from this group and stop receiving emails from it, send > > an email to foreman-user...@googlegroups.com > > <mailto:foreman-users+unsubscribe@googlegroups.com >. > > To post to this group, send email to forema...@googlegroups.com > > > <mailto:forema...@googlegroups.com >. > > Visit this group at http://groups.google.com/group/foreman-users. > > For more options, visit https://groups.google.com/d/optout. > >