[workspace-user] Re: [gt-user] workspace deployment hangs - unexplained state change: Unstaged --> Corrupted
Manuel Rodriguez Pascual
supermanue at gmail.com
Mon Apr 2 10:26:26 CDT 2007
Hi everyone,
in case you find in my same situation, this is how I solved it:
The problem was that the machine wich was executing the workspace had
several disk partitions. Workspace was configured to run in a partition
without enought free space, so it couldn't create everyhing (logs, temp
files...) and the VM didn't work correctly. That's why their status was
"corrupted".
The solution is quite simple: changing the files in wich the paths are
stablished. In my case, there were :
--> /etc/worksp.conf
you have to modify the following paths
localdir: /workspace/images
securelocaldir: /workspace/secureimages
mountdir:/workspace/mnt
tmpdir:/workspace/tmp
persistencedir: /workspace/persistence
--> /opt/workspace/bin/mount-alter.sh and and /root/workspace-control/mount-
alter.sh
Find and modify the following constants:
IMAGE_DIR=/workspace/secureimages/
MOUNTPOINT_DIR=/workspace/mnt/
FILE_DIR=/workspace/tmp/
2007/3/24, Tim Freeman <tfreeman at mcs.anl.gov>:
>
> On Sat, 24 Mar 2007 00:01:18 +0100
> Manuel Rodriguez Pascual <supermanue at gmail.com> wrote:
>
> > Hello Tim,
> >
> > Thanks for your quick response.
> > I will analize my system, and see if I can solve the problem of disk
> > space.
> > Also, following your advise, I will subscribe to workspace mailing list.
>
> Cool, good luck. If you run into more problems, don't hesitate to send
> more
> questions to workspace-user.
>
> Thanks,
> Tim
>
> >
> >
> > El 23/03/2007, a las 22:39, Tim Freeman escribió:
> >
> > > On Fri, 23 Mar 2007 21:45:54 +0100
> > > Manuel Rodriguez Pascual <supermanue at gmail.com> wrote:
> > >
> > >> Hello all,
> > >>
> > >> this is my first message to a maling list and I'm not very good
> > >> writting in english, so please don't be very hard with me :)
> > >>
> > >> I'm a newie using globus. I think I have everything corectly
> > >> configured, but jus't cannot make it work. I am using debian on the
> > >> server, and a debian Virtual Machine. The VM was (more or less)
> > >> created as explained in http://www.howtoforge.com/
> > >> perfect_setup_xen3_debian . I think it is a standard setup, with
> > >> nothing strange. It works correctly when being run with Xen, except
> > >> doesn't have internet configurated.
> > >>
> > >> Globus is correctly instalated and being used by many people, so I
> > >> supose the problem is not there.
> > >>
> > >> I was wondering if this issue is something you've seen before, and if
> > >> so whether you could recommend tests or checks to find the source of
> > >> the problem. Bellow I have posted everything I think may help to find
> > >> my problem.
> > >
> > > Hello,
> > >
> > > Comment inline below, it looks like you ran out of disk space and a
> > > write is
> > > failing on the Xen node.
> > >
> > > Also, consider signing up for the workspace-user mailing list where
> > > you may get
> > > faster/better responses. For more information see this page:
> > > http://workspace.globus.org/contact.html
> > >
> > >
> > >>
> > >> Thanks for your attention,
> > >>
> > >> Manuel Rodriguez Pascual
> > >>
> > >>
> > >> I enter the following command:
> > >>
> > >>> workspace --file workspace.epr --metadata /usr/local/globus/share/
> > >>> workspace_client/sample-workspace.xml -s https://localhost:8443/
> > >>> wsrf/services/WorkspaceFactoryService --deploy-duration 30 --deploy-
> > >>> mem 256 --deploy-state Running
> > >>
> > >>
> > >> And I get the following output:
> > >>
> > >>> Using endpoint:
> > >>> Address: https://localhost:8443/wsrf/services/
> > >>> WorkspaceFactoryService
> > >>> Reference property[0]:
> > >>> <ns1:WorkspaceKey xmlns:ns1="http://www.globus.org/2006/08/
> > >>> workspace" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > >>> xsi:type="xsd:string">default</ns1:WorkspaceKey>
> > >>>
> > >>> Reading in metadata ... ok.
> > >>> Creating deployment request from arguments... ok.
> > >>>
> > >>> *** Deployment request:
> > >>>
> > >>> - Node number: 1
> > >>> - minDuration: 1800 seconds
> > >>> - State: Running
> > >>> - Default shutdown mechanism: Normal
> > >>> - individualPhysicalMemory:
> > >>> - exact: 256.0
> > >>>
> > >>> *** Classloading for a while, then creating workspace "http://
> > >>> example1/localhost/image"... ok.
> > >>>
> > >>> Resource key: 164
> > >>> Instantiation time: Fri Mar 23 19:56:40 CET 2007
> > >>> Duration: 1800 seconds (roughly 30 minutes)
> > >>> Shutdown time: Fri Mar 23 20:26:40 CET 2007
> > >>> Resource Termination time: Fri Mar 23 20:56:40 CET 2007
> > >>>
> > >>> Wrote EPR to 'workspace.epr'
> > >>> Subscribed to termination notification.
> > >>>
> > >>> Subscribed to deployment changes. Waiting.
> > >>>
> > >>> *** Deployment:
> > >>>
> > >>> - State changed: Unstaged --> Corrupted
> > >>>
> > >>>
> > >>> *** Network configuration:
> > >>>
> > >>> - NIC #1
> > >>> - ------------
> > >>> - Name: eth0
> > >>> - MAC: ANY
> > >>> - Network mode: Bridged
> > >>> - IP configuration: Allocate
> > >>> - IP address: 192.168.0.12
> > >>> - IP gateway: null
> > >>>
> > >>
> > >>
> > >> I can terminate it without any problem, running
> > >>
> > >> workspace -e workspace.epr --destroy
> > >>
> > >> ---
> > >> The metadata file (sample-workspace.xml) is the default file. I just
> > >> modified the VM I want to run, with the following sentence:
> > >>
> > >> <def:uri>file:///local/home/manuel/base.img</def:uri>
> > >>
> > >>
> > >> ---
> > >> At last, this is the output information I recibe in globus/var/
> > >> container.log.
> > >>
> > >>> 2007-03-23 21:36:57,406 INFO factory.WorkspaceFactoryService
> > >>> [ServiceThread-1059,create:62] [WORKSPACE-EVENT]: WS-CREATE invoked
> > >>> by /O=UCM/OU=ASDS-DACYA/CN=Manuel Rodriguez
> > >>> 2007-03-23 21:36:57,429 INFO factory.AssociationUtil
> > >>> [ServiceThread-1059,getNextEntry:96] [WORKSPACE-EVENT]: 'public'
> > >>> association entry leased, ip=192.168.0.12
> > >>> 2007-03-23 21:36:57,441 INFO factory.ResourcepoolUtil
> > >>> [ServiceThread-1059,getResourcepoolEntry:92] [WORKSPACE-EVENT]:
> > >>> 'pool1' resource pool entry 'ursa02': 256 MB reserved, 127 MB left
> > >>> 2007-03-23 21:36:57,451 INFO service.WorkspaceHome
> > >>> [ServiceThread-1059,create:631] [WORKSPACE-EVENT][id-165]:
> > >>>
> > >>> WORKSPACE RESOURCE CREATED:
> > >>> - Name: 'http://example1/localhost/image'
> > >>> - Key: '165'
> > >>> - Start time: Mar 23, 2007 9:36:57 PM
> > >>> - Shutdown time: Mar 23, 2007 10:06:57 PM
> > >>> - Resource termination time: Mar 23, 2007 10:36:57 PM
> > >>> - Creator DN: /O=UCM/OU=ASDS-DACYA/CN=Manuel Rodriguez
> > >>>
> > >>> 2007-03-23 21:36:57,481 INFO impls.WorkspaceResourceImpl
> > >>> [Timer-0,setOpsEnabled:370] [WORKSPACE-EVENT][id-165]: WS-
> > >>> operations enabled
> > >>> 2007-03-23 21:36:57,529 INFO workspace.WorkspaceUtil
> > >>> [Thread-18_WorkspTaskThrd,runCommand:155] [WORKSPACE-EVENT]: /usr/
> > >>> bin/ssh xenadmin at ursa02 /opt/workspace/bin/workspace-control --
> > >>> create --name workspace-165 --memory 256 --networking
> > >>> 'eth0;public;ANY;Bridged;Static;192.168.0.12;null;
> > >>> 192.168.0.255;255.255.255.0;192.168.0.1;null;null;null;null;null' --
> > >>> image file:///local/home/manuel/base.img --imagemount sda1
> > >>> 2007-03-23 21:36:58,788 INFO workspace.WorkspaceUtil
> > >>> [Thread-18_WorkspTaskThrd,runCommand:176] [WORKSPACE-EVENT]: Return
> > >>> code is 2
> > >>> 2007-03-23 21:36:58,789 ERROR workspace.WorkspaceUtil
> > >>> [Thread-18_WorkspTaskThrd,runCommand:232] [WORKSPACE-EVENT]: system
> > >>> command FAILURE
> > >>> STDERR:
> > >>>
> > >>> 2007-03-23 21:39:20,797 - ERROR - workspace (1072) - Problem
> > >>> validating configuration:
> > >>> Traceback (most recent call last):
> > >>> File "worksp.py", line 455, in main
> > >>> IOError: [Errno 28] No space left on device
> > >
> > > ^^^^^^^^^^
> > >
> > > Here's the error that I think is the important one.
> > >
> > > Tim
> > >
> > >
> > >
> > >>> 2007-03-23 21:36:58,789 INFO xen.XenTask
> > >>> [Thread-18_WorkspTaskThrd,execute:126] [WORKSPACE-EVENT][id-165]:
> > >>> Start failed
> > >>> 2007-03-23 21:36:58,789 ERROR impls.StatefulResourceImpl
> > >>> [Thread-18_WorkspTaskThrd,notify:123] Problem moving [id-165] to
> > >>> state 'Started'
> > >>> org.globus.workspace.WorkspaceException: Problem with parameters to
> > >>> workspace driver, incorrectly supplied or validation of request
> > >>> failed
> > >>> at org.globus.workspace.xen.XenUtil.throwErr(XenUtil.java:
> > >>> 485)
> > >>> at org.globus.workspace.xen.XenUtil.translateReturnException
> > >>> (XenUtil.java:449)
> > >>> at org.globus.workspace.xen.XenTask._execute(XenTask.java:
> > >>> 203)
> > >>> at org.globus.workspace.xen.XenTask.execute(XenTask.java:
> > >>> 105)
> > >>> at
> > >>> org.globus.workspace.service.impls.async.WorkspaceThread.run
> > >>> (WorkspaceThread.java:56)
> > >>> 2007-03-23 21:36:58,791 WARN impls.StateTransition
> > >>> [Thread-18_WorkspTaskThrd,corrupted:232] Workspace was corrupted
> > >>> (when moving to state Started): can not change state anymore unless
> > >>> workspace is going to be destroyed
> > >>
> > >>
> > >>
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.globus.org/pipermail/workspace-user/attachments/20070402/fb15e91a/attachment.htm>
More information about the workspace-user
mailing list