Bug 243197 - astro/boinc-setiathome: app_info.xml file doesn't have a usable version of SETI@home
Summary: astro/boinc-setiathome: app_info.xml file doesn't have a usable version of SE...
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Larry Rosenman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-08 19:12 UTC by Scott Loga
Modified: 2023-01-10 19:33 UTC (History)
6 users (show)

See Also:
w.schwarzenfeld: maintainer-feedback? (ler)


Attachments
app_info.xml File Attached (346 bytes, text/plain)
2020-01-10 00:52 UTC, Scott Loga
no flags Details
ler's app_info.xml (2.23 KB, text/plain)
2020-01-10 01:02 UTC, Larry Rosenman
no flags Details
Output Messages from Boinc-Client (984 bytes, text/plain)
2020-01-10 04:18 UTC, Scott Loga
no flags Details
Output Message indicating absent file (1.80 KB, text/plain)
2020-01-11 21:09 UTC, Scott Loga
no flags Details
Task from Seti at Home web site (27.47 KB, application/pdf)
2020-01-11 21:36 UTC, Scott Loga
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Loga 2020-01-08 19:12:41 UTC
Installed the latest astro/setiathome-8.00_3 and net/boinc-client-7.8.6_10. Executing the command 'boinccmd --get_messages' I receive the following:

340: 08-Jan-2020 11:18:25 (user notification) [SETI@home] Message from server: Your app_info.xml file doesn't have a usable version of SETI@home v8.

As a result, no work units from the project are processed.
Comment 1 Larry Rosenman freebsd_committer freebsd_triage 2020-01-09 22:26:23 UTC
can you attach a copy of your

/var/db/boinc/projects/setiathome.berkeley.edu/app_info.xml

file?

thanks!
Comment 2 Scott Loga 2020-01-10 00:52:59 UTC
Created attachment 210578 [details]
app_info.xml File Attached

Larry, I apologize for not sending the file initially.  Please let me know if you need any additional information.

Regards,

Scott
Comment 3 Larry Rosenman freebsd_committer freebsd_triage 2020-01-10 01:00:32 UTC
What's weird for me is that my app_info.xml has a tone of that block repeated, and it works for me.

Unfortunately, I've seen this before and it went away on it's own, but I'm not sure why/how.
Comment 4 Larry Rosenman freebsd_committer freebsd_triage 2020-01-10 01:02:22 UTC
Created attachment 210580 [details]
ler's app_info.xml

My (ler) app_info.xml.

Can you try replacing it (saving yours)?
Comment 5 Scott Loga 2020-01-10 04:18:18 UTC
Created attachment 210582 [details]
Output Messages from Boinc-Client

Larry, I saved my original app_info.xml file and imported yours.  Initially, it seems to work.  I reset the setiathome project and it reported 1 completed task, however, I'm still receiving the same error.  I will let it run 24/7 and see if it will still process additional tasks.

I have included as an attachment the latest messages from the boinc-client.

I report back my findings.

Regards,

Scott
Comment 6 Scott Loga 2020-01-11 21:09:24 UTC
Created attachment 210637 [details]
Output Message indicating absent file

Larry,

I'm still receiving the message "Your app_info.xml file doesn't have a usable version of SETI@home v8".  Boinc seems to download a task then performs calculations.  However, reviewing the messages from the Boinc-Client I noticed a message "Output file NNN for task NNN absent" which seems to repeat itself.  Please see the attached file for further review.

Regards,

Scott
Comment 7 Larry Rosenman freebsd_committer freebsd_triage 2020-01-11 21:22:07 UTC
weird.  Mine works fine.  I wish I had a better idea on what was going on. 

[I] ➜ tail -50 stdoutdae.txt
11-Jan-2020 14:02:11 [SETI@home] Finished upload of 09no15ab.30843.20137.14.41.181.vlar_1_r1797506317_0
11-Jan-2020 14:05:22 [SETI@home] Sending scheduler request: To report completed tasks.
11-Jan-2020 14:05:22 [SETI@home] Reporting 5 completed tasks
11-Jan-2020 14:05:22 [SETI@home] Requesting new tasks for CPU
11-Jan-2020 14:05:24 [SETI@home] Scheduler request completed: got 4 new tasks
11-Jan-2020 14:05:26 [SETI@home] Started download of 09my15ab.5753.23797.11.38.173.vlar
11-Jan-2020 14:05:26 [SETI@home] Started download of blc14_2bit_guppi_58691_60864_HIP21547_0029.29964.409.21.44.33.vlar
11-Jan-2020 14:05:29 [SETI@home] Finished download of 09my15ab.5753.23797.11.38.173.vlar
11-Jan-2020 14:05:29 [SETI@home] Finished download of blc14_2bit_guppi_58691_60864_HIP21547_0029.29964.409.21.44.33.vlar
11-Jan-2020 14:05:29 [SETI@home] Started download of 24ja12af.8039.32271.12.39.3
11-Jan-2020 14:05:29 [SETI@home] Started download of blc14_2bit_guppi_58691_61185_HIP21870_0030.31897.0.22.45.123
11-Jan-2020 14:05:31 [SETI@home] Finished download of 24ja12af.8039.32271.12.39.3
11-Jan-2020 14:05:31 [SETI@home] Finished download of blc14_2bit_guppi_58691_61185_HIP21870_0030.31897.0.22.45.123
Comment 8 Scott Loga 2020-01-11 21:36:34 UTC
Created attachment 210638 [details]
Task from Seti at Home web site

Larry,

On my account for Seti At Home, I noticed all my tasks for this computer show "Error while computing".  I have attached a pdf view of the page which shows the latest task.  Please look at the Stderr outup section.  There appears to be an Undefined Symbol in libboinc_api.so.7.  Not sure if you can shed some light on this.

By the way, my uname output is FreeBSD fisher.loga.us 12.1-RELEASE-p1 FreeBSD 12.1-RELEASE-p1 GENERIC  amd64

Regards,

Scott
Comment 9 Larry Rosenman freebsd_committer freebsd_triage 2020-01-11 22:25:52 UTC
what's interesting is that symbol is in -lboinc, and resolved in the setiathome binary.

do you have:
[I] ➜ more cc_config.xml
<cc_config>
<options>
<alt_platform>i686-pc-linux-gnu</alt_platform>
</options>
</cc_config>

in your setup?

I'm not sure what binary isn't resolving that :(
Comment 10 Scott Loga 2020-01-12 02:18:40 UTC
There is no cc_config.xml in my setup. Would it normally be created upon pkg install or is it manually created?
Comment 11 Larry Rosenman freebsd_committer freebsd_triage 2020-01-12 02:45:14 UTC
manually.  I had created it long ago.  I'm really at a loss as to why mine works and yours doesn't.
Comment 12 Scott Loga 2020-01-14 13:08:04 UTC
Larry,

Just an update.  I removed and reinstalled Boinc and setiathome.  Still have the same issue.  Next, I installed the same on a bhyve VM on my FreeNAS Server.  It works just fine!  The issue must be related to something conflicting on my Laptop.  The laptop is an Lenovo Thinkpad 480 with FreeBSD 12.1 and KDE Plasma.  Let me fiddle with my laptop and see what's causing the issue before we close this bug report.

73,

Scott - w5plt
Comment 13 Scott Loga 2020-01-17 13:42:01 UTC
Larry,

Stated thinking about the original message:

340: 08-Jan-2020 11:18:25 (user notification) [SETI@home] Message from server: Your app_info.xml file doesn't have a usable version of SETI@home v8.

Since was able to compile the Non-GUI / No X11 options of setiathome/BOINC from the Ports Tree on my bhyve VM (FreeBSD 12.1) which does not have X11 installed, it worked just fine.  Its just a server for DNS, LDAP, etc.

On my laptop, I have FreeBSD 12.1 with KDE5 Plasma with setiathome/BOINC installed from pkg.

I notice the binary /var/db/boinc/projects/setiathome.berkeley.edu/setiathome-8.0.amd64-portbld-freebsd from the non-gui version is 1378415 bytes.  The pkg version of the same is 1652912 bytes.

So I copied the file setiathome-8.0.amd64-portbld-freebsd from my bhyve VM to my laptop.  It is working now.

Why are the two versions of the file different in size?

I'm still in the process of doing more testing..

Regards,

Scott
Comment 14 Scott Loga 2020-01-20 21:47:28 UTC
Larry,

Just a final follow up.  I installed, from pkg, boinc-client and boinc-setiathome on my digital ocean droplet.  I receive the same error as on my Laptop:

20-Jan-2020 15:32:01 [SETI@home] Your app_info.xml file doesn't have a usable version of SETI@home v8.

I also receive the following as well on both computers:

20-Jan-2020 15:13:31 [SETI@home] Output file blc61_2bit_guppi_58692_60105_HIP22741_0027.10878.409.21.44.151.vlar_0_r91068579_0 for task blc61_2bit_guppi_58692_60105_HIP22741_0027.10878.409.21.44.151.vlar_0 absent

Not sure if these issues are boinc or setiathome issues but at least I can confirm it is occurring on two separate computers running FreeBSD 12.1 with and without X11.  However, if you build boinc and setiathome from ports without GUI or X11 support it works as expected.

Regards,

Scott
Comment 15 Scott Loga 2020-01-20 21:47:51 UTC
Larry,

Just a final follow up.  I installed, from pkg, boinc-client and boinc-setiathome on my digital ocean droplet.  I receive the same error as on my Laptop:

20-Jan-2020 15:32:01 [SETI@home] Your app_info.xml file doesn't have a usable version of SETI@home v8.

I also receive the following as well on both computers:

20-Jan-2020 15:13:31 [SETI@home] Output file blc61_2bit_guppi_58692_60105_HIP22741_0027.10878.409.21.44.151.vlar_0_r91068579_0 for task blc61_2bit_guppi_58692_60105_HIP22741_0027.10878.409.21.44.151.vlar_0 absent

Not sure if these issues are boinc or setiathome issues but at least I can confirm it is occurring on two separate computers running FreeBSD 12.1 with and without X11.  However, if you build boinc and setiathome from ports without GUI or X11 support it works as expected.

Regards,

Scott
Comment 16 Alexey Dokuchaev freebsd_committer freebsd_triage 2020-07-08 13:18:42 UTC
(In reply to Larry Rosenman from comment #9)
> <alt_platform>i686-pc-linux-gnu</alt_platform>
Speaking of which...  I was quite puzzled by those "This project doesn't support computers of type x86_64-pc-freebsd-pc-freebsd" messages when I've tried to run freshly built and installed client, until I've discovered this page:

    https://boinc.berkeley.edu/wiki/Installing_on_FreeBSD

What do you think about adding --with-boinc-alt-platform=i686-pc-linux-gnu to the CONFIGURE_ARGS so it works out of the box?  Explicit --with-boinc-platform is probably not needed as it's apparently get defined correctly on its own.
Comment 17 Daniel Engberg freebsd_committer freebsd_triage 2023-01-10 19:33:37 UTC
No longer relevant, port removed in 7cf78ca64283b960af4b2f070a7117dc6d000dee