The node does not have the service role.
Enable the service role on the node, and then enable the service process running on that node.
Another process running on the machine is using the HTTP port number assigned to the service process.
On the
Processes
view for the Data Integration Service, enter a unique HTTP port number for the service process. Then, enable the service process running on that node.

Job log accessible from the
Monitor
tab.
Includes log events about how the DTM instance runs the job.
Data Integration Service log accessible from the
Service
view of the
Logs
tab.
Includes log events about service configuration, processing, and failures.

Job log accessible from the
Monitor
tab.
Includes log events about how the DTM instance runs the job.
Data Integration Service log accessible from the
Service
view of the
Logs
tab.
Includes log events about service configuration, processing, and failures. The Data Integration Service log includes the following message which indicates the host name and port number of the master compute node:
INFO: [GRIDCAL_0204] The Integration Service [<MyDISName>] elected a new master compute node [<HostName>:<PortNumber>].
Master compute node log accessible in the
cadi_services_0.log
file located in the log directory configured for the master compute node.
Includes log events written by the Service Manager on the master compute node about managing the grid of compute nodes and orchestrating worker service process requests. The master compute node logs are not accessible from the Administrator tool.
Resource Manager Service log accessible from the
Service
view of the
Logs
tab.
Includes log events about service configuration and processing and about nodes with the compute role that register with the service.
Container management log accessible from the
Domain
view of the
Logs
tab. Select
Container Management
for the category.
Includes log events about how the Service Manager manages containers on nodes with the compute role.

The mapping is still running.
When a DTM process finishes running a mapping, it sends the log file to the master Data Integration Service process. No DTM messages appear in the mapping log until the entire mapping is complete. To resolve the issue, you can wait until the mapping completes before accessing the log. Or, you can find the log file that the DTM process temporarily writes on the worker compute node.
The mapping has completed, but the DTM process failed to send the complete log file to the master Data Integration Service process.
The DTM process might fail to send the complete DTM log because of a network error or because the worker compute node unexpectedly shut down. The DTM process sends the log file to the Data Integration Service process in multiple sections. The DTM section of the log begins and ends with the following lines:
###
### <MyWorkerComputeNodeName>
###

### Start Grid Task [gtid-1443479776986-1-79777626-99] Segment [s0] Tasklet [t-0] Attempt [1]

....

### End Grid Task [gtid-1443479776986-1-79777626-99] Segment [s0] Tasklet [t-0] Attempt [1]
If these lines are not included in the mapping log or if the beginning line is included but not the ending line, then the DTM process failed to send the complete log file. To resolve the issue, you can find the DTM log files written to the following directory on the node where the master Data Integration Service process runs:
<Informatica installation directory>/logs/<node name>/services/DataIntegrationService/disLogs/logConsolidation/<mappingName>_<jobID>_<timestamp> 
If the job ID folder is empty, find the log file that the DTM process temporarily writes on the worker compute node.

INFO: [GCL_5] The grid task [gtid-1443479776986-1-79777626-99] cluster logs can be found at [./1443479776986/taskletlogs/gtid-1443479776986-1-79777626-99].

<Informatica installation directory>/logs/<node name>/dtmLogs/