Skip to content
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

Stuck at Waiting for Outline server to be healthy #1175

Closed
lvlrSajjad opened this issue Oct 4, 2022 · 2 comments
Closed

Stuck at Waiting for Outline server to be healthy #1175

lvlrSajjad opened this issue Oct 4, 2022 · 2 comments
Labels
customer support Customer support requests

Comments

@lvlrSajjad
Copy link

lvlrSajjad commented Oct 4, 2022

I tried to setup outline on a mac mini.
Though, it stuck in > Waiting for Outline server to be healthy .... Phase.
Checked docker logs and this is why:

level=info ts=2022-10-04T06:43:05.087Z caller=main.go:646 msg="Server is ready to receive web requests."
I2022-10-04T06:43:05.832Z 13 main.js:108] Prometheus is ready!
E2022-10-04T06:43:05.834Z 13 main.js:29] Error: ENOENT: no such file or directory, open '/opt/outline/persisted-state/shadowbox-selfsigned.crt'

It keeps being restarted.

I checked if the folder exists and it does exist.

I chowned the folder and these are the results which show the file is right there:

pwd
/opt/outline/persisted-state
ls
shadowbox-selfsigned.crt	shadowbox_server_config.json
shadowbox-selfsigned.key

UPDATE:

Ok it's fixed after. I chowned everything.
Now it's just stuck at > Waiting for Outline server to be healthy ....
Without any error.

A part of shadowbox logs:

I2022-10-04T07:01:23.781Z 12 main.js:29] Starting...
I2022-10-04T07:01:23.791Z 12 main.js:29] Prometheus is at 127.0.0.1:9090
I2022-10-04T07:01:23.792Z 12 main.js:29] Node metrics is at 127.0.0.1:9091
I2022-10-04T07:01:23.793Z 12 main.js:29] outline-ss-server metrics is at 127.0.0.1:9092
I2022-10-04T07:01:23.795Z 12 main.js:29] Replay protection enabled: true
I2022-10-04T07:01:23.813Z 12 main.js:108] Starting Prometheus with args [--config.file,/opt/outline/persisted-state/prometheus/config.yml,--web.enable-admin-api,--storage.tsdb.retention.time,31d,--storage.tsdb.path,/opt/outline/persisted-state/prometheus/data,--web.listen-address,127.0.0.1:9090,--log.level,info]
I2022-10-04T07:01:24.852Z 12 main.js:108] Prometheus is ready!
I2022-10-04T07:01:24.894Z 12 main.js:29] Manager listening at https://[::]:33549
level=info ts=2022-10-04T07:01:24.013Z caller=web.go:523 component=web msg="Start listening for connections" address=127.0.0.1:9090
level=info ts=2022-10-04T07:01:24.013Z caller=main.go:678 msg="Starting TSDB ..."
level=info ts=2022-10-04T07:01:24.251Z caller=head.go:575 component=tsdb msg="Replaying WAL, this may take awhile"
level=info ts=2022-10-04T07:01:24.269Z caller=head.go:624 component=tsdb msg="WAL segment loaded" segment=0 maxSegment=1
level=info ts=2022-10-04T07:01:24.281Z caller=head.go:624 component=tsdb msg="WAL segment loaded" segment=1 maxSegment=1
level=info ts=2022-10-04T07:01:24.282Z caller=head.go:627 component=tsdb msg="WAL replay completed" duration=30.568517ms
level=info ts=2022-10-04T07:01:24.287Z caller=main.go:694 fs_type=65735546
level=info ts=2022-10-04T07:01:24.287Z caller=main.go:695 msg="TSDB started"
level=info ts=2022-10-04T07:01:24.287Z caller=main.go:799 msg="Loading configuration file" filename=/opt/outline/persisted-state/prometheus/config.yml
level=info ts=2022-10-04T07:01:24.379Z caller=main.go:827 msg="Completed loading of configuration file" filename=/opt/outline/persisted-state/prometheus/config.yml
level=info ts=2022-10-04T07:01:24.379Z caller=main.go:646 msg="Server is ready to receive web requests."
I2022-10-04T07:01:24.912Z 31 server.go:254] Metrics on http://127.0.0.1:9092/metrics
I2022-10-04T07:01:24.912Z 31 server.go:260] Using IP-Country database at /var/lib/libmaxminddb/ip-country.mmdb
I2022-10-04T07:01:24.915Z 31 server.go:154] Loaded 0 access keys

I checked watch tower container logs:

time="2022-10-04T07:01:24Z" level=info msg="Watchtower 1.4.0"
time="2022-10-04T07:01:24Z" level=info msg="Using no notifications"
time="2022-10-04T07:01:24Z" level=info msg="Only checking containers using enable label"
time="2022-10-04T07:01:24Z" level=info msg="Scheduling first run: 2022-10-04 08:01:24 +0000 UTC"
time="2022-10-04T07:01:24Z" level=info msg="Note that the first check will be performed in 59 minutes, 59 seconds"

Does it mean that I have to wait for 59 minutes?

UPDATE 2:

After 59 mins:

time="2022-10-04T08:01:25Z" level=info msg="Session done" Failed=0 Scanned=1 Updated=0 notify=no

And still stuck at the same line:

> Starting Watchtower ......................... OK
> Waiting for Outline server to be healthy .... 

@lvlrSajjad lvlrSajjad changed the title no shadowbox-selfsigned.crt Stuck at Waiting for Outline server to be healthy Oct 4, 2022
@maddyhof
Copy link

Thank you for reaching out! If this is still an issue for you, please contact us at support.getoutline.org and include this GitHub issue number so that we can better support your needs.

If you haven’t already, check out the Outline Support Site at support.getoutline.org for access to help articles and more.

@maddyhof maddyhof added the customer support Customer support requests label Apr 25, 2023
@typomedia
Copy link

#1571

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer support Customer support requests
Projects
None yet
Development

No branches or pull requests

3 participants