Impossible to restart the DataStage server

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
eoyylo
Participant
Posts: 57
Joined: Mon Jun 30, 2003 6:56 am

Impossible to restart the DataStage server

Post by eoyylo »

Hi,
excuse me if exist an another post about this particular problem, but I don't find it.

I stopped the datastage server but now it is impossible to restart it. When i try to start the server all works fine but when i try to use the client i obtain the next error: RPC demon is not running

I controlled that:
- I waited over than 30 second ( I waited over 30 minuts) between shutdown and start
- there aren't client connections at the server
- the command "netstat -na |grep 31538" doesn't return any result
- the command "ps -eaf |grep dsadm" doesn't return any result
- the command "ps -eaf |grep phantom" doesn't return any result
- the command "netstat -a | grep rpc" return

tcp 0 0 h3mih012.uvrpc .1131 FIN_WAIT_2

48b70280 dgram 0 0 42cac1c0 0 0 0 /opt/dcelocal/var/rpc/local/17058/c-3/shared
437c1280 dgram 0 0 431234c0 0 0 0 /opt/dcelocal/var/rpc/local/01297/reaper
437c1580 stream 0 0 4315aac0 0 0 0 /opt/dcelocal/var/rpc/local/s-0/135
437c1880 dgram 0 0 4315a7c0 0 43062a40 0 /opt/dcelocal/var/rpc/local/s-3/135
437c1b80 dgram 0 0 43251040 4303e5c0 0 0 /opt/dcelocal/var/rpc/local/01297/c-3/7000
437c1d00 dgram 0 0 42cb5dc0 0 4303edc0 0 /opt/dcelocal/var/rpc/local/01297/c-3/shared
437c1e80 dgram 0 0 4323c700 4303e5c0 0 4303e340 /opt/dcelocal/var/rpc/local/01297/c-3/7002
4e392580 stream 0 0 0 5e5d5ac0 0 0 /opt/dcelocal/var/rpc/local/s-0/49381
43792980 dgram 0 0 436a1880 0 0 0 /opt/dcelocal/var/rpc/local/01319/reaper
43792c80 stream 0 0 43660dc0 0 0 0 /opt/dcelocal/var/rpc/local/s-0/49159
438350c0 dgram 0 0 42e07400 0 0 0 /opt/dcelocal/var/rpc/local/s-3/49258
48d95240 dgram 0 0 4321f640 0 0 0 /opt/dcelocal/var/rpc/local/25922/reaper
48d95540 stream 0 0 4309f100 48803200 0 0 /opt/dcelocal/var/rpc/local/25922/c-0/7001
438356c0 dgram 0 0 436a6f40 0 0 0 /opt/dcelocal/var/rpc/local/01329/reaper
43835b40 dgram 0 0 436a6a00 4303e2c0 0 0 /opt/dcelocal/var/rpc/local/01557/c-3/7000
43835cc0 dgram 0 0 43a02e80 0 0 0 /opt/dcelocal/var/rpc/local/01557/reaper
437f6040 dgram 0 0 438afb80 0 0 0 /opt/dcelocal/var/rpc/local/01345/reaper
437f61c0 dgram 0 0 43a06a00 0 0 0 /opt/dcelocal/var/rpc/local/01658/reaper
438c6100 dgram 0 0 43964a00 0 0 0 /opt/dcelocal/var/rpc/local/01557/c-3/shared
437f6340 dgram 0 0 42cd7dc0 0 0 0 /opt/dcelocal/var/rpc/local/25829/reaper
43d977c0 dgram 0 0 48bc2640 4303e3c0 0 0 /opt/dcelocal/var/rpc/local/01319/c-3/7001
482e8500 dgram 0 0 43322400 4303e3c0 0 4848d380 /opt/dcelocal/var/rpc/local/17058/c-3/7001
482e8c80 dgram 0 0 434c14c0 0 0 0 /opt/dcelocal/var/rpc/local/s-3/49744
482e8e00 stream 0 0 42b38940 0 0 0 /opt/dcelocal/var/rpc/local/s-0/49379
48ceb200 stream 0 0 0 48803180 0 0 /opt/dcelocal/var/rpc/local/s-0/49379
48ceb680 dgram 0 0 432f5ac0 4303e3c0 0 4848d200 /opt/dcelocal/var/rpc/local/25829/c-3/7001
4898d040 stream 0 0 43050a00 0 0 0 /opt/dcelocal/var/rpc/local/s-0/49381
4898d640 dgram 0 0 43402640 0 4303e440 0 /opt/dcelocal/var/rpc/local/s-3/49747
4898d7c0 dgram 0 0 42cc2940 0 0 0 /opt/dcelocal/var/rpc/local/25829/c-3/shared
48a0f0c0 dgram 0 0 430d6ac0 0 0 0 /opt/dcelocal/var/rpc/local/17058/reaper
4904f1c0 stream 0 0 463ad700 5e5d5340 0 0 /opt/dcelocal/var/rpc/local/25922/c-0/9960
43a2f500 stream 0 0 43927700 0 0 0 /opt/dcelocal/var/rpc/local/s-0/2121
43a2f800 dgram 0 0 4393c340 0 0 0 /opt/dcelocal/var/rpc/local/s-3/2121


where is my mistake?

Thanks in advance

Regards
aartlett
Charter Member
Charter Member
Posts: 152
Joined: Fri Apr 23, 2004 6:44 pm
Location: Australia

Post by aartlett »

eoyylo,
It looks to me you have an open IP port, and in my experience the only way to fix this problem is to bounce the whole Unix box.

If a netstat -a|grep rpc shows a datastage port waiting to close (normally someone was logged on when you stopped datastage) and it wont clear in a reasonable time, you are SOOL and booting the unix box (take that anyway you like) is your last option.

There may be another way around it, but my sysadmins in my last job couldn't clear the IP port (on a SUN box) and Ascential could only offer the solution of last resort.
Andrew

Think outside the Datastage you work in.

There is no True Way, but there are true ways.
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

Identify the system holding the port in the DataStage Server and bounce that system. This, most of the time, releases the lock.
eoyylo
Participant
Posts: 57
Joined: Mon Jun 30, 2003 6:56 am

Post by eoyylo »

Hi,
I try to shutdown the unix server and now all work fine. (Thanks aarlet)

How can I identify the process that lock the port in Datastage?

Thanks

Mario
trokosz
Premium Member
Premium Member
Posts: 188
Joined: Thu Sep 16, 2004 6:38 pm
Contact:

Post by trokosz »

You brought DataStage down more than likely while someone was running a Job and that left a ade shared memory segment orphaned. This is what causes the issue. Rebooting the server regenrates the shared menory but unnecessary....Ascential has a process to recreate shared memory or removing old ade so call them...no need to reboot...

You need to ps -ef | grep ds before you shutdown and make sure all people and Jobs ar out....
Post Reply