반응형
아래와 같이 에러메시지가 뜨면서 실행이 되지 않을때,
Dec 3 09:44:22 localhost crond: crond: can't lock /var/run/crond.pid, otherpid may be 26272: 자원이 일시적으로 사용 불가능함
Dec 3 09:44:22 localhost systemd: crond.service: main process exited, code=exited, status=1/FAILURE
Dec 3 09:44:22 localhost systemd: Unit crond.service entered failed state.
Dec 3 09:44:22 localhost systemd: crond.service failed.
[root@localhost ~]# systemctl status crond
● crond.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since 목 2020-12-03 09:44:22 KST; 6s ago
Process: 29270 ExecStart=/usr/sbin/crond -n $CRONDARGS (code=exited, status=1/FAILURE)
Main PID: 29270 (code=exited, status=1/FAILURE)
12월 03 09:44:22 localhost systemd[1]: crond.service: main process exited, code=exited, status=1/FAILURE
12월 03 09:44:22 localhost systemd[1]: Unit crond.service entered failed state.
12월 03 09:44:22 localhost systemd[1]: crond.service failed.
[root@localhost ~]# ps -ef | grep cron
root 26272 1 0 09:34 ? 00:00:00 crond
root 29301 26176 0 09:44 pts/1 00:00:00 grep --color=auto cron
[root@localhost ~]# ll /var/run/crond.pid
-rw-r--r-- 1 root root 6 12월 3 09:34 /var/run/crond.pid
[해결책]
cron.pid 파일을 삭제 후, cron 데몬으로 프로세스가 올라온 것을 다 죽이고 다시 재시작
[root@localhost ~]# rm -rf /var/run/crond.pid
[root@localhost ~]# ps -ef | grep cron*
root 26272 1 0 09:34 ? 00:00:00 crond
root 29907 26176 0 09:46 pts/1 00:00:00 grep --color=auto cron*
[root@localhost ~]# kill -9 26272
[root@localhost ~]# systemctl restart crond
반응형
'LINUX > ERROR' 카테고리의 다른 글
journal ERROR (0) | 2021.06.07 |
---|---|
[Error] fatal: git fetch-pack: expected shallow list (0) | 2021.03.25 |
/lib64/libc.so.6 version glibc_2.14' not found (0) | 2020.10.21 |
db 백업 스크립트가 crontab 형식으로 돌때, 0byte 생성시, 문제 (0) | 2020.10.16 |
/dev/sda1 has unsupported feature(s): 64bit (0) | 2020.09.02 |