Problem with Bounce Manager Cron Task

[AlokSharma]

Hello,

I had setup a cron task for bounce manager but it gives the following message:

Internal Server Error

The server encountered an internal error or
misconfiguration and was unable to complete
your request.

Please contact the server administrator,
you@example.com and inform them of the time the error occurred,
and anything you might have done that may have
caused the error.

More information about this error may be available
in the server error log.


Apache/2.2.0 (Fedora) Server at http://www.xxxxxxxxx.com Port 80

I asked the host to look into this and they said:

I ran the command again and a new error shows up now:

[root@xxxx logs]# /usr/bin/curl -s --get --data run=1\;passcode=\;verbose=0 --url http://www.xxxxxxxxx.com/cgi-bin/dada/plugins/dada_bounce_handler.pl
<h1>Software error:</h1>
<pre>Pro Dada 4.9.1 Warning: Server is way too busy to open semaphore file , /home/httpd/html/xxxxxxxxx.com/cgi-bin/.dada_files/.tmp/dada_bounce_handler.lock - Resource temporarily unavailable
at ..//DADA/App/BounceHandler.pm line 344
</pre>
<p>
For help, please send mail to the webmaster (<a href="mailto:you@example.com">you@example.com</a>), giving this error message
and the time and date of the error.

The server is not overloaded but made some adjustment to see if that will fix the error. We will update you as soon as this is sorted out.

Further they said:

As we have tested this at different times, the error always shows:

Premature end of script headers: dada_bounce_handler.pl

we have enabled/disabled mod_security but the error is still the same.

Can you please figure out what could we wrong.

P.S. I have masked the identifiable information for privacy purpose.

[justin]

Who's your host?

If you think the file locking stuff is the problem, you can disable it:

http://dadamailproject.com/support/docu ... le_locking

P.S. I have masked the identifiable information for privacy purpose.

That does make it harder to help, as I can't try the script, myself,

[AlokSharma]

Its Mojohost and the script is running on a independent dedicated server.

Can I PM or mail you the required information?

[AlokSharma]

I set this to 0 but still no good.

[justin]

I set this to 0 but still no good.

Where? (In which file?) If this config param was set to 0, you wouldn't get this error.

[AlokSharma]

I changed this in cgi-bin/.dada_files/.configs file under Bounce_Handler to Enable_POP3_File_Locking => 0,

[AlokSharma]

Any update on this?

[AlokSharma]

Can you please look into this as this is holding my work.

[justin]

I'm a little confused over this:

Code: Select all

I changed this in cgi-bin/.dada_files/.configs file under Bounce_Handler to Enable_POP3_File_Locking => 0,

First off, the docs state that you should put the .dada_files in your home directory, not your cgi-bin, as that makes upgrading much easier.

Secondly, if you did make that change, you wouldn't have this problem. Can you post your .dada_config file? My guess is, well -I have a lot of guesses: This isn't your right .dada_config file or, you didn't configure the bounce handler in your .dada_config file, but rather in the script itself - and the configuration paramaters in the .dada_config file are between cut tags.

[AlokSharma]

Actually I did configure the bounce mailer plugin and double checked everything.

However, after upgrading to 5.0.3, I am now getting the following message:

Pro Dada 5.0.3 Warning: Server is way too busy to open semaphore file , /home/httpd/html/xxxxxxxxx.com/cgi-bin/.dada_files/.tmp/dada_bounce_handler.lock -   Resource temporarily unavailable
at ..//DADA/App/BounceHandler.pm line 342