...
When job stuck after system restart, you may need to restart the
Solution
Execute the following command in SSH to etechplus.ddns.net (you need to be in Bizspoke internal network)
Panel |
---|
bgColor | #fff |
---|
title | SSH command |
---|
|
pm2 stop ss-nav-jira-JIRA pm2 stop ss-nav-jira-NAV pm2 start ss-nav-jira-JIRA pm2 start ss-nav-jira-NAV |
If job has
...
continued but old record didn't resume
Delete record from ss_order_call_date, check for the time gap between records, delete the record from the largest gap to latest (for example if 2021-9-25 07:15:02 , the next timestamp is 2021-9-26 00:00:00, which is suppose each time gap within 5mins)
Panel |
---|
bgColor | #fff |
---|
title | SQL Command example |
---|
|
delete from ss_order_call_date where last_call_date > '2021-09-25 07:15:02' |
Execute the following command in SSH to etechplus.ddns.net (you need to be in Bizspoke internal network)
Panel |
---|
bgColor | #fff |
---|
title | SSH command |
---|
|
pm2 stop ss-nav-jira-JIRA pm2 stop ss-nav-jira-NAV pm2 start ss-nav-jira-JIRA pm2 start ss-nav-jira-NAV |
If some records were not synced. It is because jira_status is marked to 'U' before being created. The status needs to be mark back to 'N' in order to sync.
Execute the following in MYSQL db in etechplus.ddns.net >> ss_jira.
Panel |
---|
|
ALTER sol, (ss_order_line sol LEFT JOIN ss_order_header soh on sol.Order_Id = soh.Order_Id) SET sol.jira_status = 'N' WHERE soh.Order_Date > '2021-12-16' AND ISNULL(sol.jira_key) |
Related articles
Content by Label |
---|
showLabels | false |
---|
max | 5 |
---|
spaces | WSKZAM80XQU4CZEL |
---|
showSpace | false |
---|
sort | modified |
---|
reverse | true |
---|
type | page |
---|
cql | label = "restart" and type = "page" and space = "WSKZAM80XQU4CZEL" |
---|
labels | restart |
---|
|
...