[英]Using Supervisor to run ratchet websockets and queue in laravel
我做了一個工匠命令,在下面的某個端口上運行一個websockets
class webSockets extends Command
{
/**
* The name and signature of the console command.
*
* @var string
*/
protected $signature = 'run:socket {port?}';
/**
* The console command description.
*
* @var string
*/
protected $description = 'Run websockets for specified port';
/**
* Create a new command instance.
*
* @return void
*/
public function __construct(RedisInterface $redis)
{
$this->redis=$redis;
parent::__construct();
}
/**
* Execute the console command.
*
* @return mixed
*/
public function handle()
{
//
$port = $this->argument('port');
if($port=='8182') {
$server = IoServer::factory(
new SocketController($this->redis),$port
);
}
else if($port=='8181'){
$server = IoServer::factory(
new Socket1Controller($this->redis),$port
);
}
$server->run();
}
}
我可以運行這些套接字輕松運行如下的工匠命令
php artisan run:socket 8181
php artisan run :socket 8182
我需要將它部署在生產服務器上,該服務器上有數千個設備連接在該網絡套接字上。 我試過主管守護程序,但沒有運氣
我的conf文件如下所示
[program:ratchet]
command = php /var/www/v3 artisan run:socket 8181;php /var/www/v3 artisan run:socket 8182
process_name = Ratchet
numprocs = 1
autostart = true
autorestart = true
stdout_logfile = ./logs/info.log
stderr_logfile = ./logs/error.log
我意識到端口8181和8182都是免費的,沒有收到任何消息。
當我嘗試sudo service supervisorctl
我看到所有進程都有正常運行時間0:00:00和不同的pid
laravel_queue RUNNING pid 62246, uptime 0:00:00
ratchet:Ratchet RUNNING pid 62245, uptime 0:00:00
supervisor> status
laravel_queue RUNNING pid 62305, uptime 0:00:00
ratchet:Ratchet RUNNING pid 62304, uptime 0:00:00
supervisor> status
laravel_queue RUNNING pid 62419, uptime 0:00:00
ratchet:Ratchet RUNNING pid 62418, uptime 0:00:00
supervisor> status
laravel_queue RUNNING pid 62553, uptime 0:00:00
ratchet:Ratchet RUNNING pid 62552, uptime 0:00:00
supervisor> status
laravel_queue RUNNING pid 62689, uptime 0:00:00
ratchet:Ratchet RUNNING pid 62688, uptime 0:00:00
supervisor> status
laravel_queue RUNNING pid 62819, uptime 0:00:00
ratchet:Ratchet RUNNING pid 62818, uptime 0:00:00
supervisor> status
我錯過了什么嗎?
我設法通過在主管上進行單獨的處理來解決它
在/etc/supervisord/conf.d/中創建laravel_queue.conf:
[program:laravel_queue]
command= php artisan queue:listen redis --timeout=7200
directory=/var/www/gpsv3
stderr_logfile=/var/www/gpsv3/storage/logs/laraqueue.err.log
stdout_logfile=/var/www/gpsv3/storage/logs/laraqueue.out.log
redirect_stderr=true
賦予它執行權限:chmod + x laravel_queue.conf
現在更新Supervisor:sudo supervisorctl reread。 並開始使用以下更改:sudo supervisorctl update。
在/etc/supervisord/conf.d/中創建socket.conf:
[program:socket]
command= php artisan run:socket 8182
directory=/var/www/gpsv3
stderr_logfile=/var/www/gpsv3/storage/logs/socket.err.log
stdout_logfile=/var/www/gpsv3/storage/logs/socket.out.log
redirect_stderr=true
賦予它執行權限:chmod + x socket.conf
現在更新Supervisor:sudo supervisorctl reread。 並開始使用以下更改:sudo supervisorctl update。
聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.