Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hawkbit Server Docker container getting Exited immediately after start in WSL #1494

Open
PrabhjeetSingh90 opened this issue Nov 29, 2023 · 5 comments

Comments

@PrabhjeetSingh90
Copy link

Hello,

we are observing Hawkbit Server Docker container getting Exited immediately after start in WSL. This is not reproducing Consistently but it is quite frequent. Here is the command that we are using to bring up the container in WSL linux Distibution(Ubuntu 20.04)

wsl docker run -d --name hawkbit-server -p 8080:8080 hawkbit/hawkbit-update-server:latest --hawkbit.server.ddi.security.authentication.gatewaytoken.enabled=true --hawkbit.server.ddi.security.authentication.gatewaytoken.key=%s

Is there any way we can debug this ?

Does anyone have seen this in your end?

Let us know if you need further info.

@strailov
Copy link
Contributor

Hey @PrabhjeetSingh90
Are there any logs from hawkbit in the container ?
Or any logs at all ?

@PrabhjeetSingh90
Copy link
Author

Hey @strailov

This is the only logs we have from exited container


| | | () | | | | | _ () |
| |
| | _ __ ___ ___ | | __ ___ | | | |) || |_
| | / | | | ' / |/ _ \ | ' \ / ` \ \ /\ / / |/ / _ <| | |
| |
| (
| | | |) _ \ / | | | | (| |\ V V /| <| |) | | |_
|
_||| ./|/_| || ||_,| _/_/ ||__/||_|
| |
|
|

Eclipse hawkBit Update Server (v0.3.0M9)
using Spring Boot (v2.7.14)

Go to https://www.eclipse.org/hawkbit for more information.

2023-11-09 10:09:28.476 INFO 1 --- [ main] org.eclipse.hawkbit.app.Start : Starting Start v0.3.0M9 using Java 17.0.7 on f431221626d8 with PID 1 (/opt/hawkbit/hawkbit-update-server.jar started by root in /opt/hawkbit)
2023-11-09 10:09:28.485 INFO 1 --- [ main] org.eclipse.hawkbit.app.Start : No active profile set, falling back to 1 default profile: "default"
2023-11-09 10:09:32.535 INFO 1 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode.
2023-11-09 10:09:33.276 INFO 1 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 713 ms. Found 20 JPA repository interfaces.
2023-11-09 10:09:33.957 INFO 1 --- [ main] faultConfiguringBeanFactoryPostProcessor : No bean named 'errorChannel' has been explicitly defined. Therefore, a default PublishSubscribeChannel will be created.
2023-11-09 10:09:33.991 INFO 1 --- [ main] faultConfiguringBeanFactoryPostProcessor : No bean named 'integrationHeaderChannelRegistry' has been explicitly defined. Therefore, a default DefaultHeaderChannelRegistry will be created.
2023-11-09 10:09:34.046 INFO 1 --- [ main] o.s.c.a.ConfigurationClassPostProcessor : Cannot enhance @configuration bean definition 'com.vaadin.spring.VaadinConfiguration' since its singleton instance has been created too early. The typical cause is a non-static @bean method with a BeanDefinitionRegistryPostProcessor return type: Consider declaring such methods as 'static'.
2023-11-09 10:09:34.484 INFO 1 --- [ main] o.s.cloud.context.scope.GenericScope : BeanFactory id=08587022-8fdf-3556-ac8f-8c6e9d596f92
2023-11-09 10:09:34.883 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.jdbc.DataSourceConfiguration$Hikari' of type [org.springframework.boot.autoconfigure.jdbc.DataSourceConfiguration$Hikari] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-09 10:09:34.903 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.commons.config.CommonsConfigAutoConfiguration' of type [org.springframework.cloud.commons.config.CommonsConfigAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-09 10:09:34.906 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.client.loadbalancer.LoadBalancerDefaultMappingsProviderAutoConfiguration' of type [org.springframework.cloud.client.loadbalancer.LoadBalancerDefaultMappingsProviderAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-09 10:09:34.907 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'loadBalancerClientsDefaultsMappingsProvider' of type [org.springframework.cloud.client.loadbalancer.LoadBalancerDefaultMappingsProviderAutoConfiguration$$Lambda$566/0x0000000801494a50] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-09 10:09:34.912 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'defaultsBindHandlerAdvisor' of type [org.springframework.cloud.commons.config.DefaultsBindHandlerAdvisor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-09 10:09:34.945 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration' of type [org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-09 10:09:34.947 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'stringOrNumberMigrationVersionConverter' of type [org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration$StringOrNumberToMigrationVersionConverter] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-09 10:09:34.985 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'spring.datasource-org.springframework.boot.autoconfigure.jdbc.DataSourceProperties' of type [org.springframework.boot.autoconfigure.jdbc.DataSourceProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-09 10:09:35.032 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'dataSource' of type [com.zaxxer.hikari.HikariDataSource] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-09 10:09:35.047 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'spring.jpa-org.springframework.boot.autoconfigure.orm.jpa.JpaProperties' of type [org.springframework.boot.autoconfigure.orm.jpa.JpaProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-09 10:09:35.088 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.eclipse.hawkbit.repository.jpa.RepositoryApplicationConfiguration' of type [org.eclipse.hawkbit.repository.jpa.RepositoryApplicationConfiguration$$EnhancerBySpringCGLIB$$98ca0bec] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-09 10:09:35.566 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'UISecurityConfigurationAdapter.UIMethodSecurity' of type [org.eclipse.hawkbit.ui.autoconfigure.UISecurityConfigurationAdapter$UIMethodSecurity$$EnhancerBySpringCGLIB$$8243815e] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-09 10:09:35.761 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.vaadin.spring.events.config.EventBusConfiguration' of type [org.vaadin.spring.events.config.EventBusConfiguration$$EnhancerBySpringCGLIB$$9439808d] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-09 10:09:35.772 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.vaadin.spring.security.config.VaadinSharedSecurityConfiguration' of type [org.vaadin.spring.security.config.VaadinSharedSecurityConfiguration$$EnhancerBySpringCGLIB$$5ff87614] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-09 10:09:36.927 INFO 1 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8080 (http)
2023-11-09 10:09:36.949 INFO 1 --- [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat]
2023-11-09 10:09:36.953 INFO 1 --- [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.78]
2023-11-09 10:09:37.106 INFO 1 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext
2023-11-09 10:09:37.108 INFO 1 --- [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 8419 ms
2023-11-09 10:09:37.578 INFO 1 --- [ main] o.f.c.internal.license.VersionPrinter : Flyway Community Edition 8.5.13 by Redgate
2023-11-09 10:09:37.578 INFO 1 --- [ main] o.f.c.internal.license.VersionPrinter : See what's new here: https://flywaydb.org/documentation/learnmore/releaseNotes#8.5.13
2023-11-09 10:09:37.579 INFO 1 --- [ main] o.f.c.internal.license.VersionPrinter :
2023-11-09 10:09:37.616 INFO 1 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Starting...
2023-11-09 10:09:38.424 INFO 1 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Start completed.
2023-11-09 10:09:38.463 INFO 1 --- [ main] o.f.c.i.database.base.BaseDatabaseType : Database: jdbc:h2:mem:testdb (H2 2.2)
2023-11-09 10:09:38.537 WARN 1 --- [ main] o.f.c.internal.database.base.Database : Flyway upgrade recommended: H2 2.2.220 is newer than this version of Flyway and support has not been tested. The latest supported version of H2 is 2.1.210.
2023-11-09 10:09:38.616 INFO 1 --- [ main] o.f.core.internal.command.DbValidate : Successfully validated 45 migrations (execution time 00:00.053s)
2023-11-09 10:09:38.645 INFO 1 --- [ main] o.f.c.i.s.JdbcTableSchemaHistory : Creating Schema History table "PUBLIC"."schema_version" ...
2023-11-09 10:09:38.731 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Current version of schema "PUBLIC": << Empty Schema >>
2023-11-09 10:09:38.783 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.0.1 - init "
2023-11-09 10:09:38.938 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.2.0 - update target info for message "
2023-11-09 10:09:38.956 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.4.0 - cascade delete "
2023-11-09 10:09:38.990 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.4.1 - cascade delete "
2023-11-09 10:09:38.997 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.5.0 - target filter query "
2023-11-09 10:09:39.006 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.6.0 - rollout management "
2023-11-09 10:09:39.042 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.7.0 - swmType maxAssignment greater 0 "
2023-11-09 10:09:39.051 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.7.1 - reduce length enums "
2023-11-09 10:09:39.098 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.8.0 - auto assign ds filter "
2023-11-09 10:09:39.107 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.8.1 - cascade delete "
2023-11-09 10:09:39.121 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.8.2 - remove external artifact "
2023-11-09 10:09:39.132 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.9.0 - add rollout groups created "
2023-11-09 10:09:39.143 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.10.0 - advanced rolloutgroup "
2023-11-09 10:09:39.162 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.10.1 - consolidate artifact sha1 "
2023-11-09 10:09:39.178 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.10.2 - rollout auto start "
2023-11-09 10:09:39.194 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.10.3 - add rollout deleted flag "
2023-11-09 10:09:39.259 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.11.0 - drop target info "
2023-11-09 10:09:39.306 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.11.1 - target filter query UQ "
2023-11-09 10:09:39.311 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.11.2 - remove unused idexes "
2023-11-09 10:09:39.316 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.11.3 - add module md targetvis "
2023-11-09 10:09:39.325 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.0 - action performance "
2023-11-09 10:09:39.369 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.1 - missing non null "
2023-11-09 10:09:39.387 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.2 - missing non null enum "
2023-11-09 10:09:39.393 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.3 - cascade delete "
2023-11-09 10:09:39.398 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.4 - add maintenance window "
2023-11-09 10:09:39.419 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.6 - add index "
2023-11-09 10:09:39.425 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.7 - add rollout approval fields "
2023-11-09 10:09:39.440 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.8 - change length of created last modified by "
2023-11-09 10:09:39.452 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.9 - add target metadata "
2023-11-09 10:09:39.462 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.10 - change length of target attributes key "
2023-11-09 10:09:39.473 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.11 - add auto assign action type "
2023-11-09 10:09:39.484 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.12 - change length of controller id and name "
2023-11-09 10:09:39.491 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.13 - add action external id "
2023-11-09 10:09:39.500 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.14 - add sha256 hash "
2023-11-09 10:09:39.514 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.15 - add weight "
2023-11-09 10:09:39.540 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.16 - add action initiated by "
2023-11-09 10:09:39.552 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.17 - add index target modified "
2023-11-09 10:09:39.557 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.18 - add target type "
2023-11-09 10:09:39.572 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.19 - add valid flag to ds "
2023-11-09 10:09:39.583 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.20 - add encryption flag to sm "
2023-11-09 10:09:39.598 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.21 - add rollouts status index "
2023-11-09 10:09:39.603 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.22 - change target type name length "
2023-11-09 10:09:39.608 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.23 - add action status code "
2023-11-09 10:09:39.615 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.24 - add last action status code "
2023-11-09 10:09:39.625 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Migrating schema "PUBLIC" to version "1.12.25 - add confirmation flag "
2023-11-09 10:09:39.661 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Successfully applied 45 migrations to schema "PUBLIC", now at version v1.12.25 (execution time 00:00.942s)
2023-11-09 10:09:40.545 INFO 1 --- [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default'

@strailov
Copy link
Contributor

strailov commented Dec 1, 2023

Hm, weird
Is this the last log - 2023-11-09 10:09:40.545 INFO 1 --- [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default'

From the logs everything seems okay ... But there is no 'Started' log for the hawkbit update server, so if this is the last log I guess something outside hawkbit kills the process before it even started somehow ...

@PrabhjeetSingh90
Copy link
Author

PrabhjeetSingh90 commented Dec 1, 2023

@strailov

The container is running a hawkbit server java application and I am assuming all the dependencies required to run the hawkbit server application is packaged with in the container image.

Does It have any dependencies on the environment or the host Machines that is running the container?

@strailov
Copy link
Contributor

strailov commented Dec 1, 2023

My first guess would be rabbitmq. You can check the dependency here - > hawkbit-runtime/docker/docker-compose-deps-mysql.yml

In your case you use it with default profile so mysql won't be necessary (it uses h2 under the hood)

But still if this is the problem why we do not see it from the hawkbit logs, and it won't happen from time to time it will happen consistently ...
So I still believe there is something outside hawkbit that is causing troubles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants