4.2.0 has a module on writing a SEG, like 4.0 did:
http://www.globus.org/toolkit/docs/4.2/4.2.0/execution/gram4/developer/scheduler-tutorial.html
There's a migration guide, but it appears to only cover the GRAM
service/client APIs, not the SEG: http://www.globus.org/toolkit/docs/4.2/4.2.0/execution/gram4/mig/gram4-migrating-gt40.html#id2467444
The SEG API is covered at
http://www.globus.org/api/c-globus-4.0/globus_scheduler_event_generator/html/index.html
Charles
On Jul 9, 2008, at 5:35 AM, Steffen Limmer wrote:
Hi,
we have a problem with gt4.2.0 and the sge.
We used the sge-adapter from LESC (http://www.lesc.ic.ac.uk/projects/SGE-GT4.html
) with gt4.0.7 and everything worked fine.
Now we upgraded to gt4.2.0 and the adapter don't work anymore.
I read that there's a new resource manager adapter API in GRAM4. May
this be the problem?
Can anybody give us a tip, how we can fix the problem?
That's what the container logs say:
2008-07-09T12:31:34.672+02:00 ERROR seg.SchedulerEventGenerator [SEG-
sge-Thread,run:230] SEG Terminated with
globus_scheduler_event_generator: Invalid module sge: activation
failed
and thats the output from gpt-verify:
****************************************************
[EMAIL PROTECTED] ~ $ gpt-verify
Verifying Bundles...
Verifying run-time dependencies...
ERROR: The following packages are missing
Package Runtime-globus_proxy_utils-ANY-pgm version 2.1 is
incompatible with myproxy-gcc64dbg-pgm
Package Runtime-globus_c_wsrf_providers-gcc64dbg-rtl version 4.10 is
incompatible with globus_c_wsrf_registry_bindings-gcc64dbg-dev
Package Runtime-globus_handler_ws_addressing-gcc64dbg-rtl version
2.8 is incompatible with globus_c_wsrf_registry_bindings-gcc64dbg-dev
Package Runtime-globus_c_wsrf_providers-gcc64dbg-rtl version 4.10 is
incompatible with globus_c_wsrf_registry_bindings-gcc64dbg-rtl
Package Runtime-globus_handler_ws_addressing-gcc64dbg-rtl version
2.8 is incompatible with globus_c_wsrf_registry_bindings-gcc64dbg-rtl
Package globus_ftp_client_test-gcc64dbg-pgm is missing Runtime-
globus_gridftp_server_test-gcc64dbg-rtl
Package globus_gssapi_gsi_test-gcc64dbg-pgm is missing Runtime-
globus_test-gcc64dbg-rtl
Package globus_gass_copy_test-noflavor-pgm is missing Runtime-
globus_gridftp_server_test-ANY-pgm
Package Runtime-globus_c_wsrf_providers-gcc64dbg-rtl version 4.10 is
incompatible with globus_notification_consumer_factory_bindings-
gcc64dbg-dev
Package Runtime-globus_handler_ws_addressing-gcc64dbg-rtl version
2.8 is incompatible with
globus_notification_consumer_factory_bindings-gcc64dbg-dev
Package Runtime-globus_c_wsrf_providers-gcc64dbg-rtl version 4.10 is
incompatible with globus_notification_consumer_factory_bindings-
gcc64dbg-rtl
Package Runtime-globus_handler_ws_addressing-gcc64dbg-rtl version
2.8 is incompatible with
globus_notification_consumer_factory_bindings-gcc64dbg-rtl
Package globus_c_wsrf_core_test_interop_client_test-gcc64dbg-pgm is
missing Runtime-globus_test-gcc64dbg-rtl
Package globus_c_wsrf_core_performance_test-gcc64dbg-pgm is missing
Runtime-globus_test-gcc64dbg-rtl
Package globus_c_delegation_test-gcc64dbg-pgm is missing Runtime-
globus_test-gcc64dbg-rtl
Package globus_wsrf_gram_service_java_setup_sge-noflavor-pgm is
missing Runtime-globus_scheduler_event_generator_sge-ANY-pgm
Verifying setup dependencies...
Verifying setup packages...
ERROR: The collection of packages in /opt/globus-4.2.0/ is not
coherent!
***********************************************************************************************
Thanks in advance,
Steffen Limmer
--
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
