...
When job stuck after system restart, you may need to restart the
Solution
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 | ||||
|---|---|---|---|---|
| ||||
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 | ||||
|---|---|---|---|---|
| ||||
pm2 stop ss-nav-jira-JIRA |
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, |
...
Related articles
| Content by Label | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Page properties | ||
|---|---|---|
| ||
|