Questions tagged with Linux Provisioning
Content language: English
Sort by most recent
AWS instance randomly becomes unresponsive
My AWS instance randomly becomes unresponsive everyday. I won't be able to ``ping`` it and all ports on the public IP are inaccessible but it shows the instance is running from the AWS dashboard. The only way to fix it is by rebooting but I don't want to have to do this every day. The instance reachability check fails but the system status check doesn't ![status check](/media/postImages/original/IMrJ6TIc7pSVKt1XkZhJ6iRQ) The CPU utilization is not even high so I know it isn't crashing or something. ![cpu utilization](/media/postImages/original/IMG3l0VCteQKypIPRy7h_w1w) The system log doesn't show anything wrong either (pastebin: https://pastebin.com/Ri1ui8sp). My machine type doesn't have EC2 serial console so I can't access that either.
Not able to connect ssh which i have created vm from the existing AMI
I am not able to connect ssh to the newly created vm using existing AMI backup and also tried creating vm by taking AMI backup from the running vm too. Either way i am unable to connect. Network and security group is all fine. I am pretty badly needed to run another instance of running vm by referring existing AMI or creating anything new AMI. Please help me to fix this : Instance-ID:i-0dea1177b03bc9c5d AMI: ami-0e69a19245c9c3248 ami-0c95fb1ecf1c439f1 Thanks,
Update Java on Greengrass devices - use "Install" lifecicle in manifest?
We are in a position that we need to update the Java version on our greengrass devices running Linux. I'm looking at what is the best method to orchestrate this, or some best practice information The updated java comes as a requirement of one of our custom compoments, so an option is to use the "Install" lifecycle of the artifact in the manifest. Then use the "onpath" or "exists" method to make sure it only runs once, which is a bit clunky. The benefit is that the update is part of the GG deployment which makes it nice and contained. We also have System manager client running on these devices, so we could use systems manager to do this to. I'm leading towards using the install lifecycle in the manifest but I'm interested if there are any better ideas, or if it's not the right tool for the job. Cheers J
Unable to Connect to AWS EC2
I am not being able to ssh to EC2 instances in any location! Whenever I try to connect I have been shown unable to connect, whether using the aws console or by using Windows cmd! Amazon EC2 AWS Command Line Interface, Compute, Linux Provisioning, Network and Content Delivery!
Lightsail Instance Data Import To Lightsail Database: ERROR 1045 (28000): Access denied for user
I keep getting denied when entering MySQL password after executing the following command (example): `sudo mysqldump -u root --databases bitnami_wordpress --single-transaction --compress --order-by-primary -p$(cat /home/bitnami/bitnami_application_password) | sudo mysql -u dbmasteruser --host ls-abc123exampleE67890.czowadgeezqi.us-west-2.rds.amazonaws.com --password` I enter the password CORRECTLY and I get the following server reply: *ERROR 1045 (28000): Access denied for user 'dbmasteruser'@'17x.xx.xx.8x' (using password: YES) mysqldump: Got errno 32 on write* I am able to connect to the database via MySQL Workbench with no issues. I am running the commands via Direct SSH Terminal via Lightsail browser (Tried Putty as well). I also tried switch to an IAM account with the same result. Resources are all in same region and zone and I am using a static IP. Any suggestions? Thank you in advance.
EC2 instance created with public IP, but unable to access over HTTP
Created an EC2 instance, having a VPC with attached Internet gateway, Security groups with inbound rule to allow any traffic fro HTTP, HTTPS and having all traffic allowed for outbound rule. internet gateway created, attached to VPC using, and add it to the route table too. But even after successful launch, instance is unreachable when hitting the assigned public ip from browser. Also when used to connect the instance from "CONNECT" button , getting console opened but later errors out with message: `EC2 Instance Connect is unable to connect to your instance. Ensure your instance network settings are configured correctly for EC2 Instance Connect. For more information, see Set up EC2 Instance Connect at https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-connect-set-up.html.` Any pointers are highly appreciated.
RE : AWS Inspector Shows Critical Updates Pending But Instance Says Otherwise
Hi Team, Instance ID - i-0e5934adddc2d8372 I've updated all the packages (See Libcurl-2.png). But the Inspector still shows critical updates are pending on my instance (See Libcurl-1.png) Requesting help in investigating this.![![Enter image description here](/media/postImages/original/IMgUGzjYUXQAOinPmO1hAqZg) Enter image description here](/media/postImages/original/IMjXCbaW5ZTuaGmhzz6Nw26g) ![Enter image description here](/media/postImages/original/IMQf0BnF4-RvGK_YroaAC43Q) Eg : >>> This is what Inspector Shows For The Instance : Affected packages Name libcurl Installed version / Fixed Version 0:7.79.1-4.amzn2.0.1.X86_64 / 0:7.79.1-6.amzn2.0.1 Package manager OS Name curl Installed version / Fixed Version 0:7.79.1-4.amzn2.0.1.X86_64 / 0:7.79.1-6.amzn2.0.1 Package manager OS >>> This is what the Instance shows when trying to remediate (i.e update the package -> It says its already updated) sh-4.2$ sudo yum update libcurl Loaded plugins: extras_suggestions, langpacks, priorities, update-motd amzn2-core | 3.7 kB 00:00:00 No packages marked for update sh-4.2$
One user unable to sudo on specific EC2 instances (g4/g5.*). PAM account management error is thrown while trying to sudo
We have multiple EC2 machines in our account, all AL2. One user is unable to sudo on specific instance types (g4/g5), while others can. The user is a part of sudoers and other users able to sudo on the same instance types. This becomes weirder when this user is able to sudo on other instance types (c5, m5, etc.). Error thrown is PAM account management error: Authentication service cannot retrieve authentication info ; TTY=pts/2 ; PWD=/home/<userid>; USER=root ; COMMAND=/usr/bin/su The users on these servers are authenticated using sssd hitting the enterprise LDAP server, so they are not created locally. We upgraded/downgraded the sudo version but it did not help. Any advise would be appreciated. [root@ip-100-x-x-x log]# cat /etc/os-release NAME="Amazon Linux" VERSION="2" ID="amzn" ID_LIKE="centos rhel fedora" VERSION_ID="2" PRETTY_NAME="Amazon Linux 2" ANSI_COLOR="0;33" CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2" HOME_URL="https://amazonlinux.com/"
Mismatch between nginx and nginx-mod-http-geoip in @amzn2extra-nginx1 repos
We rely on **@amzn2extra-nginx1** to keep nginx up to date on our amzn2 EC2 instance. A week ago, most nginx packages, including core, have been updated to the **1.22** version, as shown from `yum list` ``` nginx.x86_64 1:1.22.0-1.amzn2.0.1 amzn2extra-nginx1 ``` However, the GEOIP module is stuck at the previous version **1.20**, as shown from `yum list` ``` nginx-mod-http-geoip.x86_64 1:1.20.0-2.amzn2.0.5 amzn2extra-nginx1 ``` Is this the correct place to flag this, or are there dedicated resources to flag repo-related issues? Tried googling but couldn't find a better place than this one.
Are All EC2 Instance Level Storage Lost Upon Rebooting the Instance?
Apologies for the noob question. Some readings led me to believe that an instance level EC2 storage will be lost if I reboot. So the questions I have are * If the storage is totally lost, how does a computer even remember anything? Should not it remember at least the username, password, sudo group etc. across reboots? * How to store my codes, configurations in an EC2 instance to be retained across reboots? Is it possible at all, or does it have to be something like an EBS that is decoupled from the instance and must be mounted on every start up? I am intending to use Ubuntu 22.04 as the OS, if that is important.
Patch manager doesn't work on Rocky Linux
Hello all, I'm trying to use the patch manager to update the Rocky Linux instance, But when I go to upgrade via Patch manager I received the following error: ![Enter image description here](/media/postImages/original/IMTRBft2xVRn-tyWt_xpzLhg) Any idea where I'm going wrong. Thanks