I'm using Jenkins 1.651 with the IRC Plugin 2.27 and
instant-messaging plugin 1.35.
I've noticed that the IRC plugin logs a lot of INFO level messages to the Jenkins log (GUI and on-disk). I'd like to configure logging for this plugin, or disable logging for the plugin entirely.
I've tried adding a new log recorder for the logger hudson.plugins.ircbot, but the plugin still logged to the general Jenkins log. Any pointers?
I found this tweet:
https://twitter.com/russss/status/806560486166822915
(You can fix by changing the level of org.pircbotx.InputParser to WARNING at /log/levels in the web interface. Thanks, pircbot...)
I can confirm this works, but the config doesn't seem to stick after you restart Jenkins. If anyone knows where to capture this to make it permanent, that would be great!
Edit: so not ideal, in so far as it knocks all Jenkins logging back to the level of WARNING or higher (no more INFO messages) but this is a permanent fix to the problem you can capture in code and config:
Add the following to JAVA_ARGS for Jenkins (we typically do this in /etc/default/jenkins) :
-Djava.util.logging.config.file=/var/lib/jenkins/logging.properties
Then create the file /var/lib/jenkins/logging.properties, containing the following:
handlers = java.util.logging.FileHandler, java.util.logging.ConsoleHandler
.level= WARNING
No more IRC messages in the Jenkins log!
This answer actually provided by my colleague, mig5
There is a bug https://issues.jenkins-ci.org/browse/JENKINS-46099 that asks for addressing this issue in a persistent way.
Related
All,
I am trying to install Solr 7.2.1. While the installation works, i am not able to run solr successfully. Whenever i try to run, i get the following error.
SolrCore Initialization Failures {{core}}: {{error}}
Please check your logs for more information
I am not sure exactly what the error is. i dont see anything in the logs either. all i see are are some info.
Please advice.
cmd solr.cmd start
or cmd solr.cmd stop -p 8983
doesn't have any issues.
i am running solr in 8982 port instead of the usual 8983. not sure if that makes a difference.
As mentioned by others, this problem is related to the javascript interface not related to the solr server. The same thing happened to me in Chrome. Clearing the site data worked for me.
Clear site data by opening developer tools and going to Application -> clear storage
Important Note:
The usage was 0B before and after clearing the site data but after clearing the site data solr home page came up without any error.
CTRL + F5 did the trick for me :-)
The issue is with the IE only, I have faced the same error. There was nothing in the logs as well. I finally Enabled the JavaScript for IE, Closed all the browser instance and tried again. And it is working perfectly fine for me.
Please refer below image for the reference.
I created Spring Boot + Google App Engine application. For development purpose I use IntelliJ IDEA and Google Cloud Tools plugin. I'm currently using only localDebug, which means I don't deploy anything on Google cloud. The configuration for debug is below:
I created a simple service to be sure if my code is updated on change or not:
static int i = 10;
#GetMapping(value = "/test")
public String test() {
return Integer.toString(++i);
}
Unfortunately when I change my code (e.g. from i = 10 to i = 100) and restart the app (I mean press on Rerun (Ctrl+F5) or Stop (Ctrl+F2) + Run my code doesn't apply on server, which means Idea doesn't rebuild the sources on server start. As you see on the screenshot above I even tried to add Build Project step to Before launch, which didn't work.
So to apply changes I need to execute from command line mvn appengine:run -> press Ctrl+C to stop it, switch to IDEA and start debug again which is a pain in the ass.
Another option is to use Hot Reload (Update application, Ctrl+F10). It recompiles only changed classes and reloads resources. This is a cool feature, but unfortunately it doesn't work in a lot of cases which makes me unable to use it as a reliable reload.
Is there anything I can do to force IDEA compile my sources? Is it a bug I should report to plugin developer. Or maybe appengine uses some additional remote sources that require explicit call of maven?
I finally found a solution. As I understood the Google cloud plugin just complies the classes into target/classes but when it starts the appEngine, the engine expected unpacked .war to be present under target/demo-0.0.1-SNAPSHOT.
E.g. if because if I delete both directories I get the error below:
To solve the issue I needed to compile those sources:
In toolbar Run -> Edit configuration
Select Google App Engine Standard Local server
In before launch add Build Artifact -> demo:war exploded where demo is the name of your App.
I'm on a Mac and I've installed the latest version of the App Engine PHP SDK (1.9.19 - 2015-04-13) which include support for XDebug (since 1.9.18).
I'm using the latest version of PHPStorm (8.0.3) with the GAE plugin.
I've no trouble to run my app through PHPStorm but I can't get the debugger working automatically (will explain what it means few lines below).
Each time I try to debug my app, the debugger pane stays saying "Waiting for incoming connection with ide key '11634' " (the ide key is always a random number).
No breakpoints are triggered, and when I stop the execution, a little red popup displays: "debug connection with xdebug was not established"...
I've tried what the Google documentation suggests and it didn't work either.
Finally after hours of trying almost anything (compiling my own version of XDebug, checking every conf file, overriding php.ini to ensure paths to XDebug is correct and XDebug is on, etc...) I found a "workaround"...
The only way I can't get the debugger to work is to launch the app, then go to the debugger pane to know what's the key it's waiting for (let's say "15981"), then go to my web browser and manually add XDEBUG_SESSION_START=15981 as parameter to the URL.
Since the key changed every run, it's really a pain to work like that, and I don't talk about page redirection, etc...
Is anyone having a thought on that?
Thanks
You can start local App Endine server with App Engine For PHP run configuration, just as in JetBrains tutorial.
Then please enable Listen to incoming connections (that phone with small bug on toolbar near run configurations, or in menu Run | Start Listening for PHP Debug Connections). Then reload the page in browser. Debugger should stop on the first breakpoint or on the first line of code if that setting is enabled.
Also feel free to watch or vote the issue on bugtracker.
#leneshka has the answer! I've been pulling my hair out trying to figure out how to get PHPStorm to use the xdebug.idekey value I specified in xdebug.ini.
As soon as I enabled Start Listening for PHP Debug Connections, I was able to start debugging with my personal xdebug.idekey value.
i'm trying to upload my app engine project for the very first time and i have no clue why it is not working. the error from my terminal is:
[me][~/Desktop]$ appcfg.py update ProjectDir/
Application: tacticalagentz; version: 1
Host: appengine.google.com
Starting update of app: tacticalagentz, version: 1
Scanning files on local disk.
Error 404: --- begin server output ---
This application does not exist (app_id=u'tacticalagentz').
--- end server output ---
i'm using python 2.6.5 and ubuntu 10.04.
not sure if this is relevant, but i just created a google app engine account today. and i also just created the application today (like a couple of hours ago). this is really frustrating because i just want to upload what i have so far (as a demo). in my app.yaml this is my first line:
application: tacticalagentz
Furthermore, i checked on my admin console, and i CLEARLY see the app id right there, and it matches letter for letter with the app id in my app.yaml
could someone please enlighten me and tell me what i am doing wrong? or is it something beyond my comprehension (like indexing issue with Google that they need time to index my app id) ?
thank you very much in advance
apparently adding the "--no_cookies" parameter will work
appcfg.py update --no_cookies ProjectDir/
the way i was able to find my answer was by uploading my app from my Mac OS X (thank god i have linux mac and windows). AppEngine on Mac OS X comes with a GUI interface, and it worked for uploading. so then i found the command they used in the console, which included "--no_cookies". perhaps if you run into similar issues in the future, this is one approach to getting the answer
App Engine for Java have the same problem. The problem is about account login.
If you are using Eclipse, use Sign In button.
If u are using command-line, use "-e" option, like this:
appcfg.sh -e your#email.com update yoursite/
I had the same problem. When I changed the name of the app I used in the launcher to match the one in the app engine, It worked without any problem. The way I figured out, it was the name mismatch which caused the problem. You can see the name of your registered app in the admin console of app engine.(https://appengine.google.com/)
Here's what fixed it for me:
i had an instance of dev_appserver.py myProjDirectory/ on a different terminal.
i guess the scripts are somehow linked and aren't thread safe
An alternate option that worked for me is to just "Clear Deployment Credential" from the Control option of the GUI. When the app was deployed after this, it opened a google page to allow GAE to access the user profile and then deployment was successful.
The key bit is
This application does not exist (app_id=u'tacticalagentz').
which is telling you that appspot.com doesn't know of an application by that name. The admin console (https://appengine.google.com/) shows your applications. Check there. You might have made an inadvertent typo when you registered the app.
I'd like eclipse to output debug level traces for my app and warning level traces for everything else.
Does not matter what I do in my WEB-INF/logging.properties, the only way to control logging level is through "Run" > "Debug Configurations...", select my app, then click on "GWT" tab and change logging level. The problem is that it sets debugging level for all loggers.
Is there a way to make it output debugging messages only for my app?
Here is how my WEB-INF/logging.properties looks like:
java.util.logging.ConsoleHandler.formatter=myproject.LogFormatter
# Set the default logging level for all loggers to WARNING
.level=WARNING
#org.datanucleus.level=WARNING
#org.apache.level=WARNING
#com.google.apphosting.level=WARNING
myproject.level=FINEST
# Set the default logging level for ORM, specifically, to WARNING
DataNucleus.JDO.level=WARNING
DataNucleus.Persistence.level=WARNING
DataNucleus.Cache.level=WARNING
DataNucleus.MetaData.level=WARNING
DataNucleus.General.level=WARNING
DataNucleus.Utility.level=WARNING
DataNucleus.Transaction.level=WARNING
DataNucleus.Datastore.level=WARNING
DataNucleus.ClassLoading.level=WARNING
DataNucleus.Plugin.level=WARNING
DataNucleus.ValueGeneration.level=WARNING
DataNucleus.Enhancer.level=WARNING
DataNucleus.SchemaTool.level=WARNING
It appears that Google broke logging somewhere around SDK 1.3.7 when they tried to combine the GWT and Appengine loggers. Here's the "Fixed" bug:
http://code.google.com/p/googleappengine/issues/detail?id=4011
Unfortunately they made the situation far worse - it appears there is no way to separate the GWT logging controls from the appengine logging controls, and the GWT logger ignores your logging.properties. The craziest part is that if you have a GAE app without GWT, you have no control over logging whatsoever - you can't set the threshold to DEBUG.
As far as I can tell, we're screwed until this issue gets resolved - and it hasn't even been Acknowledged yet:
http://code.google.com/p/googleappengine/issues/detail?id=4591
Please star that issue and throw tantrums on the appengine-java mailing list :-(