Quantcast
Channel: Discourse Meta - Latest topics
Viewing all 60721 articles
Browse latest View live

Disqus Import error

$
0
0

@MZainDamlag wrote:

Hello All
I tried to run the disqus import script inside docker after some modification in the script and it run completely on development [local] and while I tried to run it inside docker

bundle exec ruby script/import_scripts/disqus.rb --file=disqus.xml --threads=threads.csv --users=users.csv --post_as=archived-user --category=9

I get this error:

URGENT: FATAL:  Peer authentication failed for user "discourse"
 Failed to initialize site default /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/connection_adapters/postgresql_adapter.rb:651:in `initialize': FATAL:  Peer authentication failed for user "discourse" (PG::ConnectionBad)

any help?

Posts: 3

Participants: 1

Read full topic


Getting Group members via API

Wrong activity data for new users

$
0
0

@CamilleRoux wrote:

Hi,

Here is the activity of a user who redeemed an invite 15 minutes ago:

The invite has been sent 4h ago. The 3 values seem to be wrong. I get the same problem on every new user.

Posts: 2

Participants: 2

Read full topic

Mails are no longer sent due to 'no_email_found' and 'message.to is blank'

$
0
0

@Sander78 wrote:

I noticed this in the mail log, first appearance three days ago. Could this be a commit that went wrong?

Posts: 4

Participants: 2

Read full topic

Mail by unknown user to group causes error

$
0
0

@Sander78 wrote:

Email can not be processed: PG::NotNullViolation: ERROR: null value in column "last_post_user_id" violates not-null constraint DETAIL: Failing row contains (796, Test 23:20, null, 20

and

Job exception: PG::NotNullViolation: ERROR: null value in column "last_post_user_id" violates not-null constraint DETAIL: Failing row contains (796, Test 23:20, null, 2016-02-02 22:20:28, 2016-02-02

Trace of the last error:

/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.8/lib/patches/db/pg.rb:90:in `exec'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.8/lib/patches/db/pg.rb:90:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/connection_adapters/postgresql_adapter.rb:592:in `block in exec_no_cache'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/connection_adapters/abstract_adapter.rb:472:in `block in log'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/connection_adapters/abstract_adapter.rb:466:in `log'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/connection_adapters/postgresql_adapter.rb:592:in `exec_no_cache'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/connection_adapters/postgresql_adapter.rb:584:in `execute_and_clear'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/connection_adapters/postgresql/database_statements.rb:160:in `exec_query'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/connection_adapters/postgresql/database_statements.rb:192:in `exec_insert'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/connection_adapters/abstract/database_statements.rb:108:in `insert'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/connection_adapters/abstract/query_cache.rb:14:in `insert'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/relation.rb:64:in `insert'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/persistence.rb:524:in `_create_record'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/counter_cache.rb:139:in `_create_record'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/locking/optimistic.rb:75:in `_create_record'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/attribute_methods/dirty.rb:132:in `_create_record'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/callbacks.rb:306:in `block in _create_record'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:778:in `_run_create_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/callbacks.rb:306:in `_create_record'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/timestamp.rb:57:in `_create_record'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/persistence.rb:504:in `create_or_update'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/callbacks.rb:302:in `block in create_or_update'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:778:in `_run_save_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/callbacks.rb:302:in `create_or_update'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/persistence.rb:120:in `save'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/validations.rb:37:in `save'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/attribute_methods/dirty.rb:21:in `save'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/transactions.rb:286:in `block (2 levels) in save'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/transactions.rb:351:in `block in with_transaction_returning_status'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/connection_adapters/abstract/database_statements.rb:211:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/transactions.rb:220:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/transactions.rb:348:in `with_transaction_returning_status'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/transactions.rb:286:in `block in save'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/transactions.rb:301:in `rollback_active_record_state!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/transactions.rb:285:in `save'
/var/www/discourse/lib/topic_creator.rb:160:in `save_topic'
/var/www/discourse/lib/topic_creator.rb:40:in `create'
/var/www/discourse/lib/post_creator.rb:289:in `create_topic'
/var/www/discourse/lib/post_creator.rb:126:in `block in create'
/var/www/discourse/lib/post_creator.rb:227:in `call'
/var/www/discourse/lib/post_creator.rb:227:in `block in transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `block in transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.5.1/lib/active_record/transactions.rb:220:in `transaction'
/var/www/discourse/lib/post_creator.rb:225:in `transaction'
/var/www/discourse/lib/post_creator.rb:124:in `create'
/var/www/discourse/lib/new_post_manager.rb:148:in `perform_create_post'
/var/www/discourse/lib/new_post_manager.rb:109:in `perform'
/var/www/discourse/lib/email/receiver.rb:324:in `create_post'
/var/www/discourse/lib/email/receiver.rb:305:in `create_post_with_attachments'
/var/www/discourse/lib/email/receiver.rb:255:in `create_topic'
/var/www/discourse/lib/email/receiver.rb:72:in `process_internal'
/var/www/discourse/lib/email/receiver.rb:34:in `process'
/var/www/discourse/app/jobs/scheduled/poll_mailbox.rb:26:in `process_popmail'
/var/www/discourse/app/jobs/scheduled/poll_mailbox.rb:81:in `block (2 levels) in poll_pop3'
/usr/local/lib/ruby/2.0.0/net/pop.rb:688:in `block in delete_all'
/usr/local/lib/ruby/2.0.0/net/pop.rb:687:in `each'
/usr/local/lib/ruby/2.0.0/net/pop.rb:687:in `delete_all'
/var/www/discourse/app/jobs/scheduled/poll_mailbox.rb:80:in `block in poll_pop3'
/usr/local/lib/ruby/2.0.0/net/pop.rb:531:in `start'
/var/www/discourse/app/jobs/scheduled/poll_mailbox.rb:79:in `poll_pop3'
/var/www/discourse/app/jobs/scheduled/poll_mailbox.rb:15:in `execute'
/var/www/discourse/app/jobs/base.rb:154:in `block (2 levels) in perform'

This is a multisite installation and this happened in the primary instance. It seemed the sender address was lost in the process:

Posts: 4

Participants: 2

Read full topic

Multiple docker containers for multiple Discourse forums?

$
0
0

@AstonJ wrote:

Is it possible to just duplicate the install process so that you end up with multiple docker containers therefore multiple Discourse instances?

Or am I completely misunderstanding things here? :neutral_face:

Posts: 13

Participants: 3

Read full topic

Install plugins for hosted solution

$
0
0

@BoVice wrote:

I am still in the 14-day trial period of the $100/month standard discourse hosted solution. I have been trying to figure out if there is any way to install plugins in the hosted solution. The only instructions I have found so for were for instances of Discourse. This would be great except I would still need some way to deploy these changes to the Discourse server, but cannot find any information on SSH/FTP access to push the changes needed.

Does the hosted plan even support this or is it meant to be cookie-cutter with no possibility of customization?

Posts: 4

Participants: 3

Read full topic

How to update a plugin without rebuild docker?

$
0
0

@Trash wrote:

Sometimes happens that we need to update a plugin.
The easiest way is doing the update when we upgrade discourse. But we need to do that in the middle of the night because we have to rebuild the container.

Is there a way to update only a plugin without rebuild docker?
Running the command
rake plugin:update plugin=discourse-name_of_plugin
is safe or is it possible that we broken something?

Better ask before so I don't cry after...

Posts: 3

Participants: 2

Read full topic


Mention group/user without notification

$
0
0

@jomaxro wrote:

Problem:

Recently, I have come across situations where I would like to mention a group (like @team or @moderators) as a reference to the group, not as a way of notifying them/getting their attention.

Two examples:

  1. On the Stonehearth Discourse: Once group mentions became a thing, we went back and modified our FAQ, rules and guidelines, and other basic topics to ask users to mention/message @moderators when they need help instead of mentioning a random moderator. As all the moderators are equally capable, and are in different timezones, we felt this would be the most efficient way for users to request help. Unfortunately, when each of those edits are made, all moderators receive a notifications (not my intent!).
  2. On Meta: Recently I wanted to reference the Discourse team. Something along the lines of "The Discourse team would ...", and would have liked the word team to be in reference to the group. Unfortunately, if I put the @ sign in front of the word team 12 people would have been notified.

Proposal:

There should be a method to "mention" a group (or user) and prevent them from receiving notifications. Currently, you can surround groups with backticks (like @team) and prevent notification, but that also prevents team from being clicked on to bring a user to the group page. I do not know what character (or set of characters) to propose, but something that can easily be inserted into the editor surrounding the group/user could be of great use.

Posts: 9

Participants: 4

Read full topic

Messages tab visible to non-group members

$
0
0

@jomaxro wrote:

Summary:

When loading a group page for a group I do not belong to, I can see the Messages tab on the left.

Steps to reproduce:

  1. Navigate to a group page you are not a part of.
  2. Look at left menu

Expected Results:

See 4 buttons, Posts, Topics, Mentions, Members

Actual Results:

See 5 buttons, Posts, Topics, Mentions, Members, Messages

Notes:

While the Messages button is there and can be clicked, no messages are shown so there does not appear to be a major privacy/security issue here.

Attachments:

Version:

Discourse 1.5.0.beta9 (meta.discourse.org)

System Information:

Windows 10 Pro, Chrome Stable 48

Posts: 1

Participants: 1

Read full topic

Moderators still able to access other users bookmarks

$
0
0

@jomaxro wrote:

Summary:

When the changes were made to the user profile page, moderators were supposed to lose access to other users bookmarks. While the tab was removed from the left menu, if a moderator navigates to another user's profile directly by URL, they are still given access to the bookmarks.

Steps to reproduce:

  1. Navigate to $site_url/users/user_name_here/activity/bookmarks as moderator

Expected Results:

Receive access denied error message

Actual Results:

View user's bookmarks

Notes:

Continuing the discussion from Moderators cannot view bookmarks on other user's activity pages

Attachments:

None for privacy reasons.

Version:

Discourse 1.5.0.beta9 (discourse.stonehearth.net)

System Information:

Windows 10 Pro, Chrome Stable 48

Posts: 1

Participants: 1

Read full topic

Muted users still show notifications

$
0
0

@carlokok wrote:

I have our bots set to muted in my profile "muted users" list, however I still get notification popups for them.

Posts: 1

Participants: 1

Read full topic

Incoming Email doesn't support mail without message id

$
0
0

@carlokok wrote:

we have some customers that don't have a messageID in their emails, discourse gives this error:

Email can not be processed: Email::Receiver::NoMessageIdError
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-1.0.1/lib/logster/logger.rb:74:in `add_with_opts'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-1.0.1/lib/logster/logger.rb:35:in `add'
/usr/local/lib/ruby/2.0.0/logger.rb:445:in `warn'
/var/www/discourse/app/jobs/scheduled/poll_mailbox.rb:33:in `handle_failure'
/var/www/discourse/app/jobs/scheduled/poll_mailbox.rb:28:in `rescue in process_popmail'
/var/www/discourse/app/jobs/scheduled/poll_mailbox.rb:24:in `process_popmail'
/var/www/discourse/app/jobs/scheduled/poll_mailbox.rb:81:in `block (2 levels) in poll_pop3'
/usr/local/lib/ruby/2.0.0/net/pop.rb:688:in `block in delete_all'
/usr/local/lib/ruby/2.0.0/net/pop.rb:687:in `each'
/usr/local/lib/ruby/2.0.0/net/pop.rb:687:in `delete_all'
/var/www/discourse/app/jobs/scheduled/poll_mailbox.rb:80:in `block in poll_pop3'
/usr/local/lib/ruby/2.0.0/net/pop.rb:531:in `start'
/var/www/discourse/app/jobs/scheduled/poll_mailbox.rb:79:in `poll_pop3'
/var/www/discourse/app/jobs/scheduled/poll_mailbox.rb:15:in `execute'
/var/www/discourse/app/jobs/base.rb:154:in `block (2 levels) in perform'

Posts: 3

Participants: 2

Read full topic

Have Akismet scan private messages

$
0
0

@Sander78 wrote:

Now that new users can mail groups, it would be good to have Akismet scan those mails, right? It's turned off by design now.

Posts: 2

Participants: 2

Read full topic

PAID: PGP Encrypted emails

$
0
0

@seanthegeek wrote:

I'd like a plugin to:

  • Store a site-wide public/private key pair for signing system emails
  • Store public PGP keys in user profiles
  • Redact the message topic the subject
  • Sign and encrypt all outgoing mail
  • Block sending emails to those who do not have a key on file

I'd like this to be Apache 2.0 Licensed, and publicly released. I'd do this myself, but I've never written a line of Ruby :stuck_out_tongue:. If interested, let me know what the cost would be.

Posts: 1

Participants: 1

Read full topic


How to read Anonymous traffic from web report when forum is login-only?

$
0
0

@prod_discourse_admin wrote:

My site is login-only and I've been eyeballing the Web performance report for a few weeks and this (see below) caught my eye today. Is this accounted for as spider/crawler traffic? I just want to be sure my user list is not exposed publicly (via user_avatars/show).

Mostly just looking for an indication as to whether i need to dig deeper in to the logs to pull more information.

Thanks a bunch in advance!

[Anonymous] 33.90 621 -(26.89) - (POST)(2.54) static/show(2.10) session/create (POST)(1.24)
user_avatars/show(0.53)

Posts: 2

Participants: 2

Read full topic

Integrating Discourse with a larger social network app?

$
0
0

@Talin wrote:

Hi folks, I'm in the process of evaluating whether we should adopt Discourse for our organization. I'm working with a group at UC Santa Cruz that is developing a social network for cancer researchers, and we'd like to replace our existing forums with something better. At the same time, we've got a lot of special needs, and we're actively researching new ideas for scientific collaboration. I'm not going to give the complete list of requirements, but I want to ask about a few basic things.

One interested in is being able to integrate Discourse with the other applications we have. For example, in our existing applications a "collaboration" object represents a research team that is focused on some project, and new collaborations are formed on a regular basis. Each collaboration should have their own private forum, but some postings would be sent to multiple collaborations.

So the first question I would pose is what kind of Discourse object a collaboration should map to - a category, or something else?

Second question is how to create that object - I was thinking that there might be some kind of RESTful API so that our server could tell Discourse to create it when a new collaboration was created.

Another question has to do with reputation and ranking. In the scientific world, reputation is gained through citations - the more people that reference your paper, the better off you are. So in a scientifically-oriented forum, reputation would be gained via quoting and resharing - that is, it counts the number of times people reference your words. Is something like this feasible?

I see that Discourse already supports embedding of SVGs, which is great - a lot of our researchers share experimental results in the form of SVGs (scatter plots, trend graphs, etc.) We're also interested in more interactive kinds of embeds - for example, we have a kind of embeddable object that represents a data set, such as the results of clinical trials, and this takes you to a page where you can slice and dice the data in different ways, form hypotheses and try them out by graphing the data in different ways.

In the long run, something we're very interested in is the creation of curated digests - that is, some sort of tool that would allow someone to grab excepts and quotes from a lot of different threads and create a publishable artifact, a summary of the outcomes of those discussions. And of course, this artifact would retain links to the original discussion, so that it's easy to determine who originally contributed a particular idea.

It seems to me that this might align with some of your goals as well, since you are interested in creating "civilized discussion" - being able to create an abstract of a conversation seems like it would fit right in.

Posts: 4

Participants: 2

Read full topic

Redis intermittently causing 500 Internal Error v1.5.0.8

$
0
0

@corillian wrote:

I'm currently in the process of upgrading to 1.5.0.9 to see if that resolves the issue but I've had problems with Redis causing 500 Internal Error in the last 2 versions of Discourse I've been running. Redis is being hosted on my data server with modifications to the data.yml sample whereas I have a single Discourse instance running with modifications to the web_only.yml sample (during upgrades I always check discourse_docker for latest and merge changes). I don't use the Discourse auto-upgrade feature and instead manually do upgrades deleting all images and rebuilding everything from scratch.

The 500 Internal Server error appearance seems to coincide with the following errors in my syslog logfile on the data server:

Feb  3 13:02:46 inovaeforumsdb0-data redis[19]: Background saving started by pid 56
Feb  3 13:02:46 inovaeforumsdb0-data redis[56]: Failed opening .rdb for saving: Permission denied
Feb  3 13:02:46 inovaeforumsdb0-data redis[19]: Background saving error
Feb  3 13:02:52 inovaeforumsdb0-data redis[19]: 10 changes in 300 seconds. Saving...
Feb  3 13:02:52 inovaeforumsdb0-data redis[19]: Background saving started by pid 57
Feb  3 13:02:52 inovaeforumsdb0-data redis[57]: Failed opening .rdb for saving: Permission denied
Feb  3 13:02:52 inovaeforumsdb0-data redis[19]: Background saving error
Feb  3 13:02:58 inovaeforumsdb0-data redis[19]: 10 changes in 300 seconds. Saving...
Feb  3 13:02:58 inovaeforumsdb0-data redis[19]: Background saving started by pid 58
Feb  3 13:02:58 inovaeforumsdb0-data redis[58]: Failed opening .rdb for saving: Permission denied

If I just restart the data server everything seems to work fine anywhere from a few hours to weeks:

Feb  3 13:52:04 inovaeforumsdb0-data redis[19]: Background saving started by pid 1336
Feb  3 13:52:04 inovaeforumsdb0-data redis[1336]: Failed opening .rdb for saving: Permission denied
Feb  3 13:52:04 inovaeforumsdb0-data redis[19]: Background saving error
Feb  3 13:52:10 inovaeforumsdb0-data redis[19]: 1 changes in 900 seconds. Saving...
Feb  3 13:52:10 inovaeforumsdb0-data redis[19]: Background saving started by pid 1349
Feb  3 13:52:10 inovaeforumsdb0-data redis[1349]: Failed opening .rdb for saving: Permission denied
Feb  3 13:52:10 inovaeforumsdb0-data redis[19]: User requested shutdown...
Feb  3 13:52:10 inovaeforumsdb0-data redis[19]: There is a child saving an .rdb. Killing it!
Feb  3 13:52:10 inovaeforumsdb0-data redis[19]: Saving the final RDB snapshot before exiting.
Feb  3 13:52:10 inovaeforumsdb0-data redis[19]: Failed opening .rdb for saving: Permission denied
Feb  3 13:52:10 inovaeforumsdb0-data redis[19]: Error trying to save the DB, can't exit.
Feb  3 13:52:10 inovaeforumsdb0-data redis[19]: SIGTERM received but errors trying to shut down the server, check the logs $
Feb  3 13:52:10 inovaeforumsdb0-data redis[19]: Background saving error
Feb  3 13:52:16 inovaeforumsdb0-data redis[19]: 1 changes in 900 seconds. Saving...
Feb  3 13:52:16 inovaeforumsdb0-data redis[19]: Background saving started by pid 1358
Feb  3 13:52:16 inovaeforumsdb0-data redis[1358]: Failed opening .rdb for saving: Permission denied
Feb  3 13:52:16 inovaeforumsdb0-data redis[19]: Background saving error
Feb  3 13:52:58 inovaeforumsdb0-data rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="20" x-info="http://www.$
Feb  3 13:52:58 inovaeforumsdb0-data rsyslogd-3003: invalid or yet-unknown config file command 'KLogPermitNonKernelFacility$
Feb  3 13:52:58 inovaeforumsdb0-data rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement in$
Feb  3 13:52:58 inovaeforumsdb0-data rsyslogd: rsyslogd's groupid changed to 104
Feb  3 13:52:58 inovaeforumsdb0-data rsyslogd: rsyslogd's userid changed to 101
Feb  3 13:52:58 inovaeforumsdb0-data rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [t$
Feb  3 13:52:59 inovaeforumsdb0-data redis[22]: DB loaded from disk: 1.204 seconds
Feb  3 13:52:59 inovaeforumsdb0-data redis[22]: The server is now ready to accept connections on port 6379
Feb  3 13:57:59 inovaeforumsdb0-data redis[22]: 10 changes in 300 seconds. Saving...
Feb  3 13:57:59 inovaeforumsdb0-data redis[22]: Background saving started by pid 59
Feb  3 13:57:59 inovaeforumsdb0-data redis[59]: DB saved on disk
Feb  3 13:57:59 inovaeforumsdb0-data redis[59]: RDB: 44 MB of memory used by copy-on-write
Feb  3 13:57:59 inovaeforumsdb0-data redis[22]: Background saving terminated with success
Feb  3 14:03:00 inovaeforumsdb0-data redis[22]: 10 changes in 300 seconds. Saving...
Feb  3 14:03:00 inovaeforumsdb0-data redis[22]: Background saving started by pid 67
Feb  3 14:03:00 inovaeforumsdb0-data redis[67]: DB saved on disk
Feb  3 14:03:00 inovaeforumsdb0-data redis[67]: RDB: 44 MB of memory used by copy-on-write
Feb  3 14:03:00 inovaeforumsdb0-data redis[22]: Background saving terminated with success

Anyone have any idea what could be going on? It seems like a Redis background save process is hanging and preventing all future saves from succeeding?

Posts: 5

Participants: 2

Read full topic

Can't start docker after update (openSUSE 13.2)

$
0
0

@elutz wrote:

After updating the docker package I'm not able to start the docker daemon anymore.

 lutz@ea-esbz:/var/discourse> sudo systemctl status -l docker
docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled)
   Active: failed (Result: exit-code) since Mi 2016-02-03 21:25:09 UTC; 3s ago
     Docs: http://docs.docker.com
  Process: 28385 ExecStart=/usr/bin/docker daemon -H fd:// $DOCKER_OPTS (code=exited, status=1/FAILURE)
 Main PID: 28385 (code=exited, status=1/FAILURE)

Feb 03 21:25:09 ea-esbz docker[28385]: time="2016-02-03T21:25:09.239522989Z" level=info msg="API listen on /var/run/docker.sock"
Feb 03 21:25:09 ea-esbz docker[28385]: time="2016-02-03T21:25:09.243285203Z" level=warning msg="Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section."
Feb 03 21:25:09 ea-esbz docker[28385]: time="2016-02-03T21:25:09.252326106Z" level=fatal msg="Error starting daemon: error initializing graphdriver: Could not query and save base device UUID:Error running deviceCreate (ActivateDevice) dm_task_run failed"

The main problem seems to be (see the last line above):
"Error starting daemon: error initializing graphdriver: Could not query and save base device UUID:Error running deviceCreate (ActivateDevice) dm_task_run failed"

Any ideas? Didn't find an answer in the already psoted topics on meta.discourse
BTW:

docker --version
Docker version 1.9.1, build a34a1d5

Lutz

Posts: 7

Participants: 2

Read full topic

Duplicate digests still

Viewing all 60721 articles
Browse latest View live




Latest Images