Project

General

Profile

Bug #74

tftp and puppet ca errors are not shown in the log file

Added by Ohad Levy over 9 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Proxy gateway
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

when an error occurred to run puppetca or to generate the tftp files, the error does not show up in the log files when running in production mode.

Associated revisions

Revision f860d3d0 (diff)
Added by Ohad Levy over 9 years ago

fixes #74 - tftp and puppet ca errors are not shown in the log file

Revision be1a3fae (diff)
Added by Paul Kelly over 9 years ago

Fixes #74. Logger messaging works in the proxy module

A logger method was introduced as well as a mechanism for logging if this
code is run as a standalone cgi service

Revision c78e2c68 (diff)
Added by Matthias Kneer almost 3 years ago

Fixes #74 - Remove unnecessary hash-signes from pool config description to allow proper naming within tools like webmin (#75)

History

#1 Updated by Ohad Levy over 9 years ago

  • Status changed from New to Ready For Testing
  • % Done changed from 0 to 100

#2 Updated by Ohad Levy over 9 years ago

  • Status changed from Ready For Testing to Assigned

this fix wont work as logger is not defined

#3 Updated by Ohad Levy over 9 years ago

  • % Done changed from 100 to 0

#4 Updated by Ohad Levy over 9 years ago

  • Assignee changed from Ohad Levy to Paul Kelly

#5 Updated by Paul Kelly over 9 years ago

  • Status changed from Assigned to Closed

The fix can be found on github.com/pkelly on bug/74

#6 Updated by Ohad Levy over 9 years ago

  • Status changed from Closed to Feedback

your fix always creates a new logger, is this on purpose? (e.g. will it work correctly if the logger already exists?)

#7 Updated by Paul Kelly over 9 years ago

I always create a new logger when the application is running as a cgi web service. In this mode there is no persistence so each GET triggers a new instantiation of the whole GW library. The last call's logger is gone so we need a new one. Well, I think that it works that way.

I am also pretty sure that multiple loggers for one file are OK but don't quote me on it.

#8 Updated by Paul Kelly over 9 years ago

  • Status changed from Feedback to Ready For Testing
  • % Done changed from 0 to 100

#9 Updated by Ohad Levy over 9 years ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF