Kbase P175996: File system is filling up and I cannot see the files using up the space.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/25/2010 |
|
Status: Unverified
SYMPTOM(s):
File system is filling up and I cannot see the files using up the space.
The UNIX command df -k is showing that the file system is almost full.
FACT(s) (Environment):
The file system that is filling up is where the scripts that start the database are located.
lsof -p shows the files are associated with _mprosrv executable.
Database is started by a script.
Script to start the database is ran as root.
The script does not contain any commands to change the working directory to the directory where the file system is filling up.
The home directory for root is not the same one that is filling up.
Database supports both 4GL and SQL clients.
The database is not started with the -T or -t parameters.
WRKDIR environment variable is not set.
UNIX
Progress/OpenEdge Product Family
OpenEdge Category: Database
CHANGE:
Database had manually been restarted recently after an abnormal shutdown.
CAUSE:
The temporary files associated with the server processes for the database are filling up the file system. This is because the database was started in the directory where the scripts exist. If you do not use the -T parameter, OpenEdge creates these temporary files in the current working directory. These files cannot be seen because they are unlinked. OpenEdge stores these files as unlinked, with no visible name in the UNIX file system (unless you use the Save Temp Files (-t) parameter on startup of the database.
FIX:
Either add more file system space to the device that is becoming full if making use of logical volume groups or shutdown the database.
Once the database is shutdown the temporary files will be removed. Then prior to starting the database either:
1. Set the environment variable WRKDIR to identify where you would like the Temporary files to go. or
2. Make use of the -T parameter on the database command line to identify the directory where you would like the temporary files placed. or
3. Change the directory (either manually or via the script) to the directory that you would like the temporary files to go. Then when you start the script from this directory, the temporary files associated with the remote server processes will be placed within the current working directory.