"socks server reports Connection refused"
Did you look at socks proxy log , if it has anything for why the connection was refused ?
What is xxxx hostname ? Is this a fileserver where the extended object script resides ? If yes, why is fileserver behind socks proxy ?
Or you have a routing rule which makes fileserver go through socks ?
Looking at the socks proxy log a connection refused comes up when the application server tries to contact itself via the proxy.
xxxx host is the BBSA application server and also the fileserver, and this server is not behind the proxy but trying to connect to remote/target hosts behind the proxy....Live browsing and other extended objects can be seen thru the proxy no problems but the Inventory template creates the Linux Configuration extended object which is having this issue....
The connection to the fileserver agent should not go though the socks proxy.
Check your routing rules, and make sure you exclude appserver and fileserver to go though the socks.
In this case, its trying to get the script os_config.nsh from the fileserver and it is going through socks and its getting denied,
what are your routing rules based on ?
The application/file server are not in the routing rules, the rule is based off a server property that is defined for the relevant servers that are in the location that requires the socks proxy...
Can you paste your routing rule ?
Iirc I think the proxy needs to be able to connect back to the file server or whatever has the EOs on it for this to work right.
Yes, That can happen, if the EO is remote based .
If the EO is central and runs on appserver, it should not connect via Proxy , I think so.
Is that the case with os_config.sh ?
The EO and the os_config.sh is on the application/fileserver which is local, the socks proxy is only being used to connect to the target server...
Well, Bill has raised a doubt in my mind about Proxy being able to connect back to Fileserver !
Have you added the fileserver/appserver as a managed agent in the servers, if yes, are you sure the property is not set on that and somehow your rule is not resulting in this ?
What OS is this ?
if your fileserver is configured as the host name "xxxx",
if you create an entry in the hosts file for xxxx to go to 127.0.0.1
For troubleshooting , this should avoid it to go via proxy
There was an issue like this where the proxy could not get back to the fileserver/appserver on 4750 and was causing errors like this. I think if you have the appserver setup to use a nsh proxy this doesn’t happen…
I do remember a similar issue, but I thought it was fixed somehow.
Once the app server is set up to use a nsh proxy the servers behind the socks proxy can be viewed via the extended objects but any server that is not behind the socks proxy takes forever to see the extended objects and almost kills the console and hitting the recourses on the application server very heavily.
And the local servers are not triggering the proxy rule ?
Only the remotes servers are going thru the socks proxy.....