linux - aws server dies, status check fails -
this second time happens me.
my aws server, dies, no notifications, can't ssh it, nothing.
only after restart it, can ssh , goes normal.
i check there faq page: http://docs.aws.amazon.com/awsec2/latest/userguide/troubleshootinginstances.html
and nothing there, @ logs attached below, , still nothing... ideas?
begin: loading essential drivers ... done. begin: running /scripts/init-premount ... done.
begin: mounting root file system ... begin: running /scripts/local-top ... done.
begin: running /scripts/local-premount ... done.
[ 2.576125] ext4-fs (xvda1): info: recovery required on readonly filesystem [ 2.579775] ext4-fs (xvda1): write access enabled during recovery [ 2.644278] ext4-fs (xvda1): orphan cleanup on readonly fs [ 2.647386] ext4-fs (xvda1): 2 orphan inodes deleted [ 2.650239] ext4-fs (xvda1): recovery complete [ 2.657120] ext4-fs (xvda1): mounted filesystem ordered data mode. opts: (null) begin: running /scripts/local-bottom ... done.
done.
begin: running /scripts/init-bottom ... done.
[ 2.805807] random: init urandom read 59 bits of entropy available * starting mount filesystems on boot[74g[ ok ]
starting populate /dev filesystem[74g[ ok ]
starting populate , link /run filesystem[74g[ ok ]
stopping populate /dev filesystem[74g[ ok ]
stopping populate , link /run filesystem[74g[ ok ] [ 2.958244] ext4-fs (xvda1): re-mounted. opts: discard
starting initialize or finalize resolvconf[74g[ ok ]
stopping track if upstart running in container[74g[ ok ]
starting signal sysvinit rootfs mounted[74g[ ok ]
starting clean /tmp directory[74g[ ok ]
stopping clean /tmp directory[74g[ ok ]
cloud-init v. 0.7.5 running 'init-local' @ tue, 08 nov 2016 11:59:09 +0000. 3.47 seconds.
cloud-init-nonet[3.71]: waiting 10 seconds network device
starting set console keymap[74g[ ok ]
starting signal sysvinit virtual filesystems mounted[74g[ ok ]
starting signal sysvinit virtual filesystems mounted[74g[ ok ]
starting bridge udev events upstart[74g[ ok ]
starting signal sysvinit remote filesystems mounted[74g[ ok ]
starting device node , kernel event manager[74g[ ok ]
stopping set console keymap[74g[ ok ]
starting cold plug devices[74g[ ok ]
starting log initial device creation[74g[ ok ]
starting uncomplicated firewall[74g[ ok ]
starting configure network device security[74g[ ok ]
starting configure network device security[74g[ ok ]
starting mount network filesystems[74g[ ok ]
stopping mount network filesystems[74g[ ok ]
starting configure network device[74g[ ok ]
starting bridge socket events upstart[74g[ ok ]
cloud-init-nonet[4.92]: static networking up
starting mount network filesystems[74g[ ok ]
starting configure network device[74g[ ok ]
stopping mount network filesystems[74g[ ok ]
cloud-init v. 0.7.5 running 'init' @ tue, 08 nov 2016 11:59:11 +0000. 5.56 seconds.
ci-info: +++++++++++++++++++++++++++net device info+++++++++++++++++++++++++++
ci-info: +--------+------+---------------+---------------+-------------------+
ci-info: | device | | address | mask | hw-address |
ci-info: +--------+------+---------------+---------------+-------------------+
ci-info: | lo | true | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | true | 172.31.63.219 | 255.255.240.0 | 12:7d:8c:19:f4:ef |
ci-info: +--------+------+---------------+---------------+-------------------+
ci-info: +++++++++++++++++++++++++++++++route info++++++++++++++++++++++++++++++++
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: | route | destination | gateway | genmask | interface | flags |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 172.31.48.1 | 0.0.0.0 | eth0 | ug |
ci-info: | 1 | 172.31.48.0 | 0.0.0.0 | 255.255.240.0 | eth0 | u |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
starting signal sysvinit local filesystems mounted[74g[ ok ]
stopping mount filesystems on boot[74g[ ok ]
starting flush boot log disk[74g[ ok ]
starting flush job output logs[74g[ ok ]
stopping failsafe boot delay[74g[ ok ]
starting system v initialisation compatibility[74g[ ok ]
stopping flush job output logs[74g[ ok ]
starting d-bus system message bus[74g[ ok ]
starting systemd login management service[74g[ ok ]
starting system logging daemon[74g[ ok ]
stopping flush boot log disk[74g[ ok ]
starting handle applying cloud-config[74g[ ok ]
starting bridge file events upstart[74g[ ok ]
starting crypto disks... [80g [74g[ ok ]
skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
starting apparmor profiles [80g [74g[ ok ]
stopping system v initialisation compatibility[74g[ ok ]
starting system v runlevel compatibility[74g[ ok ]
starting acpi daemon[74g[ ok ]
starting save kernel messages[74g[ ok ]
starting configure network device security[74g[ ok ]
starting openssh server[74g[ ok ]
starting regular background program processing daemon[74g[ ok ]
starting deferred execution scheduler[74g[ ok ]
stopping save kernel messages[74g[ ok ]
stopping cpu interrupts balancing daemon[74g[ ok ]
starting configure virtual network devices[74g[ ok ]
starting automatic crash report generation[74g[ ok ]
stopping cold plug devices[74g[ ok ]
stopping log initial device creation[74g[ ok ]
starting enable remaining boot-time encrypted block devices[74g[ ok ]
open-vm-tools: not starting not vmware vm
landscape-client not configured, please run landscape-config.
- restoring resolver state... [80g [74g[ ok ]
cloud-init v. 0.7.5 running 'modules:config' @ tue, 08 nov 2016 11:59:12 +0000. 7.17 seconds.
- stopping system v runlevel compatibility[74g[ ok ]
cloud-init v. 0.7.5 running 'modules:final' @ tue, 08 nov 2016 11:59:13 +0000. 7.74 seconds. cloud-init v. 0.7.5 finished @ tue, 08 nov 2016 11:59:13 +0000. datasource datasourceec2. 7.85 seconds
ubuntu 14.04.4 lts ip-172-31-63-219 ttys0
ip-172-31-63-219 login:
might kernel panic or kind of flaw in os. os/version using? can check /var/log/kern.log or /var/log/syslog entries before crash?
Comments
Post a Comment