How to monetdb log settings (merovingian.log) - monetdb

How to MonetDB log settings.
I want to change the log level of "merovingian.log".
I want to output the ERROR and WARN the merovingian.log.
But now merovingian.log is outputting only MSG log.
2016-07-22 18:12:03 MSG merovingian[7825]: proxying client x.x.x.x:51609 for database 'test' to mapi:monetdb:///var/MonetDB/dbfarm/test/.mapi.sock?database=test
2016-07-22 18:12:03 MSG merovingian[7825]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying
OS is "CentOS 6.4",
MonetDB version is "MonetDB-11.19.7".
Any advice how to solve this problem?

No fine-tuning is provided in where log information ends up.

Related

Reg: database is not starting up an error

getting below error while starting the database:-
startup
ORA-01078: failure in processing system parameters
ORA-01565: error in identifying file '+DATA/mis/PARAMETERFILE/spfile.276.967375255'
ORA-17503: ksfdopn:10 Failed to open file +DATA/mis/PARAMETERFILE/spfile.276.967375255
ORA-04031: unable to allocate 56 bytes of shared memory ("shared pool","unknown object","KKSSP^24","kglseshtSegs")
Your database cannot find the SPFILE (newer init.ora) within ASM with the actual system parameters or has no permissions to access it.
Either your Grid Infrastructure stack or the dbs/spfile.ora is pointing to the wrong file.
To find out what the grid infrastructure stack is using, run "srvctl" which should display the parameterfile name the database should be using
srvctl config database -d <dbname>
...
Spfile: +DATA/<dbname>/PARAMETERFILE/spfile.269.1066152225
...
Then check (as the grid user), if the file indeed is not visible (by using asmcmd):
asmcmd
ASMCMD> ls +DATA/<dbname>/PARAMETERFILE/
spfile.269.1066152225
If the name is different, then you got the issue... (and you have to point to the correct file).
If the name is correct, then it could be wrong permissions on the oracle executable(s) (check My Oracle Support):
RAC Database Can't Start: ORA-01565, ORA-17503: ksfdopn:10 Failed to open file +DATA/BPBL/spfileBPBL.ora (Doc ID 2316088.1)

Artifactory decrypt passwords in debug mode

Setup:
Artifactory 7.33.12 with pro license
(satellite pass-though multiple Artifactorys)
Ubuntu 20.04 LTS
i switched all my artifactories to debug mode with logback.xml.
I changed all entries with level:info or with level:warn to level:debug
After these changes the artifactory server have began
right away to show passwords in plaintext: We have local and ldap user
Log snipped:
2022-04-04T10:46:57.758Z [jfrt ] [DEBUG] [bf2d7f554f68c503] [o.a.h.wire:87 ] [ttp-nio-8080-exec-75] - http-outgoing-145231 >> "{"username":"username1","password":"plaintext"}"
2022-04-04T10:00:59.763Z [jfrt ] [DEBUG] [e227b7e38f035f2b] [o.a.h.wire:87 ] [tp-nio-8080-exec-150] - http-outgoing-143844 >> "{"username":"username2","password":"plaintext"}"
The plaintext passwords was generated always if a user entered a wrong password (failed login)
this password was then in the artifactory logs in plaintext.
I switched immediately the logback.xml to level: warn and info and the passwords was encrypted again. Following log message looks weird:
./router-request.log:{"BackendAddr":"localhost:8040","ClientAddr":"127.0.0.1:38458","DownstreamContentSize":216532,"DownstreamStatus":200,"Duration":164389727,"RequestMethod":"GET","RequestPath":"/access/api/v1/users/?expand=passwords\u0026expand=encryptedData","StartUTC":"2022-04-08T09:52:53.86050316Z","level":"info","msg":"","request_Uber-Trace-Id":"28f3f17dc93f35c6:1b30ff214f5c8529:178287af7a330c6e:0","request_User-Agent":"JFrog Access Java Client/7.35.0 73500900 Artifactory/7.33.12 73312900","time":"2022-04-08T11:52:54+02:00"}
Did anyone know why this happened? Is that a bug?
I cant believe that was a intended behavior.
A production system can not display passwords in plaintext.
Anyone a Idea?
Please help

Oracle HTTP Server "File name too long" ERROR

I am using Oracle HTTP Server.
I would like to ask about my server log file. I saw an ERROR in my log file example like this:
[OHS] [ERROR:32] [AH00127] [core] [client_id: 10.10.10.10] [host_id: example] [host_addr: 10.10.10.10] [pid: 111111] [tid: 111111] [user: web] [ecid: 111111] [rid: 0] [VirtualHost: example.com.tr:5555] (36)File name too long: AH00127: Cannot map GET /example/...
This Error does not occur another Load Balancer. But I get in Oracle HTTP Server in a specific context path.
I know the solution for change the Linux file System limit from "255". But don't want to change the whole server for this particular error.
Any idea to fix this problem?

Trying to Connect Vertica DB with Weblogic 10.3

Working on Linux Redhat
I have two below jars
1>vertica-jdbc-5.1.1.jar
2>vertica-jdk5-6.1.1-0.jar
Steps that i followed:
1 copied the jars to $WL_HOME/server/lib
2 I set the path of the jars to Linux Path like below
export WL_HOME=/usr/local/WL_Server10.3/sever
PATH= ${WL_HOME}/lib:${PATH}
3 I modified ${WL_HOME}/common/bin/commEnv.sh
Added my jars entry like below
# set up WebLogic Server's class path
WEBLOGIC_CLASSPATH="${JAVA_HOME}/lib/tools.
jar${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic_sp.
jar${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic.
jar${CLASSPATHSEP}${FEATURES_DIR}/weblogic.server.modules_13.1.1.0.
jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.
jar${CLASSPATHSEP}${ANT_HOME}/lib/ant-all.
jar${CLASSPATHSEP}${ANT_CONTRIB}/lib/ant-contrib.jar
${CLASSPATHSEP}${WL_HOME}/server/lib/vertica-jdbc-5.1.1.jar
${CLASSPATHSEP}${WL_HOME}/server/lib/vertica-jdk5-6.1.1-0.jar"
export WEBLOGIC_CLASSPATH
//I also tried the below steps googling,................. Optional Step
4> Modified ${WL_HOME}/server/lib/jdbcdrivers.xml
Added required parameter
i didnt get what to fill in the URLClassPathName value so i ignored it.
5>I restarted the Weblogic server and logged into the admin console
6> I added new JDBC Data Source
While Testing the Connection i am getting below Error:
Message icon - Error An error occurred during activation of changes, please see the log for details.
Message icon - Error weblogic.application.ModuleException:
Message icon - Error weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: [Vertica][JDBC](10100) Connection Refused: (11640) Required Connection Key(s): user; (11480) Optional Connection Key(s): autocommit, connsettings, directbatchinsert, logintimeout, loglevel, lognamespace, logpath, readonly, resultbuffersize, sessionlabel, ssl, threepartnaming, transactionisolation
It would be great if someone can help me with the steps to connect Vertica Database to the Weblogic 10.3
What connection settings are you providing in:
"6> Added new JDBC Data Source
7>Followed the steps"
The error says you're missing specificying a user:
[Vertica][JDBC](10100) Connection Refused:
(11640) Required Connection Key(s): user;
(11480) Optional Connection Key(s): autocommit, connsettings, directbatchinsert, logintimeout, loglevel, lognamespace, logpath, readonly, resultbuffersize, sessionlabel, ssl, threepartnaming, transactionisolation

How can I disable console messages when running maven commands?

I'm in the process of executing Maven commands to run tests in the console (MacOSX). Recently, development efforts have produced extraneous messages in the console (info, debug, warning, etc.) I'd like to know how to remove messages like this:
INFO c.c.m.s.c.p.ApplicationProperties - Loading application properties from: app-config/shiro.properties
I've used this code to remove messages from the dbunit tests:
ch.qos.logback.classic.Logger Logger = (ch.qos.logback.classic.Logger)LoggerFactory.getLogger("org.dbunit");
Logger.setLevel(Level. ERROR);
However, I'm unsure how to disable these additional (often verbose and irritating) messages from showing up on the console so that I can see the output more easily. Additional messages appear as above and these:
DEBUG c.c.m.s.c.f.dao.AbstractDBDAO - Adding filters to the Main Search query.
WARN c.c.m.s.c.p.JNDIConfigurationProperties - Unable to find JNDI value for name: xxxxx
INFO c.c.m.a.t.d.DatabaseTestFixture - * executing sql: xxxxx
The successful answer was:
SOLUTION: Solution to issue IS adding a 'logback-test.xml' file to the root of my test folder. I used the default contents (as instructed by the documentation - thanks #Charlie). Once file exists there, FIXED!

Resources