PID PostMasterMailbox running twice

[guyisIT]

While looking at my logs for something unrelated, I came across the following:

Code: Select all

[Thu Apr 24 11:10:01 2014][Notice][Kernel::System::PID::PIDCreate] Can't create PID PostMasterMailbox, because it's already running (helpdesk.domain.net/2000)!

While doing some searching here, I found this link viewtopic.php?f=62&t=24273&p=97538&hili ... ing#p97538 where crythias mentions postmaster is running twice, but I couldn't find anything about resolving that issue when using Windows. I believe this might be causing issues with some of my event notifications from being sent out/ retrieving emails in a timely fashion from IMAP (I might be creating an additional ticket for that in the future.)

Any directions on where to start looking at this to correct it?

UPDATE: I just got the following entry in my log, that might explain what was happening. I still don't know what it means at a deeper level/ how to address it:

Code: Select all

[Thu Apr 24 11:30:01 2014][Notice][Kernel::System::PID::PIDCreate] Removed PID (PostMasterMailbox/helpdesk.domain.net/2000, because 1 hour old!

[crythias]

https://www.google.com/search?q=site:fo ... postmaster
It really means what it says on the box.

You're fetching too fast.
Your connection isn't connecting/timeout after next iteration.
Things to check are related to the connection to the server that holds the email.
It means: https://www.google.com/search?q=trouble ... ith+telnet

[guyisIT]

I've narrowed it down to happening when I set any agent preference to receive notification of new ticket, etc.
Turning that feature off fixes everything (emails not being deleted from the inbox of any queue email, notification events not occuring, replies not going out.)

I'm going to try the instant SMTP post you have viewtopic.php?f=60&t=20319 at a later point. Right now I'm trying to get some other event based notifications working!

[crythias]

I've narrowed it down to happening when I set any agent preference to receive notification of new ticket, etc.

This could be because the send-from (Notification Sender) for agent notifications is blank and the email server can't handle it.

[guyisIT]

So this is to provide closure to what my issue was:

I had SysConfig > Core::SendMail configured, and I had all of the Queues setup with valid emails to send from (and within Exchange, all sender emails had the appropriate Send As permissions w/ my Core::SendMail address.)

Ends up my SysConfig> Core > NotificationSenderEmail was set to the default (otrs@<OTRS_CONFIG_FQDN>). This isn't a valid address, since a) I don't have an "otrs@domain" email and b) the OTRS FQDN (Fully Qualified Domain Name) wasn't my domain, but rather the full OTRS Server name. To fix it, I matched it to the Core::SendMail email address. Now, when I set my agent preferences to notifiy me of new tickets, it sends the email correctly.

Thanks to everyone (aka: crythias) for all of your help- you and this form make open source OTRS usable!