topic Re: Monitoring Apps 2.0.1 fail on reload - missing fields in Management & Governance

Monitoring Apps 2.0.1 fail on reload - missing fields

josecardenas — Thu, 09 Jul 2015 15:39:27 GMT

Hi Tyler

I've updated qlik sense to 2.0.1 and I've found an error reloading license and operations monitor

On License monitor I'm getting field not found - <CounterName>

On operations monitor I'm getting Field not found - <ProxySessionId>

Please check the scripts logs downloaded

Thanks

Jose

Re: Monitoring Apps 2.0.1 fail on reload - missing fields

Tyler_Waterfall — Thu, 09 Jul 2015 16:04:16 GMT

Jose - This is a known issue with the timing of when certain logs are written after a service or machine restart. A fix has been identified but will not be available until the next service release.

The workaround for now is to remove the malformed log files mentioned in the data load logs, specifically:

lib://ServerLogFolder/Engine\Audit\ANALYTICSSERVER_AuditActivity_Engine.txt

and

lib://ServerLogFolder/Engine\Audit\ANALYTICSSERVER_QixCounter_Engine.txt

where ServerLogFolder is the folder where the primary Log files are stored (default is c:\programdata\qlik\sense\log)

Re: Monitoring Apps 2.0.1 fail on reload - missing fields

fosuzuki — Fri, 10 Jul 2015 22:42:00 GMT

Hi Tyler,

I also had trouble reloading the monitors. I removed the files you mentioned, but the reload tasks found errors with other 32 files in the lib://ArchivedLogsFolder folders:

- lib://ArchivedLogsFolder/[USERLOGIN]\Engine\Audit\[SERVERNAME]_AuditActivity_Engine_[DATETIME].log

- lib://ArchivedLogsFolder/[USERLOGIN]\Engine\Audit\[SERVERNAME]_QixCounter_Engine_[DATETIME].log

- lib://ArchivedLogsFolder/[USERLOGIN]\Engine\System\[SERVERNAME]_Service_Engine_[DATETIME].log

- lib://ArchivedLogsFolder/[USERLOGIN]\Engine\Trace\[SERVERNAME]_Performance_Engine_[DATETIME].log

- lib://ArchivedLogsFolder/[USERLOGIN]\Engine\Trace\[SERVERNAME]_Session_Engine_[DATETIME].log

- lib://ArchivedLogsFolder/[USERLOGIN]\Engine\Trace\[SERVERNAME]_System_Engine_[DATETIME].log

- lib://ArchivedLogsFolder/[USERLOGIN]\Engine\Trace\[SERVERNAME]_Traffic_Engine_[DATETIME].log

Apparently this bug affected all the archived logs generated between the update to v2.0.1 and the fix you mentioned for the ServerLogFolder...

Re: Monitoring Apps 2.0.1 fail on reload - missing fields

Tyler_Waterfall — Mon, 13 Jul 2015 10:45:26 GMT

Fernando,

Unfortunately, the bug we are discussing (that you are experiencing) will show itself anytime services are restarted. So, if you have multiple service restarts, it is possible that a malformed log will be created which will cause the apps to fail in reload.

The next SR will have the fix to this logging, but those bad logs will still need to be removed even after the fix.

The next version of the Monitoring Apps will handle these malformed logs better (i.e. not fail on reload!) but the delivery date for updated apps has not been defined yet.

If this is becoming impossible to deal with and you cannot wait for the SR, you can modify the load script and include SET errormode=0; before the few load .... from statements in both apps. Duplicate the apps, open the copies in the Hub and make the changes, and then published those apps to the monitoring apps stream (can replace the existing apps). This is far from ideal and would not be 'supported', but it pains me to think of your inability to use the apps

Re: Monitoring Apps 2.0.1 fail on reload - missing fields

fosuzuki — Mon, 13 Jul 2015 12:23:20 GMT

Hello Tyler,

I am from a partner and I've encountered this problem in my test environment, so fortunately for me this won't be such a big deal.

The next SR you are talking about is the one expected to be released in September?

I really appreciate your comments. For me it's ok, but it will sure help other people with Prod environments and a real need to use the monitoring apps.

Re: Monitoring Apps 2.0.1 fail on reload - missing fields

josecardenas — Tue, 14 Jul 2015 09:38:53 GMT

Hi Taylor

I've removed the "malformed" files including historical ones and it is working. Many thanks for the guidance. However, I am getting a new error, very uncommon, by the way, Field not found - <Id_temp> in the license monitor app. It's happening when the sub contacttables is called for "LogContent" as concatToTable and "Working" as IncrementalTable; the contactField is getting an error when the sub is creating the $(concatField)_temp

Please, see the log attached

Many thanks for your answer,

ose

Re: Monitoring Apps 2.0.1 fail on reload - missing fields

Tyler_Waterfall — Wed, 15 Jul 2015 18:01:31 GMT

Hola Jose -

I have seen this reload error but it is usually just when I have either turned off all Qlik services and reload the app two times (no new log entry has been generated) or when I copy log folders to a local drive for testing and then reload the app twice. The reason is that there is not a single new log entry to be found and the load script does not handle that situation well.

The next release of the Monitoring apps will include a few updates to the load script to handle this and other unexpected situations with the logs.

Can you tell me - when are you seeing this reload error? Just reloading the app from QMC? Or in a duplicate app or other scenario?

Re: Monitoring Apps 2.0.1 fail on reload - missing fields

Tyler_Waterfall — Wed, 15 Jul 2015 18:04:32 GMT

Fernando - Yes, the next service release 2.0.2 includes a fix to the logs to prevent these malformed logs. I am not sure when this SR is planned for release, though I would guess in the next few weeks.

Also, as I shared with Jose, the next release of the apps (not in the 2.0.2 service release) will handle reload issues in a more robust manner. Again it is not clear to me when 2.1 will be released.

Re: Monitoring Apps 2.0.1 fail on reload - missing fields

josecardenas — Thu, 16 Jul 2015 08:15:37 GMT

Hola Tyler,

The reload error was after I've deleted the malformed files, and I have to restart the services for a proxy change. The reloading task shows me the error sent. I’ve just decided stop the task, disable for a while and then enable it and run it again. Right now is working scheduled without a problem!

Gracias,

Jose

Re: Monitoring Apps 2.0.1 fail on reload - missing fields

Tyler_Waterfall — Thu, 16 Jul 2015 11:32:47 GMT

Look for the 2.0.2 release in the next week or so!

Re: Monitoring Apps 2.0.1 fail on reload - missing fields

fosuzuki — Thu, 16 Jul 2015 12:47:34 GMT

Hi Tyler, thanks for the info.

Re: Monitoring Apps 2.0.1 fail on reload - missing fields

korsikov — Sat, 18 Jul 2015 19:52:26 GMT

i have procution server on sense 2.0.1

After rebooting the operating system faced the same problem that occurs.

To me it is essential to have information about the system. I'll try to fix it.

But I am outraged that such an important diagnostic tool was not checked.

Re: Monitoring Apps 2.0.1 fail on reload - missing fields

korsikov — Sat, 18 Jul 2015 20:07:09 GMT

tnx twa

License montor works

I stopped the service, added to his right ntfs and removed two files

AuditActivity_Engine.txt and QixCounter_Engine.txt

but Operation monitor reload failed with error

Error: Field not found - <ProxyPackageId>

2015-07-18 23:03:18 General Script Error

2015-07-18 23:03:18 Execution Failed

2015-07-18 23:03:18 Execution finished.

What can I fix it?

Re: Monitoring Apps 2.0.1 fail on reload - missing fields

korsikov — Sat, 18 Jul 2015 20:17:57 GMT

i fix it.

I had to remove 3 last log files (session, system and perfomance) in folder

Archived Logs\servname\Engine\Trace

Re: Monitoring Apps 2.0.1 fail on reload - missing fields

korsikov — Tue, 21 Jul 2015 07:57:32 GMT

upgrade my server to 2.0.2 and test it!

Re: Monitoring Apps 2.0.1 fail on reload - missing fields

korsikov — Tue, 21 Jul 2015 08:11:30 GMT

I updated my cluster and again faced with the same problem. I'll be corrected in the same way and I hope that this problem will not arise again.

Very pleased that the update was correctly the first time.

Re: Monitoring Apps 2.0.1 fail on reload - missing fields

Tyler_Waterfall — Tue, 21 Jul 2015 14:41:40 GMT

Alexander,

Even with the upgrade you need to remove any bad log files from 2.0.1 or you will continue to get the error. Once the bad files are deleted, you will not experience the issue again.

The next release of the Monitoring Apps will make it so that you do not have to remove bad log files, but this improvement was not part of 2.0.2.

Tyler

Re: Monitoring Apps 2.0.1 fail on reload - missing fields

Allardata — Wed, 22 Jul 2015 09:49:16 GMT

Had this issue as well, together with too much errors regarding connection lost with the Sense Engine.

So I started to do everything described in this thread. That took a lot of work and longer than I'd hoped...

Removed all of the log files that both monitors complained about
Updated Sense Server to 2.0.2
After that update, almost all my reload tasks failed with the notification "App is not enabled".
Unclear what that means during this step; but after finishing it's clearly stated in the (44-page) installation guide.
Strange to me that only the License Monitor and my LDAP sync tasks succeeded.
A hint was a yellow indicator in the QMC next to the "Apps" menu button
Turns out, after close inspection and some random clicking-around...
Applications have to be Migrated! There's an action button that I can't remember seeing before.
Probably my fault rushing through the server update and not reading the entire installation guide.
So I migrated an application, just to see what happens...
Including the Operations Monitor! Which is kindof strange, but okay.
That worked! "Successfully migrated selected apps"

The Yellow indicator next to the "Apps" menu item counted down with 1.
Using the column selector I could select the column "Migration status"

All except one finished within a second.
That other one is going on for 10 minutes already, let's see what happens there.
And now the reload tasks for the migrated apps work!
Also there are now two new monitor applications added; with the suffix "_1.0.0.0"
There's even a third License monitor "_2.0.1.0", can't remember if that was already there before the update to 2.0.2

End result:

Server is updated to 2.0.2 SR.
Monitor apps reload and work, although a lot of history is lost.
Other apps are migrated (1 still ongoing), reload and are accessible.

Re: Monitoring Apps 2.0.1 fail on reload - missing fields

Allardata — Wed, 22 Jul 2015 10:04:49 GMT

Short update: The ongoing migration for that remaining app failed after about 15-20 minutes. But then restarting the migration succeeded within a second just like the others. Good news: every app successfully migrated to 2.0.2.

Re: Monitoring Apps 2.0.1 fail on reload - missing fields

Thu, 23 Jul 2015 15:47:17 GMT

We have seen this in house as well but it is a tough problem to reproduce and because of that we have not gotten far with it. I will forward this on to the developers so they can see a field based scenario where it failed as well.