PING causes 500 Internal Server Error - Incorrect datetime value

[John Palmer]

I just installed Authpuppy on IIS 7. Everything else seems to be working but when APs "ping" the auth server I get the following error in the W3SVC log (x,y,z have been used to replace IP addresses):

2011-12-21 01:10:17 x.x.x.x GET /ping/ gw_id=citrius000001&sys_uptime=61219&sys_memfree=1580&sys_load=0.00&wifidog_uptime=61186 80 - y.y.y.y WiFiDog+1.1.3_beta6 500 0 0 171

Running that query string through frontend_dev.php returns this additional detail:

SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '2011-12-21T07:04:50+00:00' for column 'last_heartbeat_at' at row 1

The logs show this statement caused the error:

execute : UPDATE nodes SET last_heartbeat_at = ?, last_heartbeat_ip = ?, last_heartbeat_sys_uptime = ?, last_heartbeat_sys_load = ?, last_heartbeat_sys_memfree = ?, last_heartbeat_wifidog_uptime = ?, updated_at = ? WHERE id = ? - (2011-12-21T08:03:15+00:00, z.z.z.z, 61219, 0.00, 1580, 61186, 2011-12-21 08:03:15, 2)

I'm not sure where to look to investigate further... Any help would be appreciated.

Thanks!

John

[Robin Jones (robin-networkfusion)]

If it exists, please can you try removing STRICT_TRANS_TABLES from sql-mode in my.ini

Robin.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of John Palmer
Sent: 21 December 2011 08:13
To: Robin Jones
Subject: [Bug 907203] [NEW] PING causes 500 Internal Server Error - Incorrectdatetime value

Public bug reported:

I just installed Authpuppy on IIS 7. Everything else seems to be working but when APs "ping" the auth server I get the following error in the W3SVC log (x,y,z have been used to replace IP addresses):

2011-12-21 01:10:17 x.x.x.x GET /ping/
gw_id=citrius000001&sys_uptime=61219&sys_memfree=1580&sys_load=0.00&wifidog_uptime=61186
80 - y.y.y.y WiFiDog+1.1.3_beta6 500 0 0 171

Running that query string through frontend_dev.php returns this additional detail:

SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value:
'2011-12-21T07:04:50+00:00' for column 'last_heartbeat_at' at row 1

The logs show this statement caused the error:

execute : UPDATE nodes SET last_heartbeat_at = ?, last_heartbeat_ip = ?, last_heartbeat_sys_uptime = ?, last_heartbeat_sys_load = ?, last_heartbeat_sys_memfree = ?, last_heartbeat_wifidog_uptime = ?, updated_at = ? WHERE id = ? - (2011-12-21T08:03:15+00:00, z.z.z.z, 61219, 0.00, 1580, 61186, 2011-12-21 08:03:15, 2)

I'm not sure where to look to investigate further... Any help would be appreciated.

Thanks!

John

** Affects: authpuppy
     Importance: Undecided
         Status: New

--
You received this bug notification because you are subscribed to AuthPuppy.
https://bugs.launchpad.net/bugs/907203

Title:
  PING causes 500 Internal Server Error - Incorrect datetime value

Status in AuthPuppy authentication server for Wifidog networks:
  New

Bug description:
  I just installed Authpuppy on IIS 7. Everything else seems to be
  working but when APs "ping" the auth server I get the following error
  in the W3SVC log (x,y,z have been used to replace IP addresses):

  2011-12-21 01:10:17 x.x.x.x GET /ping/
  gw_id=citrius000001&sys_uptime=61219&sys_memfree=1580&sys_load=0.00&wifidog_uptime=61186
  80 - y.y.y.y WiFiDog+1.1.3_beta6 500 0 0 171

  Running that query string through frontend_dev.php returns this
  additional detail:

  SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime
  value: '2011-12-21T07:04:50+00:00' for column 'last_heartbeat_at' at
  row 1

  The logs show this statement caused the error:

  execute : UPDATE nodes SET last_heartbeat_at = ?, last_heartbeat_ip =
  ?, last_heartbeat_sys_uptime = ?, last_heartbeat_sys_load = ?,
  last_heartbeat_sys_memfree = ?, last_heartbeat_wifidog_uptime = ?,
  updated_at = ? WHERE id = ? - (2011-12-21T08:03:15+00:00, z.z.z.z,
  61219, 0.00, 1580, 61186, 2011-12-21 08:03:15, 2)

  I'm not sure where to look to investigate further... Any help would
  be appreciated.

  Thanks!

  John

To manage notifications about this bug go to:
https://bugs.launchpad.net/authpuppy/+bug/907203/+subscriptions

[Robin Jones (robin-networkfusion)]

For info, I think the actual reason for the error is to do with truncation of the date and it is the format of $node->setLastHeartbeatAt(date(DATE_ATOM)); on line 55 in http://bazaar.launchpad.net/~alliancecsf-dev/authpuppy/trunk/view/head:/lib/model/authpuppycore/protocol/apActionsV1.php however I cannot seem to find the corresponding class that executes the query, so I cannot be sure.

Maybe changing it to:
$node->setLastHeartbeatAt(date('Y-m-d H:i:s', DATE_ATOM)); will do the trick...

Robin.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Robin Jones
Sent: 21 December 2011 12:22
To: Robin Jones
Subject: RE: [Bug 907203] [NEW] PING causes 500 Internal Server Error -Incorrectdatetime value

If it exists, please can you try removing STRICT_TRANS_TABLES from sql- mode in my.ini

Robin.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of John Palmer
Sent: 21 December 2011 08:13
To: Robin Jones
Subject: [Bug 907203] [NEW] PING causes 500 Internal Server Error - Incorrectdatetime value

Public bug reported:

I just installed Authpuppy on IIS 7. Everything else seems to be working but when APs "ping" the auth server I get the following error in the W3SVC log (x,y,z have been used to replace IP addresses):

2011-12-21 01:10:17 x.x.x.x GET /ping/
gw_id=citrius000001&sys_uptime=61219&sys_memfree=1580&sys_load=0.00&wifidog_uptime=61186
80 - y.y.y.y WiFiDog+1.1.3_beta6 500 0 0 171

Running that query string through frontend_dev.php returns this additional detail:

SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value:
'2011-12-21T07:04:50+00:00' for column 'last_heartbeat_at' at row 1

The logs show this statement caused the error:

execute : UPDATE nodes SET last_heartbeat_at = ?, last_heartbeat_ip = ?, last_heartbeat_sys_uptime = ?, last_heartbeat_sys_load = ?, last_heartbeat_sys_memfree = ?, last_heartbeat_wifidog_uptime = ?, updated_at = ? WHERE id = ? - (2011-12-21T08:03:15+00:00, z.z.z.z, 61219, 0.00, 1580, 61186, 2011-12-21 08:03:15, 2)

I'm not sure where to look to investigate further... Any help would be appreciated.

Thanks!

John

** Affects: authpuppy
     Importance: Undecided
         Status: New

--
You received this bug notification because you are subscribed to AuthPuppy.
https://bugs.launchpad.net/bugs/907203

Title:
  PING causes 500 Internal Server Error - Incorrect datetime value

Status in AuthPuppy authentication server for Wifidog networks:
  New

Bug description:
  I just installed Authpuppy on IIS 7. Everything else seems to be
  working but when APs "ping" the auth server I get the following error
  in the W3SVC log (x,y,z have been used to replace IP addresses):

  2011-12-21 01:10:17 x.x.x.x GET /ping/
  gw_id=citrius000001&sys_uptime=61219&sys_memfree=1580&sys_load=0.00&wifidog_uptime=61186
  80 - y.y.y.y WiFiDog+1.1.3_beta6 500 0 0 171

  Running that query string through frontend_dev.php returns this
  additional detail:

  SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime
  value: '2011-12-21T07:04:50+00:00'...

[John Palmer (1pt1nq88tvxvj-john-8aho930n7szvk)]

Thanks, Robin!

I removed STRICT_TRANS_TABLES from sql-mode in my.ini and now PING is logging 200 events.

Thanks again!

John