rancher: Rancher UI login extermely slow

We are experiencing issues with our Rancher Web UI, which is behaving slowly during logins and has been affecting user’s browser performance during the login process. I have a attached a screenshot of what we see when logging into Rancher. screen shot 2017-01-25 at 10 41 17 am

It will stay on this screen for 2-3mins.

We think the issue is LDAP related, but its hard to pen point since we can’t find any auth related log data from the rancher-server container. We had tried different domain controllers with same results. However, it does appears that auth is happening because if you enter in a wrong password, you will be denied access.

Our current setup is rancher-server container with a external MySQL database running on the host. I have also setup HTTPS and using a nginx container to proxy from port 8000 to 433.

Please let us know if we can provide any further info.

Thanks,

Useful	Info
Versions	Rancher `v1.3.2` Cattle: `v0.175.8` UI: `v1.3.5`
Access	`ldap` `admin`
Orchestration	`Kubernetes`
Route	`k8s-tab.namespace.stacks.index`

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 15 (1 by maintainers)

Most upvoted comments

Mount is large, but not terrifying. We have a cleanup script that should prune unused mounts, can you give that a go and see if it resolves the issue?

docker run --rm rancher/cleanup-1-1:v0.1.2 should give you the usage… just point it at your db.

aemneina on Jan 27, 2017

How would I run this cleanup on a single container instance? ie no external database

@cdomigan this is how I did it just now:

Create backup of database and verify dump completeness:

[deploy@docker01 ~]$ docker exec -it <id-of-server-container> mysqldump cattle > cattle.sql
[deploy@docker01 ~]$ head cattle.sql 
-- MySQL dump 10.13  Distrib 5.5.53, for debian-linux-gnu (x86_64)
--
-- Host: localhost    Database: cattle
-- ------------------------------------------------------
-- Server version       5.5.53-0ubuntu0.14.04.1

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
[deploy@docker01~]$ tail cattle.sql 

/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;

-- Dump completed on 2017-03-03  9:09:18

Run cleanup:

[deploy@docker01 ~]$ docker run --rm --link <id-of-server-container>:mysql rancher/cleanup-1-1:v0.1.2 --db-host mysql

klausmeyer on Mar 3, 2017

Okay thats a capable host… It also looks like your query is choking on the amount of volumes/mounts. Can you share the output of: SELECT table_name AS "Table", round(((data_length + index_length) / 1024 / 1024), 2) as TEST FROM information_schema.TABLES WHERE table_schema = "<cattle_db_name>" ORDER BY TEST;

aemneina on Jan 27, 2017