x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 2 replies
  • Subscribers 137 subscribers
  • Views 455 views
  • Users 0 members are here
Browse Forums
Announcements
237
topics
29
replies
General Discussion
5k
topics
13k
replies
Sage Data & Analytics
56
topics
95
replies
Sage Enterprise Intelligence
211
topics
418
replies
Sage Intelligence Reporting
121
topics
322
replies
chunheng

Batch Server is in running state but Query Management shows tasks not running

Posted By

Hi,

Need a help from Sage community on this post-mortem case (the 01/11/2023 running tasks are after resolution).

Would like to know next steps in the investigation as I have hit a wall in this search for why Batch Server not responding to Query Management but set as Running.

Is there another log file I may be missed in this Batch Server case?

The situation is as follows:

I was called in to resolve an Accounting Task issue which is active but Journal on Hold is not 0.

From the Accounting Task log at 14/10/2023.

When I checked the Batch Server's Diagnosis at that time:

When I checked the Batch Server's `serveur.tra` file, the last few records are only these regarding the queries in Query Management.

```

=1000 00274368 10-14-23 20:13:06 (Application server time) EXEC_RQT - Query execution management: Query Activation (DEV AWRKSIG P 2216 256413) (51000)
=0000 00274368 10-14-23 20:13:06 (Application server time) TACHE=AWRKSIG FLAG=2 (00000)
=0000 00274368 10-14-23 20:13:06 (Application server time) FINREQ - Ended query management: Query complete (00000)
=1000 00274369 10-14-23 20:13:08 (Application server time) EXEC_RQT - Query execution management: Query Activation (PROD ACCBATCH1 P BATCHCPT 2868 256414) (51000)
=0000 00274369 10-14-23 20:13:08 (Application server time) TACHE=ACCBATCH1 FLAG=2 (00000)
=0000 00274369 10-14-23 20:13:08 (Application server time) FINREQ - Ended query management: Query complete (00000)
=1000 00274370 10-14-23 20:13:10 (Application server time) EXEC_RQT - Query execution management: Query Activation (DEV ACCBATCH1 P BATCHCPT 844 256415) (51000)
=0000 00274370 10-14-23 20:13:10 (Application server time) TACHE=ACCBATCH1 FLAG=2 (00000)
=0000 00274370 10-14-23 20:13:10 (Application server time) FINREQ - Ended query management: Query complete (00000)
=1000 00274371 10-14-23 20:14:04 (Application server time) EXEC_RQT - Query execution management: Query Activation (PROD AWRKSIG P 5832 256416) (51000)
=0000 00274371 10-14-23 20:14:04 (Application server time) TACHE=AWRKSIG FLAG=2 (00000)
=0000 00274371 10-14-23 20:14:04 (Application server time) FINREQ - Ended query management: Query complete (00000)
=1000 00274372 10-14-23 20:14:06 (Application server time) EXEC_RQT - Query execution management: Query Activation (DEV AWRKSIG P 9032 256417) (51000)
=0000 00274372 10-14-23 20:14:06 (Application server time) TACHE=AWRKSIG FLAG=2 (00000)
=0000 00274372 10-14-23 20:14:07 (Application server time) FINREQ - Ended query management: Query complete (00000)
=1000 00274373 10-14-23 20:14:08 (Application server time) EXEC_RQT - Query execution management: Query Activation (PROD ACCBATCH1 P BATCHCPT 1456 256418) (51000)
=0000 00274373 10-14-23 20:14:08 (Application server time) TACHE=ACCBATCH1 FLAG=2 (00000)
=0000 00274373 10-14-23 20:14:08 (Application server time) FINREQ - Ended query management: Query complete (00000)
=1000 00274374 10-14-23 20:14:10 (Application server time) EXEC_RQT - Query execution management: Query Activation (DEV ACCBATCH1 P BATCHCPT 7048 256419) (51000)
=0000 00274374 10-14-23 20:14:10 (Application server time) TACHE=ACCBATCH1 FLAG=2 (00000)
=0000 00274374 10-14-23 20:14:10 (Application server time) FINREQ - Ended query management: Query complete (00000)

<1000 00274375 11-01-23 12:25:21 (Application server time) RETARD - Delay management: Out of date time limit (PROD AWRKSIG P ) (21000)
<1000 00274376 11-01-23 12:25:23 (Application server time) RETARD - Delay management: Out of date time limit (DEV AWRKSIG P ) (21000)
<1000 00274377 11-01-23 12:25:25 (Application server time) RETARD - Delay management: Out of date time limit (PROD ACCBATCH1 P BATCHCPT) (21000)
=1000 00271438 11-01-23 12:25:27 (Application server time) EXEC_RQT - Query execution management: Query Activation (PROD DOSSVG P 8432 256881) (51000)
=0000 00271438 11-01-23 12:25:27 (Application server time) TACHE=DOSSVG FLAG=2 (00000)
=1000 00274379 11-01-23 12:25:29 (Application server time) EXEC_RQT - Query execution management: Query Activation (PROD AWRKSIG P 8788 256882) (51000)
=0000 00274379 11-01-23 12:25:29 (Application server time) TACHE=AWRKSIG FLAG=2 (00000)
=1000 00274380 11-01-23 12:25:31 (Application server time) EXEC_RQT - Query execution management: Query Activation (DEV AWRKSIG P 8012 256883) (51000)
=0000 00274380 11-01-23 12:25:31 (Application server time) TACHE=AWRKSIG FLAG=2 (00000)
=0000 00274380 11-01-23 12:25:31 (Application server time) FINREQ - Ended query management: Query complete (00000)

```

When I stop the Batch Server, it did not stop immediately but took up to 500+ seconds and session timeout the interactive session.

Since I have used up the allocated emergency time, I went into the main runtime server and killed the PID manually.

Then, I log back into Sage X3 and started back the Batch Server to continue the business process while I check for errors now.

For Context:

Sage X3 v12p33.

AWS environment. Two servers: Sage X3 Server and Database Server.

Sage X3 server (c6i.xlarge) timezone at UTC+8.

AWS RDS timezone is at UTC+0.

  • 0

    Start by reviewing the Batch Server configuration, ensure that the user's defined "Locale preference" (fr-FR) is valid and that the Locale is active.

    If the configuration is valid, change the level of batch logging. To do this change the "Batch" log value in the "Server Logs" section of the Global Setting from "Error" to either "Info" or "Debug". Remember to set it back once the issue has been resolved.

  • 0 in reply to Regard Hulsbos

    For this case, I was explicitly requested to remove all locales except ENG (en-US).

    I believe only SEED (default to fr-FR) is affected by this as new folders are set to ENG as default.

    I have prepared and set those that may default to any locale except ENG, to ENG explicitly in Recurring Task Management and Setup > Folders level.

    I have set batch's subcodes to Debug mode for the observation period of one year since I do not have a way to consistently trigger it.

    Will reply here if there was any errors triggered.

*Community Hub is the new name for Sage City