Client says bad email address

 
ID: 6689
Posts: 5

HI,  Tried both of these options with no luck.  I've seen this error now for over 1 year, visible on 3 or 4  different PCs/laptops  running Windows7 some with brand new builds of windows and the client., plus various Boinc Client versions.  (I posted earlier this year 2014 with the details.)  If it helps someone out there  - oddly, Gridrepublic did work correctly for  a single period of 1-2 weeks for no evident reason around Apri/May/June 2014 and then returned to the error condition.  The only common thread evident from my diagnostics  might  be the ISP supplier (Virgin) in my situation in the UK.   CM.
ID: 2821
Posts: 50

This is a tough issue to fix because your BOINC client is very likely giving broken XML to GridRepublic. Because the data being sent cannot be parsed properly, your account email address cannot be determined.

I've updated the code so that you should see a new error if this is the case. Then the trick will be how to fix that XML so that your client works properly...  

ID: 6689
Posts: 5

With the above noted change, I've today run some tests and observed that Gridrepublic now adds into BOINC at 04/10/14 10:00 GMT, with errors evident in some circumstances.   

BOINC client version 7.2.42 for windows_x86_64
VirtualBox version: 4.3.12
 

The following observations may assist with the troubleshooting:

A) Following syncronisation with Gridrepublic the message "Failed to update account
    manager" is shown.    
    In the log the error " Unexpected XML tag or syntax" is shown.

   Interestingly, after the above initial error, a second sync. attempt worked
   correctly giving:
    "Fetching configuration file from http://www.gridrepublic.org/get_project_config.php"
    "Contacting account manager at http://www.gridrepublic.org/"
    "Fetching configuration file from http://www.gridrepublic.org/get_project_config.php"
    "Account manager contact succeeded"


B)  Restart Boinc with Gridrepublic already added.
     Restart Boinc, everything works correctly with the 1st sync. No logged errors.
     Noted that line 1 in log file is always "cc_config.xml not found - using defaults"
     "Contacting account manager at http://www.gridrepublic.org/"
     "Account manager contact succeeded"
    Any subsequent attempt generates  the xml error response.
    (These also apppear in the Notice TAB from BOINC)


C) Disconnect Gridrepublic, and shutdown Boinc, and then start Boinc and
     re-attach Gridrepublic.
     This adds OK, but fails when the sync. is attempted. The same XML error is evident.
      2nd and 3rd  sync. attempts fail and BOINC Notice with error shown.  
      (Note this is a different outcome from scenario A above)
      4th  attempt with virus scanner/firewall disabled - same XML error observed.
      5th attempt: Waited 20 minutes then repeated sync. attemp - same error.

D) System reboot, and then startup of Boinc with gridrepublic already added.
    1st: Left Boinc running for 3.5 hours from a clean start then tried Gridrepublic
     update - now works correctly.
     2nd: Immediately tried another update - XML error condition.
     3rd: Reboot later same day,  xml error observed as part of the startup activity and
     then same failures as noted above.

cheers
CM 
ID: 2821
Posts: 50

Thanks for the detailed report, Colin. Sure enough, your client is sending bad XML. The "home" venue in your general preferences has no closing </venue> tag, so the whole thing can't be parsed.

There are a number of other users who seem to have the same problem. Would you be interested in upgrading your client to see if this is fixed in a more recent build? I can raise a bug report about the problem, but the most recent version for Windows 64-bit at this point is 7.4.22, so the developers would want to see that it affects that version.

ID: 6689
Posts: 5

HI,

OK, I've now upgraded the Boinc client to the latest build, 7.4.22(x64), wxWidgets 3.0.1 and initially everything worked well at 9am BST 5Oct. However, on re-visiting later on the same day, the fault re-appears, and stays.  A further test on 6th Oct 7pm BST shows the fault is evident 100% of the testing period.

The relevant logged messages are:
05/10/2014 18:48:59 |  | [unparsed_xml] ACCT_MGR_OP::parse: unrecognized tag <error_string>

05/10/2014 18:48:59 | http://www.gridrepublic.org/ | Message from account manager: unexpected XML tag or syntax. 

cheers
Colin

ID: 2821
Posts: 50

Thanks for trying that, Colin. I see there's actually an error in the error message, too (oops). Could you try to sync again and see what the message says? We may be able to work around this without needing a new client build even if the XML is malformed. 

ID: 6689
Posts: 5

Hi,  I've tried to re-attach to GridRepublic over the past 2-3 days but no luck. I have no tasks running or pending at this time in the client. Each attempt shows the following in the log: 

Contacting account manager at http://www.gridrepublic.org/
[unparsed_xml] ACCT_MGR_OP::parse: unrecognized tag <error_string>
http://www.gridrepublic.org/ | Message from account manager: unexpected XML tag or syntax 

I also inspected  the relevant client  XML file with the /<Venue> part.  etc. This looks normal to me.

When you mention the error message above - I'm not clear which error message text you are seeking -   I've only seen  those already mentioned earlier.  I also set all diagnostic flags, and tried a connection - again nothing useful was apparent (to me) in the log file with that level of detailed data recorded. 

cheers
Colin

Post   Previous   Page 2 of 2   Next