News, GPFS status, SardanaMonitor bug, OmsVme58 crashed (P64, P65), new spectra version, scanInfo

• GPFS:
  • Stolen ESS node number: we are the first to encounter the problem. Depends on the size of the compute cluster. Above 128 the problem is more likely to occur, DESY: 221. So far no fix by IBM.

    Bug persists. IT will try to avoid this bug by organisational measures.

  • GL4S up and running.

  • IT does some cleanup on the old GL4 and GL6, effectively de-fragmenting storage.

• Cursor/SardanaMonitor bug, P06, un-sorted arrays: fixed.

• OmsVme58 server crashed, P64, P65:

  From Tango server logs (/var/tmp/ds.log), e.g.:

  OmsVme58::check_motor_register: Wed Nov  1 17:57:29 2017 
  OmsVme58::check_motor_register: p64/motor/exp.03, controller 2470253, internal 2470249, using controller 
  OmsVme58::check_motor_register: p64/motor/exp.03, controller 2470253 within limits [-3487680, 7331520]
  OmsVme58::check_motor_register: p64/motor/exp.03, corresponding units: 22.6958 [-30.5, 66.1] 
  
  OmsVme58::check_motor_register: Wed Nov  1 17:57:29 2017 
  OmsVme58::check_motor_register: p64/motor/exp.01, controller 212336, internal 212330, using controller 
  OmsVme58::check_motor_register: p64/motor/exp.01, controller 212336 within limits [-5745600, 5006400]
  OmsVme58::check_motor_register: p64/motor/exp.01, corresponding units: 22.6959 [-30.5, 65.5] 
  
  OmsVme58::check_motor_register: Wed Nov  1 17:57:29 2017 
  OmsVme58::check_motor_register: p64/motor/exp.02, controller 2188020, internal 2188010, using controller 
  OmsVme58::check_motor_register: p64/motor/exp.02, controller 2188020 within limits [-3769920, 7049280]
  OmsVme58::check_motor_register: p64/motor/exp.02, corresponding units: 22.6959 [-30.5, 66.1] 
  
  OmsVme58::check_motor_register: Tue Sep 12 10:20:03 2017 
  OmsVme58::check_motor_register: p64/motor/exp.21, controller 411885, internal 411884, using controller 
  OmsVme58::check_motor_register: p64/motor/exp.21, controller 411885 within limits [-864000, 736000]
  OmsVme58::check_motor_register: p64/motor/exp.21, corresponding units: 59.4856 [-100, 100]
  

  Now and then the controller and internal values disagree by a few steps. So far, no idea why.

• Changed HasyUtils.createScanInfo(), no longer includes motor proxy.

  The current ScanInfo structure:

  {
    'sampleTime': 0.1, 
    'serialno': 5156, 
    'intervals': 10, 
    'motors': [{'start': 800.0, 'stop': 810.0, 'name': 'exp_dmy01'}], 
    'title': 'ascan exp_dmy01 800.0 810.0 10 0.1'
  }
  

  Restarted MacroServers, since mvsa and CursorApp are affected.

• Distributed a Spectra version (internal storage from 2GB to 1GB)