[
https://issues.apache.org/jira/browse/JAMES-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
René Cordier updated JAMES-3731:
--------------------------------
Description:
A user reported on gitter that he could not run the docker-compose of the James
distributed server:
https://github.com/apache/james-project/blob/master/server/apps/distributed-app/docker-compose.yml
After investigation, it seems the latest image of the distributed server, when
starting, gets stuck during the loading phase and can't finish its startup.
Last log observed is:
{code:bash}
[INFO ] o.a.j.CONFIGURATION - Load configuration file
/root/conf/webadmin.properties
{code}
Then nothing... There is still a few things to load (like JMX, thus why the
james-cli can't work) and normally when the server is ready there should be a
log about it.
We need to investigate what happens and fix it.
We also should make clear in the docker-compose that james needs to have a
volume binded with a generated keystore as well (or/and add a docker-compose
section in the README).
We should probably check the other flavors of James too while we are at it to
make sure no others are impacted by the same issue.
Thanks to Rajesh Sundaram for the report!
was:
A user reported on gitter that he could not run the docker-compose of the James
distributed server:
https://github.com/apache/james-project/blob/master/server/apps/distributed-app/docker-compose.yml
After investigation, it seems the latest image of the distributed server, when
starting, gets stuck during the loading phase and can't finish its startup.
Last log observed is:
```
[INFO ] o.a.j.CONFIGURATION - Load configuration file
/root/conf/webadmin.properties
```
Then nothing... There is still a few things to load (like JMX, thus why the
james-cli can't work) and normally when the server is ready there should be a
log about it.
We need to investigate what happens and fix it.
We also should make clear in the docker-compose that james needs to have a
volume binded with a generated keystore as well (or/and add a docker-compose
section in the README).
We should probably check the other flavors of James too while we are at it to
make sure no others are impacted by the same issue.
Thanks to Rajesh Sundaram for the report!
> Issue with distributed docker image latest release
> --------------------------------------------------
>
> Key: JAMES-3731
> URL: https://issues.apache.org/jira/browse/JAMES-3731
> Project: James Server
> Issue Type: Bug
> Affects Versions: 3.7.0
> Reporter: René Cordier
> Priority: Major
>
> A user reported on gitter that he could not run the docker-compose of the
> James distributed server:
> https://github.com/apache/james-project/blob/master/server/apps/distributed-app/docker-compose.yml
> After investigation, it seems the latest image of the distributed server,
> when starting, gets stuck during the loading phase and can't finish its
> startup. Last log observed is:
> {code:bash}
> [INFO ] o.a.j.CONFIGURATION - Load configuration file
> /root/conf/webadmin.properties
> {code}
> Then nothing... There is still a few things to load (like JMX, thus why the
> james-cli can't work) and normally when the server is ready there should be a
> log about it.
> We need to investigate what happens and fix it.
> We also should make clear in the docker-compose that james needs to have a
> volume binded with a generated keystore as well (or/and add a docker-compose
> section in the README).
> We should probably check the other flavors of James too while we are at it to
> make sure no others are impacted by the same issue.
> Thanks to Rajesh Sundaram for the report!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
