I am learning laravel 5.4 "queues" chapter. I have a problem about queue:restart command. Because when I test it on my windows 10 platform, I found this command seems just kill queue worker, but not restart worker. So I wonder whether this command does not work on windows or this command is just kill worker but not restart worker? Thanks.
The queue:restart command never actually restarts a worker, it just tells it to shutdown. It is supposed to be combined with a process manager like supervisor that will restart the process when it quits. This also happens when queue:work hits the configured memory limits.
To keep the queue:work process running permanently in the background, you should use a process monitor such as Supervisor to ensure that the queue worker does not stop running.
Source: https://laravel.com/docs/5.4/queues#running-the-queue-worker
Related
I hosted my ejabberd on the AWS cloud server and accessing using putty. I start my ejabberd node using the ./ejabberdctl live command which is working perfectly fine. When I closed my putty session and start again on the next day I can't attach live logs again until I stop that running node and start again. How can I attach live logging of the previously running node?
There are typically two ways to run ejabberd:
A)
ejabberdctl live starts a new node and attaches an interactive shell immediately to it. You view the logs immediately in the shell. This is useful for debugging, testing, developing
B)
ejabberdctl start starts a new node keeping it running in the background. You can see the log messages in the log files (/var/log/ejabberd/ejabberd.log or something like that). This is useful for production servers.
Later, you can run ejabberdctl debug to attach an interactive shell to that node. This is useful when you run a production server, and want to perform some administrative task.
Is stopping MySQL Process with net stop MySQL57 safe? We are running MySQL Server on Windows Server and would like to backup whole server with file-system approach. If we would use net stop MySQL57 would it not cause any database corruption?
Using net stop and then net start is equivalent to using the services applet in the Windows control panel.
net stop also causes the service's dependent services (if any) to stop and restart. For example, IIS Admin depends on World Wide Web, NNTP, FTP and SMTP if you have those installed and running.
net stop causes the services to shutdown "properly" and re-read the Windows registry before starting again. It's the same as restarting safely. Use the service names and not the display names (which won't work anyway).
You can also use the service controller app sc as well as net start/net stop.
You can see (or should see, if it installed properly) the MySQL service in the registry along with all others under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\.
Hope that helps a bit.
In Apache Airflow, I can specify the worker queue upon starting the worker.
I have a use case where I would like to change the queue the worker is using live so that the existing worker will pull new jobs from that queue.
Is this possible?
As far as I can tell, no. You can launch a worker with airflow worker -q <queue>, but there doesn't seem to be a way to kill that worker, or interact with it at all once it's spawned.
I can't restart openshift application nodejs + postgres. I use free plan. Error in openshift online:
Could not stop Postgres
Failed to execute: 'control restart' for /var/lib/openshift/{my_id}/postgresql
I found some advices to need to wait sometime and tech support will resolve it without my activity. But already three days service not work. And I asked on red hat bugzilla and my question is assigned to admin but there is no response.
I've solved it. I thought users have not permission to kill process from openshift shell but they can.
ps aux|grep postgres
kill - pid
then restart app from openshift web console.
I would like to view SQS messages before they get picked up by sqsd on my Elastic Beanstalk intstance. Is there a way, once ssh'ed into the instance, that sqsd can be stopped / started as a service all together?
For the purpose of debugging you may stop sqsd by running sudo service aws-sqsd stop on the instance. You can check the status by running sudo service aws-sqsd status. Note this is not recommended for a production service but for the purpose of debugging you may try this.