CODEWITHSUNDEEP
spring-bootlogging
Scott
Scott

Reputation: 505

Spring Boot log file not being created

I have a spring boot app (1.5.10.RELEASE) that logs great when running as a standalone application in Eclipse IDE. I am using spring config and the properties file says this:

logging.level.com.myco.impl=DEBUG
logging.path=/log/myService

When I run as a standalone application, I see everything I see logged to the console and to a file in the above directory (called spring.log).

I then build my "uber jar" and run in like this:

java -jar my-service-0.1.0.jar. I see all the console logging just like running in IDE. I can see it looking for my configuration in spring config but I do not see any log file created.

I could use some ideas on what to look at.

Upvotes: 1

Views: 6877

Answers (3)

stinger
stinger

Reputation: 4138

The issue may be a bug in Spring Boot 1.5.10, see: https://github.com/spring-projects/spring-boot/issues/11951 I've faced similar issue when application cannot run, because log file was owned by root user and not available to change by application user. Try to upgrade Spring Boot to 1.5.11 -- issue fixed in this version.

Upvotes: 0

Scott
Scott

Reputation: 505

See comments above. I did not include a jar I needed that was critical for reinitializing the logging system once it contacted spring cloud.

Upvotes: 0

Lachezar Balev
Lachezar Balev

Reputation: 12021

In short - I (almost :-) ) believe that you have not set proper permissions on the logging path as pointed in the comments. The logging configurations seem quite simple and are described here. You can't get these wrong easily and yours seem OK.

The tricky part is how to diagnose the exact problem. For example on my system if I change the owner of the logging directory I can reproduce the behaviour with the uber jar that you described.

Next - I guess we both use slf4j with logback (e.g. coming because of spring-boot-starter). The laziest and quickest approach to understand what's wrong is to print the logback status messages as explained here. For example - programatically - there are other options too but I'll take the dirtiest :-) . Put this somewhere in your code:

LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory();
// print logback's internal status
StatusPrinter.print(lc);

LOGGER.debug("Some other message");

If I do that in my sample app (boot 1.5.10.RELEASE) I can immediately see the problem printed in the console along with many more status messages:

23:23:07,857 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - openFile(/tmp/so/spring.log,true) call failed. java.io.FileNotFoundException: /tmp/so/spring.log (Permission denied)
    at java.io.FileNotFoundException: /tmp/so/spring.log (Permission denied)

Upvotes: 2

Related Questions