I'm running DSEE 7.51A on a UNIX server and when I did a " uv -admin -info" I noticed these phantom segments. What are they? How would I get rid of them? Thanks.
11 phantom printer segments!
DSnum Uid Pid Ppid C Stime Tty Time Command
62962 dsadm 2574 2573 0 Jul 14 ? 0:12 dsapi_slave 8 7 0
46727 dsadm 18809 18808 0 Jul 06 ? 0:02 dsapi_slave 8 7 0
53197 dsadm 12339 12338 0 Jul 19 ? 0:15 dsapi_slave 8 7 0
60033 dsadm 5503 5502 0 Jul 14 ? 0:01 dsapi_slave 8 7 0
64219 dsadm 1317 1316 0 Aug 03 ? 0:12 dsapi_slave 8 7 0
61055 dsadm 4481 4480 0 Aug 03 ? 0:05 dsapi_slave 8 7 0
61735 dsadm 3801 3800 0 Aug 03 ? 0:02 dsapi_slave 8 7 0
61250 dsadm 4286 4285 0 Aug 03 ? 0:02 dsapi_slave 8 7 0
61047 dsadm 4489 4488 0 Aug 03 ? 0:02 dsapi_slave 8 7 0
46835 dsadm 18701 18698 0 10:10:09 ? 0:01 dsapi_slave 8 7 0
45372 dsadm 20164 20163 0 10:38:45 ? 0:03 dsapi_slave 8 7 0
phantom printer segments
Moderators: chulett, rschirm, roy
62962 dsadm 2574 2573 0 Jul 14 ? 0:12 dsapi_slave 8 7 0
46727 dsadm 18809 18808 0 Jul 06 ? 0:02 dsapi_slave 8 7 0
dsapi_slave 8 7 0 usually refers to client application like Director or Designer that are open. As these client applications constantly chat with the server to report any changes or updates you have these phantom processes.
you will be able to kill them as you can kill any of your unix processes by loging in with your user id or in this case dsadm then executing kill 2574 in some cases kill -9 2574 from your cmd prompt on your server.
HTH
Novice
46727 dsadm 18809 18808 0 Jul 06 ? 0:02 dsapi_slave 8 7 0
dsapi_slave 8 7 0 usually refers to client application like Director or Designer that are open. As these client applications constantly chat with the server to report any changes or updates you have these phantom processes.
you will be able to kill them as you can kill any of your unix processes by loging in with your user id or in this case dsadm then executing kill 2574 in some cases kill -9 2574 from your cmd prompt on your server.
HTH
Novice
Hi jtenshaw,
I did a search in the forum based on "phantom printer segments" and on "printer segements". I found a post by admin:
I did a search in the forum based on "phantom printer segments" and on "printer segements". I found a post by admin:
Code: Select all
Most of the message is normal. The only different thing is the PRINTER memory segment removed.
What this means is that some DataStage process before it finished in an errant manner.
For historic reasons, every DataStage process keeps track of certain elements of its current state resident in a shared memory segment, which was called a Printer memomy segment (again, the name came from historic reasons).
When the DS process starts/stops it either creates or destroys the process.
If a process doesnt terminate properly, that segment may not be removed.
As part of the startup of any new process, we validate whether there is an existing segment. If there is one, this could indicate that the process started is a child process. So, we check to see if the process which created the segment is still existing.
If the process is no longer alive, we assume that something wrong has occurred. We then invoke a cleanup process that performs the proper cleanup of that leftover process.
It is during this cleanup (actually, it is the dsdlockd process, the deadlock/cleanup daemon) that you see this error message displayed.
By itself, it is not a problem, as it represents proper behavior. However, for some reason you are finding printer shared memory segments being left behind, which could indicate some other problem.