, view all tags

Check Bugs:

  • BUG #39646: "edg-voms continues to run with no logs despite /var/log/glite not existing" FIXED
    • Start VOMS core with a LOGFILE parameter pointing to a non-existing directory, like for ex. --logfile=/var/log1/glite/voms.sa3test Check it throws an error message and exits, such as the following:
      [root@cert-voms-02 testsuite]# /opt/glite/sbin/edg-voms --conf /opt/glite/etc/voms/sa3test/voms.conf
      logging could not start!  Logfile /var/log1/glite/voms.sa3test could not be opened, and syslogging is disabled.

  • BUG #42601: "voms-proxy-init should accept -old option"

  • BUG #43942: "voms-proxy-info error for non standard location of CA files"

  • BUG #44160: "Strange segfault in voms-proxy-init with erroneous command line"

  • BUG #45132: "VOMS Logging, File logging can't be switched off." FIXED
    • Add specific option "--nologfile" in the "voms.conf" file di conf for voms
    • Delete the standard logfile under "/var/log/glite/"
    • Re-start VOMS and check if the logfile gets re-created by issuing a "voms-proxy-init -voms ..." for ex.

  • BUG #45133: "VOMS File Logging Fails when file history rotation not preserved." FIXED
    • Delete one of the sequence of log files, like for ex. " /var/log/glite/voms.sa3test.1"
    • Issue a "voms-proxy-init" and check the log file /var/log/glite/voms.sa3test gets populated regularly

  • BUG #45331: "voms-proxy-init -key XXX -cert YYY uses the DN from the hostcert/key"

-- ElisabettaMolinari - 03 Feb 2009

Edit | Attach | PDF | History: r10 | r7 < r6 < r5 < r4 | Backlinks | Raw View | More topic actions...
Topic revision: r5 - 2009-02-05 - ElisabettaMolinari
  • Edit
  • Attach
This site is powered by the TWiki collaboration platformCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback