Please file a bug on this. To make progress, you can use the
--retrieve=true option so that the file is written to your local
directory rather than a DAS directory.
Tom
On 9/10/2010 10:58 AM, Bobby Bissett wrote:
> This is after upgrading the DAS from a clustered v2.1.1 installation. The upgrade works, but I need to recreate the instances per instructions here:
>
> http://wikis.sun.com/display/GlassFish/V3.1Clustering#V3.1Clustering-Upgrade
>
> When I try the export-sync-bundle command, I get the following error:
>
> --- begin ---
> hostname% ./asadmin version
> Version = GlassFish Server Open Source Edition 3.1-SNAPSHOT (build bobby-private)
> Command version executed successfully.
> hostname%
> hostname% ./asadmin get-health cluster1
> instance1 not started
> instance2 not started
>
> Command get-health executed successfully.
> hostname%
> hostname% ./asadmin export-sync-bundle --target cluster1 mybundle
> remote failure: BAD WRITE!!!! null
>
> Command export-sync-bundle failed.
> --- end ---
>
> Any help would be appreciated. The server log has nothing after the get-health message:
>
> [#|2010-09-10T11:54:36.222-0400|INFO|glassfish3.1|javax.enterprise.system.tools.admin.com.sun.enterprise.v3.admin.cluster|_ThreadID=18;_ThreadName=Thread-1;|get-health called for cluster "cluster1"|#]
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>