CentOS 재부팅 현상 및 지연 문의
안녕하세요. 리눅스 초보 문의 드립니다.
현재 CentOS5.8을 사용하여 APM 환경을 운영중입니다.
최근들어 이유없이 재부팅이 3번정도 일어 났는데요.
재부팅도 문제지만, 마지막으로 재부팅된 건으로 시스템이 재부팅되면서 2일 이상 지난후 부팅이 된건이 발생하여 원인을 몰라서 고민하다가 글을 올리게 되었습니다.
아래의 내용 확인해 주세요.
[문의1] 비정상 재부팅 현상
- last -x 로그
root pts/1 100.100.100.100 Thu Oct 1 15:21 - 15:23 (00:02)
runlevel (to lvl 6) 2.6.18-308.el5PA Thu Nov 19 14:40 - 14:40 (00:00)
shutdown system down 2.6.18-308.el5PA Thu Nov 19 14:40 - 21:25 (1+06:45)
reboot system boot 2.6.18-308.el5PA Thu Nov 19 14:43 (1+06:42)
runlevel (to lvl 3) 2.6.18-308.el5PA Thu Nov 19 14:43 - 21:25 (1+06:42)
=> 정상 재부팅 완료, 로그 내용만 보면 시스템템의 재부팅 버튼 혹은 tty 및 pts가 열려있지 않은 상태에서 콘솔 키보드 상태에서 ctrl+alt+del로 재부팅 된것으로 보고 있습니다.
- /var/log/messages 로그
Nov 19 04:02:02 LINUX logrotate: ALERT exited abnormally with [1]
Nov 19 14:40:10 LINUX shutdown[27575]: shutting down for system reboot
Nov 19 14:40:10 LINUX init: Switching to runlevel: 6
Nov 19 14:40:12 LINUX shutdown[27597]: shutting down for system reboot
Nov 19 14:40:13 LINUX shutdown[27615]: shutting down for system reboot
Nov 19 14:40:14 LINUX shutdown[27617]: shutting down for system reboot
Nov 19 14:40:14 LINUX xinetd[2067]: Exiting...
Nov 19 14:40:14 LINUX shutdown[27641]: shutting down for system reboot
Nov 19 14:40:15 LINUX shutdown[27644]: shutting down for system reboot
Nov 19 14:40:15 LINUX shutdown[27646]: shutting down for system reboot
Nov 19 14:40:15 LINUX shutdown[27648]: shutting down for system reboot
Nov 19 14:40:15 LINUX shutdown[27650]: shutting down for system reboot
Nov 19 14:40:15 LINUX kernel: Kernel logging (proc) stopped.
Nov 19 14:40:15 LINUX kernel: Kernel log daemon terminating.
Nov 19 14:40:16 LINUX shutdown[27673]: shutting down for system reboot
Nov 19 14:40:16 LINUX shutdown[27675]: shutting down for system reboot
Nov 19 14:40:17 LINUX exiting on signal 15
Nov 19 14:43:34 LINUX syslogd 1.4.1: restart.
Nov 19 14:43:34 LINUX kernel: klogd 1.4.1, log source = /proc/kmsg started.
Nov 19 14:43:34 LINUX kernel: Linux version 2.6.18-308.el5PAE (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-52)) #1 SMP Tue Feb 21 20:46:05 EST 2012
Nov 19 14:43:34 LINUX kernel: BIOS-provided physical RAM map:
Nov 19 14:43:34 LINUX kernel: BIOS-e820: 0000000000010000 - 000000000009c000 (usable)
=> shutdown[27575],shutdown[27597],shutdown[27615]등.. 여러개의 아이디가 발생하는것이 이상한데. 이런경우는 어떨때 나타는 현상인가요?
[문의2] 비정상 재부팅이 부팅시간 지연(2일 이상 걸림)
- last -x 로그
runlevel (to lvl 6) 2.6.18-308.el5PA Fri Nov 20 21:25 - 21:26 (00:00)
shutdown system down 2.6.18-308.el5PA Fri Nov 20 21:26 - 10:56 (6+13:30)
reboot system boot 2.6.18-308.el5PA Mon Nov 23 13:45 (3+21:11)
runlevel (to lvl 3) 2.6.18-308.el5PA Mon Nov 23 13:45 - 10:56 (3+21:11)
=> 문의1의 마지막 정상부팅후 11월 20일 21:25의 또다시 재부팅이 이루어졌고, 부팅하는데 2일 이상의 소요시간이 걸렸습니다.
- /var/log/messages 로그
Nov 20 04:02:04 LINUX logrotate: ALERT exited abnormally with [1]
Nov 20 21:25:52 LINUX shutdown[31198]: shutting down for system reboot
Nov 20 21:25:53 LINUX init: Switching to runlevel: 6
Nov 20 21:25:54 LINUX xinetd[2074]: Exiting...
Nov 20 21:25:54 LINUX kernel: Kernel logging (proc) stopped.
Nov 20 21:25:54 LINUX kernel: Kernel log daemon terminating.
Nov 20 21:25:56 LINUX exiting on signal 15
Nov 23 13:45:20 LINUX syslogd 1.4.1: restart.
Nov 23 13:45:20 LINUX kernel: klogd 1.4.1, log source = /proc/kmsg started.
Nov 23 13:45:20 LINUX kernel: Linux version 2.6.18-308.el5PAE (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-52)) #1 SMP Tue Feb 21 20:46:05 EST 2012
요약하면..
- 시스템이 이유없이 재부팅이 되었는데, 이런 경우 어떤 부분을 점검해야 할까요?
- 문의2에서 재부팅이 진행되었고 다시 부팅하는데, 2일 이상이 소요되었습니다. 이런 경우는 어떤부분을 점검해야 할까요?
전문업체에 문의해보시기 바랍니다.
답변이 없네요.
아니면.
- 하나씩 찾아서 확인하기
- 잘 되는 책이나 설치방법을 따라하기
- 다른 버전 사용하기
- 서비스팩이나 패치로 업그레이드 하기
- 리눅스 포럼에 문의해보기
------------------------------------------------------------------------------
리눅스 비정상 재부팅
http://www.google.co.kr/search?hl=ko&source=hp&biw=&bih=&q=%EB%A6%AC%EB%88%85%EC%8A%A4+%EB%B9%84%EC%A0%95%EC%83%81+%EC%9E%AC%EB%B6%80%ED%8C%85&gbv=2&oq=%EB%A6%AC%EB%88%85%EC%8A%A4+%EB%B9%84%EC%A0%95%EC%83%81+%EC%9E%AC%EB%B6%80%ED%8C%85&gs_l=heirloom-hp.12...57.57.0.543.1.1.0.0.0.0.112.112.0j1.1.0....0...1ac..34.heirloom-hp..1.0.0.KyhXJtetu24
------------------------------------------------------------------------------
LINUX kernel: Linux version 2.6.18-308.el5PAE
Subject: [CentOS] PAE Kernel
http://osdir.com/ml/centos/2010-08/msg01119.html
Linux Kernel 2.6.18에서 2.6.27로 컴파일 기록.
http://blog.studioego.info/2771
http://kkarijoo.tistory.com/60
http://blog.naver.com/blue90210?Redirect=Log&logNo=100101241564
http://blog.naver.com/blue90210?Redirect=Log&logNo=100101241564
------------------------------------------------------------------------------
LINUX logrotate: ALERT exited abnormally with [1]
I am getting 'logrotate: ALERT exited abnormally with [1]' messages in logs when SELinux is in the Enforcing mode
https://access.redhat.com/solutions/39006
How to debug logrotate warnings or errors when logrotate is not running correctly
https://access.redhat.com/solutions/32831
[Tip] logrotate 에러 발생시 조치 방법
http://www.gits.co.kr/bbs/board.php?bo_table=pds&wr_id=102
logrotate: ALERT exited abnormally with [1]
http://www.linuxquestions.org/questions/red-hat-31/logrotate-alert-exited-abnormally-with-[1]-747571/
------------------------------------------------------------------------------
LINUX exiting on signal 15
http://www.google.co.kr/search?q=LINUX+exiting+on+signal+15&hl=ko&biw=&bih=&gbv=2&oq=LINUX+exiting+on+signal+15&gs_l=heirloom-serp.12..0i19j0i8i30i19j0i5i30i19j0i8i30i19.40361.40361.0.40867.1.1.0.0.0.0.112.112.0j1.1.0....0...1ac..34.heirloom-serp..0.1.112.KFLw-fWttNE
------------------------------------------------------------------------------
Why does Red Hat Enterprise Linux Server reboot with "signal 15" messages in /var/log/messages?
https://access.redhat.com/solutions/31411
Server rebooted with "signal 15."
Server automatically rebooted.
Server unexpectedly rebooted.
What does exiting on signal 15 mean in /var/log/messages?
------------------------------------------------------------------------------
http://stackoverflow.com/questions/16723626/what-is-signal-15-received
15) SIGTERM
------------------------------------------------------------------------------
How can I tell who/what shutdown my CentOS VPS?
http://serverfault.com/questions/334221/how-can-i-tell-who-what-shutdown-my-centos-vps
last reboot | head -1
last -x|grep shutdown
------------------------------------------------------------------------------
16.4. xinetd Configuration Files
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/3/html/Reference_Guide/s1-tcpwrappers-xinetd-config.html
xinetd won't start
http://serverfault.com/questions/78002/xinetd-wont-start
------------------------------------------------------------------------------
LINUX init: Switching to runlevel: 6
http://www.google.co.kr/search?hl=ko&source=hp&biw=&bih=&q=LINUX+init%3A+Switching+to+runlevel%3A+6&gbv=2&oq=LINUX+init%3A+Switching+to+runlevel%3A+6&gs_l=heirloom-hp.12..0i8i30.333.333.0.1748.1.1.0.0.0.0.137.137.0j1.1.0....0...1ac..34.heirloom-hp..0.1.127.ml9iv_qbW3E
------------------------------------------------------------------------------
Reboot/Shutdown messages
http://www.unix.com/linux/153625-reboot-shutdown-messages.html
umount: /dev: Device or resource busy
shutdown: unmounting all file systems
Post your /etc/inittab, it might explain more.
------------------------------------------------------------------------------
LINUX kernel: klogd 1.4.1, log source = /proc/kmsg started.
------------------------------------------------------------------------------
Re: how to check if shutdown/halt has been executed
https://www.redhat.com/archives/redhat-list/2010-November/msg00044.html
this indicates a spontaneous
shutdown caused by any number of things--power outage, drastic software or
hardware problems, etc.
------------------------------------------------------------------------------
Unexpected restart - RHEL 5.3 ?
http://www.linuxforums.org/forum/red-hat-fedora-linux/153247-unexpected-restart-rhel-5-3-a.html
for 64-bit RHEL 5
divider=10 notsc iommu=soft elevator=noop
and for a 32-bit RHEL 5:
divider=10 clocksource=acpi_pm iommu=soft elevator=noop
elevetor=deadline
----------------------------------------------------------------------------
젊음'은 모든것을 가능하게 만든다.
매일 1억명이 사용하는 프로그램을 함께 만들어보고 싶습니다.
정규 근로 시간을 지키는. 야근 없는 회사와 거래합니다.
각 분야별. 좋은 책'이나 사이트' 블로그' 링크 소개 받습니다. shintx@naver.com
댓글 달기