Forum::BAM! Bug Report::[error] Bad signature for URL ...

[BOINCstats] Willy: Forum moderator - Administrator - Developer - Tester - Translator; BAM!ID: 1; Joined: 2006-01-09; Posts: 9440; Credits: 350,105,499; World-rank: 4,782

2011-03-08 05:53:44

That won't be the solution, it will we a bad fix.

The problem is that the client messes up the tags send by BAM!. That won't be fixed by making the whole opaque a CDATA field. Quite the opposite, that will break BAM! once again because the contents of opaque will be considered as text, not as XML.

Please do not PM, IM or email me for support (they will go unread/ignored). Use the forum for support.

jamas: BAM!ID: 95619; Joined: 2011-01-13; Posts: 2; Credits: 1,270,611; World-rank: 187,430

2011-03-18 16:14:57

I recently changed my OS to Ubuntu 10.04 x86 (32-bit) to Kubuntu 10.10 x86_64 (64-bit). With the boinc packages in the repos, I had the same issue with "acct_mgr_request empty or corrupt" error. However, on installing the updated development version from the boinc website, this error no longer occurs.

jamas: BAM!ID: 95619; Joined: 2011-01-13; Posts: 2; Credits: 1,270,611; World-rank: 187,430

2011-03-18 16:16:58

I recently changed my OS to Ubuntu 10.04 x86 (32-bit) to Kubuntu 10.10 x86_64 (64-bit). With the boinc packages in the repos, I had the same issue with "acct_mgr_request empty or corrupt" error. However, on installing the updated development version from the boinc website, this error no longer occurs.

MentalPower: BAM!ID: 21750; Joined: 2007-03-23; Posts: 3; Credits: 7,565,358; World-rank: 65,527

2011-03-25 21:46:28

Do you still need more info? I can confirm that this still occurs on BOINC client version 6.12.18 for x86_64-pc-linux-gnu.

[BOINCstats] Willy: Forum moderator - Administrator - Developer - Tester - Translator; BAM!ID: 1; Joined: 2006-01-09; Posts: 9440; Credits: 350,105,499; World-rank: 4,782

2011-03-26 05:57:09

MentalPower wrote:

Do you still need more info? I can confirm that this still occurs on BOINC client version 6.12.18 for x86_64-pc-linux-gnu.

In that case I'd like the see the section <opaque> of "acct_mgr_request.xml". It's at the end of the file. You can replace the actual host_authenticator code with something else but leave the rest (including line breaks and spaces) in it. Post it as code.

Please do not PM, IM or email me for support (they will go unread/ignored). Use the forum for support.

MentalPower: BAM!ID: 21750; Joined: 2007-03-23; Posts: 3; Credits: 7,565,358; World-rank: 65,527

2011-03-28 16:23:14

BOINCstats Willy wrote:

MentalPower wrote:

Do you still need more info? I can confirm that this still occurs on BOINC client version 6.12.18 for x86_64-pc-linux-gnu.

In that case I'd like the see the section <opaque> of "acct_mgr_request.xml". It's at the end of the file. You can replace the actual host_authenticator code with something else but leave the rest (including line breaks and spaces) in it. Post it as code.

Here you go!

Code:


<acct_mgr_request>

   <name>HiThere</name>

   <password_hash>HiThere</password_hash>

   <host_cpid>HiThere</host_cpid>

   <domain_name>ubuntu1</domain_name>

   <client_version>6.12.18</client_version>

   <run_mode>auto</run_mode>

   <previous_host_cpid>HiThere</previous_host_cpid>

<host_info>

    <timezone>-14400</timezone>

    <domain_name>ubuntu1</domain_name>

    <ip_addr>127.0.1.1</ip_addr>

    <host_cpid>HiThere</host_cpid>

    <p_ncpus>24</p_ncpus>

    <p_vendor>GenuineIntel</p_vendor>

    <p_model>Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz [Family 6 Model 44 Stepping 2]</p_model>

    <p_features>fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb r$

    <p_fpops>2465280719.202862</p_fpops>

    <p_iops>9373323850.791759</p_iops>

    <p_membw>1000000000.000000</p_membw>

    <p_calculated>1301089422.901866</p_calculated>

    <m_nbytes>12613914624.000000</m_nbytes>

    <m_cache>12582912.000000</m_cache>

    <m_swap>35643187200.000000</m_swap>

    <d_total>831499001856.000000</d_total>

    <d_free>787954016256.000000</d_free>

    <os_name>Linux</os_name>

    <os_version>2.6.32-28-server</os_version>

    <coprocs>

    </coprocs>

</host_info>

   <opaque>

<![CDATA[

<host_uhtiiccaaator>HiThere</host_authentictoor>

]]>

   </opaque>

</acct_mgr_request>

[BOINCstats] Willy: Forum moderator - Administrator - Developer - Tester - Translator; BAM!ID: 1; Joined: 2006-01-09; Posts: 9440; Credits: 350,105,499; World-rank: 4,782

2011-03-28 17:17:00
last modified: 2011-03-28 19:01:25

MentalPower wrote:

Here you go!

You are using a beta version which uses a in-between fix from the BOINC devs where they encapsulated the host-authenticator tag in CDATA. That doesn't work at all, and in the next release that will be gone again. No fix will be made for that at my end.

To clarify: by encapsulated the host-authenticator tag in CDATA the host-authenticator or any other value is no longer recognized as data but as a single text string. Although the XML will (probably) be valid, BAM! (or any other proper XML parser) can't get to the data for the host-authenticator.

Please do not PM, IM or email me for support (they will go unread/ignored). Use the forum for support.

MentalPower: BAM!ID: 21750; Joined: 2007-03-23; Posts: 3; Credits: 7,565,358; World-rank: 65,527

2011-03-31 13:30:35
last modified: 2011-03-31 13:31:36

BOINCstats Willy wrote:

You are using a beta version which uses a in-between fix from the BOINC devs where they encapsulated the host-authenticator tag in CDATA. That doesn't work at all, and in the next release that will be gone again. No fix will be made for that at my end.

To clarify: by encapsulated the host-authenticator tag in CDATA the host-authenticator or any other value is no longer recognized as data but as a single text string. Although the XML will (probably) be valid, BAM! (or any other proper XML parser) can't get to the data for the host-authenticator.

Ok, any idea which version is safe to use then? Neither the currently "recommended" nor the "development" versions work for different reasons. I can probably dig up any version ever released. Help is appreciated.

PS: I'd like to point out that without the CDATA encapsulation, that XML would not pass validation since the start and end tags don't match "<host_uhtiiccaaator>" vs "</host_authentictoor>". I don't know how the account managers do their job so I'm just putting that out there as a stray comment.

[BOINCstats] Willy: Forum moderator - Administrator - Developer - Tester - Translator; BAM!ID: 1; Joined: 2006-01-09; Posts: 9440; Credits: 350,105,499; World-rank: 4,782

2011-03-31 14:38:49

MentalPower wrote:

Ok, any idea which version is safe to use then? Neither the currently "recommended" nor the "development" versions work for different reasons. I can probably dig up any version ever released. Help is appreciated.

Anything but the current latest development version.

MentalPower wrote:

PS: I'd like to point out that without the CDATA encapsulation, that XML would not pass validation since the start and end tags don't match "<host_uhtiiccaaator>" vs "</host_authentictoor>". I don't know how the account managers do their job so I'm just putting that out there as a stray comment.

I have a fix in place that repairs the XML on the fly. I don't know what other AMS's do, but the host_authenticator field is a BAM! addition.

Please do not PM, IM or email me for support (they will go unread/ignored). Use the forum for support.

Jeff17: Tester - BOINCstats SOFA member; BAM!ID: 47291; Joined: 2008-03-03; Posts: 441; Credits: 11,393,676,907; World-rank: 360

2011-04-06 12:51:04

Willy,

I can confirm your fix is working for my host. Both automatic and manual syncs to BAM work.
Linux x86_64 Ubuntu 10.04
BOINC 6.10.58

Thanks
Jeff

ebahapo: BAM!ID: 239; Joined: 2006-05-12; Posts: 662; Credits: 18,928,018; World-rank: 35,117

2011-04-06 14:54:15

Jeff17 wrote:

I can confirm your fix is working for my host. Both automatic and manual syncs to BAM work.
Linux x86_64 Ubuntu 10.04
BOINC 6.10.58

I confirm that the same set up works for me too.

However, I still see this message for new projects:

Bad signature for URL http://dnahome.cs.rpi.edu/dna/

Status

Shoutbox