Anonymous_User Absent Member.
Absent Member.
2460 views

Unable to appropriately configure proxy accounts

HI guys

I have NSM 2 running in both of my production trees.
Had some issues 'unable to connect to nsm engine' on one, but that turned
out to be httpstk not listening on the ssl port 8009. I deleted the ssl
certs, ran pkidiag, and restarted httpstk.. that fixed that prob.

Now I need to get NSM working on a new server in my production tree,
which will eventually replace the existing.

I've installed it, and configured it. I unloaded fsfengin from the
existing box (as I can understand it would be bad to have two engines
running in the same tree!).. but when i start fsfengin on the new box, I
get:

Unable to appropriately configure proxy accounts. Program terminating.

There is no logs generated.

As a test, I re-ran fsfconfig and specified two different proxy accounts,
so this box would be using two completely different proxy accounts to the
existing server. Same result.

Please advise..

Dave
0 Likes
3 Replies
Highlighted
Anonymous_User Absent Member.
Absent Member.

Unable to appropriately configure proxy accounts

One extra point of interest - the server is a cluster node, so the
fsf.ini file contains server names that are the virtual server names, not
the physical node name.


> HI guys
>
> I have NSM 2 running in both of my production trees.
> Had some issues 'unable to connect to nsm engine' on one, but that

turned
> out to be httpstk not listening on the ssl port 8009. I deleted the

ssl
> certs, ran pkidiag, and restarted httpstk.. that fixed that prob.
>
> Now I need to get NSM working on a new server in my production tree,
> which will eventually replace the existing.
>
> I've installed it, and configured it. I unloaded fsfengin from the
> existing box (as I can understand it would be bad to have two engines
> running in the same tree!).. but when i start fsfengin on the new box,

I
> get:
>
> Unable to appropriately configure proxy accounts. Program terminating.
>
> There is no logs generated.
>
> As a test, I re-ran fsfconfig and specified two different proxy

accounts,
> so this box would be using two completely different proxy accounts to

the
> existing server. Same result.
>
> Please advise..
>
> Dave


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Unable to appropriately configure proxy accounts

Dave,

On server1 did you the install and then shut it down. Did you copy the
factory directory to server2 or did you rerun the installer? Can you send a
copy of your FSF.ini to storagemanager-at-novell.com replace -at- with @
from both servers?

thanks,

NSM Development
<_dave_@chisholm.vic.edu.au> wrote in message
news:nB0mg.5870$tN4.299@prv-forum2.provo.novell.com...
> HI guys
>
> I have NSM 2 running in both of my production trees.
> Had some issues 'unable to connect to nsm engine' on one, but that turned
> out to be httpstk not listening on the ssl port 8009. I deleted the ssl
> certs, ran pkidiag, and restarted httpstk.. that fixed that prob.
>
> Now I need to get NSM working on a new server in my production tree,
> which will eventually replace the existing.
>
> I've installed it, and configured it. I unloaded fsfengin from the
> existing box (as I can understand it would be bad to have two engines
> running in the same tree!).. but when i start fsfengin on the new box, I
> get:
>
> Unable to appropriately configure proxy accounts. Program terminating.
>
> There is no logs generated.
>
> As a test, I re-ran fsfconfig and specified two different proxy accounts,
> so this box would be using two completely different proxy accounts to the
> existing server. Same result.
>
> Please advise..
>
> Dave



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Unable to appropriately configure proxy accounts

any word on this?
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.