New news: https://root.ithena.net/usr/forum_thread.php?id=33

There has been no stats export since February 8th, 2020

Perhaps any connection with the project prefs, where I can't safe my permission to export stats?

---

Grüße vom Sänger

Yes. The problem occurred after the database migration. But the database works...

There's probably a bug somewhere...

I'm trying to find the problem.

There has been no stats export since February 8th, 2020

Perhaps any connection with the project prefs, where I can't safe my permission to export stats?

Because it gives a double database error?

Yes. The problem occurred after the database migration. But the database works...

There's probably a bug somewhere...

I'm trying to find the problem.

There may be a discrepancy between the database schema version and the server version
You can try to find and run the database update script from the upgrade kit, look for the part where all these bells and whistles with the new policy are added

But why change the version of the database schema with the server version?

The structure of the database remained unchanged.
The structure has not changed. This is the old structure compatible with this server.

Only the location of the database has changed. Now the database is in a dedicated system.

It's a clone of the old database.

The structure of the database remained unchanged.

all new options that appeared on the server (= WEB interface) must be activated synchronously in the database.

for example, consent to export, agreement with the new policy, choice of applications, number of processors / tasks, separate accounting for applications / subprojects.

all these options activate part of the interface, but they also require support in the database (the presence of the necessary fields in the tables or new tables)

you _must_ change the database so that already activated options work (2 errors in the preference settings). similarly for all new options needed now and in the future

I don't understand much.
I don't understand what options in the database you mean?

I made a 1:1 base dump.
The database is identical.
The database hasn't changed anything.

Only the location of the database has changed (different IP address, different user/password).
The content is the same.

Only the reference address to the database has changed (database content unchanged).
The current database contains all information about the number of processors, etc.
Ohh - I see very old information about my hosts.

Probably the problem is not the lack of information in the database.
The problem is that BOINC server wants to connect to the old database.

All the deamons are working (only some files not working). They see the new database location.
db_dump can't see the new data:

2020-02-25 19:44:12.8122 db_dump starting
Database error: The user specified as a definer ('boincadm'@'localhost') does not exist

db_dump wants to connect to the old database.
Currently there is no database on the localhost!

In the project configuration files there is no longer a database on the localhost and with the boincadm user.
This is a bug in the server.
Probably quite an old bug (maybe in a new version of softu already fixed?).

I made a 1:1 base dump.
The database is identical.
The database hasn't changed anything.

two new options were activated - activated on the server, but not supported in the database.
the database still remained unchanged, but the server configuration changed.
two new interface options (agreement with the policy and permission to export) cannot find the necessary fields in the database

I’m not sure that these options (primarily the policy) can easily be “cleaned up” on the server to the old state - to match the database.

In my 2nd line helpdesk days I often encountered that DBA's had copied a database and that the copy did not communicate with the rest of the software/database, as the old one did.
This was because each database has an Id for the communication and copying a database results in a new Id for communication, while replicating a database -which was the recommended procedure, but which can take far longer depending on the database size- does not alter that Id. Just my two cents.

Yes. The problem occurred after the database migration. But the database works...

There's probably a bug somewhere...

I'm trying to find the problem.

There may be a discrepancy between the database schema version and the server version
You can try to find and run the database update script from the upgrade kit, look for the part where all these bells and whistles with the new policy are added

I think Sergey Kovalchuk is on the right track. The various links from within the BOINC manager (e.g. forum, account) are also no longer connecting to iThena, only the main project page does.

Maybe it's about some specific permissions / configuration to the database.
But it seemed unlikely to me.
Any link to the BOINC documentation?

I was looking for information here: https://groups.google.com/a/ssl.berkeley.edu/forum/#!topic/boinc_projects/I8HKtRTPMgA.

Any ideas?
I didn't get any new information on the BOINC mailing list.

The various links from within the BOINC manager (e.g. forum, account) are also no longer connecting to iThena, only the main project page does.

Something changed on the server last week. IE has stopped working with the site. Chrome works.
Perhaps this is the "Global site tag (gtag.js) - Google Analytics"?

Any ideas?

only ideas, this is not practice

synchronization of users on different servers is required.
something like ~/rhosts, including for the database.

and delve into the stat dump script - find where the admin name is written there, it can be explicitly inside and not from the server config

if practical
it’s better to ask your colegs directly - they already "stepped on all this rake" ;-)
write Goofyx, Rebirther or Tomáš Brada
may be able to go to the admin Gaia@Home - he is also actively searching for problems with the server

Preference page error fixed: https://root.ithena.net/usr/prefs.php?subset=project

We're waiting for the results...

not everyone managed to allow the export and get into the last dump.
probably you need to run some extraordinary dumps in order to avoid losing stats on external sites

can at the same time add "run only selected applications"?
in case the new application is launched