GePG Troubleshooting Guide
Process Schedule
Recon process runs daily at 04:30 AM IST.
Checks
- Check logs for
GePGandaz-db-servicesaround 4:30 AM in tz-msb-prod. - Look for errors in log collection output.
Reasons for Failure
- GePG recon succeeded but mail server was down.
- Error in account number from PGDB during recon.
Manual Recon Query
If logs show nothing, run curl for recon data. Use yesterday’s date.
curl -s http://10.137.129.86:30274/api/gepg-manual/query-recon-data/DD-MM-YY
Example
# If today is 26th Aug curl -s http://10.137.129.86:30274/api/gepg-manual/query-recon-data/25-AUG-2025
Check the payload response. If failed, inspect az-db-service and GePG logs.
TRA Troubleshooting Guide
Process Schedule
TRA process runs daily at 05:30 AM IST.
Checks
- Check logs for
GePGandflexdbin log collection.
Reasons for Failure
flexdbmight be down during TRA process.- Mail server might be down.
Manual TRA Statement Request
If the UI breaks long payloads, use a here-document so the XML stays intact. Copy exactly as-is:
curl --location 'https://10.137.129.57:44444/TRA/adhoc-statement' \
--header 'Content-Type: text/xml' \
--data '<?xml version="1.0" encoding="UTF-8"?>
<Rgs>
<Statement>
<Header>
<Sender>TARATZT0</Sender>
<Receiver>DTKETZT0</Receiver>
<MsgId>SPR20250609T161607</MsgId>
<MessageType>STATEMENTREQ</MessageType>
</Header>
<RequestSummary>
<RequestId>SPR20250609T161607</RequestId>
<CreDtTm>2025-06-09T16:16:07</CreDtTm>
<AcctNum>(account-num)</AcctNum>
<SmDt>(2025-06-16)</SmDt>
</RequestSummary>
</Statement>
<RgsSignature>Ldsgii4xERZOw4c0iBtULieuYNg6E5AMsYHNoNnlveloIcw4oyNtv1sZka+cJrEttc7SCMezTjSXBzj1gTokKelnIwWCae0cho6C4/cFusT7c6ZwWa7QhogUw2nVrlJxasGz/LoRyZwNr6fTt4/Xm4qFysmBqCXAPfRBMHUAYOi2pxHr2eQl9wNDHRwUWE/WQ5Ibus7W4KlwBBypHDd5HctD+JSpULtpA5tgwbCskVb82LLpd/VYn54ZkldxDyGCVAVsAXpP1oNrnUt/8d36xSstWq9wW8p8sxJMHQGQPAZELWz9YrFIaJ5H/de2fVvHhSL+kUdE93jZZFNcqNA52w==</RgsSignature>
</Rgs>'
XML
Note: Replace (account-num) and (2025-06-16) with actual values.