I have a non-Spring appliation. However, we are pulling in spring-security-config and spring-security-web. We use Log4j and have a log4j.properties file.
We want to log all the output from 'org.springframework' with the 'trace' log level.
We do not have an application.properties file, but can create one if we need one.
So, when I run my non-Spring app, all my code logs properyly, but I am not seeing anything from org.springframework in my logs.
Since Spring Security pulls in Spring Core, we created an application.properties on the classpath. We then setup a logging.file property to our log file. Then we setup some other logging property files to see if that would help. We also set debug=true as well.
So, I'll keep trying ....
Thanks in advance!
So, I found the problem. The logs were going to another log file in a different directory. I believe this is because it was a container log and not an application log.
Hope this helps someone else out.
Related
I tired a lot to run the application as production. I added in application.properties "vaadin.productionMode=true" but so the error "Failed to load content of './frontend/index.html'. It is required to have './frontend/index.html' file when using..." comes up. After I added in main/resources/META_INF/VAADIN/webapp the index.html with the content described in https://vaadin.com/docs/latest/fusion/application/starting#default-bootstrap-template-and-entry-point the error goes away the log files tells that the application has started in production ("Vaadin is running in production mode.") but unfortunately nothing is shown in the webbrowser.
Does anyone have an idea?
Thanks in advance,
Thomas
I'm very late to the party, but in addition to setting the vaadin.productionMode property, did you remember to run the Maven goal vaadin:build-frontend as well? (And vaadin:prepare-frontend, but that you probably already had in your development build.)
Documentation about enabling production mode: https://vaadin.com/docs/latest/flow/guide/production
I am trying to modify some APIs in MongooseIM and I want to see some logs. I tried adding lager-logging using MongooseIM, but the APIs stopped working after that.
If you have source code, you can add debug statement into it and compile it to beam file then replace the old file. The debug statement is to write some log into log file. I have used this method solving the problem in rabbitmq before.
I am trying to learn Grails and following along the guide on grails.org http://guides.grails.org/creating-your-first-grails-app/guide/index.html which to some extend works fine. My issue is, that I follow the guide to the dot, and when I come to part 4.4 about bootstrapping data. I fill in the code in the BootStrap.groovy file in the init folder.
When I then proceed to run my app and try to connec to the url localhost:8080 the site simply will not load. I can acces the dbconsole and see that the data is bootstrapped, so I guess the app is working to some extend. But the site wont load.
When I remove 2 of the Vehicles, the site loads fine. I have tried using grails-clean, and kill all processes on the port 8080, stille nothing helps.
Please help me with this, as I am stuck!
In your save method call, add failOnError: true. It's likely that something is failing when you try to save it. Also keep an eye on your console for error messages.
If that doesn't help, post some exact code.
One of the log files that i used regularly on my last server was the rails access.log
On our new host the file isn't supplying any data. I did a search and couldn't find any reference to the file. I'm wondering if needs to be configured and/or whether there are specific ownership/permission settings on the file that need to be in place.
Thanks for your help.
Access.log is usually written by the web server, not Rails. Check the apache or nginx or whatever config to find out where it's writing it. My guess is you're used to it being configured to be written in the same place as your rails logs, but now it isn't.
Anyone know where Mochiweb logs files by default? I'm running it along with the Beepbeep framework.
Mochiweb reports errors via the error_logger, so you can either write your own handler, or start SASL, and configure it to write a log file.
Aren't they kept in the priv directory next to mochiweb's start script?
Edit: Never mind, I'm wrong.
Mochiweb does not create log files as you would think it would. If you want to have apache-like logs, you'll have to roll your own.