arangodb icon indicating copy to clipboard operation
arangodb copied to clipboard

3.12 webui fails soon after login

Open LaravelFreelancerNL opened this issue 1 year ago • 7 comments

My Environment

  • ArangoDB Version: 3.12.0-1
  • Deployment Mode: Single Server
  • Deployment Strategy: Manual Start
  • Configuration: default, no root pw (local dev)
  • Infrastructure: own
  • Operating System: Windows 11 with WSL/Ubuntu 20.04
  • Total RAM in your machine: 64GB
  • Disks in use: SSD
  • Used Package: Ubuntu .deb

Component, Query & Data

Affected feature: web interface

Steps to reproduce

  1. Purge arangodb 3.11 (or just update, the result is the same)
  2. Install ArangoDB 3.12 within WSL2, no root pw setting
  3. Login with root
  4. Select _system db
  5. wait for the fails

Problem: Several errors occur:

  1. DB: could not fetch database
  2. Network tab shows several requests failing:
  • job (net::Err..)
  • user (net::Err..)
  • root (net::Err..)
  • fontawesome webfonts
  1. click on databases:
  • Error shown: Failure: got unexpected server response: 11: not authorized to execute this request
  • databaseDefaults request fails (401)
  • database requests fails (401)

Expected result: The UI to work properly.

I've posted a video of the sequence described here in the general slack channel. (The video was too large to attach to this issue).

(upon purging 3.12 and reverting to 3.11 everything works fine)

LaravelFreelancerNL avatar Apr 12 '24 14:04 LaravelFreelancerNL

I've just given 3.12-1 a try and this issue is resolved.

LaravelFreelancerNL avatar Aug 03 '24 13:08 LaravelFreelancerNL

Thanks!

dothebart avatar Aug 05 '24 07:08 dothebart

@dothebart apparently I spoke too soon. Although the behaviour has been improved a lot.

I still get similar behaviour but after a few hours instead of right away. After some time I get an authorization error and am redirected to the login screen. This has happened several times during active use (and from the looks of it during inactive use as well, but I don't know if that received the same error).

It looks like there is a client site timeout which doesn't take the DB connection and/or recent activity in to account.

LaravelFreelancerNL avatar Aug 06 '24 09:08 LaravelFreelancerNL

ok, can you take a look into the logfiles to see wether the PID changes in that range of time? Its the value in [] .

dothebart avatar Aug 06 '24 12:08 dothebart

Sprry, I missed your comment. I'll check the logs when it happens again.

LaravelFreelancerNL avatar Aug 19 '24 07:08 LaravelFreelancerNL