Re: [Trac] Trac 0.12.1 attachements after upload broken
goo...@ifo.net wrote: Hi all, We have the problem, that every attachment are broken after upload via the trac-page. This could be an image (jpg or png), which is corrupt, if you download the file again. If you upload executable files, the executables are corrupt and so on. There are no error-message in Debug-Log, nor special config settings for this behavior. May you have some suggestions, Thanks in advance! Greets, Peter Hi Peter. For your information I want to point your attention to my own post: Subj: [Trac] Attachment upload error - stringobject: bad argument to internal function Date: Mon, 17 Jan 2011 10:37:14 +0100 From: Clemens Feige c.fe...@osypkamed.com With my Trac 0.11.6 I had/have problems with large binary files when uploading as ticket attachment. I experimented a little. My guess is that Trac is trying to read a binary file line-by-line like a text file. But because binary files do not have normal line-breaks the line to read can become huge. If the line is getting too large (somewhere at 240.000 characters) then it fails. The crazy thing is that my problem depends not only on file size but also on file contents. Note that different from your case, for my issue I get an error message when it happens. Clemens -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Trac 0.12.1 attachements after upload broken
Dear Matthew, I have solved the problem with a new trac install using the Tracd-server. Greets, Peter Dear Matthew, No I found the time to make a check with your suggested binary tools. I have uploaded the 5MB image again, which is in correct view at my localhost. For the check I upload the correct image from localhost to server via ssh. After compare with vbindiff I can see differences in those files. So, the upload of the 5MB image get broken after upload on the trac server. A great start to the new year, Greets Peter! On 11/25/2010 07:34 AM, goo...@ifo.net wrote: Dear Matthew, Sorry for my late response, but I have a lot to fix in my company... And I was on holiday, so I apologize for my even later response. What about your suggestion with binary diff, how could I do on the linux-system? May you have an example. apt-cache search binary diff returns the kitchen sink. A quick looking about in that lists suggests: vbindiff xdelta hexdiff bsdiff -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Trac 0.12.1 attachements after upload broken
Dear Matthew, No I found the time to make a check with your suggested binary tools. I have uploaded the 5MB image again, which is in correct view at my localhost. For the check I upload the correct image from localhost to server via ssh. After compare with vbindiff I can see differences in those files. So, the upload of the 5MB image get broken after upload on the trac server. A great start to the new year, Greets Peter! On 11/25/2010 07:34 AM, goo...@ifo.net wrote: Dear Matthew, Sorry for my late response, but I have a lot to fix in my company... And I was on holiday, so I apologize for my even later response. What about your suggestion with binary diff, how could I do on the linux-system? May you have an example. apt-cache search binary diff returns the kitchen sink. A quick looking about in that lists suggests: vbindiff xdelta hexdiff bsdiff -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Trac 0.12.1 attachements after upload broken
On 11/25/2010 07:34 AM, goo...@ifo.net wrote: Dear Matthew, Sorry for my late response, but I have a lot to fix in my company... And I was on holiday, so I apologize for my even later response. What about your suggestion with binary diff, how could I do on the linux-system? May you have an example. apt-cache search binary diff returns the kitchen sink. A quick looking about in that lists suggests: vbindiff xdelta hexdiff bsdiff -- Matthew Caron Build Engineer Sixnet | www.sixnet.com O +1 518 877 5173 Ext. 138 F +1 518 602 9209 matt.ca...@sixnet.com -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Trac 0.12.1 attachements after upload broken
Dear Matthew, Sorry for my late response, but I have a lot to fix in my company... On a corrupt file, are the file sizes exactly the same? Yes, it's exactly the same byte-size! If have tested the localfile with the uploaded file on the server. I also download the 5MB-Jpg-Image with the browser and via ssh-command to localhost again. All files have the same size. What about your suggestion with binary diff, how could I do on the linux-system? May you have an example. Greets, Peter On 11/19/2010 10:30 AM, goo...@ifo.net wrote: No truncation. I have uploaded a 5MB JPG-Image, it also has 5MB on the server. If I download the image, you can view the image, but it's a corrupted (wrong colors and so on). On a corrupt file, are the file sizes exactly the same? I guess my next step would be a binary diff of two small-ish files which exhibit this corruption. At this point, we're firmly into strange crap territory. I have seen corruption like this in the past, and it often comes down to I compare the files, and notice that the corruption happens because there is random garbage inserted on interval boundaries, and then the file picks up again. In a case like that, the issue is that someone is reading interval + some size bytes out of a buffer into which only interval bytes have been stuffed, etc. -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
[Trac] Trac 0.12.1 attachements after upload broken
Hi all, We have the problem, that every attachment are broken after upload via the trac-page. This could be an image (jpg or png), which is corrupt, if you download the file again. If you upload executable files, the executables are corrupt and so on. There are no error-message in Debug-Log, nor special config settings for this behavior. May you have some suggestions, Thanks in advance! Greets, Peter -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Trac 0.12.1 attachements after upload broken
On 11/19/2010 08:02 AM, goo...@ifo.net wrote: This could be an image (jpg or png), which is corrupt, if you download the file again. May you have some suggestions, What happens with a plain text file? My thought is, if it is being mangled in some way, and you upload a plain text file, how it is being mangled may become apparent. What happens if you upload a file, then copy it off the server via some other method (say, like scp). Is it still corrupt? What happens if you try a different browser to do the upload? -- Matthew Caron Build Engineer Sixnet | www.sixnet.com O +1 518 877 5173 Ext. 138 F +1 518 602 9209 matt.ca...@sixnet.com -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Trac 0.12.1 attachements after upload broken
Dear Matthew, Thanks for your response! What happens with a plain text file? My thought is, if it is being mangled in some way, and you upload a plain text file, how it is being mangled may become apparent. The textfile is normal, no corruptions. What happens if you upload a file, then copy it off the server via some other method (say, like scp). Is it still corrupt? Yes, file is still corrupt. What happens if you try a different browser to do the upload? The same problem. If have tested more uploads yet. As I can see, a png-Image with about 3KB size is ok, if the png-Image is a larger on (about 140KB), the image is corrupt. Could the size a problem for the upload? In my oppinion 140KB is not so big for a documentation image. Greets, Peter -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Trac 0.12.1 attachements after upload broken
On 11/19/2010 09:46 AM, goo...@ifo.net wrote: Dear Matthew, Thanks for your response! What happens with a plain text file? My thought is, if it is being mangled in some way, and you upload a plain text file, how it is being mangled may become apparent. The textfile is normal, no corruptions. Based on your subsequent comments, it may be because the text file is small. If have tested more uploads yet. As I can see, a png-Image with about 3KB size is ok, if the png-Image is a larger on (about 140KB), the image is corrupt. Could the size a problem for the upload? In my oppinion 140KB is not so big for a documentation image. Hmm.. in trac.ini, what is max_size (under [attachment]) set to? I wonder if it is set to 140k, and the the file you're trying to upload is too big logic is not working correctly in 0.12? (I'm still on 0.11.6). Also, are the files corrupt because they're truncated to some limit, or are they full size? If, for example, you're uploading a 3M file, but only 140K hits disk, that could easily be the cause of the corruption (which is slightly different than it getting mangled but being roughly the same size). Also, hitting long shots here: - is the disk full? - is the webserver user hitting some usage quota? - How does a 4K file do? 8K? 16K? I ask because these are typical allocation blocksizes for a variety of storage systems. If, for example, your RAID controller is doing something strange, it could result in badness there (although you would be noticing a lot more random crashes and everything would be largely going down in flames). -- Matthew Caron Build Engineer Sixnet | www.sixnet.com O +1 518 877 5173 Ext. 138 F +1 518 602 9209 matt.ca...@sixnet.com -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Trac 0.12.1 attachements after upload broken
Dear Matthew, Hmm.. in trac.ini, what is max_size (under [attachment]) set to? I wonder if it is set to 140k, and the the file you're trying to upload is too big logic is not working correctly in 0.12? (I'm still on 0.11.6). I installed the trac system with the instructions at http://trac.edgewall.org/wiki/TracInstall with fcgi-Mode on apache. I set up the max_size-limit to 12MB (12629760 bytes). Also, are the files corrupt because they're truncated to some limit, or are they full size? If, for example, you're uploading a 3M file, but only 140K hits disk, that could easily be the cause of the corruption (which is slightly different than it getting mangled but being roughly the same size). No truncation. I have uploaded a 5MB JPG-Image, it also has 5MB on the server. If I download the image, you can view the image, but it's a corrupted (wrong colors and so on). Also, hitting long shots here: - is the disk full? No - is the webserver user hitting some usage quota? No, I have no quota set up. It's a up 2 date 10.04 ubuntu virtual server, without raid. - How does a 4K file do? 8K? 16K? I ask because these are typical allocation blocksizes for a variety of storage systems. If, for example, your RAID controller is doing something strange, it could result in badness there (although you would be noticing a lot more random crashes and everything would be largely going down in flames). You are raid, if it will be caused by raid, that would be horrible ;) The test with 4,8,16kb file was positiv - all images are correct. Peter On 11/19/2010 09:46 AM, goo...@ifo.net wrote: Dear Matthew, Thanks for your response! What happens with a plain text file? My thought is, if it is being mangled in some way, and you upload a plain text file, how it is being mangled may become apparent. The textfile is normal, no corruptions. Based on your subsequent comments, it may be because the text file is small. If have tested more uploads yet. As I can see, a png-Image with about 3KB size is ok, if the png-Image is a larger on (about 140KB), the image is corrupt. Could the size a problem for the upload? In my oppinion 140KB is not so big for a documentation image. Hmm.. in trac.ini, what is max_size (under [attachment]) set to? I wonder if it is set to 140k, and the the file you're trying to upload is too big logic is not working correctly in 0.12? (I'm still on 0.11.6). Also, are the files corrupt because they're truncated to some limit, or are they full size? If, for example, you're uploading a 3M file, but only 140K hits disk, that could easily be the cause of the corruption (which is slightly different than it getting mangled but being roughly the same size). Also, hitting long shots here: - is the disk full? - is the webserver user hitting some usage quota? - How does a 4K file do? 8K? 16K? I ask because these are typical allocation blocksizes for a variety of storage systems. If, for example, your RAID controller is doing something strange, it could result in badness there (although you would be noticing a lot more random crashes and everything would be largely going down in flames). -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Trac 0.12.1 attachements after upload broken
On 11/19/2010 10:30 AM, goo...@ifo.net wrote: No truncation. I have uploaded a 5MB JPG-Image, it also has 5MB on the server. If I download the image, you can view the image, but it's a corrupted (wrong colors and so on). On a corrupt file, are the file sizes exactly the same? I guess my next step would be a binary diff of two small-ish files which exhibit this corruption. At this point, we're firmly into strange crap territory. I have seen corruption like this in the past, and it often comes down to I compare the files, and notice that the corruption happens because there is random garbage inserted on interval boundaries, and then the file picks up again. In a case like that, the issue is that someone is reading interval + some size bytes out of a buffer into which only interval bytes have been stuffed, etc. -- Matthew Caron Build Engineer Sixnet | www.sixnet.com O +1 518 877 5173 Ext. 138 F +1 518 602 9209 matt.ca...@sixnet.com -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Trac 0.12.1 attachements after upload broken
On 11/19/2010 10:59 AM, Matthew Caron wrote: I guess my next step would be a binary diff of two small-ish files which exhibit this corruption. To be more clear - this should be between the original and corrupted version of the same file. -- Matthew Caron Build Engineer Sixnet | www.sixnet.com O +1 518 877 5173 Ext. 138 F +1 518 602 9209 matt.ca...@sixnet.com -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
