topic Crash Sense Server. Help detect problem in Management & Governance

Crash Sense Server. Help detect problem

korsikov — Tue, 21 Oct 2014 08:37:37 GMT

i have Sense site with 2 nodes. After power failure, start the server. But when I try to open one application server freeze, and not possible to open the hub and the management console. Restarting services does not help. More precisely when you restart the engine service hangs in the "stoping". Help restart operation system.

draws attention to the logs messages

Proxy audit log

The already opened client to target failed to connect, trying to reconnect with a new client once.

system proxy

When contacting https://localhost:4242/

No connection could be made because the target machine actively refused it 127.0.0.1:4242

System Engine

20141021T111502.673+0300

INFO

Fly

System.Engine.Engine

400

dc64de39-deb8-4ea7-8c80-d41b727ae76f

RBCGRP\qvuser

DOC loading: Beginning load of document 6FEB8FBA-0BFE-4708-8D3A-2EC1A33C0F5F.

INTERNAL

sa_scheduler

20141021T111502.673+0300

2072

1104

20141021T111321.000+0300

dc64de39-deb8-4ea7-8c80-d41b727ae76f

20141021T111555.805+0300

ERROR

Fly

System.Engine.Engine

400

4e6c3707-8849-4919-bfdf-4b65aadac5e0

RBCGRP\qvuser

Failed reading logs from engine. Possibly protocol violation. Exception of type 'System.OutOfMemoryException' was thrown.

4e6c3707-8849-4919-bfdf-4b65aadac5e0

20141021T111555.898+0300

ERROR

Fly

System.Engine.Engine

400

e3bab897-119f-4c01-b355-58791c3f96a5

RBCGRP\qvuser

Failed reading logs from engine. Possibly protocol violation. Exception of type 'System.OutOfMemoryException' was thrown.

e3bab897-119f-4c01-b355-58791c3f96a5

20141021T111556.226+0300

ERROR

Fly

System.Engine.Engine

400

17f6d702-cee8-4533-8520-15df77dd3396

RBCGRP\qvuser

Failed reading logs from engine. Possibly protocol violation. Exception of type 'System.OutOfMemoryException' was thrown.

17f6d702-cee8-4533-8520-15df77dd3396

20141021T111556.226+0300

ERROR

Fly

System.Engine.Engine

400

863aa766-e161-4f81-8c7c-d3ad3e4afc42

RBCGRP\qvuser

Failed reading logs from engine. Possibly protocol violation. Exception of type 'System.OutOfMemoryException' was thrown.

863aa766-e161-4f81-8c7c-d3ad3e4afc42

20141021T111556.304+0300

ERROR

Fly

System.Engine.Engine

400

f697839d-7a6f-4d47-b7c0-fe00ca164f62

RBCGRP\qvuser

Failed reading logs from engine. Possibly protocol violation. Exception of type 'System.OutOfMemoryException' was thrown.

f697839d-7a6f-4d47-b7c0-fe00ca164f62

20141021T111557.380+0300

INFO

Fly

System.Engine.Engine

400

528af7f1-e9b3-4f63-9d0d-c27390ed7fc6

RBCGRP\qvuser

DOC loading: Unloading document 6FEB8FBA-0BFE-4708-8D3A-2EC1A33C0F5F, state UNLOADING.

Personal

20141021T111557.318+0300

856

1104

20141021T111321.000+0300

528af7f1-e9b3-4f63-9d0d-c27390ed7fc6

Re: Crash Sense Server. Help detect problem

korsikov — Tue, 21 Oct 2014 08:42:14 GMT

Okay, let's say that the application is crash the engine, so why not work management console? For her work must be the work of a proxy service and service repository. Job Engine service is not obligatory

Re: Crash Sense Server. Help detect problem

korsikov — Wed, 22 Oct 2014 08:58:39 GMT

System_engine log have a record

Engine: Server aborted. Reason for restart: Internal inconsistency, type F, detected.

workaround the problem.

delete problem app, publication of the working version of the application from my work to stream.

Re: Crash Sense Server. Help detect problem

Anonymous — Thu, 30 Oct 2014 17:25:59 GMT

I have the same issue with our single Qlik Sense server. I was setting it up and only had one app, when I had a memory chip in the server go bad. After replacing the chip, the services all show started ( in delay mode) but I can't open the Management Console. I found the same message in my log files. No connection could be made because the target machine actively refused it at 127.0.0.1:4242. I tried deleting and re installing the Qlik Sense sever, but it still will not open and I have the same message. Is this a bug or did you find a solution?

Re: Crash Sense Server. Help detect problem

korsikov — Thu, 19 Feb 2015 14:41:02 GMT

Last time I just deleted the problematic applications. And now again faced with such a problem.If I find a solution, just tell you the decision problemmy.

Re: Crash Sense Server. Help detect problem

Anonymous — Fri, 06 Mar 2015 01:31:31 GMT

By any chance have you found a solution for the problem? We are having the same issue without any clue here

Re: Crash Sense Server. Help detect problem

korsikov — Fri, 06 Mar 2015 06:59:47 GMT

And what is your mistake? exactly the same? In what situation occurs?

Re: Crash Sense Server. Help detect problem

edisa — Tue, 10 Mar 2015 10:05:29 GMT

Hi guys!

I have the same issue.

My configuration server was working fine 1 week ago, but...now, i don't have idea why is the problem...I can't access HUB and QMC,...

I tried remove certificates, restart services, reinstall server,...etc (discussions forums), but nothing...

Any ideas?

MY LOGS:

In Audit_Proxy(LOG): (my hostname is demosqv, user: adminqv)

"...Audit.Proxy.Proxy.Communication.HttpChannel.HttpChannelHandler...The already opened client to target failed to connect, trying to reconnect with a new client once. https://demosqv:4242/..."

"...Audit.Proxy.Qlik.Sense.Common.Communication.Tcp.StreamFactory 3312 d458ee05-7d1c-44f2-9cd4-47100c62a576 DEMOSQV\adminqv Error during stream authentication to server..."

"...Audit.Proxy.Proxy.Communication.Streams.AsyncStreamFactory 3312 5785c5da-9d27-41a5-9711-f9a5f28b31db DEMOSQV\adminqv Connection negotiation as server failed 10.10.19.7:443 <-> 10.10.19.7:49705, using: SslNoClientValidation..."

2. In System_Proxy(LOG): (my hostname is demosqv, user: adminqv)

"...DEMOSQV\adminqv When contacting https://localhost:4242/ No se puede establecer una conexión ya que el equipo de destino denegó expresamente dicha conexión 127.0.0.1:4242 ..."

"...WARN demosqv System.Proxy.Proxy.Settings.SettingsHandler 4824 a8ed10a2-e64a-44c0-b933-480dd90bf87e DEMOSQV\adminqv Could not contact local repository to retrieve proxy settings No se puede establecer una conexión ya que el equipo de destino denegó expresamente dicha conexión 127.0.0.1:4242..."

"...DEMOSQV\adminqv Message from remote endpoint at https://localhost:4242/: <DOCTYPE HTML PUBLIC -W3CDTD HTML…"

"...WARN demosqv System.Proxy.Qlik.Sense.Common.Communication.Tcp.StreamFactory 1032 b632cf8d-0265-49fe-95e9-d7870c20206d DEMOSQV\adminqv Error during stream authentication to server Error de autenticación porque la parte remota cerró la secuencia de transporte..."

CAPTURE:

Thnaks. Regards.

Re: Crash Sense Server. Help detect problem

korsikov — Wed, 11 Mar 2015 08:23:28 GMT

can you attach all log's?

Re: Crash Sense Server. Help detect problem

edisa — Wed, 11 Mar 2015 09:21:11 GMT

I attach you all logs

Re: Crash Sense Server. Help detect problem

edisa — Thu, 12 Mar 2015 15:12:44 GMT

I have resolved my issue!

Simply, i have downloaded the new version software of Qlik Sense Server (March 2015--> (Qlik Sense v1.1.0.0), and i have re-instalated.

I dont understand why there isn't a clear support or documentation, for something so simple. I have been fighting to resolve several days, and it was as simple as reinstalling a new software again, becuase SENSE is very recent,...and in the part of server, there are lots of problems.

I hope my solution is worth to you!

Bye!

Re: Crash Sense Server. Help detect problem

HarishThirunahari — Tue, 15 Mar 2022 16:22:59 GMT

Hey everyone , I do have same issue right now, if anyone remember the issue and the resolution you did for that please guide me,

I have a cluster working all good , just that the app creation happens but app fails to open with no engine found error, below is the proxy log reference for you all, Thanks ,

110 20220315T160113.292+0000 INFO self-engine-one Audit.Proxy.Proxy.Communication.HttpChannel.HttpChannelHandler 25 f65d7a97-0b76-47ac-ab7c-891457cfcb85 SELF-ENGINE-ONE\qservice The already opened client to target failed to connect, trying to reconnect with a new client once. https://central-primary:4242/
111 20220315T160659.987+0000 INFO self-engine-one Audit.Proxy.Proxy.Communication.HttpChannel.HttpChannelHandler 25 d82aaef8-7655-426a-8a90-b97a44a592e7 SELF-ENGINE-ONE\qservice The already opened client to target failed to connect, trying to reconnect with a new client once. https://self-engine-one:4242/
112 20220315T160700.281+0000 INFO self-engine-one Audit.Proxy.Proxy.Communication.HttpChannel.HttpChannelHandler 25 624fded8-1964-4c4f-a141-9872e27c5ed8 SELF-ENGINE-ONE\qservice The already opened client to target failed to connect, trying to reconnect with a new client once. https://self-engine-one:4242/
113 20220315T160700.284+0000 INFO self-engine-one Audit.Proxy.Proxy.Communication.HttpChannel.HttpChannelHandler 24 7b026fa1-6486-4e4a-85dc-ccfc21d1c624 SELF-ENGINE-ONE\qservice The already opened client to target failed to connect, trying to reconnect with a new client once. https://self-engine-one:4242/
114 20220315T160700.288+0000 INFO self-engine-one Audit.Proxy.Proxy.Communication.HttpChannel.HttpChannelHandler 25 ab7ce70e-e53c-447e-83aa-278d43579245 SELF-ENGINE-ONE\qservice The already opened client to target failed to connect, trying to reconnect with a new client once. https://self-engine-one:4242/
115 20220315T160700.291+0000 INFO self-engine-one Audit.Proxy.Proxy.Communication.HttpChannel.HttpChannelHandler 24 4cc24ab1-8be4-4a5c-9ffa-f4fd784b72de SELF-ENGINE-ONE\qservice The already opened client to target failed to connect, trying to reconnect with a new client once. https://self-engine-one:4242/
116 20220315T160700.339+0000 INFO self-engine-one Audit.Proxy.Proxy.Communication.HttpChannel.HttpChannelHandler 20 4f9ff199-2b1f-4a27-b5b3-0d422ebaf983 SELF-ENGINE-ONE\qservice The already opened client to target failed to connect, trying to reconnect with a new client once. https://self-engine-one:4242/
117 20220315T160704.433+0000 INFO self-engine-one Audit.Proxy.Proxy.SessionEstablishment.LoadBalancingHandlerDependencies 30 9c5750bd-658e-4fd6-9bf7-ea2c91cf9531 SELF-ENGINE-ONE\qservice Retrieved 0 engine(s) from repository, result code Ok, app: 0cc24476-a77c-477f-ba37-371801d8411f 033784bf-db3e-4d2d-b
118 20220315T160704.434+0000 WARN self-engine-one Audit.Proxy.Proxy.SessionEstablishment.LoadBalancingHandlerDependencies 30 297f5fb1-08bc-4b07-8667-e33d6eeb9912 SELF-ENGINE-ONE\qservice The load balancing module did not return any engine service for the following app: 0cc24476-a77c-477f-ba37-371801d8411f