Sponsored Content
Top Forums UNIX for Advanced & Expert Users cron/logrotate chicken and egg problem Post 302235915 by strike-2 on Saturday 13th of September 2008 07:53:26 PM
Old 09-13-2008
Just a silly question:
Are you sure you have inodes available on /var?
('df -i', depending on your O/S)

If your inode table is full, you may have space on the disk but you can't make a new file to rotate the data into.
 

8 More Discussions You Might Find Interesting

1. Red Hat

Problem seen with logrotate

Hi all, I have configured logrotate to logorotate every 12 hour. The configurations are as follows. /etc/cron.d/config ------------------------- SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO="" HOME=/root 0 */12 * * * root logrotate /etc/logrotate.d/test ... (1 Reply)
Discussion started by: rsravi74
1 Replies

2. UNIX for Advanced & Expert Users

logrotate with /etc/logrotate.conf file

Hi there, I want to rotate the logfiles which are located in /var/log/jboss/tomcat* so I have created a file named as 'tomat' in /etc/logrotate.d/tomcat with the following content. # cat /etc/logrotate.d/tomcat /var/log/jboss/tomcat_access_log*.log { daily nocreate ... (2 Replies)
Discussion started by: skmdu
2 Replies

3. UNIX for Advanced & Expert Users

Logrotate configuration problem

Hi, I have the following configuration file: /logs/system/mindundi/* { rotate 0 daily missingok sharedscripts postrotate find /logs/system/mindundi/ -name "*log" -mtime +15 -exec /bin/rm -f {} \; endscript } I want to save only... (6 Replies)
Discussion started by: mitchbcn
6 Replies

4. UNIX for Dummies Questions & Answers

logrotate and cron.daily/weekly

Hi guys, I've got two separate logrotates I'd like to run, one for Tomcat and one for Apache, but I'd like to run the Tomcat one daily and the Apache one weekly. Now, the logrotate itself is working fine, but although I have 'daily' in Tomcat, and 'weekly' in the Apache one, the latter is... (2 Replies)
Discussion started by: jimbob01
2 Replies

5. Shell Programming and Scripting

Logrotate - I am not able to rotate files using logrotate

I have written script which is working in Home directory perfectly and also compressing log files and rotating correctly. But, when i try to run script for /var/log/ i am able to get compressed log files but not able to get rotation of compressed log files. Please suggest. I am using below command... (5 Replies)
Discussion started by: VSom007
5 Replies

6. AIX

Logrotate - /etc/logrotate.conf does't exist

Hi Admins. I have installed logrotate rpm on Aix 6.1. After the installation of rpm, I don't find /etc/logrotate.conf file and /etc/logrotate.d dir . The config file is located in /opt/freeware/etc/logrotate.conf. When I ran logrotate -v /opt/freeware/etc/logrotate.conf I get below... (2 Replies)
Discussion started by: snchaudhari2
2 Replies

7. Shell Programming and Scripting

Problem with logrotate

Hi, I have a problem with logrotate at Centos 7. My logrotate is configured with "rotate 0" to Apache logs, so it should never keep logs when rotating, just removing them and replacing by new empty ones at every rotation. But for some reason, once in a while, I see that logrotate is creating... (0 Replies)
Discussion started by: dado000
0 Replies

8. Shell Programming and Scripting

How to disable cron emails, but only for logrotate only not for other logs?

Guys, is there a script or command? how to disable cron emails, but only for logrotate only not for other logs (3 Replies)
Discussion started by: kenshinhimura
3 Replies
fitset(8)						      System Manager's Manual							 fitset(8)

NAME
fitset - determines if a software subset fits on a system SYNOPSIS
/usr/lbin/fitset [-c] [-d] [root-path] OPTIONS
This switch allows a file containing inventory records to be passed in as an argument in addition to the standard input. When this option is specified, fitset takes the inventory records in the file and reclaims the file system space and inodes they take up. Enables debug- ging. This option makes fitset print voluminous status information on standard output. This information is the initial file system sta- tistics, the file system location of the file from each input record, and the statistics for the file system after the space required to install the file has been deducted. DESCRIPTION
The fitset utility is used to determine if the files in a software subset will fit on a system. The fitset utility reads software subset inventory records from the standard input and calculates the number of inodes and the amount of disk space the software subset requires. For each record, fitset deducts one inode from the number available in the target file system. For the space calculation, fitset deducts the file size specified by each record. Only currently mounted file systems are included in the computations. Space requirements for files already on the disk are adjusted by using the difference between the specified size and the size of the file that is already present. A given software subset can include files that are to be installed in several file systems. The fitset utility tracks inodes and file space for all file systems affected and returns nonzero status if the remaining number of inodes or amount of free space for any of these file systems is overflowed. If there is no overflow, fitset returns a status of zero. The setld utility uses fitset to size all software subsets before attempting to install them. The root-path argument is the pathname of the top directory for the hierarchy into which the files are going to be installed. If no root-path is specified, the directory '/' is assumed. ERRORS
fitset: root-path must be absolute Explanation: A relative pathname was specified for root-path. The path must be absolute. fitset: cannot access path (error-message) Explanation: The path cannot be accessed. The error message provides more information. fitset: root-path is not a directory. Explanation: Either root-path is not a directory or it is a symbolic link to something which is not a directory. fitset: <warning> path is a symbolic link to itself Explanation: The path is a symbolic link that involves cyclic linking. fitset: file system path needs nnn Kbytes more to install the software specified. fitset: file system path needs nnn more inodes to install the software specified. Explanation: The file system path is out of space. The message that is displayed indicates whether the error is insufficient space or a lack of avail- able inodes. fitset: file system path is not writable. Explanation: The mode of the file system named by path does not permit writing into the file system. EXAMPLES
To determine if a particular software subset will fit on the system, redirect the contents of the software subset inventory file into fit- set. For example: fitset < /usr/.smdb./OSFEMACS350.inv To determine if the same software subset will fit in a hierarchy rooted at /var/tmp/root, the command would be: fitset /var/tmp/root < /usr/.smdb./OSFMANOP350.inv To determine if a particular software subset will fit on the system after the removal of another software subset, the command would be: fitset -c /usr/.smdb./OSFMANOS350.inv < /usr/.smdb./OSFMANOP350.inv FILES
Subset inventory files Log file SEE ALSO
Commands: setld(8) Files: stl_inv(4) Guide to Preparing Product Kits fitset(8)
All times are GMT -4. The time now is 03:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy