By using AWS re:Post, you agree to the Terms of Use

Unanswered Questions tagged with Linux Provisioning

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

What to look at for resolving Nice DCV 404 errors

I've got an EC2 instance setup with Nice DCV. I have setup port access in my security rules and created a session in nice dcv. However, whenever I try to connect to the session via the browsed, I get an HTTP ERROR 404. I can't seem to find any information in the Nice DCV docs about causes of 404 except for the session resolver which I'm not using. How can I go about resolving this issue? Below is the output from dcv list-sessions -j ``` [ { "id" : "cloud9-session", "owner" : "ubuntu", "num-of-connections" : 0, "creation-time" : "2022-09-23T12:58:40.919860Z", "last-disconnection-time" : "", "licenses" : [ { "product" : "dcv", "status" : "licensed", "check-timestamp" : "2022-09-23T12:58:42.540422Z", "expiration-date" : "" }, { "product" : "dcv-gl", "status" : "licensed", "check-timestamp" : "2022-09-23T12:58:42.540422Z", "expiration-date" : "" } ], "licensing-mode" : "EC2", "storage-root" : "", "type" : "virtual", "status" : "running", "x11-display" : ":0", "x11-authority" : "/run/user/1000/dcv/cloud9-session.xauth", "display-layout" : [ { "width" : 800, "height" : 600, "x" : 0, "y" : 0 } ] } ] ``` This is the output from dcv get-config ``` [connectivity] web-use-https = false web-port = 8080 web-extra-http-headers = [('test-header', 'test-value')] [security] authentication = 'none' ``` This is the output from systemctl status dcvserver ``` ● dcvserver.service - NICE DCV server daemon Loaded: loaded (/lib/systemd/system/dcvserver.service; enabled; vendor preset: enable> Active: active (running) since Fri 2022-09-23 12:58:40 UTC; 18min ago Main PID: 715 (dcvserver) Tasks: 6 (limit: 76196) Memory: 39.9M CGroup: /system.slice/dcvserver.service ├─715 /bin/bash /usr/bin/dcvserver -d --service └─724 /usr/lib/x86_64-linux-gnu/dcv/dcvserver --service Sep 23 12:58:40 ip-10-0-0-115 systemd[1]: Starting NICE DCV server daemon... Sep 23 12:58:40 ip-10-0-0-115 systemd[1]: Started NICE DCV server daemon. ``` I'm trying to access the page with http://<public ip>:8080 I've also tried including the #session_id part in the url and using the windows client with no luck. My operating system is Ubuntu 20.04 with a custom AMI running in a g4dn.4xlarge machine.
0
answers
0
votes
16
views
asked 2 days ago
0
answers
0
votes
17
views
asked 9 days ago

Unable to upgrade SLES12 SP5 to SLES 15 SP1

In SLES 12 SP5, when we reboot the Server after installing below package to migrate the system to SLES 15 SP1 ``` zypper in SLES15-Migration suse-migration-sle15-activation ``` its failing to migrate to SLES 15 SP1 with below mentioned error logs: ``` Device path /dev/disk/by-uuid/"b7bbd4b5-81ee-4cf9-b80f-048dd3eb6085" not found and skipped Device path /dev/disk/by-uuid/"242dbaba-e687-48ea-99fb-3b5f905123da" not found and skipped Device path /dev/disk/by-uuid/"03eefbc1-b95f-4125-a7bc-83034bff48ae" not found and skipped Device path /dev/disk/by-uuid/"b9459393-776b-473c-bc7a-7d17de295a6d" not found and skipped Device path /dev/disk/by-uuid/"f7cf5298-1a20-4a79-8b22-546b0c44176b" not found and skipped Device path /dev/disk/by-uuid/"aef286fb-4fb0-4e47-a2cd-f2bc31af7d03" not found and skipped Device path /dev/disk/by-uuid/"19456e98-c7da-4591-b295-e0fc297179f4" not found and skipped Device path /dev/disk/by-uuid/"04db4e56-3f5a-4f77-86c1-5c3932f8ca58" not found and skipped Calling: ['blkid', '-s', 'TYPE', '-o', 'value', '/dev/disk/by-label/ROOT'] Running suse-migration-pre-checks with options: fix: False Device path /dev/disk/by-uuid/"b7bbd4b5-81ee-4cf9-b80f-048dd3eb6085" not found and skipped Calling: ['blkid', '-s', 'TYPE', '-o', 'value', '/dev/disk/by-label/ROOT'] Running suse-migration-pre-checks with options: fix: False Calling: ['blkid', '-s', 'TYPE', '-o', 'value', '/dev/disk/by-label/ROOT'] Running suse-migration-pre-checks with options: fix: False Calling: ['blkid', '-s', 'TYPE', '-o', 'value', '/dev/disk/by-label/ROOT'] Running suse-migration-pre-checks with options: fix: False Calling: ['blkid', '-s', 'TYPE', '-o', 'value', '/dev/disk/by-label/ROOT'] Running suse-migration-pre-checks with options: fix: False Calling: ['blkid', '-s', 'TYPE', '-o', 'value', '/dev/disk/by-label/ROOT'] Running suse-migration-pre-checks with options: fix: False Calling: ['blkid', '-s', 'TYPE', '-o', 'value', '/dev/disk/by-label/ROOT'] ``` This happening after 25th Aug 2022. Before that we could migrate successfully. Please check and help us to fix this error.
0
answers
0
votes
23
views
asked 18 days ago

AWS Batch job stuck in RUNNABLE state

I'm trying to execute a Batch Job with the help of AWS AMI. The Compute Environment for the job is intended to have certain installations for which I need to use AMI. But whenever I give the AMI reference in Compute Environment, the job gets stuck in RUNNABLE state forever. I have tried all the troubleshooting measures given in https://aws.amazon.com/premiumsupport/knowledge-center/batch-job-stuck-runnable-status/ but even that did not help. I even tried using different AMIs for the same. It has been observed that jobs get stuck whenever any custom AMI is used,. As soon as job is submitted, the instance is launched but the job still fails to execute. Without the use of AMI, I have been able to execute the job successfully. I want to know the possible causes and reasons of this. Following are the details of my Compute Environment: ``` { "computeEnvironmentName": "computeenvironmentname", "type": "MANAGED", "state": "ENABLED", "unmanagedvCpus": 0, "computeResources": { "type": "EC2", "allocationStrategy": "BEST_FIT_PROGRESSIVE", "minvCpus": 0, "maxvCpus": 256, "desiredvCpus": 0, "instanceTypes": [ "p3.2xlarge" ], "imageId": "imageid", "subnets": [ "list of subnets" ], "securityGroupIds": [ "security groups" ], "ec2KeyPair": "keypair", "instanceRole": "instancerole", "tags": { "KeyName": "" }, "placementGroup": "", "bidPercentage": 0, "spotIamFleetRole": "", "launchTemplate": { "launchTemplateId": "", "launchTemplateName": "", "version": "" }, "ec2Configuration": [ { "imageType": "ECS_AL2_NVIDIA", "imageIdOverride": "imageid" } ] }, "serviceRole": "servicerole", "tags": { "KeyName": "" } } ```
0
answers
0
votes
19
views
asked a month ago

AuthorizedKeysCommand /usr/share/ec2-instance-connect/eic_run_authorized_keys <username> SHA256:<long hex string> failed, status 22

We use Ubuntu 20.04 (`ami-0c8858c090152d291`) as the basis for a production ecommerce stack, and I need to move users around as part of a handover. In order to do this I am trying to ssh in to the instance using the original ami-configured instance user and AWS generated key, so I can move the user I normally log in as. This fails with the subject error in `/var/log/auth.log`. I have reconfirmed keys and user many times obviously. This appears to be related to [AuthorizedKeysCommand fails on Ubuntu 20.04](https://github.com/widdix/aws-ec2-ssh/issues/157), which blames the package `ec2-instance-connect`. We keep instances up to date, so I suspect this package was installed as part of a post-install security update. The above-linked GitHub thread suggests: ``` # rm /usr/lib/systemd/system/ssh.service.d/ec2-instance-connect.conf # systemctl daemon-reload ``` I have tried the above unsuccessfully. Even after removing `ec2-instance-connect.conf` and issuing either `systemctl daemon-reload` or `kill -s HUP <sshd pid>` the sshd process is *still* running using the `ec2-instance-connect.conf` settings: ``` sshd: /usr/sbin/sshd -D -o AuthorizedKeysCommand /usr/share/ec2-instance-connect/eic_run_authorized_keys %u %f -o AuthorizedKeysCommandUser ec2-instance-connect [listener] 0 of 10-100 startups ``` For obvious reasons I am reluctant to tinker more extensively with the sshd configuration on a production server without hearing from the community. It seems rather questionable (to put it mildly) for a "security update package" to hijack the normal sshd auth process, especially with no well publicized info, only to come to light when I actually have to work on it. The package listing says > Configures ssh daemon to accept EC2 Instance Connect ssh keys -but what it fails to add is "... and may disable other keys". We surely cannot be the first ones to encounter this problem??
0
answers
0
votes
41
views
asked 2 months ago