Project

General

Profile

Actions
Copy link

Bug #5054

closed

Dynamic DNS - Route53 errors should probably be more verbose

Added by Braden McGrath over 9 years ago. Updated almost 8 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Renato Botelho
Category:
Dynamic DNS
Target version:
2.3.3
Start date:
08/31/2015
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:
All

Description

This is somewhat related to Bug #3973.

I have a system where the "password" for the Route53 DynamicDNS handler kept getting reset to something not-correct (I suspect LastPass was trying to be "helpful" and was changing it). There is no outwardly visible sign that this password wasn't working, until you click back to the dashboard and get the banner mentioning that there is a crash dump to view. I had to less /tmp/PHP_errors.log in order to figure out that not only was the IP not updating, there was a password problem. The GUI is displaying the IP in green as though everything is fine, when this isn't actually the case.

Actions
Copy link
 #1

Updated by Phillip Davis over 9 years ago

Please share the appropriate PHP messages in PHP_errors.log - if something ends up generating invalid PHP then that should at least be able to be easily fixed.

Actions
Copy link
 #2

Updated by Braden McGrath over 9 years ago

I have already submitted the error logs (multiple times) via the in-built mechanism, but I can re-create errors and grab the files and post here if that helps.

Actions
Copy link
 #3

Updated by Chris Buechler over 9 years ago

  • Affected Version changed from 2.2.4 to All

would need to know what IP you submitted it from (or at least the first couple octets) to identify the crash report.

Actions
Copy link
 #4

Updated by Braden McGrath over 9 years ago

70.60.165.x, I just submitted again.

When the password is incorrect (presumably similar error with a bad username?):

[31-Aug-2015 21:12:50 America/New_York] PHP Warning:  
Route53::changeResourceRecordSets(): Sender - SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. 
Check your AWS Secret Access Key and signing method. Consult the service documentation for details.
Request Id: 907ef4a0-5046-11e5-bef7-670155c3dc0a
 in /etc/inc/r53.class on line 545

Alternatively, password is correct, but an error in the hostname, in this instance an extra period at the end: (making it a truly FQDN but apparently AWS doesn't like this)

[31-Aug-2015 21:17:22 America/New_York] PHP Warning:  
Route53::changeResourceRecordSets(): Sender - InvalidChangeBatch: FATAL problem: DomainLabelEmpty encountered at my-valid.fqdn.com.
Request Id: 324c2883-5047-11e5-991a-a7c5d9388a4e
 in /etc/inc/r53.class on line 545

Actions
Copy link
 #5

Updated by Braden McGrath over 9 years ago

If it would be helpful, I can probably get you guys a test "user" on our AWS so you can poke it. We only use AWS for DNS.

Actions
Copy link
 #6

Updated by Renato Botelho almost 8 years ago

  • Status changed from New to Feedback
  • Assignee set to Renato Botelho
  • Target version set to 2.4.0

Please check next round of 2.3.3 or 2.4.0 snapshots, that contain an updated code, to see if the issue persists

Actions
Copy link
 #7

Updated by Jim Pingle almost 8 years ago

  • Status changed from Feedback to Resolved

Tested Route53, it updates records properly now.

Actions
Copy link
 #8

Updated by Jim Pingle almost 8 years ago

  • Target version changed from 2.4.0 to 2.3.3
Actions
Copy link

Also available in: Atom PDF