When running as daemon worker, there are SSL errors when attempting to send email

[wyred]

I upgraded from 4.1 to 4.2.

Running as queue:work would create SSL errors, but not when running queue:listen.

Using smtp driver with mailgun as the host.

[2014-06-04 02:26:19] production.ERROR: exception 'ErrorException' with message 'fwrite(): SSL operation failed with code 1. OpenSSL Error messages:
error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry' in /var/www/app.dev/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/StreamBuffer.php:236
Stack trace:
#0 [internal function]: Illuminate\Exception\Handler->handleError(2, 'fwrite(): SSL o...', '/var/www/queues...', 236, Array)
#1 /var/www/app.dev/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/StreamBuffer.php(236): fwrite(Resource id #3337, 'MAIL FROM: <con...')
#2 /var/www/app.dev/vendor/swiftmailer/swiftmailer/lib/classes/Swift/ByteStream/AbstractFilterableInputStream.php(175): Swift_Transport_StreamBuffer->_commit('MAIL FROM: <con...')
#3 /var/www/app.dev/vendor/swiftmailer/swiftmailer/lib/classes/Swift/ByteStream/AbstractFilterableInputStream.php(92): Swift_ByteStream_AbstractFilterableInputStream->_doWrite('MAIL FROM: <con...')
...
#30 /var/www/app.dev/artisan(59): Symfony\Component\Console\Application->run()
#31 {main} [] []

[taylorotwell]

I would explore options besides it being a Laravel issue. It's a SwiftMailer exceptoin.

[reedmaniac]

Been noticing this on Forge, actually. Periodically the Queue will be unable to send an email and this error appears in my log and then it keeps on reappearing (as if the daemon never forgets it). And last night when a job failed, it was unable to make a MySQL connection. It is sporadic though and I have been unable to figure out why it sometimes fails to make these connections.

[mferrara]

Having this exact same problem, didn't start for me until I started running the queue as a daemon.

Hoping this is updated with a potential solution.

[maknz]

Daemon workers are long running PHP processes, which can have side effects from code that wasn't built with that in mind.

It looks like SwiftMailer isn't built to be run long-term. To have a guess, it looks like it might not be catering for the fact the connection can drop and errors out.

There's nothing Laravel can do about it, it's probably best to follow the discussion here or switch to one of the API drivers which don't have this problem (e.g. the built-in Mandrill support).

[mferrara]

@maknz thanks for the response, it was very enlightening. I've since moved away from the daemon approach, but thank you for shedding some light on what the actual issue was!

[anaxamaxan]

While this is indeed a SwiftMailer issue, it might be noted in the Laravel Docs that SwiftMailer doesn't do well in a daemonized queue, or at least that we should be using API drivers when using a daemonized mail queue. The related SM thread is filled with comments from Laravel users.

[YOzaz]

After some discussion with SwiftMailer developers, it looks like it should be solved from Laravel side - either by reinitializing Swift_Mailer object, either by closing Swift_Transport class object to close SMTP connection (or any other).

[GrahamCampbell]

We're open to pull requests. :)

[YOzaz]

@GrahamCampbell can you please at least mention in docs, that SwiftMailer should not be used with queue deamon worker, but used with queue listener instead?

[crynobone]

@GrahamCampbell can you please at least mention in docs

If you feel this need to be addressed in the docs, feel free to send a Pull Request (as mentioned by @GrahamCampbell) to https://github.com/laravel/docs

[YOzaz]

Made a PRs for code patch.
5.0: #8222
4.2: #8225

[mferrara]

@YOzaz <3

[YOzaz]

So, as PR didn't go through - made a package:
https://github.com/YOzaz/Laravel-SwiftMailer
Feel free to test it.
Updated: compatible with Laravel 4 and 5 now.