RSS feedThere are probably a dozen different things that can go wrong with Apple’s Compressor and Qmaster, and the web is filled with solutions for most of them. Except mine that is. So today I ripped apart Qmaster to find out once and for all what the problem is.
For reference sake, Qmaster is Apple’s queuing and distributed processing technology. Compressor, Apple’s multipurpose AV transcoder which comes with Final Cut and DVD Studio, uses Qmaster to queue and distribute audio and video transcoding tasks across multiple Macs in a network. Sounds pretty advanced doesn’t it? I mean a home business or hobbyist is probably not going to want to run a server farm dispatching service, when all they want to do is to convert their new video to MPEG2 (for DVD) or some iPod format. Problem is, that’s the default install for both Final Cut Pro and Final Cut Studio.
The problem with Qmaster, is when you export a video sequence from Final Cut to Compressor. Compressor asks which format you’d like to transcode to, and then tries to call Qmaster to make it all happen. Typically you then get an error dialog which says “Unable to connect to background process”, at which point Compressor cancels the job, and Final Cut returns you to editing mode.
Some solutions to this problem suggest exporting from Final Cut to an intermediary format, and then using Compressor stand alone to transcode, but this doesn’t bypass the problem. The problem isn’t with Final Cut or Compressor, it is with Qmaster.
Qmaster is required by Compressor, not Final Cut. One of the things that takes a while when debugging Qmaster, is running Final Cut everytime, creating a sequence, exporting to Compressor, setting the transcoding format, and then finally clicking submit. There’s an easier way to see if the problem has been fixed.
Launch Compressor on its on, don’t bother with Final Cut. Go to Compressor’s Preferences, and change Default Destination to Desktop, change Cluster Options to Never copy source to Cluster, and set the Default Setting to Web Download (QuickTime 7 compatible) –> H.264 100Kbps, then click Apply. Exit from Compressor, and drag a small .jpg picture to your desktop. Now you’re ready to go.
To test if the “Unable to connect to background process” problem has been fixed, launch Compressor on its own, select Import file… from the File menu, click on the .jpg on the desktop, and click Open. This will return you to the Compressor Batch window, where you can simply click on Submit. If you don’t see the error dialog, then you’re done, and please leave a comment here to say what worked for you.
If you still have a problem, use the above test after each thing you test from the following huge list of possible solutions.
For the rest of this post, I was originally using Final Cut Studio 5.1.1, but have since gone back to 5.0 with the 5.0.4 update.
Qmaster the dark art
Qmaster starts up when your Mac starts up. In fact there’s a startup shell script in /Library/StartupItems/Qmaster on your boot volume, called Qmaster, which at Mac boot time grabs the file /Library/Application Support/Apple Qmaster/qmasterconfig, which contains the pathname of the Qmaster daemon (/usr/sbin/qmasterd), and some basic configuration variables. It thens launches the daemon.
At this point, the Qmaster daemon should be running. Once the boot has finished, you can launch Terminal and enter top to see the process list, which should include a number of related Qmaster processes, including one or more instances of qmasterd. An easier way to check if Qmaster is running, is to use finder to launch /Applications/Utilities/Activity Monitor, select All Processes from the select menu, and then enter qmaster into the search field. You should at least get one instance of qmasterd.
If Qmaster is not running, then there’s a few things you can try to get it running.
Qmaster is not running
- Apple recommends the first thing you do is reinstall everything, but sometimes this can make things worse if you don’t delete everything, as you can end up with mixed versions of base install and subsequent versions downloaded through Software Update. If you’re going to reinstall, then reinstall everything the way Apple recommends, but I would only use this as a last resort.
- Often a reinstall may have excluded Qmaster. To check, go to Terminal and type:
ls -l /Library/Application Support/Apple Qmaster/
Note that there are space characters between “Application” and “Support”, and “Apple” and “Qmaster”, and the slash “” character is used to escape them. You could instead wrap the entire path in double quotes if you wish. Now, if you don’t see a list of Qmaster related files, such as qmasterconfig or QmasterApplications.plist, then you haven’t installed Qmaster, and you’ll need to go back to your base install disks, and reinstall.
- It could be possible that a reinstall didn’t actually add Qmaster to the startup items folder. To check this, use finder to open /Library/StartupItems, and make sure the Qmaster folder exists, and contains the startup script. You should also check the security permissions. See below.
- Sometimes the security permissions for Qmaster’s startup script get munged. To fix this, go to Terminal, and type the following:
- cd /Library/StartupItems/Qmaster
- rm -f .disabled
- sudo chmod 755 Qmaster
- sudo chown root:wheel Qmaster
- sudo chmod 644 StartupParameters.plist
- sudo chown root:wheel StartupParameters.plist
This also removes a possible .disabled file, which can also disable Qmaster from starting. You may also need to run /System/Library/CoreServices/SecurityFixer to fix permissions, however I’ve seen very little feedback that this helps at all. You will need to reboot your Mac to actually start Qmaster, and test if it is now working.
- Another problem with starting Qmaster, is sometimes the software it requires is not available, such as AECore services and the Qmaster.framework. Go back to the install disks and make sure you’ve installed everything correctly. Alternatively, you can use Pacifist (a third party standalone package installer) to only install the Qmaster package. Different versions of Final Cut will package things differently, so you need to be careful which packages you need to install. If in doubt, use Pacifist to install the lot.
- Qmaster requires three main system services to operate, Disks, Resolver (DNS) and Network. These are listed in /Library/StartupItems/StartupParameters.plist. I doubt the startup items would be called without these, but perhaps third party software is causing these not to start before Qmaster is started. If this is the case, either start up Qmaster manually (see below), or find the offending software and remove it or get a newer version.
If Qmaster still won’t start, then try starting it manually. Go to Terminal and type:
cd /Library/StartupItems/Qmaster
Then type:
sudo /Library/StartupItems/Qmaster/Qmaster start
You’ll get a message like Starting Qmaster services, which just means that the script has tried to run. It may take up to a minute to start, but eventually it should appear in top or the Activity Monitor. If this works for you, then you’ll need to restart it again whenever you reboot.
If it still won’t start, then there’s probably some software which is missing, and I’d recommend reinstalling everything. Although there is an error log for Qmaster at /Library/Logs/Qmaster/qmasterd.log, if any of the lines within it start with Error:, then again it is probably some software which is missing.
One additional thing to try, is removing all network connections. If you’re not using a server rendering farm, just the one computer you edit on, then Qmaster won’t require network access. While there are several theories as to why this fix works, I’ve yet to find a consistent and reputable one, but it generally goes like this: when Qmaster starts up, it looks for network connections on one or more known ports, and if it can’t find them, it fails to start up. This doesn’t make much sense technically, and the solution to the problem is just as convoluted, but it seems to work for some people. It goes like this: if you shut down all network services, then Qmaster won’t go looking for ports, and it will startup without failing.
There are three ways you can do this, that I found on the web. Two you can try, and a third you should not.
- Go to the System Preferences, Network pane, select Network Port Configurations from the Show: select menu, and uncheck all the Port Configurations, then click on Apply Now. This will disable all your network services, and you can then in theory try to restart Qmaster. You can either reboot and see if it starts automatically, or use the manual method of starting it with sudo from Terminal as described above. Again, check with top or Activity Monitor to see if it starts.
- Instead of killing all your network connections, go to System Preferences, Network pane, and create a new Location: setting from the Location: select menu. Call it “Qmaster” or “Compressor” or “[no network]”, whatever makes sense to you, and then again uncheck all the Port Configurations in Network Port Configurations. You now have your standard Location: for normal networking, and your new special Qmaster settings for when you need Qmaster. Of course whenever you have the Qmaster one active, you have no network capability, so no Internet access.
- Some web forums have suggested that you remove /etc/hostconfig. DO NOT DO THIS! This file is required by your Mac when you start up, and removing it will cause your Mac to permanently boot into the system shell. It should fix the Qmaster problem, because it disables all networking, but it also disables pretty much everything else as well, and with no GUI, you’re going to find it hard to use Compressor anyway. Some have also suggested copying this file to the desktop, renaming it to hostconfig.old and then copying it back to /etc, which does nothing. Some people have reported success in playing with hostconfig, however my thought is that they did something else at the same time which fixed it, or it was a permission problem which was fixed by touching hostconfig. My recommendation is to not try it, although if you’re interested you can find numerous descriptions of it in Google.
Qmaster is running
At this point, you should be confident that Qmaster is actually running, so the problem may well be mixed versions of Compressor and Qmaster. If you think this is the case, then follow Apple’s reinstall method above, and make sure your versions are in sync.
If this is not the problem, then it could be that the Qmaster configuration is wrong. This is the problem that I was having. I’ve never changed the Qmaster preferences, but for some reason, something changed them, maybe an install of another Apple product, maybe a crashed or cancelled Compressor session, who knows.
Final Cut Studio apparently includes a System Preferences pane for Qmaster. I saw it once, but when I clicked on it, it crashed, so I’ve never actually seen it. Subsequent installs of Final Cut Studio haven’t installed it again. Final Cut Pro doesn’t include this, so you won’t see it. These preferences are used to configure the network which Qmaster will use for distributed rendering. If you’re only using your own Mac, or your preferences are corrupted, then this configuration may be wrong, causing Qmaster to fail when trying to distribute jobs.
Luckily, there is a shell version of Qmaster preferences, which comes with all versions. To see your current configuration, go to Terminal and type:
cd /usr/sbin/
… to get to the right directory. Then type:
qmasterprefs -list
… to see your current configuration.
You should see settings for one or more clusters, plus two services, Compressor Processing and Rendering. While qmasterprefs is documented in both the Qmaster and Compressor manuals, the service parameters are not, and neither are most of the cluster parameters. I’m assuming this is because users typically go through the GUI, which most people may not actually have installed.
First thing is to make a copy of the current settings, so you can restore them, so do a qmasterprefs -list, copy the output into a text editor, and save it to disk for later.
Now, we need to make sure we have a single machine defined. My machine name is g5, so I have a cluster started on g5 as follows:
-cluster on servername "g5" quickcluster on unmanagedservices on unmanagedmulticapturethreshold 0 networkinterface allinterfaces
If your machine name is wrong, then change it with:
qmasterprefs -cluster on servername "yourmachinename"
Your machine name will be listed at the beginning of the prompt in Terminal. e.g. my prompt looks like this:
[g5:/usr/sbin] richardbf%
g5 is my machine name, /usr/sbin is the directory I’m currently in, and richardbf is my user name.
You may also need to enable quick clustering using:
qmaster -cluster on quickcluster on
Next, you need to make sure Qmaster is enabled for Compressor and Rendering services. To do this, type:
qmasterprefs -service "Compressor Processing" on instances 1
… to enable Compressor, and then:
qmasterprefs -service "Rendering" on instances 1
… to enable rendering. Note that my initial prefs had these two turned off, and an instances of -1 for Rendering. As these are not documented, I don’t know the exact settings they should be, but these work for me.
The networkinterface allinterfaces may also need to be set for your cluster, in case that has been changed as well.
Here’s the configuration that works for me:
[g5:/usr/sbin] richardbf% qmasterprefs -list
Current settings:
-cluster on servername "g5" quickcluster on unmanagedservices on unmanagedmulticapturethreshold 0 networkinterface allinterfaces
-service "Compressor Processing" on instances 1 autorestart off unmanaged on
-service "Rendering" on instances 1 autorestart off unmanaged on
[g5:/usr/sbin] richardbf%
You can also type qmasterprefs -help for help on which commands you can use.
Once you’ve made your changes, double check that they’d been accepted, by reissuing:
qmaster -list
Now restart Qmaster by typing:
qmasterprefs -restart
… then go back and try Compressor to see if the error dialog still appears.
One thing to note, Compressor automatically detects your single cluster, and populates the Cluster: select menu in the Batch window, with your machine name. That’s the select menu next to the Submit button. When Compressor starts, this will be set to None, then as it connects to Qmaster, it should quickly change to your machine name. If not, then you should select it manually yourself. If your machine name isn’t in the list, then go back and make sure you set your -cluster options correctly.
Either way, you should also reboot your Mac and try Compressor again, just to be sure. If it works before the reboot but not after, then you may have a security permissions problem, or perhaps the installation is still flakey, in which case I’d suggest reinstalling everything as mentioned above.
If it doesn’t work before a reboot, but does after, or to be honest who cares so long as it works after, then you’ve fixed the problem.
Conclusion
I cannot believe that this is still a problem. Surely Apple would know of all the problems people are having, both in their support forums and elsewhere on the web, and would redesign the installation and configuration of both Qmaster and Compressor.
Subsequent versions of Final Cut Studio and Compressor do include newer versions of Qmaster, however in my experience, an upgrade makes it very easy to end up back in a whole world of “Unable to connect to background process” pain. My recommendation is, if you’ve got a running fairly up to date version of Final Cut and Compressor working, then don’t upgrade unless you absolutely need features or fixes in the newer version, and even then, only upgrade to minor versions, not a major one.
iPod support
Version 2.11 of Compressor includes a new built in setting for transcoding videos for the iPod, and gives you options such as using either H.264 or MPEG4 as the encoding format. This is a great setting to have, but in my case I’ve had to forego it in the name of Qmaster woes. Instead, I have to use the Convert to iPod setting in iTunes to convert videos to iPod format. Unfortunately this always uses MPEG4 and not H.264, but at least it works.
If you have any additional comments or solutions, then please let me know. My system is now working, but it took a lot of effort to try everything, and then come up with my own, seemingly new solution.
dude
i can’t even open compressor anymore. i try and then it just unexpectedly quits. it’s really a nightmare. however, when i sign into another user name on my computer, it does open and like you (and every other person using compressor) i get the ‘cannot connect…’ error. i’m going to try the things you say and see if it works. such a bummer.
Cheers for the instructions, it has solved my problem. The solution for me was at the point where you start Qmaster manually with the commands in the terminal –
cd /Library/StartupItems/Qmaster
sudo /Library/StartupItems/Qmaster/Qmaster start
So to ensure Qmaster is running after a reboot I wrote a small AppleScript, have saved it as an application bundle and have made it a login item.
Here is the script, simply copy and paste it into Script Editor –
delay 30 — found that it required a delay before executing so have arbitrarily set this to 30 seconds
set adminUsername to “” — put your username here (must have admin privileges, System Preferences > Accounts > Allow user to administer this computer).
set adminPassword to “” — put your password here
do shell script “cd /Library/Startupitems/Qmaster;sudo /Library/StartupItems/Qmaster/Qmaster start” user name adminUsername password adminPassword with administrator privileges
To provide further insight into the problem (at least mine). Launching the Console app shows me that qmasterd has crashed, also it indicates that qmasterd’s gethostbyname() has failed, among other things. I know that my servers do not have DNS resolving properly in the form of reverse lookups and I am thinking this may have something to do with the problem of the StartupItem for Qmaster not working correctly. I have Xserve cluster nodes without graphics cards so I definitely don’t have the option to disable networking. I will get the network people to fix the reverse lookup problem and let you know how I get on.
Here is my console.log
Mac OS X Version 10.4.7 (Build 8J135)
2006-07-23 20:30:02 +0800
2006-07-23 20:30:02.989 loginwindow[74] FSResolveAliasWithMountFlags returned err = -43
2006-07-23 20:30:03.375 SystemUIServer[90] lang is:en
Jul 23 20:30:03 av34 mDNSResponder: Adding browse domain local.
Jul 23 20:30:08 av34 mDNSResponder: Advertising processor02. IP 130.95.6.34
2006-07-23 20:30:23.414 qmasterd[214] [CDOHostInfoFactory localPortName]: gethostbyname() failed.
gethostbyname: Unknown host
[214]: CPropertyListFile::refresh(): CFURLCreateDataAndPropertiesFromResource failed, file = /Library/Application Support/Apple Qmaster/jobcontroller:com.apple.qmaster.cluster.admin.plist, error = -10
2006-07-23 20:30:27.188 qmasterqd[242] Using “localClusterAdminKey” admin key
Jul 23 20:30:31 av34 mDNSResponder: ERROR: Only name server claiming responsibility for “processor02.” is “.”!
Jul 23 20:30:31 av34 mDNSResponder: HostnameCallback: Error -65538 for registration of processor02. IP 130.95.6.34
qmasterd: terminated due to signal().
Jul 23 20:30:32 av34 crashdump[276]: qmasterd crashed
Jul 23 20:30:32 av34 crashdump[276]: crash report written to: /Library/Logs/CrashReporter/qmasterd.crash.log
Thanks for that Shaun, I’m glad it helped. I appreciate you posting your script here, hopefully it will help someone else.
High five Richard! Your post is a BIG help. I had the same frustrations with all these wonky fixes other people have suggested. Just walking through your process and I had it up and running. Thanks a lot!
If you’re getting the error:
gethostbyname() failed. gethostbyname: Unknown host
when trying to start qmaster manually.
So, I found out the unknown hostname.
> hostname
then i added the name to /etc/hosts. e.g. if you machine is called “Foo” you would add:
127.0.0.1 Foo
Hi. I am having a similar issue with Compressor being “unable to connect to background processes”. I disconnected all network activity and it worked fine. Then, after connecting back to the network, it refused to work. I realized that I installed a new Linksys router the day before it stopped working (WRT54G), since my old Linksys router (BEFW11S4) had crapped out. Something in the new router is causing the issue. However, what it is, I don’t know. Has anyone experienced this issue after a router change?
Thnx!
Fixing the security settings in Terminal worked for me: after restarting I got a dialog telling me that security settings were wrong, and asking me to have MacOS fix them. After another restart, Compressor worked fine again!
Thanks!
I followed your instructions for batch process, and it worked!!!
Thank you very much.
Pete
I have beening having the hardest trying to get compressor to work and thank you very much for this post. I do have a question, it there a way I can get Qmaster to start on startup? It looks like I’m going to have to go to terminal every time I want to start it and I guess that’s not really a problem cause I don’t use it every time I start the computer. Is there a way to at least make an icon that will start the program when double clicked?
Great!
I tried this tips and first time compressor, batch all stuff works now for me too.
Many thanks for your work!
At first this worked.
Now, as Compressor opens, it”unexpectedly quits”!
What now?
Please help.
Pete
Great!!! For the first time since very long Compressor is working again!!!!
Thanks
Thank you so much Richard…..I just had to start Qmaster manually….better than the apple website help
I can’t tell you how long I’ve battled this Qmaster problem on my own and not gotten it sorted out. Starting it manually was all it took. Thank you so much for posting such an informed, useful site!
Richard,
I cannot thank you enough for solving this problem for us once and for all. This has been a pain in my side for about the last year and has cost me a lot of time and money (not getting projects to clients on time because of it) so I am very happy to finally have the answer to this problem. Thanks again!
– Isaac
If simply manually starting qmasterd solves your problem, you most likely either have a firewall disabling the startup process, or inadvertently disabled it when the Security Fixer dialog popped up. Also, as stated, you should not mix and match versions of Qmaster and Compressor. On Final Cut Studio or DSP installation disks, you should have the same version of Qmaster and Compressor, so just install both from the same disk, and if you install another Pro app do not install another version of either, just the app you want.
The hostname issues seemed to effect earlier versions of Qmaster, so either update Qmaster to something recent, or fix your hostname resolution for your local machine.
I can’t view my Qmaster settings, when I try to -list them, I get “Exception: no config file entry for service “jobcontroller:com.apple.qmaster.cluster.admin” ”
Any advice?
WOW, thank you, thank you. This saved the day! I had reinstalled about 10 times per apples suggestion with no luck, but your advice did the trick. Thanks again!
Thanks a lot for this information. A from-scratch install of a Mac Pro with 10.4.8 and Final Cut Studio (with all the updates from Apple) was unable to submit a job to Qmaster the very first time it was attempted. After deleting the .disabled file and fixing permissions on the Qmaster startup items I was able to get it running. I’ve saved off a copy of the information in the event that I run into it again, as based on all the problem reports on the web I’m almost sure to at some point.
Apple really needs to do something about the quality of its “pro” software. On this same machine I started up FCP for the first time, set the scratch disk locations, made sure I could import some footage captured by another application, then quit without saving a project. Then FCP wouldn’t come up again (apparently died around the time it checks for FireWire devices according to the log) until all of the FCP preference files were deleted. Writing out corrupt file(s) on the very first use is pretty scary.
I changed the name of my user accont, use to be Parkland Media (TM) took out the TM at the end of it. and it works great now. It was a small TM (trademark)
Thanks so much Richard for all the good information. I’ve been battling this issue for awhile now as well and I’m starting to try your recommendations. One question;
I’m running a PowerMac G5 2.7GHz dual. OSX 10.4.7. Final Cut Studio 5.1/Compressor 2.
Under “About This Mac” -> Hardware Overview, My Machine Name is listed as “Power Mac G5”. In the terminal window however my machine name appears to be Macintosh-3? Here is what my terminal prompt looks like Macintosh-3:/usr/sbin davebeckymungai$.
Am I right in assuming I have a Machine name mis-match here? To make things even more interesting, when I do a “qmasterprefs -list” I get the following;
Current settings:
-cluster off servername “Dave & Becky Mungais Power Mac G5” quickcluster off unmanagedservices on unmanagedmulticapturethreshold 0 networkinterface allinterfaces
-service “Compressor Processing” off instances 1 autorestart off unmanaged on
According to your information, isn’t “Dave & Becky Mungai’s Power Mac G5” the Machine name Qmaster is using? So I have Three different machine names listed? I’m thinking this could be related to my problem but I’m not sure what Machine name to change Qmaster to? Any thoughts would be appreciated!
Kindest Regards,
Dave Mungai
Choice Video Services.
I’ve gotten as far as launching the terminal and typing in *cd /usr/sbin*
When I enter *qmasterprefs -list* I get a message that reads
*terminate called after throwing an instance of ‘aecore::CException’
Abort trap* This is the first time I’ve ever used Terminal so maybe this is a basic mistake I’m making? Entering qmasterprefs alone calls up:
*Exception: no arguments]
Usage: qmasterprefs options
-help (print supported options)
-list (print current settings)
-restart (restart qmaster services)
-cluster on | off [timeout min] [servername name] [quickcluster on | off] [unmanagedservices on | off] [unmanagedmulticapturethreshold sec] [networkinterface allinterfaces |
-service name options [-service name options …] (set service options):
-service “Compressor Processing” on | off [timeout min] [instances n] [autorestart on | off] [unmanaged on | off]
-service “Rendering” on | off [timeout min] [instances n] [autorestart on | off] [unmanaged on | off]*
So I see that the -list option is there…. I just don’t know how to access it. Is this just a syntax error or something? I’ve retyped it a bunch of times with no luck.
I had the same problem with Compressor. Never used it before. Didn’t know what to expect, but opened it and decided to play with it prior to “doing it for real” in a few days when I need to encode a 104 minute video for DVD Studio Pro. I really just wanted to see how much time it would say it would take to render the whole thing so I can plan accordingly.
I chose my settings, hit submit, and got the error message: “Unable to connect to background process.” There are times in my life when I wish software programmers would actually explain what the hell I’m supposed to do correct a problem rather than giving me a nonsensical error message! Why not just say “You’re screwed!” … it pretty much means the same thing without any reference material. Maybe by 2020 software programmers will figure out how to create a link to a web site or help page that acually explains their silly messages that NO ONE except them has any idea what it means. Oh, sorry, I’m digressing, huh.
So, went to Apple online Help, searched for “Unable to connect to background process” and found just ONE page on the Apple site for the problem.
I read somewhere that the Qmaster was for using multiple machines, so, after trashing everything Appe suggested I trash, I ONLY reinstalled Compressor.
Problem not fixed.
Then went to the Apple community board, searched for “Unable to connect to background process” and found a gazillion posts, and read a bunch of them. I started to really wonder why Apple can release such an obvious fault in their software which dates back to earlier versions…for $1,300 no less and is considered an integral part of the software!
Anyway, finally came across a link for THIS web page, and followed the directions to change the preferences. I did. Problem not fixed.
However, then I remembered that Compressor is tied to Qmaster (how am I supposed to know that two pieces of software need each other to work???) and reinstalled Qmaster.
And, what do you know, but it works! Finally.
Hey, THANKS Richard for figuring these things out for us! Much obliged.
Perhaps by installing them seperately, that helped. I have no idea. But, I am glad it’s finally working. Good luck!
Oh, and at 1% complete, my 104 minute video will take another 16 hours and 42 minutes to process. Joy.
Larry
After following the above steps and fixing the background encoding issue on most of the ailing computers in the lab I work in I still have a problem with a few.
*terminate called after throwing an instance of ‘aecore::CException’
Abort trap*
when will I ever find the answer.
WROC I’m with you man!
Hi,
I’m going thru the steps you outlined to get compressor to work (unable to connect to bkgrnd process) & I’m getting lost & confused, maybe because I have FCP 4.51 & Compressor 1.21 (??)
but nowhere in compressor, when opened on its own, do I have the option to do anything with clusters. I can change default destination to desktop, but no cluster options. Tried to import a jpeg & all jpegs are greyed out in the import menu.
I’m using a G5 w/ 10.4.8, single machine no network. If I’m going to reinstall Q Master, where do I find it in my tiger disc? & will the fact that I’ve updated to 10.4.8 screw up the 10.4 Q master fromthe disc?
Thanks for any guidance
Duane
ds, you need to follow the instructions precisely. You need to go into the shell and type the commands above, then you’ll see the cluster information. If it says compressor doesn’t exist, then it is not installed.
As for Qmaster, it comes on the FCP disk. It should be fine under 10.4.8.
Hi, I appreciate the help.
I went to terminal, typed TOP & saw a lot but no QMaster entries. Also typed ln -l /Library/Application Support/Apple Qmaster/ and it said : No such file or directory. So it would look like no QMaster, but yet in Startup items – there was QMaster.
I tried typing the 6 steps in terminal for if QMaster isnt running & got these results –
[ool-18bd1a91:~] duaneshe% cd /Library/StartupItem/Qmaster
tcsh: /Library/StartupItem/Qmaster: No such file or directory.
[ool-18bd1a91:~] duaneshe% rm -f .disabled
[ool-18bd1a91:~] duaneshe% sudo chmod 755 Qmaster
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
Password:
chmod: Qmaster: No such file or directory
[ool-18bd1a91:~] duaneshe%
[ool-18bd1a91:~] duaneshe% sudo chown root:wheel Qmaster
chown: Qmaster: No such file or directory
[ool-18bd1a91:~] duaneshe% sudo chmod 644 StartupParameters.plist
chmod: StartupParameters.plist: No such file or directory
[ool-18bd1a91:~] duaneshe% sudo chown root:wheel StartupParameters.plist
chown: StartupParameters.plist: No such file or directory
Tried the next suggested command & got the following –
[ool-18bd1a91:~] duaneshe% /System/Library/CoreServices/SecurityFixer
tcsh: /System/Library/CoreServices/SecurityFixer: Command not found.
[ool-18bd1a91:~] duaneshe%
It ran for a bit, but retyping TOP got a list that still excluded QMaster.
Tried the SysPrefs unchecking of the network ports & restarted.
Went to FCP and compressor was still grayed out (as its been since I followed someones advice of the apple boards about copying hostconfig file to the desktop, renaming it to hostconfig.old and then copying it back to /etc. Before that Compressor would open, but I’d get the bkground process warning.
Had to go bk into sys prefs & recheck theboxes to get bk on the internet.
So am I crawling towards the eventual reinstall of FCP? I’m dreading that because I learned to edit with the big project that I’m trying to compress & am scared of what a reinstall may do to that. All the little resource bits that I will soon have 2 of, and the probs that may bring.
Again any guidance is appreciated. Thanks Duane
Well, it sounds like Compressor isn’t installed, which means you’re stuck at step 2 in “Qmaster is not running”. Skip to step 5, where it mentions installing Qmaster from the FCP disk with Pacifist.
If at any point you feel out of your depth, then just reinstall FCP as Apple suggests, because playing around can be dangerous if you’re not sure what’s hapenning.
Hi Richard,
Well I downloaded Pacifist & used it to get into FCP 4 installer & isolate Compressor to do a full reinstall of that. I fgured it was safe since I hadnt successfully used Compressor yet (no prefs or files created). I saw that inside of Compressor were QMaster components.
It installed Compressor 1.0 & then I used Software Update to update to 1.21
I went bk into FCP & was able to again choose Compressor as an Export choice (like it was bk before I tried the hostconfig.old idea) so – its no longer grayed out.
But once again, trying to run Compressor gets the Bkgrnd Process flag & once again terminal cant find anything under ls -l /Library/Application Support/Apple Qmaster/.
So its a little frustrating. I did like the way Pacifist worked tho, it was great isolating just 1 part for the install.
BTW, when verifying the files before the install, I got a lot of permission differences noted so after I installed & upgraded, I went into disk utility & verified/repaired disc permissions. It didnt point out any FCP or Compressor or QMaster stuff, only iTunes. Could that be a factor?
I dont understand why QMaster is an issue if I’m just running 1 machine. Is it needed on 1 machine? Can it be disabled?
Thanks again, any further suggestions will be appreciated.
Regards, Duane
Every few months for the last year and a half (!) I make the rounds to see if anyone has solved the “background process” problem. Your solution did it, and it makes so much sense. Thanks for taking the time to dig this up and explain it clearly.
Thanks so much for taking time to explain the causes of this problem.
I have been pulling my hair out for weeks over this.
Apple’s solution to re-install compressor and qmaster just wasn’t working for me.
But after reading through your article i realised that i needed to force the qmaster startup items to run.
I copied the two lines of code into the terminal and bingo everything works as it should.
Hello to one an all, especially Richard.
I too was having this weird problem with Qmaster and Compressor. The one of “Unable to connect to background process.”
Well I studied the material on Richard’s website and I noticed that the qmaster processes(2) were actually running happily on my Mac. I verified this with Apple’s “Activity Monitor.app” When I launched Compressor, after about 15 seconds or so, the qmaster processes quit!
So Qmaster is happily doing its job, but Compressor killed them off.
So I then did as Richard suggested in the network connections section of his post. I set up a Qmaster no network, which is his option 2 and voila!, after rebooting again qmaster processes were active and when I launched Compressor, the qmaster processes stayed active.
So much so that I went ahead and rendered a FCP 4.5 HD project with MPEG2 encoding all the way to the end-a 30 min. joy to watch, being glued there to the end.
Man what a relief. I have so much riding on being able to perform this workflow. You don’t know how much I was disappointed with my situation that I was comtemplating having to spend money to go down the dreaded upgrade path of Final Cut Studio and a new Mac, when all along the setup I have will do the job, albeit slower than I really want. I have a Mac G4/500 running Mac OS X 10.4.8. Man the speed is enough to kill any creative processes but now that the above problem is eliminated I can at least know that I am now required to use some of my creative juices to come up with those creations that people appreciate.
Kudos and bouquets to Richard and all the others who have been across this problem all the way back to 2005, for solvng it, and as much as Apple puts out great products, they deserve brickbats on this one. Surely with all their brains to burn, someone there could have figured it out, given us a nice solution and let all of us not suffer all this heartburn!
Felix Macri
Mostly for Duane, but also for Richard: there’s no such directory as “/Library/StartupItem” in OS X. It’s “/Library/StartupItems” with an ‘s’. This will cause, as in Duane’s case, all of the above commands to fail if they’re cut and pasted, as the path is bad.
Also for Duane: your first command, “ln -l…” is incorrect. “ls” is the list command (“ln” is link, which we don’t want to use here.)
My project was saved in the nick of time. I was racking my brains over this until I came across this website. Richard is a good man, with good intentions, but most of all good advice. My project is compressing as we speak!
Thanks again lad.
Thanks J!mmy, I’ve fixed the /Library/StartupItems typo.
THis problem has reared it’s ugly head for my BUT it’s brand new and can not be fixed the same way as it was for compressor 2. MAny wasted hours so far trying to get compressor to even recogize “this computer” in it’s list of clusters.
David
Hi Richard
you have helped a lot of people this is great. i am not however a computer savvy person enough to follow this through. i got to the terminal and got it to say this
Last login: Mon Sep 3 23:22:54 on console
Welcome to Darwin!
dina-kagans-Computer:~ moreocean$
dina-kagans-Computer:~ moreocean$ cd /usr/sbin/
dina-kagans-Computer:/usr/sbin moreocean$ qmasterprefs -list
Current settings:
-cluster off servername “dina kaganâs Computer” quickcluster on unmanagedservices on unmanagedmulticapturethreshold 0 networkinterface allinterfaces
-service “Compressor Processing” off instances 1 autorestart off unmanaged on
-service “Rendering” off instances -1 autorestart off unmanaged on
dina-kagans-Computer:/usr/sbin moreocean$
but when i tried to change “off” to “on”for example, it didn’t let me change the text. and i have never done this type of stuff in my life. i only work with fcp. i was wondering if it’s at all possible to call you or to ask you to guide me through. if it’s at all a possibility, please let me know. i would really appreciate your help!! Thank you Dina
Fixing security permissions as per your instructions under >Qmaster is not running> point 4 worked for me. Thank you so much for such a clear, precise set of instructions. The best I’ve seen yet!
I am having a problem with compressor 3.0
When I assign a setting and a destination for encoding and drag them in the batch window, the user manual says click submit and it shouls start.
When I click submit i get the message that one or more targets are incomplete.
What am i doing wrong here? i follow the user manual but nothing happens after click on submit.
Can anybody please help me on this.
I am having a problem with compressor 3.0
When I assign a setting and a destination for encoding and drag them in the batch window, the user manual says click submit and it shouls start.
When I click submit i get the message that one or more targets are incomplete.
What am i doing wrong here? i follow the user manual but nothing happens after click on submit.
Can anybody please help me on this.
Thanks Richard, this is by far the most informative help article related to the subject issue that I found via googling in the past several hours. Thank you so very much for sharing.
I did read through your article as well as the thread and tried to follow your suggestions to fix my problem. I reinstalled Qmaster using Pacifist because noticing that it was not running even after I used terminal to do the lines of your suggestion (.disable etc etc that part). Anyway, when I get to the Qmaster folder in startup item, I see files there but even after reinstallation, the qmasterconfig file is still showing as qmasterconfig.default which made me wonder the case of it not running. I changed the file name to remove the “.default” part and then I ran command of manually start Qmaster in terminal. This time I can see the process running via Activity monitor, except for in terminal, here is what I saw:
Starting Qmaster services
Scarletts-Apple:/Library/StartupItems/Qmaster Scarlett$ [295]: CPropertyListFile::refresh(): CFURLCreateDataAndPropertiesFromResource failed, file = /Library/Application Support/Apple Qmaster/servicecontroller:com.apple.stomp.transcoder.stomp.plist, error = -10
[295]: CPropertyListFile::refresh(): CFURLCreateDataAndPropertiesFromResource failed, file = /Library/Application Support/Apple Qmaster/jobcontroller:com.apple.compressor.cluster.admin.plist, error = -10
[300]: CPropertyListFile::refresh(): CFURLCreateDataAndPropertiesFromResource failed, file = /Library/Application Support/Apple Qmaster/servicecontroller:com.apple.stomp.transcoder.stomp.plist, error = -10
[295]: CPropertyListFile::refresh(): CFURLCreateDataAndPropertiesFromResource failed, file = /Library/Application Support/Apple Qmaster/servicecontroller:com.apple.stomp.transcoder.stomp.plist, error = -10
Scarletts-Apple:/Library/StartupItems/Qmaster Scarlett$ cd /usr/sbin/
Scarletts-Apple:/usr/sbin Scarlett$ qmasterprefs -list
Exception: no config file entry for service “jobcontroller:com.apple.qmaster.cluster.admin”
Needless to say, something is still not right. I couldn’t go any further as this was not mentioned in your article and it’s already 1:30am my time so I need my beauty sleep now…have struggled the past 2 days with this and I am exhausted. If you have a chance to see my post and manage to help me out, that will be greatly appreciated. Actually, whether or not you have time to help me, I greatly appreciate your article. It does point me to the right thinking track but since I am not very good with those indepth tech, any help is going to save me a lot time.
Wish you a wonderful 2008! All the best and Happy New Year!
Scarlett
Hi Scarlett. The article is basically as far as I got, so I’m not sure what to suggest. Although it does sound like the config file is missing. Try “qmasterprefs -cluster on servername “yourservername” and see if it creates an initial config for you. Or if not, try creating an empty one first with “touch” (I don’t know the actual path of it). Other than that, maybe you’ll need to do the dreaded uninstall and reinstall. Good luck.
Richard…I got it fixed…well basically it’s my stupidity, really. Perhaps I just over worked :P…anyway, long story short – my compressor kept crashing at loading so I followed Apple support article to uninstall EVERYTHING and reinstall everything. Only I forgot one thing – I forgot to re-install AppleQmasterNode.mpkg which is why the config file was missing. Now it seems alright. thank you very much for all the help…^_^
Richard…I got it fixed…well basically it’s my stupidity, really. Perhaps I just over worked :P…anyway, long story short – my compressor kept crashing at loading so I followed Apple support article to uninstall EVERYTHING and reinstall everything. Only I forgot one thing – I forgot to re-install AppleQmasterNode.mpkg which is why the config file was missing. Now it seems alright. thank you very much for all the help…^_^
You are the man! I finally got Compressor to work after purchasing Final Cut Studio 2 about two months ago. It never worked after installing it. My computer name would never populate the cluster pop-down menu. It would just be blank and now it says “This Computer”. I could not get this to work despite the best efforts at the Apple Genius Bar and with Apple technical support over the phone. I really didn’t want to erase my entire computer and reinstall FCS 2 which is what everyone recommended. Thanks again and now I can actually work! Hmmm, maybe that wasn’t such a good thing after all……
I’m having problems with launching Compressor and was recommended to delete Qmaster. I got rid of Qmaster application but I’m told there are other areas where Qmaster resides and must delete in those areas. Where else do I need to delete Qmaster?
Many thanks,
yun
I’ve never had problems with Compressor or Quartermaster. I use After Effects Network Render so FCP/Compressor Render Stations has been good.
I’ve used FCP since version One and Compressor is my preferred tool; so fast and so capable (I used to use FFMpegX for a lot of my conversion work because it was more “talented” than QT but any longer) BUT I have stayed at Tiger and FCP 514/FCS 1.
Yes I wish for some of the enhancements but when I add up all that I read at Mac Support and at MacFixit, about FCS 2 and Leopard I feel justified. For now.
Maybe some should consider re-installing an earlier version until Apple fixes what is so clearly a big problem.
First the fix: The simplest of all 😛 Software update.
updated to 2.3 and then to 2.3.1 and it is working finally. It appears Apple have finally got around to fixing the bug! FINALLY! Well at least in my case it now works.
I ended up here when I had problems with Compressor version 1.x and after about half an hour of trying your fixes I had a smile on my face. I found myself back here after upgrading to Compressor 2.1. After nearly an entire day trying everything here and more with no luck I am finally Compressing again! Qmaster would crash, no matter what I did. I tried the hostconfig file trick and lucky didn’t run into the issues some other users have, although it did not fix the problem either. I tried asking the qmaster services to start with terminal and that is where I found my problem. By having activity monitor open I noticed “Crash Reporter” task would come up after calling the qmaster service with terminal. I check the crash logs and found qmaster couldn’t get off the ground at all. Repairing permissions and everything else on this site didn’t fix my problem. I removed EVERYTHING to do with Compressor and Qmaster short of Final Cut and rebooted, emptied trash, rebooted, reinstalled. Still no luck. Just keeping an eye on Activity monitor and checking if any qmaster services were running saved me a lot of time, rather than having to ask final cut to exp to Compressor and then ask compressor to submit and to see if it works. As mentioned above, you know it won’t work if the qmasterd task is not running(Activity monitor to check).
I certainly hope the updates via software update have/are solving this horrible bug for others. This has been the biggest waste of my time for months and I fix Apple computer systems for a job 😛
P.S.
My system is: MBP 2.4Ghz Penryn 2GB, 10.5.2, Final Cut 5.1.4, Apple Qadministrator 2.1/2.3.1(original with problem/working version), Apple Qmaster 2.1/2.3.1(original with problem/working version), with Gigabit network connection to Billion 7202g via Dlink 8 port gigabit switch(network seemed to play no part in the problem).
Worked! You’re a genius. Worked with changing the preferences. I’m greatful there are people who can wrap their heads around these ridiculous problems.
All the best,
Denver
… ican’t even get compressor to import a jpeg! (trying to follow the test instruction setup etc…) file > Import doesn’t allow any JPEG fule to be selected ! What the %$^&*^&*()???
CAREFUL!!!! Many of us — self included, have been clueslessly assuming something is terribly wrong while asking terminal to show the contents of the Application Support directory — THAT’S BECAUSE THE TERMINAL COMMAND NEEDS TO BE PLACED IN QUOTES! (filenames with spaces!). So — it’s:
ls -l “/Library/Application Support/Apple Qmaster/”
!!!!!!!!! (i just learned unix the HARD way) — No hard feelings Ricahrd — this is still a GREAT article — but please correct it for us unix-impaired!
Good catch jhall. After all these years. Thanks! In my defence, I was probably using the tab key to autocomplete and just figured people would do the same. I’ve added a “” to the command in the blog post, so people know to either use that or your quoted version.
CONSOLE SAYS “YES” — ACTIVITY MONITO SAYS “NO” … Ok, i’ve forced Qmaster to start via command line… but it doesn’t show up in the Activity Monitor — it DOES, howver say that it was started according to the Console (06/01/2008 16:25: qmasterd started) — any idea what this could mean? I’m going through every step i can find on the internet in detail — i am still at a total loss getting compressor to work 🙁
…. ok, Qmaster has officially crashed. Despite the Console message that “Qmasterd started” I now see in the system log that it has in fact, crashed (6/1/08 4:44:09 PM ReportCrash[225] Saved crashreport to /Library/Logs/CrashReporter/qmasterd_2008-06-01-164404_Macintosh-2.crash using uid: 0 gid: 0, euid: 0 egid: 0 )
…. ok, Qmaster has officially crashed. Despite the Console message that “Qmasterd started” I now see in the system log that it has in fact, crashed (6/1/08 4:44:09 PM ReportCrash[225] Saved crashreport to /Library/Logs/CrashReporter/qmasterd_2008-06-01-164404_Macintosh-2.crash using uid: 0 gid: 0, euid: 0 egid: 0 )
This is the best information about this problem out there. I went through every other process before finding this one, and finally pinning it down to the fact that Qmaster wasn’t starting is what worked. Thank you.
I’m still using FCP 4.5, Compressor 1.21, & DVD Studio Pro 3. I’m having the same ‘Unable to connect to background process’. Obviously, I can’t use your fix because of version differences. Any help would really be appreciated for this setup. It worked great until installing Leopard (10.5.4). Thanks!
thanks again for this great post, i have to come here about once a month to fix compressor. if u look on the apple discussion forum and search on my handle in the compressor forum, u will see all the problems that i have had along with dozens of other users. i think what’s going on with me is that qmaster is not starting on every boot. then i get unable to connect to que messages. then i use ur procedure for a manual restart. why qmaster won’t start reliably? who knows. but in ur post u mention that the qmaster preference pane is broken. so is mine. u don’t seem bothered by that. so i guess that’s no big deal. well, anyway, thanks again for ur help with what must be apple’s worst software ever. cheers,
coocoo
Hi,
It seems that qmaster uses the network configuration for part of it’s work. I noticed that Batch Monitor seems to get it’s information using the network. This is likely how the batch monitor and qmaster operate with clusters. Someone mentioned a problem with DNS lookup and you mentioned the local host name is important.
All this points to the need for proper network setup of the machine before using compressor or qmaster or batch monitor. I don’t think this is in the documentation?
So go into network settings and make sure the machine has a name, BEFORE running compressor. Maybe some people don’t use the network as advanced users might do, so this is never really set up? In OSX 10.5 the setting for machine name is even recommended to be set in that preference window– it will default to something like blahblah.local so that even if the network is not set up, the machine can always look up it’s own name (& address) using blahblah.local. Also the other network settings might matter too, even WIFI or ethernet can affect the DNS if there is a network problem.
In the compressor “batch” window I found my problem about “can’t connect” was helped (which only started happening after working for a while when an encoding crashed and I had to reboot so something obviously got stuck) via setting Cluster: to “This Computer blahblah” and then also going to menu Compressor->”Reset Background Processing…”
First, I love my Mac Pro when it works. Unfortunately…I spend way too much time struggling to get LogicPro, FCP, Compressor, Color, etcworking properly and consistently. Applecare is an oxymoron 🙁
So…thx for the help – I’m going to try your advice to get Compressor back running and in the future Apple software will be my LAST choice -there are too many alternatives in audio and video production on both platforms – struggling along with overpriced, underperforming Apple software has made me feel pretty foolish…
When I try to enable quick clustering in Terminal i.e.
qmaster -cluster on quickcluster on
I get the error message
qmaster: command not found
What’s up??
OS 10.5.4
Final Cut Pro 5.14
Regarding “Qmaster not running”: I don’t have a startup items folder in my library! My Macbook Pro runs 10.5.5 and is brand new… what’s the deal with this, anyone know?
After finding this I tried to run Qmaster with the Terminal commands:
/Library/StartupItems/Qmaster
sudo /Library/StartupItems/Qmaster/Qmaster start
And got this message:
Starting Qmaster services
dan-brownes-macbook-pro:Qmaster db$ The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
These last two lines, from “Break on…” until “exec().” repeat over 100+ times. What gives? I am unfamiliar with Terminal-style programming, though i will try to continue following the other processes in this post, but am worried about destroying the machine in the process… if someone could please help it would be amazing. this is absolutely unbelievable that Apple has allowed these issues to continue for 2 years…. might have to go back to rendering with my 667mhz powerbook!
This is much appreciated, but it hasn’t solved my problem. I followed all instructions – QMaster runs on startup, so I went into the configuration. One obvious issue: I has changed my startup disk name. It is no longer “Rich Potter’s G5” but “Meninha” (In other words, I renamed the icon/directory) So I changed that. I also changed the configuration to what was suggested, but one wouldn’t take – I can’t turn quickcluster on. I cut pasted the text, and cluster turned on, but that line gave me this response:
-bash: qmaster: command not found
Having done all that, I get the same “Unable to connect to background process” error…
Any suggestions?
Thanks.
Thanks a ton for all your work on this program. I used it and it got me started in the right direction however the thing still will not complete a project. I submit a file and at about 60% it kicks out to an error and will not complete the project. I did all your steps, also deleted and reinstalled all to continue with the same issue. I am now at a complete loss. Do I have to purchase the next version? If you have time to further assist I would warmly welcome it.
Thanks,
Barry
I followed all these steps to no avail.
I even tried on a fresh and clean install of OSX. I can’t seem to get QMaster running. I start it manually in Terminal (
“Starting Qmaster services”), but never shows up in active processes, and Compressor still can’t “Connect to background process.”
I’ve done so many re-installations, it’s absurd. I’ve come across so many different errors, and different problems, all without any success.
FWIT, I’ve also tried everything Apple suggested.
I give up 🙁
Getting rid of network connections worked for me. I had tried a lot of remidies before that, but nothing worked.
(Some didn’t work… some I was affraid to try. I’m creative guy, not computer guy)
I had searched the web for days. This is by far the best site for the “unable to connect to background…” issue.
Thanks.
IDIOT’S GUIDE TO MAKING MPG2 FILES – If you just want to encode an mpg2 file (.m2v) for a dvd, use DVD studio Pro! Just import it, go to prefs and set the encoding prefs you want and hit ‘Build’. What a releif – I thought just thought o of it – I certainly couldn’t do all that clever stuff I’ve read on this page…!
Thanks. QMaster was still running, and fixing its preferences in terminal worked for me. OSX 10.3.9, Compressor 2
Dear Richard,
thanks for those efforts but when it turns into code I am really lost, basically I have tried everything but the complicated Terminal rewriting and it still doesn’t work…
I also found a Compressor Repair
http://www.macupdate.com/info.php/id/30104/compressor-repair
but it has not worked for me unfortunately.
Richard,
Thanks for the great article. Nevertheless, none of the possible fixes worked for me, until I changed my network setup. I used to have a cable direct connection through a Motorola modem via Ethernet. The moment i installed a Belkin (kind of crappy) router in the middle, qmasterd stopped crashing at login, and Compressor works fine again.
Who knows… stranger things have happened!
Thank you very much
Hello…
My Compressor instances, on the cluster controller, and service-only machines are “(captured)” but will not show up as available in the QAdministrator.
I have tried the following terminal commands to reset the QMaster compressor services, but they still persist. I was able to use these to get the Rendering services to appear again (same problem w/ (captured) instances being unavailable)
qmasterprefs -cluster off -service Rendering off
qmasterprefs -service “Compressor Processing” off
rm /Library/Application Support/Apple Qmaster/jobcontroller:com.apple.qmaster.cluster.admin.plist
rm /Library/Application Support/Apple Qmaster/servicecontroller:com.apple.qmaster.executor.plist
qmasterprefs -cluster on -service Rendering on
qmasterprefs -service “Compressor Processing” on
i was wondering if it’s at all possible to call you or to ask you to guide me through.. if it’s at all a possibility, please let me know.The article is basically as far as I got,so I’m not sure what to suggest.Although it does sound like the con fig file is missing. Try “quartermasters -cluster on server name “your server name” and see if it creates an initial con fig for you I noticed that Batch Monitor seems to get it’s information using the network. This is likely how the batch monitor and qmaster operate with clusters. Someone mentioned a problem with DNS look up and you mentioned the local host name is important.i found this informative and interesting blog so i think so its very useful and knowledge able.it is Very good info.I am hoping the same best work from you in the future as well. In fact you creative writing abilities has inspired me.
I was having this problem luckily updating to Compressor 2.3.1 fixed it
you rule it actually worked i can not believe it
thanks so much
Thanks so much for this site, although it didn’t help me directly to solve my problems, but with the information i had the understanding what the problems between compressor and qmaster are.
Here how i solved my problem with 10.5.6 on a MacBook Pro (Intel) and DVDSP 2 and Compressor, it will help the people who have the same set up & Software as me, maybe not all the steps have to be done, but like that it worked for me on a MacBook Pro:
– install 10.5.6 and all the updates
– deactivate Airport or your internet connection
– install DVD Studio Pro 2 and Compressor (i had the Compressor 1.0.1 version)
– download and install DVD Studio Pro 2.0.5 update from apple (probably not really needed)
– click on compressor application, open package content, find the info.plist file, change in there everything from AGP to PCI
– restart computer, make sure internet connection is deactivated
– check in Activity monitor if qmaserd is running
– open compressor, and send a file to convert, if you dont get the error-msg
that background process cant be found, the problem is solved
– DO NOT UPDATE to COMPRESSOR 1.2.1, it will not more work in 10.5.6, stay with your old Compressor Version (mine is 1.0.1)
update to my post from before:
-check in Activity monitor if qmaserd is runnin (should be qmasterd, i did mistype)
– fyi: if i close the batch-monitor and compressor, somehow in the background the application is still running, but i could stop it in the activiy monitor. no reason why, a small problem with that i can life
I have the Production Suite. The first package that included FCP, DVDSP, Motion etc. It uses Compressor 1. I currently have installed 1.2.1. OS is 10.5.7. I’ve tried just about everything, including recently trying to start Qmaster manually and this is what I got:
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
qmasterd: terminated due to signal().
Any ideas?
i am having the same issue as listed above. with the “FORK” issue. i am currently running lepord on a dual proc ppc g5.
the version of compressor i am running is compressor 2.
here is the error message i am getting
from compressor it says
“cannot submit batch – unable to connect to background process”
after looking around on my system and on the net i found that the issue is related to a break with “mqueued”
i brought up a bash shell and ran the following:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Last login: Wed Sep 16 14:34:07 on ttys000
Audio-mac:~ betzelelgalut$ sudo /Library/StartupItems/Qmaster/Qmaster start
Password:
Starting Qmaster services
Audio-mac:~ betzelelgalut$ The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
qmasterd: terminated due to signal().
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
does any one know if the issue with mqueued, is a incompatibility issue with lepord? or is there an update that could be hanging the process?
i ran this app flawlessly on tiger for over a year, and have just started using it again recently on lepord.
when the issue first appeared compressor would not come up, but would post a window for me to input the serial key , which it kept rejecting.
so far the T.S. steps i have taken are :
1) complete reinstall of the OS, and final cut pro package
2) after reinstall compressor would come up, but had the “cannot connect” issue and shows in the cluster tab “none available”
3) i removed all the preference files for compressor and Qmaster and Qadmin, i also removed the apps themselves as directed on the apple web site.
4) i reinstalled compressor, qmaster, and qadmin again.
5) still get same error message as shown above.
6) i tried a free prog called compressor_repair, it still did not resolve the issue.
7) found another document on line that talks about deleting and stripping out all the lib files, pref files, and such – but did not want to go through that and corrupt my OS as this is a fresh install.
8) tried doing the moving of the startup file folder as recommended in this article, but found that there is no folders in that directory.
has anyone else had any luck with this? are there any other documented solutions that anyone else has come across?
will i need to upgrade to a more recent version of final cut to fix this issue? or would down grading to tiger be better?
thanks for any input…
Hi I got as far as –
cd /Library/StartupItems/Qmaster
rm -f .disabled
sudo chmod 755 Qmaster
but then it asked me for a password and i couldn’t go on any further.
This is the first time I’ve used Terminal or even heard of it, so my skill level is close to zero
Many thanks
I have tried what is mentioned on your guide but it did not helped.
There are no preferences setting when I click Qmaster.
I get the forked issue also, Tried all of the above. Doesn’t work.
Tried uninstalling everything and reinstalling and running the updates. Does not work.
When I try to update Compressor from 1.2 to 1.2.1 everything seems fine. But when I restart to complete the installation and check for updates it says that I’m still running Compressor 1.2 and that I should update to 1.2.1. I download that and install it, restart and the same thing happens again.
I really tried many things, but finally your advice below did it!! No more error message, and the “Cluster” setting in the Compressor window changed to “This Computer” as it should.
Thanks a lot…from today your are one of my hero’s (;->
>Launch Compressor on its on, don’t bother with Final Cut. Go to Compressor’s Preferences, and change Default Destination to Desktop, change Cluster Options to Never copy source to Cluster, and set the Default Setting to Web Download (QuickTime 7 compatible) –> H.264 100Kbps, then click Apply. Exit from Compressor, and drag a small .jpg picture to your desktop. Now you’re ready to go.
To test if the “Unable to connect to background process” problem has been fixed, launch Compressor on its own, select Import file… from the File menu, click on the .jpg on the desktop, and click Open. This will return you to the Compressor Batch window, where you can simply click on Submit. If you don’t see the error dialog, then you’re done, and please leave a comment here to say what worked for you.>
To be brief, the solution that worked for me turned out to be as simple as deleting the .disabled file, which I discovered was present in the StartupItems/Qmaster folder, as described in item #2 f Step 4 in the QMaster is not running segment of Richards blog.
Instead of using Terminal to remove that file, I located it via a search for Qmaster in that old super-utllity, FileBuddy, I selected .disabled from the list of files in FileBuddy, and I trashed .disabled from within FileBuddy. Upon restart, I was presented with a dialogue window that informed me that there was a security issue regarding this item and asking me if I wanted to Fix it. I said, Yes, Fix it.
After that, I launched Final Cut Pro HD, version 4.5, and selected the sequence I wanted to use in Compressor, version 1.21. (Compressor version 1.21 does not seem to have as wide range of choices to allow me to use a .jpg as my test case, as the suggestion indicated.) I chose my Compressor presets, my destination, and I hit the Submit button. And, this time, Compressor began to do its job. That dreaded warning window about being unable to connect to the background process no longer appeared.
The conclusion that I draw from this is that the presence of that .disabled file was preventing the QMaster background process from activating. It is possible that, during installation of Final Cut Pro on this computer, I may not have selected the option to Fix this security at that time, thus inadvertently crippling Compressor from operating. The corollary that others may infer from this is that, it may not be necessary to reinstall all of Final Cut Pro in order to cure the problem, but, if you do have to go through the process of completely re-installing, be sure to agree to Fix that alleged security issue, if requested during the installation process, else you, too, might inadvertently cause Compressor to be disabled.
I did all this on a PowerMac G4 single processor running Final Cut Pro 4.5 and Compresssor 1.21 within Mac OS 10.4.9 at 1.25 MHz.
Thank you, Richard, for taking the time to thoroughly explain the programming code and interactions between Final Cut Pro, Compressor, and QMaster, as well as to provide a set of trouble-shooting paths to take and solutions to offer. To my way of thinking, this is exactly how tech support should be delivered, in contrast to the Twitteriffic crowd who mistakenly think that short notes without in-depth, user friendly explanation does the job. It does not. Your method should set the standard for how such support ought to be given.
Richard, I have the error in Compressor “Unable to submit to queue”. I am able to see that qmaster is running in the activity montior. However I get these results in my settings via the Terminal
Current settings:
-sharingType servicesAndQuickCluster
-launchContentAgent off
-log 3 truncate on
-statusMenu off
Exception: no config file entry for service “jobcontroller:com.apple.qmaster.cluster.admin”
Other errors I get when I follow your steps to enable quick clustering are:
Exception: no config file entry for service “servicecontroller:com.apple.stomp.transcoderx”
and to make sure Qmaster is enabled for Compressor and Rendering services is this error:
Exception: no config file entry for service “servicecontroller:com.apple.qmaster.executor”
I have lost the install discs and now I am unable to use Compressor. Any help is of great appreciation. Thanks
I bought my G5 from ebay which came with FCP studio. Every time i try to export a sequence through compressor to DVD studio pro, the compressor program doesnt seem like it fully opens… only the batch window and inspector pop up. I get the same thing “unable to connect to background process” when I try to submit a batch. Ive tried the repair compresssor app, which includes the windows reset, but it says the version of compressor not identified. I cant reinstall Compressor or FCP because I did not get the actually program CDs when I bought the used G5. Is there anyway I can get Compressor working, or do I have to buy/download Compressor? Thanks
This is a different question but maybe you have some ideas.
When I try and submit a batch “This Computer” doesn’t show up under my cluster options – any advice?