I have created a package using the “AIX Fileset Deployment Wizard” but I keep getting the JobDiskFreeLimited in the agent log as detailed during the download phase.
ActionLogMessage: (action 101 ) JobDiskFreeLimited - try again in 10 minutes
The package is 1597mb, at first it would stop at around 63mb but after growing various filesystems it stops at 1073. The ulimit is unlimited as default and there is no user with a specific value.
df -m
Filesystem MB blocks Free %Used Iused %Iused Mounted on
Part of this could be based on limits for the user the agent is running as or on your file system.
To set this limit from the Korn shell, run the following command:
ulimit -f unlimited
To set this value permanently for a specific user, use the chuser command, as shown in the following example:
chuser fsize_hard = -1 root
The maximum size of a file is ultimately a characteristic of the file system itself, not just the file size limit or the environment, as follows:
For the JFS, the maximum file size is determined by the parameters used at the time the file system was made. For JFS file systems that are enabled for large files, the maximum file size is slightly less than 64 gigabytes (0xff8400000). For all other JFS file systems, the maximum file size is 2Gb-1 (0x7fffffff). Attempts to write a file in excess of the maximum file size in any file system format will fail, and errno will be set to EFBIG.
For the JFS2, the maximum file size is limited by the size of the file system itself.
If both of these conditions are met then you might be encountering some other issue.
Although last reply is 2194 days old - still seems to be the place to reply
a) my partition is, by design, coming up with minimal fs sizes
b) I got the message “JonDiskFreeLimited” which is not too surprising – but, it is still unclear which filesystems the BESClient is looking at. More than just /opt and 1G free space it seems.
I am going to increase the filesystems - starting with /, then /tmp, then /var - to 1G and hope I can report which filesystem did the trick.
Update: not sure - but it seems /var needs to have extra space - as with / and /tmp - both with over 1G free - message continued. After increasing /var to have > 1G free the actions continued normally.
Actually - my bad! I was thinking the BESClient was in /opt - but that is just the executable. /var/opt/BESClient is what needs space - and I need to make a task the root/server can run (or perhaps a relay - to create a new filesystem at /var/opt/BESClient before I deploy the agent!
IMHO: bad practice to depend on /var - as there are too many other things that depend on /var - but nice to see that BESClient is monitoring it’s (BESClient) free space - rather than stomp on /var.