mail bounced

Always this error comes in my kolab2.1 server have any one
idea regarding this


Command time limit exceeded: "/kolab/bin/php"

with regds
rajnish

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Dear friends
                      We have  installed kolab server with
800 users
with good config hardware machine. My problem is after 1
year
successful running kolab2.1 is bouncing mails with this
error  "
Command time limit exceeded: "/kolab/bin/php''
kindly any one have solution about this.

with regds
rajnish

On Jan 2, 2008 2:19 PM, rajnish krishna
<krishnarajnishguptagmail.com> wrote:
> Always this error comes in my kolab2.1 server have any
one idea regarding this
>
>
> Command time limit exceeded:
"/kolab/bin/php"
>
> with regds
> rajnish
>

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

The related line in postfix.log could help.


On Jan 4, 2008 3:08 PM, rajnish krishna
<krishnarajnishguptagmail.com> wrote:
> Dear friends
>                       We have  installed kolab server
with 800 users
> with good config hardware machine. My problem is after
1 year
> successful running kolab2.1 is bouncing mails with this
error  "
> Command time limit exceeded: "/kolab/bin/php''
> kindly any one have solution about this.
>
> with regds
> rajnish
>
>
> On Jan 2, 2008 2:19 PM, rajnish krishna
<krishnarajnishguptagmail.com> wrote:
> > Always this error comes in my kolab2.1 server have
any one idea regarding this
> >
> >
> > Command time limit exceeded:
"/kolab/bin/php"
> >
> > with regds
> > rajnish
> >
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-userskolab.org
> https:
//kolab.org/mailman/listinfo/kolab-users
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

rajnish krishna wrote:
> Dear friends
>                       We have  installed kolab server
with 800 users
> with good config hardware machine. My problem is after
1 year
> successful running kolab2.1 is bouncing mails with this
error  "
> Command time limit exceeded: "/kolab/bin/php''
> kindly any one have solution about this.

Hello!

In php.ini you have something like this:

;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;

max_execution_time = 30     ; Maximum execution time of each
script, in 
seconds
max_input_time = 60 ; Maximum amount of time each script may
spend 
parsing request data

[...]

And your php script is hitting that limit. As a quick
workaround you can 
increase the max_execution_time... However you should debug
this further 
because something is taking way to long to complete. Maybe
the 
anti-virus or anti-spam? Maybe other services are using all
the CPU or 
I/O available?

Peace,
Nuno Silva

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Dear
           I have checked "max_execution_time" is
is already more than 30.

I am in trouble kindly resolve my issue bcz i am in
production server.

This is my postfix.log

Jan 07 15:36:56 indo <warning> postfix/pipe[1797]:
warning:
pipe_command_read: read time limit exceeded
Jan 07 15:36:56 indo <info> postfix/pipe[1797]:
F3D86859C01E:
to=<pawan.krishnaindo.com>, relay=kolabmailboxfilter,
delay=1001,
status=bounced (Command time limit exceeded:
"/kolab/bin/php")


with regds
rajnish krishna gupta

On Jan 5, 2008 3:36 AM, Nuno Silva <nuno.silvavgertech.com> wrote:
> rajnish krishna wrote:
> > Dear friends
> >                       We have  installed kolab
server with 800 users
> > with good config hardware machine. My problem is
after 1 year
> > successful running kolab2.1 is bouncing mails with
this error  "
> > Command time limit exceeded:
"/kolab/bin/php''
> > kindly any one have solution about this.
>
> Hello!
>
> In php.ini you have something like this:
>
> ;;;;;;;;;;;;;;;;;;;
> ; Resource Limits ;
> ;;;;;;;;;;;;;;;;;;;
>
> max_execution_time = 30     ; Maximum execution time of
each script, in
> seconds
> max_input_time = 60 ; Maximum amount of time each
script may spend
> parsing request data
>
> [...]
>
> And your php script is hitting that limit. As a quick
workaround you can
> increase the max_execution_time... However you should
debug this further
> because something is taking way to long to complete.
Maybe the
> anti-virus or anti-spam? Maybe other services are using
all the CPU or
> I/O available?
>
> Peace,
> Nuno Silva
>

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

"rajnish krishna" <krishnarajnishguptagmail.com> writes:

> Dear
>            I have checked
"max_execution_time" is is already more than 30.
>
> I am in trouble kindly resolve my issue bcz i am in
production server.
>
> This is my postfix.log
>
> Jan 07 15:36:56 indo <warning>
postfix/pipe[1797]: warning:
> pipe_command_read: read time limit exceeded
> Jan 07 15:36:56 indo <info> postfix/pipe[1797]:
F3D86859C01E:
> to=<pawan.krishnaindo.com>,
relay=kolabmailboxfilter, delay=1001,

kolabmailboxfilter is apparently failing here. Can you post
the log
file of the filter here?

Cheers,

Gunnar

> status=bounced (Command time limit exceeded:
"/kolab/bin/php")
>
>
> with regds
> rajnish krishna gupta
>
> On Jan 5, 2008 3:36 AM, Nuno Silva <nuno.silvavgertech.com> wrote:
>> rajnish krishna wrote:
>> > Dear friends
>> >                       We have  installed kolab
server with 800 users
>> > with good config hardware machine. My problem
is after 1 year
>> > successful running kolab2.1 is bouncing mails
with this error  "
>> > Command time limit exceeded:
"/kolab/bin/php''
>> > kindly any one have solution about this.
>>
>> Hello!
>>
>> In php.ini you have something like this:
>>
>> ;;;;;;;;;;;;;;;;;;;
>> ; Resource Limits ;
>> ;;;;;;;;;;;;;;;;;;;
>>
>> max_execution_time = 30     ; Maximum execution
time of each script, in
>> seconds
>> max_input_time = 60 ; Maximum amount of time each
script may spend
>> parsing request data
>>
>> [...]
>>
>> And your php script is hitting that limit. As a
quick workaround you can
>> increase the max_execution_time... However you
should debug this further
>> because something is taking way to long to
complete. Maybe the
>> anti-virus or anti-spam? Maybe other services are
using all the CPU or
>> I/O available?
>>
>> Peace,
>> Nuno Silva
>>
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-userskolab.org
> https:
//kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com
_______________ http://kolab-konsortium.c
om _

prdus Kolab work is funded in part by KDAB and the
Kolab Konsortium

____ http://www.pardus.de
_________________ http://gunnarwrobel.de _
E-mail : prdus.de                                 Dr. Gunnar
Wrobel
Tel.   : +49 700 6245 0000                         
Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146
Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at
prdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

On January 7, 2008, rajnish krishna wrote:
> Jan 07 15:36:56 indo <warning>
postfix/pipe[1797]: warning:
> pipe_command_read: read time limit exceeded
> Jan 07 15:36:56 indo <info> postfix/pipe[1797]:
F3D86859C01E:
> to=<pawan.krishnaindo.com>,
relay=kolabmailboxfilter, delay=1001,
> status=bounced (Command time limit exceeded:
"/kolab/bin/php")

The default for postfix command_time_limit is 1000s.   You
can see by the 
delay=1001, that you have exceeded that limit.   

This limit is not PHP enforced, but postfixs pipe delivery. 
The pipe program 
uses command_time_limit as it's default time limit.  The
transport 
kolabmailboxfilter uses pipe to pass off the data to the PHP
script as the 
transport.

When postfix hands off the data via pipe it is taking longer
than 1000s (or 
almost 17minutes).  Which is quite alarming.

Have you checked the resources on this server?  How process
heavy is it?   How 
is the memory?   How is the disk I/O?  If you have 800
users, during peak 
performance you could quite easily tie up all of the
resources, and 
processing grinds to a halt.

You also did not mention if this was bouncing all email, or
just some.   If it 
is just some, it is most likely during overload when this
occurs.  You could 
probably fix this by increasing command_time_limit in
main.cf.template, but I 
think if this is happening frequently you are pushing the
limits of your 
server, and should look to upgrade.  You wouldn't want a
processing delay of 
30 mins per email, just because the server is too busy to
handle the load.


Andy

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Dear sir
                  Here is the log file


January 07 16:45:07 kolabmailboxfilter.php[13748]: Debug:
Kolabmailboxfilter successfully completed
January 07 16:45:07 kolabmailboxfilter.php[13756]: Debug:
Kolabmailboxfilter starting up, sender=sandeep.malhotraindo.com,
recipients=pkmisraindo.com, client_address=127.0.0.1
January 07 16:45:07 kolabmailboxfilter.php[13751]: Debug:
Kolabmailboxfilter starting up, sender=sandeep.malhotraindo.com,
recipients=idrees.khanindo.com, client_address=127.0.0.1
January 07 16:45:07 kolabmailboxfilter.php[13757]: Debug:
Kolabmailboxfilter starting up, sender=sandeep.malhotraindo.com,
recipients=akrainaindo.com, client_address=127.0.0.1
January 07 16:45:07 kolabmailboxfilter.php[13752]: Debug:
Kolabmailboxfilter starting up, sender=sandeep.malhotraindo.com,
recipients=kapil.guptaindo.com, client_address=127.0.0.1
January 07 16:45:07 kolabmailboxfilter.php[13754]: Debug:
Kolabmailboxfilter starting up, sender=sandeep.malhotraindo.com,
recipients=manish.khandelwalindo.com,
client_address=127.0.0.1
January 07 16:45:07 kolabmailboxfilter.php[13763]: Debug:
Kolabmailboxfilter starting up, sender=sandeep.malhotraindo.com,
recipients=skwadhwaindo.com, client_address=127.0.0.1
January 07 16:45:07 kolabmailboxfilter.php[13761]: Debug:
Kolabmailboxfilter starting up, sender=sandeep.malhotraindo.com,
recipients=shivshankar.royindo.com,
client_address=127.0.0.1
January 07 16:45:08 kolabfilter.php[13769]: Debug:
Kolabfilter
starting up, user=, sender=apradhanindo.com,
recipients=balwantsinghindo.com, client_address=127.0.0.1
January 07 16:45:08 kolabfilter.php[13769]: Debug:
Kolabfilter
successfully completed
January 07 16:45:08 kolabmailboxfilter.php[13757]: Debug:
Kolabmailboxfilter successfully completed
January 07 16:45:08 kolabmailboxfilter.php[13763]: Debug:
Kolabmailboxfilter successfully completed
January 07 16:45:08 kolabmailboxfilter.php[13752]: Debug:
Kolabmailboxfilter successfully completed
January 07 16:45:08 kolabmailboxfilter.php[13754]: Debug:
Kolabmailboxfilter successfully completed
January 07 16:45:08 kolabmailboxfilter.php[13761]: Debug:
Kolabmailboxfilter successfully completed
January 07 16:45:08 kolabmailboxfilter.php[13756]: Debug:
Kolabmailboxfilter successfully completed
January 07 16:45:08 kolabmailboxfilter.php[13751]: Debug:
Kolabmailboxfilter successfully completed
January 07 16:45:08 kolabmailboxfilter.php[13771]: Debug:
Kolabmailboxfilter starting up, sender=apradhanindo.com,
recipients=balwantsinghindo.com, client_address=127.0.0.1
January 07 16:45:09 kolabmailboxfilter.php[13771]: Debug:
Kolabmailboxfilter successfully completed
January 07 16:45:09 kolabfilter.php[13772]: Debug:
Kolabfilter
starting up, user=, sender=anil.dhimanindo.com,
recipients=wahid.khanindo.com, client_address=127.0.0.1
January 07 16:45:09 kolabfilter.php[13772]: Debug:
Kolabfilter
successfully completed


with regds
rajnish

On Jan 7, 2008 4:41 PM, Andrew J. Kopciuch <akopciuchbddf.ca> wrote:
> On January 7, 2008, rajnish krishna wrote:
> > Jan 07 15:36:56 indo <warning>
postfix/pipe[1797]: warning:
> > pipe_command_read: read time limit exceeded
> > Jan 07 15:36:56 indo <info>
postfix/pipe[1797]: F3D86859C01E:
> > to=<pawan.krishnaindo.com>,
relay=kolabmailboxfilter, delay=1001,
> > status=bounced (Command time limit exceeded:
"/kolab/bin/php")
>
> The default for postfix command_time_limit is 1000s.  
You can see by the
> delay=1001, that you have exceeded that limit.
>
> This limit is not PHP enforced, but postfixs pipe
delivery.  The pipe program
> uses command_time_limit as it's default time limit. 
The transport
> kolabmailboxfilter uses pipe to pass off the data to
the PHP script as the
> transport.
>
> When postfix hands off the data via pipe it is taking
longer than 1000s (or
> almost 17minutes).  Which is quite alarming.
>
> Have you checked the resources on this server?  How
process heavy is it?   How
> is the memory?   How is the disk I/O?  If you have 800
users, during peak
> performance you could quite easily tie up all of the
resources, and
> processing grinds to a halt.
>
> You also did not mention if this was bouncing all
email, or just some.   If it
> is just some, it is most likely during overload when
this occurs.  You could
> probably fix this by increasing command_time_limit in
main.cf.template, but I
> think if this is happening frequently you are pushing
the limits of your
> server, and should look to upgrade.  You wouldn't want
a processing delay of
> 30 mins per email, just because the server is too busy
to handle the load.
>
>
> Andy
>

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

On January 7, 2008, rajnish krishna wrote:
> Dear sir
>                   Here is the log file
>
>
> January 07 16:45:07 kolabmailboxfilter.php[13748]:
Debug:
> Kolabmailboxfilter successfully completed
> January 07 16:45:07 kolabmailboxfilter.php[13756]:
Debug:
> Kolabmailboxfilter starting up,
sender=sandeep.malhotraindo.com,
> recipients=pkmisraindo.com, client_address=127.0.0.1


That's the resmgr.log file, and it's showing you success on
the email that is 
actually successful.   The problems you were asking about
are not going to 
show up here.   They occur prior to kolabmailboxfilter even
getting 
started ... so there's going to be no log for the problems
in there.

The problem is : the mail server takes too much time to pass
the data to 
kolabmailboxfilter.  So the command times out, and the
process fails, and the 
messages bounce.

You need to see what is going on with your server resources,
and most likely 
take some action to fix the load on the resources.  You
might make this go 
away by increasing command_time_limit 
in /kolab/etc/kolab/templates/main.cf.template ... _but_
there's obviously 
something else going on there.   That will only band aid the
situation.


Andy


_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Dear sir,
               I have checked my all resources all are in
normal
condition like CPU , I/O, RAM every thing is normal
condition
but still some mails are bouncing not all. I am only
snatching my hair
 plz suggest me in this critical situation.
with regds
rajnish

On Jan 7, 2008 5:41 PM, Andrew J. Kopciuch <akopciuchbddf.ca> wrote:
> On January 7, 2008, rajnish krishna wrote:
> > Dear sir
> >                   Here is the log file
> >
> >
> > January 07 16:45:07 kolabmailboxfilter.php[13748]:
Debug:
> > Kolabmailboxfilter successfully completed
> > January 07 16:45:07 kolabmailboxfilter.php[13756]:
Debug:
> > Kolabmailboxfilter starting up,
sender=sandeep.malhotraindo.com,
> > recipients=pkmisraindo.com,
client_address=127.0.0.1
>
>
> That's the resmgr.log file, and it's showing you
success on the email that is
> actually successful.   The problems you were asking
about are not going to
> show up here.   They occur prior to kolabmailboxfilter
even getting
> started ... so there's going to be no log for the
problems in there.
>
> The problem is : the mail server takes too much time to
pass the data to
> kolabmailboxfilter.  So the command times out, and the
process fails, and the
> messages bounce.
>
> You need to see what is going on with your server
resources, and most likely
> take some action to fix the load on the resources.  You
might make this go
> away by increasing command_time_limit
> in /kolab/etc/kolab/templates/main.cf.template ...
_but_ there's obviously
> something else going on there.   That will only band
aid the situation.
>
>
> Andy
>
>

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users