-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on line 58 in commander script #15
Comments
Could you please check the boulder logs: either via https://host.domain.local/admin/logs/boulder or on the commandline (cd /home/labca/boulder; docker-compose logs boulder). |
Mmh, First look at the logs and it seems the database server isn`t coming up: boulder_1 | I210216192139 ocsp-responder mbD4lQM Loading OCSP Database for CA Cert: labca/test-ca.pem |
|
From
it appears that you may be running in an unprivileged container? |
Hmmm, never mind that - I see the same message also in an instance that is working fine |
Maybe try running the updater manually (/home/labca/labca/install) to force refreshing everything |
Hi, did the update, but again, same result: boulder_1 | rsyslogd: error during parsing file /etc/rsyslog.d/boulder.rsyslog.conf, on or before line 1: omfile: warning: default template was already set via legacy directive - may lead to inconsistent results. [v8.1901.0 try https://www.rsyslog.com/e/2207 ] |
Ok, i think i miss the /labca/config/health-checker.json root@linux5:/home/labca/boulder# ./bin/health-checker -addr ca2.boulder:9093 -config labca/config/health-checker.json |
Does /home/labca/boulder_labca/config/health-checker.json exist? Docker-compose should map the folder /home/labca/boulder_labca to the correct location inside the docker container |
yes, this exists root@linux5:/home/labca/boulder_labca/config# ls -l health* |
You could try to increase the timeout value in that health-checker.json to e.g. 10 seconds:
When I made mine smaller than the default at e.g. 100ms I see the same error messages as you. |
Nope, i think i setup a new fresh server and try again: boulder_1 | I210217123213 boulder-publisher kKG6cwA Caught SIGTERM |
So, fresh install, debian 10.8 this time english, same behaviour, only additional package is "ssh and basic" and webmin. boulder_1 | 2021/02/19 09:44:01 ct-test-srv on :4500 with pubkey MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEYggOxPnPkzKBIhTacSYoIfnSL2jPugcbUKx83vFMvk5gKAz/AGe87w20riuPwEGn229hKVbEKHFB61NIqNHC3Q== |
Can you check line 17 in /home/labca/boulder_labca/rate-limit-policies.yml - I see that your last two logs are complaining about that. |
I can`t see my host in that file: linux5.itschnack.local See cmd/shell.go for definitions of these rate limits.certificatesPerName: |
I've no idea how that could have happened, I'm not able to reproduce this in any way. If you would remove all the lines with only whitespace before the colon (": 10000") then at least the boulder-ra component should be able to start again. I'll further investigate how to prevent and especially recover from this situation |
Hi, strange. I created a complete new debian 10.8 VM, this time with english localization and installed only webmin. Same behaviour. I did all the tweaks mentioned here, but also no function (Also the remove of the :10000". I added my local fqdn in the top of the rate-limits. i copied some missing folders from boulder_ca to boulder/labca (config and grpc-certs). boulder_1 | rsyslogd: error during parsing file /etc/rsyslog.d/boulder.rsyslog.conf, on or before line 1: omfile: warning: default template was already set via legacy directive - may lead to inconsistent results. [v8.1901.0 try https://www.rsyslog.com/e/2207 ] |
* release/21.03: Prevent warning when updating LabCA Lower frequency of looking for file changes of hostname and rate-limit policies Do not wait for boulder startup when setup is not yet complete Wait longer for server to be ready before requesting first certificate Tweak description string of whitelist mode Fix config substitutions for whitelist mode (#15) Hold off on starting boulder until setup wizzard is completed Make installer more robust Make config substitutions more robust Stick to release tags even if there are newer commits on master Minor tweaks Fix query buildup when combining tables
I think I finally have solved the problem. Please try updating your instance (by running /home/labca/labca/install again), hopefully it works now. |
Hi thanks for your work and support. I did a fresh install of debian and installed it from beginning: No errors in the ACME Log, but still stuck on reloading the page for creating new certificate pair. So, i found this in the Certificate Log: Thu 04 Mar 2021 09:28:41 AM CET Now i wondering, why i can`t create .local Certs with a private PKI :) |
Ok, got it, restarted the whole process and now i got it running! thank you very much, what i can see, looks very good! |
Hi,
on a clean debian i had had some problems (after switched to explicit root (su - root) everything worked well) the website is stuck on "Almost there! Now we will request a certificate for this website and restart one more time...". I restarted several times, i think the problem is, that the webserver in the docker image isn`t ready. But, here are the results from the logs:
Web Certificate Log
Di 16. Feb 13:31:15 CET 2021
<title>502 Bad Gateway</title>Parsing account key...
Parsing CSR...
Found domains: host.domain.local
Getting directory...
Traceback (most recent call last):
File "/home/labca/acme_tiny.py", line 197, in
main(sys.argv[1:])
File "/home/labca/acme_tiny.py", line 193, in main
signed_crt = get_crt(args.account_key, args.csr, args.acme_dir, log=LOGGER, CA=args.ca, disable_check=args.disable_check, directory_url=args.directory_url, contact=args.contact)
File "/home/labca/acme_tiny.py", line 105, in get_crt
directory, _, _ = _do_request(directory_url, err_msg="Error getting directory")
File "/home/labca/acme_tiny.py", line 45, in _do_request
raise ValueError("{0}:\nUrl: {1}\nData: {2}\nResponse Code: {3}\nResponse: {4}".format(err_msg, url, data, code, resp_data))
ValueError: Error getting directory:
Url: http://host.domain.local
Data: None
Response Code: 502
Response:
502 Bad Gateway
nginx
LABCA Logs
labca_1 | 2021/02/16 12:33:56 errorHandler: ERROR! On line 58 in commander script
labca_1 | main._hostCommand(0xbd1c00, 0xc00027e0e0, 0xc00024e700, 0xb104bf, 0xc, 0x0, 0x0, 0x0, 0xb3b500)
labca_1 | /go/src/labca/main.go:1513 +0x5a5
labca_1 | main.finalHandler(0xbd1c00, 0xc00027e0e0, 0xc00024e700)
labca_1 | /go/src/labca/main.go:1860 +0xf9
labca_1 | net/http.HandlerFunc.ServeHTTP(0xb3ac58, 0xbd1c00, 0xc00027e0e0, 0xc00024e700)
labca_1 | /usr/local/go/src/net/http/server.go:2042 +0x44
labca_1 | main.authorized.func1(0xbd1c00, 0xc00027e0e0, 0xc00024e700)
labca_1 | /go/src/labca/main.go:2316 +0x230
labca_1 | net/http.HandlerFunc.ServeHTTP(0xc000130b20, 0xbd1c00, 0xc00027e0e0, 0xc00024e700)
labca_1 | /usr/local/go/src/net/http/server.go:2042 +0x44
labca_1 | github.com/gorilla/mux.(*Router).ServeHTTP(0xc00020a0c0, 0xbd1c00, 0xc00027e0e0, 0xc00024e500)
labca_1 | /go/pkg/mod/github.com/gorilla/mux@v1.8.0/mux.go:210 +0xd3
labca_1 | net/http.serverHandler.ServeHTTP(0xc0001062a0, 0xbd1c00, 0xc00027e0e0, 0xc00024e500)
labca_1 | /usr/local/go/src/net/http/server.go:2843 +0xa3
labca_1 | net/http.(*conn).serve(0xc0002540a0, 0xbd32c0, 0xc00023df00)
labca_1 | /usr/local/go/src/net/http/server.go:1925 +0x8ad
labca_1 | created by net/http.(*Server).Serve
labca_1 | /usr/local/go/src/net/http/server.go:2969 +0x36c
labca_1 | 2021/02/16 12:33:56 http: superfluous response.WriteHeader call from main.finalHandler (main.go:1861)
labca_1 | 2021/02/16 12:34:11 ERROR: Message from server: 'ERROR! On line 58 in commander script
labca_1 | '
labca_1 | 2021/02/16 12:34:11 errorHandler: ERROR! On line 58 in commander script
labca_1 | main._hostCommand(0xbd1c00, 0xc00027e2a0, 0xc00024ed00, 0xb104bf, 0xc, 0x0, 0x0, 0x0, 0xb3b500)
labca_1 | /go/src/labca/main.go:1513 +0x5a5
labca_1 | main.finalHandler(0xbd1c00, 0xc00027e2a0, 0xc00024ed00)
labca_1 | /go/src/labca/main.go:1860 +0xf9
labca_1 | net/http.HandlerFunc.ServeHTTP(0xb3ac58, 0xbd1c00, 0xc00027e2a0, 0xc00024ed00)
labca_1 | /usr/local/go/src/net/http/server.go:2042 +0x44
labca_1 | main.authorized.func1(0xbd1c00, 0xc00027e2a0, 0xc00024ed00)
labca_1 | /go/src/labca/main.go:2316 +0x230
labca_1 | net/http.HandlerFunc.ServeHTTP(0xc000130d20, 0xbd1c00, 0xc00027e2a0, 0xc00024ed00)
labca_1 | /usr/local/go/src/net/http/server.go:2042 +0x44
labca_1 | github.com/gorilla/mux.(*Router).ServeHTTP(0xc00020a0c0, 0xbd1c00, 0xc00027e2a0, 0xc00024eb00)
labca_1 | /go/pkg/mod/github.com/gorilla/mux@v1.8.0/mux.go:210 +0xd3
labca_1 | net/http.serverHandler.ServeHTTP(0xc0001062a0, 0xbd1c00, 0xc00027e2a0, 0xc00024eb00)
labca_1 | /usr/local/go/src/net/http/server.go:2843 +0xa3
labca_1 | net/http.(*conn).serve(0xc0002541e0, 0xbd32c0, 0xc00043c180)
labca_1 | /usr/local/go/src/net/http/server.go:1925 +0x8ad
labca_1 | created by net/http.(*Server).Serve
labca_1 | /usr/local/go/src/net/http/server.go:2969 +0x36c
labca_1 | 2021/02/16 12:34:11 http: superfluous response.WriteHeader call from main.finalHandler (main.go:1861)
labca_1 | 2021/02/16 12:34:39 GET /logs/web
labca_1 | 2021/02/16 12:34:39 GET /ws?logType=web
labca_1 | 2021/02/16 12:35:00 GET /logs/weberr
labca_1 | 2021/02/16 12:35:25 GET /logs/labca
labca_1 | 2021/02/16 12:35:25 GET /ws?logType=labca
Thanks for this project and your support.
The text was updated successfully, but these errors were encountered: