Weird - I try to add eight lines of text to root in /var/spool/cron/crontabs and i get:
"scp: /var/spool/cron/crontabs/root: No space left on device"
Surely this cannot be hitting the limit?
Those files probably aren't but the filesystem may already be full, so trying to copy any additional information won't work. Have you tried doing a df and see if you are in fact filling up the storage?
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at:
VMware Code Central - Scripts/Sample code for Developers and Administrators
![]()
If you find this information useful, please award points for "correct" or "helpful".
Filesystem Size Used Available Use% Mounted on
visorfs 218.3M 183.8M 34.5M 84% /
vmfs3 1.4T 1.1T 301.6G 78% /vmfs/volumes/4a7f6526-91bbfcb7-1aad-001e4f3fe854
vfat 249.7M 59.3M 190.4M 24% /vmfs/volumes/7cfc25ed-9e7abe3b-92b0-4b92d4cdeb1e
vfat 249.7M 60.5M 189.2M 24% /vmfs/volumes/53cc92eb-5326110e-6194-a0c34fc4fe34
vfat 285.9M 242.7M 43.2M 85% /vmfs/volumes/efd8efe3-03bc1cbf-15e0-080efd9e7379
nfs 2.7T 2.0T 784.7G 72% /vmfs/volumes/7f11a7af-49abb21a
Looks like plenty of room to store a kilobyte or two?
Hmmm ... even stranger. I was getting a read-only message from vi so i chmoded to 777 and pasted the lines, saved it with no errors, went to view it and hoila - zero byte file, empty, zilch ![]()
William - this actually for your script. How many entries have you successfully put into crontabs?
Haven't tried, we don't use ESXi ... and generally our crons are setup outside of the host say through a launch box such as vMA.
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at:
VMware Code Central - Scripts/Sample code for Developers and Administrators
![]()
If you find this information useful, please award points for "correct" or "helpful".
Did you ever solve this problem, having the exact same problem tried to delete old log files but that didn't work!
Solved it by creating scripts to launch other scripts, problem was that with all parameters and folder names the line in crontab became to big! so by creating a script containing all the parameters i could call that script using very few characters.
In http://communities.vmware.com/docs/DOC-8760, look under the 'Cronjob FAQ ' section, subheading 'Configure on ESXi:', where it describes copying the /var/spool/cron/crontabs/root file, making the changes, then moving it back. That worked for me on ESXI 4.0
