Derwood
Newbie
Karma: 1
Posts: 19
|
 |
« on: March 16, 2011, 02:15:38 AM » |
|
G'day all,
has anyone experience the problem where the file ticket.cgi sudeenly has a filesize of zero?
I have been running TTX for 2 years now, without any serious problems and twice in two days the file tickets.cgi has just suddenly decided all the data is gone and its filesize is now zero. loosing everything in the file and everything grinds to a halt.
luckily we lost nearly nothing in the end and were able to recover due to good backs.
Darren
|
|
|
|
|
Logged
|
|
|
|
Sparky
Moderator
Hero Member
   
Karma: 83
Posts: 2,228
stop pushing all those buttons
|
 |
« Reply #1 on: March 16, 2011, 02:37:40 AM » |
|
That's not good. I cannot think of one thing internally that would cause that to happen unless there's some kind of upper limit on the file size and you keep hitting it. I know the tickets themselves each have a max file size and everything after that gets cropped.
Send a ticket to Alex and report back what you find out.
|
|
|
|
|
Logged
|
Did you update the paths in ttxcfg.cgi after moving TTX to your new location? To those seeking help.... please report back when you figure it out. 
|
|
|
|
Alex
|
 |
« Reply #2 on: March 16, 2011, 09:37:55 AM » |
|
The TTX does not operate on tickets.cgi directly. Every time script needs to update the tickets.cgi, it builds temporary file and renames the temporary file into tickets.cgi when ready. If during rename operation (which is a single call to internal Perl function) script was terminated the outcome is unpredictable.
The rename operation may also fail due to hitting file system quota - watch your disk usage.
Please also notice that standard edition is for evaluation only. For production environments please use either MySQL or SQL Server Edition.
|
|
|
|
|
Logged
|
|
|
|
Derwood
Newbie
Karma: 1
Posts: 19
|
 |
« Reply #3 on: March 17, 2011, 10:43:47 PM » |
|
thanks guys, we had plenty of space on the server... or at least should have and we certainly do now.
Alex, if the temp file wasnt renamed, what is the name of this temp file. I might have been able to recover by renaming that file.
We have had no further issues in the two days since, so everything seems back to normal.
I might have to look at the SQL version I think.
|
|
|
|
|
Logged
|
|
|
|
|
Alex
|
 |
« Reply #4 on: March 21, 2011, 10:13:01 AM » |
|
tickets.cgi.tmp
|
|
|
|
|
Logged
|
|
|
|
Derwood
Newbie
Karma: 1
Posts: 19
|
 |
« Reply #5 on: March 22, 2011, 09:29:36 PM » |
|
argh, I would have noticed this so it wasnt there.
as for going to Mysql or Sql, what happens to the tickets already created and in use?
thanks guys...
|
|
|
|
|
Logged
|
|
|
|
Sparky
Moderator
Hero Member
   
Karma: 83
Posts: 2,228
stop pushing all those buttons
|
 |
« Reply #6 on: March 22, 2011, 09:51:25 PM » |
|
The SQL module comes with a conversion script for importing all the old flat-file tickets.
|
|
|
|
|
Logged
|
Did you update the paths in ttxcfg.cgi after moving TTX to your new location? To those seeking help.... please report back when you figure it out. 
|
|
|
|
Alex
|
 |
« Reply #7 on: March 22, 2011, 10:09:06 PM » |
|
As a matter of fact, the conversion script is already on your server. Just point your browser at sqlsetup.cgi, sign in using admin password, provide MySQL connection info and submit the form - doing this will import all your tickets to MySQL database (the system will continue using flat text database if no MySQL module installed).
|
|
|
|
|
Logged
|
|
|
|
|
|
Derwood
Newbie
Karma: 1
Posts: 19
|
 |
« Reply #9 on: March 27, 2011, 08:31:29 AM » |
|
suggest you do it, or keep good backups. I just had it happen again. not sure whats going on here.
|
|
|
|
|
Logged
|
|
|
|
Sparky
Moderator
Hero Member
   
Karma: 83
Posts: 2,228
stop pushing all those buttons
|
 |
« Reply #10 on: March 28, 2011, 05:26:25 PM » |
|
Too much to do first... like upgrade to 3.0 and apply my zillion custom modifications.
I just wrote a little Perl script to do a daily backup of tickets.cgi via a cron job.
- copies the tickets.cgi file to a new file appended with a time-stamp in the filename - emails me a confirmation complete with file size and total size of the backup directory
In the daily email, I'll see that a new backup was created and if the file size reports back anything weird like zero, I'd know immediately. My hosting account does not have a size limitation but I will see the backup directory grow and can clean it out every so often. For me, even if I forget about it, it looks like a daily backup would accumulate to roughly 50-100 MB per year... this is still only a fraction of the total space I'm using now.
|
|
|
|
« Last Edit: March 28, 2011, 05:36:24 PM by Sparky »
|
Logged
|
Did you update the paths in ttxcfg.cgi after moving TTX to your new location? To those seeking help.... please report back when you figure it out. 
|
|
|
Derwood
Newbie
Karma: 1
Posts: 19
|
 |
« Reply #11 on: April 16, 2011, 05:42:06 AM » |
|
Sounds like it shouldnt be a problem for you if it happens now.
Am very happy with the switch to SQL, searching seems faster.
thanks guys for the help.
|
|
|
|
|
Logged
|
|
|
|
|