Difference between revisions of "ARS1400E"
(Initial edit - addition of ARS1400E message from CMOD.) |
|||
| Line 35: | Line 35: | ||
kill <process-id-number> <process-id-number> | kill <process-id-number> <process-id-number> | ||
And restart only one instance of the IBM CMOD arsload command. | |||
== Articles Related to this message == | == Articles Related to this message == | ||
None available. | None available. | ||
Revision as of 10:09, 25 March 2018
What was the error?
Message Number: 1400
Message Severity: Error (Corrective action is required to continue)
Message Name: ARS1400E
Message Text: Loading was unable to continue due to encountering a previously failed load of the same name that has yet to be unloaded. Failed LoadId >5301-18-0-100FAA-20160112000000-20160112000000-5306< was attempted to be loaded at approximately 2016-01-13 15:13:56
Related Errors
None.
What were you doing?
Probably loading files into Content Manager OnDemand with the arsload command, running as a daemon.
What happened?
More than one arsload daemon was launched for the same directory & Application Group -- now the two processes are 'fighting' over files.
Example
ARS1400E Loading was unable to continue due to encountering a previously failed load of the same name that has yet to be unloaded. Failed LoadId >5316-29-0-100454FAA-20161012000000-20161012000000-5318< was attempted to be loaded at approximately 2016-10-13 15:13:56
Troubleshooting
Find the Process ID numbers for the arsload processes with:
ps -ef |grep arsload
Then issue a kill command for both of the processes:
kill <process-id-number> <process-id-number>
And restart only one instance of the IBM CMOD arsload command.
Articles Related to this message
None available.