Now that the Drupal module sends the data back to the Warden application behind the scenes, it can be difficult to identify exactly where the communication problems might be,

We therefore need some additional logging added to the Drupal module, which can be turned on within the settings and possibly even setting a log level variable to be able to log data at different places.

Comments

  • ceng committed ee14125 on 7.x-1.x
    Issue #2510494 by ceng: Added the conection failure error message to the...
johnennew’s picture

A small improvement to just include the connection error to the report status screen.

johnennew’s picture

StatusFileSize
new1.42 KB

Add error logging for the access request callback

  • ceng committed 2cd09b5 on 7.x-1.x
    Issue #2510494 by ceng: Added error logging in the access request...
johnennew’s picture

Version: 7.x-1.x-dev » 6.x-1.x-dev
StatusFileSize
new1.26 KB

Same access validation for warden request error logging but for D6

  • ceng committed e5a4c01 on 6.x-1.x
    Issue #2510494 by ceng at Deeson: Added additional error logging during...

  • ceng committed 9d76787 on 7.x-1.x
    Issue #2510494 by ceng at Deeson: Corrected bug - watchdog function case...
mike.davis’s picture

StatusFileSize
new597 bytes

Update on #5 as there was still reference to REQUEST_TIME in the watchdog call.

  • mike.davis committed e6fd754 on 6.x-1.x
    Issue #2510494 by ceng, mike.davis: Need additional error logging...
mike.davis’s picture

Status: Active » Fixed

This has been committed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.