Why does STM report that it is unable to connect to the host due to an unexpected error?
(This problem is fixed in IPR 9806.) STM can experience problems as a result of extra files being left on the system by the software update utility swinstall and the frecover utility. The directory /usr/sbin/stm/uut/bin/sys should contain only the three files: diagmond, diaglogd, and memlogd. If there are other files in this directory, they should be removed (or moved out of this directory). Files to be removed typically have names like EMYa01203 (the exact name will vary). Other files to be removed have names like diagmond.1284 (the string “diagmond,” “diaglogd,” or “memlogd”, with a number appended). • First stop the diagnostics daemon using the command: /sbin/init.d/diagnostics stop • Remove the files which shouldn’t be there. • If removing the extra files fails due to “text file busy,” then you may need to: • ps -ef | grep diaglogd # to find the Process ID (PID) for diaglogd • kill -2
Related Questions
- When I select computers in the Network Browser, it sometimes takes a long time for LogWatcher to connect or report an error. Why is this?
- Why do I get error messages like: Unable to locate server, Cannot connect to host or Server does not have a DNS entry?
- Why does STM report that it is unable to connect to the host due to an unexpected error?
