KIX - Forum
Community => Fragen | Konfiguration | Hilfe => Thema gestartet von: johndoe132 am 15.12.2020 14:27:21
Hi,
I've just completed a new installation following the docker install option on Ubuntu 20.04. Everything looks good however when trying to access the backend or frontend web interfaces the system hangs at the KIX logo.
There are multiple errors in the docker logs, e.g.
2020/12/15 13:08:35 [error] 29#29: *53 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.98, server: , request: "GET / HTTP/1.1", upstream: "http://172.18.0.5:3000/", host: "192.168.0.99:20001", referrer: "http://192.168.0.99:20001/"
and
frontend_1 | Tue Dec 15 2020 13:09:12 GMT+0000 (Coordinated Universal Time) - error: Error during HTTP (system/config/definitions/job-new-form-page-filters) DELETE request.
and
frontend_1 | Tue Dec 15 2020 13:09:12 GMT+0000 (Coordinated Universal Time) - error: (404) Object.NotFound Cannot delete SysConfigOptionDefinition. SysConfigOptionDefinition 'job-edit-form-page-information' not found.
Can anyone help please? Thanks
Hi "John",
did you apply any changes to environment or other of the Docker setup config files? Apart from the first, second and third error messages occur on any first startup since the application is setup then. It checkst for existence of files and creates them if not there. So in order to help you, please provide us some more information.
regards, Torsten
Hi, thanks for the quick response.
No I didn't change anything, just installed the two Docker components then ran the commands to download and run the containers. Everything seemed to be working fine, just unable to access the Web UI. Are there any other logs etc I can provide to help?
Hi,
could you please stop any services (./stop.sh) start them again and attach the output of "./logs.sh" here? Maybe this would give some hints.
regards, Torsten
...sorry, haven't experienced this yet. It may be an issue of the docker environment:
https://forums.docker.com/t/ucp-dtr-login-issues/16256
But again - that's just a guess.
Hi,
I'm facing the same problem with the currentl KIX 18 Version running on Ubuntu 18.04.5, with docker 20.10.5:
proxy_1 | 2021/03/29 10:44:13 [error] 30#30: *1 connect() failed (113: Host is unreachable) while connecting to upstream, client: 192.168.0.11, server: , request: "GET / HTTP/1.1", upstream: "http://172.23.0
.5:3000/", host: "192.168.0.228:20001"
proxy_1 | 192.168.0.11 - - [29/Mar/2021:10:44:13 +0000] "GET / HTTP/1.1" 502 2179 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.150 Safari/537.36" "-"
docker ps returns the following output:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS
NAMES
0b6a48fa415b docker-registry.kixdesk.com/public/proxy:stable "/docker-entrypoint...." 14 minutes ago Up 13 minutes 0.0.0.0:20001->80/tcp, 0.0.0.0:20444->443/tcp, 0.0.0.0:20000->8080/tcp, 0.0.0.0:20443-
>8443/tcp, 0.0.0.0:20002->9080/tcp, 0.0.0.0:20445->9443/tcp kix_proxy_1
5045c77780c5 docker-registry.kixdesk.com/public/backend:stable "/docker-entrypoint...." 14 minutes ago Up 14 minutes
kix_backend_1
2f15d196f547 docker-registry.kixdesk.com/public/redis:stable "docker-entrypoint.s..." 14 minutes ago Up 14 minutes 6379/tcp
kix_redis_1
8e50ddbeea83 docker-registry.kixdesk.com/public/db:stable "docker-entrypoint.s..." 14 minutes ago Up 14 minutes 5432/tcp
kix_db_1
Let's check the docker network:
docker network ls
NETWORK ID NAME DRIVER SCOPE
aa5780005911 bridge bridge local
98582c96c205 host host local
32a533f35a7f kix_default bridge local
72e510190d50 none null local
docker network inspect 32a533f35a7f
[
{
"Name": "kix_default",
"Id": "32a533f35a7f97bd78b73542443885a26321682cc1f444c72b7d57b1ff141c49",
"Created": "2021-03-29T10:32:18.824530463Z",
"Scope": "local",
"Driver": "bridge",
"EnableIPv6": false,
"IPAM": {
"Driver": "default",
"Options": null,
"Config": [
{
"Subnet": "172.23.0.0/16",
"Gateway": "172.23.0.1"
}
]
},
"Internal": false,
"Attachable": true,
"Ingress": false,
"ConfigFrom": {
"Network": ""
},
"ConfigOnly": false,
"Containers": {
"0b6a48fa415b29647fdfa57a70b29690b20508a66277c58c118da753e1bfe613": {
"Name": "kix_proxy_1",
"EndpointID": "1df23125c5ca77355fa85cdb2ca4ba4394f69790598deb188f75d28431098ee5",
"MacAddress": "02:42:ac:17:00:06",
"IPv4Address": "172.23.0.6/16",
"IPv6Address": ""
},
"2f15d196f5479a69bc47e1d686eeff05337cf4bf17b50fac163779069ecaff62": {
"Name": "kix_redis_1",
"EndpointID": "054829ff1fdd93a540e263a36dc78725710d38b5f5182470e2c67a7f949beaa4",
"MacAddress": "02:42:ac:17:00:03",
"IPv4Address": "172.23.0.3/16",
"IPv6Address": ""
},
"5045c77780c5ce32f073243086b7a559f6c5b994e0b9507b1e6e0164d4260726": {
"Name": "kix_backend_1",
"EndpointID": "24a962350146062798d790de97ed617dd3f99e977f951e8692f0cf0a4a1ccf3e",
"MacAddress": "02:42:ac:17:00:04",
"IPv4Address": "172.23.0.4/16",
"IPv6Address": ""
},
"8e50ddbeea8301dd3f597747b47ba8e6b2d3fca641b946f1476e89348e8e5745": {
"Name": "kix_db_1",
"EndpointID": "b5a542c3545af42eee50d46bb96f800a54266c8ebece0fd08231464cf149f617",
"MacAddress": "02:42:ac:17:00:02",
"IPv4Address": "172.23.0.2/16",
"IPv6Address": ""
}
},
"Options": {},
"Labels": {
"com.docker.compose.network": "default",
"com.docker.compose.project": "kix",
"com.docker.compose.version": "1.21.2"
}
}
]
It seems, there is no host with ip 172.23.0.5 to connect to.
Regards,
Stefan
Hi,
can you please execute a "docker logs kix_frontend_1" and post the result here ?
thxRené
Wait I see that this container doesn't exist. That's pretty strange. Can you please execute a "docker images | grep kix" instead and post the result ?
Here's the output:
root@kix:~# docker images | grep kix
docker-registry.kix[/color]desk.com/public/proxy stable 42e945dd9c78 5 weeks ago 21.9MB
docker-registry.kix[/color]desk.com/public/backend stable b565929ec499 5 weeks ago 366MB
docker-registry.kix[/color]desk.com/public/frontend stable aa4101f216e3 5 weeks ago 317MB
docker-registry.kix[/color]desk.com/public/redis stable abf87045f0af 5 weeks ago 31.4MB
docker-registry.kix[/color]desk.com/public/db stable 5b9937400989 5 weeks ago 158MB
Regards,
Stefan
Ok, the image exists. Can you please try the command "docker logs kix_frontend_1" as well. Maybe the container logs still exist. It looks like the frontend service stopped.
best regards,Rene
Oh, this looks strange:
Mon Mar 29 2021 10:39:39 GMT+0000 (Coordinated Universal Time) - error: Error: Render async fragment error (lasso-slot:head). Exception: Error: Async fragment (lasso-slot:head) timed out after 200000ms
at Timeout._onTimeout (/opt/kix/node_modules/marko/dist/runtime/html/AsyncStream.js:193:33)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
Mon Mar 29 2021 10:39:39 GMT+0000 (Coordinated Universal Time) - info: marko app build finished: agent-portal
Mon Mar 29 2021 10:39:39 GMT+0000 (Coordinated Universal Time) - error: uncaughtException: Render async fragment error (lasso-slot:body). Exception: Error: Async fragment (lasso-slot:body) timed out after 200000
ms
at Timeout._onTimeout (/opt/kix/node_modules/marko/dist/runtime/html/AsyncStream.js:193:33)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
Error: Render async fragment error (lasso-slot:body). Exception: Error: Async fragment (lasso-slot:body) timed out after 200000ms
at Timeout._onTimeout (/opt/kix/node_modules/marko/dist/runtime/html/AsyncStream.js:193:33)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
at AsyncStream.error (/opt/kix/node_modules/marko/dist/runtime/html/AsyncStream.js:429:13)
at Timeout.<anonymous> (/opt/kix/node_modules/marko/dist/runtime/html/AsyncStream.js:193:27)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
Mon Mar 29 2021 10:39:39 GMT+0000 (Coordinated Universal Time) - error: Error loading application template
Mon Mar 29 2021 10:39:39 GMT+0000 (Coordinated Universal Time) - error: Render async fragment error (lasso-slot:head). Exception: Error: Async fragment (lasso-slot:head) timed out after 200000ms
at Timeout._onTimeout (/opt/kix/node_modules/marko/dist/runtime/html/AsyncStream.js:193:33)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
Mon Mar 29 2021 10:39:39 GMT+0000 (Coordinated Universal Time) - info: Build marko app authentication-login
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @kix/frontend@0.0.15 start: `node dist/server/index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @kix/frontend@0.0.15 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Regards,
Stefan
Great, thanks a lot. There's the cause. The machine takes too long to compile the frontend templates during startup. So the frontend service hits the 200s timeout mark and exists.
Please edit the file "environment" and add the line "LASSO_TIMEOUT=500000" to the frontend config section.
What type of machine do you use (CPU, RAM, Disk) ? It's unusual for the template compile to take that long.
best regards,Rene
The system is running on Proxmox with VirtIO SCSI, 12 GB RAM and 2 cores and KIX is currently the only application.
/opt/kix-on-premise/deploy/linux/environment
.....
# --------------------------------------------------
# frontend service configuration
# --------------------------------------------------
# the port on the docker host system where the frontend service is listening
FRONTEND_PORT=20001
FRONTEND_PORT_SSL=20444
# frontend logging (0=ERROR, 1=WARNING, 2=INFO, 3=DEBUG)
LOG_LEVEL=2
LASSO_TIMEOUT=500000
.....
root@kix:/opt/kix-on-premise/deploy/linux# watch docker logs kix_frontend_1
backend not ready yet, waiting for 10 seconds...
backend not ready yet, waiting for 10 seconds...
backend not ready yet, waiting for 10 seconds...
> @kix/frontend@0.0.15 start /opt/kix
> node dist/server/index.js
Tue Mar 30 2021 14:47:46 GMT+0000 (Coordinated Universal Time) - ^[32minfo^[39m: Startup Server
Tue Mar 30 2021 14:47:50 GMT+0000 (Coordinated Universal Time) - ^[32minfo^[39m: Create Client Registration
Tue Mar 30 2021 14:47:50 GMT+0000 (Coordinated Universal Time) - ^[32minfo^[39m: Update translations
Tue Mar 30 2021 14:47:52 GMT+0000 (Coordinated Universal Time) - ^[32minfo^[39m: Create Default Configurations
Tue Mar 30 2021 14:47:58 GMT+0000 (Coordinated Universal Time) - ^[32minfo^[39m: Found 88 configuration extensions
Tue Mar 30 2021 14:48:00 GMT+0000 (Coordinated Universal Time) - ^[32minfo^[39m: REDIS connecting
Tue Mar 30 2021 14:48:00 GMT+0000 (Coordinated Universal Time) - ^[32minfo^[39m: REDIS ready
That looks good but still the gui hangs and the system complains about a perl error and no connection to port 3000:
root@kix:/opt/kix-on-premise/deploy/linux# ./logs.sh
backend_1 | ERROR: API-89 Perl: 5.28.1 OS: linux Time: Tue Mar 30 16:48:56 2021
backend_1 |
backend_1 | Message: DebugLog error: Summary: AddCacheDependency.NoCacheType Data : Should add cache dependencies but no CacheType has been configured for this operation!.
backend_1 |
backend_1 | RemoteAddress: ::ffff:172.18.0.5
backend_1 | RequestURI: /clientregistration
backend_1 |
backend_1 | Traceback (119):
backend_1 | Module: Kernel::API::Debugger::DebugLog Line: 218
backend_1 | Module: Kernel::API::Debugger::Error Line: 313
backend_1 | Module: Kernel::API::Operation::V1::Common::_Error Line: 968
backend_1 | Module: Kernel::API::Operation::V1::Common::AddCacheDependency Line: 704
backend_1 | Module: Kernel::API::Operation::V1::ClientRegistration::ClientRegistrationCreate::Run Line: 267
backend_1 | Module: Kernel::API::Operation::V1::Common::RunOperation Line: 189
backend_1 | Module: Kernel::API::Operation::Run Line: 248
backend_1 | Module: Kernel::API::Provider::Run Line: 415
backend_1 | Module: (eval) Line: 31
backend_1 | Module: (eval) Line: 74
backend_1 | Module: Plack::Sandbox::_2fopt_2fkix_2fbin_2fserver_2fapp_2epsgi::__ANON__ Line: 73
backend_1 | Module: CGI::Emulate::PSGI::__ANON__ (v0.23) Line: 30
backend_1 | Module: Plack::Middleware::StackTrace::try {...} Line: 38
backend_1 | Module: (eval) (v0.30) Line: 100
backend_1 | Module: Try::Tiny::try (v0.30) Line: 93
backend_1 | Module: Plack::Middleware::StackTrace::call Line: 42
backend_1 | Module: Plack::Component::__ANON__ Line: 50
backend_1 | Module: Plack::Middleware::AccessLog::Timed::call Line: 17
backend_1 | Module: Plack::Component::__ANON__ Line: 50
backend_1 | Module: Plack::Middleware::Deflater::call (v0.12) Line: 20
backend_1 | Module: Plack::Component::__ANON__ Line: 50
backend_1 | Module: Plack::Middleware::Refresh::call Line: 23
backend_1 | Module: Plack::Component::__ANON__ Line: 50
backend_1 | Module: Plack::Middleware::Lint::call Line: 24
backend_1 | Module: Plack::Component::__ANON__ Line: 50
backend_1 | Module: Plack::Middleware::StackTrace::try {...} Line: 38
backend_1 | Module: (eval) (v0.30) Line: 100
backend_1 | Module: Try::Tiny::try (v0.30) Line: 93
backend_1 | Module: Plack::Middleware::StackTrace::call Line: 42
backend_1 | Module: Plack::Component::__ANON__ Line: 50
backend_1 |
proxy_1 | 2021/03/30 14:49:01 [error] 29#29: *47 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.11, server: , request: "GET / HTTP/1.1", upstream: "http://172.18.0.5:3000/", host: "192.168.0.228:20001", referrer: "http://192.168.0.228:20001/"
proxy_1 | 192.168.0.11 - - [30/Mar/2021:14:49:01 +0000] "GET / HTTP/1.1" 502 2179 "http://192.168.0.228:20001/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4371.0 Safari/537.36" "-"
Thank you for your help!
Regards,
Stefan
Finally! I can log into the system, but it seems to be slow compared to other vms/applications running on that node. What is the recommended environment (CPU, RAM) for KIX18?
Regards,
Stefan
Hi,
we recommend using a machine with more CPUs for parallelism. KIX on-prem has a good bunch of processes (multiple backend workers, frontend server, redis, database, nginx proxy). Please try 4 vCPU for the docker host VM. Just have a look at the docker host VM whether you are running 100% flatline when using KIX with 2 vCPU. What type of CPU are you using ?
best regards
René
Hi,
since I had no reason to change it, I configured the VM with the "Default (kvm64)" CPU.
Regards,
Stefan
Hi Stefan,
ok, that's the emulated CPU (virtual). But what kind of physical CPU is built into that server ?
best regardsRene
Hi Rene,
it is a Xeon E5645.
Regards,
Stefan
Hi Stefan,
ok, that's a rather old CPU with lower single core performance (about the same single core performance like an actual Intel Celeron J4005 CPU). We are using the same CPU in one of our test swarm nodes. It's the slowest node and you will definitely notice when the app services are located on this node. The other servers of this swarm are running 2650v3 and X5670 cpus and are noticably faster.
But beside that, we've never hit the Lasso timeout during the frontend build process on that slower node.
best regards,
René