No, no idea. I usually put several MB attachments into elogs without problems. Can you try with the demo logbook https://midas.psi.ch/elogs/Linux+Demo/. Maybe you have an old version of elog? 

You have an old version of elog, this bug has been fixed some time ago. Have a look for example at https://midas.psi.ch/elogs/Linux+Demo/.

If you click on a peperclip there, the attachment is shown correctly. 

Hi Devin,

first of all, your stack traces are only of limited use for me. This typically happens 
if you attach gdb to a running process, then you get something like

#0  0x080b2f8a in decode_post ()
#1  0x00000100 in ?? ()
#2  0x00000000 in ?? ()

(note the ??). If you run elogd directly from gdb, the stack trace contains much more information:

[meg@megon elog]# gdb elogd
...

(gdb) run
...
Server listening on port 8080 ...

Program received signal SIGINT, Interrupt.
0x0000003cb48c78d3 in __select_nocancel () from /lib64/libc.so.6
(gdb) where
#0  0x0000003cb48c78d3 in __select_nocancel () from /lib64/libc.so.6
#1  0x000000000046ea51 in server_loop () at src/elogd.c:27688
#2  0x0000000000471de8 in main (argc=1, argv=0x7fffe2b9bf18) at src/elogd.c:29018
(gdb) 

including the line numbers, arguments etc. So please try to start elogd from inside gdb 
and then reproduce your crash.

Your first problem seems to be related to some contents of your elogd.cfg, since in 
one stack dump I saw a 

strlen()
...
getcfg()

Here, the getcfg() function is called to retrieve some configuration from elogd.cfg. 
Maybe you have a very long line, or the file is otherwise corrupt. Please check that
carfully and send me your elogd.cfg so that I can have a look myself. Usually it helps
to remove one line after the other and check when the problem disappears.

Your other problem which has the decode_post() in the stack dump seems to be related
to the case when you upload an entry (or attachment), and the TCP link breaks in 
the middle. Probably the error handling in such a case is not correct. I will try
to reproduce this, although I don't have a satellite network.

Best regards,

  Stefan

 No problem attaching big files on F10 or CentOS 4.7.   The one that is having issue was on JeOS-8.0.4 - Ubuntu ;-).  All tested with ELOG version 2.7.5 build 2130.

There was a general problem in submitting entries. If the TCP connection between the browser and elog 
disconnects during the transmission and only part of the request gets transferred, it consistently 
crashed elog. The probability for this is large if you have a slow connection and long attachments. The problem 
has been fixed in SVN revision 2174, so please upgrade and try again.

 Correction.  The OSes are OK.  But don't use Opera when uploading big files.

 Thanks - just downloaded and compiled the latest version and all is well

Hi,

I was wondering if anybody else seen this problem and maybe has a solution. I use Elog version 2.7.5 rev. 2172 that I compiled from the tar.gz package on a Ubuntu PC. It is very strange that everything works fine except I can not view / download PDF attachments specifically. I can view / download images and I can download all sorts of file formats: xls, doc, ppt, etc. Viewing in the same window / tab or in a different one does not work. Saving the attachment produces a file empty file with the correct name! This is so strange, for example following a link from an image or any other attachment type works but if that link is a PDF file I get an empty page! When uploading a PDF file there a thumbnails that are generated, I do view the thumbnail but not the PDF itself! I didn't even managed to start a download on PDF attachment.

Any help would be appreciated!