rscd - <Server_Name> 17888 SYSTEM (Not_available): (Not_available): InitAgentNet: ERROR: Unable to open main agent socket (_net_open failed). You may have another daemon already running or a lingering (previously connected) client.
Can you please confirm the RSCD Version installed on this server? Is the RSCD agent service running? Please attach or go through rscdsvc.log too.
1 of 1 people found this helpful
had you checked if an other application uses the same port that your BSA Agent uses? it look like you have a listning problem. If you're using the default port 4750 check if there is an application qlickview, quickvew or something like that... running on the same port.
You have not confirmed the RSCD version. Also, it seems your target server is Widows 7?
rscd - <Server_Name> 17068 SYSTEM (Not_available): (Not_available): Platform Details: x86_64;<Server_Name>;6.1;WindowsNT;7601;x86_64
Please validate and paste output of the below commands here:
On Application Server: agentinfo <server_name>
On target server: netstat -anp | grep 4750
netstat -anp | grep rsc
Target device is windows server 2008 machine.
1 of 1 people found this helpful
can you check the application name listning on 4750? if it's an other application...you can use PID
yes, netstat -p will provide you the program using the specific port on Windows machines.
Also, did you get a chance to look into the Event Viewer logs for the service/program rscd? Any chance to reinstall the agent?
that's not correct - on windows:
-p proto Shows connections for the protocol specified by proto; proto may be any of: TCP, UDP, TCPv6, or UDPv6. If used with the -s option to display per-protocol statistics, proto may be any of: IP, IPv6, ICMP, ICMPv6, TCP, TCPv6, UDP, or UDPv6.
on linux - will show the process.
you want to use the -o option on windows:
netstat -ano. that will give you the pid which you can then run tasklist /fi "pid eq thepid"
That i tried ans sent the screen shot in above post. and we found the there are two process RSCDSvc and RSCD. this RSCD process is getting stopped and started automatically we tried to kill the process even it's getting restart in seconds time interval. we are thinking this may be the cause. but we are unable to resolve the issue. we reinstalled the agent even then same behavior. Please suggest
the rscdsvc is the watcher process. the service starts that process and then starts the rscd. if the rscd fails to start it will try and restart it 50 times and then stop.
so when there is no rscd.exe or rscdsvc.exe running on the box, is there any process listening on 4750 ?
we can try to get more debug out of the rscd - in the c:\windows\rsc\log4crc.txt you can edit the log level for the rscd line from info1 to debug, and also change the rollmaxfiles for the rscd log to 100. then delete all the rscd.log files, start the agent and let the watch try the restarts. after it finally fails, zip up all the rscd.log* files and attach.
thank you for your support and suggestion on the posted issue. issue got resolved now as we found port was occupied by process SYSTEM, and it was not getting closed so we changed the port and started the service it got started and PAJ is also success.
very much thank full to you all....