Questions[loglevel](server)

How to run/configure syslog-ng to log only above the security loglevel/priority WARNING?

I would like to discard NOTICES like:

Destination timeout has elapsed, closing connection; fd='36'

From the docs: (https://www.syslog-ng.com/technical-documents/doc/syslog-ng-open-source-edition/3.22/administration-guide/17#TOPIC-1209129) I found this:

The syslog-ng OSE application sends the following message types from the internal() source:

fatal: Priority value: critical (2), Facility value: syslog (5)

error: Priority value: error (3), Facility value: syslog (5)

warning: Priority value: warning (4), Facility value: syslog (5)

notice: Priority value: notice (5), Facility value: syslog (5)

info: Priority value: info (6), Facility value: syslog (5)

But can't find how to set the loglevel to warning

When connecting to a server via SFTP, I can use -o to specify a LogLevel, like so:

sftp -oLogLevel=DEBUG3 username@host

This spits out a ton of debug information about the login process. However, it gets to this point and all debugs cease:

debug1: Sending subsystem: sftp
debug2: channel 0: request subsystem confirm 1
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel 0: rcvd adjust 131072
debug2: channel_input_status_confirm: type 99 id 0
debug2: subsystem request accepted on channel 0
Connected to host.
sftp> ls
Some    Directories
sftp> cd Some
sftp> ls
sftp> quit
debug2: channel 0: read<=0 rfd 4 len 0
debug2: channel 0: read failed
debug2: channel 0: close_read
debug2: channel 0: input open -> drain
debug2: channel 0: ibuf empty
debug2: channel 0: send eof
debug2: channel 0: input drain -> closed
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
Received disconnect from <IP>: 11: User Disconnected

What about that ls command? Where can I get debugs for that? cd? quit?

Also, I don't have any control over the remote server, so I'm not asking about configuring the SFTP subsystem on the server via sshd_config. I've tried that and it doesn't work.

The sftp-client.c file has calls to debug3, so where are they going?

We are using mongodb version 3 in a AWS environment with Linux AMIs.

Initially mongo was logging the entire document. We then lowered the verbosity in the yaml. That seemed to make most (99%) of the documents to not get logged. However we still find that it occasionally still logs the record. It seems to do a WRITE and then a COMMAND and both contain the entire record.

Is there anyway to ensure the document never gets written to the log while still having useful logging?

Thanks

systemLog:
  quiet: true
  destination: file
  path: /var/log/mongodb.log
  logAppend: true
  logRotate: rename
  traceAllExceptions: false
  timeStampFormat: iso8601-utc
  verbosity: 1 # This will be inherited by any component with verbosity -1
  component:
    accessControl:
      verbosity: -1 # NOTE: Negative one (-1) means "inherit"
    command:
      verbosity: 0 # MUST BE ZERO!!! Otherwise, inserted/updated records (all the data) will get logged.
    control:
      verbosity: -1
    geo:
      verbosity: 0
    index:
      verbosity: -1
    network:
      verbosity: -1
    query:
      verbosity: -1
    replication:
      verbosity: -1
    sharding:
      verbosity: 0
    storage:
      verbosity: -1
    write:
      verbosity: 0 # MUST BE ZERO!!! Otherwise, inserted/updated records (all the data) will get logged.

Version and Logs look like this. Please note I typed the data in so any invalid json or typos are due to me not mongo.

Version 3.0.6

TIMESTAMP I WRITE [conn0001] insert project.collection query {<insert our json document here>}
ninserted:1 
keyUpdates:0
writeConflicts:0
numYields:0
locks:{Global: {acquireCount: {r: 2, w: 2}}, MMAPV1Journal: {acquireCount: {w:2},aquireWaitCount: {w:2}, 
timeAquiringMicros: {w: 119326}}, Database: {acquireCount:w: 2}}, Collection" {acquireCount: {W:1}}, oplog: {acquireCount: {w: 1}}} 119ms



TIMESTAMP I COMMAND [conn0001] insert project.$cmd command:  insert {<insert our json document here>}
ninserted:1 
keyUpdates:0
writeConflicts:0
numYields:0
reslen: 80
locks:{Global: {acquireCount: {r: 2, w: 2}}, MMAPV1Journal: {acquireCount: {w:2},aquireWaitCount: {w:2}, 
timeAquiringMicros: {w: 119326}
timeAquiringMicros: {w: 119326}}, Database: {acquireCount:w: 2}}, Collection" {acquireCount: {W:1}}, oplog: {acquireCount: {w: 1}}} 119ms

There are several kernel messages printed to the console during boot time. I do not want the messages with loglevel "KERN_WARNING" to printed to the console. I only want the loglevels above "KERN_WARNING" like "KERN_ERR" to be printed to the console during boot time. When and where should i make changes to get this done. Do the changes have to be made during build time of kernel? Where should i make the changes to change the loglevel.?

I am using WindRiver Linux on PowerPC in an embedded environment. The boot loader i am using is uboot.

When i do ps -eaf, i cannot find the klogd daemon as well.

Is it possible to setup Loglevel so that it will ignore a specific module, such as ssl_engine_io.c ?