Session reset after each page request, idle_timeout set to zero
Multiple reports on Ubuntu 14.04 that on a clean installation, web UI sessions are reset after every single request.
This appears to be caused by an idle_timeout set to zero.
As a workaround, go to Administer > Settings > General and set idle_timeout to 60 or similar.
#5 Updated by Dmitri Dolguikh over 6 years ago
- Status changed from Assigned to Need more information
Can't reproduce based on currently available information. Would be useful to know:
- if the installer was used (if not, how install was performed)
- what installer options were used
- maybe even step-by-step description of the install?
#8 Updated by Matt Darcy over 6 years ago
This issue is not related to just ubuntu 14.04.
I hit this problem with CentOS 6.4 x86_64 using Foreman 1.6.2
I installed Centos 6.5 minimal install.
Added the SCL/EPEL/Puppetlabs/Foreman repos and updated my yum metadata.
I installed dhcp-server, tftp-server, puppet-server and foreman-installer (with associated dependency packages)
I used the following foreman installation line.
--enable-foreman-compute-libvirt --foreman-db-host localhost --foreman-proxy-dhcp-interface eth1 --foreman-db-type mysql
the installer appeared to complete without error (the error log confirms this)
but the timeout parameter was set to 0. Setting this to a higher number resolved the issue.
#10 Updated by Nate Walck over 6 years ago
I just did a fresh spinup using the puppet-foreman module and ran into this issue.
OS: 14.04 LTS
I included the module and set the one time admin_password var, otherwise no modifications.
idle timeout defaulted to 0 seconds, changing it to 3600 prevented the instant page timeouts.
#12 Updated by Dominic Cleal over 6 years ago
I just hit the same issue with Ubuntu 14.04 in 1.8 nightlies. The installation took a very long time, but I suspect that's related to API locale changes (https://github.com/theforeman/foreman/commit/a59972c3).
root@foremandeb:~# sudo -H -u foreman /usr/share/foreman/script/foreman-config
foreman-config script is deprecated. Please consider using `foreman-rake config` instead
[deprecated] I18n.enforce_available_locales will default to true in the future. If you really want to skip validation of your locale you can set I18n.enforce_available_locales = false to avoid this message.
Workaround for RbVmomi may not work as ComputeResource is already loaded: ComputeResource
bootdisk_generic_host_template: Boot disk iPXE - generic host
bootdisk_host_template: Boot disk iPXE - host
Note that all integer settings are zero. The installation was simply with
foreman-installer --foreman-admin-password=XXX, default settings otherwise, including PostgreSQL.
I did try accessing the login page towards the end of the installation while it was still installing either bootdisk or foreman_setup.
#14 Updated by Tomer Paz over 6 years ago
happened to me too, consistently running on docker, Foreman 1.6.3
Can't change the idle_timeout from GUI since egg/chicken scenario - can't login, 'session expires' (tried on FF and Chrome).
What's the CLI so I can change the idle_timeout from 0?
the only other option for me is to trace down this field in the PostgreSQL DB and alter it manually