Long-running commands dies early and unexpectedly

[NiklasBr]

For example presta:sitemaps:dump keeps dying even though we have configured a long timeout:

www-data@610465edab50:~/pimcore$ bin/console debug:config ElementsProcessManagerBundle

Current configuration for "ElementsProcessManagerBundle"
========================================================

elements_process_manager:
    processTimeoutMinutes: 120
    archiveThresholdLogs: 7
    disableShortcutMenu: false
    reportingEmailAddresses: {  }
    additionalScriptExecutionUsers: {  }
    restApiUsers: {  }

Running this command directly on the server as the web user works:

www-data@610465edab50:~/pimcore$ bin/console presta:sitemaps:dump --section site_5 --base-url https://example.com/ public/var/tmp/sitemaps
Dumping sitemaps section site_5 into public/var/tmp/sitemaps directory
Created/Updated the following sitemap files:
    sitemap.site_5.xml
    sitemap.xml

What are we doing incorrectly here?

[ArianJuwig]

Same problem with the ecommerce:indexservice:bootstrap command and other long running commands (Havent tested our Presta sitemap process yet). Sorry for replying to such an old issue but I cant seem to find any solution for it.
Can you remember if you found one?

[NiklasBr]

Unfortunately no, we did not find a solution and instead moved those processes out into raw cron commands. For example:

10 5 * * 1-5 www-data /bin/bash -c '/usr/bin/flock --timeout 0 $PIMCORE_ROOT/var/tmp/pimcore_sitemaps.lock /usr/local/bin/php $PIMCORE_ROOT/bin/console presta:sitemaps:dump --section site_5 --base-url https://example.com/ public/var/tmp/sitemaps/5'