Skip to main content

We have a situation where in both 22R1 and now 22R2, the reporting pods need to be restarted several times a month.  Has anyone else encountered this or know what may be the cause?

When it occurs:

  1. We see that print jobs go into Waiting status inside IFS.  No errors are seen but depending on what/how they are printing, some users get a message that the print is taking time and will be completed as a background job.  
  1. Checking the status of the pods, no errors or bad status is shown.  Everything appears fine.
  1. Performing a stop and then a start on the ifsapp-reporting-<id> pod immediately starts processing the jobs again.

The problem occurs mostly when we have heavier volumes (most of which are actually PDF) are being printed.

Here is what we have tried so far to resolve, which doesn’t appear to have made any difference:

  • Created a dedicated “In Sequence” report message queue and message queue (instead of “In Parallel” to try to avoid contention) for the jobs being sent to the NO_PRINTOUT printer being used for the PDF prints.
  • Added extra replicas for the ifsapp-reporting, ifsapp-reporting-ren and ifsapp-reporting-br pods (for a total of 2 each)

Looking for any thoughts, guidance for things to try or whether this might even be a known issue in 22R2.

Thanks in advance!

Nick

 

Hello @NickPorter,

We have the same issue, IFS support asked to do an AWR Report but we don’t know exactly how to do this.

Denis

Hello @ERPDMORENA,

One of our customers experience a similar issue. Have you managed to resolve the above issue?

Regards,

Namal 

Hi @namouk 

We have the same issue but with our experience… No, IFS has yet to provide a fix in over a year since the issue has started to occur. They are claiming they need more log information when we have provided it all.

Thanks,
Bryan 

Hi Nick,

Same issue as you described. Finally we had IFS schedule a pods restart every sunday evening. In that period found no printing - issues for which pod restart was neccessary.

Now on 23R2 for one month in which this should be solved 

Kind regards,

Arjen 

We had a similar issue, our implementation partner mentioned that the fix is in the following releases:

 

22.2.24 - 22R2 SU24, 23.1.17 - 23R1 SU17, 23.2.10 - 23R2 SU10, 24.1.4 - 24R1 SU4, 24.2E.0 - 24R2 EA

 

Hope this helps.

 

We would like to know if this is a known issue as well. So far no response from IFS (we have an open case CS0290861).

Have You created service tickets for that? Maybe we should gather the list of ticket to show scale...

Hi knepiosko, 

We had serious issue with this in our warehouse picking proces for which we had a prio case. Due to the need of frequent restart of the pods (separate prio cases) for us, the request was granted to (preventive) restart of the print-pods every weekend for a limited period until we upgraded from 22R2 SU7 to 23R2 SU5. After upgrade in last 2 months no issues with printing-pods.

Reply


Terms & ConditionsCookie settings