Menu
▾
▴
#539 Attachments being lost - 0 bytes
Attachments have been discovered to contain 0 bytes
following migration from Ver.1.1.2 to Ver2. This has
also occurred on subsequent occasions with new
attachments. In some cases the same file type has been
lost in subsequent ticket replies. So far it has been
evident on some pdf files and with .hmd files, which
are specific to our applications. I have attached
copies of 2 hmd which were lost during migration to Ver.2
Zip of the .hmd files
Logged In: YES
user_id=1241761
There appears to be no obvious explanation for this in the
code. MailManager relies upon the python email library for
parsing and decoding mail, which is quite comprehensively
tested. In order to resolve this further, we really need a
recent example of processing with version 2.x with new
attachments being lost. A full export of the ticket, message
, history and attachment tables from SQL for that message
would be exceptionally helpful.
* Has the server ever run our of disk space?
* What email client was used to send in the tickets
* What version of python/zope is being used on the target
platform
* What database backend is being used?
I'm not sure what is meant by "In some cases the same file
type has been lost in subsequent ticket replies.". Do you
mean that the attachment was present in full, but after a
reply was sent to a ticket, the attachment was then set to 0
bytes in the database?
Logged In: YES
user_id=838577
Unfortunately, some elements of the support requests are
covered by confidentiality and may need to be sanitised, but
I will try to get a full export. Meanwhile to answer your
questions:
* The server is a new server with plenty of spare disk space
* We run the script MMGetMail.py using cron to fetch mail
* Zope 2.8.5-final, python 2.3.5(#2, Aug 30 2005, 15:50:26)
[GCC 4.0.2 20050821 (prerelease) (Debian 4.0.1-6)]
* Postgres 8.0 running on the same Debian server
* what I meant was that in the originator request the .hmd
file was 0 bytes, but other attachments to that request were
ok. On subsequent replies to the ticket via MM where similar
attachments were added, the .hmd file on each occasion was 0
bytes. Since the original and some replies were created in
MM Ver1.1.2 many of the missing files were a result of
migrating to Ver2.0, as we were able to restart the old
server and recover some of the missing files. The files
provided in the first attachment to this bug are 2 of the
recovered files.
As mentioned, I will arrange a full export of an offending
ticket (suitably sanitised) in a followup.
Logged In: YES
user_id=838577
Kevin, I have received further information from users which
would suggest that the problem may only be associated with
records which were migrated from Ver1.1.2. Since some of
those records are still ongoing (Open tickets) I would
appreciate info on how to restore them to Postgres.
Do you still require the attachment table data?
Logged In: YES
user_id=1241761
If it's purely migration related, then there may still be a
clearer explanation in the code for why the problem
occurred. I'll read through the code some more. Additional
attachments are probably not necessary at this stage,
although feel free to upload as it may reduce the delay
should it be found they are necessary.