View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001047||bareos-core||[All Projects] webui||public||2019-02-06 20:40||2019-02-14 17:00|
|Target Version||Fixed in Version|
|Summary||0001047: Webui login returns a blank page when logging in.|
|Description||Sometimes when logging into Webui or attempting to log in with a different users, I am getting a blank page. The following errors appear in the httpd error log when this occurs.|
[Wed Feb 06 13:28:14.347786 2019] [:error] [pid 3627] [client x.x.x.x:63602] PHP Notice: Undefined variable: form in /usr/share/bareos-webui/module/Auth/view/auth/auth/login.phtml on line 45, referer: http://x.x.x.x/bareos-webui/auth/login
[Wed Feb 06 13:28:14.347819 2019] [:error] [pid 3627] [client x.x.x.x:63602] PHP Fatal error: Call to a member function prepare() on a non-object in /usr/share/bareos-webui/module/Auth/view/auth/auth/login.phtml on line 45, referer: http://x.x.x.x/bareos-webui/auth/login
If you refresh the blank page, I then get a page of the attached image.
Occasionally this will self heal, and the error does not appear in the logs.
|Steps To Reproduce||Fresh install of 18.2.5 on RHEL 7.6. After first successful login into Webui with created admin account (TLS Enable = no for the console profile), error and blank page are received on next login attempt. Will self-heal within a day and then be fine until current session times out and you log back in or force the logout and back in.|
bareos-error.PNG (23,787 bytes)
bareos-error.PNG (23,787 bytes)
|Additional information: Created a second admin account. Can temporary work around issue switching accounts in the webui when error is encountered.|
|same problem here, 18.2.5 updated from 17.2.4, system ubuntu 16.04 lts|
I originally posted this in another bug report, but I believe it applies better here:
The observation I have found, regarding this issue, is that intentionally logging out (before doing anything that triggers a session expiry response/notification) avoids triggering this bug on subsequent login.
Typically, if you remain logged in and your session expires by the time you try to perform an action, you have to log back in. This is when you encounter this bug.
Following a long idle period, if you avoid performing any action, so as to avoid being notified that your session has expired, and instead click your username and properly logout from the drop-down, you can log back in successfully without triggering this bug.
In fact, I have found that if I always deliberately logout, such that I avoid triggering the session expiry notice, I can always successfully login on the next attempt.
I have not yet tested a scenario of closing all browser windows, without logging out, then trying to login again. However, so far it seems that deliberately logging out -- even after session expiry (but without doing anything to trigger a session expiry notification) -- avoids triggering this bug.
Hope that helps with figuring out where the bug resides.
|2019-02-06 20:40||murrdyn||New Issue|
|2019-02-06 20:40||murrdyn||Tag Attached: broken|
|2019-02-06 20:40||murrdyn||Tag Attached: webui|
|2019-02-06 20:40||murrdyn||File Added: bareos-error.PNG|
|2019-02-06 20:43||murrdyn||Note Added: 0003251|
|2019-02-07 02:02||teka74||Note Added: 0003252|
|2019-02-14 17:00||xyros||Note Added: 0003262|