WEBGUI Messages 3100-3199

3100

INFO: Terminating wlisten process

Description

The wlisten process was terminated by a signal.

Action

If you purposely terminated wlisten by issuing an operating system command (such as the UNIX kill(1) command), then no action is required. Otherwise, you must determine the reason why a signal was sent to the wlisten process. In some operating systems processes are killed when the system is critically low on resources.

3102

INFO: wlisten starting

Description

This message signals the start of the wlisten process.

Action

No action required.

3103

ERROR: Unable to determine license level

Description

An error occurred while retrieving the current license attributes.

Action

Check the log for prior messages indicating the cause of the problem. Normally, it means that the product has not been licensed properly.

3105

ERROR: wlisten could not initialize network

Description

An error occurred while initializing the network provider.

Action

Make sure that your network stack is correctly installed and configured. Use network administration tools to determine the cause of the initialization problem.

See Also

wlisten(1)

3106

ERROR: wlisten TUXDIR is not set and no ini file was specified, exiting

Description

The wlisten process could not determine the location of the Web GUI initialization file because you did not specify the -i option. It attempted to find the default initialization file (which is $TUXDIR/udataobj/webgui/webgui.ini) but could not because the TUXDIR variable was not set in the environment.

Action

Either use the -i option to specify the initialization file, or set TUXDIR in the environment before running wlisten.

See Also

wlisten(1)

3107

ERROR: wlisten found no address in initialization file, exiting

Description

The wlisten process needs to know a network address on which it should listen for incoming connections. It gets this address from the Web GUI initialization file. The NADDR parameter in the initialization file holds the listening address. However, no NADDR parameter could be found.

Action

Set the NADDR parameter in the Web GUI initialization file before running wlisten.

See Also

wlisten(1)

3108

WARN: Network device does not exist

Description

The wlisten process was not able to find a network device in the initialization file. This is not a problem on some operating systems where sockets are used, but this is a problem if TLI is being used.

Action

If you are using sockets and wlisten seems to work, then no action is required. Otherwise, set the appropriate network device (e.g. /dev/tcp or whatever is required by your operating system) in the Web GUI initialization file DEVICE parameter.

See Also

wlisten(1)

3109

ERROR: Could not establish listening endpoint

Description

The wlisten process was unable to open the network address specified by the NADDR parameter of the Web GUI initialization file. This could be because that address is already in use by another process, or the address could be incorrect.

Action

Make sure no other system service is using the address specified by NADDR. Check to see if another wlisten process is already running (and thus using the address). Check the format of the address to make sure it is correct.

See Also

wlisten(1)

3110

ERROR: Could not establish accept endpoint

Description

The wlisten process was unable to accept a connection. This could be because of a lack of available network virtual circuits.

Action

Check your network configuration to ensure there are a sufficient number of available system sockets (or other network circuits if you are not using sockets).

See Also

wlisten(1)

3111

ERROR: Could not accept new connection

Description

The wlisten process was unable to accept an incoming connection request.

Action

This could be a network resource problem, check you networking configuration.

See Also

wlisten(1)

3112

INFO: Starting server (info)

Description

The wlisten process is starting a wgated server process to handle a Web GUI connection.

Action

No action required.

See Also

wlisten(1)

3113

ERROR: could not start wgated process, errno=errno

Description

The wlisten process was unable to start a wgated process to handle an incoming Web GUI connection.

Action

There are many possible reasons for this, including a lack of system resources that makes it impossible to start a new process, or a corruption or mis-installation of the Web GUI wgated executable, or other system-dependent problems. Check your system configuration to ensure you are not near the system limit for processes, and make sure the Web GUI is properly installed.

See Also

wlisten(1)

3114

ERROR: _gp_new_task info Error # errno

Description

The wlisten process was unable to start a wgated process to handle an incoming Web GUI connection.

Action

There are many possible reasons for this, including a lack of system resources that makes it impossible to start a new process, or a corruption or mis-installation of the Web GUI wgated executable, or other system-dependent problems. Check your system configuration to ensure you are not near the system limit for processes, and make sure the Web GUI is properly installed.

See Also

wlisten(1)

3115

ERROR: Failure to get job id of spawned child, error code is: code

Description

On the AS/400 platform, the wlisten process failed to retrieve the job id of the wgated process which handles communications with the Java management console.

Action

Check error string given at the end of this error message for further information on what caused the problem.

See Also

wlisten(1)

3116

ERROR: Failure passing socket to child process, error code is: code

Description

On the AS/400, there was an error when wlisten attempted to pass a file descriptor to a newly created wgated process.

Action

Check the error string at the end of the log message to determine the possible reason for the failure.

See Also

wlisten(1)

3117

ERROR: _e_proc_new_task val Error # val

Description

Attempt to create a new process for wgated failed.

Action

Check the error indicated in the log message to determine the possible reason for the failure.