Clearing the .debug file (reducing the size) fixed the issue. I was told this was a bug in Microlite and the .debug file was appending instead of overwriting as it should be doing.
Thanks for all your suggestions.
User Profile
Collapse
-
Hello
Thanks you for your input. Microlite support which you can get free email support is pretty good. Arne gets back very quickly. He asked for the .debug file to be sent to him. When I checked the file it was huge 2147483647 bytes. I ran the program from the command line and received the "File size limit exceeded error". I then made a copy of .debug the cat /dev/null > .debug. I reran the program from the comman line...Leave a comment:
-
First, I want to thank you for taking the time to help me.
This is a program file so I can't edit it.
Cron runs the command at a certain time and that is it...it has done the same thing now for 6 years - no issues.
Lots of space...the full system backup with verify only takes 3 hours and we ran a menu initiated backup yesterday.
I have contacted Microlite - they don't know
It must have something to do with how...Leave a comment:
-
This will be a standard user answer..lol..." nothing changed" from May 2 when the backup ran fine to May 3rd when the error began. This server never gets touched. It just runs a database. I know something has changed in the system but I don't know what cron sees about file size limit when the ulimit is unlimited.Leave a comment:
-
No it isn't. I would suspect if the files were too big the backup couldn't run from the menu...which it can. I think it must be to do with how cron does the job. the error is "sh line 1. File size limit exceeded /usr/lib/edge/bin/edge.nightly. "edge.night ly" is the executable of the scheduled backup program.
Thanks for replying. I'm sure someone has seen or heard of this and it's an easy fix.Leave a comment:
-
Cron issue using backup software - Solved
We are using the backup program Microlite Backup Edge on a Centos OS. When running the program from the menu, we can backup with no problem. When we schedule a backup in cron, we get an error "file size limit exceeded". The ulimit of the system is unlimited and this program has been running for years. It has just happened recently and the program will not run. Any ideas?
ThanksLast edited by mikee99; Jun 5 '13, 01:17 PM. Reason: Issue was solved and wanted to update everyone that a solution was found
No activity results to display
Show More
Leave a comment: