parallel: Context apparently died but still running?

Hi,

I’m using amp and parallel from about 1 year ago with no issues at all. Recently, I have updated both using Composer and now, from time to time, I’m getting this error:

[2018-05-04 08:30:04] app.CRITICAL: Error sending ID 4833. Error: The channel closed unexpectedly. Did the context die? {“script”:“Watcher.php”} []

The weird thing is that according to my log’s the thread is still running:

[2018-05-04 08:30:04] app.INFO: Processing ID 4833 {"script":"Watcher.php"} []
[2018-05-04 08:30:04] app.CRITICAL: Error sending ID 4833. Error: The channel closed unexpectedly. Did the context die? {"script":"Watcher.php"} []
----- AT THIS POINT THE THREAD SHOULD BE DEAD, BUT I'M GETTING LOGS FROM IT ----
[2018-05-04 08:32:45] app.INFO: Sending batch 0 to 1000 emails ID 4833 {"script":"Watcher.php"} []
[2018-05-04 08:32:50] app.INFO: Batch 0 sent ID 4833 {"script":"Watcher.php"} []
[2018-05-04 08:33:51] app.INFO: Sending batch 1 to 1000 emails ID 4833 {"script":"Watcher.php"} []
[2018-05-04 08:33:56] app.INFO: Batch sent 1 ID 4833 {"script":"Watcher.php"} []
[2018-05-04 08:34:19] app.INFO: Sending batch 2 to 1000 emails ID 4833 {"script":"Watcher.php"} []
[2018-05-04 08:34:26] app.INFO: Batch sent 2 ID 4833 {"script":"Watcher.php"} []
[2018-05-04 08:34:29] app.INFO: Sending batch 3 to 1000 emails ID 4833 {"script":"Watcher.php"} []
[2018-05-04 08:34:38] app.INFO: Batch sent 3 ID 4833 {"script":"Watcher.php"} []
[2018-05-04 08:34:40] app.INFO: Sending batch 4 to 1000 emails ID 4833 {"script":"Watcher.php"} []
[2018-05-04 08:34:48] app.INFO: Batch sent 4 ID 4833 {"script":"Watcher.php"} []
[2018-05-04 08:34:50] app.INFO: Sending batch 5 to 278 emails ID 4833 {"script":"Watcher.php"} []
[2018-05-04 08:34:52] app.INFO: Batch sent 5 ID 4833 {"script":"Watcher.php"} []
[2018-05-04 08:34:52] app.INFO: Invalid emails ID 4833: 0 | Array ( )  {"script":"Watcher.php"} []
[2018-05-04 08:34:52] app.INFO:  Done ID 4833 | Emails sent: 5278 | Final state: sent {"script":"Watcher.php"} []

Hope you can help me, thanks!

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 23 (11 by maintainers)

Most upvoted comments

Should we read the contents from the stderr stream when getting a channel exception, as typically the reason is to be found on stderr (error message)? And attach that to the exception message