beanstalkd | Development repository for the beanstalkd cookbook | Infrastructure Automation library

I would like to implement a queuing mechanism for sending out email via PHPMailer on Amazon EC2. I have set up Beanstalkd correctly on the server and can access it via a console. The mail doesn't seem to go through (trying the various combinations of sample code). In addition do I need to set up a cron job also that would call one of the producer or consumer files?

Does anyone have working code for sending out email via phpmailer/pheanstalk please for Amazon EC2?

Thanks.

Good day to you all!

I have a Ubuntu 18.04 LTS server with MySQL 8.0 and ProFTPD 1.3.5e Server.

I used these instructions to set up MySQL authentication for ProFTPd.

https://medium.com/@nico26deo/how-to-set-up-proftpd-with-a-mysql-backend-on-ubuntu-c6f23a638caf

And it works great!

The article above sets up the first user "test" with a UID of 5500 and a GID of 5500. It says that the FTP user directory should be created and chowned to 5500:5500. All very nice.

What it does not say is what to do when the second and third and successive users come along. It is easy to create new users in the database with an INSERT query but should the UID and GID be unique to the new ftp user? If so, is there an easy way to get MySQL to AUTO_INCREMENT the new values above 5500 and 5500 respectively?

Obviously, outside of that query, I will need an auxiliary process that creates the directory and chowns it to the correct UID and GID in the database. My thoughts is as follows:

1. INSERT the new ftp user name, password, homedir into the database. This would include what ever UID and GIU need to be inserted.
2. Create a beanstalkd task to create homedir for the new ftp user and pass the ftp user name used in the SELECT query.
3. The FTP server would check beanstalkd and find out it has a task to perform.
4. The FTP server would query the db for the details associated with the new ftp user. (e.g. homedir, UID,GID,etc)
5. The FTP server would create the new user's homedir and chown it to the UID and GID in the database.

So to make my questions crystal clear:

1. Should the UID and GID be unique to the new ftp user?
2. And if so, in the context of ProFTPD auth from MySQL, is there an easy way to get MySQL to AUTO_INCREMENT the new values starting at 5500 and 5500 respectively?

Thanks!

I have a Laravel 5.3 installation running as a pure API application and need to connect from several different applications.

Everything is working fine (after all it's Laravel we're talking about :P), except I can't figure out one thing:

I have a MQTT server that is listening for messages from several devices (doesn't matter what). These messages contain information about a Job Class and method that need to be called on the backend.

I can't call the API directly, the devices simply don't support this (they do, but it's a lot more effort than using MQTT to transmit data). My thought was to push a new job onto the queue defining which Laravel Job Class to call (and which method). The problem is the JSON serialization...

The MQTT server is running on NodeJS, my queues are running on Redis. I remember a Tweet from Taylor where he mentioned that theoretically it could be possible to serialize the JSON needed and push to the queue from outside Laravel, and have the job processed by Laravel.

Anyone any idea how to approach this? Is there a documentation available about the structure of the JSON?

I should also mention that this solution NodeJS push queue, consumed by Laravel worker did not work for me. Same result as above, the job is placed on the queue but discarded without being processed or any errors thrown.

The sample data structure for a queued Event in Redis looks like this:

"{\"job\":\"Illuminate\\\\Broadcasting\\\\BroadcastEvent\",\"data\":{\"event\":\"O:28:\\\"App\\\\Events\\\\NotificationEvent\\\":5:{s:7:\\\"\\u0000*\\u0000name\\\";s:12:\\\"notification\\\";s:4:\\\"data\\\";a:4:{s:4:\\\"testkey\\\";s:14:\\\"testval\\\";s:9:\\\"timestamp\\\";s:19:\\\"2017-02-24 11:07:48\\\";s:5:\\\"event\\\";s:12:\\\"notification\\\";s:5:\\\"class\\\";s:28:\\\"App\\\\Events\\\\NotificationEvent\\\";}s:10:\\\"\\u0000*\\u0000channel\\\";N;s:7:\\\"\\u0000*\\u0000user\\\";O:45:\\\"Illuminate\\\\Contracts\\\\Database\\\\ModelIdentifier\\\":2:{s:5:\\\"class\\\";s:8:\\\"App\\\\User\\\";s:2:\\\"id\\\";i:2;}s:6:\\\"socket\\\";N;}\"},\"id\":\"XuUKRTf8CTSdzaVgp2gRcvmxQqLcpBUG\",\"attempts\":1}"

Based on that structure, I would think the object (that needs to be serialized) should look similar to this:

I am not that familiar with Beanstalkd.

My list of jobs ready is just increasing over time and I need to discover which tube is processing broken jobs. Is there a way to pause a Beanstalkd tube to try to process the jobs on that queue and let other tubes take priority to be processed?

I am trying to avoid to lose all the jobs on the queue and discover a way to let other jobs to be processed while we fix and find the broken tube.

Thanks for any help.

Answer: My patch to Tinker docs now made it to official Laravel documentation, see the warning frame here: https://laravel.com/docs/6.x/artisan#tinker

Yesterday I noticed this really weird Laravel queue behavior, where the queue always waits for the NEXT job to be scheduled to process the previously scheduled one. Please help me understand what is going on.

Whenn I send the following sequence via telnet I get EXPECTED_CRLF:

Integrated Pheanstalk library in my web app. Created three tubes for three type of jobs. Created a beanstalkd web console also to see the job status. All are working fine.

The issue is, today when I checked the console, one of the tubes is missing. I restarted beanstalkd and it appeared and started working again. Why did this happen?

I've set up Laravel (5.5) queuing with Beanstalkd, and I'm using Supervisor. Laravel docs mention the following:

By pushing jobs to different queues, you may "categorize" your queued jobs and even prioritize how many workers you assign to various queues.

but it's never mentioned how to do that. If I have 2 queues on my beanstalkd connection, and I do the following:

I'm new to Laravel, and tried to create my first background task.

Used docs: https://laravel.com/docs/master/queues

Job: (ProcessDatabaseImport.php)