No PumaWorkerKiller logs when upgrading to Puma 4.1.0

zombocom / puma_worker_killer

Automatically restart Puma cluster workers based on max RAM available

747 stars 77 forks source link

No PumaWorkerKiller logs when upgrading to Puma 4.1.0 #76

Closed ernestojpg closed 4 years ago

ernestojpg commented 4 years ago

Hi all,

I noticed that I lost the typical PumaWorkerKiller log messages from stdout ("PumaWorkerKiller: Consuming X mb with master and Y workers.") when I updated the version of Puma from 4.0.1 to Puma 4.1.0.

Could it be related to this change introduced in Puma 4.1.0?

Regards.

ernestojpg commented 4 years ago

OK, it seems the problem was the change I mentioned before. It has been reverted in the new Puma 4.1.1, and logs work again.

Closing this ticket.