@lll wrote:

Discourse has a setting to disable all outgoing emails.

email.PNG1195x321 27 KB

If you enable this option Discourse shows an alert to let admins know and it looks like this when an you use an admin account:

Admin view:

Capture.jpg2175x1347 456 KB

However, the alert is also displayed to logged out users - and I presume to non-admin users as well - like so:

Logged out view:

logged out.jpg2024x1194 306 KB

Notice how the bootstrap alert does not show for logged out users. I expect the desired result is the same.

---

Edgy… but came across it so figured I should mention it

Posts: 3

Participants: 2

Read full topic

@Anshul_TM wrote:

Hello,

My forum has a category which is relevant to OP and staff only.

I’d like to suppress all posts by others in the category, but keep my posts visible on homepage.

Even better if we can not suppress for staff members, in addition to above.

Thanks

Posts: 4

Participants: 3

Read full topic

@Tumi wrote:

Hello . I was think its all ok and i was mega happy but NO , not yet …

This is from terminal:

> Already up-to-date.
> I, [2017-12-22T13:00:12.317668 #13]  INFO -- : Loading --stdin
> I, [2017-12-22T13:00:12.323458 #13]  INFO -- : > mkdir -p /shared/postgres_run
> I, [2017-12-22T13:00:12.336627 #13]  INFO -- :
> I, [2017-12-22T13:00:12.337106 #13]  INFO -- : > chown postgres:postgres /shared/postgres_run
> I, [2017-12-22T13:00:12.386537 #13]  INFO -- :
> I, [2017-12-22T13:00:12.387049 #13]  INFO -- : > chmod 775 /shared/postgres_run
> I, [2017-12-22T13:00:12.389418 #13]  INFO -- :
> I, [2017-12-22T13:00:12.389737 #13]  INFO -- : > rm -fr /var/run/postgresql
> I, [2017-12-22T13:00:12.392340 #13]  INFO -- :
> I, [2017-12-22T13:00:12.392679 #13]  INFO -- : > ln -s /shared/postgres_run /var/run/postgresql
> I, [2017-12-22T13:00:12.437103 #13]  INFO -- :
> I, [2017-12-22T13:00:12.437499 #13]  INFO -- : > socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running     stop container ; exit 1
> 2017/12/22 13:00:12 socat[21] E connect(6, AF=1 "/shared/postgres_run/.s.PGSQL.5432", 36): No such file or directory
> I, [2017-12-22T13:00:13.035452 #13]  INFO -- :
> I, [2017-12-22T13:00:13.036017 #13]  INFO -- : > rm -fr /shared/postgres_run/.s*
> I, [2017-12-22T13:00:13.038472 #13]  INFO -- :
> I, [2017-12-22T13:00:13.038949 #13]  INFO -- : > rm -fr /shared/postgres_run/*.pid
> I, [2017-12-22T13:00:13.040694 #13]  INFO -- :
> I, [2017-12-22T13:00:13.041019 #13]  INFO -- : > mkdir -p /shared/postgres_run/9.5-main.pg_stat_tmp
> I, [2017-12-22T13:00:13.042900 #13]  INFO -- :
> I, [2017-12-22T13:00:13.043268 #13]  INFO -- : > chown postgres:postgres /shared/postgres_run/9.5-main.pg_stat_tmp
> I, [2017-12-22T13:00:13.044726 #13]  INFO -- :
> I, [2017-12-22T13:00:13.047651 #13]  INFO -- : File > /etc/service/postgres/run  chmod: +x
> I, [2017-12-22T13:00:13.050449 #13]  INFO -- : File > /etc/runit/3.d/99-postgres  chmod: +x
> I, [2017-12-22T13:00:13.053097 #13]  INFO -- : File > /root/upgrade_postgres  chmod: +x
> I, [2017-12-22T13:00:13.053607 #13]  INFO -- : > chown -R root /var/lib/postgresql/9.5/main
> I, [2017-12-22T13:00:46.807963 #13]  INFO -- :
> I, [2017-12-22T13:00:46.808667 #13]  INFO -- : > [ ! -e /shared/postgres_data ] && install -d -m 0755 -o postgres -g postgres /shared/postgres_data && sudo     -E -u postgres /usr/lib/postgresql/9.5/bin/initdb -D /shared/postgres_data || exit 0
>
> WARNING: enabling "trust" authentication for local connections
> You can change this by editing pg_hba.conf or using the option -A, or
> --auth-local and --auth-host, the next time you run initdb.
> I, [2017-12-22T13:01:09.907790 #13]  INFO -- : The files belonging to this database system will be owned by user "postgres".
> This user must also own the server process.
>
> The database cluster will be initialized with locale "en_US.UTF-8".
> The default database encoding has accordingly been set to "UTF8".
> The default text search configuration will be set to "english".
>
> Data page checksums are disabled.
>
> fixing permissions on existing directory /shared/postgres_data ... ok
> creating subdirectories ... ok
> selecting default max_connections ... 100
> selecting default shared_buffers ... 128MB
> selecting dynamic shared memory implementation ... posix
> creating configuration files ... ok
> creating template1 database in /shared/postgres_data/base/1 ... ok
> initializing pg_authid ... ok
> initializing dependencies ... ok
> creating system views ... ok
> loading system objects' descriptions ... ok
> creating collations ... ok
> creating conversions ... ok
> creating dictionaries ... ok
> setting privileges on built-in objects ... ok
> creating information schema ... ok
> loading PL/pgSQL server-side language ... ok
> vacuuming database template1 ... ok
> copying template1 to template0 ... ok
> copying template1 to postgres ... ok
> syncing data to disk ... ok
>
> Success. You can now start the database server using:
>
>     /usr/lib/postgresql/9.5/bin/pg_ctl -D /shared/postgres_data -l logfile start
>
>
> I, [2017-12-22T13:01:09.908294 #13]  INFO -- : > chown -R postgres:postgres /shared/postgres_data
> I, [2017-12-22T13:01:09.913023 #13]  INFO -- :
> I, [2017-12-22T13:01:09.913294 #13]  INFO -- : > chown -R postgres:postgres /var/run/postgresql
> I, [2017-12-22T13:01:09.914904 #13]  INFO -- :
> I, [2017-12-22T13:01:09.915405 #13]  INFO -- : > /root/upgrade_postgres
> I, [2017-12-22T13:01:09.922011 #13]  INFO -- :
> I, [2017-12-22T13:01:09.922148 #13]  INFO -- : > rm /root/upgrade_postgres
> I, [2017-12-22T13:01:09.923561 #13]  INFO -- :
> I, [2017-12-22T13:01:09.935796 #13]  INFO -- : Replacing data_directory = '/var/lib/postgresql/9.5/main' with data_directory = '/shared/postgres_data' in /e    tc/postgresql/9.5/main/postgresql.conf
> I, [2017-12-22T13:01:09.936458 #13]  INFO -- : Replacing (?-mix:#?listen_addresses *=.*) with listen_addresses = '*' in /etc/postgresql/9.5/main/postgresql.    conf
> I, [2017-12-22T13:01:09.937059 #13]  INFO -- : Replacing (?-mix:#?synchronous_commit *=.*) with synchronous_commit = $db_synchronous_commit in /etc/postgres    ql/9.5/main/postgresql.conf
> I, [2017-12-22T13:01:09.937693 #13]  INFO -- : Replacing (?-mix:#?shared_buffers *=.*) with shared_buffers = $db_shared_buffers in /etc/postgresql/9.5/main/    postgresql.conf
> I, [2017-12-22T13:01:09.938139 #13]  INFO -- : Replacing (?-mix:#?work_mem *=.*) with work_mem = $db_work_mem in /etc/postgresql/9.5/main/postgresql.conf
> I, [2017-12-22T13:01:09.938725 #13]  INFO -- : Replacing (?-mix:#?default_text_search_config *=.*) with default_text_search_config = '$db_default_text_searc    h_config' in /etc/postgresql/9.5/main/postgresql.conf
> I, [2017-12-22T13:01:09.939137 #13]  INFO -- : > install -d -m 0755 -o postgres -g postgres /shared/postgres_backup
> I, [2017-12-22T13:01:09.940865 #13]  INFO -- :
> I, [2017-12-22T13:01:09.941298 #13]  INFO -- : Replacing (?-mix:#?max_wal_senders *=.*) with max_wal_senders = $db_max_wal_senders in /etc/postgresql/9.5/ma    in/postgresql.conf
> I, [2017-12-22T13:01:09.985283 #13]  INFO -- : Replacing (?-mix:#?wal_level *=.*) with wal_level = $db_wal_level in /etc/postgresql/9.5/main/postgresql.conf
> I, [2017-12-22T13:01:09.985867 #13]  INFO -- : Replacing (?-mix:#?checkpoint_segments *=.*) with checkpoint_segments = $db_checkpoint_segments in /etc/postg    resql/9.5/main/postgresql.conf
> I, [2017-12-22T13:01:09.986271 #13]  INFO -- : Replacing (?-mix:#?logging_collector *=.*) with logging_collector = $db_logging_collector in /etc/postgresql/    9.5/main/postgresql.conf
> I, [2017-12-22T13:01:09.987022 #13]  INFO -- : Replacing (?-mix:#?log_min_duration_statement *=.*) with log_min_duration_statement = $db_log_min_duration_st    atement in /etc/postgresql/9.5/main/postgresql.conf
> I, [2017-12-22T13:01:09.987708 #13]  INFO -- : Replacing (?-mix:^#local +replication +postgres +peer$) with local replication postgres  peer in /etc/postgre    sql/9.5/main/pg_hba.conf
> I, [2017-12-22T13:01:09.988084 #13]  INFO -- : Replacing (?-mix:^host.*all.*all.*127.*$) with host all all 0.0.0.0/0 md5 in /etc/postgresql/9.5/main/pg_hba.    conf
> I, [2017-12-22T13:01:09.988661 #13]  INFO -- : > HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-ce    rt /usr/lib/postgresql/9.5/bin/postmaster -D /etc/postgresql/9.5/main
> I, [2017-12-22T13:01:09.990125 #13]  INFO -- : > sleep 5
> LOG:  0 is outside the valid range for parameter "shared_buffers" (16 .. 1073741823)
> 2017-12-22 13:01:10.049 UTC [83] FATAL:  configuration file "/etc/postgresql/9.5/main/postgresql.conf" contains errors
> I, [2017-12-22T13:01:15.040397 #13]  INFO -- :
> I, [2017-12-22T13:01:15.040609 #13]  INFO -- : > su postgres -c 'createdb discourse' || true
> createdb: could not connect to database template1: could not connect to server: No such file or directory
>         Is the server running locally and accepting
>         connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
> I, [2017-12-22T13:01:15.841364 #13]  INFO -- :
> I, [2017-12-22T13:01:15.841746 #13]  INFO -- : > su postgres -c 'psql discourse -c "create user discourse;"' || true
> psql: could not connect to server: No such file or directory
>         Is the server running locally and accepting
>         connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
> I, [2017-12-22T13:01:16.236829 #13]  INFO -- :
> I, [2017-12-22T13:01:16.237220 #13]  INFO -- : > su postgres -c 'psql discourse -c "grant all privileges on database discourse to discourse;"' || true
> psql: could not connect to server: No such file or directory
>         Is the server running locally and accepting
>         connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
> I, [2017-12-22T13:01:16.285438 #13]  INFO -- :
> I, [2017-12-22T13:01:16.285877 #13]  INFO -- : > su postgres -c 'psql discourse -c "alter schema public owner to discourse;"'
> psql: could not connect to server: No such file or directory
>         Is the server running locally and accepting
>         connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
> I, [2017-12-22T13:01:16.333852 #13]  INFO -- :
> I, [2017-12-22T13:01:16.334299 #13]  INFO -- : Terminating async processes
>
>
> FAILED
> --------------------
> Pups::ExecError: su postgres -c 'psql discourse -c "alter schema public owner to discourse;"' failed with return #<Process::Status: pid 109 exit 2>
> Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
> exec failed with the params "su postgres -c 'psql $db_name -c \"alter schema public owner to $db_user;\"'"
> ba599d5a146a5773965191aea5bae886b3b9dca2afe21f165c5faec664b0ca9d
> ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

Posts: 8

Participants: 4

Read full topic

@Jean-Michel25 wrote:

Hello

Many time to read topics, but I cannot undestand how to do.
Maybe you can help me ?

We installed a Discourse forum on OVH VPS, subdomain of our site (forum.mysite.com)

Old users will be imported into Discourse Forum.
New users will create account by Discourse Forum.
All users will sign on with Discourse.
OK

Our main site (www.mysite.com) is PHP/MySQL.
My php pages have to know if the user is logged, his username, his group.
How to do ?
I can create PHP scripts, but I don’t know Ruby.

Maybe read session (cookie) ?

I found this but cannot find what to do with :

Your help is welcome.
Discourse is new for me…

Many thanks

Posts: 12

Participants: 3

Read full topic

@jordan1909 wrote:

I am using webhooks as I’ve mentioned in other threads here.

I’ve noticed a bug however in this and I’d like to understand if its by design or other.

On our install we use moderator approval on posts if the TL is 2 or less. In my testing however I have noticed that with this feature enabled, the webhooks on post or topic actions do not fire 99.9% of the time.

The biggest confusion for me is a few randomly fire but the bulk majority do not. I could potentially wrap my head around all not going or all going but a few here or there going and the rest not is confusing me.

Can anyone think of a reason webhooks wouldn’t fire when we approve moderated posts? I’ve tried all variations including send me everything to no success.

Posts: 3

Participants: 3

Read full topic

@communitygal wrote:

In the admin console, I have gone to Customize- > Email templates and would like to send one of the templates as a welcome.

How can I adjust the settings for different templates? For example, sending a welcome template to users after they join.

I checked the sent emails and I have noticed that my users have only received signup, digest, user posted, user mentioned.

Thanks,
Emma

Posts: 2

Participants: 2

Read full topic

@fwielstra wrote:

I’ve been trying to import my vBulletin forum into Discourse for a while now. I’ve been following this guide: Importing from vBulletin 4.

I’m running the product on my Macbook using the Vagrant image as described on discourse/VAGRANT.md at master · discourse/discourse · GitHub.

I’ve managed to finish the main database import after about 56 hours (~750K posts, ~10K users), but I’m running into trouble in the sidekiq task. It’s queued up 2 million tasks, and while it starts off right (cpu usage of the host going to 400%), it seems to just lock up after a while; host CPU usage is at exactly 100%, and the Vagrant image becomes unresponsive - can’t exit the main discourse process, can’t exit Sidekiq, and htop (which I had also running in screen) was just as unresponsible.

I’ve run it again, this time not starting the main Discourse process and having htop in the foreground. It’s done it again, this is the last what I can see in htop:

image.png3360x2004 848 KB

Nothing major, just a lot of processes running at low speeds, not even high CPU usage, but it’s still frozen.

Is this an issue in the software somewhere, or is this a known problem when running in Vagrant? Should I just get the whole thing set up locally? Or are there tricks to making this work?

Some technical details: Virtualbox gets access to 8 CPUs (autodetected by vagrant; I have 4 physical cpu cores, 8 with hyperthreading) and 4 GB of memory, a late 2013 model Macbook Pro. I’ve tweaked the database and sidekiq settings so that the DB has a pool of 25 and sidekiq a parallelism of 10 (-c argument).

It looks like it’s in a deadlock of sorts.

I’m running the HEAD commit of the main discourse repo, commit b963307 from about a week ago.

Any configuration tweaks I can do to help fix this?

Posts: 2

Participants: 2

Read full topic

@Zelakto wrote:

Hi there,

Recently, a user complained to me about not being able to create an account due to there being too many accounts registered for that IP address. Turns out, this was because I was running my Discourse forum on the standard 80 and 443 ports, however it I was running Discourse through Cloudflare’s proxy (to get SSL and what not). A fix for this would be to use NGINX to reverse proxy Discourse, and use the “realip” module that NGINX has to offer, which allows Discourse to see real user IPs, and not Cloudflares regional IP addresses due to the proxy.

Everything works great! However there’s one small problem. When replying or creating a topic, Discourse seems to throw an error in the console when trying to display the content preview for what you’re writing. The error is this:

Blocked loading mixed active content “http://community.phantombot.tv/assets/markdown-it-bundle-278dd87cca85c40ed9c85bff51af14639959f40df44b285fe0007619fc1be8e9.js” [Learn More] _ember_jquery-a8dcbd325e04410f036f2a791d66d8316c48c5387acdd914de99a5dd6afb3cd3.js:9248:4

Loading failed for the <script> with source “http://community.phantombot.tv/assets/markdown-it-bundle-278dd87cca85c40ed9c85bff51af14639959f40df44b285fe0007619fc1be8e9.js”.

If you’re curious, here’s my configuration for NGINX while running this setup:

server {
        listen 80;
        listen [::]:80;

        server_name community.phantombot.tv;

        location / {
         proxy_pass http://127.0.0.1:8080;
         include proxy_params;
         proxy_http_version 1.1;
        set_real_ip_from 103.21.244.0/22;
        set_real_ip_from 103.22.200.0/22;
        set_real_ip_from 103.31.4.0/22;
        set_real_ip_from 104.16.0.0/12;
        set_real_ip_from 108.162.192.0/18;
        set_real_ip_from 131.0.72.0/22;
        set_real_ip_from 141.101.64.0/18;
        set_real_ip_from 162.158.0.0/15;
        set_real_ip_from 172.64.0.0/13;
        set_real_ip_from 173.245.48.0/20;
        set_real_ip_from 188.114.96.0/20;
        set_real_ip_from 190.93.240.0/20;
        set_real_ip_from 197.234.240.0/22;
        set_real_ip_from 198.41.128.0/17;
        set_real_ip_from 2400:cb00::/32;
        set_real_ip_from 2606:4700::/32;
        set_real_ip_from 2803:f800::/32;
        set_real_ip_from 2405:b500::/32;
        set_real_ip_from 2405:8100::/32;
        set_real_ip_from 2c0f:f248::/32;
        set_real_ip_from 2a06:98c0::/29;

        # use any of the following two
        real_ip_header CF-Connecting-IP;
        #real_ip_header X-Forwarded-For;
    }
}

I tried to find a solution for this, such as installing Let’s Encrypt on the server and using both that, and Cloudflare’s cert together. Here is the NGINX configuration for that:

server {
        listen 80;
        server_name community.phantombot.tv;
        return 301 https://community.phantombot.tv$request_uri;
}

server {
        listen 443 ssl spdy;
        server_name community.phantombot.tv;
        ssl_certificate /etc/letsencrypt/live/community.phantombot.tv/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/community.phantombot.tv/privkey.pem;
        ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
        ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA$
        ssl_prefer_server_ciphers on;
        location / {
                proxy_pass      http://127.0.0.1:8080/;
                proxy_read_timeout      90;
                proxy_redirect  http://127.0.0.1:8080/ https://community.phantombot.tv;
        }
}

For the last proxy_pass and proxy_redirect options, I tried using http://community.phantombot.tv:8080/ for both, but it refuses to work.

Doing things this way seems to fixed the Mixed Content error, however, the script for previewing markdown still doesn’t work. It results in this error:

Loading failed for the <script> with source "http://127.0.0.1:8080/assets/markdown-it-bundle-278dd87cca85c40ed9c85bff51af14639959f40df44b285fe0007619fc1be8e9.js".

Is there something I’m doing wrong here? I’d love to get this running, if not, it’s not too big of a loss. Thank you!

Posts: 1

Participants: 1

Read full topic

@Tsirist wrote:

I recently tried to update Discourse via the Docker Manager plugin’s interface but have run into some problems.

Initially, Discourse was running but there were updates available, and it had been a month or two since I’d updated. First I updated Docker from Docker Manager, which worked fine. Then I tried to update Discourse. I believe the log opened with a message about bundle being out-of-date, but eventually the entire site became unresponsive to web requests and the Docker Manager web interface stopped responding too, so I couldn’t tell whether something had gone wrong from there. I decided to just update the system and restart everything to start fresh.

Unfortunately this did not fix the issue, as the site became unresponsive again. It wasn’t immediate though. When it came back up I believe I tried to update some of the other plugins, but after it stopped responding again I decided to just rebuild the app.

This is about where I am now. I’ve tried some other things but they haven’t yielded much success. With the latest rebuilt/restarted app, the site works momentarily (topics are accessible, posts can be written, etc.), but after a minute or two the site stops responding. The server health looks fine as far as I can tell. Here is a summary during the brief period of availability for the web interface.

top - 15:48:40 up  7:36,  1 user,  load average: 1.94, 0.80, 0.38
Tasks: 139 total,   3 running, 136 sleeping,   0 stopped,   0 zombie
%Cpu(s): 60.0 us, 12.5 sy,  0.0 ni, 25.0 id,  1.2 wa,  0.0 hi,  1.2 si,  0.0 st
MiB Mem : 2000.180 total,   77.324 free, 1003.438 used,  919.418 buff/cache
MiB Swap: 2047.996 total, 2010.887 free,   37.109 used.  719.566 avail Mem

And here it is after the site has become unresponsive.

top - 15:52:05 up  7:40,  1 user,  load average: 0.61, 0.70, 0.42
Tasks: 143 total,   2 running, 141 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.7 us,  0.8 sy,  0.0 ni, 98.3 id,  0.0 wa,  0.0 hi,  0.2 si,  0.0 st
MiB Mem : 2000.180 total,  131.539 free, 1021.273 used,  847.367 buff/cache
MiB Swap: 2047.996 total, 2003.777 free,   44.219 used.  660.539 avail Mem

Here’s a ps -aux dump where my username is “tmpname”:

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.1  37912  2528 ?        Ss   08:11   0:04 /sbin/init
root         2  0.0  0.0      0     0 ?        S    08:11   0:00 [kthreadd]
root         3  0.0  0.0      0     0 ?        S    08:11   0:01 [ksoftirqd/0]
root         5  0.0  0.0      0     0 ?        S<   08:11   0:00 [kworker/0:0H]
root         7  0.0  0.0      0     0 ?        S    08:11   0:14 [rcu_sched]
root         8  0.0  0.0      0     0 ?        S    08:11   0:00 [rcu_bh]
root         9  0.0  0.0      0     0 ?        S    08:11   0:00 [migration/0]
root        10  0.0  0.0      0     0 ?        S    08:11   0:00 [watchdog/0]
root        11  0.0  0.0      0     0 ?        S    08:11   0:00 [watchdog/1]
root        12  0.0  0.0      0     0 ?        S    08:11   0:00 [migration/1]
root        13  0.0  0.0      0     0 ?        S    08:11   0:01 [ksoftirqd/1]
root        15  0.0  0.0      0     0 ?        S<   08:11   0:00 [kworker/1:0H]
root        16  0.0  0.0      0     0 ?        S    08:11   0:00 [kdevtmpfs]
root        17  0.0  0.0      0     0 ?        S<   08:11   0:00 [netns]
root        18  0.0  0.0      0     0 ?        S<   08:11   0:00 [perf]
root        19  0.0  0.0      0     0 ?        S    08:11   0:00 [khungtaskd]
root        20  0.0  0.0      0     0 ?        S<   08:11   0:00 [writeback]
root        21  0.0  0.0      0     0 ?        SN   08:11   0:00 [ksmd]
root        22  0.0  0.0      0     0 ?        SN   08:11   0:04 [khugepaged]
root        23  0.0  0.0      0     0 ?        S<   08:11   0:00 [crypto]
root        24  0.0  0.0      0     0 ?        S<   08:11   0:00 [kintegrityd]
root        25  0.0  0.0      0     0 ?        S<   08:11   0:00 [bioset]
root        26  0.0  0.0      0     0 ?        S<   08:11   0:00 [kblockd]
root        27  0.0  0.0      0     0 ?        S<   08:11   0:00 [ata_sff]
root        28  0.0  0.0      0     0 ?        S<   08:11   0:00 [md]
root        29  0.0  0.0      0     0 ?        S<   08:11   0:00 [devfreq_wq]
root        33  0.1  0.0      0     0 ?        S    08:11   0:28 [kswapd0]
root        34  0.0  0.0      0     0 ?        S<   08:11   0:00 [vmstat]
root        35  0.0  0.0      0     0 ?        S    08:11   0:00 [fsnotify_mark]
root        36  0.0  0.0      0     0 ?        S    08:11   0:00 [ecryptfs-kthrea]
root        52  0.0  0.0      0     0 ?        S<   08:11   0:00 [kthrotld]
root        53  0.0  0.0      0     0 ?        S<   08:11   0:00 [acpi_thermal_pm]
root        54  0.0  0.0      0     0 ?        S    08:11   0:00 [vballoon]
root        55  0.0  0.0      0     0 ?        S<   08:11   0:00 [bioset]
root        56  0.0  0.0      0     0 ?        S<   08:11   0:00 [bioset]
root        57  0.0  0.0      0     0 ?        S<   08:11   0:00 [bioset]
root        58  0.0  0.0      0     0 ?        S<   08:11   0:00 [bioset]
root        59  0.0  0.0      0     0 ?        S<   08:11   0:00 [bioset]
root        60  0.0  0.0      0     0 ?        S<   08:11   0:00 [bioset]
root        61  0.0  0.0      0     0 ?        S<   08:11   0:00 [bioset]
root        62  0.0  0.0      0     0 ?        S<   08:11   0:00 [bioset]
root        63  0.0  0.0      0     0 ?        S<   08:11   0:00 [bioset]
root        64  0.0  0.0      0     0 ?        S    08:11   0:00 [scsi_eh_0]
root        65  0.0  0.0      0     0 ?        S<   08:11   0:00 [scsi_tmf_0]
root        66  0.0  0.0      0     0 ?        S    08:11   0:00 [scsi_eh_1]
root        67  0.0  0.0      0     0 ?        S<   08:11   0:00 [scsi_tmf_1]
root        73  0.0  0.0      0     0 ?        S<   08:11   0:00 [ipv6_addrconf]
root        86  0.0  0.0      0     0 ?        S<   08:11   0:00 [deferwq]
root        87  0.0  0.0      0     0 ?        S<   08:11   0:00 [charger_manager]
root       124  0.0  0.0      0     0 ?        S<   08:11   0:00 [bioset]
root       125  0.0  0.0      0     0 ?        S<   08:11   0:00 [bioset]
root       126  0.0  0.0      0     0 ?        S<   08:11   0:00 [bioset]
root       127  0.0  0.0      0     0 ?        S<   08:11   0:00 [bioset]
root       128  0.0  0.0      0     0 ?        S<   08:11   0:00 [bioset]
root       129  0.0  0.0      0     0 ?        S<   08:11   0:00 [bioset]
root       130  0.0  0.0      0     0 ?        S<   08:11   0:00 [bioset]
root       131  0.0  0.0      0     0 ?        S<   08:11   0:00 [bioset]
root       132  0.0  0.0      0     0 ?        S    08:11   0:00 [scsi_eh_2]
root       133  0.0  0.0      0     0 ?        S<   08:11   0:00 [kpsmoused]
root       134  0.0  0.0      0     0 ?        S<   08:11   0:00 [scsi_tmf_2]
root       135  0.0  0.0      0     0 ?        S<   08:11   0:00 [ttm_swap]
root       136  0.0  0.0      0     0 ?        S<   08:11   0:00 [qxl_gc]
root       413  0.0  0.0      0     0 ?        S    08:11   0:02 [jbd2/vda1-8]
root       414  0.0  0.0      0     0 ?        S<   08:11   0:00 [ext4-rsv-conver]
root       455  0.0  0.0      0     0 ?        S<   08:11   0:00 [kworker/0:1H]
root       456  0.0  0.1  29648  2772 ?        Ss   08:11   0:05 /lib/systemd/systemd-journald
root       479  0.0  0.0      0     0 ?        S    08:11   0:00 [kauditd]
root       495  0.0  0.0  44432  1412 ?        Ss   08:11   0:00 /lib/systemd/systemd-udevd
root       532  0.0  0.0      0     0 ?        S<   08:11   0:00 [kworker/1:1H]
systemd+   627  0.0  0.0 100324   388 ?        Ssl  08:11   0:00 /lib/systemd/systemd-timesyncd
root       750  0.0  0.0      0     0 ?        S<   08:11   0:00 [kvm-irqfd-clean]
root       991  0.0  0.0   4400    80 ?        Ss   08:12   0:00 /usr/sbin/acpid
root       997  0.0  0.0  65520   816 ?        Ss   08:12   0:01 /usr/sbin/sshd -D
root      1004  0.0  0.0  29880   220 ?        Ss   08:12   0:00 /sbin/cgmanager -m name=systemd
syslog    1008  0.0  0.0 256396    84 ?        Ssl  08:12   0:01 /usr/sbin/rsyslogd -n
root      1012  0.0  0.0 275872  1456 ?        Ssl  08:12   0:02 /usr/lib/accountsservice/accounts-daemon
root      1015  0.0  0.0  29008   580 ?        Ss   08:12   0:00 /usr/sbin/cron -f
message+  1020  0.0  0.0  42900   856 ?        Ss   08:12   0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activati
daemon    1030  0.0  0.0  26044   196 ?        Ss   08:12   0:00 /usr/sbin/atd -f
root      1031  0.0  0.0  28620  1784 ?        Ss   08:12   0:00 /lib/systemd/systemd-logind
root      1038  0.5  1.3 530876 27212 ?        Ssl  08:12   2:24 /usr/bin/dockerd -H fd://
root      1068  0.0  0.0  19472   104 ?        Ss   08:12   0:01 /usr/sbin/irqbalance --pid=/var/run/irqbalance.pid
root      1075  0.0  0.0 277088   696 ?        Ssl  08:12   0:00 /usr/lib/policykit-1/polkitd --no-debug
root      1091  0.0  0.0  15940   144 tty1     Ss+  08:12   0:00 /sbin/agetty --noclear tty1 linux
root      1095  0.1  0.6 383184 13932 ?        Ssl  08:12   0:52 docker-containerd --config /var/run/docker/containerd/containerd.toml
root     14580  0.0  0.0      0     0 ?        S    15:00   0:01 [kworker/u4:1]
root     18499  0.0  0.0      0     0 ?        S    15:07   0:00 [kworker/1:3]
root     20792  0.0  0.1  99512  3544 ?        Ss   15:35   0:00 sshd: tmpname [priv]
tmpname  20812  0.0  0.1  45248  2196 ?        Ss   15:36   0:00 /lib/systemd/systemd --user
root     20814  0.0  0.0      0     0 ?        S    15:36   0:00 [kworker/0:1]
tmpname  20816  0.0  0.0  63424  1156 ?        S    15:36   0:00 (sd-pam)
root     20818  0.0  0.0      0     0 ?        S    15:36   0:00 [kworker/1:1]
tmpname  20924  0.0  0.1  99512  2788 ?        S    15:36   0:00 sshd: tmpname@pts/0
tmpname  20925  0.0  0.2  24324  4964 pts/0    Ss   15:36   0:00 -bash
root     20957  0.0  0.1  56836  2212 pts/0    S    15:36   0:00 sudo bash
root     20958  0.0  0.2  24176  5636 pts/0    S    15:36   0:00 bash
root     21690  0.0  0.0      0     0 ?        S    15:45   0:00 [kworker/0:2]
root     21797  0.0  0.0      0     0 ?        S    15:45   0:00 [kworker/u4:0]
root     23189  0.0  0.0  50872  1548 ?        Sl   15:47   0:00 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 443 -container-ip 172.17.0.
root     23201  0.0  0.2  50872  5624 ?        Sl   15:47   0:00 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 80 -container-ip 172.17.0.2
root     23207  0.0  0.2 233780  5256 ?        Sl   15:47   0:00 docker-containerd-shim --namespace moby --workdir /var/lib/docker/containerd/daemon/io.c
root     23224  0.0  0.0  21288  1220 pts/0    Ss+  15:47   0:00 /bin/bash /sbin/boot
root     23521  0.0  0.0   4396   940 pts/0    S+   15:47   0:00 /usr/bin/runsvdir -P /etc/service
root     23522  0.0  0.0   4244   400 ?        Ss   15:47   0:00 runsv cron
root     23523  0.0  0.0   4244   404 ?        Ss   15:47   0:00 runsv nginx
root     23524  0.0  0.0   4244   452 ?        Ss   15:47   0:00 runsv postgres
root     23525  0.0  0.0   4244   416 ?        Ss   15:47   0:00 runsv unicorn
root     23526  0.0  0.0   4244   372 ?        Ss   15:47   0:00 runsv redis
root     23527  0.0  0.1  82724  3284 ?        S    15:47   0:00 nginx: master process /usr/sbin/nginx
root     23528  0.0  0.0  29300  1232 ?        S    15:47   0:00 cron -f
root     23529  0.0  0.0   4244   404 ?        Ss   15:47   0:00 runsv rsyslog
systemd+ 23530  0.0  0.7 295044 15104 ?        S    15:47   0:00 /usr/lib/postgresql/9.5/bin/postmaster -D /etc/postgresql/9.5/main
systemd+ 23531  0.0  0.0 182664  1240 ?        Sl   15:47   0:00 rsyslogd -n
_apt     23533  2.1 10.9 261612 224668 ?       Sl   15:47   0:06 /usr/bin/redis-server *:6379
www-data 23543  0.1  0.2  84500  5228 ?        S    15:47   0:00 nginx: worker process
www-data 23544  0.2  0.2  84444  5064 ?        S    15:47   0:00 nginx: worker process
www-data 23545  0.0  0.0  82892  1640 ?        S    15:47   0:00 nginx: cache manager process
systemd+ 23549  0.0  0.2 295148  4600 ?        Ss   15:47   0:00 postgres: 9.5/main: checkpointer process
systemd+ 23550  0.0  0.6 295044 13636 ?        Ss   15:47   0:00 postgres: 9.5/main: writer process
systemd+ 23551  0.0  0.3 295044  6432 ?        Ss   15:47   0:00 postgres: 9.5/main: wal writer process
systemd+ 23552  0.0  0.1 295472  3620 ?        Ss   15:47   0:00 postgres: 9.5/main: autovacuum launcher process
systemd+ 23553  0.0  0.1 150348  2368 ?        Ss   15:47   0:00 postgres: 9.5/main: stats collector process
tmpname  23684  0.2  0.1  29900  4092 ?        S    15:47   0:00 /bin/bash config/unicorn_launcher -E production -c config/unicorn.conf.rb
tmpname  23689  6.3  7.9 472664 163784 ?       Sl   15:47   0:17 unicorn master -E production -c config/unicorn.conf.rb
tmpname  23780  0.8  8.5 516740 174604 ?       Sl   15:48   0:02 sidekiq 5.0.5 discourse [0 of 5 busy]
systemd+ 23787 11.8  7.3 315760 149940 ?       Ss   15:48   0:29 postgres: 9.5/main: discourse discourse [local] UPDATE
systemd+ 24034  0.2  2.6 309200 54172 ?        Ss   15:48   0:00 postgres: 9.5/main: discourse discourse [local] SELECT
systemd+ 24068  0.8  7.2 313480 149440 ?       Ss   15:48   0:02 postgres: 9.5/main: discourse discourse [local] idle
systemd+ 24295  0.4  7.2 309404 149224 ?       Ss   15:49   0:00 postgres: 9.5/main: discourse discourse [local] SELECT
systemd+ 24402  0.0  2.3 308764 48828 ?        Ss   15:49   0:00 postgres: 9.5/main: discourse discourse [local] SELECT
systemd+ 24693  0.6  6.7 307392 139276 ?       Ss   15:50   0:00 postgres: 9.5/main: discourse discourse [local] SELECT
systemd+ 24710  1.2  7.8 325556 160096 ?       Ss   15:50   0:01 postgres: 9.5/main: discourse discourse [local] SELECT
systemd+ 24904  0.0  1.0 302932 20832 ?        Ss   15:51   0:00 postgres: 9.5/main: discourse discourse [local] UPDATE waiting
systemd+ 25045  0.0  1.1 303176 23092 ?        Ss   15:51   0:00 postgres: 9.5/main: discourse discourse [local] UPDATE waiting
systemd+ 25210  0.7  3.6 305964 74032 ?        Ss   15:51   0:00 postgres: 9.5/main: discourse discourse [local] SELECT
systemd+ 25213  0.0  0.9 303100 19800 ?        Ss   15:51   0:00 postgres: 9.5/main: discourse discourse [local] idle
tmpname  25218 22.5 14.6 1688000 300012 ?      Sl   15:51   0:07 unicorn worker[0] -E production -c config/unicorn.conf.rb
systemd+ 25345  0.4  2.0 306012 41032 ?        Ss   15:51   0:00 postgres: 9.5/main: discourse discourse [local] UPDATE waiting
tmpname  25378  101 14.4 1679772 295916 ?      Sl   15:52   0:06 unicorn worker[1] -E production -c config/unicorn.conf.rb
root     25394  0.0  0.0      0     0 ?        S    15:52   0:00 [kworker/u4:2]
tmpname  25494  0.0  0.1  20148  3480 ?        S    15:52   0:00 sleep 1
root     25495  0.0  0.1  37364  3216 pts/0    R+   15:52   0:00 ps -aux

I’ve tried rebuilding with a couple different configurations. One of the first things I tried was just disabling all plugins in containers/app.yml. I tried this with the latest Discourse version as well as in combination with specifying an older Discourse version to use in the same file. Unfortunately, while I think both have some effect prolonging the life of the web interface to a half-hour or an hour, they don’t solve the problem. However, I’ve noticed that with one version of Discourse from October, the interface would work, but topics would be inaccessible, so I’m not sure how reliable this information is. Interface lifetime with the default configuration is somewhat variable anyways, but tends to be from 1 to 5 minutes.

Discourse admin logs on web interface don’t show any fatal errors in the time it’s up, but I’d love to know how to check from within the container proper if it would help.

Does anyone have any idea what may be happening or what else I could throw at the wall to try and solve it? If more info would be useful I’d be happy to provide it.

Posts: 6

Participants: 2

Read full topic

@PatrickH wrote:

Hello,

It seems that my topic layout is different, please see image.
What can i do to change this to the current one ?

image.png1586x508 32.9 KB

Posts: 4

Participants: 3

Read full topic

@tobiaseigen wrote:

Hi @LeoMcA! I love this query of yours that you created last year to use the data explorer to display a chronological list of user topics started, replied and liked. Would you be willing to update the query to also optionally include user custom fields in the results? It would be a big help to me right now.

Trust all is well. Happy holidays!

Posts: 1

Participants: 1

Read full topic

@Biscuit wrote:

If you search for a specific user and reveal their email address, it shows just their email address and mentions this in the logs. That’s fine.

Now, if you need to lookup another user and use the search box on the same screen, if multiple users are in the results, they all appear with their personal email address showing. And the logs mention that multiple email addresses were looked up.

In summary:

Intention - Look up two individual email addresses.

Actual Results

1. Logs show that many addresses were looked up.
2. Multiple users had their personal emails displayed unnecessarily.

Suggestions

1. Searching for user(s) should turn off “show email address” before completing the search.
2. “Check email” in the logs should say “Check email address” as it currently incorrectly implies reading of PMs. This was raised by someone in an earlier thread, but it’s still misleading.

Posts: 2

Participants: 2

Read full topic

@Biscuit wrote:

It appears that Moderators are unable to correct poll results.

This means an important forum poll can easily be compromised by one or more forum members using inappropriate accounts to vote. It’s frustrating to know with certainty that specific votes are invalid, but to be unable to remove them. As a result, the votes, totals, percentages and positions within the poll may all be displayed incorrectly for the remainder of the polls life.

Current workaround

• Use your own votes to correct if possible (can do this once).
• Apologuise within the poll thread and explain that the poll totals above are incorrect.

Suggestions:

• Allow moderators / Admins to edit votes, but specify when that option has been set and/or used.
• Optionally track any poll changes by staff, under the poll for transparency.

Posts: 1

Participants: 1

Read full topic

@AstonJ wrote:

Is this one still the best place to start? (It’s from 2015)

To start with I just want to do something simple; have a ‘Spotlight’ feature to appear in our digest email but for the contents of the block to be randomly chosen (or cycled) from a group of possible spotlight articles (either per individual digest sent out, or rotated on an hourly or daily basis). They’d only be a single paragraph with a single image.

Which guides do you think are best suited to achieve this?

Any other tips (such as reading order of guides/threads) would also be appreciated

Posts: 3

Participants: 3

Read full topic

@Vu_Hoang wrote:

Hi guys,

I backup my website to the .tar.gz file, then my website was down and i deleted instances on Amazon.
Now, i transfer to use an instances on Linode. But how can i restore my website from .tar.gz file?

Pls help me to do this.
Many thanks!

Posts: 2

Participants: 2

Read full topic

@lll wrote:

Beta testers needed for Vincent theme.

repo:

GitHub - hnb-ku/discourse-vincent-theme: v0.4 beta

Compressed Screenshots:

will look much better on your screen, image compression cases artifacts / blur

Homepage

home.jpg2881x1626 448 KB

Topic page

post-desktop.jpg2890x1631 451 KB

Topic replies

replies .jpg2458x1379 180 KB

---

Give it a spin for a few minutes, kindly report any issues here.

Don’t forget to set the color scheme to “Vincent Dark”

---

Ideas, tips, critique welcome

Posts: 1

Participants: 1

Read full topic

@appcomq wrote:

root@ubuntu:/var/discourse# ./launcher rebuild app
Ensuring launcher is up to date
Fetching origin
Launcher is up-to-date
cd /pups && git pull && /pups/bin/pups --stdin
fatal: unable to access 'https://github.com/SamSaffron/pups.git/': gnutls_handshake() failed: Error in the pull function.
19f5c0a33d1ecb80a73182c696b06016a0d3f4f37da34bd267dcab9a29887398
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

Posts: 2

Participants: 1

Read full topic

@mcwumbly wrote:

I’m starting to put together a curated, weekly “newsletter” on our forum, and thought I’d share something about it here.

The contents include:

• Links to a few of the best discussions from the past week.
• Sharing some high-level thoughts about things we can do to continue to improve the community.
• One or two tips about specific features of Discourse.

My aim is to publish a new topic like this once a week. The topic title is in the format with “Some Title - Sitename Weekly No. X”.

I just published the first issue with the title Making sitename more welcoming - First Issue! - Sitename Weekly No. 1. It is also tagged with #sitename-weekly so it will be easy to link to a list to all of the issues.

The section that links to existing topics looks kind of like this:

Interesting discussions

This week

You can always check out what Sitename thinks are the top discussions this week, but here are a few in particular that we’d like to highlight:

• What do you think about the new guidelines around email, Slack and Sitename usage?
  @SoAndSo started this discussion about the recent announcement sent by @OtherOne that we should use Slack instead of email for certain kinds of discussions, and Sitename for others. @NewFolk asked some insightful questions and @OG had some great ideas for refinements. Check it out and share your thoughts!

…2-4 more like that…

Pots of Gold

I occasionally come across some pots of gold at the end of the reading rainbow. Here’s one I found this week:

• How we stay effective when your team grows in size
  Before @OG was running this place, she was working on projects like many of us here. Check out this post from ~5 years ago where she shares some tips for organizing on project teams as they grow in size.

The tips are aligned with the theme for this issue, “Making sitename more welcoming”:

But who are all these people?

We want this to be an inclusive and safe space for all to participate openly in discussions about things that matter to them, their teams and the organization. People are here from every office and every role, and that’s cool, but it can also be confusing and intimidating, especially to newcomers, but also to many of us who day to day work in much smaller teams with people we are familiar with.

One thing we think can help make our community more welcoming is to make it easier to find out who someone is when you come across them here. So here are a couple tips:

TIP: Introduce yourself (Update your user info)

Take a couple minutes to go to your profile and add the following information:

On the account tab:

• Full Name
  Adding your full name makes it easier to connect who you are when we cross paths in othere places (like Slack) if you don’t use the same username. It also makes it easier to mention you.
• Profile Picture
  If your photo didn’t automatically load from gravatar, upload it here. Use the same photo you use in Gmail and Slack. It’ll make it a lot easier to recognize you across the variety of platforms we use to communicate.

On the your profile tab it’s helpful to update these fields too:

• Location
  Add your location so people know where you are. In addition to gaining a better sense of where we’re all from, it can help us understand who else you may work alongside (we might know some of them!).
• About me
  Include your role and what you’re working on. Add anything else you want too. It’s a great way to show a bit of your personality in brief. The field supports markdown, so you can add links to your twitter profile or blog too.

TIP: Click on a user’s avatar or when you see them @mentioned

If you’re not sure who someone is when you see a post of theirs here, click on their avatar and a user card will pop up that will have more information about them, depending on what they’ve filled out in their profile:

mcwumbly-user-card.jpg1168x618 304 KB

What do you think? Do you have other ideas to make Sitename more welcoming?

What do you think? Are there other things we should suggest people add to their profile? Is it worth investing in some integration with Workday?

This text is included in the footer, to remind people how they can follow along via email (and to subtly remind them of that feature in general):

---

If you want these to get delivered directly to your inbox, go to the #sitename-weekly tag and select “Watching First Post” in the upper right. (Or “Watching” if you also want to be notified about every reply).

Have feedback about this issue or the weekly updates in general? Let us know here or reach out to us in #sitename on Slack.

The reason I’m using a tag instead of a category is that I think there are a number of other groups within our organization that may see value in this pattern and so I’m hoping to model it in a way that allows those groups to autonomously create their own “publication” by following this process if this is successful.

Also, I realize there is some overlap with what gets sent out automatically as the weekly digest, but my hypothesis is that having a shared weekly issue that points out some content humans are specifically identifying, will engender a greater sense of belonging among those having those discussions.

I’ve only done one issue so far, but the feedback has been positive. I’ll try to follow up periodically on this topic to share how it evolves (and feel free to ask me if you have questions).

Posts: 1

Participants: 1

Read full topic

@mcwumbly wrote:

One of the best features of Discourse, vs. something like Slack, is that discussions can unfold over a long period of time. I love it when I see a thread that has laid dormant for 3 months revived with new thoughts and ideas while retaining the context of the earlier discussion.

In this new weekly newsletter I’m experimenting with, I’d love to be able to see a list of the top topics for the past week that includes older topics as long as they’ve had activity in the past week. Sometimes the best discussions in the past week were discussions taking place on older topics.

What do others think? Should /top include older topics with activity within the date range? Or continue to only list topics created within the selected date range?

Posts: 1

Participants: 1

Read full topic

@ashledombos wrote:

Hello :),

until now I had blog posts and comments embedded, all working perfectly.

It’s not working anymore, I can’t tell exactly since when (maybe two/three weeks) as I did not really paid attention to this part, but I did not change anything to the blog engine code.

Here is an URL example:

• Blog post
• Discourse topic automatically created

Though the url is https://www.openmandriva.org/en/news/article/eelo-mobile-os-and-web-services-by-gael-duval one can see this message in blog post:

Screenshot_20171223_222424.png1009x162 14.8 KB

The code generated in blog posts (for this example case):

<script type="text/javascript">
  DiscourseEmbed = { discourseUrl: 'https://forum.openmandriva.org/',
                      discourseEmbedUrl: 'https://www.openmandriva.org/en/news/article/eelo-mobile-os-and-web-services-by-gael-duval' };

  (function() {
    var d = document.createElement('script'); d.type = 'text/javascript'; d.async = true;
    d.src = DiscourseEmbed.discourseUrl + 'javascripts/embed.js';
    (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(d);
  })();
</script>

And my “allowed posts” configuration

Screenshot_20171223_223831.png1202x208 11.9 KB

I really don’t see what is wrong, and furthermore, it worked in the past…

Do you have any idea what could have happened?

Posts: 1

Participants: 1

Read full topic