Hi,
We had a problem with a Java application that run out of memory:
Caused by: java.lang.OutOfMemoryError: Java heap space
at java.io.UnixFileSystem.list(Native Method)
...
It happened because of 2 million files in /var/tmp:
sapserverx:/var/tmp# ls -l|wc -l
1899062
Almost all "ExAAA??????", 0 bytes.
These files are created by:
sapserverx:/var/tmp# ps -ef|grep 12143
root 12143 3159 0 Dec 17 ? 46:58 /bin/sh - /usr/local/bin/bashbug
root 20890 12143 5 10:43:48 ? 0:00 vi /tmp/bbug.12143/bbug1
The bug files are these:
sapserverx:/tmp/bbug.12143# ls -l
total 32
-rw------- 1 root sys 973 Dec 17 17:07 bbug1
-rw------- 1 root sys 973 Dec 17 17:07 bbug2
sapserverx:/tmp/bbug.12143# diff bbug*
sapserverx:/tmp/bbug.12143# cat bbug1
From: root
To: bug-bash@gnu.org
Subject: [50 character or so descriptive subject here (for reference)]
Configuration Information [Automatically generated, do not change]:
Machine: ia64
OS: hpux11.23
Compiler: cc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='ia64'
-DCONF_OSTYPE='hpux11.23' -DCONF_MACHTYPE='ia64-hp-hpux11.23'
-DCONF_VENDOR='hp' -DLOCALEDIR='/usr/local/share/locale' -DPACKAGE='bash'
-DSHELL -DHAVE_CONFIG_H -DHPUX -I. -I. -I./include -I./lib -O
-I/usr/local/include -D_XOPEN_SOURCE_EXTENDED
uname output: HP-UX sapserverx B.11.31 U ia64 1664014788 unlimited-user license
Machine Type: ia64-hp-hpux11.23
Bash Version: 4.0
Patch Level: 33
Release Status: release
Description:
[Detailed description of the problem, suggestion, or complaint.]
Repeat-By:
[Describe the sequence of events that causes the problem
to occur.]
Fix:
[Description of how to fix the problem. If you don't know a
fix for the problem, don't include this section.]
-----------
I never experience this before, in fact I don't remember getting the "bashbug"
run.
It seems it happened when my colleague did logoff:
sapserverx:/tmp/bbug.12143# last
...
adminxxx pts/0 Mon Dec 17 10:55 - 17:07 (06:11)
I don't know how he exit, what signal...
It is because of "trap '' 2" in the script "bashbug", isn't it?
Now that we've detected the problem we just kill the process and rm all trash,
and everything is back to normal.
I send this mail to consider if it's too aggresive that trap. However it's the
first time I saw this problem...
Regards
Aitor
