Changes between Version 32 and Version 33 of RoseCylc/Hints

09/12/15 11:36:46 (5 years ago)


  • RoseCylc/Hints

    v32 v33  
    304304After identifying the error, fix in the original {{{suite.rc}}} or {{{rose-suite.conf}}} file in the {{{roses}}} directory.  
    305305Editing the file in the {{{cylc-run}}} directory will have no effect! 
     307=== Can't view output in Rose bush === 
     309Note that, currently, Rose bush is not available on MONSooN due to system issues. 
     311However Rose bush should work properly for suites submitted to ARCHER and PUMA.  
     313Sometimes clicking on the log file in Rose bush gives a "403 Forbidden" error with a Python traceback:  
     315Traceback (most recent call last): 
     316  File "/usr/local/python/lib/python2.6/site-packages/cherrypy/", line 606, in respond 
     317    cherrypy.response.body = self.handler() 
     318  File "/usr/local/python/lib/python2.6/site-packages/cherrypy/", line 25, in __call__ 
     319    return self.callable(*self.args, **self.kwargs) 
     320  File "/home/fcm/rose/lib/python/rose/", line 301, in view 
     321    f_name = self._get_user_suite_dir(user, suite, path) 
     322  File "/home/fcm/rose/lib/python/rose/", line 472, in _get_user_suite_dir 
     323    *paths)) 
     324  File "/home/fcm/rose/lib/python/rose/", line 446, in _check_dir_access 
     325    raise cherrypy.HTTPError(403) 
     326HTTPError: (403, None) 
     328This is because the Rose bush server does not have permissions to read the log file. Navigate to your log files on the command line then manually add read permissions:  
     330cd ~/cylc-run/<suite-id>/log 
     331chmod -R a+r * 
     334So that future log files have the correct permission add the line {{{ -W umask = 0022}}} to your {{{suite.rc}}} under the {{{[[HPC]] [[[directives][]]}}} namespace. For example:  
     336    [[XC30]] 
     338        [[[directives]]] 
     340            -W umask = 0022 
     343Sometimes log files may also not show up if connection has been lost between PUMA and ARCHER. In this case log on to ARCHER, and navigate to the suite output directory:  
     345chmod -R a+r ~/cylc-run/<suite-id>/log/job 
     347Then browse the log files manually. You should also check your ssh agent on PUMA is still active.