Custom Query (87 matches)
Results (25 - 27 of 87)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#61 | fixed | Move GIMI Labwiki instance to OMF6 | ||
Description |
Once Labwiki is stable, we should test it with OMF6 and eventually change the configuration to use this version. |
|||
#79 | fixed | Encountering issues with VLC application and OML 2.11 | ||
Description |
Divya has been working with Olivier et al to troubleshoot issues she has encountered with the VLC application when using OML 2.11 server. This is currently being tracked in the OML ticket: https://oml.mytestbed.net/issues/1591 |
|||
#84 | fixed | Job service stalls | ||
Description |
While using the job service running at http://emmy9.casa.umass.edu:8003, I ran into the following problem:
The EC tries to connect to an RC which is either not up or does not exist and stays in that state while still showing the job status as "Running". STDOUT: 11:26:21 INFO OmfEc::Experiment: Experiment: dbhat-2014-04-11T10-18-13-05-00 starts STDOUT: 11:26:21 INFO OmfEc::Experiment: Configure 'nodea-labwikicrashtest' to join 'Source1' STDOUT: 11:26:21 INFO OmfEc::Experiment: Configure 'nodeb-labwikicrashtest' to join 'Source2' STDOUT: 11:26:21 INFO OmfEc::Experiment: Configure 'nodec-labwikicrashtest' to join 'Source3'
To resolve this problem, I tried:
After this the experiments were ran successfully.
I am not sure if all of these resources are listed in the AMQP database.
But, suppose these resources are listed in the AMQP database and are deleted by the experimenter or Aggregate Manager, and at a later time, the experimenter tries to connect to these resources that do not actually exist:
|