OpenVZ Forum: Support » *SOLVED* blank lsof output

Home » General » Support » *SOLVED* blank lsof output

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

*SOLVED* blank lsof output [message #10020]

Mon, 05 February 2007 15:40

skizzo
Messages: 10
Registered: December 2006

Junior Member

Hello,
I am FC5 OpenVZ VE user. Last night the system came to a halt and I was locked out (too many open files, cannot allocate memory...). I had the system reset, and I am now trying to figure out what happened. I believe that the problem was caused by httpd trying to feed log messages into syslog-ng via named pipes. Do you see anything odd with the included beancounters? I also tried to run lsof and was surprised seeing a blank output. I don't know how to interpret that, as I am not familiar with OpenVZ internals. Could you please shed some light? thank you.

skizzo

# cat /proc/user_beancounters
Version: 2.5
uid resource held maxheld barrier limit failcnt
1011: kmemsize 6540905 7434827 18036899 19840588 0
lockedpages 0 0 880 880 0
privvmpages 139358 147841 503155 3553470 0
shmpages 1325 1981 50315 50315 0
dummy 0 0 0 0 0
numproc 68 79 800 800 0
physpages 53126 60787 0 2147483647 0
vmguarpages 0 0 512503155 1547483647 0
oomguarpages 53126 60787 503155 2147483647 0
numtcpsock 27 66 800 800 0
numflock 5 14 704 774 0
numpty 2 3 80 80 0
numsiginfo 1 20 1024 1024 0
tcpsndbuf 400392 856168 2735500 6012300 0
tcprcvbuf 337984 712824 2735500 6012300 0
othersockbuf 267376 559592 1367750 4644550 0
dgramrcvbuf 0 8440 1367750 1367750 0
numothersock 148 193 800 800 0
dcachesize 0 0 3936932 4055040 0
numfile 2644 3185 7040 7040 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 10 10 200 200 0

[Updated on: Wed, 07 February 2007 07:41] by Moderator

Report message to a moderator

Re: blank lsof output [message #10024 is a reply to message #10020]

Mon, 05 February 2007 16:26

Vasily Tarasov
Messages: 1345
Registered: January 2006

Senior Member

Hello,

Nothing odd with user_beancounters settings on my mind.
As concerns lsof output. For me it works... What kernel do you use?

Thanks,
Vasily.

Report message to a moderator

Re: blank lsof output [message #10025 is a reply to message #10024]

Mon, 05 February 2007 16:31

skizzo
Messages: 10
Registered: December 2006

Junior Member

this is what uname reports:
2.6.18-028test005 #4 SMP Sat Dec 2 02:28:58 EST 2006 i686 athlon i386 GNU/Linux

skizzo

strace lsof output reads:

fstat64(3, {st_mode=S_IFREG|0755, st_size=1529392, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7f4d000
mmap2(NULL, 1254812, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7e1a000
mmap2(0xb7f47000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x12d) = 0xb7f47000
mmap2(0xb7f4a000, 9628, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7f4a000
close(3) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7e19000
set_thread_area({entry_number:-1 -> 6, base_addr:0xb7e196c0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0,
useable:1}) = 0
mprotect(0xb7f47000, 8192, PROT_READ) = 0
mprotect(0xb7f6f000, 4096, PROT_READ) = 0
munmap(0xb7f4e000, 31465) = 0
getrlimit(RLIMIT_NOFILE, {rlim_cur=1024, rlim_max=1024}) = 0
close(3) = -1 EBADF (Bad file descriptor)
close(4) = -1 EBADF (Bad file descriptor)
close(5) = -1 EBADF (Bad file descriptor)

...and so on up 10 descriptor 1024

[Updated on: Mon, 05 February 2007 16:34]

Report message to a moderator