Skip to content

Commit 4022f86

Browse files
committed
Merge #296: Remove nixops examples and as recommended deployment method; replace with krops
520a983 docs: nixops-krops migration guide (nixbitcoin) 7c0b521 docs: describe deploying with krops in installation tutorial (Jonas Nick) eb6dff5 docs: various improvements to installation tutorial (Jonas Nick) e8b47f0 examples: add deploy-krops.sh (Erik Arvstedt) fe118b2 examples: add krops deployment method (Jonas Nick) e017675 krops: add package (Jonas Nick) 03db1a6 lnd, joinmarket: don't write to secrets dir (Erik Arvstedt) 55d8749 secrets: make configuration more robust (Erik Arvstedt) b0c223e secrets: don't stop services when the secrets target stops (Erik Arvstedt) b701cb5 secrets: add option 'generateSecrets' (Erik Arvstedt) 03515a8 examples/qemu: disable hardened preset (Erik Arvstedt) 908af3b examples/deploy-qemu-vm: show progress when waiting (Erik Arvstedt) ccba86a examples: extract common features for running QEMU VMs (Erik Arvstedt) cb3d544 examples: use relative paths to example files (Erik Arvstedt) a4dabc7 Remove nixops examples and documentation (Jonas Nick) Pull request description: ACKs for top commit: erikarvstedt: ACK 520a983 Tree-SHA512: 380fcda3528e703e8a218f92a216befbee6cc279952388b2df48c1bcb803b72336bbe6e4deed87f3f26caba7a5cb5ab60c2bcabf2b13eba56f34c47eb02e128a
2 parents b071859 + 520a983 commit 4022f86

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

42 files changed

+805
-648
lines changed

.gitignore

Lines changed: 0 additions & 1 deletion
This file was deleted.

docs/faq.md

Lines changed: 0 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -1,33 +1,3 @@
1-
* **Q:** When deploying or trying to SSH into the machine I see
2-
```
3-
bitcoin-node> waiting for SSH...
4-
Received disconnect from 10.1.1.200 port 22:2: Too many authentication failures
5-
```
6-
* **A:** Somehow ssh-agent and nixops don't play well together. Try killing the ssh-agent.
7-
* **Q:** When deploying or trying to SSH into the machine I see
8-
```
9-
[email protected]: Permission denied (publickey,password,keyboard-interactive).
10-
```
11-
Make sure you don't have something like
12-
```
13-
Host *
14-
PubkeyAuthentication no
15-
```
16-
in your ssh config.
17-
* **Q:** When deploying to virtualbox for the first time I see
18-
```
19-
bitcoin-node> Mar 19 09:22:27 bitcoin-node systemd[1]: Started Get NixOps SSH Key.
20-
bitcoin-node> Mar 19 09:22:27 bitcoin-node get-vbox-nixops-client-key-start[2226]: VBoxControl: error: Failed to connect to the guest property service, error VERR_INTERNAL_ERROR
21-
bitcoin-node> Mar 19 09:22:27 bitcoin-node systemd[1]: get-vbox-nixops-client-key.service: Main process exited, code=exited, status=1/FAILURE
22-
bitcoin-node> Mar 19 09:22:27 bitcoin-node systemd[1]: get-vbox-nixops-client-key.service: Failed with result 'exit-code'.
23-
bitcoin-node> error: Traceback (most recent call last):
24-
File "/nix/store/6zyvpi0q6mvprycadz2dpdqag4742y18-python2.7-nixops-1.6pre0_abcdef/lib/python2.7/site-packages/nixops/deployment.py", line 731, in worker
25-
raise Exception("unable to activate new configuration")
26-
Exception: unable to activate new configuration
27-
```
28-
* **A:** This is issue https://github.com/NixOS/nixops/issues/908. The machine needs to be rebooted. You can do that by running `nixops deploy` with the `--force-reboot` flag once.
29-
* **Q:** I'm deploying to virtualbox it's not able to connect anymore.
30-
* **A:** Maybe the IP address of the box changed. Run `nixops deploy --check` to update nixops with the new IP address. Sometimes you need to run `nixops modify -d <deployment> network/network.nix network/network-vbox.nix`. Sometimes you also need to remove the old IP address from `~/.ssh/known_hosts`.
311
* **Q:** The clightning service is running but when I try to use it (f.e. by running `lightning-cli getinfo` as user operator) all I get is `lightning-cli: Connecting to 'lightning-rpc': Connection refused`.
322
* **A:** Check your clightning logs with `journalctl -eu clightning`. Do you see something like `bitcoin-cli getblock ... false` failed? Are you using pruned mode? That means that clightning hasn't seen all the blocks it needs to and it can't get that block because your node is pruned. If you're just setting up a new node you can `systemctl stop clightning` and wipe your `/var/lib/clightning` directory. Otherwise you need to reindex the Bitcoin node.
333
* **Q:** My disk space is getting low due to nix.

0 commit comments

Comments
 (0)