Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 674 of 807  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6456 Entries 
Goto page Previous  1, 2, 3 ... 673, 674, 675 ... 805, 806, 807   Next  
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  66375   Thu Jun 4 17:51:02 2009 Reply Mikemike@raghuexim.comBug reportLinux2.7.6-2204Re: Embedded images break when moving from one book to another.

Stefan Ritt wrote:

 

Mike wrote:

Here's the issue. We use elog to develope products we need to be able to see all the thumbnail images in a

particular logbook. Our default view is to use the threaded view fully expanded in order to have all the thumbnails

be displayed for each product. This works fine but when we move one message to another logbook the thumbnails

end up getting broken and won't be displayed. The only way to fix this is to remove the image and re-upload the

picture after the message is moved. This is not a good option because we have hundrends of items that are

constantly being moved around from logbook to logbook. Any ideas?

Regards,

Mike

 

EDIT:

On further inspection it seems that when you are moving messages to another log book the image date filename

is re-written which of course breaks the html link to the image.  Is there anyway to supress this so that the filename

stays in tact when it's moved from one book to another. I don't see why the name of an attachment has to get changed

just because something is moved around.

 

I fixed this in revision #2204. The attachment names now stay the same. There is one tiny risk of screwing up, namely if you have the same attachment name in two different logbooks (accidentally also submitted at the same second and therefore the same time stamp). If you then copy these two entries to a third logbook, one attachment will overwrite the other one, but that risk is indeed really small. I actually had to re-write the link to the attachment inside the text body (even differently for ELCode and HTML encoding). So I'm not 100% sure I covered all cases, so just give it a try.

 This is a major improvement. The only issue now is when we embed an image in the body of the message elog makes a nice thumbnail. When you move the message to another logbook the thumbnail doesn't work and instead it shows the MASSIVE full size version of the picture instead. Is that possible to fix?

 

Thanks Stefan!

Mike

  66376   Thu Jun 4 17:51:50 2009 Entry jon huangjon.huang@ses.comBug reportWindows2.76Memory leak in 2.76 elogd.exe

Hi,

There's seems to be a memory leak with elogd.exe running windows.  I had this problem with older version of elogd.exe, i've just upgrade to the latest and the problems still exist. I've had this issue with earlier versions.  I've just upgrade elog to the latest 2.76 version. The memory leak still persist. I really appreciate if you or anyone here can help me resolve this issue.

Thank!

JH

 

Attachment 1: elogd.jpg
elogd.jpg
  66377   Thu Jun 4 18:49:29 2009 Reply Paul T. Keenerkeener@hep.upenn.eduBug reportOther2.7.5Re: elogd dies after receiving second SIGHUP
> > > > elogd continues to run after a SIGHUP. If a second SIGHUP is received the daemon terminates.
> > > > This was observed on Solaris 10 (SPARC).
> > > > The documentation states that elogd should re-read configuration after receiving SIGHUP.
> > > 
> > > I tried to reproduce this but without success. I could send many SIGHUPs without the daemon terminating. Maybe 
> > > you modified the configuration file in between and elogd barked out because of some wrong configuration? Try to 
> > > start the daemon interactively and see what exactly happens if you send several SIGHUPs.
> > 
> > The problem is that under Solaris signal handlers installed via signal() get uninstalled *before* the signal handler
> > is called.  Thus the second time elogd receives a SIGHUP, you get the default action, which is to kill the process.
> > 
> > The solution is to use the POSIX sigaction() call instead of signal(). 
> 
> Can you try to modify the signal() calls into sigaction(). If this really works under Solaris, I will incorporate this 
> then into the distribution.

Here is the patch.  It works under both Solaris and Linux.
Attachment 1: elogd-signal.patch 
*** src/elogd.c-orig	2009-04-14 04:16:02.000000000 -0400
--- src/elogd.c	2009-06-04 11:33:31.337804000 -0400
***************
*** 27553,27558 ****
--- 27553,27565 ----
     SSL_CTX *ssl_ctx;
  #endif
  
+    /*
+     * sigaction structs
+     */
+    struct sigaction ctrlc_handle;
+    struct sigaction ignore_handle;
+    struct sigaction hup_handle;
+ 
     i_conn = content_length = 0;
     net_buffer_size = 100000;
     net_buffer = xmalloc(net_buffer_size);
***************
*** 27708,27718 ****
        close(fd);
     }
  
!    /* install signal handler */
!    signal(SIGTERM, ctrlc_handler);
!    signal(SIGINT, ctrlc_handler);
!    signal(SIGPIPE, SIG_IGN);
!    signal(SIGHUP, hup_handler);
     /* give up root privilege */
     if (geteuid() == 0) {
        if (!getcfg("global", "Grp", str, sizeof(str)) || setegroup(str) < 0) {
--- 27715,27739 ----
        close(fd);
     }
  
!    /*
!     * install signal handlers 
!     */
!    ctrlc_handle.sa_handler = ctrlc_handler;
!    sigemptyset( &ctrlc_handle.sa_mask );
!    ctrlc_handle.sa_flags = 0;
! 
!    sigaction(SIGTERM, &ctrlc_handle, NULL);
!    sigaction(SIGINT, &ctrlc_handle, NULL);
! 
!    ignore_handle.sa_handler = SIG_IGN;
!    sigaction(SIGPIPE, &ignore_handle, NULL);
! 
!    hup_handle.sa_handler = hup_handler;
!    sigemptyset( &hup_handle.sa_mask );
!    hup_handle.sa_flags = 0;
!    sigaction(SIGHUP, &hup_handle, NULL);
! 
! 
     /* give up root privilege */
     if (geteuid() == 0) {
        if (!getcfg("global", "Grp", str, sizeof(str)) || setegroup(str) < 0) {
  66378   Fri Jun 5 10:51:17 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.76Re: Memory leak in 2.76 elogd.exe

 

jon huang wrote:

Hi,

There's seems to be a memory leak with elogd.exe running windows.  I had this problem with older version of elogd.exe, i've just upgrade to the latest and the problems still exist. I've had this issue with earlier versions.  I've just upgrade elog to the latest 2.76 version. The memory leak still persist. I really appreciate if you or anyone here can help me resolve this issue. 

 

ELOG has been carefully designed not to contain memory leaks. The server for this forum for example runs for months without problem:

[ritt@midas ~]$ ps aux | grep elogd

elog      1958  0.4  3.1  39412 32940 ?        Ss   May09 178:16 /usr/local/sbin/elogd -D -c /usr/local/elog/elogd.cfg

So if you have a problem, it must be specific to your installation. You should note that if you up- or download big attachents, memory gets allocated for some network buffers to contain these attachments. The buffer is kept to contain the largest attachment, it will never shrink. But once established, it will also not grow. If you see however a constant increase in memory consumption, I would appreciate if you tell me how you do this. Like which configuration you use, if you just read entries or also upload them, etc. etc. Once I can reproduce exactly your problem, I can try to fix it. 

  66381   Fri Jun 5 12:42:55 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.6-2204Re: Embedded images break when moving from one book to another.
Mike wrote:

 This is a major improvement. The only issue now is when we embed an image in the body of the message elog makes a nice thumbnail. When you move the message to another logbook the thumbnail doesn't work and instead it shows the MASSIVE full size version of the picture instead. Is that possible to fix?

 

Thanks Stefan!

Mike

Can you try revision #2206? 

 

  66382   Fri Jun 5 13:18:00 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportOther2.7.5Re: elogd dies after receiving second SIGHUP
> Here is the patch.  It works under both Solaris and Linux.

Thanks! I put that into revision #2207.
  66383   Fri Jun 5 14:13:52 2009 Reply Mikemike@raghuexim.comBug reportLinux2.7.6-2207Re: Embedded images break when moving from one book to another.

Stefan Ritt wrote:
Mike wrote:

 This is a major improvement. The only issue now is when we embed an image in the body of the message elog makes a nice thumbnail. When you move the message to another logbook the thumbnail doesn't work and instead it shows the MASSIVE full size version of the picture instead. Is that possible to fix?

 

Thanks Stefan!

Mike

Can you try revision #2206? 

 

 Stefan,

Works perfectly, thanks for the fix you rock!

Mike

  66409   Wed Jun 24 13:23:49 2009 Entry Michael Husbynmichael.husbyn@gmail.comBug reportWindows2.7.6(my) Firefox breaks Elog with this config file
Hi, Did a fresh install on a Windows 2003 server (and tried it on my personal computer) After startup I can click on Norway/nor, and then the server just stops responding. I see in the log nothing, the last line: Received unknown cooke "style" Then it stops responding and after a few seconds I see the dos window returns to commandline prompt. Probably a very bad config file. On Windows XP it informs we of Dr Watson, memory could not be read message. Using Firefox 3.0.11 But if I use IE 7, no problem at all.. Any suggestion? Best regards Michael Husbyn
Attachment 1: elogd.cfg 
[global]
port = 8091

group Norway=nor
group Sweden=swe
group Denmark=den

[nor]
Comment = $subject
Theme = default
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type


[den]
Theme = default
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
Comment = General linux tips & tricks

[swe]
Comment = General linux tips & tricks
Theme = default
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
Goto page Previous  1, 2, 3 ... 673, 674, 675 ... 805, 806, 807   Next  
ELOG V3.1.5-3fb85fa6