Joined: 11 Apr 20
Thanks for taking me seriously and for the new/further advice!
Doing an update on EACH concerned project after changing, let's say, "anything" is basic procedure for me.
When there is no immediatly apparent change in behavior, I have also "learned" to suspend ALL projects AND exit BOINC Manager
AND re-boot the rig.
I have been doing this successfully for ages.
So, NO, the notices and messages do re-appear -- I have tried a lot of different scenarios before posting here.
Even running the cache empty before closing/shutting erverything down.
To repeating myself: It is a new (for me) BM behaviour after upgrading from 7.14.2 to 7.16.5 !
I will have a look at the VirtualBox issue. But I am not using VB at the moment.
Since the upgrade, I am unable to receive CPU jobs that I was pleasantly getting with v7.14.2.
I only upgraded, made no other changes (I know everone says that also) and since then no more CPU WU (on E@H), just GPU WUs.
Hereby the interesting thing is, that BM in event log does not bring/show the RED alert message for E@H, but just for the others,
which I am NOT running at all at the present time.
Side note for the people wondering why I am supposedly ranting my head off:
I have several rigs, which often have to be stoped/re-adjusted/finetuned (the rigs - not BOINC or projects) etc., that is why the Notice tab and the REd messages in the Event Log automatically attract my attention in the fear of me having done/changed something "wrong" and now affecting BOINC or whatever.
> Hope you had the nerve to read all the way to here <
Just checked Virtualbox Problem that you referred to.
The Event Log pointed out the problem quite well - maybe not for a newbie.
As someone pointed out, that these buggy messages are a nice SERVICE to the user, well, that raises the question on my side, why I am not informed that I have GPU turned OFF at my other projects?
Am I ranting again?
Joined: 5 Oct 06
To repeating myself: It is a new (for me) BM behaviour after upgrading from 7.14.2 to 7.16.5 !That's OK - and I did read right down to the bottom.
This may be a small point, but the messages we're talking about are displayed by the Manager, but generated by the client. I assume you did update, and subsequently stop/start, both components? (obviously, you would with a machine restart)
If it's any consolation, at least one of the core developers has written to say that he shares you irritation. I think some middle way will be found, but it may take a while.
Joined: 11 Apr 20
Sounds good if not even perfect ...
Patience will tell!
Hope you cought my EDIT1 and 2 ...
Here is EDIT 3:
Strange things are happening: Suddenly, AND I mean suddenly, I am receiving CPU WUs on E@H.
Being waiting for this over 24 hours.
So at least that small problem seems to be solved.
I wonder if somebody is tinkering around.
Maybe the "Easter bunny" got his paws off the FIC (Fiberglass Internet Connection) ....
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.