New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Double archive creation v3.0 #285
Comments
From c...@3pcmedia.com on January 21, 2012 01:48:21 Can you attempt this on 3.1 to see if you can replicate this problem? I cannot. |
From borislav...@gmail.com on January 21, 2012 14:48:18 |
From borislav...@gmail.com on January 21, 2012 15:43:30
Will report back. |
From borislav...@gmail.com on January 21, 2012 16:23:42 Backup action created two archives with a bit different timestamp. |
From borislav...@gmail.com on January 21, 2012 16:24:26 |
From borislav...@gmail.com on January 21, 2012 16:49:54 I will contact tech support, but I will need some input from you, as I wouldn't know what to tell them. From the testing I've done (turning stuff on and off), I couldn't come to idea what might cause this. Maybe it is an internal problem on their side. |
From borislav...@gmail.com on January 21, 2012 17:03:11 Deleting all stuff from uploads resulted in one archive created. Could it be that the archive creation is capped in size? I've noted 600M limit in the code. |
From borislav...@gmail.com on January 21, 2012 18:35:05
attach Than, I return to the old install, try backup, and again two archives. Somewhere in the middle, FTP gives two files in creation, in paralel. Attached. |
From m...@digimute.com on January 21, 2012 20:57:14 the 2 other file above are the temp files created when zipping up the folders , why they failed who knows... we should disable the create archive button until the zip file is created or fails. |
From borislav...@gmail.com on January 21, 2012 23:22:33 The strange.png is just a representation of a process when process created zips, both archives were correctly created. The what now.png show the situation with new release. I have checked the time stamps, and they are created ~30 sec apart, in both cases (old version and new version). Please mind that I am testing on a quality cluster, using quality equipment, and don't have Parkinson's. :-) Any idea beyond double click? |
From borislav...@gmail.com on January 21, 2012 23:34:36 Any way to solve this? |
From ccagle8 on January 23, 2012 01:42:41 |
From borislav...@gmail.com on January 23, 2012 09:06:36
The archive job(s) are always completed. According to tech support, ZIP is resource intensive, and can even be turned off sometimes (than an error pops up). They suggested using tar gz instead zip, as it always available. |
From borislav...@gmail.com on January 23, 2012 23:22:57 Please do ask me to do any tests you think out to get this problem sorted out, I will be happy to oblige! |
From ccagle8 on January 26, 2012 01:58:08 |
From borislav...@gmail.com on January 26, 2012 06:46:35 Tried set_time_limit(0) myself, but it didn't work. I've also tried doing that in .htaccess (php engine is controlled from it on the cluster), but it also didn't work. I am setting up a three environments for testing: clusterdedicated serverconvetional hostingWill report back with findings. |
From borislav...@gmail.com on January 26, 2012 14:49:20 I have tested the archive creation on cluster - the result is as before dedicated server - while ZipArchive was installed, and GS reported it works, when the create archive was clicked, it gave ZipArchive error convetional hosting (cpanel) - the archive creation worked nicely // What should I do now? |
From ccagle8 on January 28, 2012 00:41:46 |
From borislav...@gmail.com on January 28, 2012 01:11:30 |
From borislav...@gmail.com on January 28, 2012 01:12:35 |
From tablatronics on May 11, 2012 19:26:19 |
From borislav...@gmail.com on May 11, 2012 19:53:02 Archive size is 200+ MB. |
From tablatronics on May 12, 2012 04:18:48 |
From borislav...@gmail.com on May 12, 2012 06:57:43 |
From tablatronics on May 20, 2012 01:04:47 |
From borislav...@gmail.com on May 20, 2012 20:34:56 |
From tablatronics on May 22, 2012 14:30:37 |
From borislav...@gmail.com on May 22, 2012 15:55:41 Give me instructions what to do, and I will. |
From tablatronics on August 20, 2012 15:54:34 Will debug. |
From borislav...@gmail.com on August 20, 2012 17:19:01 |
This is hard to nail down, but I am pretty certain it has to do with our synchronous browser request waiting for the response, or a php timeout or both. This is a bad pattern, browsers will timeout, which might be recalling the page. We might have to have have an ajax request that checks periodically instead of the synchronous browser request for long waits. This is something we should build in for other operations as well. |
No progress on this yet, problem not persisting. |
Original author: borislav...@gmail.com (January 20, 2012 23:32:55)
What steps will reproduce the problem?
Doing website archive on RackSpace cluster
What is the expected output? What do you see instead?
One file, and instead two archive files with almost the same (time differs a bit) name appear.
What version of the product are you using? On what operating system?
3.0
RackSpace cluster
There are some plugins, I've tested with and without them and no change
Please provide any additional information below.
The site is very large 140MB+
Original issue: http://code.google.com/p/get-simple-cms/issues/detail?id=285
The text was updated successfully, but these errors were encountered: