[Expired for cron (Ubuntu) because there has been no activity for 60
days.]
** Changed in: cron (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
Problem is solved! It was related to systemd which starts cronjobs and
limits max threads/processes to 512 by default. I'm not sure if this is
a good setting since one single user/cronjob is able to prevent any
other cronjobs from being executed ("(CRON) error (can't fork)")-
system-wide. However
The server has 64gb RAM and the problem even occurs even with much
smaller -Xmx (tested with 6g). The java program logs this issue:
'Exception in thread "StartNextJob" java.lang.OutOfMemoryError: unable
to create new native thread' - but as I've mentioned, this only happens
if the program is
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:
* Can you reproduce it with other java programs?
* Can you reproduce it with a smaller -Xmx?
* What specific steps should we take to recreate this bug?
Please provide:
* How much
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1582692
Title:
OOM using CRON but not using SHELL under 16.04
Status in cron package in Ubuntu:
New
** Package changed: ubuntu => cron (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1582692
Title:
OOM using CRON but not using SHELL under 16.04
Status in cron
6 matches
Mail list logo
