App-server Error Message Codes
Twitter
LinkedIn
Facebook
EmailApp-server Error Message Codes
The following error message codes may appear on the app-server log. Use the following message code references and the corresponding reasons and actions to help troubleshoot issues.
App-server informational messages
ZWED0020I
Registering at discoveryUrl
Reason:
The app-server is registering its existence to the API ML discovery server, because components.app-server.node.mediationLayer.enabled=true is set in the zowe configuration.
Action:
No action required.
ZWED0021I
Eureka Client Registered from ipAddress. Available at discoveryUrl.
Reason:
The registration attempt from ZWED0020I has succeeded. The server is known to the API ML discovery server from the address ipAddress.
Action:
No action required.
ZWED0022I
Fork worker workerId
Reason:
A new app-server worker process is starting. Workers are redundant execution contexts of the server and increase throughput and latency of requests when the server has a lot of concurrent client requests. Workers are started and stopped according to current server load and the minimum and maximum worker limits defined in environment variables ZLUX_MIN_WORKERS and ZLUX_MAX_WORKERS.
Action:
No action required.
ZWED0023I
Restart worker workerId
Reason:
An existing app-server worker process has exited with a status code that indicates it should be restarted rather than permenantly stopped.
Action:
Review the preceeding log messages as worker restart may be due to a caught error.
ZWED0024I
Keys=workerIds
Reason:
The server lists the worker IDs right before all workers are about to be reloaded.
Action:
No action required.
ZWED0025I
Killing worker pid=processId
Reason:
The server just issued the SIGTERM unix signal to the worker with the process ID listed. This is an expected action when reloading all workers of the server.
Action:
No action required.
ZWED0026I
Fork quantity workers.
Reason:
The server is starting up quantity new workers. Workers are redundant execution contexts of the server and increase throughput and latency of requests when the server has a lot of concurrent client requests. This message appears at startup and the quantity is determined by the environment variables ZLUX_MIN_WORKERS and ZLUX_MAX_WORKERS.
Action:
No action required.
ZWED0027I
Close worker workerId
Reason:
The server is removing an existing worker due to lack of recent client activity. Workers are added and removed according to average load of the server. Workers are redundant execution contexts of the server and increase throughput and latency of requests when the server has a lot of concurrent client requests. Workers may be removed down to the minimum count as defined by the environment variable ZLUX_MIN_WORKERS.
Action:
No action required.
ZWED0028I
Master processId is running.
Reason:
The server has started up and is printing its unix process ID in case the user needs to know for analysis or troubleshooting.
Action:
No action required.
ZWED0029I
Worker workerId pid processId
Reason:
A worker has started and is listing its ID and unix process ID in case the user needs to know for analysis or troubleshooting.
Action:
No action required.
ZWED0031I
Server is ready at ipAddress, Plugins successfully loaded: percentage% (successful/total)
Reason:
The server is ready to accept client requests. It can be found at the ipAddress listed, and you can tell if it has loaded all plugins successfully by the percentage listed.
Action:
If the percentage is less than expected, review the log for messages with IDs ZWED0159W or ZWED0027W. Those messages will tell you which plugins failed, and you can search for their plugin ID within the log to find out the reason they failed to load.
ZWED0033I
The http port given to the APIML is: tcpPort The https port given to the APIML is: tcpPort The zlux-apiml config are: jsonConfig
Reason:
The server lists the properties that will be used to connect to the APIML Discovery server to help with troubleshooting.
Action:
No action required.
ZWED0036I
Plugin pluginId will serve static files from filePath
Reason:
The plugin pluginId was loaded which has a webContent section defined in its pluginDefinition.json file. The server will serve the read-only content from the filePath.
Action:
No action required.
ZWED0037I
pluginId: found proxied service serviceName
Reason:
When the server was loading the plugin pluginId, it found that the plugin contains a service named serviceName of type "service".
Action:
No action required.
ZWED0038I
pluginId: importing service sourceServiceName from sourcePluginId as serviceName
Reason:
When the server was loading the plugin pluginId, it found that the plugin contains a service named serviceName of type "import". It then resolved the import to the service sourceServiceName from plugin sourcePluginId.
Action:
No action required.
ZWED0039I
pluginId: found router serviceName
Reason:
When the server was loading the plugin pluginId, it found that the plugin contains a service named serviceName of type "router".
Action:
No action required.
ZWED0040I
pluginId: found legacy node service serviceName
Reason:
When the server was loading the plugin pluginId, it found that the plugin contains a service named serviceName of type "nodeService".
Action:
This type of service is deprecated and may not work on a future version of Zowe, so you should consider getting an upgraded version of the plugin that instead uses a service of an undeprecated type.
ZWED0041I
pluginId: found external service serviceName
Reason:
When the server was loading the plugin pluginId, it found that the plugin contains a service named serviceName of type "external".
Action:
No action required.
ZWED0042I
pluginId: found serviceType service serviceName
Reason:
When the server was loading the plugin pluginId, it found that the plugin contains a service named serviceName of type "serviceType".
Action:
No action required.
ZWED0043I
Plugin pluginId is not requested skipping without error
Reason:
When the server was loading the "nodeAuthentication" type plugin pluginId, it determined that the plugin only handles security actions for a category that was not requested by the server configuration or any plugins. The plugin was skipped because it was not required.
Action:
No action required unless you need the plugin to be used. If you need the plugin, you can set an authentication category it implements as the default by configuration property components.app-server.dataserviceAuthentication.defaultAuthentication, or within a plugin's security configuration.
ZWED0044I
Processing plugin reference filePath...
Reason:
The server is checking if the plugin definition file filePath exists and will attempt to load it.
Action:
No action required.
ZWED0045I
Reading plugins dir pluginsDirectory
Reason:
The server is scanning the directory pluginsDirectory as specified by the server configuration property components.app-server.pluginsDir so that it can locate each plugin in the instance.
Action:
No action required.
ZWED0046I
Adding dynamic plugin pluginIdentifier
Reason:
The server has added the plugin with pluginIdentifier to its bootstrapped list of plugins. It also emits a pluginAdded event.
Action:
No action required. If you need it, you may check the list of plugins on the Desktop to see if the plugin was added successfully.
ZWED0047I
Reason:
A child process from path has received data of data - usually done interally by ProcessManager.
Action:
No action required.
ZWED0048I
[Path= path] exited, code: code
Reason:
A process from path has exited with a return code.
Action:
No action required.
ZWED0049I
Stopping managers
Reason:
Begins ending all child processes.
Action:
No action required.
ZWED0050I
Server shutting down, received signal=signal
Reason:
Tells server to shutdown after receiving signal by ending all child processes and then performing cleanup.
Action:
No action required.
ZWED0052I
Deleting plugin due to request, id pluginIdentifier, path path
Reason:
Notifies that the server is removing a plugin with pluginIdentifier located in path.
Action:
No action required. Optionally, you could verify that the plugin was deleted using following options:
- doing a GET call to the list of the plugins, OR
- viewing the status code of the REST request if plugin was deleted by the network request.
ZWED0053I
Setting up type proxy (pluginIdentifier:serviceName) to destination=destination
Reason:
Making an external proxy of type (HTTP or HTTPS) for pluginIdentifier:serviceName at the destination.
Action:
No action required.
ZWED0054I
Installing root service at url
Reason:
Attempting to install new root service at url.
Action:
No action required.
ZWED0055I
Installing root service proxy at url
Reason:
Attempting to install new root service proxy at url.
Action:
No action required.
ZWED0056I
pluginIdentifier: installing websocket service
Reason:
Attempting to install new websocket service for pluginIdentifier.
Action:
No action required.
ZWED0059I
Found connection info for pluginIdentifier:service=info
Reason:
Connection info for pluginIdentifier:service was found as info.
Action:
No action required.
ZWED0062I
pluginIdentifier: installing router at url
Reason:
For pluginIdentifier, the server is installing new router at url.
Action:
No action required.
ZWED0064I
pluginIdentifier: installing import sourcePlugin:name at url
Reason:
For pluginIdentifier, the server is instaling import from sourcePlugin with name at url.
Action:
No action required.
ZWED0066I
pluginIdentifier: serving static files at url
Reason:
For pluginIdentifier, the server is serving static files and assets at url.
Action:
No action required.
ZWED0067I
pluginIdentifier: serving library files at url
Reason:
For pluginIdentifier, the server is serving libary files at url.
Action:
No action required.
ZWED0070I
User=user (pluginId): Session authCapability successful. Plugin response: httpResponse
Reason:
An authentication plugin ran successfully and received a valid HTTP response.
Action:
No action required.
ZWED0072I
Using Certificate: stringArray
Reason:
The app server has successfully loaded a certificate and added it to the certificates array.
Action:
No action required.
ZWED0086I
tomcatPID closed, code=returnCode
Reason:
A running tomcat process with PID tomcatPID was cloesd.
Action:
Refer to return code.
ZWED0087I
tomcatPID exited, code=returnCode
Reason:
A running tomcat process with PID tomcatPID was exited.
Action:
Refer to return code.
ZWED0090I
tomcatPID closed, code=returnCode
Reason:
A running tomcat process with PID tomcatPID was cloesd.
Action:
Refer to return code.
ZWED0091I
tomcatPID exited, code=returnCode
Reason:
A running tomcat process with PID tomcatPID was exited.
Action:
Refer to return code.
ZWED0092I
Tomcat Manager ID=manager id stopping
Reason:
It specifies that Apache Tomcat Host Manager is stopping manager id.
Action:
No action required.
ZWED0093I
Tomcat Manager ID=manager id cleanup successful
Reason:
It specifies that Apache Tomcat Host Manager successfully cleaned up the manager id.
Action:
No action required.
ZWED0094I
Extracted war to destination path
Reason:
It specifies that it extracted the WAR directory successfully to the destination path.
Action:
No action required.
ZWED0095I
Making junction from extracted war to appbase
Reason:
A junction link is a sort of subset or a variation of a symbolic link. It creates a junction link between extracted war directory to appbase directory.
Action:
No action required.
ZWED0096I
Making symlink from extracted war to appbase
Reason:
It creates a symbolic link between extracted war directory to appbase directory.
Action:
No action required.
ZWED0109I
Registering App (ID=plugin identifier) with App Server
Reason: The registration attempt from ZWED0109I has succeeded. Before the server starts, it registers all the plugin identifier with the App server and installs them.
Action:
No action required.
ZWED0110I
App plugin identifier installed to appdir and registered with App Server
Reason:
App plugin identifier installed to appdir and registered with App Server successfully.
Action:
No action required.
ZWED0111I
Authentication plugin plugin identifier added to category authentication category
Reason:
Auth plugin plugin identifier is being registered as a part of authentication category.
Action:
No action required.
ZWED0112I
Auth enabled=false. Auth passthrough.
Reason:
This message alerts you whenever an authentication handler is requested but the dataservice has authentication disabled via configuration. This is not the default behavior of Zowe but a user may have configured it for a dataservice or a plugin may have shipped with this configuration.
Action:
Review dataservice configuration to determine if this is intentional and desired. Some dataservices do not require authentication, while others should have it.
ZWED0114I
Adding plugin remotely
Reason:
A new plugin is detected and is being added.
Action:
No action required.
ZWED0115I
Skip child processes spawning on worker workerId childProcessPath
Reason: The process listed as childProcessPath was not spawned under the specified worker because it was listed as being a process that should only be started once. Some child processes should be started per-worker for redundancy, while others that need exclusive access to a resource such as a network port are specified with the property childProcess.once, and are skipped on all but one worker. The other workers print this message to indicate this behavior.
Action:
No action required.
ZWED0116I
The LOCATIONS are serverModuleLocation and clientModuleLocation
Reason:
The server has set the location serverModuleLocation and clientModuleLocation.
Action:
No action required.
ZWED0117I
The fileLocation is lib
Reason:
Location of files will be in lib directory.
Action:
No action required.
ZWED0118I
The NODE_PATH is NODE_PATH from environment variable.
Reason: The server recognizes the location of Node as NODE_PATH from environment variable.
Action:
No action required.
ZWED0119I
Plugin plugin identifier will serve library data from directory dir location
Reason:
For plugins with type 'library', plugin plugin identifier has been registered and will be serving library data from dir location
Action:
No action required.
ZWED0120I
Auth plugin plugin identifier: loading auth handler module app server
Reason: An auth category was requested as the default in the server configuration, or requested by a particular plugin, and because the auth plugin pluginId handles this category, it is being loaded by the app-server.
Action:
No action required.
ZWED0124I
Plugin plugin identifier at path=plugin location loaded.
Reason: All the plugin identifier will be loaded at plugins directory at path. Plugins will be available in plugin location.
Action:
No action required.
ZWED0125I
Plugin plugin identifier not loaded
Reason: A plugin object was not returned in the makePlugin() call of the app-server, and therefore the app-server did not load this plugin. The plugin will not be available in the server.
Action:
Check the log for references to pluginId to see other messages that indicate the cause
ZWED0129I
(HTTP or HTTPS) Listening on ip address:port
Reason: type (HTTP or HTTPS) Listening on ip address:port.
Action:
No action required.
ZWED0130I
(HTTP or HTTPS) About to start listening on app-server port
Reason: About to start listening on app-server port.
Action:
No action required.
ZWED0154I
Following link: dependency: dependency importer
Reason:
Following the link formed by the dependency and the dependency importer in the graph.
Action:
No action required.
ZWED0158I
*** pluginsSorted:
Reason:
The graph with the sorted plugins.
Action:
No action required.
ZWED0159I
*** rejects:
Reason:
Removing the plugins with the broken dependencies from the graph.
Action:
No action required.
ZWED0160I
Dep.valid:
Reason:
Checking if the dependency is valid.
Action:
No action required.
ZWED0205I
User=user (pluginId): User logout
Reason:
This message prints when the user logs out of the Zowe Desktop. Logout is being handled by the pluginId plugin.
Action:
If logout was intentional, message can be safely ignored. If logout was unintentional, keep in mind the Desktop logs out after inactivity. Incorrect logout behavior can be troubleshooted with the authentication plugin.
ZWED0211I
The number of processors is: count
Reason:
Lists the count of CPU cores on the system hosting the App server.
Action:
No action required.
ZWED0212I
Environmental variable ZLUX_MIN_WORKERS was not a valid number therefore count will be used as the minimum workers
Reason:
ZLUX_MIN_WORKERS environment variable is not valid, so the minimum number of workers as part of the cluster will be count
Action:
By default, the App server runs in a cluster. You can specify minimum number of cluster workers.
ZWED0213I
Environmental variable ZLUX_MAX_WORKERS was not a valid number therefore count will be used as the maximum workers.
Reason:
ZLUX_MAX_WORKERS environment variable is not valid, so the maximum number of workers as part of the cluster will be count.
Action:
By default, the App server runs in a cluster. You can specify maximum number of cluster workers.
ZWED0214I
Read directory: found plugin id = identifier, type = type
Reason:
Reading in directory, found a plugin with identifier of type
Action:
No action required.
ZWED0287I
JarMgr with id=id invoked to startup with config=object
Reason:
JarManager id has been started with the configuration object
Action:
No action required.
ZWED0290I
Plugin (pluginId) loaded. Version: pluginVersion. Successful: overallSuccess% (pluginsLoaded/pluginsTotal) Attempted: pluginsAttempted% (attemptedCount/pluginsTotal)
Reason:
Plugin with pluginId loaded, with version pluginVersion. The server attempted to load a total of pluginsTotal with pluginsLoaded plugins already successfully loaded.
Action:
No action Required.
ZWED0292I
Plugin identifier loaded. Version: pluginVersion.
Reason:
Plugin identifier loaded successfully and the plugin version for the same is pluginVersion.
Action:
No action Required.
ZWED0294I
Successfully loaded recognizers length recognizers for appId into config
Reason:
Successfully loaded recognizers length for appId into config at path workspace/app-server/ZLUX/pluginStorage/org.zowe.zlux.ng2desktop/.
Action:
No action Required.
ZWED0295I
Successfully loaded actions length actions for appId into config
Reason:
Successfully loaded actions length for appId into config at path workspace/app-server/ZLUX/pluginStorage/org.zowe.zlux.ng2desktop/.
Action:
No action required.
ZWED0299I
Loading remote iframe app plugin_identifier located at remoteUrl.
Reason:
Loading remote iframe app plugin_identifier which is located at remoteUrl.
Action:
No action Required.
ZWED0300I
APIML Storage configured
Reason:
caching service/APML storage is configured
Action:
No action Required.
ZWED0301I
Found pre-existing recognizers/pre-existing actions in config for appID.
Reason:
Get pre-existing recognizers/pre-existing actions in config, if any for appID.
Action:
No action Required.
ZWED0302I
HA mode is enabled/disabled.
Reason:
High Availability mode is enabled/disabled.
Action:
No action Required.
ZWED0004W
Tomcat for ID=id not starting, no services succeeded loading
Reason:
A tomcat instance required for loading a set of java dataservices could not start, so none of the associated dataservices will be available either.
Action:
Review prior logs to determine the reason the tomcat server is not starting, and address the problem before restarting Zowe in order to access the missing dataservices.
ZWED0006W
RBAC is disabled in the configuration. All authenticated users will have access to all services. Enable RBAC in the configuration to control users' access to individual services.
Reason:
RBAC can be used to permit and reject access to each URL of the app-server individually according to security rules such as those from SAF resources. Enabling RBAC is beneficial but requires configuration first so this message is often seen.
Action:
If you wish to learn more about RBAC and enable it, read Application Framework Advanced Configuration
ZWED0007W
Dataservice authentication definition is not present in server configuration file, or malformed. Correct the configuration file before restarting the server.
Reason:
The components.app-server.dataserviceAuthentication configuration section is missing or invalid, so the server cannot continue until it is fixed. Authentication plugins for dataservices are described here
Action:
Correct your zowe configuration for this section according to the app-server schema
ZWED0008W
Error loading auth plugin pluginIdentifier: error
Reason:
The plugin could not be loaded due to an error. This plugin may be required for the server to continue, but if it is non-essential then the server will continue to run without the ability to perform authentication against that particular plugin.
Action:
Review the error to determine the way to fix the plugin before restarting Zowe.
ZWED0013W
Initializing was not complete for worker workerId
Reason:
A cluster mode worker exited before it fully initialized. Another worker will be started soon to attempt again.
Action:
If this continues to happen, you should contact support.
ZWED0014W
Error adding plugin: error
Reason:
A dynamic plugin, or a plugin added post-startup was unable to be added to the server. The server continues to run, but this plugin was not added.
Action:
Check the error and lines above in the log to determine the reason for the failure.
ZWED0015W
Error reloading workers: error
Reason:
The server was attempting to reload all workers, probably to complete a configuration change. An error occurred instead so some of the workers may not have been reloaded and could contain the old configuration.
Action:
If you were doing a configuration change, you should try again or restart the server if the error persists. You can check the error to see the reason for the issue.
ZWED0016W
Error setting override: error
Reason:
The server attempted to load a new configuration, but failed when writing the configuration update to a file.
Action:
Check the error to see the possible cause for the failure. Retry this operation but if the issue persists you should restart the server.
ZWED0017W
Duplicate plugin identifier pluginId found.
Reason:
A plugin was trying to be added to the server but it wasn't possible because another plugin with the same ID was already running within the server.
Action:
Plugin upgrades cannot be done through the add plugin operation. Instead, the server should be stopped to perform this upgrade.
ZWED0018W
Could not initialize Java manager. Java services from Apps will not be able to load stackTrace
Reason:
The Java manager is used to run Java services bundled into plugins. It could not start, so the server cannot load any Java services. Plugins that have Java services may fail to load, but the server will still run with the remaining plugins.
Action:
Check the stackTrace output to determine the reason the Java manager could not run.
ZWED0019W
Exception when setting log level for ID=logId. E: stackTrace
Reason:
Log levels listed in the configuration file are set during startup. For some reason, the level for logId could not be set, but the server will continue to run with that logger set to default verbosity.
Action:
Check the stackTrace to determine the reason why logId could not be set. Potentially the log id was an invalid name, or the log level was an invalid number.
ZWED0020W
Could not spawn childProcess: errorMessage
Reason:
The child process that was requested to run when the server started up could not run for some reason. childProcess lists the parameters requested to start the process.
Action:
Check the errorMessage to determine the reason of failure, and also verify that the information in childProcess is valid.
ZWED0021W
Missing one or more parameters required to run. The server requires either HTTP or HTTPS. HTTP Port given: httpPort. HTTPS Port given: httpsPort HTTPS requires either a PFX file or Key & Certificate files. Given PFX: pfx Given Key: key Given Certificate: certificate config was: configuration All but host server and config file parameters should be defined within the config file in JSON format.
Reason:
The server could not start because the configuration was not valid. When the server's HTTPS section is specified, httpsPort must be a valid TCP port number and you must have a key and certificate. If the HTTPS section is not specified, the HTTP section must be specified and httpPort must be a valid TCP port number.
Action:
Review the configuration to see if there are corrections to be made before restarting the server.
ZWED0027W
Plugin (pluginId) loading failed. Version: versionNumber. Message: "errorMessage" Successful: percentSuccess% (pluginsLoaded/pluginsTotal) Attempted: percentAttempted% (pluginsAttempted/pluginsTotal)
Reason:
An error prevented the plugin pluginId from loading. Other plugins will still be attempted to be loaded, until percentAttempted reaches 100%. The server will run if all auth plugins needed have successfully loaded.
Action:
Review errorMessage to see if there is something you can do to fix the error. You may need to contact the plugin developer to find a solution. If you do not need this plugin, it is OK to continue.
ZWED0028W
Encountered parse exception while reading filename
Reason:
The server cannot read the JSON file filename. This might be a configuration file or a plugin file. In either case, the server may not be able to run or may run with less plugins than desired.
Action:
Review the file listed in filename. Check if it is in the right encoding for your platform. Tagging the file according to its encoding is recommended for z/OS. Also check if the file is valid JSON. The file may have a missing or extra comma, or missing quotes or brackets.
ZWED0029W
Authentication plugin was found which was not requested in the server configuration file's dataserviceAuthentication object. Skipping load of this plugin
Reason:
The server will attempt to load every plugin given to it in the plugins directory. Authentication plugins are only needed if a plugin requests them or it implements the default authentication category. Because the server did not find a user of this plugin, it was not loaded.
Action:
No action is needed unless you believe that this plugin needed to be loaded. If so, check for plugins that require it to determine if there is missing or incorrect auth configuration.
ZWED0030W
location points to an invalid plugin definition, skipping
Reason:
The file specified at location is not valid according to the pluginDefinition schema, so it cannot be loaded. The server will still start without the plugin if possible.
Action:
Correct the pluginDefinition.json file of the plugin to load the plugin on next server restart, or remove the plugin if not needed.
ZWED0032W
Failed to load filename
Reason:
The plugin definition located at filename could not be read, so the plugin that referred to this cannot be loaded. The server may still run without the plugin if possible.
Action:
Check if the file exists and is readable to the user that is running the server. Also check that the file is in the right encoding for the OS the app-server is running on. On z/OS, it is recommended to have the file encoding tagged.
ZWED0033W
Could not initialize plugin pluginId: error
Reason:
The plugin pluginId could not be loaded. This may be due to unsatisfied imports, where an import requested a version of something that was not available, or an entire plugin was not available. The server will still attempt to load if this plugin was not needed.
Action:
Check the error message to determine the cause of error for correction.
ZWED0034W
Skipping install of plugin due to existing plugin with same id=identifier
Reason:
The plugin could not be loaded due to a plugin that is already loaded containing the same identifier ID. Plugin IDs are unique, so the first plugin with that ID that is seen is the one that is loaded.
Action:
Check to see if you have 2 extensions that contain plugins with the same ID. Alternatively, an extension may have updated to have its name change without its ID changing, causing a duplicate to appear. You may need to clean up your extensions or the contents of the pluginsDir directory.
ZWED0035W
Error thrown when installing plugin=identifier: error
Reason:
The plugin with id identifier could not be added to the server because of an error that occurred. The server will still attempt to run without the plugin if possible.
Action:
Check the error message to see the reason for the error, and correct it before restarting the server in order to try loading the plugin again.
ZWED0036W
Uncaught exception found. Error: stackTrace
Reason:
The server encountered an unexpected error. If cluster mode is running, this will result in the worker crashing but the cluster starting a new worker to replace it. The client that initiated the request will need to retry the operation though other clients should not experience disruption.
If cluster mode is not running, the process will end but the launcher will restart it. In this case, state may be lost unless the caching service was also being used.
Action:
The stackTrace should be sent to developers so that the issue can be fixed.
ZWED0037W
Ending server process due to uncaught exception.
Reason:
The server is stopping after encountering ZWED00036W.
Action:
The information within ZWED0036W should be sent to developers so that the issue can be fixed.
ZWED0038W
Reason:
A child process with path childProcessConfig.path encountered an error with receiving data.
Action:
Action depends on context of what data is. May be useful in debugging an issue with internal ProcessManager.
ZWED0039W
Exception at server cleanup function: stack
Reason:
An exception occurred when ending process, during the cleanup phase.
Action:
No action is needed, but stack can be sent to developers if server processes are failing to end.
ZWED0040W
Callservice: Service call to %s:%s%s failed.
Reason:
An HTTP request to host with port at path failed.
Action:
Check the subsequent error message to see why it failed or Network log, if request originated from the browser.
ZWED0041W
[Proxy URL: urlPrefix] Exception caught. Message=message
Reason:
For urlPrefix proxy, an exception was caught with content message
Action:
No action needed usually, but message may be needed for debugging
ZWED0042W
Stack trace follows stack
Reason:
For the exception from ZWED0041W, a stack trace is printed
Action:
No action needed usually, but stack may be needed for debugging
ZWED0043W
[Proxy URL: urlPrefix] proxyWS error: error
Reason:
Proxy worker encountered an error
Action:
No action needed usually except, debugging of the error.
ZWED0044W
[Proxy URL: urlPrefix] WS error: error
Reason:
Worker encountered an error
Action:
No action needed usually except, debugging of the error.
ZWED0045W
Failed to reach the auth services host for address host:port
Reason:
Client encountered error when trying to connect to an agent host:port
Action:
This usually means your agent (for example: ZSS) is unreachable or your configuration is pointing to an incorrect agent
ZWED0046W
The auth services host system was not specified at startup, and defaulted to 127.0.0.1. Verify that the auth services server is running, or specify at startup the remote host and port to connect to. See documentation for details.
Reason:
Client encountered an error when trying to connect to the agent from ZWED0045W
Action:
See ZWED0045W
ZWED0048W
Invalid Swagger from file for service (plugin identifier:service name)
Reason:
N/A
Action:
Check validity of Swagger file
ZWED0049W"
error message stack
Reason:
Prints the error message and stack from ZWED0048W
Action:
See ZWED0048W
ZWED0051W
Failed to parse translation file path. File skipped
Reason:
Failed to parse the file path as a valid translation file, most likely because it's not valid JSON
Action:
Check if the translation file is valid JSON and matches the structure of core translation files (i.e. Sample Apps)
ZWED0052W
Error when reading file=path. Error=message
Reason:
Failed to read certificates or keys path with a returned message
Action:
Review content of message and correct
ZWED0053W
Event handler failed: error
Reason:
An asynchronous event listener handler failed
Action:
This isn't part of normal operation, if it causes issue, error and any relevant context should be sent to developers
ZWED0054W
Skipping invalid listener address=hostname
Reason:
hostname was deemed invalid when attempting a DNS lookup to find IP address
Action:
Compare with your configuration to see where the invalid hostname is being picked up
ZWED0055W
Skipping invalid listener address=hostname
Reason:
hostname is not a valid string
Action:
Compare with your configuration to see where the invalid hostname is being referenced
ZWED0056W
Couldn't process address as IP
Reason:
The address was not pointing a valid IP address by the ipaddr utility
Action:
Compare with your configuration to see where the invalid address is being referenced
ZWED0057W
Loopback calls: localhost equivalent address not found in the list listenerAddresses. Using first address address; Verify firewall will allow this.
Reason:
Unable to find a localhost equivalent from the listenerAddresses list so the server considers the first address in the loop by default.
Action:
Verify if this is intended configuration (edit/define zowe.components.app-server.node.https.ipAddresses or check Zowe documenation)
ZWED0058W
Log location for logger 'identifier:serviceDefinitionName' is undefined
Reason:
Log location isn't being specified for this dataservice.
Action:
Check dataservice plugin definition to see if log location is being specified.
ZWED0059W
Failed to add the plugin: errorMessage
Reason:
Using the /plugins API to add a plugin, has failed
Action:
Review errorMessage for explanation
ZWED0060W
errorMessage
Reason:
Invalid JSON
Action:
Review errorMessage
ZWED0061W
Callservice: Service call failed.
Reason:
A network request to this service failed.
Action:
Check Network log and review the error.
ZWED0062W
[Service URL: url] Exception caught. Message=errorMessage
Reason:
An error occurred calling url with reason errorMessage
Action:
Review correctness of url and review errorMessage
ZWED0063W
Stack trace follows stackTrace
Reason:
This exception originates from the web socket and the stack trace message handles the generated exception. The stack trace for an exception helps in understanding the error and what went wrong with the code.
Action:
No action needed unless user is experiencing an interruption in the server service, then send the stack to developers.
ZWED0064W
plugin.identifier: Invalid method method
Reason:
It will throw the warning if method is invalid (different from these methods: get|post|put|delete|ws)
Action:
Review the warning message and use correct method.
ZWED0065W
Library plugin plugin.identifier is missing libraryVersion attribute for hosting files. Skipping file hosting.
Reason:
Library plugin's plugin definition is missing the library version attribute.
Action:
Add the correct library version in the plugin definition.
ZWED0066W
pluginID: getCapabilities() is not a function
Reason:
The handler for plugin pluginID does not have a getCapabilities() method
Action:
No action required. If your desired authentication plugin isn't successfully authenticating a login, please send the log and any relevant info to the developers.
ZWED0068W
Failed to set proxy authorizations. Error=errorMessage
Reason:
Failed to add proxy authorization with reason errorMessage.
Action:
No action required. If your desired authentication plugin isn't successfully authenticating a login, please send the log and any relevant info to the developers.
ZWED0069W
Returning null for cipher array because input had non-string:
Reason:
Returns null for cipher array if an array element is not a string type.
Action:
Please verify, if any custom cyphers present, that all cyphers are of type string.
ZWED0070W
Error when reading PFX. The server cannot continue. Error=errorMessage
Reason:
If we get an error while reading config.https.pfx file then the server cannot continue and throws errorMessage.
Action:
No action is needed, but the errorMessage may be needed to debug
ZWED0071W
Unexpected error on server ipAddress:port. E=errorMessage. Stack trace follows. stack
Reason:
When we get an unexpected (anything except EACCES, EADDRINUSE, ENOTFOUND, EADDRNOTAVAIL) error in the web server for ipAddress:port.
Action:
No action needed unless user is experiencing an interruption in server, then send error message and stack to developers
ZWED0072W
Could not stop manager due to error errorMessage
Reason:
If the server manager is unable to stop due to any reason it will throw an exception with an errorMessage.
Action:
If the Java manager (handles Jar and War) is unable to stop all servers, send errorMessage to developers
ZWED0073W
No server returned for group=group
Reason:
If No server was found in this War group then it will throw this warning message.
Action:
No action is required
ZWED0074W
Unknown default behavior=defaultBehavior
Reason:
The default grouping behaviour in the config for this War is not of type 'microservice' or 'appserver'
Action:
No action is needed, but the warning may be needed to debug
ZWED0075W
Services in plugin=plugin war grouping skipped. Plugin missing or already grouped
Reason:
Server was not created for plugin War grouping, because it was already made or plugin is missing.
Action:
No action is needed
ZWED0076W
Skipping invalid plugin group=plugins
Reason:
If plugins is not an array and the size is less than zero, then it will log a warning message.
Action:
Make sure plugins should be an array of size greater than zero.
ZWED0077W
Could not extract war for service=key-value, error=errorMessage
Reason:
If the service with the key-value pair is unable to extract the war file then it throws the errorMessage
Action:
Check if the war file exists and configured correctly.
ZWED0078W
Could not access files to determine status for service=key-value, error=errorMessage
Reason:
If we are unable to get the status of war extracted or not, then it throws errorMessage in catch block.
Action:
Check if the war file exists.
ZWED0079W
Cannot add servlet for service=key-value, error=errorMessage
Reason:
If unable to add servlet for service key-value, then it logs a warning errorMessage.
Action:
No action is needed, but the warning may be needed to debug this War
ZWED0080W
Cannot add servlet for service=key-value
Reason:
When we are not able to get the directory to add servlet for service key-value.
Action:
Check if your directory exists and is valid.
ZWED0081W
Could not start Tomcat, error=errorMessage
Reason:
Tomcat manager is unable to start Tomcat with the Java option, due to an incorrect configuration with components.app-server.node.https.port, components.app-server.node.https.key, or components.app-server.node.https.certificate.
Action:
Verify configuration with components.app-server.node.https.port, components.app-server.node.https.key, or components.app-server.node.https.certificate is valid or not.
ZWED0082W
Tomcat PID=pid: stderr=error
Reason:
A Tomcat process with Tomcat pid encountered an error (stderr).
Action:
Action depends on what error is and may be useful to debug.
ZWED0083W
Tomcat could not start. Closing. code=code
Reason:
If the Tomcat manager is unable to start itself, then it closes with code.
Action:
Review the message and if app server service is interrupted, send the message along with the log to support for troubleshooting.
ZWED0084W
Tomcat could not start. Exiting. code=code
Reason:
If the Tomcat manager is unable to start itself, then it exits with code.
Action:
Review the message and if app server service is interrupted, send the message along with the log to support for troubleshooting.
ZWED0085
Tomcat PID=pid Error when stopping, error=errorMessage
Reason:
If Tomcat manager is unable to stop the Tomcat process on Windows, then it logs errorMessage.
Action:
Review the errorMessage and see if there is something you can do to fix the error
ZWED0086W
Could not stop Tomcat, error=errorMessage
Reason:
If Tomcat manager is unable to stop the Tomcat process on Unix, then it logs errorMessage.
Action:
Review the errorMessage and if app server service is interrupted, send the message along with the log to support for troubleshooting.
ZWED0087W
Tomcat PID=pid: stderr=error
Reason:
While stopping Tomcat, Tomcat process with Tomcat pid encountered an error (stderr).
Action:
Review the error and if app server service is interrupted, send the message along with the log to support for troubleshooting..
ZWED0146W
Could not stat destination or temp folder path. Error=ErrorMsg
Reason:
Server was unable to use 'stat' command on folder path and threw ErrorMsg.
Action:
No action is needed usually, however, need to debug the ErrorMsg.
ZWED0148W
App extracted but not registered to App Server due to write fail. Error=errorMessage
Reason:
App extracted successfully but not registered to App Server due to write fail. Error=errorMessage.
Action:
Go through the errorMessage and undestand what to debug.
ZWED0149W
Could not find pluginDefinition.json file in App (dir=AppDir). Error=ErrorMsg
Reason:
Throws ErrorMsg when its not able to find the pluginDefinition.json file in AppDir location.
Action:
Check if pluginDefinition.json exists in AppDir.
ZWED0150W
identifier library path location does not exist.
Reason:
Server throws warning when library plugin identifier does not exist at path location.
Action:
Check if the library plugin exists in the path location.
ZWED0151W
unhandledRejection error
Reason:
When process experiences an unhandledRejection.
Action:
No action is needed usually, however, need to debug the ErrorMsg.
ZWED0152W
Error at call sessionStore. APIMethodname: Error Object
Reason:
There is a problem calling a sessionStore APIMethodname.
Action:
No action is needed usually, however, need to debug the ErrorMsg.
ZWED0153W
WARNING: CLI Argument missing name or has unsupported type=type
Reason:
The server throws a warning when the CLI argument is missing a name, or has an unsupported type (supported types: 1 - flag, 2 - value, 3 - json).
Action:
Check any missing argument or unsupported argument.
ZWED0154W
WARNING: Unrecognized command: args
Reason:
Throws warning when args is unrecognized.
Action:
Check the command once again or check if the specified command is interpreted as intended.
ZWED0155W
ErrorMsg
Reason:
Server throws 500 code with ErrorMsg.
Action:
Go through the ErrorMsg for context on what to debug.
ZWED0156W
1 function initLoggerMessages - ERROR - Error
Reason:
Attempt to get log message for a language a user may have specified, has failed with Error.
Action:
Go through the Error for details on what to debug.
ZWED0157W
2 function initLoggerMessages - ERROR - Error.
Reason:
Attempt to get log message for English has failed with Error.
Action:
Go through the Error for details on what to debug.
ZWED0158W
ErrorMsg
Reason:
Server throws 500 code with ErrorMsg.
Action:
Go through the ErrorMsg for details on what to debug.
ZWED0159W
Plugin (PluginIdentifier) loading failed. Message: "errorMessage" Successful: pluginsLoaded% (pluginsLoaded/eventCount) Attempted: pluginCount% (pluginCount/eventCount)
Reason:
Plugin with pluginId loaded failed with errorMessage. The server attempted to load a total of pluginCount with pluginsLoaded plugins already successfully loaded.
Action:
Review errorMessage to see if there is something you can do to fix the error. You may need to contact the plugin developer to find a solution. If you do not need this plugin, it is OK to continue.
ZWED0166W
Error updating the storage: Error
Reason:
Throws warning Error when it faced error while updating the storage.
Action:
Contact support if Error is not clear.
ZWED0167W
Error adding to the storage: errorMessage
Reason:
Throws errorMessage while adding to the storage.
Action:
If app server service is interrupted, go through the errorMessage for details on what to debug or contact support if errorMessage is not clear.
ZWED0168W
Unable to retrieve storage value from cluster Error
Reason:
Throws warning Error when it is unable to retrieve storage value from cluster.
Action:
By default, the timeout for cluster method calls is 1000ms which should cause no issues. If service is interrupted, contact support and provide Error.
ZWED0169W
Error deleting the storage with id: deleteStorageByKey Error
Reason:
when server tries deleting storage by key deleteStorageByKey.
Action:
Contact support if Error is not clear.
ZWED0170W
Plugin (PluginIdentifier) loading failed. Version: PluginVersion. Message: "Error"
Reason:
Plugin PluginIdentifier with version PluginVersion has failed to load with an Error.
Action:
Review Error to see if there is something you can do to fix the error. You may need to contact the plugin developer to find a solution. If you do not need this plugin, it is OK to continue.
ZWED0171W
Rejected undefined referrer for url=originalUrl, ip=ip
Reason:
Throws 403 Forbidden when App server fails to honor a network request due to failed referrer check.
Action:
Double check the address. A possible reason for a 403 error is a misstyped originalUrl or ip or because loopback routing is not configured in the App server.
ZWED0172W
Rejected bad referrer=referrerHeaderValue for url=accessedUrl, ip=clientIp
Reason:
The client from clientIp tried to access accessedUrl but due to having a referrer header value that didn't seem to originate from this server, a security violation was caused and the attempt to access the URL was rejected.
Action:
Review the values to determine if this was a valid attempt to access the server or not. If this access seems suspicious, then the server was correct in rejecting the access. However, if the access attempt seemed legitimate, then this points to the referrer configuration needing revision. You can customize which referrer header values are permitted using the environment variable ZWE_REFERRER_HOSTS and it should be set to match the external hostnames of the system the app-server is running on.
ZWED0173W
Unable to decode P12 certificate (different password than keystore?). Attempting to use empty string as password. Decode error: error.
Reason:
The server tried to load the p12 file provided for the server certificate or certificate authorities, but encountered error. The server may not be accessible as a result of invalid TLS configuration.
Action:
Check the value of zowe.certificate.keystore.password and zowe.certificate.truststore.password, or the environment variable KEYSTORE_PASSWORD to see if they are valid for the p12 file provided, and adjust the configuration if needed.
ZWED0174W
componentName could not verify (operatingSystem) as a supported platform to install (pluginId). Proceeding anyway...
Reason:
The plugin pluginId has a dependency which can only run on certain operating systems, and operatingSystem is not on the list, but because the operating system is not explicitly forbidden, the server will attempt to load the plugin anyway. This may fail, but the server may continue to run without the plugin if possible.
Action:
Review the plugin dependencies as seen in the plugin's pluginDefinition.json file to see if your Zowe configuration or the plugin can be changed in order to match the requirements. Consult the plugin developer if you believe the plugin was able to run fine on the operating system, so they can explicitly add support in the future.
ZWED0175W
componentName could not verify (systemArchitecture) as a supported architecture to install (pluginId). Proceeding anyway...
Reason:
The plugin pluginId has a dependency which can only run on certain system architectures, and systemArchitecture is not on the list, but because the system architecture is not explicitly forbidden, the server will attempt to load the plugin anyway. This may fail, but the server may continue to run without the plugin if possible.
Action:
Review the plugin dependencies as seen in the plugin's pluginDefinition.json file to see if your Zowe configuration or the plugin can be changed in order to match the requirements. Consult the plugin developer if you believe the plugin was able to run fine on the system architecture, so they can explicitly add support in the future.
ZWED0177W
Unable to load actionOrRecognizer for 'pluginId' into config
Reason:
The plugin pluginId has an action or recognizer within its package and the plugin install process was trying to copy that into the workspace so it can be used, but encountered an error that prevented this.
Action:
Contact support if the reason cannot be determined.
ZWED0178W
Skipping authentication plugin pluginId because it's not HA compatible
Reason:
The server is setup for running in high availability (HA) mode which requires that plugins that have state, in particular authentication plugins, must be HA-compatible or else errors will occur. Therefore, the server skips over loading of this plugin nbecause its pluginDefinition.json did not state it was HA compatible.
Action:
Either the plugin must be updated to support and state its support for HA, or it must be removed, or HA mode disabled. To make a plugin support HA, the conformance program should be reviewed. When HA mode is supported, the plugin can be marked as compatible by setting capabilities.haCompatible=true within its initialization.
ZWED0179W
Unable to retrieve the list of certificate authorities from the keyring=keyringName owner=username Error: error
Reason:
The server could not automatically determine the certificate authorities (CA) from the z/OS keyring listed. This may cause the server to be unable to verify certificate chains from other servers or clients causing other errors later.
Action:
Review the error to resolve it and contact support if needed. It's also possible as a workaround to explicitly state the CAs within the keyring that you would like to load, rather than relying upon the server's attempt to automatically find all CAs within the keyring.
ZWED0001E
Error: error
Reason:
The server is running in cluster mode and the cluster manager has encountered an unexpected error.
Action:
Review the error to resolve it, and contact support if needed.
ZWED0002E
Could not stop language manager for types=languageNames
Reason:
A plugin had a service that needed a language manager to run. During shutdown, the language manager could not be stopped.
Action:
The language manager may continue to run after the app-server shuts down. Review the logs to determine the location of the language manager and try to stop the manager manually.
ZWED0003E
Loopback configuration not valid, loobackConfiguration Loopback calls will fail!
Reason:
The loopback configuration that the server uses to contact itself over an internal network was missing a value for the network port, therefore no requests over the loopback address will be possible.
Action:
Review the configuration of components.app-server.node.port to see if it has a value and set one to fix the issue.
ZWED0004E
Could not listen on address ip:port. It is already in use by another process.
Reason:
The server tried to start using the ip and port values shown which were from the zowe configuration. When trying to connect to this address, the server recieved an error telling it that the address was already in use.
Action:
Check the system's network port status to see what program could be using this address, and either stop that program or change the zowe configuration to use a different address before restarting zowe.
ZWED0005E
Could not listen on address ip:port. Invalid IP for this system.
Reason:
When the app-server was binding to the address shown, it recieved the error EADDRNOTAVAIL or ENOTFOUND. In either case, the app-server was not able to bind to the address and so it will not run until the problem is solved.
Action:
Review the address and check if it is valid or if there is some lack of permissions that might explain why these errors were received by the server.
ZWED0006E
Usage: --inputApp | -i INPUTAPP --pluginsDir | -p PLUGINSDIR --zluxConfig | -c ZLUXCONFIGPATH [--verbose | -v]
Reason:
This message appearas when you attempt app installation but have not provided enough of the mandatory arguments for the program to run. It is printing out what options are valid so that you can retry with different options.
Action:
Retry the operation after modifying the input arguments to be valid against the list shown. Or, if you are trying to do app installation, you should use zwe components install instead whenever possible.
ZWED0007E
serviceName invalid version version
Reason:
The service mentioned was trying to be loaded by the server but failed validation due to the version number not being a a valid semver string. This service and therefore plugin will be skipped during loading.
Action:
Contact the developers so that they can revise the pluginDefinition.json of the plugin where the service is located to be semver-compatible. Details on semver version can be found at semver.org
ZWED0008E
localServiceName: invalid version range serviceName: versionRange
Reason:
When the serviceName was trying to be imported into a plugin as localServiceName, the version range of acceptable versions for the service to be imported was not valid. Due to this, the import cannot be resolved and the plugin will be skipped in loading.
Action:
Contact the developers of the plugin this error occurred in as the pluginDefinition.json needs to be revised to have the version range given for this import service be a valid semver range string.
ZWED0009E
localServiceName: invalid version range versionRange
Reason:
When the a service was trying to be imported into a plugin as localServiceName, the version range of acceptable versions for the service to be imported was not valid. Due to this, the import cannot be resolved and the plugin will be skipped in loading.
Action:
Contact the developers of the plugin this error occurred in as the pluginDefinition.json needs to be revised to have the version range given for this import service be a valid semver range string.
ZWED0010E
No file name for data service
Reason:
When the server was trying to load a service for a plugn, it couldn't identify the filename where the service is located within the plugin, so the service and therefore plugin have been skipped during loading.
Action:
Contact the plugin developer to fix that the service within the pluginDefinition.json is missing the "fileName" or "filename" property which must describe the path to the dataservice entry file, relative to the plugin's lib directory.
ZWED0011E
Plugin pluginId has web content but no web directory under location
Reason:
The plugin definition of pluginId stated that the plugin has web content to serve such as HTML files, but the required 'web' folder was missing, so the plugin cannot be loaded.
Action:
Check that the web folder within this plugin exists or not. If it does exist, then the server may not have had permission to read it. Otherwise, if it doesn't exist, try to reinstall the plugin in case it is corrupt. Or, contact the developers to fix the lack of web directory.
ZWED0012E
pluginId::serviceName Required local service missing: localService
Reason:
The service serviceName could not be loaded because of an unsatisfied version requirement upon another service. This causes the plugin pluginId to be skipped during loading.
Action:
Review the plugin's definition to see why the version match could not be made. Either a required plugin is missing, or the pluginDefinition.json will need to be revised by the developer of the plugin to fix the version check failure.
ZWED0013E
pluginId::serviceName Could not find a version to satisfy local dependency serviceName@requiredVersion
Reason:
The service serviceName could not be loaded because of an unsatisfied version requirement upon another service. This causes the plugin pluginId to be skipped during loading.
Action:
Review the plugin's definition to see why the version match could not be made. Either a required plugin is missing, or the pluginDefinition.json will need to be revised by the developer of the plugin to fix the version check failure.
ZWED0014E
Plugin pluginId invalid
Reason:
The plugin could not be loaded because the plugin definition was not valid in some way. There are fields that every plugin must define, such as type. Then, depending on type, there are more fields a plugin can and cannot have. When the server went to load the plugin, it found that the definition was not correct versus the requirements, so the loading of this plugin was skipped.
Action:
Contact the developers of this plugin so that they can fix the plugin to adhere to the plugin schema
ZWED0015E
No plugin directory found at pluginLocation
Reason:
The server finds plugins by reading JSON files within the "plugins" folder of its workspace directory. When it checked the JSON of this particular plugin, the JSON stated the plugin could be found at a folder pluginLocation which either does not exist or could not be read by the server.
Action:
Check that the location shown exists. If it does exist, then there is some permission problem preventing the server from reading it. If it does not exist, determine whether this plugin is desired but has the wrong location, or if this plugin is not desired and should be removed. Contact support so they can assist in fixing the plugin location problem.
ZWED0016E
No pluginDefinition.json found at pluginLocation
Reason:
The server finds plugins by reading JSON files within the "plugins" folder of its workspace directory. When it checked the JSON of this particular plugin, it stated the plugin was located in a folder which the server determined did not contain the pluginDefinition.json file that every plugin requires. Due to this missing file, the loading of this plugin was skipped.
Action:
Check that a pluginDefinition.json exists at the location specified. If it does, then the server is missing permissions necessary to read the file. If the file does not exist, review if there is a problem with the plugin itself that should be resolved by contacting the plugin developers. If the plugin exists with a pluginDefinition.json file at a different location than the error suggests, contact Zowe support to resolve the location problem.
ZWED0017E
Identifier doesn't match one found in pluginDefinition: pluginIdentifier
Reason:
The identifier found in the plugin reference doesn't match the one specified in the pluginDefinition.json
Action:
Check if identifier found is the same one as intended (typo perhaps?). If not, delete the plugin identifier JSON (found in instance/workspace/app-server/plugins) and restart Zowe. If issue isn't resolved, increase app server debugging and send logs to the app developer
ZWED0018E
No plugin type found, skipping
Reason:
The plugin definition for the plugin has no 'pluginType' property set
Action:
Contact app developers if you need plugin to be loaded and working
ZWED0019E
Plugin already registered
Reason:
A plugin with this identifier has already been registered to the map of plugins
Action:
Check if you have multiple components sharing the same, or different versions, of the same plugin. This is not allowed
ZWED0020E
"pluginIdentifier: pluginType type is unknown
Reason:
The plugin pluginIdentifier has in its plugin definition an invalid plugin type
Action:
Accepted plugin types found in the schema (https://github.com/zowe/zlux-app-server/blob/v2.x/staging/schemas/plugindefinition-schema.json#L47)
ZWED0021E
pluginPath is missing
Reason:
App server tried to process the plugin reference from path pluginPath
Action:
Check if pluginPath is a real path or the App server (started task user of Zowe) has the permission to read it
ZWED0022E
Module not found moduleName
Reason:
App server, during a cluster/worker method call, tried to require a module moduleName it couldn't find
Action:
Contact the plugin developer if plugin returns this error.
ZWED0023E
Method not implemented methodName
Reason:
App server, during a cluster/worker method call, tried to act on a method that isn't valid.
Action:
Contact the plugin developer if plugin returns this error.
ZWED0024E
Object not exported exportName
Reason:
App server, during a cluster/worker method call, tried and failed to export a module object.
Action:
Contact the plugin developer if plugin returns this error.
ZWED0025E
.authenticate() missing
Reason:
Authentication plugin (which plugin includes looking at nearby log messages) is missing the .authenticate() method.
Action:
Contact the plugin developer if plugin is essential for authenticaiton.
ZWED0026E
Circular dependency: pluginIdentifier
Reason:
The App server encountered a circular dependency for plugin pluginIdentifier (meaning it contains a dependency that imports itself).
Action:
Contact the plugin developer for troubleshooting help. This is a packaging issue.
ZWED0027E
Circular dependency: pluginIdentifier
Reason:
The App server encountered a circular dependency for plugin pluginIdentifier (meaning it contains a dependency that imports itself).
Action:
Contact the plugin developer for troubleshooting help. This is a packaging issue.
ZWED0028E
Config invalid
Reason:
The App server attempted to validate and process the server configuration and there was an issue.
Action:
Please consult the App server schema components.app-server.node section (https://github.com/zowe/zlux-app-server/blob/v2.x/staging/schemas/app-server-config.json#L9). You may also instead have a syntax issue. For a free, offline YAML validator, check out RedHat's VSCode YAML Extension
ZWED0038E
JavaManager given port range beyond limits
Reason:
The Java manager was given a port outside the valid port range (0 < 65535).
Action:
Please check your configuration to see if any ports are out of bounds.
ZWED0039E
JavaManager not given any ports with which to run servers.
Reason:
Configuration does not contain ports for Java manager to try to run the servers.
Action:
Please check your configuration to see if any ports are missing.
ZWED0040E
Unknown java war grouping default=grouping
Reason:
For this war, an unknown grouping default grouping was encountered (types: 'microservice' or 'appserver' allowed).
Action:
Contact the plugin developer for troubleshooting.
ZWED0041E
Could not find port to use for configuration, at config position=portIndex.
Reason:
The server was trying to determine a network port to use for a Java dataservice, but no available ports could be found, so the server cannot load that service.
Action:
Check your Zowe configuration to see if you have enough or any ports specified for the app-server to use when assigning ports to Java dataservices.
ZWED0042E
Could not find runtime to satisfy group: javaRuntime
Reason:
When trying to run a group of Java dataservices under a common java runtime, the javaRuntime couldn't be found, so the dataservices cannot be run.
Action:
Check the configuration for this group of Java services to see if javaRuntime is a good value, and resolve the Java issue before restarting the server.
ZWED0043E
Unknown java app server type=javaRuntimeTime specified in config. Cannot continue with java loading.
Reason:
The app-server can only handle Java dataservices if they run under certain types of Java server runtimes. The type chosen was not one of the types supported, so the server cannot continue with the loading.
Action:
Check if the version of the plugin you are using is compatible with the version of Zowe you are using. Check if you can change the "type" of java server to one that the app-server does work with, such as "tomcat".
ZWED0044E
Java runtimes not specified, and no JAVA_HOME set
Reason:
The app-server cannot run the java dataservices because it doesn't know how to start any Java with the configuration specified.
Action:
Either define the environment variable JAVA_HOME to point to a valid Java runtime home, or specify a Java runtime within the app-server configuration as components.app-server.languages.java.runtimes. For more information, see the server schema https://github.com/zowe/zlux-app-server/blob/v2.x/master/schemas/app-server-config.json
ZWED0045E
Java app server not defined in config
Reason:
A dataservice was configured to run from a WAR file but the configuration section components.app-server.languages.java.war.javaAppServer was missing, so the app-server could not run the dataservice.
Action:
Define the missing configuration section according to the app-server schema https://github.com/zowe/zlux-app-server/blob/v2.x/master/schemas/app-server-config.json or remove it and the plugin that required it.
ZWED0046E
JavaManager not given either war or jar configuration options, nothing to do
Reason:
A java dataservice was requested but the components.app-server.languages.java configuration section of Zowe was missing either a war or jar subsection. Since one of the two is needed, the server could not continue with loading the java dataservices.
Action:
Review the app-server schema https://github.com/zowe/zlux-app-server/blob/v2.x/master/schemas/app-server-config.json and your Zowe configuration file to identify and correct the missing properties within components.app-server.
ZWED0047E
Proxy (pluginid:servicename) setup failed. Host & Port for proxy destination are required but were missing. For information on how to configure a proxy service, see the Zowe wiki on dataservices (https://github.com/zowe/zlux/wiki/ZLUX-Dataservices)
Reason:
A proxy was requested by the service pluginid:servicename but the service configuration or pluginDefinition did not specify what the proxy destination was, so the server is skipping the loading of that plugin.
Action:
Review the plugin's configuration or contact the developer of that plugin to correct the proxy configuration.
ZWED0049E
Can't specify error metadata
Reason:
When a dataservice called the utility function makeErrorObject, it did not supply context of the _objectType and _metaDataVersion, which are required and caused the function to throw its own error about the lack of information.
Action:
Contact the developer of the plugin which caused this error.
ZWED0050E
Root service serviceName not found
Reason:
A dataservice tried to call a "root", or non-plugin service of the app-server or app-server's agent, and this root service serviceName was not found on the server, so the request failed.
Action:
Verify that your version of Zowe works with the plugins that you have installed, and contact the developer of the plugin which tried to call this missing root service.
ZWED0051E
Could not resolve service URL. Plugin=pluginId, service=serviceName
Reason:
A dataservice serviceName handled by a language manager could not be used because the URL in which to access this dataservice from its language manager could not be determined.
Action:
Check the logs to see if there was trouble installing the service or plugin, and contact the developers of pluginId for more support.
ZWED0052E
Could not load service pluginId:serviceName due to unknown type=serviceType
Reason:
The service from the plugin shown could not be loaded because the plugin declared the service to be of some type that the app-server does not handle.
Action:
Check to see if the version of Zowe you are using works with the version of the plugin you are using. Plugins must have dataservices only of types seen within the pluginDefinition schema https://github.com/zowe/zlux-app-server/blob/v2.x/staging/schemas/plugindefinition-schema.json
ZWED0053E
Import sourcePluginId:sourceServiceName can't be satisfied
Reason:
A plugin trying to load a dataservice from sourcePluginId:sourceServiceName couldn't load that service, therefore the requesting plugin will fail to load.
Action:
Confirm that the source plugin and service exist. Check the logs to see if there was something that caused the source service to fail loading. Contact the developers of either source or target plugin for more assistance if the cause is not clear.
ZWED0111E
SEVERE: Exception occurred trying to generate object from input: error
Reason:
The server could not parse its input configuration due to the error shown, so the server cannot start.
Action:
Review the error to determine the cause, or contact support if the cause is unclear.
ZWED0112E
The server found no plugin implementing the specified default authentication type of type.
Reason:
The value of components.app-server.dataserviceAuthentication.defaultAuthentication within the server configuration specified a type of authentication that some authentication plugin must implement in order for the server to run. Because no plugin that successfully loaded declared that it implemented this type, the server found no implementation and could not continue.
Action:
Review if any plugin you have implements the given type. If the type is incorrect, revise the configuration to choose a type that does exist in your system. If the type is correct, check if you are missing a required plugin.
ZWED0113E
The server found no authentication types. Verify that the server configuration file defines server authentication.
Reason:
The server was unable to find any authentication plugins where at least one is required to run.
Action:
Review the list of plugins that are being used and see if any authentication plugins you needed have failed to load, and review their error messages.
ZWED0114E
The server found no plugin implementing the specified default authentication type of type.
Reason:
The value of components.app-server.dataserviceAuthentication.defaultAuthentication within the server configuration specified a type of authentication that some authentication plugin must implement in order for the server to run. Because no plugin that successfully loaded declared that it implemented this type, the server found no implementation and could not continue.
Action:
Review if any plugin you have implements the given type. If the type is incorrect, revise the configuration to choose a type that does exist in your system. If the type is correct, check if you are missing a required plugin.
ZWED0115E
Unable to retrieve storage object from cluster. This is probably due to a timeout. You may change the default of 'storageTimeout' ms by setting 'node.cluster.storageTimeout' within the config.
Reason:
The app-server was running in cluster mode and a service attempted to get content from the cluster storage but this failed. Because storage could not be read, its possible the service that requested the storage will have further errors.
Action:
If there was a network disruption or performance issue, a timeout could have occurred. Review the rest of the logs to see if there are other messages to explain the failure. You can attempt to avoid timeout-related failures by editing the configuration parameter components.app-server.node.cluster.storageTimeout.
ZWED0145E
Cannot load SAF keyring content outside of z/OS
Reason:
The Zowe configuration of zowe.certificate or components.app-server.node.https specifies SAF keyrings as locations to find keystore and truststore data. SAF keyrings only exist on z/OS, and the server detected it was not running on z/OS so it cannot continue.
Action:
Modify the configuration to use a different keystore type, or migrate the server to z/OS.
ZWED0146E
SAF keyring data had no attribute "attribute". Attributes=attributeKeys
Reason:
Within the list of attributeKeys, attribute could not be found.
Action:
Check the keystore configuration of the server such as in zowe.certificate or components.app-server.node.https to see if it is valid for Zowe. The SAF keyring Zowe was configured to use may be missing a key and certificate pair, or certificate authorities keychain. For more suggestions on configuring keyrings for Zowe, review the install guide
ZWED0147E
SAF keyring data was not found for "keyName"
Reason:
The server tried to read the SAF keyring specified within the Zowe configuration, but ran into an error where the server received no data instead.
Action:
Review the logs to see if a reason for the error is shown. Verify that the Zowe configuration points to a valid keyring that the Zowe server user has permissions to read.
ZWED0148E
Exception thrown when reading SAF keyring, e=error
Reason:
The SAF keyring which the app-server was configured to use could not be read due to an error. The server likely will not start or will be unable to do any network activity until this error is resolved.
Action:
Review the error message to determine the cause. Often, the error messages will originate from a system service where the documentation can be found here https://www.ibm.com/docs/en/zos/2.5.0?topic=library-return-reason-codes
ZWED0149E
SAF keyring reference missing userId "user", keyringName "name", or label "label"
Reason:
The server configuration specified that the app-server should load keystore and truststore content from a SAF keyring, but the syntax in the configuration was incorrect, because user, name, or label were not usable by the server.
Action:
Check the zowe.certificate or components.app-server.node.https sections of Zowe configuration to see if there are entries that start with safkeyring:// and verify that they are in the format of safkeyring://USERNAME:RINGNAME&LABEL. Older versions of zowe will require that there be 4 slashes, such as safkeyring:////. The &LABEL suffix is only needed for specifying certificate authorities and should be omitted in other sections, for example it is only needed within zowe.certificate.pem.certificateAuthorities or components.app-server.node.https.certificateAuthorities. For more suggestions on configuring keyrings for Zowe, review the install guide
ZWED0150E
Cannot load SAF keyring due to missing keyring_js library
Reason:
The Zowe configuration specified that the app-server should load keystore and truststore information from a SAF keyring, which requires the nodejs library keyring_js. This library is defined within the package.json of zlux-server-framework and ships with Zowe installs, but could not be loaded for some reason and therefore the server could not load keyrings and will either stop or have issues with network communication.
Action:
Use the command zwe support to verify if the Zowe install has all files expected, as this message indicates the keyring_js library is missing and reinstalling Zowe may be required.
ZWED0151E
Env var variableName not found
Reason:
The server was loading plugins. It determines the location of each plugin via a plugin pointer file. The plugin referenced in the logs, it's location is dynamically determined by an environment variable variableName. Because the variable did not resolve to a value, the plugin could not be found and could not be loaded.
Action:
Review the documentation for the plugin that failed to load, check what the value of the variable should be, and contact support for that plugin if needed.
ZWED0152E
Unable to locate server config instance location and INSTANCE_DIR environment variable does not exist.
Reason:
While installing a plugin, the server could not determine the location of the configuration dataservice's "instance" folder. Due to this, the plugin could not be completely installed.
Action:
Correct the error before reinstalling the plugin. This error could happen due to an incorrect value for components.app-server.instanceDir and normally defaults to {{ zowe.workspaceDirectory }}/app-server.
ZWED0153E
(operatingSystemName) is not a supported platform for componentName. Skipping (pluginid)... Supported: requiredOperatingSystem
Reason:
The Zowe host operating system operatingSystemName is not supported by the component componentName. Supported platforms are defined in the component's pluginDefinition.json.
Action:
Refer to componentName pluginDefinition.json for supported platforms. The installation of Zowe may also be moved to a supported platform. Lastly, contact the author of the component, or a system administrator.
ZWED0154E
(architectureName) is not a supported architecture for componentName. Skipping (pluginid)... Supported: requiredArchitecture
Reason:
The Zowe host architecture is not supported by componentName. Supported architectures are defined in the component's pluginDefintion.json.
Action:
Refer to componentName pluginDefinition.json for supported architectures. The installation of Zowe may also be moved to a supported architecture. Lastly, contact the author of the component, or a system administrator.
ZWED0155E
(url) is not a supported endpoint for componentName. Skipping (pluginid)... Supported: urls
Reason:
The endpoint url does not match any required endpoints of componentName. Supported endpoints may be viewd in the component's pluginDefinition.json.
Action:
Refer to componentName pluginDefinition.json for supported endpoints. Optionally, remove url from the required endpoints in pluginDefinition.json. Lastly, contact the author of the component, or a system administrator.
ZWED0156E
Could not register default plugins into app-server.
Reason:
org.zowe.zlux.json is missing from app-server plugin directory. This error will cause the process to exit.
Action:
Verify integrity of Zowe installation, or contact system administrator. Please refer to https://docs.zowe.org/stable/appendix/zwe_server_command_reference/zwe/support/zwe-support for collecting Zowe runtime information.
ZWED0157E
Could not register default plugin pluginid into app-server.
Reason:
Could not register default plugin pluginid into app-server due to plugin upgrade failure.
Action:
Verify integrity of plugin files, or contact system administrator. Please refer to https://docs.zowe.org/stable/appendix/zwe_server_command_reference/zwe/support/zwe-support for collecting Zowe runtime information.
ZWED0158E
Could not listen on address ipAddress:port. Insufficient permissions to perform port bind.
Reason:
Server could not bind to port due to an EACCES error. User lacks privilege to perform port bind. This error will cause the process to exit.
Action:
Contact system administrator.