Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 924441 - Boinc Manager sends bad information to BAM! manager
Summary: Boinc Manager sends bad information to BAM! manager
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: boinc-client
Version: 18
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Milos Jakubicek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1039258
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-21 19:21 UTC by Robert Gammon
Modified: 2023-09-12 00:21 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 20:10:35 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
/var/lib/boinc/acct_mgr_request.xml (4.44 KB, application/xml)
2013-03-30 08:03 UTC, Mattia M. 		no flags Details
Account Manager Request file (12.24 KB, text/xml)
2013-03-30 12:06 UTC, Robert Gammon 		no flags Details
View All

Description Robert Gammon 2013-03-21 19:21:41 UTC 
Description of problem:  When attempting to connnect to the BOINC project Manger BAM!, bad information is sent to BAM! and the connection is refused.


Version-Release number of selected component (if applicable):  Boinc 7.0.29.2


How reproducible:  Connect to Project Manager in Boinc Manager, EVERY time


Steps to Reproduce:
1.  verify boinc client is running (ps aux | grep boinc)
2.  start Boinc Manager
3.  select Tools-> Add project or Account Manager
4.  select Use account manager. then select Next
5.  select BAM! from the list, and click Next
6.  supply login information for BAM!, click Next
7.  BOINC manager and BAM start a conversation that ends as follows
  
Actual results:
Thu 21 Mar 2013 03:18:13 PM EDT | BOINCstatsBAM! | Message from account manager: Opening and ending tag mismatch: pci_info line 265 and coproc_cuda. Opening and ending tag mismatch: coproc_cuda line 222 and coprocs. Opening and ending tag mismatch: coprocs line 221 and host_authenticator. Premature end of data in tag host_authenticator line 2.


Expected results:
You are now using the BAM! account manager (and the list of projects in BOINC gets updated with all projects and statistics from BAM!)

Additional info:   This is not a problem with BOINC 7.0.28 or BOINC 7.0.27 on Ubuntu.  I only see the issue in Fedora 18.   I am a new user to Fedora with very limited proior use prior to F18
Comment 1 Robert Gammon 2013-03-22 17:51:19 UTC 
Thu 21 Mar 2013 05:44:13 PM EDT | |
OS: Linux: 3.8.3-203.fc18.x86_64

All Updates applied daily.   This system level was as of the last restart of BOINC and no kernel updates have come since that restart happened.
Comment 2 Mattia M. 2013-03-30 08:03:36 UTC 
Created attachment 718213 [details]
/var/lib/boinc/acct_mgr_request.xml
Comment 3 Mattia M. 2013-03-30 08:06:22 UTC 
The same problem occurs on my system (boinc-client-7.0.29-2.r25790svn.fc18.x86_64, Fedora 18 x86_64 with kernel 3.8.4-202.fc18.x86_64).

Connection to BAM! ends up with "Failed to add account manager" and the following message:

sab 30 mar 2013 08:32:08 CET | BOINCstatsBAM! | Message from account manager: Opening and ending tag mismatch: pci_info line 92 and coproc_cuda. Opening and ending tag mismatch: coproc_cuda line 68 and coprocs. Opening and ending tag mismatch: coprocs line 67 and host_authenticator. Premature end of data in tag host_authenticator line 2.

In fact, file /var/lib/boinc/acct_mgr_request.xml seems to actually be malformed (see attachment): there's no closing tag for "<pci_info>" on line 92.

Excerpt from /var/lib/boinc/acct_mgr_request.xml, lines 67 to 97:

    <coprocs>
<coproc_cuda>
   <count>1</count>
   <name>GeForce 9600 GT</name>
...
[lines 71 to 90 omitted]
...
   <multiProcessorCount>8</multiProcessorCount>
<pci_info>
   <bus_id>1</bus_id>
   <device_id>0</device_id>
   <domain_id>0</domain_id>
</coproc_cuda>
    </coprocs>
Comment 4 Robert Gammon 2013-03-30 12:03:03 UTC 
Comment on attachment 718213 [details]
/var/lib/boinc/acct_mgr_request.xml

In my version of this file, </coprocs_cuda> and </coprocs> are followed by <pci_info> and this block is NOT closed.   This unclosed block APPEARS to be the problem.  I will upload my version created by boinc 7.0.29.2 for your review
Comment 5 Robert Gammon 2013-03-30 12:06:04 UTC 
Created attachment 718239 [details]
Account Manager Request file

The pc_info block that immediately follows the close of coproc_cuda and coproc blocks IS NOT CLOSED.   This appears to be the source of the error in talking to BAM!
Comment 6 Robert Gammon 2013-03-30 12:15:20 UTC 
And the file gets re-written each time an Account Manager request is sent to BAM!  So a manual edit of the file does not cure the problem.   This appears to be an issue in the code inside BOINC Manager.  Our files are IDENTICAL in this area of the file, <pci_info> is NOT closed with </pci_info>
Comment 7 Milos Jakubicek 2013-05-01 11:01:39 UTC 
This does not look like a Fedora-specific bug, I just built boinc 7.0.65, would you please try to reproduce it with that version:

http://koji.fedoraproject.org/koji/taskinfo?taskID=5320442
Comment 8 Fedora End Of Life 2013-12-21 12:21:37 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 9 Fedora End Of Life 2014-02-05 20:10:35 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 10 Red Hat Bugzilla 2023-09-12 00:21:19 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.