determine username that is used to start server
login with that username
cd NodeFilesInitialisationFolder
sudo chown ServerOperatorName NodeFilesInitialisationFolder
sudo chmod 777 NodeFilesInitialiasationFolder
Martin Gainty
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.
> To: users_at_glassfish.java.net
> Subject: Re: Sun Glassfish Enterprise Server 2.1.1 - can not start ...
> From: forums_at_java.net
> Date: Tue, 26 Feb 2013 03:34:22 -0600
>
> New findings. Starting node agent is not the primary problem. Starting is
> failing due to inability to made initial synchronization of nodeagent (NA)
> from domain administration server (DAS). I copied some files missed in
> /config from /config, namely: domain.xml, admin-keyfile, cert8.db, key3.db,
> secmode.db, login.conf. Then start-node-agent and voila! NA started. But,...
> 'access denied' error in NA's server.log is still there (with same error
> trace):
> [#|2013-02-22T14:12:34.646+0100|SEVERE|sun-appserver2.1.1|javax.ee.enterprise.system.nodeagent|_ThreadID=10;_ThreadName=main;|NAGT0030:There
> was an unknown error while communi cating with Domain Administration Server
> (DAS). The actual exception stack trace follows ...
> java.security.AccessControlException: access denied
> (javax.management.MBeanPermission
> com.sun.enterprise.ee.synchronization.Synchronization#-[com.sun.appserv:category=config,t
> ype=synchronization] registerMBean) at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:374)
> at java.security.AccessController.checkPermission(AccessController.java:549)
> : I made some changes in DAS configuration. DAS's domain.xml was updated to
> follow the changes. NA was restarted with '--syncinstances=true', but no
> changes was made in NA's domain.xml. This lead me to conclusion -
> synchronization is corrupted. I found excellent article about DAS, NA and SI
> communication -
> https://blogs.oracle.com/bloggerkedar/entry/how_das_communicates_with_node .
> It contains explanation for DAS's communication. According to the article
> mentioned above, master password is kind of very important in initial
> start-agent-node sequence, when synchronization with DAS should happened. In
> my configuration, no matter, if I started NA with --savemasterpassword or
> wich master password specified during execution, the result is same "access
> denied". Did I search on wrong place? Am I debugging wrong Glassfish v2
> component? Any ideas are welcome.
>
> --
>
> [Message sent by forum member 'milos1av']
>
> View Post: http://forums.java.net/node/894801
>
>