AbstractEventInspector question

View: New views
7 Messages — Rating Filter:   Alert me  

AbstractEventInspector question

by K H :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,
I implemented a plugin to inspect event (extends AbstractEventInspector).
The Nexus application is install as 'root' however, we are initiating/starting the process (/nexus/bin/jsw/linux-x86-32/nexus) as another owner. The setup does not seem to work - nexus log does not show the inspected events. If the nexus install and initiation/start is own by same user (root) will work. Is there any way to get around this issue? Please let me know if you need more information.
Thanks,
Kelly

Re: AbstractEventInspector question

by Tamás Cservenák :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi there,

you probably had started nexus as root once, and all the workdirs are created as root. So, your "nexus" user will be unable to write there.... fix file/dir ownership and retry.

~t~

On Fri, May 1, 2009 at 1:39 AM, K H <kehsiao@...> wrote:

Hi,
I implemented a plugin to inspect event (extends AbstractEventInspector).
The Nexus application is install as 'root' however, we are
initiating/starting the process (/nexus/bin/jsw/linux-x86-32/nexus) as
another owner. The setup does not seem to work - nexus log does not show the
inspected events. If the nexus install and initiation/start is own by same
user (root) will work. Is there any way to get around this issue? Please let
me know if you need more information.
Thanks,
Kelly
--
View this message in context: http://www.nabble.com/AbstractEventInspector-question-tp23326226p23326226.html
Sent from the Nexus Maven Repository Manager Dev List mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-dev-unsubscribe@...
For additional commands, e-mail: nexus-dev-help@...



Re: AbstractEventInspector question

by K H :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Tamas,
Resending the same message as the first reply was send to the author only.
I try the following but still fails to work as desired:
1- change workdir (files/dirs) ownership to "nexus" user
2- chmod go+w on workdir (files/dirs)
3- change install (files/dirs) ownership to "nexus" user
4- re-create a workdir as "nexus" user
Thanks,
Kelly

Tamás Cservenák wrote:
Hi there,
you probably had started nexus as root once, and all the workdirs are
created as root. So, your "nexus" user will be unable to write there.... fix
file/dir ownership and retry.

~t~

On Fri, May 1, 2009 at 1:39 AM, K H <kehsiao@cisco.com> wrote:

>
> Hi,
> I implemented a plugin to inspect event (extends AbstractEventInspector).
> The Nexus application is install as 'root' however, we are
> initiating/starting the process (/nexus/bin/jsw/linux-x86-32/nexus) as
> another owner. The setup does not seem to work - nexus log does not show
> the
> inspected events. If the nexus install and initiation/start is own by same
> user (root) will work. Is there any way to get around this issue? Please
> let
> me know if you need more information.
> Thanks,
> Kelly
> --
> View this message in context:
> http://www.nabble.com/AbstractEventInspector-question-tp23326226p23326226.html
> Sent from the Nexus Maven Repository Manager Dev List mailing list archive
> at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-dev-unsubscribe@sonatype.org
> For additional commands, e-mail: nexus-dev-help@sonatype.org
>
>

Re: AbstractEventInspector question

by Brian Fox :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

If it works are root, there has to be a privilege issue somewhere in the
work folder that's causing this.

K H wrote:

> Hi Tamas,
> Resending the same message as the first reply was send to the author only.
> I try the following but still fails to work as desired:
> 1- change workdir (files/dirs) ownership to "nexus" user
> 2- chmod go+w on workdir (files/dirs)
> 3- change install (files/dirs) ownership to "nexus" user
> 4- re-create a workdir as "nexus" user
> Thanks,
> Kelly
>
>
> Tamás Cservenák wrote:
>  
>> Hi there,
>> you probably had started nexus as root once, and all the workdirs are
>> created as root. So, your "nexus" user will be unable to write there....
>> fix
>> file/dir ownership and retry.
>>
>> ~t~
>>
>> On Fri, May 1, 2009 at 1:39 AM, K H <kehsiao@...> wrote:
>>
>>    
>>> Hi,
>>> I implemented a plugin to inspect event (extends AbstractEventInspector).
>>> The Nexus application is install as 'root' however, we are
>>> initiating/starting the process (/nexus/bin/jsw/linux-x86-32/nexus) as
>>> another owner. The setup does not seem to work - nexus log does not show
>>> the
>>> inspected events. If the nexus install and initiation/start is own by
>>> same
>>> user (root) will work. Is there any way to get around this issue? Please
>>> let
>>> me know if you need more information.
>>> Thanks,
>>> Kelly
>>> --
>>> View this message in context:
>>> http://www.nabble.com/AbstractEventInspector-question-tp23326226p23326226.html
>>> Sent from the Nexus Maven Repository Manager Dev List mailing list
>>> archive
>>> at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: nexus-dev-unsubscribe@...
>>> For additional commands, e-mail: nexus-dev-help@...
>>>
>>>
>>>      
>>    
>
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-dev-unsubscribe@...
For additional commands, e-mail: nexus-dev-help@...


Re: AbstractEventInspector question

by Tamás Cservenák :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hm, the safest would be to fix the owneship on bundle files too (wrapper.log for example) and all the config files...

CHmodding the bundle and workdir to nexus user should make it work.

~t~

On Fri, May 1, 2009 at 7:09 PM, Brian Fox <brianf@...> wrote:
If it works are root, there has to be a privilege issue somewhere in the work folder that's causing this.


K H wrote:
Hi Tamas,
Resending the same message as the first reply was send to the author only.
I try the following but still fails to work as desired:
1- change workdir (files/dirs) ownership to "nexus" user
2- chmod go+w on workdir (files/dirs)
3- change install (files/dirs) ownership to "nexus" user
4- re-create a workdir as "nexus" user
Thanks,
Kelly


Tamás Cservenák wrote:
 
Hi there,
you probably had started nexus as root once, and all the workdirs are
created as root. So, your "nexus" user will be unable to write there....
fix
file/dir ownership and retry.

~t~

On Fri, May 1, 2009 at 1:39 AM, K H <kehsiao@...> wrote:

   
Hi,
I implemented a plugin to inspect event (extends AbstractEventInspector).
The Nexus application is install as 'root' however, we are
initiating/starting the process (/nexus/bin/jsw/linux-x86-32/nexus) as
another owner. The setup does not seem to work - nexus log does not show
the
inspected events. If the nexus install and initiation/start is own by
same
user (root) will work. Is there any way to get around this issue? Please
let
me know if you need more information.
Thanks,
Kelly
--
View this message in context:
http://www.nabble.com/AbstractEventInspector-question-tp23326226p23326226.html
Sent from the Nexus Maven Repository Manager Dev List mailing list
archive
at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-dev-unsubscribe@...
For additional commands, e-mail: nexus-dev-help@...


     
   

 

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-dev-unsubscribe@...
For additional commands, e-mail: nexus-dev-help@...



Re: AbstractEventInspector question

by K H :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi All,
I now re-install nexus as the "nexus" user which automatically creates the workdir from scratch as the install user. This doesn't seem to work either. I'm wondering if the new plugin (*.jar) was even picked up by nexus app....

With the new setup starting nexus as "nexus" user doesn't work however, chmod go+w for workdir and run start nexus as "root" works.
Thanks,
Kelly

Tamás Cservenák wrote:
Hm, the safest would be to fix the owneship on bundle files too (wrapper.log
for example) and all the config files...
CHmodding the bundle and workdir to nexus user should make it work.

~t~

On Fri, May 1, 2009 at 7:09 PM, Brian Fox <brianf@sonatype.com> wrote:

> If it works are root, there has to be a privilege issue somewhere in the
> work folder that's causing this.
>
>
> K H wrote:
>
>> Hi Tamas,
>> Resending the same message as the first reply was send to the author only.
>> I try the following but still fails to work as desired:
>> 1- change workdir (files/dirs) ownership to "nexus" user
>> 2- chmod go+w on workdir (files/dirs)
>> 3- change install (files/dirs) ownership to "nexus" user
>> 4- re-create a workdir as "nexus" user
>> Thanks,
>> Kelly
>>
>>
>> Tamás Cservenák wrote:
>>
>>
>>> Hi there,
>>> you probably had started nexus as root once, and all the workdirs are
>>> created as root. So, your "nexus" user will be unable to write there....
>>> fix
>>> file/dir ownership and retry.
>>>
>>> ~t~
>>>
>>> On Fri, May 1, 2009 at 1:39 AM, K H <kehsiao@cisco.com> wrote:
>>>
>>>
>>>
>>>> Hi,
>>>> I implemented a plugin to inspect event (extends
>>>> AbstractEventInspector).
>>>> The Nexus application is install as 'root' however, we are
>>>> initiating/starting the process (/nexus/bin/jsw/linux-x86-32/nexus) as
>>>> another owner. The setup does not seem to work - nexus log does not show
>>>> the
>>>> inspected events. If the nexus install and initiation/start is own by
>>>> same
>>>> user (root) will work. Is there any way to get around this issue? Please
>>>> let
>>>> me know if you need more information.
>>>> Thanks,
>>>> Kelly
>>>> --
>>>> View this message in context:
>>>>
>>>> http://www.nabble.com/AbstractEventInspector-question-tp23326226p23326226.html
>>>> Sent from the Nexus Maven Repository Manager Dev List mailing list
>>>> archive
>>>> at Nabble.com.
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: nexus-dev-unsubscribe@sonatype.org
>>>> For additional commands, e-mail: nexus-dev-help@sonatype.org
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-dev-unsubscribe@sonatype.org
> For additional commands, e-mail: nexus-dev-help@sonatype.org
>
>

Re: AbstractEventInspector question

by Brian Fox :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Make sure it's in /runtime/apps/nexus/lib not the /lib in the root of  
the bundle

--Brian (mobile)


On May 1, 2009, at 5:18 PM, K H <kehsiao@...> wrote:

>
> Hi All,
> I now re-install nexus as the "nexus" user which automatically  
> creates the
> workdir from scratch as the install user. This doesn't seem to work  
> either.
> I'm wondering if the new plugin (*.jar) was even picked up by nexus  
> app....
>
> With the new setup starting nexus as "nexus" user doesn't work  
> however,
> chmod go+w for workdir and run start nexus as "root" works.
> Thanks,
> Kelly
>
>
> Tamás Cservenák wrote:
>>
>> Hm, the safest would be to fix the owneship on bundle files too
>> (wrapper.log
>> for example) and all the config files...
>> CHmodding the bundle and workdir to nexus user should make it work.
>>
>> ~t~
>>
>> On Fri, May 1, 2009 at 7:09 PM, Brian Fox <brianf@...>  
>> wrote:
>>
>>> If it works are root, there has to be a privilege issue somewhere  
>>> in the
>>> work folder that's causing this.
>>>
>>>
>>> K H wrote:
>>>
>>>> Hi Tamas,
>>>> Resending the same message as the first reply was send to the  
>>>> author
>>>> only.
>>>> I try the following but still fails to work as desired:
>>>> 1- change workdir (files/dirs) ownership to "nexus" user
>>>> 2- chmod go+w on workdir (files/dirs)
>>>> 3- change install (files/dirs) ownership to "nexus" user
>>>> 4- re-create a workdir as "nexus" user
>>>> Thanks,
>>>> Kelly
>>>>
>>>>
>>>> Tamás Cservenák wrote:
>>>>
>>>>
>>>>> Hi there,
>>>>> you probably had started nexus as root once, and all the  
>>>>> workdirs are
>>>>> created as root. So, your "nexus" user will be unable to write
>>>>> there....
>>>>> fix
>>>>> file/dir ownership and retry.
>>>>>
>>>>> ~t~
>>>>>
>>>>> On Fri, May 1, 2009 at 1:39 AM, K H <kehsiao@...> wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Hi,
>>>>>> I implemented a plugin to inspect event (extends
>>>>>> AbstractEventInspector).
>>>>>> The Nexus application is install as 'root' however, we are
>>>>>> initiating/starting the process (/nexus/bin/jsw/linux-x86-32/
>>>>>> nexus) as
>>>>>> another owner. The setup does not seem to work - nexus log does  
>>>>>> not
>>>>>> show
>>>>>> the
>>>>>> inspected events. If the nexus install and initiation/start is  
>>>>>> own by
>>>>>> same
>>>>>> user (root) will work. Is there any way to get around this issue?
>>>>>> Please
>>>>>> let
>>>>>> me know if you need more information.
>>>>>> Thanks,
>>>>>> Kelly
>>>>>> --
>>>>>> View this message in context:
>>>>>>
>>>>>> http://www.nabble.com/AbstractEventInspector-question-tp23326226p23326226.html
>>>>>> Sent from the Nexus Maven Repository Manager Dev List mailing  
>>>>>> list
>>>>>> archive
>>>>>> at Nabble.com.
>>>>>>
>>>>>>
>>>>>> ---
>>>>>> ---
>>>>>> ---------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: nexus-dev-unsubscribe@...
>>>>>> For additional commands, e-mail: nexus-dev-help@...
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>> ---
>>> ------------------------------------------------------------------
>>> To unsubscribe, e-mail: nexus-dev-unsubscribe@...
>>> For additional commands, e-mail: nexus-dev-help@...
>>>
>>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/AbstractEventInspector-question-tp23326226p23339858.html
> Sent from the Nexus Maven Repository Manager Dev List mailing list  
> archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-dev-unsubscribe@...
> For additional commands, e-mail: nexus-dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-dev-unsubscribe@...
For additional commands, e-mail: nexus-dev-help@...