Mind Modeling Issue

Message boards : Projects : Mind Modeling Issue
Message board moderation

To post messages, you must log in.

AuthorMessage
Kaziqi

Send message
Joined: 23 Aug 20
Posts: 1
Message 100422 - Posted: 23 Aug 2020, 14:57:09 UTC

I get the following message on my boinc notices about MindModeling:
MindModeling: Notice from BOINC
This project is using an old URL. When convenient, remove the project, then add http://mindmodeling.org/
23/08/2020 15:47:01

But I am unable to remove the project from my projects list, even going into the advanced view, removal of the project is grayed out.
Any guesses what I should try?

Thanks
ID: 100422 · Report as offensive
Bryn Mawr
Help desk expert

Send message
Joined: 31 Dec 18
Posts: 154
United Kingdom
Message 100424 - Posted: 23 Aug 2020, 15:00:31 UTC - in response to Message 100422.  

I get the following message on my boinc notices about MindModeling:
MindModeling: Notice from BOINC
This project is using an old URL. When convenient, remove the project, then add http://mindmodeling.org/
23/08/2020 15:47:01

But I am unable to remove the project from my projects list, even going into the advanced view, removal of the project is grayed out.
Any guesses what I should try?

Thanks


It sounds like you're using an account manager - something like BAM or Science United. If this is the case you can only do the deed from the account manager.
ID: 100424 · Report as offensive
brett5355

Send message
Joined: 31 Mar 19
Posts: 8
United States
Message 100770 - Posted: 17 Sep 2020, 9:23:06 UTC - in response to Message 100424.  

I was getting the same message, but now I get this one as well:

MindModeling: Notice from BOINC
You are attached to this project twice. Please remove projects named MindModeling, then add http://mindmodeling.org/
9/17/2020 1:11:54 AM

As far as I can tell I am only running it once.
Also like the earlier message, I cannot remove it as that option is greyed out.
ID: 100770 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 14625
Netherlands
Message 100772 - Posted: 17 Sep 2020, 12:07:54 UTC - in response to Message 100770.  

If the project is greyed out that means you have added it via an account manager such as BAM, GridRepublic or Science United
ID: 100772 · Report as offensive
Dr Who Fan
Avatar

Send message
Joined: 10 May 07
Posts: 689
United States
Message 100774 - Posted: 17 Sep 2020, 17:44:40 UTC

I get the same exact message across all 5 PC's attached to the project but do not use any account manager (s).

I think someone hacked did something to the project server.

The project forums are a SPAM message haven; There are NO project administrator around to deal with it and no administrator has replied to any PM sent as to what is going on with the project.
ID: 100774 · Report as offensive
Les Bayliss
Help desk expert

Send message
Joined: 25 Nov 05
Posts: 1486
Australia
Message 100779 - Posted: 18 Sep 2020, 1:43:58 UTC

Would deleting / moving-to-a-different-folder, the file: account----.xml, and then restarting BOINC, cause the project to "disappear"?
ID: 100779 · Report as offensive
Dr Who Fan
Avatar

Send message
Joined: 10 May 07
Posts: 689
United States
Message 100788 - Posted: 19 Sep 2020, 21:24:38 UTC

Problem not resolved at MindModeling.
.
To try and fix the problem at MindModeling I was able to detach from the project, then Downloaded and installed latest BOINC 7.16.11 for Windows. After upgrading, restarting and reattaching all 5 of my PC's to MindModeling@home using http I still get the RED notice below.
MindModeling: Notice from BOINC
You are attached to this project twice. Please remove projects named MindModeling, then add http://mindmodeling.org/
9/19/2020 15:42:15


I had posted on the project forum yesterday about the problem and received a reply from the project admin earlier today and was told this:
you have a new version of the boinc, this is the work of one of the improvements.
read carefully Release notes for the BOINC Client 7.16.11
Client: let a project master URL change from http: to https: without involving the user.

check logs from other projects.
you are a longtime user, there must be many connections before switching to https.


After upgrade, I noticed earlier today same "double connect" message from from Moo! Wrapper so I detached and reattached via http to that project with no new warning messages.

Not sure what server version MindModeling project is using and if that makes a difference.
Moo! Wrapper web site says Server software version: 1.2.1 on the project status page.

I can provide logs from one PC's stderr on a download link if that will help in figuring out .
ID: 100788 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 14625
Netherlands
Message 100789 - Posted: 20 Sep 2020, 1:50:50 UTC - in response to Message 100788.  

Not sure what server version MindModeling project is using and if that makes a difference.
Database schema version: 27013, "update_4_15_2015".
ID: 100789 · Report as offensive
Dr Who Fan
Avatar

Send message
Joined: 10 May 07
Posts: 689
United States
Message 100790 - Posted: 20 Sep 2020, 7:13:30 UTC

Did a bit more looking around I discovered the URL listed for MindModeling is https not http in the BOINC 7.16.11 ADD PROJECT drop-down selection list.

Moo! Wrapper master URL is http in the list.
Could this be the reason we are getting the error message of being "twice attached"?
ID: 100790 · Report as offensive
Dr Who Fan
Avatar

Send message
Joined: 10 May 07
Posts: 689
United States
Message 100793 - Posted: 20 Sep 2020, 18:36:04 UTC

I think I might have solved the double attach issue!
Last time I reattached using using the built-in BOINC list with https Short while ago I removed the project, re-added it MANUALLY using http across my 5 PC's and so far I have not seen the double attach message.
ID: 100793 · Report as offensive
Dr Who Fan
Avatar

Send message
Joined: 10 May 07
Posts: 689
United States
Message 100794 - Posted: 20 Sep 2020, 23:56:01 UTC

In the 5+ hours since I re-attached my y 5 PC's the error message has not shown up..

All that is need now is to get a change in the MASTER BOINC PROJECTS LIST to http for the project to prevent other users from getting the error.
ID: 100794 · Report as offensive
Bryn Mawr
Help desk expert

Send message
Joined: 31 Dec 18
Posts: 154
United Kingdom
Message 100795 - Posted: 21 Sep 2020, 9:04:11 UTC - in response to Message 100794.  

In the 5+ hours since I re-attached my y 5 PC's the error message has not shown up..

All that is need now is to get a change in the MASTER BOINC PROJECTS LIST to http for the project to prevent other users from getting the error.


That is controlled by the project rather than Boinc.
ID: 100795 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 4498
United Kingdom
Message 100796 - Posted: 21 Sep 2020, 9:37:37 UTC - in response to Message 100795.  

That is controlled by the project rather than Boinc.
It's even more complicated than that.

There are three different ways of connecting to a project.

1) via BOINC Manager.

The Manager takes the value from the all_projects_list, but validates it with the project via a call to get_project_config.php
The project will be attached using the returned value - which may even be a completely different domain, let alone swapping between https / http.

2) via boinccmd.

The project will be attached using the url you supply - unchecked.

3) via an Account Manager.

The project will be attached using a url specified by the AM administrator - unchecked.

In the current case (MindModelling), somebody suggested using http://mindmodeling.org/. If you paste that into a browser, you are redirected to https://mindmodeling.org/

But https://mindmodeling.org/get_project_config.php returns

<master_url>mindmodeling.org/</master_url>
without a protocol specifier - which is a project mistake. The results are probably undefined.

The only way you can get attached twice is if you use two different methods - usually, both an Account Manager and a native BOINC route. It's best not to do that.
ID: 100796 · Report as offensive
Profile Dave

Send message
Joined: 28 Jun 10
Posts: 1377
United Kingdom
Message 100798 - Posted: 21 Sep 2020, 11:24:45 UTC

There are three different ways of connecting to a project.

1) via BOINC Manager.

The Manager takes the value from the all_projects_list, but validates it with the project via a call to get_project_config.php
The project will be attached using the returned value - which may even be a completely different domain, let alone swapping between https / http.


I am probably being a bit picky here but you can also type or paste a url directly into the manager to attach to a project. - For me the easiest way with testing branch of a project which isn't listed in the drop down menu for instance.
ID: 100798 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 4498
United Kingdom
Message 100799 - Posted: 21 Sep 2020, 12:14:29 UTC - in response to Message 100798.  

I am probably being a bit picky here but you can also type or paste a url directly into the manager to attach to a project. - For me the easiest way with testing branch of a project which isn't listed in the drop down menu for instance.
I think (but I'm not certain) that if you paste a url into the GUI 'Add project' wizard', it'll still get checked through the 'get_project_config.php' mechanism.
ID: 100799 · Report as offensive
Profile Dave

Send message
Joined: 28 Jun 10
Posts: 1377
United Kingdom
Message 100808 - Posted: 21 Sep 2020, 18:25:32 UTC - in response to Message 100799.  

I think (but I'm not certain) that if you paste a url into the GUI 'Add project' wizard', it'll still get checked through the 'get_project_config.php' mechanism.


You are far more likely to know that than I am Richard so I will bow to your superior knowledge!
ID: 100808 · Report as offensive

Message boards : Projects : Mind Modeling Issue

Copyright © 2021 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.