procmail + PostMaster.pl does not push into queues

[kyiyer]

Hi

CentOS release 5.5 (Final)
OTRS 3.2.2

postfix and procmail and otrs.PostMaster.pl were working like a dream but they stopped suddenly. Have tried everything I could but postfix -> procmail -> otrs.PostMaster.pl simply does not send mails into queues. If I were to cat /opt/otrs/var/spool/1 | /opt/otrs/bin/otrs.PostMaster.pl works perfectly. Something messing up through procmail.

I have tried two variations of .procmailrc

The standard one is here

**********************************************************
* .procmailrc
**********************************************************
:0 :
| /opt/otrs/bin/otrs.PostMaster.pl
**********************************************************

The above recipe leads to the following error in the procmail log and results in a file being created in /opt/otrs/var/spool

******************************************************************************************************************************************************************************
procmail: [21002] Mon Mar 11 19:49:52 2013
procmail: Couldn't determine implicit lockfile from "/opt/otrs/bin/otrs.PostMaster.pl"
procmail: Locking ".lock"
procmail: Error while writing to "_KIF.IgePRB.del-syslog"
procmail: Lock failure on ".lock"
procmail: Executing "/opt/otrs/bin/otrs.PostMaster.pl"
procmail: [21002] Mon Mar 11 19:49:53 2013
procmail: Non-zero exitcode (-25) from "/opt/otrs/bin/otrs.PostMaster.pl"
procmail: Assigning "LASTFOLDER=/opt/otrs/bin/otrs.PostMaster.pl"
procmail: Locking "/opt/otrs/var/spool/..lock"
procmail: Assigning "LASTFOLDER=/opt/otrs/var/spool/18"
procmail: Opening "/opt/otrs/var/spool/18"
procmail: Acquiring kernel-lock
procmail: Unlocking "/opt/otrs/var/spool/..lock"
procmail: Notified comsat: "otrs@0:/opt/otrs/var/spool/18"
From Traffic@ndtv.com Mon Mar 11 19:49:52 2013
Subject: OSC files of NDTV Profit for 12th March 2013
Folder: /opt/otrs/var/spool/18 75280
******************************************************************************************************************************************************************************

If I were to remove the second colon, the errors in procmail log go away

******************************************************************************************************************************************************************************
* .procmailrc
******************************************************************************************************************************************************************************
:0
| /opt/otrs/bin/otrs.PostMaster.pl
******************************************************************************************************************************************************************************

This results in the following entries in procmail log
******************************************************************************************************************************************************************************
procmail: [21059] Mon Mar 11 20:01:42 2013
procmail: Executing "/opt/otrs/bin/otrs.PostMaster.pl"
procmail: [21059] Mon Mar 11 20:01:43 2013
procmail: Assigning "LASTFOLDER=/opt/otrs/bin/otrs.PostMaster.pl"
procmail: Notified comsat: "otrs@:/opt/otrs/bin/otrs.PostMaster.pl"
From RUCHIKA@NDTV.COM Mon Mar 11 20:01:42 2013
Subject: Password please
Folder: /opt/otrs/bin/otrs.PostMaster.pl 2931
******************************************************************************************************************************************************************************

But the lack of errors means that neither a ticket is created in OTRS nor a file is created in /opt/otrs/var/spool.

What am I doing wrong? How do I debug this?

Thanks a million

Iyer

[crythias]

make sure you include

Code: Select all

:0 :
$SYS_HOME/var/spool/.

to spool email it can't get

[kyiyer]

Hi

Yes, that part is there - which is why the files get created in /opt/otrs/var/spool directory

Any idea why procmail generates those logs that it does?

Thanks

Iyer

[crythias]

which is why the files get created in /opt/otrs/var/spool directory

They get created there usually because you've changed the label of, for instance, priority

[kyiyer]

I am sorry but I don't understand the changing the label of priority. My current .procmailrc is. What is wrong with the two effective recipies? In fact, the second recipe is working find - that creates a file in /opt/otrs/var/spool. The first recipe that is supposed to hand over the mail to PostMaster.pl does not seem to be working. How can I debug this, please?

Thanks a bunch for all your help

Iyer



# --
# .procmailrc - procmailrc of the OTRS user
# Copyright (C) 2001-2012 xxx, http://otrs.org/
# --
# $Id: .procmailrc.dist,v 1.9 2012/11/20 14:25:12 mh Exp $
# --
# This software comes with ABSOLUTELY NO WARRANTY. For details, see
# the enclosed file COPYING for license information (AGPL). If you
# did not receive this file, see http://www.gnu.org/licenses/agpl.txt.
# --

#SYS_HOME=/opt/otrs/
SYS_HOME=$HOME

SHELL=/bin/sh
PATH=/bin:/usr/bin:/usr/local/bin
MONTHFOLDER=`date +%Y-%m`
YEARFOLDER=`date +%Y`
LOGFILE=$SYS_HOME/var/log/procmail-$MONTHFOLDER.log
VERBOSE=on

:0
| $SYS_HOME/bin/otrs.PostMaster.pl

#:0
#| /opt/otrs/bin/otrs.PostMaster.pl

# spool all the rest (which the otrs.PostMaster.pl can't process!)
# If the database is down or the otrs.PostMaster.pl exit was not '0'!

:0 :
$SYS_HOME/var/spool/.

[kyiyer]

Hi

The problem is the lock part in the .procmailrc recipe

:0: in procmailrc generates the following error in procmail log

procmail: Couldn't determine implicit lockfile from "/opt/otrs/bin/otrs.PostMaster.pl"
procmail: Locking ".lock"
procmail: Error while writing to "_1IG.oGzPRB.del-syslog"
procmail: Lock failure on ".lock"
procmail: Executing "/opt/otrs/bin/otrs.PostMaster.pl"
procmail: [25141] Tue Mar 12 19:16:17 2013
procmail: Non-zero exitcode (-25) from "/opt/otrs/bin/otrs.PostMaster.pl"

Why should this be so? Could this be anything to do with rights or the user context under which the process is executing? Any ideas at all, please?

This is super killing me!

[crythias]

http://www.mhonarc.org/archive/html/pro ... 00320.html

"Error while writing to" is in the procmail manpage ('man procmail'), where it is described as "Nonexistent subdirectory, no write permission, pipe died or disk full."

Makes sense to me

do a df
or a df -i (inodes)

but they stopped suddenly.

If you've done nothing to otrs, and this is "sudden", then check the disk.

[kyiyer]

Hi

The same error has started coming again - no changes in the last 24 odd hours to OTRS configuration

procmail logs shows

procmail: [9118] Thu Sep 12 19:24:57 2013
procmail: Couldn't determine implicit lockfile from "/opt/otrs/bin/otrs.PostMaster.pl"
procmail: Locking ".lock"
procmail: Executing "/opt/otrs/bin/otrs.PostMaster.pl"
procmail: Non-zero exitcode (-25) from "/opt/otrs/bin/otrs.PostMaster.pl"
procmail: Assigning "LASTFOLDER=/opt/otrs/bin/otrs.PostMaster.pl"
procmail: Unlocking ".lock"
procmail: Locking "/opt/otrs/var/spool/..lock"
procmail: Assigning "LASTFOLDER=/opt/otrs/var/spool/1"
procmail: Opening "/opt/otrs/var/spool/1"
procmail: Acquiring kernel-lock
procmail: Unlocking "/opt/otrs/var/spool/..lock"
procmail: Notified comsat: "otrs@0:/opt/otrs/var/spool/1"
From Iyer@ndtv.com Thu Sep 12 19:24:57 2013
Subject: Another test
Folder: /opt/otrs/var/spool/1 3128



df -i shows

Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/mapper/VolGroup00-LogVol00 8936928 120473 8816455 2% /
/dev/sda1 26104 41 26063 1% /boot
tmpfs 505464 1 505463 1% /dev/shm

Please advise and help - I am getting nowhere. I understand from the df that there is no disk problem like space. And I can't see any permission problems

If I run

service otrs restart

all the mails in /opt/otrs/var/spool get processed, new ticket notifications get sent and tickets are generated in OTRS - so Postmaster.pl does not have a space problem or a rights problem - whatever is the problem only manifests itself when Postmaster.pl is called by procmail

What do I do?

please help

Many, many thanks

Most grateful

Iyer

[crythias]

There's no error when writing to, so there's something else, that isn't disk issue.

[kyiyer]

Thanks for your response

Any other pointers at all?

Please help

I have got OTRS implemented in my teams with great difficultly - can't afford for it to fail - I do not want to stop.

Please, please help

Thanks

Iyer

There's no error when writing to, so there's something else, that isn't disk issue.

[crythias]

I can't help without understanding more about what might have changed. Since that is impossible to handle in a forum for this random occurrence, I can only see what I can see.

Perhaps restart the otrs server might help? I don't know.