large attachment seems to hang elogd?, posted by Haitao Yu on Tue Mar 7 21:41:28 2006
|
Hello,
I am trying to attach somewhat large file (4-15MB files tested) with my messages but it seems to hang the elogd server for a really long time (30-100minutes). The file upload was done pretty soon (within a few seconds), then the elogd process seems to be busy doing something, using around 50MB of memory and 95% of CPU time, and stop respond to the requests. I can read the logbook with another copy of elogd running on another port, and I can see (and download) the uploaded file. I am wondering what could cause the problem --- and could it be related to the problem of not setting up the SMTP server right? Thanks for any suggestion!
Haitao
P.S. I read in some old message that if we want to upload very large files, we have to change the WEB_BUFFER_SIZE in elogd.c, however this parameter is no longer in v2.6.1. Is there something similiar I have to change? |
Re: large attachment seems to hang elogd?, posted by Konrad Klimaszewski on Thu Oct 25 09:43:52 2007
|
Hello,
I'm observing the same behavior with ELOG V2.6.5-1844.
Is there a fix for this?
Best Regards,
Konrad |
|
Re: large attachment seems to hang elogd?, posted by Jacky Li on Wed Oct 31 22:33:49 2007
|
Hi,
I am having the same problem with 2.6.4.1 and the latest version. It just hangs and taking a long time to upload multiple of 1.5 to 2 MB attachments...or just one few MB attachment. Hope that's a fix soon. |
|
Re: large attachment seems to hang elogd?, posted by Jacky Li on Wed Oct 31 22:39:54 2007
|
Hi,
I did more testing..if I suppress email notification, it is fast. There is something wrong there.
| Jacky Li wrote: | Hi,
I am having the same problem with 2.6.4.1 and the latest version. It just hangs and taking a long time to upload multiple of 1.5 to 2 MB attachments...or just one few MB attachment. Hope that's a fix soon. |
|
|
Re: large attachment seems to hang elogd?, posted by Jacky Li on Wed Oct 31 22:44:06 2007
|
Ok,
I noticed that the email notification got two copies of the attached files to elog post. It looks like the cause is
between elog and the mail server. When there is email notification, the attachement is sent along to the mail server and that's taking a long time and there are two copies of the attachment.
| Jacky Li wrote: | Hi,
I did more testing..if I suppress email notification, it is fast. There is something wrong there. |
|
Re: large attachment seems to hang elogd?, posted by Konrad Klimaszewski on Mon Nov 5 14:00:56 2007
|
Hi,
| Jacky Li wrote: | Ok,
I noticed that the email notification got two copies of the attached files to elog post. It looks like the cause is
between elog and the mail server. When there is email notification, the attachement is sent along to the mail server and that's taking a long time and there are two copies of the attachment.
| Jacky Li wrote: | Hi,
I did more testing..if I suppress email notification, it is fast. There is something wrong there.
|
|
Indeed I can confirm that without email notification it's blazing fast. I haven't observed attachments being send twice. Though I got two indentical entries in the elog.
On my box I'm using sendmail. Until there is some fix in the way elog comunicates with mailer (if it is possible that is) could we have an option to suppress sending attachments in email notification?
Best Regards,
Konrad |
|
Re: large attachment seems to hang elogd?, posted by Stefan Ritt on Mon Nov 5 14:06:41 2007
|
| Konrad Klimaszewski wrote: | | Until there is some fix in the way elog comunicates with mailer (if it is possible that is) could we have an option to suppress sending attachments in email notification? |
There is such an option:
Email format = 47
This tells elog to send email notifications without attachments. Anyhow I would not recommend to send big attachments as emails, since most email systems won't allow you that. Since the attachments are base64 encoded, the encoding can also take quite a long time. |
|
Re: large attachment seems to hang elogd?, posted by Konrad Klimaszewski on Mon Nov 5 14:15:55 2007
|
| Stefan Ritt wrote: |
| Konrad Klimaszewski wrote: | | Until there is some fix in the way elog comunicates with mailer (if it is possible that is) could we have an option to suppress sending attachments in email notification? |
There is such an option:
Email format = 47
This tells elog to send email notifications without attachments. Anyhow I would not recommend to send big attachments as emails, since most email systems won't allow you that. Since the attachments are base64 encoded, the encoding can also take quite a long time. |
Great  . I missed this one while digging through documentation.
Maybe you could consider setting as default:Email format = 111
Cheers,
Konrad |
|
Re: large attachment seems to hang elogd?, posted by Stefan Ritt on Mon Nov 5 14:20:27 2007
|
| Konrad Klimaszewski wrote: | Great . I missed this one while digging through documentation.
Maybe you could consider setting as default:Email format = 111 |
Well, then people will come up and ask: I can see some attachment name in my email, but the attachment is missing, what can I do?. So they would not find the configuration option as you did not, and complain here. You never can make everybody happy 
An alternative approach however would be to limit the attachment size. If above 1 MB for example, do not send it. Then make this a flexible parameter (maybe someone wants 2 MB). I will think about that. |
|
Re: large attachment seems to hang elogd?, posted by Konrad Klimaszewski on Mon Nov 5 14:34:31 2007
|
| Stefan Ritt wrote: |
| Konrad Klimaszewski wrote: | Great . I missed this one while digging through documentation.
Maybe you could consider setting as default:Email format = 111 |
Well, then people will come up and ask: I can see some attachment name in my email, but the attachment is missing, what can I do?. So they would not find the configuration option as you did not, and complain here. You never can make everybody happy
An alternative approach however would be to limit the attachment size. If above 1 MB for example, do not send it. Then make this a flexible parameter (maybe someone wants 2 MB). I will think about that. |
Of course you're right. I suggested using "111" because then in email notification there is a link to the attachment.
Which for me is enough . But there always will be someone that's not happy.
Your solution is nice but then attachments will be sent in a bit inconsistent way.
Easier would be to make it more obvious in the documentation.
I don't know put it in the FAQ or something (under: "Why my posts with large attachments are submitted so slowly"  ).
Best Regards,
Konrad
PS
Thanks for implementing ELCode for tables - love them  |
|
Re: large attachment seems to hang elogd?, posted by Stefan Ritt on Mon Nov 5 15:05:33 2007
|
| Konrad Klimaszewski wrote: | | I don't know put it in the FAQ or something (under: "Why my posts with large attachments are submitted so slowly" ). |
http://midas.psi.ch/elog/faq.html#18
| Konrad Klimaszewski wrote: | | Thanks for implementing ELCode for tables - love them |
Have you tried tables in HTML form? Even better! Just switch the encoding from ELCode to HTML (starting from version 2.7.0). |
|
Re: large attachment seems to hang elogd?, posted by Jacky Li on Tue Nov 20 22:27:03 2007
|
Hi,
I put in the option:
Email Format = 111
Attachment still comes in to the notification instead of the link. I am using elog-2.7.0-1. Any ideas? Thank you.
| Stefan Ritt wrote: |
| Konrad Klimaszewski wrote: | | I don't know put it in the FAQ or something (under: "Why my posts with large attachments are submitted so slowly" ). |
http://midas.psi.ch/elog/faq.html#18
| Konrad Klimaszewski wrote: | | Thanks for implementing ELCode for tables - love them |
Have you tried tables in HTML form? Even better! Just switch the encoding from ELCode to HTML (starting from version 2.7.0). |
|
Re: large attachment seems to hang elogd?, posted by Stefan Ritt on Thu Nov 22 14:16:51 2007 
|
| Jacky Li wrote: | I put in the option:
Email Format = 111
Attachment still comes in to the notification instead of the link. I am using elog-2.7.0-1. Any ideas? |
You will see the attachment name in the notification (see below), but the actual attachment is not contained in the email, thus making it very small. |
Quick Filter including Subtext applied overzealously?, posted by Richard Stamper on Mon Nov 12 15:58:57 2007
|
When there are two or more Quick Filters available, and one of them is on the Subtext attribute, once one of the other filters has its value changed the null text for the Subtext selection criterion (namely, "-- Text --") is used as a genuine selection criterion, thus typically preventing any entries from matching.
This is for v2.7.0-1961 with both Mozilla 2.0.0.9 and IE 6 on Windows XP Professional SP2, and I think has appeared with this release. You can demonstrate the behaviour on this forum:
- Go to http://midas.psi.ch/elogs/Forum/
- Quick filter on dates in the "Last Month" and nothing is listed. The URL is now http://midas.psi.ch/elogs/Forum/?last=31&Subtext=--+Text+--
- Set the date filter back to "-- All Entries --" and the spurious subtext filter remains; the URL is now http://midas.psi.ch/elogs/Forum/?Subtext=--+Text+--
- Delete the "-- Text --" value in the filter box and everything reappears; the URL is back to http://midas.psi.ch/elogs/Forum/
Richard Stamper
|
|
Re: Quick Filter including Subtext applied overzealously?, posted by Stefan Ritt on Tue Nov 13 11:04:58 2007
|
| Richard Stamper wrote: |
|
When there are two or more Quick Filters available, and one of them is on the Subtext attribute, once one of the other filters has its value changed the null text for the Subtext selection criterion (namely, "-- Text --") is used as a genuine selection criterion, thus typically preventing any entries from matching.
This is for v2.7.0-1961 with both Mozilla 2.0.0.9 and IE 6 on Windows XP Professional SP2, and I think has appeared with this release. You can demonstrate the behaviour on this forum:
- Go to http://midas.psi.ch/elogs/Forum/
- Quick filter on dates in the "Last Month" and nothing is listed. The URL is now http://midas.psi.ch/elogs/Forum/?last=31&Subtext=--+Text+--
- Set the date filter back to "-- All Entries --" and the spurious subtext filter remains; the URL is now http://midas.psi.ch/elogs/Forum/?Subtext=--+Text+--
- Delete the "-- Text --" value in the filter box and everything reappears; the URL is back to http://midas.psi.ch/elogs/Forum/
|
Thanks for reporting this. I fixed it in revision 1964. You can test it in this forum. |
Re: Quick Filter including Subtext applied overzealously?, posted by Richard Stamper on Wed Nov 21 14:21:08 2007
|
| Stefan Ritt wrote: |
|
| Richard Stamper wrote: |
|
When there are two or more Quick Filters available, and one of them is on the Subtext attribute, once one of the other filters has its value changed the null text for the Subtext selection criterion (namely, "-- Text --") is used as a genuine selection criterion, thus typically preventing any entries from matching.
This is for v2.7.0-1961 with both Mozilla 2.0.0.9 and IE 6 on Windows XP Professional SP2, and I think has appeared with this release. You can demonstrate the behaviour on this forum:
- Go to http://midas.psi.ch/elogs/Forum/
- Quick filter on dates in the "Last Month" and nothing is listed. The URL is now http://midas.psi.ch/elogs/Forum/?last=31&Subtext=--+Text+--
- Set the date filter back to "-- All Entries --" and the spurious subtext filter remains; the URL is now http://midas.psi.ch/elogs/Forum/?Subtext=--+Text+--
- Delete the "-- Text --" value in the filter box and everything reappears; the URL is back to http://midas.psi.ch/elogs/Forum/
|
Thanks for reporting this. I fixed it in revision 1964. You can test it in this forum.
|
Working perfectly! Many thanks for your usual quick response.
|
|
Quick filter - Subtext, posted by An Thai on Mon Nov 19 14:11:33 2007
|
The default subtext "-- Text --" for quick filter is included when another attribute is selected. So that the searched category always shows 0 entrie
I cannot find this problem on your demo forum, but it is happening on my server.
My config:
Quick filter = Author, Category, SubText
Result: Please see the screenshot attached. |
|
Re: Quick filter - Subtext, posted by Stefan Ritt on Mon Nov 19 14:25:48 2007
|
| An Thai wrote: |
|
The default subtext "-- Text --" for quick filter is included when another attribute is selected. So that the searched category always shows 0 entrie
I cannot find this problem on your demo forum, but it is happening on my server.
My config:
Quick filter = Author, Category, SubText
Result: Please see the screenshot attached.
|
It's fixed already, that's why you cannot see it on the demo server. So just download elog270-2.exe and install it. |
New ELOG version with HTML Editor, posted by Stefan Ritt on Fri Oct 26 14:00:48 2007
|
I'm pleased to announce the release of ELOG version 2.7.0 which contains the HTML editor FCKeditor. This allows the formatting of ELOG entries just as one is used from a word processor. I tried to make all functionality working as one is used from the ELCode system (like replies quote the original text in a yellow text box), but I'm not sure if I covered everything. So if you experience problems with the new editor, please report it and I will try to fix it. Anyhow it is always possible to switch back to the old ELCode encoding.
One warning for site administrators: Since it is possible to enter HTML code directly into a web page, one risks a XSS vulnerability. If someone knows how to protect the FCKeditor against submission of JavaScript, please let me know and I will add it. If this is an issue, you can turn off HTML encoding completely for public ELOG sites with allowed encoding = 3 in elogd.cfg.
Finally I would like to give credits to An Thai who proposed this editor.
|
|
Re: New ELOG version with HTML Editor, posted by An Thai on Tue Nov 13 17:59:35 2007
|
Congratulation Stefan and Co.!
I think Elog is the first Weblog which supports this feature.
The new integrated HTML WYSIWYG editor is great. Now, my colleagues who are in finance department and don't have good IT-skill will be very happy about this feature.
Thank you for your support and effort.   |
Email notification: "Use Email From = " always set to admin, posted by Alan Stone on Thu Oct 25 23:36:28 2007
|
My current syntax is:
; Email notification
Suppress Email to users = 0
Omit Email To = 1
Use Email Subject = $system: $subject
#Use Email From = Author Email
Email Report General = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
I had to comment out the 'Use Email From' option because all forwarded
entries to the CMS HyperNews or Fermilab ListServer appeared to originate
from me (alstone@fnal.gov), even though other users were logged in and
saving the entries to the logbook. After commenting out this line, the
entries were properly credited when forwarded, although the
There are two admins defined in the [global] section, and "alstone" is
not the first name in the "Admin user" list.
Is this a bug, or have I used this option incorrectly?
Alan |
|
Re: Email notification: "Use Email From = " always set to admin, posted by Stefan Ritt on Fri Oct 26 11:44:36 2007
|
| Alan Stone wrote: |
My current syntax is:
; Email notification
Suppress Email to users = 0
Omit Email To = 1
Use Email Subject = $system: $subject
#Use Email From = Author Email
Email Report General = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
I had to comment out the 'Use Email From' option because all forwarded
entries to the CMS HyperNews or Fermilab ListServer appeared to originate
from me (alstone@fnal.gov), even though other users were logged in and
saving the entries to the logbook. After commenting out this line, the
entries were properly credited when forwarded, although the
There are two admins defined in the [global] section, and "alstone" is
not the first name in the "Admin user" list.
Is this a bug, or have I used this option incorrectly?
Alan |
Documentation says:
If Use Email From is present, it is always used. If not, the email address of the currently logged in user is used for the "From:" field. If no user is logged in, or the current user has not specified a email address in the password database, the setting of the option Default Email From is used for the "From:" field. Only if this option is not specified, a generic address ELOG@<hostname> is used, which might be rejected by the SMTP server however.
So if you write
Use Email From = me@some.where
then of course all emails have "me@some.where" in the From: field. If you want the email of the people logged in, you either remove this option (since it's the default anyhow), or you write explicitly
Use Email From = $user_email |
|
Email Notification: Clarification on Attribute - can value be a string?, posted by Alan Stone on Thu Oct 25 23:55:28 2007
|
I encountered a rather insidious feature which had me scratching trying quite
a number of things over the past couple of weeks until I compared what two
different users were doing.
I had defined the attributes:
; attributes
Attributes = Author, System, Report, Subject
Required Attributes = Author, System, Report, Subject
Extendable Options = System, Report
Options System = Data Transfer, RelVal, Skimming, Reconstruction, CSA07, Global Running, T0 Operations, T1 Operations, DataOps, ProdAgent
#Options Report = General, Fix, Info, Job Report, Problem, Shift Summary, Test, Flummoxed
Options Report = General, Fix, Info, Job_Report, Problem, Shift_Summary, Test, Flummoxed
Thread display = $Subject, entered by $author for $system on $Entry time
Quick filter = Date, Report
Reverse sort = 1
and the Email Notification:
; email notification
Suppress Email to users = 0
Omit Email To = 1
Use Email Subject = $system: $subject
#Use Email From = Author Email
Email Report General = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
Email Report Fix = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
Email Report Info = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
#Email Report Job Report = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
Email Report Job_Report = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
Email Report Problem = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
#Email Report Shift Summary = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
Email Report Shift_Summary = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
I finally realized that logbook entries sent with a two-word Attribute value
(Shift Summary, Job Report) would not be forwarded to the CMS HyperNews
forum or Fermilab List Server. I incorrectly assumed that:
Email <attribute> <value> = <list>
an attribute could be a string.
Do I have to remove the spaces (replace with hyphens or underscores)?
Alan |
|
Re: Email Notification: Clarification on Attribute - can value be a string?, posted by Stefan Ritt on Fri Oct 26 11:18:59 2007
|
If you read
http://midas.psi.ch/elog/config.html#email
you will see the sentence:
If either the attribute or the value contains one or more blanks the string must be enclosed with quotation marks, as in:
* Email Type "Normal routine" = ...
so in your case you should write
Email Report "Shift Summary" = ... |
|
Date attribute in Quick filter, posted by Peter Rienstra on Thu Oct 25 12:04:02 2007
|
Stefan,
I downloaded the latest source (ELOG V2.6.5-1946) to solve another problem. But now I get:
Error: "Attribute "Date" for quick filter not found", see attachment.
In the configfile I have: Quick filter = Date
A bug?
(It works fine, so it's not really a big problem.) |
|
Re: Date attribute in Quick filter, posted by Stefan Ritt on Thu Oct 25 20:15:46 2007
|
| Peter Rienstra wrote: | I downloaded the latest source (ELOG V2.6.5-1946) to solve another problem. But now I get:
Error: "Attribute "Date" for quick filter not found", see attachment.
In the configfile I have: Quick filter = Date
A bug? |
Yep. Fixed in V2.6.5-1951. |
|
extendable options, posted by Arno Teunisse on Sat Oct 13 15:32:23 2007
|
Hello
running ELOG V2.6.5-1890
Snap of the config file :
=======================
; attributes
Attributes = OS, Version, Klant , Category, Subject
Options OS = AIX{1}, HP-UX{2} , Redhat{3} , Suse{4}, Fedora{5}, SUN{6}
Options Category = Documentation, disk , network , software , backup , boot,
Options Klant = None, Cust1 , Cust2 , Cust3 , Cust4, Cust5
{1} options Version = 4.3, 5.1 , 5.2 ,5.3
{2} options Version = 10.20, 11.11, 11.23
{3} options Version = 4.0
{4} options Version = 10.0
{5} options Version = 5.0,6.0,7.0
{6} options Version = 5.6,5.7,5.8,5.9,5.10
extendable Options = Category, Klant, OS , Version
============ end of snap
When I click the "Add Version" button Elog end's with a "Internal error, no
valid header!" after hitting the submit button. ( See attachments )
An other problem is when I add a new OS and a new Version at the same time. The
OS is added , ( without the {7} extension.) and no new "{7} options version = "
gets added.
Is there a way to get this going? |
|
Re: extendable options, posted by Stefan Ritt on Mon Oct 22 16:33:50 2007
|
| Arno Teunisse wrote: | When I click the "Add Version" button Elog end's with a "Internal error, no
valid header!" after hitting the submit button. ( See attachments ) |
"Extendable Options" are currently only possible outside any condition. While
Options Version = 1,2,3
will work, the following will not
{1} Options Version = 1,2,3
I will add a note to the documentation about this. |
|
Re: extendable options, posted by Stefan Ritt on Mon Oct 22 21:22:28 2007
|
| Arno Teunisse wrote: |
; attributes
Attributes = OS, Version, Klant , Category, Subject
Options OS = AIX{1}, HP-UX{2} , Redhat{3} , Suse{4}, Fedora{5}, SUN{6}
Options Category = Documentation, disk , network , software , backup , boot,
Options Klant = None, Cust1 , Cust2 , Cust3 , Cust4, Cust5
{1} options Version = 4.3, 5.1 , 5.2 ,5.3
{2} options Version = 10.20, 11.11, 11.23
{3} options Version = 4.0
{4} options Version = 10.0
{5} options Version = 5.0,6.0,7.0
{6} options Version = 5.6,5.7,5.8,5.9,5.10
extendable Options = Category, Klant, OS , Version |
Actually me previous statement was incorrect. Extendable options work also under conditions. Your problem is that you specified
{1} options Version = 4.3, 5.1 , 5.2 ,5.3
instead
{1} Options Version = 4.3, 5.1 , 5.2 ,5.3
(note the capital O). If you change that, it will work. Anyhow I changed the code so that the case of these statements is ignored in the future. |
|
|
ELOG V3.1.5-3fb85fa6 |