similar to: Log level to debug in production?

I am seeing errors of this type: ActionController::RoutingError (Recognition failed for "/blah/50112.mp3"): Showing up in production.log. I''d like to suppress as they are ''known'' and not real errors. I have my logging set to: config.log_level = :error In environmnent.rb. What can I do to remove these errors from my log? Cheers

http://bugzilla.mindrot.org/show_bug.cgi?id=1221 Summary: Banner only suppressed at log level = QUIET (used to be at log level < INFO) Product: Portable OpenSSH Version: 4.3p2 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P2 Component: ssh AssignedTo:

Hi, I have added to my migration a change_table action. It works fine on my local dev machine, but on the production server the migration does not happen although the schema.rb file gets correctly updated. I am running Rails 2.1.1 -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google

Hello, In production environment, I have this error ActionView::Template::Error Not a directory vendor/assets/javascripts/holder.js when in my template I have this line <%= image_tag "holder.js/150x200" %> My production.rb is : Libapp::Application.configure do # Settings specified here will take precedence over those in config/application.rb # Code is not reloaded

i have an eager load query as such: @groups = ReviewQuestionGroup.find(:all, :conditions => ["review_category_id = ?", @review.category.id], :order => ''review_question_groups.position, review_questions.position'', :include => :questions) in dev mode, this works fine... i get results like @groups[0].questions.length = 13. in production, i

Hi there, I know this is off-topic or semi off-topic but I really need some help since I am stucked. I'm trying to redirect MariaDB logs to `/var/log/mysql/*.log` files as shown below on the `/etc/my.cnf.d/server.cnf` file: # # These groups are read by MariaDB server. # Use it for options that only the server (but not clients) should see # # See the examples of server

Hi, Related to: http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/ssh.c.diff?r1=1.100&r2=1.101 It'd appear that logging in readconf.c: --- debug("Applying options for %.100s", arg); debug("Reading configuration data %.200s", filename); --- Goes to /dev/null. This is caused by the fact, that in ssh.c there is: --- /* * Initialize

I like the Stanford Best Practices guide for puppet. One thing I didn''t see it address was handling of separate environments, for example Dev, Test, Staging, Production. My thoughts on this so far, are: brainstorm #1) Handle environment differences with metadata: node devProductName01 { $env = "dev" include ProductName-webserver } node testProductName01 {

Hi, I noticed that some, but not all, of my CentOS 7 machines have these kernel parameters for turning on systemd debug level logging added to the grub.cfg file. systemd.log_level=debug systemd.log_target=kmsg The parameters are *not* in the /etc/default/grub file, so if I rebuild grub.cfg with grub2-mkconfig, they disappear. I am a bit puzzled over how they got introduced. Has anyone else

this patch adds a LogFile option to sshd_config. it just logs messages directly to a file instead of stderr or syslog. the largest change is an additional argument to log_init() in log.c for the log file name (and then changes to the rest of the tools to add a NULL arg). galt -------------- next part -------------- diff -urN openssh-3.5p1-orig/log.c openssh-3.5p1/log.c ---

Hi, I have a local development environment and remote production environment, however I am really just learning/playing, hence I would like to be able to define these environments separately in the config files, however.... I would like my production environment to really act in a development mode fashion at the moment (i.e. sense updates I make without any need to restart things etc). Is

Hi all, I am now working on performance tuning. I am still a newbie thus I am not talking about "full blown performance tuning". What I do now is just tracking my development.log to find whether I accidentally make redundant queries because of my misunderstanding of ActiveRecord, redundant AJAX calls, or logical mistakes. The questions: 1. From what I understand the standard log_level

The interval between having to clear out the git caches has become ridiculously short. I''m going to arrange to keep the logs for less long. We need, however, to have more space for logs. I will try to organise this. We also need an approach to git caching that is less wasteful of space. If anyone fancies writing a competent caching proxy for git, please get in touch. Failing that

By default, all the paramaters are displayed in the production.log on a POST. Unfortunately, this includes all the plain-text passwords that people type into the login form on my application, which is a huge security risk. I''m using a custom evaluation system that hooks into LDAP (not any of the generators/plugins). View code is simple: <%= text_field ''employee'',

The attached modification to log-server.c add a "tag" to all the syslog output. The tag is a composite of the internal verbose level names used in sshd and the external syslogd names. The form of the tag is as follows. ssh_internal_name(syslog_priority) This might be instructive for a learning sysadmin trying to setup syslog for sshd logging. (I have posted earlier about

So, as I''m working on migrating my app from Rails 1.2.1 to Rails 1.2.6, suddenly my database adaptor password is showing up in production log on startup. This could be because use " ActiveRecord::Base.allow_concurrency = true" (I know, nobody else does and you''ll tell me not to do it. But I''ve investigated it and it''s working for me, that''s

Hi, I''ve got an app that talks to two databases on a given MySQL server. When I run in development mode, pointing to the MySQL server running on localhost (127.0.0.1), I am able to access both databases without any problem. The relevant yaml looks like this: (names have been changed to protect the innocent) development: adapter: mysql database: dev username: username password:

Hello I'm going to change the raid array of my mailhub in fews days/weeks and I wonder if it would be a good idea to take the opportunity of this migration to also change the storage method from mailbox to maildir. I've never used maildir on my production server only on small satellites. So I really need advice of admins that use maildir format on prod servers. My server has approx

Here is what my data looks like: source:~# ls -ld /data /data/etc2 lrwxrwxrwx 1 root root 12 2010-06-03 23:32 /data -> /export/hda3 -rw-r--r-- 1 produser prod 4 2010-06-15 17:30 /data/etc2 destination:/# ls -l /data lrwxrwxrwx 1 root root 12 2010-06-15 18:36 /data -> /export/hda3 Let's start with an ancient rsync: source:~# rsync-broken --version rsync version 2.4.6 protocol

Is it possible to filter the generated emails from the production-log? I''d like to remove them there, since there is some private-info in them... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to