User's Manual

Fluid Cache For DAS Fails To Start

Probable Cause Port conflict.

Solution If you have a did not start error for a Mongoose server, check for a port conflict. If

another service or application is trying to use the default fluid_cache service port,

change ports to end the conflict. For more information, see the topic “Fluid Cache For DAS Port

Conflict Daemon Error” in this section.

Fluid Cache For DAS Port Conflict Daemon Error

Probable Cause

• fldc_cfm is not running and the Mongoose server fails to start.

• DWS login failed. Openwsman is not running.

Solution

• If fldc_cfm is not running, query the system to see which ports are in use by running

the command:

netstat --listening --numeric --tcp. This command

displays the sockets all services are listening on.

– If there is a socket listening on port 6772, set fldc-https to an unassigned

port.

– If there is a socket listening on port 8080, set fldc-http to an unassigned

port.

– If there is a socket listening on port 7449, find the service using that socket and

configure that service to use a different unassigned port.

• For Openwsman not running, query the system to see which ports are in use by running

the command: netstat --listening --numeric --tcp. This command

displays the sockets all services are listening on. If there is a socket listening on port

443, find the service using that socket and configure that service to use a different

unassigned port.

Fluid Cache Service For DAS Has Stopped

Probable Cause After starting, the service may shut down and the fluid_cache service is no longer

displayed.

Solution

1. To determine if Fluid Cache has stopped, run the command: fldc --status

2. If status returns a cannot connect message, restart fluid_cache service. Run

the command: service fluid_cache start

PCIe SSD Cannot Be Added As A Cache Device

Probable Cause

• The first PCIe SSD cannot be added.

• The second, third, or fourth PCIe SSD cannot be added.

• A PCIe SSD exists, but cannot be added to the cache.