gchristensen changed the topic of #nixops to: NixOps related talk | logs: https://logs.nix.samueldr.com/nixops/ https://meet.jit.si/NixOpsReview
tewfik has joined #nixops
<tewfik> @charukiewicz You can first run 'check' to update the actual state of the resource, then if the resource is marked as obsolete, you can launch a deploy operation with '--kill-obsolete' flag
<tewfik> If you still cannot destroy it, you can use the *delete-resource* sub-command to remove it from the state file
<tewfik> PR reference : charukiewicz
<{^_^}> nixops#1201 (by PsyanticY, 34 weeks ago, merged): Adding nixops delete-resources command
tewfik has quit [Quit: Leaving]
abathur has quit [Ping timeout: 240 seconds]
pbb has quit [Remote host closed the connection]
pbb has joined #nixops
<DigitalKiwi> gchristensen: they were in #nixos in february
pbb has quit [Remote host closed the connection]
pbb has joined #nixops
<virus_dave> qq, i must be doing something very stupid. I have a simple config similar to examples/vpc.nix shows. Specifying security group for my ec2 deployment with something like: securityGroupIds = [ resources.ec2SecurityGroups.test_sg.name ];
<virus_dave> gives an error like: InvalidGroupId.Malformed</Code><Message>Invalid id: "None" (expecting "sg-...")< ...
<virus_dave> which makes sense as value for `test_sg.name` looking at the implementation, but then i can’t figure out how examples/vpc.nix would ever work.
<virus_dave> meta: i’m finding nixops exceedingly difficult to debug when things don’t work, and so far they have failed at every step :(
cole-h has quit [Quit: Goodbye]
meh` has quit [Ping timeout: 265 seconds]
charukiewicz has quit [Quit: leaving]
meh` has joined #nixops
niso has quit [Ping timeout: 265 seconds]
niso has joined #nixops
<gchristensen> virus_dave: securityGroupIds = [ resources.ec2SecurityGroups.test_sg ] ; I think is all you need there
meh` has quit [Ping timeout: 264 seconds]
mtjmullen has quit [Ping timeout: 264 seconds]
mutantmell has joined #nixops
meh` has joined #nixops
virus_dave has quit [Quit: virus_dave]
teto has joined #nixops
teto has quit [Client Quit]
teto has joined #nixops
<davidtwco> I've started using `nixFlakes` in my NixOS configuration, and now running `nixops` (with pinned nixpkgs) fails with `error: stack overflow`; running with `nix-shell -p nix` fails with `unexpected end-of-file` - anyone got this working?
<davidtwco> Was hoping that I could use `nixFlakes` and still work with non-flakes nixops.
<davidtwco> when I increase `ulimit -s`, I get the same `unexpected end-of-file` as with `nix-shell -p nix`.
<gchristensen> sounsd like nix-daemon is being OOM'd, davidtwco
<gchristensen> probably from a very large source file being uploaded
<davidtwco> gchristensen: I suppose it's possible if it has a limited amount of memory that it'll use - I've got 64G on this system, I doubt it's using all that.
<gchristensen> maybe pass `-vvvv` and see what nix is telling you it is doing?
<davidtwco> what do I pass `-vvvv` to?
<gchristensen> nix-shell
<davidtwco> this is when running `nixops deploy`, would adding `-vvvv` to `nix-shell` tell me about that?
<gchristensen> oh I thought you were getting the error while running nix-shell too
<gchristensen> hrm... I think I have to defer to adisbladis. I'm pretty swamped right now and thought it'd be really easy to get you an answer :x
<davidtwco> I'm in a `nix-shell`, which has `nixops` - and originally the `unexpected end-of-file` only happened when I was running with `nix-shell -p nix` (since my system is using `nixFlakes`); but with `ulimit -s`, it happens outside of that shell (but still in the nix-shell with nixops).
<davidtwco> thanks for the help though
<gchristensen> but fwiw I got this same error when I tried uploading about 100 .iso's to the nix daemon as part of a single Nix source
<davidtwco> unless htop isn't updating fast enough, I don't think it's memory - I do have one large iso in this nixops network though, but not this particular host.
<gchristensen> anything in dmesg or the nix daemon's log
<davidtwco> ah, `nix-daemon` is also hitting the stack limit
meh` has quit [Ping timeout: 260 seconds]
<davidtwco> got it working by increasing my user's stack limit, and adding a directive to the systemd unit of the nix-daemon to increase it's stack limit
<gchristensen> please report a bug though? :)
meh` has joined #nixops
meh` has quit [Ping timeout: 265 seconds]
cole-h has joined #nixops
teto has quit [Ping timeout: 256 seconds]
abathur has joined #nixops
teto has joined #nixops
sevanspowell has quit [Ping timeout: 256 seconds]
manveru has quit [Ping timeout: 260 seconds]
feepo has quit [Ping timeout: 272 seconds]
gleber has quit [Ping timeout: 260 seconds]
davidtwco has quit [Ping timeout: 272 seconds]
dmj` has quit [Ping timeout: 272 seconds]
typetetris has quit [Ping timeout: 260 seconds]
kalbasit has quit [Ping timeout: 260 seconds]
sevanspowell has joined #nixops
davidtwco has joined #nixops
gleber has joined #nixops
feepo has joined #nixops
kalbasit has joined #nixops
dmj` has joined #nixops
manveru has joined #nixops
typetetris has joined #nixops
virus_dave has joined #nixops
cole-h has quit [Quit: Goodbye]
<virus_dave> @gchristensen thanks, i’d tried that too. this gives error of: The option value `deployment.ec2.securityGroupIds.[definition 1-entry 1]' in `/Users/dave/local/config/virusdave/nixops/scratch/test01/cloud-test.nix' is not of type `string'.
cole-h has joined #nixops
cole-h has quit [Client Quit]
cole-h has joined #nixops
cole-h has quit [Client Quit]
teto has quit [Quit: WeeChat 2.8]
cole-h has joined #nixops
cole-h has quit [Client Quit]