Bug #8116
JSVC fails to start after kernel upgrade in response to CVE-2017-1000364
100%
Description
after kernel upgrade jsvc fails with only Service killed by signal 11 being reported in /var/log/dataone/index/d1-index-task-generator-jsvc.err
jsvc is used to run d1-processing, d1-index-task-generator and d1-index-task-processor
In summary:
* jsvc fails on kernel 3.13.0-121-generic
* svc runs ok on kernel 3.13.0-119-generic
Temporary solution by using older kernel:
/etc/default/grub
#GRUB_DEFAULT=0
GRUB_DEFAULT="Advanced options for Ubuntu>Ubuntu, with Linux 3.13.0-119-generic"
sudo update-grub
sudo reboot
History
#1 Updated by Dave Vieglais almost 7 years ago
- Assignee set to Dave Vieglais
#2 Updated by Dave Vieglais almost 7 years ago
Possible solution:
JSVC_EXTRA_OPTS -Xss1280k
#3 Updated by Dave Vieglais almost 7 years ago
- Description updated (diff)
#4 Updated by Dave Vieglais almost 7 years ago
@Xss@ is the thread stack size. If it is too low, then StackOverflowError will happen since the stack required is greater than the limit. If it is set too high however, then an OutOfMemoryError will result, since there is insufficient memory available for the number of threads being started.
The default value of @Xss@ is:
$ java -XX:+PrintFlagsFinal -version | grep ThreadStackSize
intx CompilerThreadStackSize = 0 {pd product}
intx ThreadStackSize = 1024 {pd product}
intx VMThreadStackSize = 1024 {pd product}
openjdk version "1.8.0_111"
OpenJDK Runtime Environment (build 1.8.0_111-8u111-b14-3~14.04.1-b14)
OpenJDK 64-Bit Server VM (build 25.111-b14, mixed mode)
#5 Updated by Dave Vieglais almost 7 years ago
- % Done changed from 0 to 30
- Status changed from New to In Progress
#6 Updated by Dave Vieglais almost 7 years ago
Setting @-Xss1280k@ verified to work on cn-dev-unm-1
#7 Updated by Dave Vieglais almost 7 years ago
- Status changed from In Progress to Closed
- % Done changed from 30 to 100
