AWS Instance no longer contactable

0

Dear Sir/Madam,

My AWS instance is no longer contactable. I have recreated the HTTP/HTTPS and SSH firewall rules and ensured my public IP is listed.

I have checked the public elastic IP address is correct.

The instance appears to have booted based on screenshot (serial console login is not possible on my instance type)

The problem occurred when (as far as I know) no changes were being made to the system.

The startup log is below.

Many thanks for your help.

Welcome to CentOS Linux 7 (Core)!

[ 6.646736] systemd-sysv-generator[373]: stat() failed on /etc/rc.d/init.d/jexec: No such file or directory [ OK ] Stopped Switch Root. [ OK ] Stopped Journal Service. Starting Journal Service... [ OK ] Stopped target Switch Root. Mounting POSIX Message Queue File System... [ OK ] Created slice system-serial\x2dgetty.slice. [ OK ] Started Dispatch Password Requests to Console Directory Watch. Starting Read and set NIS domainname from /etc/sysconfig/network... [ OK ] Created slice system-selinux\x2dpol...grate\x2dlocal\x2dchanges.slice. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Reached target rpc_pipefs.target. [ OK ] Set up automount Arbitrary Executab...ats File System Automount Point. [ OK ] Created slice User and Session Slice. [ OK ] Reached target Slices. [ OK ] Started Forward Password Requests to Wall Directory Watch. [ OK ] Reached target Paths. [ OK ] Stopped target Initrd File Systems. [ OK ] Listening on Delayed Shutdown Socket. [ OK ] Created slice system-getty.slice. Starting Create list of required st... nodes for the current kernel... Mounting Debug File System... [ OK ] Reached target Local Encrypted Volumes. Mounting Huge Pages File System... [ OK ] Stopped File System Check on Root Device. Starting Remount Root and Kernel File Systems... Starting Apply Kernel Variables... [ OK ] Reached target RPC Port Mapper. Starting Setup Virtual Console... [ OK ] Stopped target Initrd Root File System. [ OK ] Listening on udev Control Socket. [ OK ] Listening on udev Kernel Socket. [ OK ] Mounted Debug File System. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Mounted Huge Pages File System. [ OK ] Started Journal Service. [ OK ] Started Read and set NIS domainname from /etc/sysconfig/network. [ OK ] Started Create list of required sta...ce nodes for the current kernel. [ OK ] Started Remount Root and Kernel File Systems. [ OK ] Started Apply Kernel Variables. [ OK ] Started Setup Virtual Console. Starting udev Coldplug all Devices... Starting Configure read-only root support... Activating swap /swap... Starting Create Static Device Nodes in /dev... Starting Flush Journal to Persistent Storage... [ 7.774831] systemd-journald[398]: Received request to flush runtime journal from PID 1 [ OK ] Started Create Static Device Nodes in /dev. [ OK ] Started udev Coldplug all Devices. [ OK ] Started Flush Journal to Persistent Storage. [ OK ] Reached target Local File Systems (Pre). Starting udev Kernel Device Manager... [ OK ] Started Configure read-only root support. Starting Load/Save Random Seed... [ OK ] Reached target Local File Systems. Starting Preprocess NFS configuration... Starting Import network configuration from initramfs... [ OK ] Started Load/Save Random Seed. [ OK ] Started Preprocess NFS configuration. [ OK ] Started udev Kernel Device Manager. [ 8.092198] input: PC Speaker as /devices/platform/pcspkr/input/input4 [ 8.113229] piix4_smbus 0000:00:01.3: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr [ OK ] Started Import network configuration from initramfs. Starting Create Volatile Files and Directories... [ 8.317801] [TTM] Zone kernel: Available graphics memory: 1939310 kiB [ 8.332058] [TTM] Initializing pool allocator [ OK ] Found device /dev/ttyS0. [ OK [ 8.373158] Adding 4194300k swap on /swap. Priority:-2 extents:4 across:335358284k SSFS ] Started Create Volatile Files and Directories.[ 8.399536] [TTM] Initializing DMA pool allocator

[ OK ] Activated swap /swap.[ 8.427533] cryptd: max_cpu_qlen set to 1000

[ 8.436055] [drm] fb mappable at 0xF0000000 [ 8.436056] [drm] vram aper at 0xF0000000 [ 8.436056] [drm] size 33554432 [ 8.436057] [drm] fb depth is 16 [ 8.436057] [drm] pitch is 2048 [ 8.496630] fbcon: cirrusdrmfb (fb0) is primary device [ 8.515080] ppdev: user-space parallel port driver [ 8.530430] AVX2 version of gcm_enc/dec engaged. [ 8.530431] AES CTR mode by8 optimization enabled [ 8.533264] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni) [ 8.533291] alg: No test for __generic-gcm-aes-aesni (__driver-generic-gcm-aes-aesni) [ 8.703061] Console: switching to colour frame buffer device 128x48 [ 8.727500] cirrus 0000:00:02.0: fb0: cirrusdrmfb frame buffer device [ OK ] Reached target Swap. Starting Security Auditing Servi[ 8.793774] [drm] Initialized cirrus 1.0.0 20110418 for 0000:00:02.0 on minor 0 ce... [ 8.808114] EDAC sbridge: Ver: 1.1.2 [ 8.867523] type=1305 audit(1682408275.896:4): audit_pid=526 old=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:auditd_t:s0 res=1 [ OK ] Started Security Auditing Service. Starting Update UTMP about System Boot/Shutdown... [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Reached target System Initialization. [ OK ] Listening on D-Bus System Message Bus Socket. Starting Initial cloud-init job (pre-networking)... [ OK ] Started Daily Cleanup of Temporary Directories. [ OK ] Reached target Timers. [ OK ] Listening on RPCbind Server Activation Socket. [ OK ] Reached target Sockets. [ OK ] Reached target Basic System. Starting Authorization Manager... Starting NTP client/server... [ OK ] Started irqbalance daemon. Starting Login Service... [ OK ] Started D-Bus System Message Bus. Starting Dump dmesg to /var/log/dmesg... Starting Process Monitoring and Control Daemon... Starting GSSAPI Proxy Daemon... Starting RPC bind service... [ OK ] Started Login Service. [ OK ] Started RPC bind service. [ OK ] Started NTP client/server. [ OK ] Started Authorization Manager. [ OK ] Started Dump dmesg to /var/log/dmesg. [ OK ] Started GSSAPI Proxy Daemon. [ OK ] Reached target NFS client services. [ OK ] Reached target Remote File Systems (Pre). [ OK ] Reached target Remote File Systems. [ OK ] Started Process Monitoring and Control Daemon. [ 10.304853] cloud-init[595]: Cloud-init v. 19.4 running 'init-local' at Tue, 25 Apr 2023 07:37:57 +0000. Up 10.27 seconds. [ OK ] Started Initial cloud-init job (pre-networking). [ OK ] Reached target Network (Pre). Starting LSB: Bring up/down networking... [FAILED] Failed to start LSB: Bring up/down networking. See 'systemctl status network.service' for details. [ OK ] Reached target Network. Starting MySQL Server... Starting Dynamic System Tuning Daemon... Starting Sendmail Mail Transport Agent... Starting The Apache HTTP Server... Starting Initial cloud-init job (metadata service crawler)... [ OK ] Started Sendmail Mail Transport Agent. Starting Sendmail Mail Transport Client... [ OK ] Started Sendmail Mail Transport Client. [ 12.895411] cloud-init[871]: Cloud-init v. 19.4 running 'init' at Tue, 25 Apr 2023 07:37:59 +0000. Up 12.78 seconds. [ 12.989232] cloud-init[871]: ci-info: ++++++++++++++++++++++++++++++++++++Net device info++++++++++++++++++++++++++++++++++++ [ 13.034113] cloud-init[871]: ci-info: +--------+------+-----------------------------+-----------+-------+-------------------+ [ 13.069618] cloud-init[871]: ci-info: | Device | Up | Address | Mask | Scope | Hw-Address | [ 13.095540] cloud-init[871]: ci-info: +--------+------+-----------------------------+-----------+-------+-------------------+ [ 13.157977] cloud-init[871]: ci-info: | eth0 | True | fe80::4f6:39ff:fe19:ee8a/64 | . | link | 06:f6:39:19:ee:8a | [ 13.185821] cloud-init[871]: ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | host | . |[ OK ] Started Dynamic System Tuning Daemon.

[ 13.227876] cloud-init[871]: ci-info: | lo | True | ::1/128 | . | host | . | [ 13.244949] cloud-init[871]: ci-info: +--------+------+-----------------------------+-----------+-------+-------------------+ [ 13.279694] cloud-init[871]: ci-info: +++++++++++++++++++Route IPv6 info+++++++++++++++++++ [ 13.299077] cloud-init[871]: ci-info: +-------+-------------+---------+-----------+-------+ [ 13.321298] cloud-init[871]: ci-info: | Route | Destination | Gateway | Interface | Flags | [ 13.339736] cloud-init[871]: ci-info: +-------+-------------+---------+-----------+-------+ [ 13.363740] cloud-init[871]: ci-info: | 9 | fe80::/64 | :: | eth0 | U |[ OK ] Started The Apache HTTP Server.

[ 13.387090] cloud-init[871]: ci-info: | 12 | ff00::/8 | :: | eth0 | U | [ 13.403810] cloud-init[871]: ci-info: +-------+-------------+---------+-----------+-------+ [ OK ] Started Initial cloud-init job (metadata service crawler). Starting Permit User Sessions... [ OK ] Reached target Network is Online. Starting Notify NFS peers of a restart... Starting Crash recovery kernel arming... Starting System Logging Service... Starting OpenSSH server daemon... [ OK ] Reached target Cloud-config availability. Starting Apply the settings specified in cloud-config... [ OK ] Started Permit User Sessions. [ OK ] Started Notify NFS peers of a restart. [ OK ] Started Command Scheduler. [ OK ] Started Getty on tty1. [ OK ] Started Serial Getty on ttyS0. [ OK ] Reached target Login Prompts. [ OK ] Started System Logging Service. [ OK ] Started OpenSSH server daemon. [ 14.429972] cloud-init[1001]: Cloud-init v. 19.4 running 'modules:config' at Tue, 25 Apr 2023 07:38:01 +0000. Up 14.29 seconds. [ OK ] Started Apply the settings specified in cloud-config. Starting Execute cloud user/final scripts... [ 14.938029] cloud-init[1083]: Cloud-init v. 19.4 running 'modules:final' at Tue, 25 Apr 2023 07:38:01 +0000. Up 14.83 seconds. [ 15.050137] cloud-init[1083]: Cloud-init v. 19.4 finished at Tue, 25 Apr 2023 07:38:02 +0000. Datasource DataSourceEc2Local. Up 15.04 seconds [ OK ] Started Execute cloud user/final scripts. [ OK ] Started Crash recovery kernel arming.

CentOS Linux 7 (Core) Kernel 3.10.0-1160.76.1.el7.x86_64 on an x86_64

ip-172-31-20-0 login:

asked a year ago426 views
1 Answer
0

I changed the instance type from t2.medium to t3.medium in order to allow a serial connection to debug further. This fixed the issue and the server was online again, without needing the serial interface. The system log seems to suggest the server was no longer assigned a private IP address at boot time.

No other changes were made other than changing the instance type.

Changing back to a t2.medium does not make the error reappear.

Can anyone shed any light on what might have caused this issue and how to avoid it in the future?

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions