back to phpList.org

Error: Process Killed by other process - Entry point problem?


#1

Greetings!

I recently updated to phpList v3.3.6 and yesterday I started sending a new Mailing. The send fails repeatedly with this error:

Error: Process Killed by other process

I asked my web host what was happening (i.e. why the mailing process gets killed off) and they replied:
I have checked the server logs and found that your account is reaching the
resources limits and that is causing the reported problems. Your account is
located on a shared environment and in order to protect the server stability and
the other clients located on the same server we had to limit the amount of
resources an account can use. More details about those limitations can be found
at:

https://hostpapasupport.com/limits-restrictions-shared-web-hosting/

In the past 24 hours it reached the Entry Points limit 53 times and I think that
that is causing the issues you reported

So this limit on “Entry Points” - I do not know what that is, but it appear this is why my mailing process is killed.

I am currently sending at:
2 messages sent in 61.66 seconds (116 msgs/hr)
So that should NOT be an issue with so few emails per minute!!

Any ideas how this can be fixed? (and what an “Entry Point” is?)
THANK you for your assistance!!

Regards,
The Only Sheet


#2

If you look further down the page you linked to, you will see Entry points are the number of processes used to serve actual website content.

To me that means you are limited to the number of processes (or sometimes this might refer to files or pages displayed) but the page does not make it very clear as to the time limit for the number of entry points.

If for example you are on the Starter package, is it 10 entry points per minute, per hour, per day?? Not very clear.


#3

I asked them and they said:

Entry processes are the number of processes that enter your account. For example, every PHP page that is accessed by a user will usually generate a single entry process. That limit is for concurrent processes. Let us know if you have any other question or concern and our team will assist you right away.

Does this helps? Any ideas how many processes the phpList needs/requires and if there is a way to reduce its footprint while sending to a list? (i.e. since I send 1 email per 30 seconds, it shouldn’t leave the process open all the time, right?)

Thanks!


#4

Still trying to figure this out… Perhaps my settings are not good?! Here is what I got in my config:
define(“MAILQUEUE_BATCH_SIZE”,0);
define(“MAILQUEUE_BATCH_PERIOD”,100);
define(‘MAILQUEUE_THROTTLE’,30);

Should I be using Batch processing to reduce the footprint? (i.e. use less processes - would that work to reduce the number of processed used by phpList?). How is this done if, let’s say, I’m ok with sending an email each 30 seconds? (or even 1 per minute if that makes it work…)

Help!!
TOS


#5

I played around with my send speed - set it to send 1 email per minute (ZZzzz!!!) but after 43 minutes, that stopped with the error:

Unable get lock for processing

There were 3 ‘alive’ in the last entry of phplist_sendprocess
I killed those and restarted.

How can sending 1 email per 60 seconds be too much for a server? Or is there something amiss in phpList? I’m confused… and I don’t know what to try next. This worked fine in the last mailing I sent a couple of weeks ago…

Any ideas?

TOS


#6

@TheOnlySheet It looks like there are several instances of phplist running. One cause is that the process fails but does not terminate.

If you want to process the queue through the browser then you should change the batch settings to use batch processing with a batch period of 60s and batch size commensurate with that.
But it is better to use a cron job, which will have fewer restrictions.


#7

I have to use the browser, as I don’t have cron access on my web host.

I tested with these values:
define(“MAILQUEUE_BATCH_SIZE”,1);
define(“MAILQUEUE_BATCH_PERIOD”,45);
define(‘MAILQUEUE_THROTTLE’,30);

It results in:
1 messages sent in 30.96 seconds (116 msgs/hr)
Finished this run
Waiting for 30 seconds before reloading

How can this use too much of the server’s resources!?!


#8

@TheOnlySheet are you still getting the “killed by other process” message?

That indicates the phplist process that is not terminating properly. That then causes a build-up of zombie processes that hits the hosting limit of the allowed number of processes, nothing to do with processing resources such as cpu time or memory.


#9

Tried again and after sending a small batch (got 40 out this time), then I am getting: Unable get lock for processing

I jump in phpMyadmin and delete the ‘3’ alive in phplist_sendprocess
The restart for another tiny batch… sigh