Forum:

Spring

[Deployment]: Spring Boot deployment Systemd Service File Error Failed to configure a DataSource

Greenhorn

Posts: 5

posted 2 months ago

Number of slices to send:

Optional 'thank-you' note:

Send

Hi everyone I haven been struggle for 3 days with deploying Spring boot app on Linode Ubuntu Server, please help if you may, thanks in advance.

So, everything works with java -jar target/omi-0.0.1-SNAPSHOT.jar, all connections to the postgres works normal however when I try to run it with systemd/system/omi.service
I have also followed the Spring Boot Documentation, still no luck

I am facing this error. Classes and rest of stuff are posted after the log.
Error log -> Application.java -> BreafastConfiguration.java - > application.properties -> systemd/system/omi.service

Feb 29 17:33:22 personal-server java[60796]: ***************************
Feb 29 17:33:22 personal-server java[60796]: APPLICATION FAILED TO START
Feb 29 17:33:22 personal-server java[60796]: ***************************
Feb 29 17:33:22 personal-server java[60796]: Description:
Feb 29 17:33:22 personal-server java[60796]: Failed to configure a DataSource: 'url' attribute is not specified and no embedded datasource cou>
Feb 29 17:33:22 personal-server java[60796]: Reason: Failed to determine a suitable driver class
Feb 29 17:33:22 personal-server java[60796]: Action:
Feb 29 17:33:22 personal-server java[60796]: Consider the following:
Feb 29 17:33:22 personal-server java[60796]:         If you want an embedded database (H2, HSQL or Derby), please put it on the classpath.
Feb 29 17:33:22 personal-server java[60796]:         If you have database settings to be loaded from a particular profile you may need to acti>
Feb 29 17:33:22 personal-server systemd[1]: omi.service: Main process exited, code=exited, status=1/FAILURE
Feb 29 17:33:22 personal-server systemd[1]: omi.service: Failed with result 'exit-code'.

Application.java

BreakfastConfiguration

@Configuration
public class BreakfastDatasourceConfiguration{

private DataSource dataSource;
    @Bean
    @Primary
    @ConfigurationProperties("spring.datasource.breakfast")
    public DataSourceProperties breakfastDataSourceProperties() {
        return new DataSourceProperties();
    }

@Bean
    @Primary
    public DataSource breakfastDataSource() {
        return breakfastDataSourceProperties().initializeDataSourceBuilder().build();
    }

@Bean
    @Primary
    public JdbcTemplate breakfastJdbcTemplate( DataSource dataSource) {
        return new JdbcTemplate(dataSource);
    }

@Bean
    public JdbcClient breakfastJdbcClient( DataSource dataSource) {
        return JdbcClient.create(dataSource);
    }

@Bean(name="breakfastDataSourceInitializer")
    public DataSourceInitializer breakfastDataSourceInitializer(@Qualifier("breakfastDataSource") DataSource dataSource) {
        ResourceDatabasePopulator resourceDatabasePopulator = new ResourceDatabasePopulator();

/** postgres **/
        resourceDatabasePopulator.addScript(new ClassPathResource("schema-pg-breakfast.sql"));

DataSourceInitializer dataSourceInitializer = new DataSourceInitializer();
        dataSourceInitializer.setDataSource(dataSource);
        dataSourceInitializer.setDatabasePopulator(resourceDatabasePopulator);
        return dataSourceInitializer;
    }
}

application-production.properties

if you are all the way down here, thank you, and please let me know anything I should change that I can fix this problem.

Mikalai Zaikin

Bartender

Posts: 3915

posted 2 months ago

Number of slices to send:

Optional 'thank-you' note:

Send

could it be related to duplicated periods here:

David Ko

Greenhorn

Posts: 5

posted 2 months ago

Number of slices to send:

Optional 'thank-you' note:

Send

Thanks for replying, I did removed it but still have the same issue
are there any ways that I can debug it?

I have tried ExecStart and echo some variables but it all seems ok

Tim Holloway

Saloon Keeper

Posts: 27851

196

I like...

posted 2 months ago

1
Number of slices to send:

Optional 'thank-you' note:

Send

I don't recommend using environment variables to configure Java apps. And in the case of Spring Boot, I definitely don't, because that sort of stuff would be better off in a Spring Boot config file.

Here's the setup I use to run https://gourmetj.mousetech.com:

/etc/systemd/system/systemd gourmetj.service

runme.sh

Actually, the "nohup" is left over from before I set up systemd and should probably be removed.

/home/tomcat/application.properties

There's a whole raft of places to externally configure a Spring boot app, but I took this one since I didn't need it hidden out of sight or in some sort of global context, etc.

The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.

You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.

Tim Holloway

Saloon Keeper

Posts: 27851

196

I like...

posted 2 months ago

Number of slices to send:

Optional 'thank-you' note:

Send

Update: Yes, remove the "nohup" from the "runme.sh" and delete the "type=forking" from the service.

Himai Minh

Bartender

Posts: 2421

posted 2 months ago

1
Number of slices to send:

Optional 'thank-you' note:

Send

I think this one:
spring.datasource.breakfast.driver-class-name=org.postgresql.Driver
should be replaced by
spring.datasource.driver-class-name=org.postgresql.Driver

Tim Holloway

Saloon Keeper

Posts: 27851

196

I like...

posted 2 months ago

1
Number of slices to send:

Optional 'thank-you' note:

Send

OK, It appears that this app has multiple datasources.

In that case, the syntax should be like so:

However, I would like to repeat that it's NOT a good idea to hard-code that stuff into the systemd service file. As a general rule, you don't want to put customized/changeable data into an init script or systemd file. It's better to put it in an external config file like I did. Depending on your preferences, that can be in a config directory (for example, /etc/sysconfig for Red Hat, /etc/default for Debian), a product-specific directory like /var/lib/myproduct, an "/opt" product directory such as /opt/com/mousetech/gourmetj, or, as in my case, the same directory that the product itself lives in, since it's a trivial app.

The advantages are several. First, you can make it so that you don't need full administrator privileges to change things. Secondly, it's more in tune with general Best Practices (partly because of the preceding). Thirdly, you don't have to do a "systemctl daemon-reload" every time you alter the configuration. And finally, it keeps the actual service definition down to a generic minimum of statements.

Oh, and last, but not least, you have more flexibility in your configuration syntax. For example, "application.yml":

Try doing that in a systemd service file!

David Ko

Greenhorn

Posts: 5

posted 2 months ago

Number of slices to send:

Optional 'thank-you' note:

Send

Hi Tim and Himai,
Thanks for replying I didn’t realize there were replies, please correct if i misunderstood
And indeed i do have multiple data source

I want to point out that I have a docker compose file that create database breakfast and mesure when docker compose up, and my current situation is when I do Java -jar all the connection works fine, I have also put all my environment variables in my .bashrc (I am not sure am I wrong here)

The only problem is when I do systemctl start myservice, it just can’t recognize postgres breakfast, and when docker exec psql the database do exist.

So
1. i should not hard code any variables in Systemd service file
2. It is more flexible to use yml
3. I can place them in the config file (which I did myservice.d/myenv.conf)
Again thank you so much for answering my questions!

David Ko

Greenhorn

Posts: 5

posted 2 months ago

Number of slices to send:

Optional 'thank-you' note:

Send

Thank you so much for your time again, I just want post some update with my files
Only systemd service has this error, ./mvnw clean package; jar -jar target/omi:0.0.1-SNAPSHOT works just fine.

Mar 09 04:53:00 personal-server java[96283]: 2024-03-09T04:53:00.421Z ERROR 96283 --- [           main] o.s.b.d.LoggingFailureAnalysisReporter>
Mar 09 04:53:00 personal-server java[96283]: ***************************
Mar 09 04:53:00 personal-server java[96283]: APPLICATION FAILED TO START
Mar 09 04:53:00 personal-server java[96283]: ***************************
Mar 09 04:53:00 personal-server java[96283]: Description:
Mar 09 04:53:00 personal-server java[96283]: Failed to configure a DataSource: 'url' attribute is not specified and no embedded datasource cou>
Mar 09 04:53:00 personal-server java[96283]: Reason: Failed to determine a suitable driver class
Mar 09 04:53:00 personal-server java[96283]: Action:
Mar 09 04:53:00 personal-server java[96283]: Consider the following:
Mar 09 04:53:00 personal-server java[96283]:         If you want an embedded database (H2, HSQL or Derby), please put it on the classpath.
Mar 09 04:53:00 personal-server java[96283]:         If you have database settings to be loaded from a particular profile you may need to acti>

Current application-production.yml

/etc/systemd/system/omi.service.d/env.conf

/etc/systemd/system/omi.service

docker postgres running normal

dko@personal-server:~/omi$ docker-compose -f docker/docker-compose.yml up --build --detach
Starting docker_omi_pg_1 ... done
dko@personal-server:~/omi$ docker exec -it docker_omi_pg_1 psql -U postgres -d breakfast
psql (16.2)
Type "help" for help.

breakfast=#

Tim Holloway

Saloon Keeper

Posts: 27851

196

I like...

posted 2 months ago

Number of slices to send:

Optional 'thank-you' note:

Send

Well, the error message indicates a missing URL, but not much more. You have 3 datasources, so 3 URLs. However, only one datasource is configured in a way that Spring Boot's connection pool constructor can use it. The root of each datasource must be "spring/datasource", not "app/datasource".

Your environment file is also problematic, as it's in Windows ".ini" form, when it should be unix shell "source" form. Actually, it's not even truly valid for INI format. It seems to be a weird hybrid.

Also it's VERY bad to put the config file in /etc/systemd/system. Better locations would be "/etc/sysconfig/namex", "/var/lib/namex/" or "opt/something/namex", where the reasonable value of "namex" would be the name of the service that uses it, and "something" is your choice, although I like something like "/opt/com/coderanch" to point out that it's an app specific to my domain. In Ubuntu/Debian, instead of /etc/sysconfig/namex, I think the standard location is something like "/etc/default" and I have no idea what MacOS uses.

Tim Holloway

Saloon Keeper

Posts: 27851

196

I like...

posted 2 months ago

Number of slices to send:

Optional 'thank-you' note:

Send

Also, Docker doesn't run under Systemd like that. A Docker container must be controlled by a "docker" command. You cannot simply put a "java jar" command in a systemd file to run a Docker container.

A Docker container for a systemd base image such as CentOS, is even more problematic. Systemd and Docker don't naturally fit together, so various contortions need to be performed to get systemd working inside a docker container.

David Ko

Greenhorn

Posts: 5

posted 2 months ago

Number of slices to send:

Optional 'thank-you' note:

Send

Tim Holloway wrote:Also, Docker doesn't run under Systemd like that. A Docker container must be controlled by a "docker" command. You cannot simply put a "java jar" command in a systemd file to run a Docker container.

A Docker container for a systemd base image such as CentOS, is even more problematic. Systemd and Docker don't naturally fit together, so various contortions need to be performed to get systemd working inside a docker container.

Thank you Tim, no wonder by my docker doesn't work like that, I have done some google search, I have complete changed to run the spring boot from docker-compose as well, thank you for helping out!

Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters?

[Deployment]: Spring Boot deployment *Systemd Service File* Error Failed to configure a DataSource

[Deployment]: Spring Boot deployment Systemd Service File Error Failed to configure a DataSource