Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • autosubmit autosubmit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 338
    • Issues 338
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 21
    • Merge requests 21
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Earth SciencesEarth Sciences
  • autosubmitautosubmit
  • Issues
  • #624
Closed
Open
Issue created Nov 25, 2020 by jberlin@jberlinMaintainer

Checking connectivity for each host should be carry out only before running the experiment

Hi in Autosubmit 3.13.0b, for changing status of a given job, checking the connectivity with platforms used may be skipped since at this point users just want to change status of a job, not run. since Nord3 is down I cannot change the status even if the job I want to run will execute in other platform than Nord3 ( that is currently down )

autosubmit setstatus a36j -ft "SYNCHRONIZE" -t READY -s -nt -np Preparing .lock file to avoid multiple instances with same expid.

Checking configuration files...
expdef_a36j.conf OK
platforms_a36j.conf OK
jobs_a36j.conf OK
wrappers OK
autosubmit_a36j.conf OK
Configuration files OK

Creating jobs...
Loading JobList
Adding dependencies...
Removing redundant dependencies...
Checking the connection to all platforms in use
[local] Connection successfull to host localhost
[ERROR] Trace: [nord3] connection failed for host: nord1.bsc.es
 [CRITICAL] Unhandled error: If you see this message, please report it in Autosubmit's GitLab project

ideally checking connectivity is a cool idea before starting running the experiment, however for all the other commands may add overhead.

@dbeltran @mcastril

Assignee
Assign to
Time tracking