Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
Qerion
Contributor
Contributor

Qlik NPrinting engine stays offline

Hi all,

The Qlik NPrinting engine stays offline on our server since 30-12-2023 (that day the NPrinting 2019 November was installed). RabbitMQ version 3.7.10.

NPrinting_engine log:

RabbitMq bus is not connected - trying listener registration again in 10 seconds

Some logging:

{handshake_error,opening,
{amqp_error,internal_error,
"access to vhost '/' refused for user 'client_engine': vhost '/' is down",
'connection.open'}}
2024-01-08 16:31:12.205 [info] <0.31826.10> closing AMQP connection <0.31826.10> ([::1]:52328 -> [::1]:5672 - Qlik.NPrinting.Engine.exe, vhost: 'none', user: 'client_engine')
2024-01-08 16:31:15.595 [info] <0.31835.10> accepting AMQP connection <0.31835.10> ([::1]:52330 -> [::1]:5672)
2024-01-08 16:31:15.611 [error] <0.31835.10> Error on AMQP connection <0.31835.10> ([::1]:52330 -> [::1]:5672, vhost: 'none', user: 'client_engine', state: opening), channel 0:
{handshake_error,opening,
{amqp_error,internal_error,
"access to vhost '/' refused for user 'client_engine': vhost '/' is down",
'connection.open'}}
2024-01-08 16:31:15.611 [info] <0.31835.10> closing AMQP connection <0.31835.10> ([::1]:52330 -> [::1]:5672, vhost: 'none', user: 'client_engine')
2024-01-08 16:31:16.017 [info] <0.31844.10> accepting AMQP connection <0.31844.10> ([::1]:52331 -> [::1]:5672)
2024-01-08 16:31:16.017 [info] <0.31844.10> Connection <0.31844.10> ([::1]:52331 -> [::1]:5672) has a client-provided name: Qlik.NPrinting.WebEngine.exe
2024-01-08 16:31:16.017 [error] <0.31844.10> Error on AMQP connection <0.31844.10> ([::1]:52331 -> [::1]:5672 - Qlik.NPrinting.WebEngine.exe, vhost: 'none', user: 'client_webengine', state: opening), channel 0:
{handshake_error,opening,
{amqp_error,internal_error,
"access to vhost '/' refused for user 'client_webengine': vhost '/' is down",
'connection.open'}}
2024-01-08 16:31:16.017 [info] <0.31844.10> closing AMQP connection <0.31844.10> ([::1]:52331 -> [::1]:5672 - Qlik.NPrinting.WebEngine.exe, vhost: 'none', user: 'client_webengine')
2024-01-08 16:31:17.231 [info] <0.31853.10> accepting AMQP connection <0.31853.10> ([::1]:52332 -> [::1]:5672)
2024-01-08 16:31:17.231 [info] <0.31853.10> Connection <0.31853.10> ([::1]:52332 -> [::1]:5672) has a client-provided name: Qlik.NPrinting.Engine.exe
2024-01-08 16:31:17.246 [error] <0.31853.10> Error on AMQP connection <0.31853.10> ([::1]:52332 -> [::1]:5672 - Qlik.NPrinting.Engine.exe, vhost: 'none', user: 'client_engine', state: opening), channel 0:

Crash logging:

2024-01-18 10:50:23 =CRASH REPORT====
crasher:
initial call: rabbit_recovery_terms:init/1
pid: <0.365.0>
registered_name: []
exception error: {{badmatch,{error,{not_a_dets_file,"c:/PROGRA~3/NPRINT~1/RabbitMQ/db/RABBIT~1/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L/recovery.dets"}}},[{rabbit_recovery_terms,open_table,1,[{file,"src/rabbit_recovery_terms.erl"},{line,191}]},{rabbit_recovery_terms,init,1,[{file,"src/rabbit_recovery_terms.erl"},{line,171}]},{gen_server,init_it,2,[{file,"gen_server.erl"},{line,374}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,342}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
ancestors: [<0.363.0>,<0.362.0>,rabbit_vhost_sup_sup,rabbit_sup,<0.260.0>]
message_queue_len: 0
messages: []
links: [<0.363.0>]
dictionary: []
trap_exit: true
status: running
heap_size: 1598
stack_size: 27
reductions: 1292
neighbours:
2024-01-18 10:50:23 =CRASH REPORT====
crasher:
initial call: rabbit_vhost_process:init/1
pid: <0.364.0>
registered_name: []
exception exit: {{badmatch,{error,{{{badmatch,{error,{not_a_dets_file,"c:/PROGRA~3/NPRINT~1/RabbitMQ/db/RABBIT~1/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L/recovery.dets"}}},[{rabbit_recovery_terms,open_table,1,[{file,"src/rabbit_recovery_terms.erl"},{line,191}]},{rabbit_recovery_terms,init,1,[{file,"src/rabbit_recovery_terms.erl"},{line,171}]},{gen_server,init_it,2,[{file,"gen_server.erl"},{line,374}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,342}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]},{child,undefined,rabbit_recovery_terms,{rabbit_recovery_terms,start_link,[<<"/">>]},transient,30000,worker,[rabbit_recovery_terms]}}}},[{gen_server2,init_it,6,[{file,"src/gen_server2.erl"},{line,583}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
ancestors: [<0.362.0>,rabbit_vhost_sup_sup,rabbit_sup,<0.260.0>]
message_queue_len: 0
messages: []
links: [<0.362.0>]
dictionary: []
trap_exit: true
status: running
heap_size: 6772
stack_size: 27
reductions: 19150
neighbours:
2024-01-18 10:50:23 =SUPERVISOR REPORT====
Supervisor: {<0.362.0>,rabbit_vhost_sup_wrapper}
Context: start_error
Reason: {badmatch,{error,{{{badmatch,{error,{not_a_dets_file,"c:/PROGRA~3/NPRINT~1/RabbitMQ/db/RABBIT~1/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L/recovery.dets"}}},[{rabbit_recovery_terms,open_table,1,[{file,"src/rabbit_recovery_terms.erl"},{line,191}]},{rabbit_recovery_terms,init,1,[{file,"src/rabbit_recovery_terms.erl"},{line,171}]},{gen_server,init_it,2,[{file,"gen_server.erl"},{line,374}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,342}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]},{child,undefined,rabbit_recovery_terms,{rabbit_recovery_terms,start_link,[<<"/">>]},transient,30000,worker,[rabbit_recovery_terms]}}}}
Offender: [{pid,undefined},{id,rabbit_vhost_process},{mfargs,{rabbit_vhost_process,start_link,[<<"/">>]}},{restart_type,permanent},{shutdown,30000},{child_type,worker}]

Is there maybe someone who can help me?

Many thanks.

Best regards,
Rick

Labels (3)
3 Replies
Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

Hi @Qerion 

This is not enough information to troubleshoot this issue. All you are saying is that since you installed no longer supported version (not supported for last 3 years) engine stayed offline. 
You dont say:

  • what was the previous version?
  • whether you upgraded engine and designer?
  • whether you meet all other system requirements?
  • why you have upgraded to unsupported version ?
  • why you are labelling your post as version Nprinting 16.7?
  • what is the os?
  • Is there any other software installed on that server?
  • why arent you upgrading to supported version?
  • do you have backup of previous setup?
  • did you take repository db backup?
  • where there any upgrades or patches done to OS on that server?

That is just few basic questions so i can just picture the scenario-surely there will be more questions once we have basics.
For us to be able to help you we need to have information to replicate your scenario, environment and all your steps you have taken. We don't have that at the moment so i will wait for you to give us all that missing info before i speculate more.

Cheers

 

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.
Frank_S
Support
Support

Also if one or more engines

Have all the NP engine been updated.

 

Nov. 2019 is VERY out of support and as Lech mentioned, and also without the version upgraded from, its quite difficult the help you.

 

Recommend that you:

1. restore your original NP server version

2. Check the upgrade notes thoroughly again here before proceeding. (you can try to follow this but it is not aligned with Nov. 2019 as those notes are archived) 

https://help.qlik.com/en-US/nprinting/May2023/Content/NPrinting/DeployingQVNprinting/Qlik-NPrinting-...

https://help.qlik.com/en-US/nprinting/May2023/Content/NPrinting/DeployingQVNprinting/Upgrading-Qlik-...

3. Do NOT restore your NP database 'after' upgrading...that is not necessary (in case you have done a restore as part of your upgrade. note that restoring an old NP DB over an upgraded NP server will permanently damage your deployment). 

 

Kind regards,

Please remember hit the 'Like' button and for helpful answers and resolutions, click on the 'Accept As Solution' button. Cheers!
Qerion
Contributor
Contributor
Author

Thank you for your replies @Lech_Miszkiewicz and @Frank_S. I will follow up your recommendations and I will put an update later.

Have a nice day.