4.0.20 -> 4.1.2 Problem with tmp directory growing up

Discussion in 'Bug Reports' started by track1, Jul 27, 2011.

  1. track1

    track1 Well-Known Member

    after upgrading to from 4.0.20 to 4.1.2, /tmp/ directory begins to grow (1gb), but do not get to show any files that occupy that space. Restarting litespeed returns to be free space and starts to grow again.

    Any idea?

    Cache is activated but cache files only takes 50-60mb and there is a cron task that deletes.

    With 4.0.20 /tmp/ dir have about 90% free space and doesn't go up.
  2. webizen

    webizen Well-Known Member

    try 'du -sk /tmp/lshttpd* |sort -n | tail' when /tmp is getting big
  3. mistwang

    mistwang LiteSpeed Staff

  4. track1

    track1 Well-Known Member

    du -skh /tmp/lshttpd* |sort -n | tail
    612K /tmp/lshttpd

    df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/sda5 9.7G 1.4G 7.8G 16% /
    /dev/sda8 996M 323M 622M 35% /tmp

    # service lsws restart

    # df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/sda5 9.7G 1.4G 7.8G 16% /
    /dev/sda8 996M 119M 825M 13% /tmp
  5. track1

    track1 Well-Known Member

    i don' tthink is related to open files, my settings are correct.

    root@[/tmp]# /usr/sbin/lsof -u root | wc -l
    root@[/tmp]# /usr/sbin/lsof -u nobody | wc -l
    root@[/tmp]# ulimit -n

    Anyway just did a force reinstall to check again.
  6. track1

    track1 Well-Known Member

    still with problems:

    Filesystem Size Used Avail Use% Mounted on
    /dev/sda8 996M 866M 79M 92% /tmp

    # service lsws restart

    Filesystem Size Used Avail Use% Mounted on
    /dev/sda8 996M 85M 860M 9% /tmp

    Just downgraded @ v4.0.20 to check if this problem exists.
  7. NiteWave

    NiteWave Administrator

    have you enabled cache and cache folder under /tmp ?
  8. track1

    track1 Well-Known Member


    but was taking only 50-70mb max, with clean cron running.

    Currently with 4.0.20 and zero config changes no problem at moment.
  9. NiteWave

    NiteWave Administrator

    anyway, here's the latest:
    #curl -I http://www.litespeedtech.com/packages/4.0/lsws-4.1.2-ent-x86_64-linux.tar.gz
    HTTP/1.1 200 OK
    Date: Mon, 01 Aug 2011 12:49:46 GMT
    Server: LiteSpeed
    Accept-Ranges: bytes
    Keep-Alive: timeout=5, max=100
    ETag: "30dd26-4e331221-1bc8de9"
    Last-Modified: Fri, 29 Jul 2011 20:03:45 GMT
    Content-Type: application/gzip
    Content-Length: 3202342
    Connection: keep-alive

    if your 4.1.2 is older, please do a force-reinstall again.
  10. track1

    track1 Well-Known Member

    will wait one day with 4.0.20 to be sure tmp problem is related to lsws, and then force reinstall to latest 4.1.2 (i was using version downloaded day 28, so wasn't day 29 build).
  11. track1

    track1 Well-Known Member

    no problems at all with 4.0.20, dir /tmp/ is at 15% usage all time and doesn't grow.

    Just forced-install upgrade again to 4.1.2 build 29 Jul, will report if problem continues.

Share This Page