Timeline for Single-machine install and capabilites
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 6, 2017 at 12:28 | comment | added | Nuno Linhares♦ | If a service auto-registers, it will not show in the Conf, only if you query the service. The warnings are because the scripts are waiting for the service to respond, but while installing it takes a few seconds (maybe up to 40-50 seconds) until the services are up & running. | |
| Mar 6, 2017 at 8:53 | comment | added | Neil | Why is it during installation of these services I always see "WARNING: TCP connect to localhost:xxx failed" ??? | |
| Mar 6, 2017 at 8:51 | comment | added | Neil | Am I right in thinking that its not the case that the Discovery service should have all capabilities listed in its storage file - each role should auto-register with the Discovery database as its installed. I think I was expecting the Discovery services storage file to have all the capabilities defined within it. | |
| Mar 5, 2017 at 17:33 | comment | added | Pankaj Gaur | I may be missing something, but I just compare the cd_Storage_config from the installer package with the one in the discovery service install - and just copy pasted the Web Capability roles as it is from their follower by discovery service registration | |
| Mar 5, 2017 at 12:52 | comment | added | Nuno Linhares♦ | The web capability missing is the harder to fix - basically you need to add it to storage Conf yourself. To fix the -auto-register switch missing just run quick-install again, but add the switch. The script will reinstall the services with the new parameters | |
| Mar 5, 2017 at 8:15 | history | answered | Pankaj Gaur | CC BY-SA 3.0 |