Termination status upon daemon startup

If the Send daemon, the Receive daemon, or the Observe daemon fails to start, HULFT returns an exit code other than '0.'

If HULFT detects an error after daemonizing has finished, the application returns the exit code '0.'

To detect errors after daemonizing has finished, you need to use the start synchronization command for each daemon.

Refer to Clustering Manual for more information.

1

Description:

A system error occurred.

Measure:

There may be an error in the file system, socket stream, or the operating system and so on. Check the environment.

2

Description:

An error in startup parameter.

Measure:

Check the manual and restart. This may be due to the socket buffer size exceeding the limitation of the operating system. Check the socket buffer size.

3

Description:

The daemon might have already started. In the Send daemon, opening the Send Control file (sddsendlist.dat) might have failed as well. In the Receive daemon or in the Observe daemon, other application may have used the port number that is assigned to the daemon.

Measure:

Using the ps command, check whether the Send daemon, the Receive daemon, or the Observe daemon has started.

When the daemon has stopped, using the netstat command, check whether the value specified for Command Acknowledge Port No., Receive Port No. or Observe Port No. in the System Environment Settings.

If the value is being used, change the value for Port No.

Also, the Send daemon has stopped, check the following too.

  • If the Send daemon pid file (hulsndd.pid) exists on Pid File Generation Path in the System Environment Settings, delete the file.

  • Check the access permissions for the Send Control file.

4

Description:

The process cannot start.

Measure:

There may be an error in the file system or the operating system and so on. Check the environment.

5

Description:

An error in communication socket.

Measure:

There may be error in the socket stream and so on. Check the environment.

6

Description:

Reading of the Send Control file (sddsendlist.dat) failed.

Measure:

Delete the Send Control file (sddsendlist.dat) and restart the Send daemon because there is an error in the Send Control file (sddsendlist.dat).

7

Description:

A memory error.

Measure:

Terminate other applications, and restart the daemon.

8

Description:

Opening of pipe failed.

Measure:

An error occurred in the pipe. A fifo file for communication that HULFT is using may exist on the path specified for FiFo Path (fifopath) in the System Environment Settings. When a value is not specified for FiFo Path (fifopath), a fifo file for communication that HULFT is using is created on the directory specified with HULPATH. When there is a fifo file for communication that HULFT is using, delete the file. Then, restart the HULFT system.

9

Description:

The System Environment Settings file (hulenv.conf) is invalid.

Measure:

In the contents of the System Environment Settings file (hulenv.conf), check whether a tag is unintentionally commented out, or whether a required tag is mistakenly deleted, etc.

10

Description:

A path specification error.

Measure:

A specified path name with a length of 201 bytes or more is over the limit. Set a path name with 200 bytes or less.

11

Description:

Work File Generation Path is invalid.

Measure:

Check the contents in the Work File Generation Path such as the directory and the permission.

12

Description:

A common library load error.

Measure:

Check whether the manufacturer's name at the upper left corner of Management Console is correct. In HULFT-SAN, loading of the common library required for the SAN transfer failed. Check whether or not the common library has been installed properly. 

13

Description:

An invalid startup parameter was specified for the daemon in the cluster startup synchronization command.

Measure:

Check the startup parameter that can be specified on the cluster support version in the relevant manual, and restart HULFT.

15

Description:

Failed in creating or reading a trace file.

Measure:

Check that the following files can be created or written.

  1. The file specified with the parameter -l at the time of the startup of the daemon

  2. The trace file specified in the System Environment Settings file (hulenv.conf)

18

Description:

The service period of the HULFT trial version has expired.

Measure:

Use the Product version.

19

Description:

Access to the System Environment Settings file (hulenv.conf) failed.

Measure:

Check whether or not the access to the System Environment Settings file (hulenv.conf) is permitted. Also, check whether there is an error or not in the specification of HULPATH.

21

Description:

The daemon was forcibly terminated.

Measure:

Forced termination of the daemon was executed. Restart the HULFT daemon.

22

Description:

The valid term of the Fixed Term License has expired.

Measure:

Check the valid term of the Fixed Term License.

26

Description:

An error occurred during character code conversion upon starting the daemon.

Measure:

Make sure that the set value of Code Set for Transfer (cs4trnsfr) in the System Environment Settings is correct. Further, check whether the environment variables 'HULPATH' and 'HULEXEP' are set correctly.

27

Description:

Forced Strong Key mode cannot be enabled.

Measure:

HULFT Cipher Option (AES) is needed. Check the following:

  1. Cipher Option (AES) is installed

  2. Encryption Scheme (ciphertype) is set to "Other Encryption Scheme"