Project

General

Profile

Actions

Bug #4473

closed

Jetty cache files in /tmp directory are removed by the OS tmpwatch cron job, preventing access to the application

Added by Alex Tkachenko about 10 years ago. Updated over 8 years ago.

Status:
Released
Priority:
2
Assignee:
Matthieu CERDA
Category:
Web - Maintenance
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

I was not able to work on Rudder for over a week and when I tried to log in today I've got a white screen with a couple of screen and no images.

The apache logs show the following errors (just an example, there are more):

10.32.48.196 - - [14/Feb/2014:14:05:33 -0800] "GET /rudder/javascript/jquery/jquery-1.8.3.min.js HTTP/1.1" 404 286 "https://sjc1-ops-proxmox01-ve-104.carrieriq.com/rudder/" "Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Firefox/24.0" 
10.32.48.196 - - [14/Feb/2014:14:05:33 -0800] "GET /rudder/images/themes/ui-lightness/jquery.ui.all.css HTTP/1.1" 404 293 "https://sjc1-ops-proxmox01-ve-104.carrieriq.com/rudder/" "Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Firefox/24.0" 
10.32.48.196 - - [14/Feb/2014:14:05:33 -0800] "GET /rudder/style/rudder-login.css HTTP/1.1" 404 271 "https://sjc1-ops-proxmox01-ve-104.carrieriq.com/rudder/" "Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Firefox/24.0" 
10.32.48.196 - - [14/Feb/2014:14:05:33 -0800] "GET /rudder/images/logoIndexRudder.jpg HTTP/1.1" 404 275 "https://sjc1-ops-proxmox01-ve-104.carrieriq.com/rudder/" "Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Firefox/24.0" 

The problem went away after restarting jetty; I was able to track it down to the directory /tmp/jetty-127.0.0.1-8080-rudder.war-_rudder-any- - if I manually delete this directory, the effect is the same.

So apparently this was the daily cron job (I am using CentOS 6) which removes files not accessed for certain period of time.

The problem could be addressed in one of two ways:

  1. Create an exception for the tmpwatch in /etc/cron.daily/tmpwatch to exclude certain directories (which exactly?)
  2. Create temp files elsewhere, where the tmpwatch does not apply.

Either approach has its own pros and cons - i.e. it could be made a matter of policy to maintain the tmpwatch file (but rpm upgrades will be fixing it all the time); on the other hand deploying the war and whatnot in the application directory may be subject to upgrade problems.

I do not know the right solution at the moment but thought I would bring it up just to raise awareness of the issue.

Actions

Also available in: Atom PDF