SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
NMC and administrators usergroup
Author Message
Post NMC and administrators usergroup 
So I moved the NMC server from the backup server itself to a new host,
and started using the local console authentication "administrator"
account to log into the console. I set the console service to run as
nobody/nobody (the default in the nmc_config script).

I could monitor the backup server just fine but trying to change
configuration options, received an error which paraphrased said
something like

"User 'root' on host 'nmchost.domain.tld' not authorized for privilege
Configure NetWorker"

On the backup host using nsraddadmin and verified in nsradmin:
"user=root,host=nmchost.domain.tld" was in NSR usergroup
administrators.

same error: "User 'root' on host 'nmchost.domain.tld' not authorized
for privilege Configure NetWorker"

Eventually i set "user=administrator,host=nmchost.domain.tld" using
nsraddadmin, which resolved the error.

Is the error message about 'root' user, while the resolution was to
add 'administrator', a bug or a feature?

Thanks!
-Eugene


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

View user's profile Send private message
Post NMC and administrators usergroup 
Run the following command on Networker server:

nsraddadmin -u root < at > nmchost.domain.tld

Thanks & Regards

Akshay Bhumkar
+91-9342420444
* < at > k$h < at > y*



On Tue, Nov 29, 2011 at 8:23 PM, Eugene Vilensky <evilensky < at > gmail.com>wrote:

So I moved the NMC server from the backup server itself to a new host,
and started using the local console authentication "administrator"
account to log into the console. I set the console service to run as
nobody/nobody (the default in the nmc_config script).

I could monitor the backup server just fine but trying to change
configuration options, received an error which paraphrased said
something like

"User 'root' on host 'nmchost.domain.tld' not authorized for privilege
Configure NetWorker"

On the backup host using nsraddadmin and verified in nsradmin:
"user=root,host=nmchost.domain.tld" was in NSR usergroup
administrators.

same error: "User 'root' on host 'nmchost.domain.tld' not authorized
for privilege Configure NetWorker"

Eventually i set "user=administrator,host=nmchost.domain.tld" using
nsraddadmin, which resolved the error.

Is the error message about 'root' user, while the resolution was to
add 'administrator', a bug or a feature?

Thanks!
-Eugene


type "signoff networker" in the body of the email. Please write to
networker-request < at > listserv.temple.edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER



via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Post NMC and administrators usergroup 
What is the path for the command





Robert L. Bell, Jr.
Data Center Specialist 1
Information Technology
University of Houston Downtown
713-221-8224
bellr < at > uhd.edu




On Nov 30, 2011, at 12:21 AM, "akshay bhumkar"
<akshay.bhumkar < at > GMAIL.COM> wrote:

Run the following command on Networker server:

nsraddadmin -u root < at > nmchost.domain.tld

Thanks & Regards

Akshay Bhumkar
+91-9342420444
* < at > k$h < at > y*



On Tue, Nov 29, 2011 at 8:23 PM, Eugene Vilensky
<evilensky < at > gmail.com>wrote:

So I moved the NMC server from the backup server itself to a new
host,
and started using the local console authentication "administrator"
account to log into the console. I set the console service to run as
nobody/nobody (the default in the nmc_config script).

I could monitor the backup server just fine but trying to change
configuration options, received an error which paraphrased said
something like

"User 'root' on host 'nmchost.domain.tld' not authorized for
privilege
Configure NetWorker"

On the backup host using nsraddadmin and verified in nsradmin:
"user=root,host=nmchost.domain.tld" was in NSR usergroup
administrators.

same error: "User 'root' on host 'nmchost.domain.tld' not authorized
for privilege Configure NetWorker"

Eventually i set "user=administrator,host=nmchost.domain.tld" using
nsraddadmin, which resolved the error.

Is the error message about 'root' user, while the resolution was to
add 'administrator', a bug or a feature?

Thanks!
-Eugene


type "signoff networker" in the body of the email. Please write to
networker-request < at > listserv.temple.edu if you have any problems with
this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER



and type "signoff networker" in the body of the email. Please write
to networker-request < at > listserv.temple.edu if you have any problems
with this list. You can access the archives at http://listserv.temple.edu/archives/networker.html
or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Post NMC and administrators usergroup 
Should work if environ. Variable is set for networker path. Or else default
is c:\program files\legato\nsr\bin

Sent from my Galaxy S...
On Nov 30, 2011 12:58 PM, "Bell Jr, Robert" <BellR < at > uhd.edu> wrote:

What is the path for the command





Robert L. Bell, Jr.
Data Center Specialist 1
Information Technology
University of Houston Downtown
713-221-8224
bellr < at > uhd.edu




On Nov 30, 2011, at 12:21 AM, "akshay bhumkar" <akshay.bhumkar < at > GMAIL.COM>
wrote:

Run the following command on Networker server:

nsraddadmin -u root < at > nmchost.domain.tld

Thanks & Regards

Akshay Bhumkar
+91-9342420444
* < at > k$h < at > y*



On Tue, Nov 29, 2011 at 8:23 PM, Eugene Vilensky <evilensky < at > gmail.com
wrote:

So I moved the NMC server from the backup server itself to a new host,
and started using the local console authentication "administrator"
account to log into the console. I set the console service to run as
nobody/nobody (the default in the nmc_config script).

I could monitor the backup server just fine but trying to change
configuration options, received an error which paraphrased said
something like

"User 'root' on host 'nmchost.domain.tld' not authorized for privilege
Configure NetWorker"

On the backup host using nsraddadmin and verified in nsradmin:
"user=root,host=nmchost.**domain.tld" was in NSR usergroup
administrators.

same error: "User 'root' on host 'nmchost.domain.tld' not authorized
for privilege Configure NetWorker"

Eventually i set "user=administrator,host=**nmchost.domain.tld" using
nsraddadmin, which resolved the error.

Is the error message about 'root' user, while the resolution was to
add 'administrator', a bug or a feature?

Thanks!
-Eugene


type "signoff networker" in the body of the email. Please write to
networker-request < at > listserv.**temple.edu<networker-request < at > listserv.temple.edu>if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/**archives/networker.html<http://listserv.temple.edu/archives/networker.html>or
via RSS at http://listserv.temple.edu/**cgi-bin/wa?RSS&L=NETWORKER<http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER>



type "signoff networker" in the body of the email. Please write to
networker-request < at > listserv.**temple.edu<networker-request < at > listserv.temple.edu>if you have any problems with this list. You can access the archives at
http://listserv.temple.edu/**archives/networker.html<http://listserv.temple.edu/archives/networker.html>or
via RSS at http://listserv.temple.edu/**cgi-bin/wa?RSS&L=NETWORKER<http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER>




via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Post NMC and administrators usergroup 
On Wed, Nov 30, 2011 at 12:18 AM, akshay bhumkar
<akshay.bhumkar < at > gmail.com> wrote:
Run the following command on Networker server:

nsraddadmin -u root < at > nmchost.domain.tld

Yes, I have done this, but using user=xxxx,host=xxxx notation.

For future Google searches, the solution to this problem is documented
in EMC Solution ID esg75186:

Use both host=nmchost.domain.tld and also host=nmchost[shortname].

Cheers,
Eugene


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

View user's profile Send private message
Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB