Couchbase
  • Why NoSQL?
  • Couchbase Server
  • Download
  • Resources
  • Careers
Home | Forums | Couchbase | Couchbase Server 1.8.x

Unexpected debug logs created

9 replies [Last post]
  • Login or register to post comments
Tue, 09/11/2012 - 12:20
rchouinard
Offline
Joined: 09/11/2012
Groups: None

Hi all,

We've recently upgraded our cluster to 1.8.1, and we've started seeing a bunch of debug logs created along side the standard logs. I can't find where these have been enabled, and they're throwing our space calculations off.

We upgraded to 1.8.1 on Sept. 2nd, and our log directory currently looks like this:

# ls -lA var/lib/couchbase/logs/
total 397040
-rw-r--r-- 1 couchbase couchbase 10475986 Aug 28 18:02 1
-rw-r--r-- 1 couchbase couchbase 10474371 Sep  1 18:06 10
-rw-r--r-- 1 couchbase couchbase 10478439 Sep  2 04:51 11
-rw-r--r-- 1 couchbase couchbase 10484498 Sep  2 15:36 12
-rw-r--r-- 1 couchbase couchbase  4506576 Sep  2 20:12 13
-rw-r--r-- 1 couchbase couchbase 10484011 Aug 25 15:20 14
-rw-r--r-- 1 couchbase couchbase 10477452 Aug 26 01:59 15
-rw-r--r-- 1 couchbase couchbase 10484939 Aug 26 12:40 16
-rw-r--r-- 1 couchbase couchbase 10482882 Aug 26 23:22 17
-rw-r--r-- 1 couchbase couchbase 10474503 Aug 27 10:01 18
-rw-r--r-- 1 couchbase couchbase 10478265 Aug 27 20:42 19
-rw-r--r-- 1 couchbase couchbase 10475345 Aug 29 04:41 2
-rw-r--r-- 1 couchbase couchbase 10477176 Aug 28 07:22 20
-rw-r--r-- 1 couchbase couchbase 10482258 Aug 29 15:22 3
-rw-r--r-- 1 couchbase couchbase 10478579 Aug 30 02:02 4
-rw-r--r-- 1 couchbase couchbase 10474952 Aug 30 12:41 5
-rw-r--r-- 1 couchbase couchbase  9529407 Aug 30 22:23 6
-rw-r--r-- 1 couchbase couchbase 10481695 Aug 31 09:48 7
-rw-r--r-- 1 couchbase couchbase 10479310 Aug 31 20:35 8
-rw-r--r-- 1 couchbase couchbase 10479893 Sep  1 07:21 9
-rw-r--r-- 1 couchbase couchbase 10479649 Sep 11 18:27 debug.1
-rw-r--r-- 1 couchbase couchbase 10484037 Sep  7 13:58 debug.10
-rw-r--r-- 1 couchbase couchbase 10474223 Sep  7 23:08 debug.11
-rw-r--r-- 1 couchbase couchbase 10469317 Sep  8 08:18 debug.12
-rw-r--r-- 1 couchbase couchbase 10475054 Sep  8 17:29 debug.13
-rw-r--r-- 1 couchbase couchbase 10479681 Sep  9 02:38 debug.14
-rw-r--r-- 1 couchbase couchbase 10476464 Sep  9 11:48 debug.15
-rw-r--r-- 1 couchbase couchbase 10481733 Sep  9 20:59 debug.16
-rw-r--r-- 1 couchbase couchbase 10478842 Sep 10 06:08 debug.17
-rw-r--r-- 1 couchbase couchbase 10485525 Sep 10 15:18 debug.18
-rw-r--r-- 1 couchbase couchbase 10479018 Sep 11 00:09 debug.19
-rw-r--r-- 1 couchbase couchbase   723819 Sep 11 19:04 debug.2
-rw-r--r-- 1 couchbase couchbase 10485722 Sep 11 09:18 debug.20
-rw-r--r-- 1 couchbase couchbase 10476132 Sep  3 23:41 debug.3
-rw-r--r-- 1 couchbase couchbase 10484284 Sep  4 08:52 debug.4
-rw-r--r-- 1 couchbase couchbase 10471966 Sep  4 18:03 debug.5
-rw-r--r-- 1 couchbase couchbase 10483331 Sep  5 03:05 debug.6
-rw-r--r-- 1 couchbase couchbase 10476206 Sep  5 11:59 debug.7
-rw-r--r-- 1 couchbase couchbase 10471278 Sep  6 19:34 debug.8
-rw-r--r-- 1 couchbase couchbase 10484174 Sep  7 04:46 debug.9
-rw-r--r-- 1 couchbase couchbase      170 Sep 11 18:27 debug.idx
-rw-r--r-- 1 couchbase couchbase       13 Sep  6 13:45 debug.siz
-rw-r--r-- 1 couchbase couchbase    37210 Sep 11 01:32 error.1
-rw-r--r-- 1 couchbase couchbase       18 Sep  6 13:45 error.idx
-rw-r--r-- 1 couchbase couchbase       13 Sep  6 13:45 error.siz
-rw-r--r-- 1 couchbase couchbase        1 Sep  2 15:37 index
-rw-r--r-- 1 couchbase couchbase  3290060 Sep 11 19:04 info.1
-rw-r--r-- 1 couchbase couchbase       18 Sep  6 13:45 info.idx
-rw-r--r-- 1 couchbase couchbase       13 Sep  6 13:45 info.siz

Any ideas how to disable the debug logs, or is this normal behavior?

Top
  • Login or register to post comments
Tue, 09/11/2012 - 13:04
alkondratenko
alkondratenko's picture
Offline
Joined: 12/01/2010
Groups: None

It is normal behavior. We have changed our logger implementation in 1.8.1. You can delete old logs.

If you want to decrease size of logs or disable debug logging completely this is doable.

Top
  • Login or register to post comments
Tue, 09/11/2012 - 13:23
rchouinard
Offline
Joined: 09/11/2012
Groups: None

Okay, I figured something had changed. How do we disable the debug log? I can't find any reference in the docs, other than the names of the log levels. From what I can see (and I may be looking in the wrong place... static_config?) all of our logs are set to "info" level.

Top
  • Login or register to post comments
Tue, 09/11/2012 - 13:31
alkondratenko
alkondratenko's picture
Offline
Joined: 12/01/2010
Groups: None

Yes static_config would work. But, please, consider not disabling debug logging. It can be very valuable tool in case something will go wrong. We haven't observed any significant CPU or memory usage from our debug logging.

Top
  • Login or register to post comments
Tue, 12/11/2012 - 00:01
dew_ice
Offline
Joined: 09/05/2012
Groups: None

hi ,
how to change 'static_config'? where can i find it?

And if I just want print error info , how can I do?

I understand there's NO issue about debug logging, i just want decrese the log info in app server (e.g. tomcat).

Thanks.

Top
  • Login or register to post comments
Tue, 12/11/2012 - 00:04
dew_ice
Offline
Joined: 09/05/2012
Groups: None

I just want to don't show following info:

 2012-12-11 14:01:50.333 INFO com.couchbase.client.CouchbaseConnection:  Added {QA sa=/{ServerB}:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
[java] 2012-12-11 14:01:50.333 INFO com.couchbase.client.CouchbaseConnection:  Added {QA sa=/{ServerA}:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
[java] 2012-12-11 14:01:50.334 INFO com.couchbase.client.CouchbaseConnection:  Added {QA sa=/{ServerC}:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
[java] 2012-12-11 14:01:50.360 INFO com.couchbase.client.CouchbaseConnection:  Connection state changed for sun.nio.ch.SelectionKeyImpl@22baebe7
[java] 2012-12-11 14:01:50.360 INFO com.couchbase.client.CouchbaseConnection:  Connection state changed for sun.nio.ch.SelectionKeyImpl@635031df
[java] 2012-12-11 14:01:50.361 INFO com.couchbase.client.CouchbaseConnection:  Connection state changed for sun.nio.ch.SelectionKeyImpl@3315e874
[java] 2012-12-11 14:01:50.364 INFO net.spy.memcached.auth.AuthThread:  Authenticated to {ServerB}/{ServerB}:11210
[java] 2012-12-11 14:01:50.364 INFO net.spy.memcached.auth.AuthThread:  Authenticated to {ServerC}/{ServerC}:11210
[java] 2012-12-11 14:01:50.377 INFO net.spy.memcached.auth.AuthThread:  Authenticated to {ServerA}/{ServerA}:11210
[java] 2012-12-11 14:03:26.383 INFO com.couchbase.client.CouchbaseConnection:  Added {QA sa=/{ServerB}:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
[java] 2012-12-11 14:03:26.384 INFO com.couchbase.client.CouchbaseConnection:  Added {QA sa=/{ServerB}:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
[java] 2012-12-11 14:03:26.384 INFO com.couchbase.client.CouchbaseConnection:  Added {QA sa=/{ServerA}:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue

Top
  • Login or register to post comments
Tue, 12/11/2012 - 15:55
tgrall
Offline
Joined: 09/05/2012
Groups: None

Hello,
Have you seen this part of the Couchbase Java Client library documentation:
http://www.couchbase.com/docs/couchbase-sdk-java-1.0/java-api-configurin...

This is based on standard login options, as you can see the message you have the INFO level, if you want to remove them you just need to change the level in your code or configuration. The levels in descending order are:
- SEVERE (highest value)
- WARNING
- INFO
- CONFIG
- FINE
- FINER
- FINEST (lowest value)

So you can put for example the loggers to the WARNING level and these information will not be visible anymore in your logs file.

__________________

Tug
@tgrall

Top
  • Login or register to post comments
Thu, 12/13/2012 - 01:44
dew_ice
Offline
Joined: 09/05/2012
Groups: None

thanks a lot. i will try it.

tgrall wrote:
Hello,
Have you seen this part of the Couchbase Java Client library documentation:
http://www.couchbase.com/docs/couchbase-sdk-java-1.0/java-api-configurin...

This is based on standard login options, as you can see the message you have the INFO level, if you want to remove them you just need to change the level in your code or configuration. The levels in descending order are:
- SEVERE (highest value)
- WARNING
- INFO
- CONFIG
- FINE
- FINER
- FINEST (lowest value)

So you can put for example the loggers to the WARNING level and these information will not be visible anymore in your logs file.

Top
  • Login or register to post comments
Sat, 01/05/2013 - 19:13
dew_ice
Offline
Joined: 09/05/2012
Groups: None

based on the url,
I create a file 'logging.properties' under classpath,
the content are below
handlers = java.util.logging.ConsoleHandler
java.util.logging.ConsoleHandler.level = SEVERE
java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
com.couchbase.client.vbucket.level = SEVERE
com.couchbase.client.vbucket.config.level = SEVERE
com.couchbase.client.level = SEVERE

it seems don't work, i still get the log like :

2013-01-04 14:59:47.742 INFO com.couchbase.client.CouchbaseConnection: Added {Q
A sa=/*.*.*.***:11210, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toW
rite=0, interested=0} to connect queue
2013-01-04 14:59:48.242 INFO com.couchbase.client.CouchbaseConnection: Connecti
on state changed for sun.nio.ch.SelectionKeyImpl@73a51852
2013-01-04 14:59:48.250 INFO com.couchbase.client.CouchbaseConnection: Connecti
on state changed for sun.nio.ch.SelectionKeyImpl@5f0f8407
2013-01-04 14:59:48.276 INFO net.spy.memcached.auth.AuthThread: Authenticated t
o EPEKW-Q1100017.is.ad.igt.com/*.*.*.***:11210

But if I change ‘SERVER' to 'FINEST', i can get more log info about vbucket,
this show the log properties files work.
but why 'SERVER' donesn't work?

Could you show your comment?Thanks.

tgrall wrote:
Hello,
Have you seen this part of the Couchbase Java Client library documentation:
http://www.couchbase.com/docs/couchbase-sdk-java-1.0/java-api-configurin...

This is based on standard login options, as you can see the message you have the INFO level, if you want to remove them you just need to change the level in your code or configuration. The levels in descending order are:
- SEVERE (highest value)
- WARNING
- INFO
- CONFIG
- FINE
- FINER
- FINEST (lowest value)

So you can put for example the loggers to the WARNING level and these information will not be visible anymore in your logs file.

Top
  • Login or register to post comments
Fri, 03/29/2013 - 11:49
lcheung
Offline
Joined: 03/29/2013
Groups: None

Hi,
I'm using "2.0.0 community edition (build-1976)" and static_config doesn't work. Set the debug level to "error" for production server:

root@server1:/tmp/couchbase/logs$ cat /opt/couchbase/etc/couchbase/static_config
{error_logger_mf_dir, "/opt/couchbase/var/lib/couchbase/logs"}.
{error_logger_mf_maxbytes, 10485760}.
{error_logger_mf_maxfiles, 20}.
{path_config_bindir, "/opt/couchbase/bin"}.
{path_config_etcdir, "/opt/couchbase/etc/couchbase"}.
{path_config_libdir, "/opt/couchbase/lib"}.
{path_config_datadir, "/opt/couchbase/var/lib/couchbase"}.
{path_config_tmpdir, "/tmp"}.

{loglevel_default, error}.
{loglevel_couchdb, error}.
{loglevel_ns_server, error}.
{loglevel_error_logger, error}.
{loglevel_user, error}.
{loglevel_menelaus, error}.
{loglevel_ns_doctor, error}.
{loglevel_stats, error}.
{loglevel_rebalance, error}.
{loglevel_cluster, error}.
{loglevel_views, error}.
{loglevel_mapreduce_errors, error}.
{loglevel_xdcr, error}.

But the debug log indicate that everything is still in debug level:
root@server1:/opt/couchbase/var/lib/couchbase/logs$$ more debug.1
[ns_server:info,2013-02-04T18:44:17.063,nonode@nohost:<0.59.0>:ns_server:init_logging:225]Started & configured logg
ing
[ns_server:info,2013-02-04T18:44:17.065,nonode@nohost:<0.59.0>:ns_server:log_pending:30]Static config terms:
[{error_logger_mf_dir,"/opt/couchbase/var/lib/couchbase/logs"},
{error_logger_mf_maxbytes,10485760},
{error_logger_mf_maxfiles,20},
{path_config_bindir,"/opt/couchbase/bin"},
{path_config_etcdir,"/opt/couchbase/etc/couchbase"},
{path_config_libdir,"/opt/couchbase/lib"},
{path_config_datadir,"/opt/couchbase/var/lib/couchbase"},
{path_config_tmpdir,"/opt/couchbase/var/lib/couchbase/tmp"},
{loglevel_default,debug},
{loglevel_couchdb,info},
{loglevel_ns_server,debug},
{loglevel_error_logger,debug},
{loglevel_user,debug},
{loglevel_menelaus,debug},
{loglevel_ns_doctor,debug},
{loglevel_stats,debug},
{loglevel_rebalance,debug},
{loglevel_cluster,debug},
{loglevel_views,debug},
{loglevel_mapreduce_errors,debug},
{loglevel_xdcr,debug}]

Thanks.

Louis

Top
  • Login or register to post comments
  • Login or register to post comments
  • Login
  • Register

Company

  • About Us
  • Leadership
  • Customers
  • Partners
  • Contact Us

Product

  • Couchbase Server
  • Couchbase SDKs
  • Use Cases
  • Documentation
  • Forums

Open Source

  • Couchbase Project
  • Couchbase vs. CouchDB

Commercial

  • Subscriptions & Support
  • Training & Services

News

  • Blog
  • Newsletter
  • Press Releases
  • Buzz

Follow Us

    
  • Customer Login
  • Terms of Service
  • Privacy Policy
  • Trademark Policy
  • Site Map

© 2013 COUCHBASE All rights reserved.

Sign in to Couchbase Community

close
  • Create new account
  • Request new password
You are logging into the Forums, Wiki and Issue Tracker