IBM InfoSphere DataStage and QualityStage Operations Console does not display Disk Space information

-

Technote (troubleshooting)

Problem(Abstract)

IBM InfoSphere DataStage and QualityStage Operations Console sometimes displays the Disk Space information of a selected engine as 'Nothing monitored'.

For example,
Activity > Resources > Charts > Disk Space > MYSERVER (Engine) > (Nothing monitored)

Cause

The Operations Console retrieves a list of mounted file systems to be monitored from the DSODBConfig.cfg file on the engine tier.

The possible causes for the issue:
- Properties ResourceLocalFS and / or ResourceRemoteFS in the DSODBConfig.cfg are not set.
- The file systems specified in these properties do not actually exist.
- Properties ResourceLocalFS and / or ResourceRemoteFS have leading and trailing spaces in their names and values.
For example,
# The following specifies a locally mounted file system to be monitored.
# This property can be repeated any number of times to specify multiple file systems.
  ResourceLocalFS =/local_test1
  ResourceLocalFS=/ local_test2


Resolving the problem

The steps to resolve the issue:

1. Ensure the mounted file systems to be monitored are set correctly without any leading and trailing spaces in the property names and their values.

For example, in the /opt/IBM/InformationServer/Server/DSODB/DSODBConfig.cfg file on UNIX/Linux platforms:
# The following specifies a locally mounted file system to be monitored.
# This property can be repeated any number of times to specify multiple file systems.
ResourceLocalFS=/local_test1
ResourceLocalFS=/local_test2

# The following specifies a file system mounted on a remote node to be monitored.
# Specify the node name and file system path separated by a plus (+)
# The remote node name must match that specified in the corresponding ResourceNode entry above.
# This property can be repeated any number of times to specify multiple file systems.
ResourceRemoteFS=node1+/remote_test
ResourceRemoteFS=node2+/remote_test

2. Remove the leading and trailing spaces, if there are any, from other property names and their values in the file.

3. Verify the specified file systems exist with mount or ls command.

4. Log out from the Operations Console.

5. Restart the AppWatcher service.

For example,
- On UNIX/Linux platforms, run the following commands as dsadm or an equivalent user:
/opt/IBM/InformationServer/Server/DSODB/bin/DSAppWatcher.sh -stop
/opt/IBM/InformationServer/Server/DSODB/bin/DSAppWatcher.sh -start

- On Windows platform, restart the service from the Control Panel services menu or run commands below from a command prompt (run as administrator):
net stop "DataStage AppWatcher Service"
net start "DataStage AppWatcher Service"

6. Log in to the Operations Console to verify the issue is resolved.





Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more