| 17 Jul 2022 |
|  @rendakuenthusiast:imperishable.name joined the room. | 04:28:23 |
| @rendakuenthusiast:imperishable.name | I'm getting a "child process was killled by signal 11" error when I try to use colmena to remove a specific piece of configuration from a remote machine, not sure how to debug | 04:29:16 |
| @rendakuenthusiast:imperishable.name | specifically this happens when I try to remove a vhost from an nginx config | 04:29:45 |
| @rendakuenthusiast:imperishable.name | literally deleting the block because I don't need that vhost anymore | 04:29:57 |
| @rendakuenthusiast:imperishable.name | I tried renaming the vhost and that seemed to apply without a problem | 04:30:12 |
 Winter (she/her) | oh wow that's weird
i assume the vhost names don't have anything weird about them? | 04:30:46 |
| Winter (she/her) | like any weird characters or something | 04:30:53 |
| @rendakuenthusiast:imperishable.name | nope, just normal ascii urls | 04:31:00 |
| Winter (she/her) | if you run with --verbose, where is it segfaulting? eval? | 04:31:30 |
| @rendakuenthusiast:imperishable.name | is there a way I can tell what the child process is? | 04:31:31 |
| @rendakuenthusiast:imperishable.name | does colmena have a verbose option? | 04:31:54 |
| @rendakuenthusiast:imperishable.name | I'm specifically running nix-shell -p colmena --run 'colmena apply -f my-hive.nix' | 04:32:19 |
| Winter (she/her) | In reply to @winterqt:nixos.dev
if you run with --verbose, where is it segfaulting? eval? ^^, it won't show what command is being run but it'll at least show if the failure is eval or apply related | 04:34:13 |
| @rendakuenthusiast:imperishable.name | ok I'll try that | 04:36:39 |
| @rendakuenthusiast:imperishable.name | didn't help, just prints out:
(...) | Evaluation failed: Child process was killed by signal 11
| Failed: Child process was killed by signal 11
| 04:37:15 |
| @rendakuenthusiast:imperishable.name | this is nix-shell -p colmena --run 'colmena apply -f my-hive.nix --verbose' | 04:37:54 |
| Winter (she/her) | okay at least we know it's eval related... somehow.
to be clear, you can reliably reproduce this by making a single change, right? | 04:38:26 |
