Tags:
, view all tags

Check bugs:

  • Bugs #45437: Sometimes the jobPurger throws the exception "Too many open files"

  • Bugs #45718: Some check on log lines should be added on BLParser code

  • Bugs #45736: Problems in case of resubmissions in the same CREAM CE

  • Bugs #45913: Proxy renewal not done for CREAM jobs not yet in IDLE status

  • Bugs #45983: BLAH can leave children processes behind.

  • Bugs #46283: Possible memory leak in strtoken function for BLParser

  • Bugs #46684: CREAM should call glexec directly (not via a wrapper script)

  • Bugs #46916: blparser startup daemon FIXED
    • Log on a CE where the Blparser is supposed to run.
    • Using the command "ps ax | grep -i parser" you should see two processes:
      23221  /opt/glite/bin/blparser_master
      28232  /opt/glite/bin/BLParserPBS -d 1 -l /opt/glite/var/log/glite-pbsparser.log -s /var/spool/pbs -p 33333 -m 56565
    • Kill the BLParserPBS process (e.g. kill -15 28232), and after some seconds you should see a new process

  • Bugs #47209: BL parser startup script assumes ${GLITE_LOCATION_VAR} exists FIXED
    • Check the file /opt/glite/etc/init.d/glite-ce-blparser to see is these lines have been removed:
      pidfile=$GLITE_LOCATION_VAR/glite-blparser${lrms}.pid
      echo `pidofproc ${exe}` > $pidfile 
      

-- AlessioGianelle - 24 Feb 2009

Edit | Attach | PDF | History: r8 | r4 < r3 < r2 < r1 | Backlinks | Raw View | More topic actions...
Topic revision: r2 - 2009-02-24 - AlessioGianelle
 
  • Edit
  • Attach
This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback