Hubzilla Support Forum

Hubzilla Support Forum

support@zotadel.net

Mark all messages in a forum as read?

Mon, 27 Mar 2023 13:59:02 +0200

support@zotadel.net

Harald Eilertsen wrote the following post Mon, 27 Mar 2023 13:58:04 +0200

Mark all messages in a forum as read?

I haven't found a way to mark all messages in a forum as read, other than to scroll past all of them. Especially for larger forums where I haven't been in them from the beginning, this would be a welcome feature. I'm probably never going to scroll back to the very beginning of the forum.

Are there any tricks I have not discovered yet?

"Refurbished" worker doesn't want to work

Sat, 25 Mar 2023 22:34:53 +0100

Hubzilla Support Forum

support@zotadel.net

0mega 🕱 [hz] wrote the following post Sat, 25 Mar 2023 22:34:53 +0100

"Refurbished" worker doesn't want to work

Hello,

several days after upgrading my Hubzilla to 8.2 I noticed something strange. Interaction with posts didn't get federated/sent to servers, post weren't showing up in Diaspora or ActivityPub servers. I finally had some time to take a look at the logfile and it also gives me a hint about the lazy worker:

loooong logfile spoiler

webserver2:/# grep -e "workerq" /var/www/html/hzlogs
2023-03-25T21:11:05Z:LOG_INFO:247dae41e1:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:11:08Z:LOG_INFO:0a5f2e3441:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:11:14Z:LOG_INFO:b04b344e8c:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:11:32Z:LOG_INFO:b62756afce:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:11:45Z:LOG_INFO:35b01289e8:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:12:03Z:LOG_INFO:fda3474962:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:12:10Z:LOG_INFO:cad597389d:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:12:29Z:LOG_INFO:000bfc33fa:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:12:32Z:LOG_INFO:f91f96cb2f:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:12:36Z:LOG_INFO:39807e2ca4:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:12:38Z:LOG_INFO:4b04cbab68:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:13:06Z:LOG_INFO:1d87f5b665:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:13:15Z:LOG_INFO:766ea14712:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:13:20Z:LOG_INFO:63cb56bbd9:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:13:39Z:LOG_INFO:6512093788:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:13:44Z:LOG_INFO:2ad18d8390:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:13:55Z:LOG_INFO:20ead33078:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:14:05Z:LOG_ERR:ebd8f194e6:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:14:05Z:LOG_ERR:c6f9283736:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:14:05Z:LOG_ERR:c6f9283736:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:14:05Z:LOG_ERR:c6f9283736:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id, workerq_cmd FROM workerq WHERE workerq_reservationid IS NULL ORDER BY workerq_priority DESC, workerq_id ASC LIMIT 1 FOR UPDATE NOWAIT
2023-03-25T21:14:06Z:LOG_INFO:af410eee46:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:14:32Z:LOG_INFO:864564bc69:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:14:35Z:LOG_INFO:117434de08:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:14:45Z:LOG_INFO:06afbaa3ee:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:15:02Z:LOG_INFO:3705ec455b:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:15:10Z:LOG_INFO:90522229a9:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:15:32Z:LOG_INFO:dc648414d9:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:16:02Z:LOG_INFO:f1d3cf5f96:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:16:09Z:LOG_INFO:fc8d2aae5c:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:16:30Z:LOG_INFO:3a0d9a3c2e:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:16:50Z:LOG_INFO:b116869f42:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:16:53Z:LOG_INFO:7b8af31359:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:16:57Z:LOG_ERR:d455725c59:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:16:57Z:LOG_ERR:140a4f51a6:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:16:57Z:LOG_ERR:140a4f51a6:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:16:57Z:LOG_ERR:140a4f51a6:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id, workerq_cmd FROM workerq WHERE workerq_reservationid IS NULL ORDER BY workerq_priority DESC, workerq_id ASC LIMIT 1 FOR UPDATE NOWAIT
2023-03-25T21:17:05Z:LOG_INFO:8296f0251c:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:17:13Z:LOG_INFO:f4a8c2a123:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:17:19Z:LOG_INFO:f2e540fe92:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:17:44Z:LOG_INFO:5f313be667:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:17:54Z:LOG_INFO:192a7d4742:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:18:06Z:LOG_INFO:3adb964fdb:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:18:06Z:LOG_ERR:e17361ac17:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:18:07Z:LOG_ERR:9eaa52345a:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:18:07Z:LOG_ERR:9eaa52345a:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:18:07Z:LOG_ERR:9eaa52345a:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id, workerq_cmd FROM workerq WHERE workerq_reservationid IS NULL ORDER BY workerq_priority DESC, workerq_id ASC LIMIT 1 FOR UPDATE NOWAIT
2023-03-25T21:18:09Z:LOG_INFO:6301a10012:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:18:13Z:LOG_INFO:07b54c1a62:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:18:26Z:LOG_INFO:f77fdb638b:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:18:30Z:LOG_INFO:08d644c62e:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:18:36Z:LOG_ERR:70ceaf6df4:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:18:36Z:LOG_ERR:7809fbe50a:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:18:36Z:LOG_ERR:7809fbe50a:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:18:36Z:LOG_ERR:7809fbe50a:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id, workerq_cmd FROM workerq WHERE workerq_reservationid IS NULL ORDER BY workerq_priority DESC, workerq_id ASC LIMIT 1 FOR UPDATE NOWAIT
2023-03-25T21:19:04Z:LOG_INFO:db7b6970a0:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:19:12Z:LOG_INFO:1bce0357e1:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:19:30Z:LOG_INFO:e9ec44ce17:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:19:37Z:LOG_INFO:61aeaf059f:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:19:45Z:LOG_INFO:f71753f7cb:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:19:52Z:LOG_INFO:5a6b90b34b:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:20:28Z:LOG_INFO:9ad2049123:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:20:29Z:LOG_INFO:d3862a8af7:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:20:32Z:LOG_ERR:7514c36cf7:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:20:33Z:LOG_INFO:3dc017b972:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:20:33Z:LOG_ERR:7b745cddf2:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:20:33Z:LOG_ERR:7b745cddf2:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:20:33Z:LOG_ERR:7b745cddf2:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id, workerq_cmd FROM workerq WHERE workerq_reservationid IS NULL ORDER BY workerq_priority DESC, workerq_id ASC LIMIT 1 FOR UPDATE NOWAIT
2023-03-25T21:20:38Z:LOG_INFO:3b2fc0bcd9:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:20:44Z:LOG_ERR:498d3b5f49:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:20:44Z:LOG_ERR:5bc4d2648a:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:20:44Z:LOG_ERR:5bc4d2648a:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:20:44Z:LOG_ERR:5bc4d2648a:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id, workerq_cmd FROM workerq WHERE workerq_reservationid IS NULL ORDER BY workerq_priority DESC, workerq_id ASC LIMIT 1 FOR UPDATE NOWAIT
2023-03-25T21:20:47Z:LOG_INFO:1f5fc4e1cb:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:21:08Z:LOG_INFO:749882e154:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:21:12Z:LOG_INFO:846901ad95:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:21:14Z:LOG_INFO:71c77ef596:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:21:34Z:LOG_INFO:eec9e0d102:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:21:54Z:LOG_INFO:60ba75d55e:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:21:58Z:LOG_ERR:a8cadabfc2:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:21:59Z:LOG_ERR:b5e50a6858:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:21:59Z:LOG_ERR:b5e50a6858:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:21:59Z:LOG_ERR:b5e50a6858:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id, workerq_cmd FROM workerq WHERE workerq_reservationid IS NULL ORDER BY workerq_priority DESC, workerq_id ASC LIMIT 1 FOR UPDATE NOWAIT
2023-03-25T21:22:03Z:LOG_INFO:2210d4b6a1:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:22:06Z:LOG_INFO:67cad2f582:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:22:11Z:LOG_INFO:84ef4435e7:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
2023-03-25T21:22:33Z:LOG_ERR:d4c870e2b0:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:22:33Z:LOG_ERR:16e94bbc99:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:22:33Z:LOG_ERR:16e94bbc99:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:22:33Z:LOG_ERR:16e94bbc99:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id, workerq_cmd FROM workerq WHERE workerq_reservationid IS NULL ORDER BY workerq_priority DESC, workerq_id ASC LIMIT 1 FOR UPDATE NOWAIT
2023-03-25T21:22:39Z:LOG_INFO:66a67d6666:QueueWorker.php:60:Summon: Summon: Ignoring duplicate workerq task
root@webserver2:/# grep -e "ERROR" /var/www/html/hzlogs
2023-03-25T21:14:05Z:LOG_ERR:ebd8f194e6:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:14:05Z:LOG_ERR:c6f9283736:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:14:05Z:LOG_ERR:c6f9283736:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:14:05Z:LOG_ERR:c6f9283736:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id, workerq_cmd FROM workerq WHERE workerq_reservationid IS NULL ORDER BY workerq_priority DESC, workerq_id ASC LIMIT 1 FOR UPDATE NOWAIT
2023-03-25T21:16:57Z:LOG_ERR:d455725c59:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:16:57Z:LOG_ERR:140a4f51a6:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:16:57Z:LOG_ERR:140a4f51a6:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:16:57Z:LOG_ERR:140a4f51a6:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id, workerq_cmd FROM workerq WHERE workerq_reservationid IS NULL ORDER BY workerq_priority DESC, workerq_id ASC LIMIT 1 FOR UPDATE NOWAIT
2023-03-25T21:18:06Z:LOG_ERR:e17361ac17:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:18:07Z:LOG_ERR:9eaa52345a:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:18:07Z:LOG_ERR:9eaa52345a:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:18:07Z:LOG_ERR:9eaa52345a:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id, workerq_cmd FROM workerq WHERE workerq_reservationid IS NULL ORDER BY workerq_priority DESC, workerq_id ASC LIMIT 1 FOR UPDATE NOWAIT
2023-03-25T21:18:36Z:LOG_ERR:70ceaf6df4:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:18:36Z:LOG_ERR:7809fbe50a:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:18:36Z:LOG_ERR:7809fbe50a:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:18:36Z:LOG_ERR:7809fbe50a:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id, workerq_cmd FROM workerq WHERE workerq_reservationid IS NULL ORDER BY workerq_priority DESC, workerq_id ASC LIMIT 1 FOR UPDATE NOWAIT
2023-03-25T21:20:32Z:LOG_ERR:7514c36cf7:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:20:33Z:LOG_ERR:7b745cddf2:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:20:33Z:LOG_ERR:7b745cddf2:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:20:33Z:LOG_ERR:7b745cddf2:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id, workerq_cmd FROM workerq WHERE workerq_reservationid IS NULL ORDER BY workerq_priority DESC, workerq_id ASC LIMIT 1 FOR UPDATE NOWAIT
2023-03-25T21:20:44Z:LOG_ERR:498d3b5f49:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:20:44Z:LOG_ERR:5bc4d2648a:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:20:44Z:LOG_ERR:5bc4d2648a:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:20:44Z:LOG_ERR:5bc4d2648a:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id, workerq_cmd FROM workerq WHERE workerq_reservationid IS NULL ORDER BY workerq_priority DESC, workerq_id ASC LIMIT 1 FOR UPDATE NOWAIT
2023-03-25T21:21:58Z:LOG_ERR:a8cadabfc2:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:21:59Z:LOG_ERR:b5e50a6858:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:21:59Z:LOG_ERR:b5e50a6858:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:21:59Z:LOG_ERR:b5e50a6858:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id, workerq_cmd FROM workerq WHERE workerq_reservationid IS NULL ORDER BY workerq_priority DESC, workerq_id ASC LIMIT 1 FOR UPDATE NOWAIT
2023-03-25T21:22:33Z:LOG_ERR:d4c870e2b0:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:22:33Z:LOG_ERR:16e94bbc99:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:22:33Z:LOG_ERR:16e94bbc99:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:22:33Z:LOG_ERR:16e94bbc99:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id, workerq_cmd FROM workerq WHERE workerq_reservationid IS NULL ORDER BY workerq_priority DESC, workerq_id ASC LIMIT 1 FOR UPDATE NOWAIT
2023-03-25T21:23:09Z:LOG_ERR:c0c226b2cb:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:23:09Z:LOG_ERR:e6e27a1d79:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:23:09Z:LOG_ERR:e6e27a1d79:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:23:09Z:LOG_ERR:e6e27a1d79:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id, workerq_cmd FROM workerq WHERE workerq_reservationid IS NULL ORDER BY workerq_priority DESC, workerq_id ASC LIMIT 1 FOR UPDATE NOWAIT
2023-03-25T21:23:24Z:LOG_ERR:a4a0327742:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:23:24Z:LOG_ERR:088031a6a3:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:23:25Z:LOG_ERR:088031a6a3:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id FROM workerq WHERE workerq_reservationid IS NOT NULL AND workerq_processtimeout < UTC_TIMESTAMP() FOR UPDATE NOWAIT
2023-03-25T21:23:25Z:LOG_ERR:088031a6a3:dba_driver.php:463:db_logger: dba_pdo: ERROR: SELECT workerq_id, workerq_cmd FROM workerq WHERE workerq_reservationid IS NULL ORDER BY workerq_priority DESC, workerq_id ASC LIMIT 1 FOR UPDATE NOWAIT

It looks like I might have been missing something after the upgrade. workerq has 2034 items at the moment. Any hint what went wrong and how I might fix it would be great. Thanks!

show all 6 Comments

Sat, 25 Mar 2023 23:12:01 +0100

0mega 🕱 [hz]

0mega@social.c-r-t.tk

My DB is too old for NOWAIT, gotta upgrade. But thanks anyway.

Sun, 26 Mar 2023 01:35:13 +0100

Grouchy

grouchy@hub.grouchysysadmin.com

What's your database type and version? Do you have any failed database updates under Admin -> DB updates?

Sun, 26 Mar 2023 10:22:28 +0200

Victoria

vsrjaccount@hub.netzgemeinde.eu

There seem to be a lot of queueing issues on different instances since 8.2 was rolled out. I wonder if this is happening elsewhere, too.

Sun, 26 Mar 2023 16:58:56 +0200

Mario Vavti

mario@hub.somaton.com

@0mega 🕱 [hz] which DB and version?

Mon, 27 Mar 2023 05:18:33 +0200

0mega 🕱 [hz]

0mega@social.c-r-t.tk

@Mario Vavti It was MariaDB 10.2, I've upgraded it to a more recent version which implements "NOWAIT" and now everything's working fine again

Mon, 27 Mar 2023 14:19:13 +0200

0mega 🕱 [hz]

0mega@social.c-r-t.tk

I'm adding some replies for the sake of completeness and because I don't want to be rude to everyone who tried to help ☺️

@Grouchy

What's your database type and version?

It was Mariadb 10.2.x I've upgraded to 10.3.x so you've already had the right feeling here.

@Grouchy

Do you have any failed database updates under Admin -> DB updates?

Nope. That was the first thing I've checked.

@Victoria

There seem to be a lot of queueing issues on different instances since 8.2 was rolled out. I wonder if this is happening elsewhere, too.

Aye, it might happen to anyone with really old SQL servers. Even though I've appreciated a hint in the changelog ("requires mysql >= x.y, mariadb >= 10.3.0"), those old versions will probably only be found in outdated distros like Debian Stretch *cough-cough*

GitLab issue for non-delivery of mentions by non-contacts

Sat, 25 Mar 2023 04:35:18 +0100

Hubzilla Support Forum

support@zotadel.net

Victoria wrote the following post Sat, 25 Mar 2023 04:35:17 +0100

GitLab issue for non-delivery of mentions by non-contacts

Currently in #Hubzilla there is no way for you to receive mentions from channels that are not already among your contacts, unless the mention is a direct reply to one of your posts. The sender believes they have contacted you, but you never receive the message.

If you would like to be able to opt-in to receiving these mentions, please consider giving a thumbs up to this GitLab issue: https://framagit.org/hubzilla/core/-/issues/1732

Thank you

Configuration of "HQ"

Fri, 24 Mar 2023 10:17:03 +0100

Hubzilla Support Forum

support@zotadel.net

Kristian wrote the following post Fri, 24 Mar 2023 10:17:03 +0100

Configuration of "HQ"

Relating usability: When I head for zotum.net on my mobile browser, I always end up in /hq and see my "photos" and nothing else. Is there a way to reconfigure or re-arrange the items displayed in the /hq page? Any recommendations for that?
Thanks and best regards,
Kristian

Fri, 24 Mar 2023 12:27:52 +0100

Victoria

vsrjaccount@hub.netzgemeinde.eu

Can you see a little sideways arrow at the top? That will make the interface wider and show you the message panel that is usually on the left hand side of HQ. On my mobile web screen I can also see an exclamation mark, which toggles notifications, and a burger menu that shows my apps and the dark/light interface toggle. Sometimes I have to swipe to get back to where I want to be, when it's in wide mode. Also, at the top left I can see my userpic and the dropdown that is the same as the regular PC web interface.

Do any of those things show up for you?

Fri, 24 Mar 2023 14:14:52 +0100

Kristian

z428@zotum.net

@Victoria Thanks... Yes, they're around. It's not really a big "problem" - just a bit confusing as this "photos" view has little to no use for me, and I'd rather have, say, "stream" or "public timeline" of my instance as a default view.... 🙂

Server issues zotum.net <-> hub.netzgemeinde.eu

Fri, 24 Mar 2023 07:07:47 +0100

Hubzilla Support Forum

support@zotadel.net

Kristian wrote the following post Fri, 24 Mar 2023 07:07:46 +0100

Server issues zotum.net <-> hub.netzgemeinde.eu

Alls; I'm having a channel on zotum.net (@z428@zotum.net) and a clone of it on hub.netzgemeinde.eu. As I wanted to try this nomadic identity yesterday, it seems completely broken at the moment. Here we are:

- Looking at the channel from both hosts shows different posts. Apparently, they aren't synchronized at the moment.

- Looking at the channel from an activitypub account (like my main Friendica account which uses to follow "me" there), I only see the state seen in zotum.net, not posts made from the other account.

- From zotum.net, I tried posting to this forum yesterday, but apparently this post (again) is invisible for anyone except me; when I'm looking at the forum from my zotum.net account, I can see it, but using another account or a public view, I can't.

- Likewise, for none of these messages posted yesterday, the "delivery report" shows _any_ kind of delivery has happened.

This is utterly weird, and it's also concerning because I left some comments on some messages I've seen here and have absolutely no idea whether they made it out or not. Can anyone help here...?
Merci,
Kristian

show all 7 Comments

Fri, 24 Mar 2023 07:10:23 +0100

Kristian

z428@zotum.net

(Hmmm. Strange. For whichever reasons, at least one of the posts made from hub.netzgemeinde.eu to the channel has become visible elsewhere now. No idea what happened in between...)

Fri, 24 Mar 2023 08:08:39 +0100

Victoria

vsrjaccount@hub.netzgemeinde.eu

Connectivity between Zotum.net, Netzgemeinde and ActivityPub has been offline since yesterday morning. I posted a message to the Zotum admin account but I don't know if they have received that message (I don't know if this comment will arrive with you, either, or when that may happen). I will try to reach them again now.

If you want posts to synchronise correctly with ActivityPub later, send them from the Zotum account rather than the Netzgemeinde clone. They may not arrive until the issue is fixed, but they will arrive on the correct identity in ActivityPub. If you send them from the clone, they will appear in ActivityPub as from the Netzgemeinde clone and your contacts may not see them.

Fri, 24 Mar 2023 08:17:46 +0100

Kristian

z428@zotum.net

@Victoria Ok, thanks very much, that explains it ... (apparently at least these messages have been successfully delivered). Just out of curiosity: Is there a "good" channel for this kind of communication that does work, too, if zotum or any of the other involved systems is having a bad day? Matrix? ...? Trying to reach an admin to report an issue with a system but only having a contact on that particular system feels ... rather helpless...😁

Fri, 24 Mar 2023 08:25:24 +0100

Victoria

vsrjaccount@hub.netzgemeinde.eu

I will let you know when I find out. I'd thought this was it, but my messages are not always displayed (I've noticed some comments I wrote here during the previous Zotum outage never appeared here). I've just tried to connect with the people I think may be able to help and/or are watching this issue using my clone account, but I'm not sure if it will work or if it will just try to route things through Zotum again. The most reliable method right now may be to be connected to the admin via a completely separate (non cloned) account on a different instance, or another platform.

Since Zotum is a development hub, I can understand the need for it to go offline unexpectedly sometimes, and for it to have long outages. It would be very useful if there was a completely separate page or noticeboard for when that happens, so we know the admin knows about it, and also so there is somewhere unaffected by outages where we can report them.

Fri, 24 Mar 2023 08:49:20 +0100

Kristian

z428@zotum.net

@Victoria Thanks. Yes, of course, this being a development hub makes it easy to understand. My problem, apparently, is that I wasn't aware of this fact before...😬

Fri, 24 Mar 2023 09:17:56 +0100

Victoria

vsrjaccount@hub.netzgemeinde.eu

It's easy to miss. I think on the registration page it says it's an "experimental hub", and then somewhere else it mentions that it might go offline unexpectedly as well (although I can't remember right now there that's written). Usually it's a bit more stable, though. I think Fediverse Observer has the uptime as around 86%, and I'd been using it very smoothly up until Sunday night. Usually it's been really fast. This week has just been unfortunate.

Fri, 24 Mar 2023 09:38:48 +0100

Kristian

z428@zotum.net

@Victoria Yeah, I think I noticed at least that "experimental" part of it, but then again, it feels most of the distributed federated web is sort of "experimental" so that wasn't enough to scare me away I guess, and most of the time I checked it it indeed has been quite reliable. So maybe just bad luck at a bad time...🙂

Unwanted and unseen comments from non-contacts

Thu, 23 Mar 2023 14:32:19 +0100

Hubzilla Support Forum

support@zotadel.net

Maria Karlsen wrote the following post Thu, 23 Mar 2023 14:32:18 +0100

Unwanted and unseen comments from non-contacts

Using the default privacy setting for my personal channel this happened:
One of my public posts was commented on by someone who is not my contact. Is that how it is supposed to work?
Also the comment didn't show up in my stream, so I wasn't aware of it until I watched my public stream where it was visible.
That is a problem in my opinion.
(There was also a mention, but that might be related to Victoria's issue)

Thu, 23 Mar 2023 15:58:48 +0100

Maria Karlsen

shimriez@zotum.net

It seems I am not allowed to edit my own post so here is some extra information:
I had automatic acception of connection turned on. Then I found someone adding me that I don't want to have any contact with, so I turned the option off and removed that person from my contacts. Maybe that's what caused a hiccup.

Fri, 24 Mar 2023 08:28:08 +0100

Victoria

vsrjaccount@hub.netzgemeinde.eu

I don't think there is any way a non-contact can sent a message that reaches you right now (that's the issue I wrote about before), and Mario has confirmed the functionality is not currently in place, so I'd be really surprised if that's what happened. If that is what happened. It does sound like the connection was accepted automatically. Hope it is resolved for you now.

Fri, 24 Mar 2023 13:43:54 +0100

Maria Karlsen

shimriez@zotum.net

Yes, I believe it was the automatic acceptance plus me changing permissions while Zotum was having delivery problems, possibly.

Mentions from non-contacts, but not the rest of their posts

Tue, 21 Mar 2023 19:04:57 +0100

Hubzilla Support Forum

support@zotadel.net

Victoria wrote the following post Tue, 21 Mar 2023 19:04:57 +0100

Mentions from non-contacts, but not the rest of their posts

Is there any option I can set it to so that I do receive posts/notifications from authenticated users (anywhere) who mention me, but not posts/notifications for all posts known to the hub including those that don't mention me?

Right now it seems I have to choose between only seeing mentions from contacts or seeing (and getting notifications for) posts from anyone known to the hub instance I'm using. I've tried out some different combinations using the "Can send me their channel stream and posts" dropdown and other settings under channel privacy, and can't seem to find a combination that does what I need.

(Sorry to be posting so many queries -- as a new user there seems to be a lot to figure out.)

Wed, 22 Mar 2023 05:49:21 +0100

Victoria

vsrjaccount@hub.netzgemeinde.eu

I'd thought this was to do with my privacy and role settings, but I just tested with a completely fresh channel (to make sure I hadn't messed anything up) and with all the options set to the loosest possible setting. A test post tagging the test account wasn't displayed at all - not as a notification, and not in the stream.

I know posts by that Mastodon account are received by the Hubzilla instance because another channel on this instance is following it. Its posts, including the ones tagging the test account, all show up in my other channel.

This is a major problem.

Wed, 22 Mar 2023 14:24:42 +0100

Victoria

vsrjaccount@hub.netzgemeinde.eu

After checking with Mario I have added the following issue to framagit/GitLab in relation to this: Mentions by unknown users are not received (#1732)

Tue, 21 Mar 2023 15:57:41 +0100

Hubzilla Support Forum

support@zotadel.net

Anthony wrote the following post Tue, 21 Mar 2023 15:57:41 +0100

Hello everyone,

I am one of the users who use Hubzilla because this tool allows (among other things) to communicate on several networks (Mastodon, Diaspora...).
There is a little thing that bothers me and that concerns only the communication with Diaspora and Mastodon.
When I comment my own post to answer a Mastodon user, the person on Diaspora sees my message and doesn't understand who I'm talking to (since he doesn't see the Mastodon user's message). Same for the opposite.
Would it be possible (and not too complicated) to make sure that only the diaspora network receives a message sent in response to a diaspora comment? And the same for the ActivityPub protocol for example ? In short, to limit the sending of a comment to the network of the person to whom you are replying?
There might be a reason why this is not possible but I think I'm not the only one in this situation.
Thanks for your attention and have a nice day.

Identity portability and ActivityPub

Tue, 21 Mar 2023 05:36:50 +0100

Hubzilla Support Forum

support@zotadel.net

Victoria wrote the following post Tue, 21 Mar 2023 05:36:49 +0100

Identity portability and ActivityPub

The Zotum queueing issue Sunday night gave me the opportunity to try out Hubzilla's instance portability and using the clone of my channel (on Netzgemeinde) during an outage for the first time.

Within Hubzilla

Hubzilla itself handled everything really well. Because I'd already set up the clone, I could just log into the clone and post from there using my primary identity. The posts appeared quickly on both my channel page and on the public stream on my primary instance despite the issues that primary instance was also having with other functionality. Everything appeared as though it had been posted from the single primary identity. This is exactly as I'd expected.

With ActivityPub

With ActivityPub things worked a little differently to how I'd expected, and I'd like to note that here to check whether I've understood correctly how it should be working, and whether it is working as intended.

What I'd expected

I had expected posts sent via the clone during the outage to eventually appear on ActivityPub as having been sent from my primary identity (the same way things had worked within Hubzilla). I had always understood this wouldn't happen until the primary instance was restored, because ActivityPub depends on connecting to the primary instance to collect posts sent from my primary identity.

Also, I had expected any ActivityPub user tagged in posts sent from my primary identity via the clone to eventually see those posts and receive notifications as normal, so my use of a clone on Hubzilla was invisible to them and the only impact to them of the outage was the delay in receiving my posts.

What happened

Posts I sent via my primary instance during the outage appeared on ActivityPub later, after the instance recovered, and any users tagged did receive notifications. This was as expected.

Posts I sent via the clone during the outage never appeared on ActivityPub as sent from my primary identity. Instead, it seems they were seen by ActivityPub as having been sent from the cloned identity.

In practice, this meant that the posts were invisible, because my ActivityPub contacts are only following ("connected to", in Hubzilla terms) my primary identity, not the clone.

The only post sent via the clone during the outage that is visible to me now in ActivityPub is one that tagged a Mastodon account. No notification was ever received by that account because the account is not following the cloned identity. The post, with the tag, is visible on the ActivityPub profile page of the cloned identity, but you have to go and look for it to know that it's there. Posts that did not tag anyone are not visible.

Implications

If identity portability works with ActivityPub to keep identity consistent (so posts always appear to have come from the primary identity), the way I had expected, the cost is a delay to post delivery during outages of the primary instance. During outages, ActivityPub contacts will be unreachable. Only if an instance never recovers will those messages never arrive. Providing it recovers, interactions with ActivityPub will be seamless aside from the delay.

If identity portability works with ActivityPub the way it currently seems to be set up, the cost is that from the perspective of ActivityPub users, there is no identity portability. Posts sent from primary identities via cloned instances by Hubzilla users, believing ActivityPub will behave the same way as Hubzilla, may never be seen by ActivityPub contacts even if they are tagged. There will be no notifications for these posts. Posts that tag no one will not appear even on the profile pages for the primary identity within ActivityPub.

For posts sent from primary identities via cloned instances to be visible to ActivityPub contacts, all of those contacts must follow both the primary identity and the identity on the cloned instance - two different addresses. If they have to do this, they are essentially operating with two separate identities. If they interact with posts sent via the clone, their interactions will not be sent to the primary identity but to the clone (I'm not sure what will happen to these interactions when they are received within Hubzilla).

Questions

1. Have I understood the current behaviour correctly?

2. Is the current behaviour working as it should?

Tue, 21 Mar 2023 05:41:57 +0100

Victoria

vsrjaccount@hub.netzgemeinde.eu

I just tried to edit this to move this line to the top: "With ActivityPub things worked a little differently to how I'd expected, and I'd like to note that here to check whether I've understood correctly how it should be working, and whether it is working as intended".... which is the point.

The forum won't let me edit or even delete the post. When I try there is an error message saying "permission denied".

Tue, 21 Mar 2023 16:12:26 +0100

Nolan

nolan@ein-hub-von-vielen.de

See also issue https://framagit.org/hubzilla/core/-/issues/1722 about clone-sent publications.

Tue, 21 Mar 2023 16:45:19 +0100

Victoria

vsrjaccount@hub.netzgemeinde.eu

@Nolan Ooh that's interesting, thank you.

I asked Mike about how this is supposed to work earlier, as well as posting here. He seemed to think both the primary instance and the clone should, in the end, send updates on ActivityPub about posts sent from the primary identity via a cloned instance.

If that had happened on Monday when Zotum recovered, a lot of things would've worked much more as I'd expected and there wouldn't have been the issue of missing posts. Users connected to only the primary identity would have just experienced a delay, and no confusion over receiving messages or notifications from multiple identities.

So perhaps it would be good to probe why Zotum never sent that ActivityPub notification (or, if it did, why it was never acted upon by Mastodon). Messages just vanishing when people think they've been sent seems like quite a problem.

Problem writing with webdav

Mon, 20 Mar 2023 18:00:13 +0100

Hubzilla Support Forum

support@zotadel.net

Alexandre Hannud Abdo wrote the following post Mon, 20 Mar 2023 18:00:03 +0100

Problem writing with webdav

For a while now I've been getting this when trying to paste a file with webdav (Gnome Nautilus).

The apache user has write access to /store and all its subdirectories. PHP is 8.2.4. Hubzilla is currently 8.2.

In the Hubzilla logs:

2023-03-20T16:35:06Z:LOG_INFO:4db2b77893:Directory.php:508:getDir: GetDir: /
2023-03-20T16:35:06Z:LOG_INFO:4db2b77893:Directory.php:508:getDir: GetDir: /cloud
2023-03-20T16:35:06Z:LOG_INFO:4db2b77893:Directory.php:508:getDir: GetDir: aleabdo
2023-03-20T16:35:06Z:LOG_INFO:4db2b77893:Directory.php:508:getDir: GetDir: /
2023-03-20T16:35:06Z:LOG_INFO:4db2b77893:Directory.php:508:getDir: GetDir: /cloud
2023-03-20T16:35:06Z:LOG_INFO:4db2b77893:Directory.php:508:getDir: GetDir: aleabdo
2023-03-20T16:35:06Z:LOG_INFO:4db2b77893:Directory.php:508:getDir: GetDir: /
2023-03-20T16:35:06Z:LOG_INFO:4db2b77893:Directory.php:508:getDir: GetDir: /cloud
2023-03-20T16:35:06Z:LOG_INFO:4db2b77893:Directory.php:508:getDir: GetDir: aleabdo
2023-03-20T16:35:06Z:LOG_INFO:4db2b77893:Directory.php:508:getDir: GetDir: /
2023-03-20T16:35:06Z:LOG_INFO:4db2b77893:Directory.php:508:getDir: GetDir: /cloud
2023-03-20T16:35:06Z:LOG_INFO:4db2b77893:Directory.php:508:getDir: GetDir: aleabdo
2023-03-20T16:35:06Z:LOG_INFO:4db2b77893:Directory.php:882:FileData: not found aleabdo/photo1674659640.jpeg
2023-03-20T16:35:07Z:LOG_INFO:4db2b77893:Directory.php:508:getDir: GetDir: /
2023-03-20T16:35:07Z:LOG_INFO:4db2b77893:Directory.php:508:getDir: GetDir: /cloud
2023-03-20T16:35:07Z:LOG_INFO:4db2b77893:Directory.php:508:getDir: GetDir: aleabdo
2023-03-20T16:35:07Z:LOG_INFO:4db2b77893:Directory.php:882:FileData: not found aleabdo/photo1674659640.jpeg
2023-03-20T16:35:07Z:LOG_INFO:4db2b77893:Directory.php:209:createFile: create file in directory photo1674659640.jpeg
2023-03-20T16:35:07Z:LOG_INFO:4db2b77893:Directory.php:217:createFile: permission denied photo1674659640.jpeg
2023-03-20T16:35:07Z:LOG_INFO:4db2b77893:Directory.php:508:getDir: GetDir: /
2023-03-20T16:35:07Z:LOG_INFO:4db2b77893:Directory.php:508:getDir: GetDir: /cloud
2023-03-20T16:35:07Z:LOG_INFO:4db2b77893:Directory.php:508:getDir: GetDir: aleabdo
2023-03-20T16:35:07Z:LOG_INFO:4db2b77893:Directory.php:882:FileData: not found aleabdo/photo1674659640.jpeg

In Nautilus:

Could not parse response

I'd be glad if anyone has any clues?

show all 5 Comments

Mon, 20 Mar 2023 18:25:08 +0100

Grouchy

grouchy@hub.grouchysysadmin.com

I just tested it with Hubzilla 8.2 and PHP 8.1 and it worked. I was able to paste or drag and drop several different file types into the Nautilus and Hubzilla davs mount.

I wonder what is causing this error:
2023-03-20T16:35:07Z:LOG_INFO:4db2b77893:Directory.php:217:createFile: permission denied photo1674659640.jpeg

Can you create files on the command line running as the same user that is executing Hubzilla's PHP scripts?

Tue, 21 Mar 2023 00:21:30 +0100

Alexandre Hannud Abdo

aleabdo@hubzilla.com.br

Cheers @Grouchy,

PHP is run by apache (mod php) under a user (www-data) who owns with 'rwX' access all of the tree under 'store/'.

Also, enabling PHP logs in '.htconfig' didn't show anything of interest.

I get the same error in Nautilus when trying to create a directory, though with no "permission denied" line.

I would seem to get no error in Nautilus when trying to delete a file or a directory, and no "permission denied" line in the logs, but when I reload the parent the directory the deleted item is still present.

Tue, 21 Mar 2023 23:02:48 +0100 last edited: Tue, 21 Mar 2023 23:03:50 +0100

Grouchy

grouchy@hub.grouchysysadmin.com

@Alexandre Hannud Abdo

The error indicates file permission issues. But since www-data can read/write to it all, I'm not sure what the issue is.

I'll try and test PHP 8.2 later this week and see if that makes a difference.