Posts by admin@friendica.utzer.de
(DIR) Post #A37oXHOtQ5txTb5WNc by admin@friendica.utzer.de
2021-01-11T10:11:25Z
0 likes, 0 repeats
I deleted about 90 users, which gave me 180000 tasks in the queue. Didn't think about that before, but that will take a few hours now. @helpers #Friendica
(DIR) Post #A4yjVM1VbcYmlNmVMW by admin@friendica.utzer.de
2021-03-01T14:29:39Z
0 likes, 0 repeats
Please check if the "data" field contains a value there. If not then you have got a problem. The backend-class should only be empty when you still store your pictures in the database.Please check if you have got a field in the storage table with the id "670476". Also check if in the storage folder there is some file that contains this id. I don't know the exact format of the stored pictures, so I can't give you a hint for the exact filename.I missed that comment. Need to figure out how to check that in mysql cli.
(DIR) Post #A4yjVNUGAD9VIqEyoa by admin@friendica.utzer.de
2021-03-02T17:34:59Z
0 likes, 0 repeats
Did you find out what the problem is? I was thinking when I should switch to the RC, will this be fixed in RC or only in a future release? Is this a problem specific to my system?
(DIR) Post #A4yjVOBrY61xU4dnmK by admin@friendica.utzer.de
2021-03-06T07:01:39Z
0 likes, 0 repeats
Wochenende... 😉 If you need any info/action from my side let me know.
(DIR) Post #A4yjVOqd6WdlWViMK0 by admin@friendica.utzer.de
2021-03-06T19:16:11Z
0 likes, 0 repeats
update photo inner join storage on storage.id = photo.`backend-ref` set `backend-class` = 'Database' where photo.data = '' and `backend-class` = '' and `backend-ref` != '';Query OK, 1625 rows affected (0.302 sec)Rows matched: 1625 Changed: 1625 Warnings: 0done
(DIR) Post #A4yjVPBXqlN2ZNV3vE by admin@friendica.utzer.de
2021-03-07T11:54:06Z
0 likes, 0 repeats
@heluecht I think I can execute this again and again and again and it will always find new rows. My uneducated guess would be that the move does not set this and the move is still ongoing. See here: MariaDB [friendica]> update photo inner join storage on storage.id = photo.`backend-ref` set `backend-class` = 'Database' where photo.data = '' and `backend-class` = '' and `backend-ref` != '';Query OK, 500 rows affected (0.077 sec)Rows matched: 500 Changed: 500 Warnings: 0MariaDB [friendica]> update photo inner join storage on storage.id = photo.`backend-ref` set `backend-class` = 'Database' where photo.data = '' and `backend-class` = '' and `backend-ref` != '';Query OK, 245 rows affected (0.059 sec)Rows matched: 245 Changed: 245 Warnings: 0MariaDB [friendica]> update photo inner join storage on storage.id = photo.`backend-ref` set `backend-class` = 'Database' where photo.data = '' and `backend-class` = '' and `backend-ref` != '';Query OK, 89 rows affected (0.052 sec)Rows matched: 89 Changed: 89 Warnings: 0MariaDB [friendica]> update photo inner join storage on storage.id = photo.`backend-ref` set `backend-class` = 'Database' where photo.data = '' and `backend-class` = '' and `backend-ref` != '';Query OK, 73 rows affected (0.049 sec)Rows matched: 73 Changed: 73 Warnings: 0MariaDB [friendica]> update photo inner join storage on storage.id = photo.`backend-ref` set `backend-class` = 'Database' where photo.data = '' and `backend-class` = '' and `backend-ref` != '';Query OK, 77 rows affected (0.044 sec)Rows matched: 77 Changed: 77 Warnings: 0MariaDB [friendica]> update photo inner join storage on storage.id = photo.`backend-ref` set `backend-class` = 'Database' where photo.data = '' and `backend-class` = '' and `backend-ref` != '';Query OK, 67 rows affected (0.049 sec)Rows matched: 67 Changed: 67 Warnings: 0MariaDB [friendica]> update photo inner join storage on storage.id = photo.`backend-ref` set `backend-class` = 'Database' where photo.data = '' and `backend-class` = '' and `backend-ref` != '';Query OK, 86 rows affected (0.051 sec)Rows matched: 86 Changed: 86 Warnings: 0MariaDB [friendica]> update photo inner join storage on storage.id = photo.`backend-ref` set `backend-class` = 'Database' where photo.data = '' and `backend-class` = '' and `backend-ref` != '';Query OK, 67 rows affected (0.048 sec)Rows matched: 67 Changed: 67 Warnings: 0MariaDB [friendica]> update photo inner join storage on storage.id = photo.`backend-ref` set `backend-class` = 'Database' where photo.data = '' and `backend-class` = '' and `backend-ref` != '';Query OK, 87 rows affected (0.048 sec)Rows matched: 87 Changed: 87 Warnings: 0
(DIR) Post #A4yjVPsRHHgKiPZJmS by admin@friendica.utzer.de
2021-03-07T13:32:28Z
0 likes, 0 repeats
I think some pictures were lost also... for example the old profile photo of this account is gone. Also another question, can I somehow initiate that the server pulls all remote profile information for all known contacts? I mean all contacts that are somehow connected to users on this server.
(DIR) Post #A4yjVQcAXGGH0Exq3k by admin@friendica.utzer.de
2021-03-07T13:44:01Z
0 likes, 0 repeats
is that the setting in /admin/site "Auto-discovered contact directory" - "Days between enquiry"? Maybe I will set this to 2 days to force it to happen?
(DIR) Post #A4yjVRP5bNORRxquJM by admin@friendica.utzer.de
2021-03-07T13:57:28Z
0 likes, 0 repeats
hmm ok, so until this happens the profile pictures will be missing. Just in case this would be easy to trigger, such a trigger seems to be helpful to be added to bin/console.
(DIR) Post #A58FHenDyBojsUFfUm by admin@friendica.utzer.de
2021-03-07T14:19:10Z
0 likes, 0 repeats
also agree that there is something strange here.The contact update was something I wished to have before, not for this problem. I think that sometimes it just takes to long for profile changes to arrive, so I sometimes wished I had a manual way to fix this.
(DIR) Post #A58FHf9Yd9gKzkhVJ2 by admin@friendica.utzer.de
2021-03-07T20:06:19Z
0 likes, 0 repeats
stagely it will only find 500 rows maximum, each time I run it after some time, ie. some hours, it will find 500 maximum, a few on the second time I execute it and now there after. Query OK, 500 rows affected (0.063 sec)Rows matched: 500 Changed: 500 Warnings: 0
(DIR) Post #A58FHfU7Oi821WJvM0 by admin@friendica.utzer.de
2021-03-07T20:57:30Z
0 likes, 0 repeats
again me... I don't know why I never did that before, but now after I switched to the RC and ran mysql_upgrade (seems that is sometimes needed after mariadb updates, I fired up mytop when I restarted the move process and from time to time I see this:and then also this: So it seems this is what is needed, right?
(DIR) Post #A58FHfogAGZj3HwLOy by admin@friendica.utzer.de
2021-03-07T21:04:46Z
0 likes, 0 repeats
or does it - SET `backend-class` = '' - in fact set an empty backend class? Commit UPDATE `photo` SET `backend-class` = '', `backend-ref` = 37368503, `data` = '' WHERE (`id` = 577936)
(DIR) Post #A58FHgWzVW1LGifjTE by admin@friendica.utzer.de
2021-03-07T21:35:20Z
0 likes, 0 repeats
From filesystem to database.
(DIR) Post #A58FHhJYawrvhLOWAa by admin@friendica.utzer.de
2021-03-12T08:53:15Z
0 likes, 0 repeats
did you already create a pull request for this in the current RC?
(DIR) Post #A58FHi4LmyIc2THt6e by admin@friendica.utzer.de
2021-03-12T10:45:02Z
0 likes, 0 repeats
It could be that the photos you see missing are in reality in 'storage' table, but 'photo.backend-ref' is pointing to the row with empty data.Problem is you probably never manage to find which "orphan" photo data in 'storage' goes with which row in 'photo' table, because there is no filename in 'storage' table, only data...Meaning, you don't think it can be fixed?
(DIR) Post #A9VdLn41uLvCsaWCeW by admin@friendica.utzer.de
2021-07-21T09:27:48Z
0 likes, 0 repeats
I did not interact with this post from this account, now I wonder why I get notifications for this thread and if every user of Friendica gets notifications or just admins? I guess any user where this post is available on the server? So it is like a broadcast post function. 😛
(DIR) Post #AVJsO9oHhv73l8kWno by admin@friendica.utzer.de
2023-05-03T18:16:56Z
1 likes, 0 repeats
New troll domain with many subdomains. This is a strongly recommended block for all #Fediverse services for *.mastotroll.netz.org.Please share this post!#Friendica !adminscc @utzer
(DIR) Post #AZcTSrFHRZudZV5nbU by admin@friendica.utzer.de
2023-09-10T09:09:35Z
0 likes, 0 repeats
OK @developers we got to talk.I have been patient (not that much, I know) but now we really have to solve the deleted users don't get deleted issue.There were some users on my server that signed up and started sharing sexual abuse of children and there is no way I can delete these users because the deletion stopped working months ago. The profiles will be listed in the deleted tab in moderation forever and the remote posts will not be deleted. So there is CP from theses accounts out there just because the deletion is not working.Locally I can not see these posts.This is really aggravating.Issue on github:https://github.com/friendica/friendica/issues/12876cc @utzer
(DIR) Post #AcP41aXFy2DffQM41Y by admin@friendica.utzer.de
2023-12-01T12:04:31Z
1 likes, 0 repeats
Hier auch.