Problem with docker installation


(artem) #1

Hello. I was tryed to do the manual installation of discourse with the following steps:

  1. Cloned the repository.
  2. Created ./container/discourse-main.yml template (from samples), changed port mappings.
  3. Run launcher script (there was first error that image local_discourse/discourse-main is not found, so i used docker tag to fix this).
  4. The container runs successfully, but there is no listened port into it. There is contianer logs:
    run-parts: executing /etc/runit/1.d/00-fix-var-logs
    run-parts: executing /etc/runit/1.d/anacron
    run-parts: executing /etc/runit/1.d/cleanup-pids
    Cleaning stale PID files
    Started runsvdir, PID is 26
    rsyslogd: command ‘KLogPermitNonKernelFacility’ is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try htp://www.rsyslog.com/e/2222 ]
    rsyslogd: imklog: cannot open kernel log (/proc/kmsg): Operation not permitted.
    rsyslogd: activation of module imklog failed [v8.16.0 try htp://www.rsyslog.com/e/2145 ]
    rsyslogd: Could not open output pipe ‘/dev/xconsole’:: No such file or directory [v8.16.0 try htp://www.rsyslog.com/e/2039 ]

Can you help me please? I wanna access discourse http port (exposed from container on host’s custom port) through nginx.


(artem) #2

I just fixed my problem.
But now there’s another problem: discourse is spamming me via email for activating my accout, that was already activated.
Please help.


(Bhanu Sharma) #3

Check your sidekiq jobs
If there are any that state activation email just delete them

Visit sidekiq from your.discourse.domain/sidekiq


(Andrey) #4

Facing this error now. How did you fix it?


(Bhanu Sharma) #5

Can you explain in brief what issue are you facing exactly?


(Andrey) #6

I’m trying to install discourse with ssl and nginx
The site is not working now and I found this in logs

rsyslogd: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
rsyslogd: imklog: cannot open kernel log (/proc/kmsg): Operation not permitted.
rsyslogd: activation of module imklog failed [v8.16.0 try http://www.rsyslog.com/e/2145 ]
rsyslogd: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.16.0 try http://www.rsyslog.com/e/2039 ]
supervisor pid: 281 unicorn pid: 310
Reopening logs

(Andrew Schleifer) #7

Rsyslogd is, as the name suggests, a logging process. It will not prevent the site from running.

Can you be more specific about how “[t]he site is not working” –

  • Does curl localhost return any input from outside the container?
  • Can you enter the container with launcher?
  • Are nginx and unicorn running inside the container?
  • Does curl localhost return any input from inside the container?

(Andrey) #8

I made some changes to app.yml and nginx config file, rebuild it and now site is working, but I’ve got problems with sending emails. Discribed it here

Regarding KLogPermitNonKernelFacility - i still see it when run

docker logs app 
/var/discourse$ docker logs app
run-parts: executing /etc/runit/1.d/00-ensure-links
run-parts: executing /etc/runit/1.d/00-fix-var-logs
run-parts: executing /etc/runit/1.d/anacron
run-parts: executing /etc/runit/1.d/cleanup-pids
Cleaning stale PID files
run-parts: executing /etc/runit/1.d/copy-env
run-parts: executing /etc/runit/1.d/enable-brotli
run-parts: executing /etc/runit/1.d/remove-old-socket
Started runsvdir, PID is 40
ok: run: redis: (pid 50) 0s
ok: run: postgres: (pid 48) 0s
rsyslogd: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
rsyslogd: imklog: cannot open kernel log (/proc/kmsg): Operation not permitted.
rsyslogd: activation of module imklog failed [v8.16.0 try http://www.rsyslog.com/e/2145 ]
rsyslogd: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.16.0 try http://www.rsyslog.com/e/2039 ]

Regarding your questions. Yes, I am able to enter app and when I run

/var/discourse$ curl localhost

I see

<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor=“white”>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/1.10.3 (Ubuntu)</center>
</body>
</html>


(Sam Saffron) #9

KLogPermitNonKernelFacility is not your issue. Getting a redirect on localhost is likely due to having HTTPS template enabled. I would try without HTTPS if you are handling all termination in your front end proxy.