NixOS AWS | 64 Members | |
| 15 Servers |
| Sender | Message | Time |
|---|---|---|
| 6 Nov 2024 | ||
| Also import image takes *waaaay* longer than import-snapshot | 23:34:25 | |
| Like 25-30 minutes | 23:34:30 | |
| 7 Nov 2024 | ||
| Feature request on the public Cfn roadmap: https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/2175 Will be chasing AWS internally for this one as well. | 00:16:05 | |
| * Feature request on the public Cfn roadmap: https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/2175 | 00:29:24 | |
| Please do let me know if there's any help I can lend to this PR, besides testing/reviewing: https://github.com/NixOS/nixpkgs/pull/343939 | 15:46:40 | |
| Just seems to need a rebase and a re-review | 15:49:10 | |
| We did go into breaking changes freeze for 24.11 though. So idk if I can still merge it :/ | 15:49:31 | |
| 19:52:46 | ||
| hi! I'm using my custom NixOS AMI built with "${modulesPath}/../maintainers/scripts/ec2/amazon-image.nix" module. The EC2 serial console in the AWS web interface works (shows boot messages like it's a display), but "get system log" in the web interface, and the aws ec2 get-console-output command both always return empty output.Is the system log thing even supposed to work? I am not very familiar with AWS, but I thought it works via the same mechanism as the EC2 serial console, and since the amazon-image.nix module enables serial console via kernel param ( console=ttyS0), it should work too | 20:04:28 | |
| * hi! I'm using my custom NixOS AMI built with "${modulesPath}/../maintainers/scripts/ec2/amazon-image.nix" module. The EC2 serial console in the AWS web interface works (shows boot messages like it's a display), but "get system log" in the web interface, and the aws ec2 get-console-output command both always return empty output.Is the system log thing even supposed to work? I am not very familiar with AWS, but I thought it works via the same mechanism as the EC2 serial console, and since the amazon-image.nix module enables serial console via kernel param ( console=ttyS0), it should work too | 20:04:40 | |
| This is expected for Nitro instances you need to call get-console-output with --latest | 20:13:04 | |
| get-console-output without --latest is only available after instance termination | 20:13:28 | |
| Or Connect -> EC2 Serial Console. Should work roo | 20:14:19 | |
| * Or Connect -> EC2 Serial Console. Should work too | 20:14:26 | |
| * get-console-output without --latest is only available after instance termination . Or around 15 minutes after the instance started | 20:14:45 | |
In reply to @arianvp:matrix.orgoh, thank you very much! indeed it returns the output after termination. I wonder why the web interface doesn't warn about it | 20:17:25 | |
| But the --latest flag should work too | 20:18:18 | |
In reply to @arianvp:matrix.orgyes, just tried it, it works! not immediately after instance launch, but quite quickly | 20:20:56 | |
interesting, after termination the output is again empty, with --latest or without | 20:27:40 | |
| ok, a few more munutes after the termination get-console-output starts returning the full output again. I guess it's just a bit of weirdness on AWS side | 20:32:47 | |
| 8 Nov 2024 | ||
| Arian: Thanks for the help the other day https://github.com/tuxiqae/autovm | 22:56:29 | |
BTW, had to use 24.05 since AMI building in unstable seems to be broken due to hash mismatch in the getty package. Couldn't figure where the faulty hash is defined so I didn't fix it yet | 22:58:29 | |
Download image.png | 22:58:33 | |
| 9 Nov 2024 | ||
hmmm | 04:26:31 | |
| Sometimes AWS just .... Doesn't work | 08:47:34 | |
| I've had it before where instance just doesn't get into the healthy state and nothing was wrong | 08:47:53 | |
| 10 Nov 2024 | ||
| 20:02:20 | ||
| 11 Nov 2024 | ||
| Draft PR for amazon-ec2-net-utils: https://github.com/NixOS/nixpkgs/pull/355111 Someone will need to update the NixOS systemd libs to allow setting the | 02:34:15 | |
| Oh no, sorry, it was just a joke about smoking. :( | 17:31:37 | |
| Though that does remind me, it maybe doesn't matter, but I am curious if you thought about using systemd-boot instead of grub on the EFI image.s | 17:32:19 | |