[Touch-packages] [Bug 1582692] Re: OOM using CRON but not using SHELL under 16.04
[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.
https://bugs.launchpad.net/bugs/1582692
Title:
OOM using CRON but not using SHELL under 16.04
Status in cron package in Ubuntu:
Expired
Bug description:
When I start a java program with high memory usage ("-Xmx52g") by
shell, everything is working well. However if I start the same program
with the same command and same user by CRON, I get a
java.lang.OutOfMemoryError just after a few seconds.
Additionally CRON isn't able to do anything as long as I don't kill
the blocked java program. No matter which cronjob should be started,
it always ends up with "(CRON) error (can't fork)" in syslog. After
killing the java program all new cronjobs are working fine again.
The problem only occurs with Ubuntu 16.04, all older versions worked
very well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1582692/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582692] Re: OOM using CRON but not using SHELL under 16.04
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 as soon as you are aware of, it's no problem to
change it.
--
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:
Incomplete
Bug description:
When I start a java program with high memory usage ("-Xmx52g") by
shell, everything is working well. However if I start the same program
with the same command and same user by CRON, I get a
java.lang.OutOfMemoryError just after a few seconds.
Additionally CRON isn't able to do anything as long as I don't kill
the blocked java program. No matter which cronjob should be started,
it always ends up with "(CRON) error (can't fork)" in syslog. After
killing the java program all new cronjobs are working fine again.
The problem only occurs with Ubuntu 16.04, all older versions worked
very well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1582692/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582692] Re: OOM using CRON but not using SHELL under 16.04
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 started by crontab.
The java program creates many threads (1500 at startup, more afterwards)
and it always begins to hang just after 475 threads have been created.
So maybe it's more something like "OutOfThreads" even OutOfMemory is
logged.
The crontab of my local user only starts a simple perl script:
*/2 ** * */home/dob/getjob/getjob.pl > /dev/null 2>&1
The script (getjob.pl) itself creates some config files and finally starts the
java program by calling a shell script like this:
system('JAVA_OPTS="-Xmx6g -Xms6g" /home/dob/prog/bin/start');
Starting "/home/dob/getjob/getjob.pl" on SHELL with user 'dob'
everything is fine. Placing the line above in dob's crontab ("crontab
-e") the java program fails with 'Exception in thread "StartNextJob"
java.lang.OutOfMemoryError: unable to create new native thread' after
creating 475 threads.
I tried to start getjob.pl by root's crontab, but with same results. For
testing purpose I reduced the number of initial threads to 450 and with
this setting everything works fine for some minutes (until more threads
should be created). However I really need those 1500+ threads and I have
no clue why this isn't possible when the java program has been started
by crontab.
--
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:
Incomplete
Bug description:
When I start a java program with high memory usage ("-Xmx52g") by
shell, everything is working well. However if I start the same program
with the same command and same user by CRON, I get a
java.lang.OutOfMemoryError just after a few seconds.
Additionally CRON isn't able to do anything as long as I don't kill
the blocked java program. No matter which cronjob should be started,
it always ends up with "(CRON) error (can't fork)" in syslog. After
killing the java program all new cronjobs are working fine again.
The problem only occurs with Ubuntu 16.04, all older versions worked
very well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1582692/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582692] Re: OOM using CRON but not using SHELL under 16.04
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 RAM your system has (so I can try to simulate the % of used and
available RAM)
* Your crontab and under which user it is being run
* (If at all possible) a sample of the program you are trying to run (or the
program + settings)
This will help us to find and resolve the problem, as I have been so far
unable to reproduce it.
** Changed in: cron (Ubuntu)
Status: New => Incomplete
--
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:
Incomplete
Bug description:
When I start a java program with high memory usage ("-Xmx52g") by
shell, everything is working well. However if I start the same program
with the same command and same user by CRON, I get a
java.lang.OutOfMemoryError just after a few seconds.
Additionally CRON isn't able to do anything as long as I don't kill
the blocked java program. No matter which cronjob should be started,
it always ends up with "(CRON) error (can't fork)" in syslog. After
killing the java program all new cronjobs are working fine again.
The problem only occurs with Ubuntu 16.04, all older versions worked
very well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1582692/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582692] Re: OOM using CRON but not using SHELL under 16.04
** 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
Bug description:
When I start a java program with high memory usage ("-Xmx52g") by
shell, everything is working well. However if I start the same program
with the same command and same user by CRON, I get a
java.lang.OutOfMemoryError just after a few seconds.
Additionally CRON isn't able to do anything as long as I don't kill
the blocked java program. No matter which cronjob should be started,
it always ends up with "(CRON) error (can't fork)" in syslog. After
killing the java program all new cronjobs are working fine again.
The problem only occurs with Ubuntu 16.04, all older versions worked
very well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1582692/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582692] Re: OOM using CRON but not using SHELL under 16.04
** 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 package in Ubuntu:
New
Bug description:
When I start a java program with high memory usage ("-Xmx52g") by
shell, everything is working well. However if I start the same program
with the same command and same user by CRON, I get a
java.lang.OutOfMemoryError just after a few seconds.
Additionally CRON isn't able to do anything as long as I don't kill
the blocked java program. No matter which cronjob should be started,
it always ends up with "(CRON) error (can't fork)" in syslog. After
killing the java program all new cronjobs are working fine again.
The problem only occurs with Ubuntu 16.04, all older versions worked
very well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1582692/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
