You can force the agent to use separate preferences by using the -p commandline
parameter.
Not sure how the wrapper can define that though.
/agent1/bin/rhq-agent.sh -p agent1
/agent2/bin/rhq-agent.sh -p agent2
that way the 2 agents will use separate preferences even if they run as the same user.
----- Original Message -----
From: "barry barnett" <barry.barnett(a)wellsfargo.com>
To: rhq-users(a)lists.fedorahosted.org
Sent: Wednesday, June 25, 2014 1:10:10 PM
Subject: RE: RHQ agent port issue
Sounds like if you have multiple instances of RHQ running on the same VM, you
need each to have its own userid to run under (if they are each using their
own separate storage nodes).
-----Original Message-----
From: rhq-users-bounces(a)lists.fedorahosted.org
[mailto:rhq-users-bounces@lists.fedorahosted.org] On Behalf Of Jay
Shaughnessy
Sent: Tuesday, June 24, 2014 9:09 PM
To: rhq-users(a)lists.fedorahosted.org
Subject: Re: RHQ agent port issue
This really seems like a preferences thing. The agent wrapper creates
a service that runs by default as the system default user, interactively the
agent runs as the logged in user. I think this is a case of two sets of
preferences in the registry.
On 6/23/2014 3:39 PM, barry.barnett(a)wellsfargo.com wrote:
> Same user as rhq server. Can I change the port in the wrapper config? I
> didn't see a place for it.
>
> ----- Original Message -----
> From: John Mazzitelli [mailto:mazz@redhat.com]
> Sent: Monday, June 23, 2014 02:02 PM
> To: rhq-users(a)lists.fedorahosted.org
> <rhq-users(a)lists.fedorahosted.org>
> Subject: Re: RHQ agent port issue
>
> does the agent run as the same user when you use the wrapper? The agent
> configuration is stored in Java Preferences, which is user-specific.
>
> The wiki docs and FAQ talk about Java Preferences if you want more details
> on how the config works.
>
> ----- Original Message -----
>> When I configure the agent to listen on port 16463, everything works
>> fine when ./rhq-agent.sh start is issued. However, when I stop the
>> agent and restart it with the wrapper script, the wrapper for one
>> reason or another wants to listen on port 16163, why is that? I did a
>> full clean config with the rhq-agent script to change the port to
>> 16463. Why would the wrapper want to listen on the default port even
>> after the full clean config? How do I fix this issue?
>>
>> _______________________________________________
>> rhq-users mailing list
>> rhq-users(a)lists.fedorahosted.org
>>
https://lists.fedorahosted.org/mailman/listinfo/rhq-users
>>
> _______________________________________________
> rhq-users mailing list
> rhq-users(a)lists.fedorahosted.org
>
https://lists.fedorahosted.org/mailman/listinfo/rhq-users
> _______________________________________________
> rhq-users mailing list
> rhq-users(a)lists.fedorahosted.org
>
https://lists.fedorahosted.org/mailman/listinfo/rhq-users
_______________________________________________
rhq-users mailing list
rhq-users(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-users
_______________________________________________
rhq-users mailing list
rhq-users(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-users