8/10/2005
Unable to Connect to Background Process
Generally, Apple releases reliable software that's been properly tested and is bug free. Rival companies like Microsoft can't exactly make that same claim. But everyone once in awhile, a major bug makes its way into one of Apple's programs and leaves many people scratching their heads and calling tech support.Users of Final Cut Pro and DVD Studio Pro may have encountered the "Unable to Connect to Background Process" error when trying to submit video files to the Compressor utility. This is a common problem caused by older versions on the Compressor application being accidentally installed over a newer version. The only way to prevent this issue is to run custom installs of all of Apple's Pro Applications and related updates and de-select Compressor. However, for many of us, it's too late for that.
Apple is aware of the issue and has a support article on their website called Compressor - Cannot submit job from Batch Window. In the article they make some suggestions on how to fix this "Unable to Connect to Background Process" problem. Apple's solutions are to trash preference files and reinstall everything.Apple's suggestions suck for several reasons:
- they are very time consuming
- don't always work for every situation
- don't address the real issue
The best solution is to install a newer version of Compressor and overwrite any older software components. Compressor comes with Final Cut Studio. Upgrading to a newer version of Compressor is your BEST solution to this problem.
However, if you don't feel like shelling out lots of money for the upgrade, here's a solution that could fix several of the "Unable to Connect to Background Process" problems you might encounter.
WARNING: Only advanced users should attempt this. If you attempt this hack, you must be prepared to undo it!!! (see below for undo options). Don't do this if you are on a tight deadline or in the middle of a major project.
- Click on the Finder icon in your Dock
- Select "Go to folder" from the Go menu. (Go > Go to Folder)
- Type "/etc/" (without the quotes) and press return
- Find the "hostconfig" file and COMMAND drag a copy to your desktop.
- Rename the file to "hostconfig.old"
- Drag the "hostconfig.old" file back into the etc folder. You may be prompted for an admin username and password.
- Restart your computer
- Open Compressor and submit a batch.
If your computer restarts in Command Line Mode, you can rename the "hostconfig.old" file back to "hostconfig" from the Command Line if you don't have a Journaled hard drive.
Just do the following:
The other undo option is to connect a second computer to the problem machine with a Firewire cable. Restart the problem machine and hold down the "T" key to boot it in Target Mode. The problem machine will mount as an external hard drive. Go into the computer and rename the "hostconfig" file and restart.
- type "mount -u -w root_device" at the prompt (without the quotes)
- press enter
- type "cd /etc"
- press enter
- then type "sudo mv hostconfig.old hostconfig"
- press enter
- provide your admin password if asked
- type "reboot" and your done
Good luck! Maybe someday Apple will fix this problem.
Post a Comment
permanent link |
10:33 AM
|
MethodShop.com
|
MethodShop.com
If you follow these instructions, you may end up without a hostconfig file in your /etc directory causing your system to not be able to boot properly.
When I tried this my system rebooted to a command line in read only mode. The only way I was able to fix it was to connect via a firewire cable, reboot in target mode, and recopy the file using the terminal.
Looking at the hostconfig file carefully, I don't see how this would fix the problem it says it will fix. I'd like to hear the original poster's explanation as to what exactly this will do.
When I tried this my system rebooted to a command line in read only mode. The only way I was able to fix it was to connect via a firewire cable, reboot in target mode, and recopy the file using the terminal.
Looking at the hostconfig file carefully, I don't see how this would fix the problem it says it will fix. I'd like to hear the original poster's explanation as to what exactly this will do.
[*] posted by 
: August 11, 2005 2:18 PM
: August 11, 2005 2:18 PM
Be careful doing this. I tried this technique and then my system could only boot to the the UNIX command line. Had a hell of a time fixing the problem (UNIX novice here).
[*] posted by : August 11, 2005 5:54 PM
: August 11, 2005 5:54 PM
I got this tip from a friend who works at TekServe. Apple support reps sometimes have people remove the "hostconfig" file as a last resort. Most people don't run into any problems ...
However, if your computer restarts in Command Line Mode, you can rename the "hostconfig.old" file back to "hostconfig" from the Command Line.
Just do the following:
1) type "cd /etc" at the prompt (without the quotes)
2) press enter
3) then type "sudo mv hostconfig.old hostconfig"
4) press enter
5) provide your admin password if asked
6) type "reboot" and your done
However, if your computer restarts in Command Line Mode, you can rename the "hostconfig.old" file back to "hostconfig" from the Command Line.
Just do the following:
1) type "cd /etc" at the prompt (without the quotes)
2) press enter
3) then type "sudo mv hostconfig.old hostconfig"
4) press enter
5) provide your admin password if asked
6) type "reboot" and your done
Definitely did NOT work for me (OS X 10.4.2)! As described, the computer would only boot to unix shell. However the fix did NOT work either, as the filesystem is mounted in read-only mode, where even the superuser cannot make any modifications (so "sudo" is useless).
To make it work, I first had to change the access mode of the filesystem: "mount -u -w boot_device" and then only the "sudo mv ..." command can execute correctly. Well, now I'm real happy my Mac boots correctly again, however Compressor still doesn't work ...
To make it work, I first had to change the access mode of the filesystem: "mount -u -w boot_device" and then only the "sudo mv ..." command can execute correctly. Well, now I'm real happy my Mac boots correctly again, however Compressor still doesn't work ...
[*] posted by : September 09, 2005 4:35 AM
: September 09, 2005 4:35 AM
you totally saved my ass. it worked! i dont know why or how, but it worked. thanks again. now i just need to download Compressor 2.0 off BitTorrent.
[*] posted by : September 21, 2005 9:42 PM
: September 21, 2005 9:42 PM
bec people had both good and bad stuff to say about this technique, i was scared. i waited until my Unix master friend came over and we tried it on 2 machines.
the first machine, a g5, worked fine after we did it. but the second machine rebooted in unix mode. we fixed it using the firewire fix. at least i have one machine with Compressor working.
thanks kids.
the first machine, a g5, worked fine after we did it. but the second machine rebooted in unix mode. we fixed it using the firewire fix. at least i have one machine with Compressor working.
thanks kids.
i had this problem over the weekend when i install tiger. i am still using compressor 1.2.1 and didn't feel like taking a chance of screw up my system or wasting money just to buy compressor 2 which is supposedly slower and has some bugs in it.
so i went into the preferences in compressor and unchecked "Auto Launch Batch Monitor"
I just tried rendering a project and now everything seems to be working great. You just have to click the batch monitor button manually to bring up the window once you've submitted.
I don't know if this will work for anyone else, but its worth a try.
so i went into the preferences in compressor and unchecked "Auto Launch Batch Monitor"
I just tried rendering a project and now everything seems to be working great. You just have to click the batch monitor button manually to bring up the window once you've submitted.
I don't know if this will work for anyone else, but its worth a try.
[*] posted by : October 17, 2005 11:31 AM
: October 17, 2005 11:31 AM
Like many others, I have run into the "Unable to Connect to Background Process" error when trying to submit video files to the Compressor utility. I've looked all over the net, including the Apple web site for a fix and found nothing truly useful. The best Apple seemingly can do is to ask the user to reinstall the software.
After many hours of reading and testing, I think I have found the fix for this problem. When you install Final Cut Pro HD 4.5 with Compressor, at the end you get a message box asking you if you would like to fix Qmaster. You would think that this would fix the Qmaster problem, but it doesn't seem to do so. This is the reason that you get the background process error message -- the Qmaster process is not running in the background, and this is what Compressor needs to work properly. What you can do to get it working again is run this command in a Terminal window (you will need your admin password):
sudo /Library/StartupItems/Qmaster/Qmaster start
This will only work until you restart your computer again.
To get the Qmaster working properly again permanently, what you can do is this ... I haven't tried these steps, but I’m sure they would work. Remove the Qmaster folder from the StartupItems folder and restart the computer. After the computer has restarted, put the Qmaster folder back in the StartupItems folder and restart again. This time you will get the message box to fix Qmaster. If that doesn't work, you can (I have done this and it works) copy the Qmaster folder from a computer that has Compressor working properly and replace it with the one that’s not working, restart to get the message box to fix the Qmaster again.
That’s all you need to do to get Compressor working again, and not do a full reinstall like Apple asks us to do.
X@vier
After many hours of reading and testing, I think I have found the fix for this problem. When you install Final Cut Pro HD 4.5 with Compressor, at the end you get a message box asking you if you would like to fix Qmaster. You would think that this would fix the Qmaster problem, but it doesn't seem to do so. This is the reason that you get the background process error message -- the Qmaster process is not running in the background, and this is what Compressor needs to work properly. What you can do to get it working again is run this command in a Terminal window (you will need your admin password):
sudo /Library/StartupItems/Qmaster/Qmaster start
This will only work until you restart your computer again.
To get the Qmaster working properly again permanently, what you can do is this ... I haven't tried these steps, but I’m sure they would work. Remove the Qmaster folder from the StartupItems folder and restart the computer. After the computer has restarted, put the Qmaster folder back in the StartupItems folder and restart again. This time you will get the message box to fix Qmaster. If that doesn't work, you can (I have done this and it works) copy the Qmaster folder from a computer that has Compressor working properly and replace it with the one that’s not working, restart to get the message box to fix the Qmaster again.
That’s all you need to do to get Compressor working again, and not do a full reinstall like Apple asks us to do.
X@vier
[*] posted by : October 20, 2005 8:55 AM
: October 20, 2005 8:55 AM
Yes! Thanks last poster. Compressor complains about a process being inaccessible. It's interesting this wasn't fixed by Software Update in some form.
Be careful because the original instructions are open to interpretation.
4. Find the "hostconfig" file and COMMAND drag a copy to your desktop.
5. Rename the file to "hostconfig.old"
Following to the letter, I interpreted the copy to be renamed (not a novice, Windows admin, have not slept a while however).
Next reboot came up with a flashing globe for a while (netboot, I would suppose it was looking for a netboot server and dhcp...). And then the flashing folder/question mark.
Ran the first aid apprehensively, did nothing.
Rebooted with Option key, selected the hard drive, came up as usual.
Grr macs are not nice. At least I can get a nice blue screen for half a second to try to determined why Windows failed. (Yes yes, logs, terminal, whatever...)
Be careful because the original instructions are open to interpretation.
4. Find the "hostconfig" file and COMMAND drag a copy to your desktop.
5. Rename the file to "hostconfig.old"
Following to the letter, I interpreted the copy to be renamed (not a novice, Windows admin, have not slept a while however).
Next reboot came up with a flashing globe for a while (netboot, I would suppose it was looking for a netboot server and dhcp...). And then the flashing folder/question mark.
Ran the first aid apprehensively, did nothing.
Rebooted with Option key, selected the hard drive, came up as usual.
Grr macs are not nice. At least I can get a nice blue screen for half a second to try to determined why Windows failed. (Yes yes, logs, terminal, whatever...)
[*] posted by : November 07, 2005 12:08 PM
: November 07, 2005 12:08 PM
Tottaly screwed my system and both undo methods didn't work. My advice is dont attempt it! or you'll regret it!!!
[*] posted by : November 22, 2005 11:04 AM
: November 22, 2005 11:04 AM
None of these fixes worked for me... It would have been good to know that two hours ago.
[*] posted by : March 23, 2006 3:06 PM
: March 23, 2006 3:06 PM
What ever your "localhost:/ root#" problem. Just make sure the name of the hostconfig file is renamed exactly "hostconfig".
I don't use compressor, but this link helped me solve my boot problem on my Powerbook.
S
I don't use compressor, but this link helped me solve my boot problem on my Powerbook.
S
[*] posted by : March 24, 2006 6:44 AM
: March 24, 2006 6:44 AM
the Qmaster solution worked perfectly for us. Thanks very much.
[*] posted by : April 03, 2006 10:56 PM
: April 03, 2006 10:56 PM
Did not work at all but at least my machine came up OK.
Neither did starting Qmaster....
This sucks. Wish I had bought an AVID system.
Neither did starting Qmaster....
This sucks. Wish I had bought an AVID system.
[*] posted by : April 16, 2006 1:23 AM
: April 16, 2006 1:23 AM
After having no success with Apple's instructions, I went a step further and deleted QMaster's Frameworks, QMaster's Startup Items and QMaster's Application Support folders from the Library (in addition to what Apple says to throw away). I rebooted after dumping the trash, re-installed Compressor and QMaster, downloaded the Software Updates, re-booted - - - It finally worked! I'm not sure if it was the additional deletions or the multiple re-boots that fixed it though. I hope this works for others.
[*] posted by : May 22, 2006 8:57 PM
: May 22, 2006 8:57 PM
well, i have just purchased a mirror drive door g4 dual 2 gig machine with 1 gig ram, and started doing a final cut pro job and was eagerly waiting to see the speed of my new beast in compressor, but low and behold... (insert buzzer noise here) i got the old "cannot connect blah blah) .. not being one to take advice from the net i was sceptical, however as i only got the system a day ago, and i can re install in a heartbeat.. what the hey! ---- guess what .... it friggin worked! now all i can you tell is .. my situation was a little different.. i had 2 hostconfig files .. one as hostconfig and one as hostconfig~ so i removed both. and changed one of them to .old and wacked it back in.. and hey presto .. im compressing from FCPRO 4.5 HD and im running 10.3.9 - i can understnad how this may not work for all.. but you saved my but tonight and i thank you!
[*] posted by : June 16, 2006 12:17 PM
: June 16, 2006 12:17 PM
Definitely did NOT work for me (OS X 10.4.2)! As described, the computer would only boot to unix shell. However the fix did NOT work either, as the filesystem is mounted in read-only mode, where even the superuser cannot make any modifications (so "sudo" is useless).
To make it work, I first had to change the access mode of the filesystem: "mount -u -w boot_device" and then only the "sudo mv ..." command can execute correctly. Well, now I'm real happy my Mac boots correctly again, however Compressor still doesn't work ...
Holy crap ... after spending a long time trying to fix this "fix" from the command line, I realised that it should be:
"mount -u -w root_device" and not "mount -u -w -boot_device" as was posted. That typo took me fifteen minutes of panic ...
To make it work, I first had to change the access mode of the filesystem: "mount -u -w boot_device" and then only the "sudo mv ..." command can execute correctly. Well, now I'm real happy my Mac boots correctly again, however Compressor still doesn't work ...
Holy crap ... after spending a long time trying to fix this "fix" from the command line, I realised that it should be:
"mount -u -w root_device" and not "mount -u -w -boot_device" as was posted. That typo took me fifteen minutes of panic ...
[*] posted by : August 23, 2006 6:50 PM
: August 23, 2006 6:50 PM
X@vier:
>run this command in a Terminal window
>sudo /Library/StartupItems/Qmaster/Qmaster start
>This will only work until you restart your computer again.
Worked!
Thanks!
>run this command in a Terminal window
>sudo /Library/StartupItems/Qmaster/Qmaster start
>This will only work until you restart your computer again.
Worked!
Thanks!
[*] posted by : May 05, 2007 7:45 AM
: May 05, 2007 7:45 AM
REGARDING COMPRESSOR ERROR
"Unable to connect to background process"
I ran into this problem over two years ago with a completely different generation of software and hardware. what a joke that apple has not fixed this for compressor 2. what a huge waste of time. I went to the apple page and got rid of the old software reinstalled everything entered all my stupid codes and it didnt work!
the simple terminal command posted up by x@vier worked for me. dont forget the space after sudo
sudo /Library/StartupItems/Qmaster/Qmaster start
basically prodding qmaster to get off its ass.. Im putting the command in my notes for future reference.
thank you APPLE for wasting my time on the same error twice two years apart
OS 10.4.9 on a Powerbook G4 1.67GHZ
Compressor 2.0.1 FC 5
"Unable to connect to background process"
I ran into this problem over two years ago with a completely different generation of software and hardware. what a joke that apple has not fixed this for compressor 2. what a huge waste of time. I went to the apple page and got rid of the old software reinstalled everything entered all my stupid codes and it didnt work!
the simple terminal command posted up by x@vier worked for me. dont forget the space after sudo
sudo /Library/StartupItems/Qmaster/Qmaster start
basically prodding qmaster to get off its ass.. Im putting the command in my notes for future reference.
thank you APPLE for wasting my time on the same error twice two years apart
OS 10.4.9 on a Powerbook G4 1.67GHZ
Compressor 2.0.1 FC 5
[*] posted by : May 24, 2007 3:45 AM
: May 24, 2007 3:45 AM
This worked great for me. I am processing a batch right now!
I also saw a "hostconfig~" in /etc/
whats that I wonder?
Mac OS X 10.4.9
2GHZ Intel Core Duo
1.25 SDRAM
I also saw a "hostconfig~" in /etc/
whats that I wonder?
Mac OS X 10.4.9
2GHZ Intel Core Duo
1.25 SDRAM
I tried both the hostconfig solution and the
sudo /Library/StartupItems/Qmaster/Qmaster start solution... Neither worked...
I am thinking about re-installing OSX and then re-installing FCP Studio from scratch, so it's a completely clean install... Will try that when I get back from Holiday...
sudo /Library/StartupItems/Qmaster/Qmaster start solution... Neither worked...
I am thinking about re-installing OSX and then re-installing FCP Studio from scratch, so it's a completely clean install... Will try that when I get back from Holiday...
NOTHING is working for me. AT ALL.
running OS 10.5.2, installed software updates, this is really driving me mad...
running OS 10.5.2, installed software updates, this is really driving me mad...
on 10.5.4. I'm running Compressor 2.0.
I'm getting the same problem except that I cannot get Qmaster to start, lots of forked error messages
I'm running the PPC version of Final Cut Studio 5.
See this post:
http://discussions.apple.com/thread.jspa?messageID=6685282
It looks like you need to run the Universal Binary on 10.5.x
I'm getting the same problem except that I cannot get Qmaster to start, lots of forked error messages
I'm running the PPC version of Final Cut Studio 5.
See this post:
http://discussions.apple.com/thread.jspa?messageID=6685282
It looks like you need to run the Universal Binary on 10.5.x
[*] posted by : August 21, 2008 9:47 AM
: August 21, 2008 9:47 AMPost a Comment
Links to this post:
YouTube
prevents viewers from downloading files off their site. But there
are ways around this. Here's a step-by-step tutorial on how to
rip video files off YouTube.com and convert them for your Video
iPod.
Wicked Lasers named their new flashlight the TORCH... and for good reason. The "TORCH" is technically a flashlight. It looks like a flashlight. Operates like a flashlight. But this is no ordinary flashlight. The TORCH is so bright that its beam can ignite flammable objects as fast as fire. 
The average teenager these days probably has no idea who poor old Wilford is. But if you grew up during the 80's, then you probably remember Wilford from movies like Cocoon, The Natural and his many Quaker Oats Oatmeal commercials. Does Wilford Brimley really look like a cat? You decide.
As Twitter continues to gain in popularity and users, those of us already on Twitter might find ourselves in a position where we have to explain Twitter to a non-techie type person like Grandma. So what do you say when someone asks you something silly like "What is the Twitter?" or "Are you taking the Twitter?"
Bugs tend to freak us out. Mosquitoes, spiders, wasps, centipedes... you name it. If it crawls, bites or buzzes anywhere near our faces, then we squirm, swat and run. But what's worse than a little bug crawling on or biting you? How about a really, really big one? Here are some of the biggest bugs on Earth. Enjoy!. 
Instead of having to go to a separate site or use a specific application like Second Life, ROCKETON turns the entire Internet into a virtual world for browser based avatars. 
If you're looking for an inexpensive, lightweight pair of earbuds with fantastic bass, then Radius' Atomic Bass earbuds are the earbuds of your dreams.
In a time when so-called MC's rap about their bank accounts or invent the latest dance craze to sell records, Lupe Fiasco is on the other side of the spectrum. It's refreshing to find a mainstream rapper dealing with non-commercial issues with the passion and sheer lyrical skill that Lupe exemplifies.
Want
to upgrade the RAM in your
Mac Mini? You can definitely save a few bucks by buying a stripped
down Mac Mini and upgrading the RAM yourself. But before you
can install that extra RAM, you'll need to take a walk down to
your local hardware store and grab a couple putty knives.
Need
something to watch on your iPod or iPhone? Here's a tutorial that
explains how to use a program called Handbrake to rip DVD's
into iPod compatible MPEG-4 video files.
Is a weak arm or physical stamina keeping you from taking your Nintendo Wii gaming experience to the next level? Perhaps you should look into getting the Nintendo Wii Nunchuck Controller. This accessory adds even more innovation to the next generation of gaming and does it all with less physical movement.
Are
you trying to eject your iPod from your computer but the "Do
Not Disconnect" won't go away? Don't worry, this is a common
problem with a fairly easy solution.
So
Napster's gone pay, KaZaA is chock-full of viruses and spyware,
and you need someplace to get your file sharing on. Luckily
for you, there's BitTorrent! Here's a
tutorial to get you started. 
