"Stray process with PGID equal to this dead job..." in Console

I keep getting these errors in Console:
24/06/08 11:36:18 AM com.apple.launchd[1] (org.postfix.master[2376]) Stray process with PGID equal to this dead job: PID 2378 PPID 1 qmgr
24/06/08 11:36:18 AM com.apple.launchd[1] (org.postfix.master[2376]) Stray process with PGID equal to this dead job: PID 2377 PPID 1 pickup
Any ideas what causes this?
Thanks,
James.

Did you ever find out why these messages were happening and how to stop them?
I have the same problem - once a minute, a new set of postfix log entries appear...
Aug 20 10:45:16 devel com.apple.launchd[1] (org.postfix.master[619]): Stray process with PGID equal to this dead job: PID 620 PPID 1 pickup
Aug 20 10:45:16 devel com.apple.launchd[1] (org.postfix.master[619]): Stray process with PGID equal to this dead job: PID 621 PPID 1 qmgr
Aug 20 10:46:16 devel com.apple.launchd[1] (org.postfix.master[622]): Stray process with PGID equal to this dead job: PID 623 PPID 1 pickup
Aug 20 10:46:16 devel com.apple.launchd[1] (org.postfix.master[622]): Stray process with PGID equal to this dead job: PID 624 PPID 1 qmgr
Aug 20 10:47:16 devel com.apple.launchd[1] (org.postfix.master[625]): Stray process with PGID equal to this dead job: PID 627 PPID 1 qmgr
Aug 20 10:48:16 devel com.apple.launchd[1] (org.postfix.master[628]): Stray process with PGID equal to this dead job: PID 630 PPID 1 qmgr
Aug 20 10:49:16 devel com.apple.launchd[1] (org.postfix.master[631]): Stray process with PGID equal to this dead job: PID 633 PPID 1 qmgr
Aug 20 10:50:16 devel com.apple.launchd[1] (org.postfix.master[634]): Stray process with PGID equal to this dead job: PID 635 PPID 1 pickup
Aug 20 10:51:16 devel com.apple.launchd[1] (org.postfix.master[637]): Stray process with PGID equal to this dead job: PID 639 PPID 1 qmgr
Aug 20 10:52:16 devel com.apple.launchd[1] (org.postfix.master[640]): Stray process with PGID equal to this dead job: PID 642 PPID 1 qmgr

Similar Messages

Stray process killed by launchd

Hi there,
I am trying to make launchd restart a Java daemon in my Mac. I finally made my plist file work. I use a shell script that kills old java process and starts it from scratch. It works but right after the shell script finishes executing launchd kills the java process with the following error:
Mar 26 21:28:42 Micaias com.apple.launchd[1] (com.skios.smtpserver[8377]): Stray process with PGID equal to this dead job: PID 8383 PPID 1 bash
Can I make launchd not to worry about that process? That is the pourpose of the plist file... here it is by the way:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Disabled</key>
<true/>
<key>Label</key>
<string>com.skios.smtpserver</string>
<key>ProgramArguments</key>
<array>
<string>/bin/sh</string>
<string>/Applications/ServEngineSMTPd/startSMTPserver.sh</string>
</array>
<key>StartInterval</key>
<integer>5</integer>
</dict>
</plist>
Thanks for any help/directions
Ignacio

try adding the following to your plist
<key>AbandonProcessGroup</key>
<true/>
then your launch daemon should look like this
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Disabled</key>
<true/>
<key>Label</key>
<string>com.skios.smtpserver</string>
<key>ProgramArguments</key>
<array>
<string>/bin/sh</string>
<string>/Applications/ServEngineSMTPd/startSMTPserver.sh</string>
</array>
<key>StartInterval</key>
<integer>5</integer>
<key>AbandonProcessGroup</key>
<true/>
</dict>
</plist>

Stray process for Postfix on a server not hosting Mail

I have three servers and each does different stuff. Well my web server has been showing an error constantly over and over again and it won't stop. It says it has to do with postfix and I'm not even running mail services on that server. So I'm not sure why it keeps showing it over and over again. Here is the error below.
Thanks.
Jul 14 09:18:35 xpmedia3 com.apple.launchd[1] (org.postfix.master[60298]): Stray process with PGID equal to this dead job: PID 60303 PPID 1 smtp

Even with mail services disabled, SMTP is set to be used on demand (think cron job, web form, etc.).
To completely disable it, issue:
sudo /bin/launchctl unload -w /System/Library/LaunchDaemons/org.postfix.master.plist
To re-enable:
sudo /bin/launchctl load -w /System/Library/LaunchDaemons/org.postfix.master.plist

Repeated postfix "Stray process" chatter in log after update to 10.5.8

After updating to 10.5.8 (via combo updater), I've been getting a bunch of odd console messages, about every minute, along the lines of the following:
com.apple.launchd[1] (org.postfix.master[6214]): Stray process with PGID equal to this dead job: PID 6216 PPID 1 qmgr
The dead job alternates seemingly at random between qmgr and pickup (both of which I can see running via Activity Monitor (owned by _postfix), and the PID increases steadily. A Google search turned up a few things along the lines of this older thread:
http://discussions.apple.com/thread.jspa?messageID=8141721
...but they largely seemed to be from people who actually were doing something with postfix, which I'm not. This is a 2009 mini with a pretty much stock OS install; I certainly haven't done anything at that low of a level, and I'm in fact not even using Mail on that system (it's a media center/file server).
The only persistent process that's running that I can imagine would have anything to do with this is Growl, which I do happen to be using to send myself notifications of failed backups. Disabling Growl didn't seem to make any difference, though.
Anybody else seen this with 10.5.8, or have any suggestions about why it might be happening? It seems to be functioning fine, but I kinda don't like bloated log files, and I like randomly spawned/killed processes without understanding them even less.

Addendum:
I just saw this in my system log, no idea what exactly it's about:
Aug 21 11:37:26 FrontRow blued[51]: Potentially fatal Bluetooth firmware error condition detected:
Aug 21 11:37:26 FrontRow blued[51]: PSKeyUser0: len = 4, error = 0x0, psKey=650, Data: 0000B22300001800
Aug 21 11:37:26 FrontRow blued[51]: PSKeyUser1: len = 4, error = 0x0, psKey=650, Data: 0000B22300001800
Aug 21 11:37:26 FrontRow blued[51]: Attempting repair...
Aug 21 11:37:27 FrontRow blued[51]: Repair complete: error = 0x0
The condition persists, and the usual ad nauseum errors resumed. Wish I didn't have to sign up to ADC to submit a conventional bug that I could update with new content like this.

Down pmnts with taxes are not permitted when processing with jur.code (Message no. FS206)

Hi Guys,
I am facing very critical issue on down Payment request, to process with saperate Tax Value.
We are supporting on Roll-out for Germany. We have implemented all standard SAP processes in the Project. We have also implemented many interfaces and one of the Interface is Sabrix Tax Engine (Tax Jurisdiction Code).
As per the Germany legal requirement, the Tax has to get calculated whenever the funds gets transfered from one Bank Account to Another Bank Account.
Coming to the issue: In the Customer Down Payment scenario, we are creating the Down payment request for Customer and as per Germany local requirement the Tax of 19% has to get calculated on Down payment.
For an Example: We have the Sales Order Contract Value of 100,000.00 EUR and we are creating the Down Payment reqeust of 10% which is 10000 EUR + Tax 19% 1900 EUR.
We are trying to post the Down Payment request in F-37 and we get the issue "Down pmnts with taxes are not permitted when processing with jur.code". This error is appearing due to Sabrix Tax engine (Tax Jurisdiction Code) has implemented in our System.
We have gone through the SAP notes 97288 and 213567 and understood that the Standard SAP does not support us to post the Down Payment request with Separate Tax Value, when the External Tax Engine has implemented.
I request you to suggest me, if you have already seen this issue in any of your Projects and fixed through the work-around solution. We have been working on work-around since 2 weeks, however no result.
Below is the error message:
Down pmnts with taxes are not permitted when processing with jur.code
Message no. FS206

HI Preeti,
Thanks for your response. We have already seen the similar SAP notes and the SAP notes explains that the "Down pmnts with taxes cannot be done along with with jur.code". The only solution is to post the DP without Tax.
However there might be some workaround which can be done in SAP, to process the Down Payment/Advance Payments with Tax Value along with Jurisdiction Code. I would like to know this.
Did any one seen this case in your experiece, if yes, what is the work-around solution?.
Need your help guys!,...
Regards,
Damodar Naidu

In Processing with SAP

Hello Experts,
I could not confirm a message when it is still "In Processing with SAP". Is this standard? How should we customize this so that messages can still be confirmed even if it is still with SAP. Thank you.
regards,
Grace

Hi Algrace,
Try with AI_SDK_SP_AUTO_CLOSE. I hope this report, You can close the message with the status "In Process By SAP" too,
but SAP's standard practise we are not supposed to close CRM ticket which are in INPROCESS by sap. this lead inconsistency. Even sap provided another report AI_SDK_SP_AUTO_CLOSE_2 which prevent the ticket confirmation when the ticket with SAP Still opens.
All the needed information for how to create this report and usage available in the SAP note 1498458 - AI_SDK_SP_AUTO_CLOSE: Eliminate status inconsistencies and also refer the sap note 1792409.
Thanks
Jansi

The computer that I original used with my ipod touch is dead, so I am now synching and backing up to a new computer. I had to restore the software to this ipod. I can drop and drag my tunes back into the ipod, but not my apps.

The computer that I originally used with my ipod touch is dead, so I am now synching with another computer. I had to restore the software of the ipod, I am able to drop and drag my tunes back to the ipod but not my purchased apps. I have no problem doing this with other ipods that I have synced and backed up to this computer.

Start here:
iPhone, iPad, or iPod touch: Device not recognized in iTunes for Windows

I have a problem with my white macbook, this message keeps popping up when I start the laptop " no matching processes belonging to you were found " even though I didn't mess up with the system or even use terminal. It just appeared

I have a problem with my white macbook, this message keeps popping up when I start the laptop " no matching processes belonging to you were found " even though I didn't mess up with the system or even use terminal. It just appeared without Doing anything!!
And now I can't use the " tap an click " from my tack-board and no nothing was spilled on my mac.
Please help

Check your login items in the Users & Groups preference pane. Remove any that you don't recognize.

What does this error means? "Line 20 column 57: character content of element "language" invalid; must be a string with length equal to 3 (actual length was 7) at XPath /package/book/metadata/languages/language" "

Hi there.
I am about to publish a book in English and Chinese.
What does this error means?
Line 20 column 57: character content of element "language" invalid; must be a string with length equal to 3 (actual length was 7) at XPath /package/book/metadata/languages/language"
And where is line 20, column 57?
Thanks folks!

Go into iTunes Producer and select from the dropdown, don't type.
cs
iBooks Author Guide

When going through the download process with social monkee and getting to the point of adding it to firefox I get the following message: 'Social Monkee could not be installed because firefox cannot modify the needed file'. How can this be fixed?

When going through the download process with social monkee and getting to the point of adding it to firefox I get the following message: 'Social Monkee could not be installed because firefox cannot modify the needed file'. How can this be fixed?

That is usually caused by a missing unpack directive (<em:unpack>true</em:unpack>) in the file install.rdf of that extension.
See https://developer.mozilla.org/En/Updating_extensions_for_Firefox_4.0#XPI_unpacking
-----

The 'JobServerChild.exe' processes with ID '6632' has been running on this

Hi team,
Automated tiket is being generated for the below following issue.
can any one suggest me how to move forward to solve the issue
The Windows Process Monitor script has determined that the 'JobServerChild.exe' processes with ID '6632' has been running on this computer for longer than the maximum acceptable time of 18000 seconds (5 hours).
Thanks
Murthy

Hi Murthy,
It sounds as though you have a schedule which is long running or the jobserverchild.exe process has become orphaned.
If you check with the Instance Manager you chould be able to see if any schedules are taking much longer than usual. The Task Manager on the XI3.1 server will also show you if any jobserverchild.exe processes are hung i.e. not consuming any CPU\memory - once located you can kill the process.
I would also recommend that you apply the -type OUTPROC switch on the Job Servers to ensure that in future the jobserverchild.exe processes are killed upon completion of the schedule task.
I hope this is a very helpful answer to you.
Kind regards,
John

This is so basic: How do you turn off Apple TV, or do you just exit by changing the Input back to regular TV? When I put Apple TV to sleep, I had to log in again, a very tedious process with that awful "announcer" for the hearing impaired (how to remove?)

This is so basic: How do you turn off Apple TV, or do you just exit by changing the Input back to regular TV? When I put Apple TV to sleep after I installed it, I had to log in again, a very tedious process with that awful "announcer" for the hearing impaired (and how to remove that?).

Welcome to the Apple Community.
The Apple TV will put itself to sleep. I'm not sure what you needed to log into again, but you shouldn't have to. Do you have a little more detail about what happens.

TS2529 my iphone updation time this message are came "We're sorry, we are unable to continue with your activation at this time" at present my iphone 3gs in dead condition

My iphone 3gs software of ios updation time iphone restart. then strat the phone but phone is not strating normal like previous version.
1. selection country
2.next region select india
3 then for wifi and select connect to itunes but that time message is came "We're sorry, we are unable to continue with your activation at this time" at present my iphone 3gs not working previous version.

https://discussions.apple.com/message/21709610#21709610

On start up i just get a grey screen with the apple logo-this has suddenly started happenin. Please help?

on start up i just get a grey screen with the apple logo-this has suddenly started happenin. Please help?

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.
Step 1
The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a startup failure can be resolved by resetting the NVRAM.
Step 4
If a desktop Mac hangs at a plain gray screen with a movable cursor, the keyboard may not be recognized. Press and hold the button on the side of an Apple wireless keyboard to make it discoverable. If need be, replace or recharge the batteries. If you're using a USB keyboard connected to a hub, connect it to a built-in port.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
Start up in safe mode. Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
Step 9
If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.
Step 10
Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 11
Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
Step 12
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 13
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

Third party process with Valuated sales order stock

Hi All,
We have third party sales order process with valuated sales order stock. The problem is that in the theird party PR which is triggered directly from the sales order it determines a stock account which is assigned to the BSX key in OBYC.
But since this is third party processing as per my understanding a consumption account assigned to key GBB-VAX (since account assignmnt category is X) should get determined, so that when the GR is done against the PO a consumption posting is done in the background.
I am not able to understand if the system is determining the stock account due to the fact that it is valuated sales order stock and if so, what should happen after GR. Should we have a stock created for the material which is physically directly delivered to the customer?
Regards,
V S

Hi,
Check GBB-VKA which is defined in OME9 for your ''E'' Account Assignment Category that SAP will debit upon GR posting
Also check "X" GBB-VAX and the G/L account assignment in OBYC
The posting on GR should be debit KBS -Credit GR-IR
Thanks
Diwakar

"Stray process with PGID equal to this dead job..." in Console

Similar Messages

Maybe you are looking for