You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-- The unit podman-coaster-celery-agent.service has successfully entered the 'dead' state.
2月 02 15:47:00 node-1.domain.tld systemd[1]: Started Celery Service via podman.
-- Subject: podman-coaster-celery-agent.service 单元已结束启动
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- podman-coaster-celery-agent.service 单元已结束启动。
-- 启动结果为“done”。
cat /usr/lib/systemd/system/podman-coaster-celery-agent.service
[Unit]
Description=Celery Service via podman
After=network.target
ExecStartPre=/bin/rm -f /var/lib/celery/${CELERYD_NODES}.pid
ExecStartPre=mkdir -p /var/lib/celery /var/log/celery
ExecStart=podman run $POD_OPTS $POD_IMG sh -c '${CELERY_BIN} multi start ${CELERYD_NODES}
-A ${CELERY_APP} --pidfile=${CELERYD_PID_FILE} -n celery
--logfile=${CELERYD_LOG_FILE} --loglevel=${CELERYD_LOG_LEVEL} ${CELERYD_OPTS}'
ExecStop=podman run $POD_OPTS $POD_IMG /bin/sh -c '${CELERY_BIN} multi stopwait ${CELERYD_NODES}
--pidfile=${CELERYD_PID_FILE}'
ExecReload=podman run $POD_OPTS $POD_IMG /bin/sh -c '${CELERY_BIN} multi restart ${CELERYD_NODES}
-A ${CELERY_APP} --pidfile=${CELERYD_PID_FILE}
--logfile=${CELERYD_LOG_FILE} --loglevel=${CELERYD_LOG_LEVEL} ${CELERYD_OPTS}'
questions: Why is there no error when entering the container to start ExecStart, but a rough error is reported about 'conmon c82ee1934e559bd5868f : stdio_input read failed Resource ' when starting the podman-coaster-celery-agent.service?
The text was updated successfully, but these errors were encountered:
[root@node-1 ~]# journalctl -xe podman-coaster-celery-agent.service
Failed to add match 'podman-coaster-celery-agent.service': Invalid argument
[root@node-1 ~]# journalctl -xe -u podman-coaster-celery-agent.service
-- podman-coaster-celery-agent.service 单元已结束启动。
-- 启动结果为“done”。
2月 02 15:46:57 node-1.domain.tld systemd[1]: Starting Celery Service via podman...
-- Subject: podman-coaster-celery-agent.service 单元已开始启动
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- podman-coaster-celery-agent.service 单元已开始启动。
2月 02 15:46:59 node-1.domain.tld podman[51690]: celery multi v3.1.19 (Cipater)
2月 02 15:46:59 node-1.domain.tld podman[51690]: > Starting nodes...
2月 02 15:46:59 node-1.domain.tld podman[51690]: > celery_1@celery: OK
2月 02 15:46:59 node-1.domain.tld conmon[51722]: conmon c82ee1934e559bd5868f : stdio_input read failed Resource temporarily unavailab>
2月 02 15:46:59 node-1.domain.tld conmon[51722]: conmon c82ee1934e559bd5868f : stdio_input read failed Resource temporarily unavailab>
2月 02 15:47:00 node-1.domain.tld podman[51818]: celery multi v3.1.19 (Cipater)
2月 02 15:47:00 node-1.domain.tld podman[51818]: > [email protected]: DOWN
2月 02 15:47:00 node-1.domain.tld systemd[1]: podman-coaster-celery-agent.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- The unit podman-coaster-celery-agent.service has successfully entered the 'dead' state.
2月 02 15:47:00 node-1.domain.tld systemd[1]: Started Celery Service via podman.
-- Subject: podman-coaster-celery-agent.service 单元已结束启动
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- podman-coaster-celery-agent.service 单元已结束启动。
-- 启动结果为“done”。
cat /usr/lib/systemd/system/podman-coaster-celery-agent.service
[Unit]
Description=Celery Service via podman
After=network.target
[Service]
Type=forking
User=root
Group=root
EnvironmentFile=-/etc/sysconfig/celeryd.sysconfig
Environment=POD_IMG=hub.easystack.cn/escl-switch/es8
Environment=POD_OPTS="--privileged
--network=host
--pid=host
--volume /proc:/proc
--volume /var/lib/celery:/var/lib/celery
--volume /var/log/celery:/var/log/celery"
Note the -f: don't fail if there is no PID file
ExecStartPre=/bin/rm -f /var/lib/celery/${CELERYD_NODES}.pid$POD_IMG sh -c '$ {CELERY_BIN} multi start ${CELERYD_NODES} $POD_IMG /bin/sh -c '$ {CELERY_BIN} multi stopwait ${CELERYD_NODES} $POD_IMG /bin/sh -c '$ {CELERY_BIN} multi restart ${CELERYD_NODES}
ExecStartPre=mkdir -p /var/lib/celery /var/log/celery
ExecStart=podman run $POD_OPTS
-A ${CELERY_APP} --pidfile=${CELERYD_PID_FILE} -n celery
--logfile=${CELERYD_LOG_FILE} --loglevel=${CELERYD_LOG_LEVEL} ${CELERYD_OPTS}'
ExecStop=podman run $POD_OPTS
--pidfile=${CELERYD_PID_FILE}'
ExecReload=podman run $POD_OPTS
-A ${CELERY_APP} --pidfile=${CELERYD_PID_FILE}
--logfile=${CELERYD_LOG_FILE} --loglevel=${CELERYD_LOG_LEVEL} ${CELERYD_OPTS}'
questions: Why is there no error when entering the container to start ExecStart, but a rough error is reported about 'conmon c82ee1934e559bd5868f : stdio_input read failed Resource ' when starting the podman-coaster-celery-agent.service?
The text was updated successfully, but these errors were encountered: