you updated the secure file w/ the host specific entries on all appservers and then restarted the appserver service ?
Are your appservers configured to use themselves as an NSH proxy ? If not, that might work
It is probably worth pointing out as this is a post about alternate ports that if you managed servers are behind a SOCKS proxy they will not work as 4750 is hardcoded in the SOCKS call from the app server
Bill - Tried the restarting the appserver services, the logs for the usp and snapshot jobs now reflect the proper port '104750' but are still failing to connect.
Here is a sample
Error Jan 24, 2014 12:53:46 PM Snapshot of target part '/System' of asset class type 'Hardware Information.Machine Summary' failed on target 'edcwappd213': Failed to connect to host213:104750
Yeah – what about nsh proxy/socks proxy as mike mentioned ? or you can live browse the same host ?
I can execute all of the below against the host successfully
- Live Browse
- Deploy Configuration Objects
- Deploy BL Packages
- Run Discovery Jobs
- Run Compliance Jobs
hmm. can you set the 'debug_mode_enabled = true' property on a usp, then run the usp against it, then get the debug log from the appserver(s) that ran it (NSH/tmp/debug/...)
This looks important...
[24 Jan 2014 14:18:27,211] [WorkItem-Thread-8] [DEBUG] [me@DOMAIN.COM:BLAdmins:] [ServerProperty]  Provider processed method: getAsset
[24 Jan 2014 14:18:27,289] [WorkItem-Thread-8] [DEBUG] [me@DOMAIN.COM:BLAdmins:] [ServerProperty]  Couldn't find proxy server for servername= HOST213
[24 Jan 2014 14:18:27,289] [WorkItem-Thread-8] [ERROR] [me@DOMAIN.COM:BLAdmins:] [ServerProperty]  port out of range:104750
java.lang.IllegalArgumentException: port out of range:104750
I have more if you want it, but this looked most relevant
I though the high port range capped at 65536 ? so can you use a lower port ?
Boom that was it! Set the alternate port configs to 14750, restarted appserver services.
Tested USP - works
Tested Snapshot - works