Is there a way to restart or remove loaded but not executed tasks?

Rene

I've got a couple of task remaining in the loaded stage, is there a way to restart or remove them from the queue?

	
ldapSync	Loaded		Aug 8, 2025 10:58 AM	Aug 8, 2025 10:58 AM
ldapSync	Loaded		Aug 8, 2025 10:42 AM	Aug 8, 2025 10:42 AM
ldapSync	Loaded		Aug 8, 2025 10:41 AM	Aug 8, 2025 10:41 AM
ldapSync	Completed	0/0 synced (0.0s)	Aug 8, 2025 10:41 AM	Aug 8, 2025 10:41 AM
ldapSync	Completed	3/3 synced (0.1s)	Aug 6, 2025 12:19 PM	Aug 6, 2025 12:19 PM
ldapSync	Completed	3/3 synced (0.1s)	Aug 6, 2025 12:18 PM	Aug 6, 2025 12:18 PM

I've tried opening them, en clicking the 'restart / refresh' icon but that doesn't help

Steakie

How did you manage to get the Loaded state so i can try and fix this? xD

Steakie

Alright i figured it out. There will be new cancel and delete buttons in the task details view soon (or in a few hours idk lol).

Rene

You're faster than my replies to you ..

these happen when I try to sync ldap, and they usually are accompanied by an error in the admin api log

[2025-08-10 11:26:28.336395]: Sun Aug 10 11:26:28 2025 - uwsgi_response_writev_headers_and_body_do(): Broken pipe [core/writer.c line 306] during GET /api/v1/system/mconf/ldap (10.1.31.54)

[2025-08-10 11:26:28.341091]: OSError: write error

Steakie

Rene Yea i have never seen that before. This doesn't even seem like an API bug but something on your system... but anyway, you should be able cancel/delete tasks now

Rene

Steakie
Something on the Grommunio Appliance ? or my workstation (as in the webclient)? If its the latter, then i'll try a different browser.

Steakie

Rene I cannot tell you what exactly the problem is, only that it's most likely your workstation. Since this is some sort error withing writer.c (wherever that's from) it is definitely not an issue of the browser

Rene

Strange since grommunio is running in the official appliance, which is as provided with only 1 additional tool installed (growpart, to 'grow' the disk partition).

Is that writer routine doing a write to the appliance, or to the webclient in that routine line 306? Since when it happens, the current action in the webclient seems to wait for an answer from the host ( the wait spinner is running in the client web interface). The frontend itself is still responsive, its just the action that has started remains in wait state.