-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
None
-
None
From Scott McCulley,
I ran in to some difficulties during the install of Crowd. I thought I might bring them up to as something to address in your next release.
1) During the configuration of the default admin, the application attempts to resolve the hostname of the server. If it fails, it reports error. But before it does, it adds the user and group to the DB so it is impossible to re-use that admin user or create a new one, since the group already exists.
Question:
Is it really necessary to attempt to resolve the hostname of the server? What if (and I am) using a different name to access Crowd, and it isn't the name of the server??
Suggestion:
1) Ask for the name of the server (actually, I think you do.) Then use that server name instead of attempting to use the hostname. 2) Don't create the user if you intend to fail. Or if you fail, drop the user from the DB, so it can be re-used later. 3) Same goes for the admin group as well...
Error log:
2011-09-18 19:34:20,050 http-8095-1 INFO [console.action.setup.SelectSetupStep] Current setup step is /console/setup/directoryinternalsetup.action
2011-09-18 19:34:24,651 http-8095-1 INFO [console.action.setup.SelectSetupStep] Current setup step is /console/setup/defaultadministrator.action
2011-09-18 19:34:46,700 http-8095-1 ERROR [console.action.setup.DefaultAdministrator] web3.cardboard-box.com: web3.cardboard-box.com
java.net.UnknownHostException: web3.cardboard-box.com: web3.cardboard-box.com
at java.net.InetAddress.getLocalHost(InetAddress.java:1360)
at com.atlassian.crowd.console.action.setup.DefaultAdministrator.addCrowdApplication(DefaultAdministrator.java:213)
at com.atlassian.crowd.console.action.setup.DefaultAdministrator.doUpdate(DefaultAdministrator.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CWD-2665] Installation creates username and groups when it fails to resolve local host name.
| Workflow | Original: Simplified Crowd Development Workflow v2 - restricted [ 1511064 ] | New: JAC Bug Workflow v3 [ 3365565 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Simplified Crowd Development Workflow v2 [ 1393085 ] | New: Simplified Crowd Development Workflow v2 - restricted [ 1511064 ] |
| Workflow | Original: Crowd Development Workflow v2 [ 344939 ] | New: Simplified Crowd Development Workflow v2 [ 1393085 ] |
| Remote Link | New: This issue links to "Wiki Page (Extranet)" [ 34483 ] |
Um: just to be clear - 'crowd-trial' in the message is the actual hostname of the machine I was trying to install onto.
What about sneaking a little more info into the message? eg:
Unable to resolve this machine's hostname into an IP address. Thus Crowd cannot complete its installation. Please ensure [hostname] resolves to an IP address then reload this web page to continue the installation. For more see https://jira.atlassian.com/browse/CWD-2665 .
Where [hostname] is the machines actual hostname...
Again, thanks for the fast turn around 
Fair point. The message is now:
Unable to resolve this machine's hostname. Please ensure 'crowd-trial' resolves to an IP address.
I appreciate the prompt turnaround. Mind you, 'cryptic error' doesn't fill my heart with joy 
I think that Alan Cooper's dictum of if you have to issue an error message then tell the user
1) what went wrong
2) how they are affected
3) what they can do to solve the problem
4) where they can go for more information
is a good one to follow: especially in an installation wizard that is the first view a user has of the product.
| Fix Version/s | New: 2.6 [ 25892 ] | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
(Yes, to be clear, the actual hostname of the machine is shown.)
Agreed, the setup process could be improved to offer more information. I've opened
CWD-3061to avoid scope-creep on this issue, and to allow for some more general improvements at the same time.