Due Date |
---|
2017-04-06 |
-
I've fixed this issue during work on #4880. In fact wrong fields were annotated with
@ConfigField
and now it should be set as:http () { setup () { 'admin-user' = 'admin' 'admin-password' = 'tigase' } }
so for starting with scratch - we have no configuration and we want to launch setup - following config should be used:
'config-mode' = 'setup' http () { setup () { 'admin-user' = 'admin' 'admin-password' = 'tigase' } }
-
There seems to be something wrong with Kernel as latest nightly doesn't start with the provided config:
wojtek@atlantiscity.local ~/dev/tmps/tigase-server-dists/tigase-server-7.2.0-SNAPSHOT-b4759 $ less logs/tigase-console.log wojtek@atlantiscity.local ~/dev/tmps/tigase-server-dists/tigase-server-7.2.0-SNAPSHOT-b4759 $ cat etc/init.properties 'config-mode' = 'setup' http () { setup () { 'admin-user' = 'admin' 'admin-password' = 'tigase' } } wojtek@atlantiscity.local ~/dev/tmps/tigase-server-dists/tigase-server-7.2.0-SNAPSHOT-b4759 $ cat logs/tigase-console.log STARTED Tigase Wed Apr 5 13:05:09 -03 2017 componentInfo{Title=Tigase XMPP Server, Version=7.2.0-SNAPSHOT-b4759/e7432aa7 (2017-04-04/23:10:36), Class=tigase.xml.XMLUtils} componentInfo{Title=Tigase XMPP Server, Version=7.2.0-SNAPSHOT-b4759/e7432aa7 (2017-04-04/23:10:36), Class=tigase.util.ClassUtil} componentInfo{Title=Tigase XMPP Server, Version=7.2.0-SNAPSHOT-b4759/e7432aa7 (2017-04-04/23:10:36), Class=tigase.server.XMPPServer} 2017-04-05 13:05:09.794 [main] ConfiguratorAbstract.parseArgs() CONFIG: Setting defaults: --property-file = etc/init.properties 2017-04-05 13:05:11.767 [main] DNSResolverDefault.<init>() WARNING: Resolving default host name: localhost took: 11
Please see complete logs (attachment:logs.tar.gz) for details.
-
WIth the updated config I receive:
404 Not Found No context found for request
At any rate:
-
we should avoid flooding logs: #5208
-
before assigning the issue back for check please try next complete nightly build if it works for you.
-
-
OK, after a little chat - in setup mode only setup context is available (hence above error while navigating to http://localhost:8080/) - it works with http://localhost:8080/setup/
I think in setup mode we should have automatic redirect to the setup context.
And possibly in the log print information something like "please setup server at
Type |
Task
|
Priority |
Normal
|
Assignee | |
RedmineID |
4896
|