Messages related to system control (0001 to 1000)

The daemon indicated by %s completed initialization processing, and started reception for the service.

--

In accordance with the instruction for a normal end by the termination command, the daemon indicated by %s successfully ended reception of the service.

--

In accordance with the instruction for a forced termination by the termination command, the daemon indicated by %s stopped processing, and ended reception for the service. For details about termination codes, see Exit statuses of the daemon.

--

An error occurred in the daemon indicated by %s and the processing could not continue. The service ended abnormally. For details about termination codes, see Exit statuses of the daemon.

See Exit statuses of the daemon, and take measures to resolve the problem indicated by the termination code.

Due to the reason (%s), the signal (%s) could not be registered.

Remove the cause that is indicated by the reason.

The maximum number of threads that can be generated in one process is not defined in the operating system. The value indicated in %d is set as the upper limit, and processing continues.

The measure to resolve the problem differs depending on the type of operating system. For more details, see the manual of each operating system.

An attempt to acquire the value of the upper limit for file descriptors failed.

An attempt to acquire the limit value of the operating system failed. Confirm that the product supports the operating system.

Due to the reason (%s), the process could not be generated.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to start the program indicated by the path (%s) failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to start the program indicated by the path (%s) failed.

Remove the cause that is indicated by the reason.

The HULFT-HUB Server program (program-name output to the header part of this trace) started the daemon (%s).

--

Initialization processing of the daemon (%s) was completed, and the completion report was sent to the PROXY daemon.

--

The daemon (%s) acknowledged an instruction for a normal end by the termination command.

--

The daemon (%s) acknowledged an instruction for a forced termination by the termination command.

--

An error occurred in the wait processing from HULFT, HULFT-HUB Manager, or HULFT-HUB Server.

Possible causes include a socket abnormality or an operating system restriction. Remove the cause that is indicated by the reason.

Replacement of the process of the daemon (%s) was completed in the Relay/Multicasting processing.

--

The process of the daemon (%s) was replaced in the Relay/Multicasting processing.

--

HULFT-HUB Server cannot be started because the Trial period expired.

Upgrade the program to the product version.

A HULFT-HUB Server program that uses the System Environment Settings file ('hulhub.conf') created in the Environment Settings directory (%s) is already running.

When starting multiple HULFT-HUB Server programs, create the System Environment Settings file in an Environment Settings directory other than the Environment Settings directory (%s).

A HULFT-HUB Server program that uses the same service name on the same host is already running.

When starting multiple HULFT-HUB Server programs, change the service name to a name other than (%s), and then start them.

Initialization processing of the daemon (%s) was completed, and the completion report was sent to the PROXY daemon.

--

A user command was entered, but there was no response within the time limit (%d (sec)).

The response might be being transferred if the termination command was executed in the termination synchronization mode. Check the environment.

The program (%s) cannot be executed because HULFT-HUB Server is not running.

Start HULFT-HUB Server and execute the program (%s).

An attempt to acquire a mutex resource failed.

A possible cause is that a limit of the operating system was reached. Remove the cause indicated by the details (%s).

After waiting for the specified time (%d sec) because the target resource was locked by another process, the lock was not released.

Wait a while, and then retry.

A system error occurred.

A possible cause is an abnormality in the operating system. Remove the cause indicated by the details (%s).

A connection request from HULFT-HUB client was acknowledged.

--

HULFT-HUB Server will transfer (relay) files in response to the request from the connection-source host.

--

HULFT-HUB Server will transfer (multicast) files in response to the request from the connection-source host. This HULFT-HUB Server is a multicast point.

--

HULFT-HUB Server will relay a send request or resend request in response to the request from the connection-source host.

--

HULFT-HUB Server will relay the request from HULFT-HUB Manager or a neighboring server.

--

A request from HULFT-HUB Manager or a neighboring server was acknowledged, and passed to the Manager daemon.

--

HULFT-HUB Server could not finish because the termination command was executed by a user other than the executor.

Enter the termination command by using the ID of the user who started HULFT-HUB Server or by the root user.

Stop processing for HULFT-HUB Server was executed from the host indicated by the IP address (%s).

Execute stop processing on the host on which HULFT-HUB Server started.

An attempt to acquire the MAC address failed.

Possible causes are an abnormality in the socket or a restriction imposed by the operating system. Check the environment.

The Installation Information file used when HULFT-HUB Server was installed is corrupted.

Install HULFT-HUB Server again, and then restart it.

Stop processing by the termination command or by a command for clustering functionality was started.

--

Stop processing by the termination command or by a command for clustering functionality successfully finished.

--

An abnormality occurred in the termination command or in a command for clustering functionality.

Remove the cause of the problem.

The connection request could not be acknowledged because the version of HULFT-HUB Manager is not supported by HULFT-HUB Server.

Use HULFT-HUB Manager whose version is supported by HULFT-HUB Server.

An attempt to initialize the output environment for operation logs failed.

A possible cause is a lack of access permissions for a file or directory. Ensure that the executor of HULFT-HUB Server has required permissions, and restart HULFT-HUB Server.

An attempt to output the operation log failed.

A possible cause is that the specified directory does not exist or that the executor does not have necessary permissions. Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to generate the thread failed.

Remove the cause that is indicated by the reason.

A shutdown was detected.

--

Due to the reason (%s), an attempt to wait for the object failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to generate the object failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to open the object failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to generate a service thread failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to register a service handler failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to send a service status notification failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to acquire a process end status failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to open a process failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to acquire a thread end status failed.

Remove the cause that is indicated by the reason.

An unexpected stop of the service (%s) was detected.

Check the messages output before and after this message, and remove the cause of the error.

An unexpected stop of the service (%s) was detected.

Check the messages output before and after this message, and remove the cause of the error.

Due to the reason (%s), an attempt to duplicate a handle failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to set an event object failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to reset an event object failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to connect to a service control manager failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to register a service failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to modify the settings of a service failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to open a service failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to delete a service failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to create the registry key failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to set data for the registry entry failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to delete the registry key failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to acquire a service configuration information failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to acquire a service configuration information failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to acquire service list information failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to acquire a process list failed.

Remove the cause that is indicated by the reason.

The command indicated by %s completed the initialization processing.

--

The command indicated by %s ended successfully.

--

The command indicated by %s terminated unsuccessfully. For details about termination codes, see the description of the corresponding command in HULFT-HUB Server Utilities.

See the description of the corresponding command in HULFT-HUB Server Utilities, and take measures to cope with the problem corresponding to the termination code.

Due to the reason (%s), an attempt to acquire a process access token failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to acquire a privilege identifier failed.

Remove the cause that is indicated by the reason.

Due to the reason (%s), an attempt to adjust special privileges failed.

Remove the cause that is indicated by the reason.

The upper limit for the number of processes that can exist at the same time for a user is not defined in the operating system. The value indicated in %d is set as the upper limit, and processing continues.

The measure to resolve the problem differs depending on the type of operating system. For more details, see the manual of each operating system.

Because the number of file descriptors is not limited, HULFT-HUB Server will assume '%d' as the upper limit and continue the processing.

--

HULFT-HUB Server used the heartbeat check functionality for heartbeat check, but could not return the heartbeat check report because there was a daemon that did not respond.

Check the messages output before and after this message, and remove the cause of the error.