Closed robnagler closed 8 years ago
This is with systemctl on fedora cloud. @elventear I'm not too concerned right now but wanted to note this was happening so we don't lose it.
Sep 29 02:14:12 ip-10-14-2-5.ec2.internal systemd[1]: celery-sirepo.service: Unit entered failed state. Sep 29 02:14:12 ip-10-14-2-5.ec2.internal systemd[1]: celery-sirepo.service: Failed with result 'exit-code'. Sep 29 02:14:23 ip-10-14-2-5.ec2.internal systemd[1]: celery-sirepo.service: Service hold-off time over, scheduling restart. Sep 29 02:14:23 ip-10-14-2-5.ec2.internal systemd[1]: Started Celery Sirepo. Sep 29 02:14:23 ip-10-14-2-5.ec2.internal systemd[1]: Starting Celery Sirepo... Sep 29 02:14:23 ip-10-14-2-5.ec2.internal docker[1874]: /usr/bin/docker: Error response from daemon: Conflict. The name "/celery-sirepo" is already in use by container a3be7 Sep 29 02:14:23 ip-10-14-2-5.ec2.internal docker[1874]: See '/usr/bin/docker run --help'. Sep 29 02:14:23 ip-10-14-2-5.ec2.internal systemd[1]: celery-sirepo.service: Main process exited, code=exited, status=125/n/a Sep 29 02:14:23 ip-10-14-2-5.ec2.internal docker[1878]: celery-sirepo Sep 29 02:14:23 ip-10-14-2-5.ec2.internal systemd[1]: celery-sirepo.service: Unit entered failed state. Sep 29 02:14:23 ip-10-14-2-5.ec2.internal systemd[1]: celery-sirepo.service: Failed with result 'exit-code'. Sep 29 02:14:33 ip-10-14-2-5.ec2.internal systemd[1]: celery-sirepo.service: Service hold-off time over, scheduling restart. Sep 29 02:14:33 ip-10-14-2-5.ec2.internal systemd[1]: Started Celery Sirepo. Sep 29 02:14:33 ip-10-14-2-5.ec2.internal systemd[1]: Starting Celery Sirepo... Sep 29 02:14:33 ip-10-14-2-5.ec2.internal docker[1885]: /usr/bin/docker: Error response from daemon: Conflict. The name "/celery-sirepo" is already in use by container a3be7
This is with systemctl on fedora cloud. @elventear I'm not too concerned right now but wanted to note this was happening so we don't lose it.