It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×1,305

question asked: Mar 18 '11, 5:13 p.m.
question was seen: 3,961 times
last updated: Mar 18 '11, 5:13 p.m.

Related questions

FAQ - How this Forum works

Filesystem access error on policy exec

0
Rogério Ramos da Silva (335●28●27) | asked Mar 18 '11, 5:13 p.m.
Hi all,

I've just installed the RAM 7.5.0.2 on my desenv. environment, but I got a unexpected error.

The problematic policy uses the RAM API to change an attribute, when it runs, the logs show me this: 

[3/18/11 17:30:49:673 BRT] 0000003a SystemOut     O [03/18/11 17:30:49 BRT] CRRAM0002W  3766632 WARN  web com.ibm.ram.internal.client.RAMClient - HTTP Error trying to upload. (500: Internal Server Error), STATUSTEXT:Internal Server Error, RESPONSE:Error 500: Repository exception trying to submit asset - TestarNovoLC - ID#F8E6160F-AF20-561F-4074-CE46F97DB3D0 Version#1.0



: The file access permissions do not allow the specified action.



[3/18/11 17:30:49:675 BRT] 0000003a SystemOut     O [03/18/11 17:30:49 BRT] CRRAM0001E  3766634 ERROR web com.ibm.ram.client.RAMSession         - Error when uploading the asset {0}.TestarNovoLC[1.0]



Manifest = <xml>

<defaultprofile:Asset xmi:version="2.0"

  <others manifest's tags and values cutted here />

 <solution>

</defaultprofile>



Archive = [no file]



[3/18/11 17:30:49:676 BRT] 0000003a SystemOut     O [03/18/11 17:30:49 BRT] CRRAM0001E  3766637 ERROR web com.ibm.ram.client.RAMSession         - The asset TestarNovoLC[1.0] was not updated.


All configured folders (index, local, persist) have totall permission (chmod 777), so what files permissons is causing this error?

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Rogério Ramos da Silva (335●28●27) | answered Mar 22 '11, 8:36 a.m.
In a clustered environment it's necessary to have the persist folder shared between all RAM's nodes/instances. In my case I've a folder exported via NFS from the A node to all others nodes.

As the all WAS instances runs as root, the shared folders should be the same permissions, and my exported folder had not root access configured. So the NSF source node works fine but the others (clients) not.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.