supervisord

Supervisor 守护 dotnetcore 程序

[亡魂溺海] 提交于 2019-12-02 05:53:44
版权声明:本文由屈政斌原创文章,转载请注明出处: 文章原文链接: https://www.qcloud.com/community/article/240 来源:腾云阁 https://www.qcloud.com/community 接上篇 腾讯云centos 7部署 dotnetcore+Angular2 实践 环境准备 1.设置nginx 服务开机启动 systemctl enable nginx.servic 2.安装Supervisor yum install python-setuptools easy_install supervisor 3.配置Supervisor mkdir /etc/supervisor echo_supervisord_conf > /etc/supervisor/supervisord.conf #指定配置文件 supervisord -c /etc/supervisor/supervisord.conf 指定守护的程序配置 vim /etc/supervisor/supervisord.conf 在最后增加 [include] files=conf.d/*.conf 配置Supervisor开机启动 新建一个“ supervisord.service ”文件 # dservice for systemd (CentOS 7.0+) #

在CentOS部署AspNetCore网站

一个人想着一个人 提交于 2019-12-02 03:15:20
  前段时间某云服务器大促,就买了一台打算折腾一下,买了几个月,却啥也没做,就改了个初始密码。最近快到双十一了,另一家厂商相同配置的服务器价格又便宜了一大截,看来又得剁手了。从今年开始,搜索一下云服务器,发现好多大厂都开始涉足云服务器市场了,之前做这块和没做这块业务的大大小小的厂商今年都在大力推广自己的云服务器产品,市场竞争起来了,价格就友好多了呀。😁 2019年已经不适合在地上走了,咱也到云里面去看一看。开始折腾吧。 安装dotnet 运行时   首先注册微软产品仓库,这样就可以通过yum安装.NET Rumtime了。 sudo rpm -Uvh https://packages.microsoft.com/config/centos/7/packages-microsoft-prod.rpm   目前dotnetcore3.0已经发布,运行时版本最好选择和本地开发的sdk版本一致。我本地已经更新到.NET SDK3.0了,所以在服务器安装aspnetcore-runtime-3.0 sudo yum install aspnetcore-runtime-3.0 aspnetcore网站   创建aspnetcore Web程序,目标框架选择.NET Core 3.0,啥也不做,直接发布。powershell或者cmd进入到publish目录,使用dotnet命令运行一下程序

Centos7 中使用Supervisor守护进程

我们两清 提交于 2019-12-01 19:17:46
原文出处: Centos7 中使用Supervisor守护进程 配置supervisor实现进程守护 1.安装supervisor yum install Supervisor 2.启动服务 supervisord -c /etc/supervisord.conf 进入 cd /etc 目录 找到supervisord.conf 配置文件 和 supervisord.d 文件夹,使用vim编辑supervisord.conf文件,拉到最底部我们可以看到 files = supervisord.d/*.ini 这句代码说明它会加载supervisord.d文件夹中的所有.ini配置文件 3.编辑配置文件 随后我们在supervosprd.d中创建一个delploy.ini文件并编辑如下 [program:DeployLinux] #DeployLinux 为程序的名称 command=dotnet DeployLinux.dll #需要执行的命令 directory=/home/publish #命令执行的目录 environment=ASPNETCORE__ENVIRONMENT=Production #环境变量 user=root #用户 stopsignal=INT autostart=true #是否自启动 autorestart=true #是否自动重启 startsecs

Celery dies with DBPageNotFoundError

懵懂的女人 提交于 2019-12-01 17:16:32
问题 I have 3 machines with celery workers and rabbitmq as a broker, one worker is running with beat flag, all of this is managed by supervisor, and sometimes celery dies with such error. This error appears only on beat worker, but when it appears, workers on all machines dies. (celery==3.1.12, kombu==3.0.20) [2014-07-05 08:37:04,297: INFO/MainProcess] Connected to amqp://user:**@192.168.15.106:5672// [2014-07-05 08:37:04,311: ERROR/Beat] Process Beat Traceback (most recent call last): File "/var

Celery dies with DBPageNotFoundError

孤街醉人 提交于 2019-12-01 17:04:27
I have 3 machines with celery workers and rabbitmq as a broker, one worker is running with beat flag, all of this is managed by supervisor, and sometimes celery dies with such error. This error appears only on beat worker, but when it appears, workers on all machines dies. (celery==3.1.12, kombu==3.0.20) [2014-07-05 08:37:04,297: INFO/MainProcess] Connected to amqp://user:**@192.168.15.106:5672// [2014-07-05 08:37:04,311: ERROR/Beat] Process Beat Traceback (most recent call last): File "/var/projects/env/local/lib/python2.7/site-packages/billiard/process.py", line 292, in _bootstrap self.run()

Reuse containers with `docker-compose`

谁说胖子不能爱 提交于 2019-12-01 17:01:13
I've an app running on multiple Docker containers defined by docker-compose . Everything works fine from my user and the docker-compose ps output looks like: Name Command State Ports ------------------------------------------------------------ myuser_app_1 /config/bootstrap.sh Exit 137 myuser_data_1 sh Exit 0 myuser_db_1 /run.sh Exit 143 Now I'm trying to run docker-compose up with supervisord (see relevant part of supervisord.conf below) and the issue is that the containers are now named myapp_app_1 , myapp_data_1 and myapp_db_1 , that is they're created from scratch and all customizations on

Reuse containers with `docker-compose`

非 Y 不嫁゛ 提交于 2019-12-01 16:10:40
问题 I've an app running on multiple Docker containers defined by docker-compose . Everything works fine from my user and the docker-compose ps output looks like: Name Command State Ports ------------------------------------------------------------ myuser_app_1 /config/bootstrap.sh Exit 137 myuser_data_1 sh Exit 0 myuser_db_1 /run.sh Exit 143 Now I'm trying to run docker-compose up with supervisord (see relevant part of supervisord.conf below) and the issue is that the containers are now named

supervisord logs don't show my output

三世轮回 提交于 2019-12-01 13:46:21
问题 I have a [program:x] running and it prints / sys.stdout.writes a lot of things. None of which comes up in either in the AUTO childlogdir of [supervisord] or in stdout_logfile of [program:x] Am I missing something? How do I capture all that is printed or stdout-ed from [program:x] ? In my program I am explicitly doing both, print "something" sys.stdout.write("something") Relevant supervisord.conf file [supervisord] childlogdir = %(here)s/../logs/supervisord/ logfile = %(here)s/../logs

制作各种docker镜像

做~自己de王妃 提交于 2019-12-01 10:45:11
做了一个星期的镜像,收货颇多,现在整理记录下来,当做工作笔记吧。把常用的几个镜像的Dockerfile分享下。 制作基础docker镜像 制作基础镜像网上有很多实例,可以参考下开源中国的这篇文章: http://my.oschina.net/feedao/blog/223795 和51博客中的这篇文章: http://zhou123.blog.51cto.com/4355617/1439895 ;下面的基础镜像制作大部分就是参考了上面的文章。非常感谢他们,转载时请保存这两篇文章的完整信息。 第一步:设置docker镜像源 yum install -y yum-priorities && rpm -ivh http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm && rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6 第二步:安装 docker-io febootstrap,用来制作centos镜像,到时候会生成个centos的镜像。 yum -y install docker-io;如果没有安装docker,则需要先安装docker service docker start ;启动docker yum -y install febootstrap

linux 项目部署部署

隐身守侯 提交于 2019-12-01 10:00:35
原文: https://note.youdao.com/ynoteshare1/index.html?id=c91446020ebd25b05190799c50ede8e6&type=note (1)应用环境 mkdir myapp cd myapp 新建run.py 脚本 from flask import Flask app = Flask(__name__) app.route('/') def index(): return 'hello world':q if __name__ =='__main__': app.run() (2)gunicorn配置 安装gunicorn pip install gunicorn 启动gunicorn gunicorn -D -w 3 -b 0.0.0.0:8000 run:app D 表示后台运行 w 表示有3 个 工作线程(感觉有些类似 nginx 的 master-worker 模型) b 指定ip 和端口 这里采用本机访问, 主要是为了使用nginx 进行代理, 方便管理 ,可以用0.0.0.0来让其他主机访问,但是记得要看后面的防火墙端口,记得开启这里的8000 run表存放 写着全局变量 app 的那个工程文件 在我们的这个工程中, 即包含 init.py 的那个文件 (3)supervisor配置 安装: pip