Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 232 of 801  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subject
  67918   Wed May 20 01:54:55 2015 Entry Konstantin Olchanskiolchansk@triumf.caBug reportOtherthis oneedit somebody else's draft
this elog offers me to edit a draft message, then yells at me "only some other user can edit this draft!!!".
methinks I should only be offered to edit draft messages that I own or I can edit. K.O.
  67917   Wed May 20 01:52:23 2015 Entry Konstantin Olchanskiolchansk@triumf.caBug reportOtherthis onethis elog errors sending email
this elog gives errors sending mail through PSI email server. (did not capture the error messages, sorry). K.O.
  67916   Wed May 20 01:49:37 2015 Entry Konstantin Olchanskiolchansk@triumf.caBug reportLinux3.1.0elconv deletes everything
Converting from elog 2.9.something to new elog 3.1.0 elogd refuses to start, instructs running elconv in one logbook.

When I do so, elconv converts a existing mhttpd-style elog entries to the new format (the corresponding new-format entries already exist)
and deletes everything else - this is very bad.

So there are 2 bugs:
- elogd should not tell us to run elconv when both old-style and corresponding new-style elog entries exist
- elconv should not delete all existing new-style elog entries.

I confirm that elconv *does* delete all new-style elog entries - with strace, I see it issue "unlink" on every elog entry.

What a disaster!

K.O.
  67915   Wed May 20 01:45:09 2015 Entry Konstantin Olchanskiolchansk@triumf.caBug reportLinux3.1.0elogd complains about unknown cookies
elogd is spewing these messages about unknown cookies:

Received unknown cookie "is_returning"
Received unknown cookie "__utma"
Received unknown cookie "__utmz"
Received unknown cookie "SSESSee3cc9c70bedf9a840203765bf409d7b"
Received unknown cookie "SESSee3cc9c70bedf9a840203765bf409d7b"
Received unknown cookie "MidasWikiUserID"
Received unknown cookie "MidasWikiUserName"
Received unknown cookie "MidasWiki_session"

K.O.
  67914   Tue May 19 16:34:20 2015 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.9.2Re: Entry size too large for email notification
Hi Jacky,
if I read the source code correctly then the maximum size of a base64 encoded email is hard coded to be 10 MB in elogd.h (recompile after changing it):
#define MAX_CONTENT_LENGTH 10*1024*1024
But I think that an 2.2 MB image should easily fit into that.
Andreas
Jacky Li wrote:

Hi,

I am doing an inline image that is about 2.2 MB.  When I do a submit, I got the following message:

Error sending Email via <i>"<email server>"</i>: Entry size too large for email notification.

May I know what is the limit of the entry size and how do I change it?  Thank you.

Jacky

  67913   Tue May 19 12:27:01 2015 Question Jacky Lizli@hawaii.eduQuestionLinux2.9.2Entry size too large for email notification

Hi,

I am doing an inline image that is about 2.2 MB.  When I do a submit, I got the following message:

Error sending Email via <i>"<email server>"</i>: Entry size too large for email notification.

May I know what is the limit of the entry size and how do I change it?  Thank you.

Jacky

  67912   Tue May 19 12:26:39 2015 Question Jacky Lizli@hawaii.eduQuestionLinux2.9.2Entry size too large for email notification

Hi,

I am doing an inline image that is about 2.2 MB.  When I do a submit, I got the following message:

Error sending Email via <i>"<email server>"</i>: Entry size too large for email notification.

May I know what is the limit of the entry size and how do I change it?  Thank you.

Jacky

  67911   Thu May 14 22:16:03 2015 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux3.1Re: csv import timestamp
Hi Ferdinand,
"import" is meant to be used for files that have been exported with "find". Therefore it is not very flexible with the date format.
Todays date should look like that: "Thu  14 May 2015 22:12:00 +0200".
You have to convert your file that the date matches this format (BTW: I found this out by using the find - export feature; it may depend on a local configuration.)
Cheers
Andreas
Ferdinand Gassauer wrote:

Thanks

what is the format of the Date field in the csv file ?

My Date is date and not datetime. 

Andreas Luedeke wrote:
Hi Ferdinand,
and that is exactly what happens when you import a csv file with a date field:
the creation date ($entry time) of the imported entries will be used from the "Date" column in the file.
I've just tried it and it works like a charm. Did you have any problems doing it?
Cheers
Andreas
Ferdinand Gassauer wrote:

I have to import a csv with a date field, which represents the creation date

this date should be used as "date" timestamp which is set automatically, otherwise all entries get the current datetime as timestamp

 

 

 

 

ELOG V3.1.5-3fb85fa6