Bad error message. What "asadmin" is not executable? I'll bet that
there is no asadmin file at all where it is looking and it simply
did a File.canExecute() -- which returns false if it doesn't exist.
Error messages like this should
always say something like
"c:/foo/goo/asadmin.bat is not executable". Or "expected to find
asadmin in /blah/blah/foo"
On 10/27/2010 6:21 PM, Jason Lee wrote:
For
what it's worth, I get this in the Console when creating a new
node:
Successfully created instance
testInstancea1d4e413a950dc3f0ac98c43d10b8b7383 in the DAS
configuration, but failed to create the instance files on node
testNodea23317ff406bbfdc536b1f372f3b9290c9 (localhost). Failed to
execute local command: asadmin is not executable! To complete this
operation run the following command locally on host localhost from
the GlassFish install location /InstallDir: asadmin --port 4848
create-local-instance --nodedir /NodeDir --node
testNodea23317ff406bbfdc536b1f37...
But asadmin IS executable:
-rwxr-xr-x 1 jasonlee staff 2262 Oct 27 14:58 ./bin/asadmin
-rwxr-xr-x 1 jasonlee staff 2332 Oct 27 14:58
./glassfish/bin/asadmin
It does seem to create the node (though I'm not sure if it's
created correctly), as the entry is made in domain.xml, but the
call to the REST layer fails with that error because something
seems to be returning a warning.
Does this look familiar to anyone?
On 10/27/10 4:06 PM, Joe Di Pol wrote:
Bill Shannon wrote:
We decided to get rid of the WARNING
exit code, right?
So when that's done nothing will need to be fixed in
create-instance.
We got rid of the WARNING exit code from the asadmin client.
Remote commands
can still return WARNING.
create-instance calls _register_instance and the exit
code in that action report can be WARNING -- so it needed
to be changed to not consider that an error.
Joe
Joe Di Pol wrote on 10/27/10 11:32 AM:
This may be related to bug:
https://glassfish.dev.java.net/issues/show_bug.cgi?id=14247
At some point _register_instance started returning a Warning
in some situations
so create-instance doesn't create the instance filesystem in
that case.
create-instance needs to be changed to create the filesystem
on SUCCESS or WARNING.
I'm testing the fix now.
Joe
Jason Lee wrote:
On 10/27/10 11:44 AM, Byron Nevins
wrote:
The instance directory does not exist:
/Users/jasonlee/src/servers/glassfish3/glassfish/nodes/localhost/instanceNamea2765faa833cb8ebd23c02893e7fd4534b
Is it true? Stop the test at that point and see if it is
true
It's true. That directory is not there.
Anyone have any ideas what's
going on? If you need the exact CLI params, I
can turn on logging and dig those out for you.
No need to dig. Set this env. variable once and forget
it:
AS_LOGFILE=/Users/jasonlee/src/servers/glassfish3/glassfish/cli.log
You'll get one line for every cli command forever after
I'll do that and include the relevant information in the
issue that Tom asked
me to file.
Thanks.
--
Jason Lee Senior Member of Technical Staff
GlassFish Administration Console
Oracle Corporation
Phone +1 405-216-3193
Blog http://blogs.steeplesoft.com
---------------------------------------------------------------------
To unsubscribe, e-mail:
admin-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail:
admin-help@glassfish.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail:
admin-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail:
admin-help@glassfish.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: admin-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail:
admin-help@glassfish.dev.java.net
--
Byron Nevins - Oracle Corporation
Home: 650-359-1290
Cell: 650-784-4123
Sierra: 209-295-2188