NPrinting Engine Offline and error is RabbitMQ server is not connected

[podge2019]

Hello,

Have had this issue for a few days and waiting on support, so in the meantime, I'm just asking the community if has anyone encountered this issue previously and found a resolution.

Our initial issue occurred when a running task used up all our space on the C:\ drive. We cleared down space, stopped services, rebooted and we were able to abort the task. The NPrinting Engine then went offline but a restart of the Services got it back online.  Before we had an opportunity to clear down more space on the disk, a user kicked off the task which caused us again.

Once this task was kicked off again it left us with 0 space on the C:\ Drive, the task crashed, the engine was offline and the task was still showing as running.

We managed to clear down the space on the C:\ drive using cleanup_audit.sql from this Nprinting database growing and c:\drive running out of hard disk space. After running this script the task was still showing as running on the NPrinting Console and we were unable to abort as the engine was still offline.

I then ran the cleanup_executions.sql from the same support page and this has cleared out the task executions, however, the engine is still offline now and the RabbitMq server is not connected and is appearing in the logs and constantly trying to connect.

Since then I have uninstalled and reinstalled the engine multiple times and reinstalled RabbitMQ from the instructions here The Qlik NPrinting messaging service and the Qlik NPrinting Scheduler service go offline after resta....

I'm assuming the next step would be to do a clean install and restore from a backup, however, the only backup we have is from when the engine is offline.

We're on NPrinting November 2019 running on Windows Server 2012 R2 Datacenter.

Thanks for any advice.

[Frank_S · Accepted solution]

@podge2019

This is a potentially complex resolution that would likely be better handled in your support request.

If this is your PROD environment, I suggest you ask for an update asap.

Normally, however, this issue - where the Messenger Service (RabbitMQ) is damaged or has become corrupted - can generally be resolved by a typical upgrade to a newer NP version (keeping in mind the NP server/engine/designer requirements as per Planning your deployment).

(Note: Before proceeding below, make a Fresh backup of your NP database and date it accordingly.)

However, I suggest that you install another copy of NP 19 on another server, restore your NP 19 backup and test your backup to ensure your backup file is sound. (Make sure you immediately disable your TEST server once you've confirmed that the NP DB backup is sound and uninstall the TEST NP server when able)

Once you validate your NP 19 backup on a separate test NP 19 server, attempt an upgrade to a supported version of the NPrinting Server.

You should find an automated backup of your PRE and POST NP server DB's in the following folder once the upgrade is complete

• C:\ProgramData\NPrinting​

If you have files in this directory, and you are running out of space on your c: drive, you need to clean up your c: drive as much as possible to ensure your upgrade attempt does not fail during the upgrade process. Note that a temp folder is created during the upgrade process which uses up additional drive space.

The bottom line is that you need to ensure you have plenty of c:\drive space before you attempt to upgrade.

Kind regards...

Related Info:

• How to BackUp and Restore Qlik NPrinting Repository Database from End to End

[Ruggero_Piccoli · Accepted solution]

Hi,

From November 2019 to latest available May 2021 SR3 we solved some issues related to RabbitMQ and we also update the installed version of RabbitMQ. So the first suggestion is to update your installation to take advantage of all those updates.

After upgrading test again and be sure to have enough free space on C drive. The audit trail can be configured to use less space or be disabled but, unluckily, you can install Qlik NPrinting only on the C drive.

Best Regards,

Ruggero

[podge2019]

Hi Lads, @Ruggero_Piccoli @Frank_S , went ahead and done the update.

It has indeed worked 😁 thanks so much for the guidance.

It is much appreciated.

[Ruggero_Piccoli]

@podge2019 thanks for the feedback and for marking the solution 🙂

[Frank_S]

Perfect!
Pleased to hear the upgrade worked!