InfoSphere Information Server dsrpcd tracing

-

InfoSphere DataStage clients are not connecting. How can I trace the dsrpcd daemon to see what the problem is.

Answer

here are the steps to put the dsrpcd daemon into debug mode to trace client connection issues.
  1. You must login as the root user
  2. Run:
    ps -ef|grep dsrpc
    and get the process id (PID) of the dsrpcd daemon.
  3. Make sure that no one is connected to InfoSphere DataStage by typing:
    netstat -a |grep dsrpc
    The only thing you should see is the dsrpcd daemon itself in LISTEN mode
  4. Once there are no more connections, kill the dsrpcd using:
    kill <pid>
  5. cd to the DSEngine directory
  6. Source the dsenv file by typing:
    . ./dsenv
  7. Restart the dsrpcd daemon in debug mode by typing:
    nohup bin/dsrpcd -d9 > /tmp/trace.out 2>&1 &
  8. Type:
    ps -ef|grep dsrpc
    and be sure the daemon is running in debug mode
  9. Try your connection again. The output of the tracing will be in /tmp/trace.out
  10. Once you are finished with the trace, the easiest way to take the daemon out of debug mode is to stop and restart the InfoSphere DataStage server
    bin/uv -admin -stop
    bin/uv -admin -start

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