Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

loss of control process ifind.exe

Status
Not open for further replies.

mdeneen

IS-IT--Management
Mar 12, 2008
9
0
0
US
Loss of control process ifind.exe. Possible causes: 1. The control process has unexpectedly died. Check dr watson log or core file. 2. The communication to the control process machine bld-1440-web55.corpdmz.com might have gone down due to network errors. 3. If the machine bld-1440-web55.corpdmz.com is a cluster, it may have failed over. 4. The machine bld-1440-web55.corpdmz.com may have rebooted.


I have all ports open, so communication is fine. I've reinstalled the comvault agent and reconfigured it on the commserv end...still get the loss of control process ifind.exe error...

Any ideas?
 
here you go;-

KB Article ID: 10975
Article Type: Troubleshooting
Published: 6/25/2007 3:15:37 PM


Loss of control process ifind.exe.
Description:
File system backup jobs fail and show Dangling Cleanup as their status with the following error:

Loss of control process ifind.exe. Possible causes: 1. The control process has unexpectedly died. Check dr watson log or core file. 2. The communication to the control process machine may have rebooted.

You may also see the following event message:

Processes for job [] were forcefully terminated.

Cause:
The ifind.exe process runs in the initial stages of File System backups to gather a list of files on the computer. This error indicates that ifind.exe has not responded to JobManager in a timely fashion.

The most common cause for this error is when the client's Event Manager service (EvMgrC.exe) is down or unresponsive.

In other situations the process may be dying due to a mismatch in binaries or you may see that there are multiple instances of ifind.exe running.
Resolution:
First, check the Process tab of Windows Task Manager on the client computer to see if there are multiple copies of ifind.exe running. If you see multiple copies of ifind.exe, please select each of them and click End Process to kill these processes.

Check the client computer's Galaxy services. Client Event Manager service might be down, or if it is still running might be hung. Restart the services on the client.

Resume the job. If the job continues to fail with the same error, the problem may be due to a mismatch in binaries or involve network issues. Please gather the logs for the job in question and contact software support for assitance.





Birky
CommVault Certified Engineer
 
Ok,

It doesnt have multiple Ifind.exe instances and I've tried restarting the services as well as reinstalling commvault all together.
I've had all 8400-8404 ports opened and i can ping and telnet back and forth between commserv and the server, still get the error.

3148 13d4 03/12 14:24:39 90558 Service -> RESUMED <- Resumed by user
3148 13d4 03/12 14:24:39 ##### Servant WakeUp operation completed in [0] seconds. Number of jobs affected=[1]
3148 5a0 03/12 14:24:40 90558 Scheduler Phase [4-Scan] started on [bld-1440-web55.corpdmz.com] - ifind.exe -j 90558 -a 2:831 -t 1 -d dfw-bkup-apps58.drhorton.com -r 0 -ab 0 -i 1 -cs bld-bkup-comm51 -jt 90558:4:10 -mountPath
3148 a5c 03/12 14:28:22 90558 Liveliness [Control Timeout] on Liveliness
3148 a5c 03/12 14:28:22 90558 Liveliness Job [90558:4:10] did not register in timeout period
3148 a5c 03/12 14:28:22 90558 Control -- TERMINATE -- (killing processes -- [IsAlive] operation)
3148 a5c 03/12 14:28:22 90558 Control Registration Status [Unknown]
3148 a5c 03/12 14:28:22 90558 Service -> DANGLING JOB [90558:4:10] <-- Detected as part of a [IsAlive] operation.
3148 1228 03/12 14:28:22 90558 Scheduler Set pending cause [Loss of control process ifind.exe. Possible causes: 1. The control process has unexpectedly died. Check dr watson log or core file. 2. The communication to the control process machine bld-1440-web55.corpdmz.com might have gone down due to network errors. 3. If the machine bld-1440-web55.corpdmz.com is a cluster, it may have failed over. 4. The machine bld-1440-web55.corpdmz.com may have rebooted.]::Client [bld-bkup-comm51] Application [JobManager] Message Id [318767703] RCID [0] ReservationId [0].
3148 13ac 03/12 14:28:22 90558 Scheduler Phase [Failed] message received from [Job Manager] Module [JobManager] Token [90558:4:10] restartPhase [0]
3148 13ac 03/12 14:28:23 90558 JobSvr Obj Phase [4-Scan] for Backup Job Failed. Backup will continue with phase [Scan].






However maybe it is still network? This server is in our DMZ. So it is in the CORPDMZ domain whereas the commserv and backup systems are in our corporate domain. But we have other systems that seem to work fine like this.
 
try setting data interface pairs (in the control panel) with IP addresses instead of hostnames



Birky
CommVault Certified Engineer
 
still no go, i setup interface pairs between both the media agent and server and the commserv server and the target server.

Loss of control process ifind.exe. Possible causes: 1. The control process has unexpectedly died. Check dr watson log or core file. 2. The communication to the control process machine bld-1440-web55.corpdmz.com might have gone down due to network errors. 3. If the machine bld-1440-web55.corpdmz.com is a cluster, it may have failed over. 4. The machine bld-1440-web55.corpdmz.com may have rebooted.

still getting that.
 
try to simplify it
Remove DIP and rem out host file entries
If still pingable, try to backup a single file


If still a no go, I would remove all updates and reinstall SP4
What version of CV is this?

If 6.1 and above you can right click and "Check connectivity" from the all tasks.

Let us know
 
Connectivity check passes.
It is 6.1

I'm going to try reinstalling everything agent wise on the target server.

Last time I watched it though, i never see Ifind.exe process start up. Although I can ping, telnet to the 8400-8403 ports and the connectivity check works. So I'm not sure whats up.
I'll repost when I get a chance to reinstall it.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top