Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 276 of 806  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6445 Entries 
Goto page Previous  1, 2, 3 ... 275, 276, 277 ... 804, 805, 806   Next  
IDdown Date Icon Author Author Email Category OS ELOG Version Subject
  67592   Tue Oct 29 12:04:44 2013 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.9.2-2455Re: Attachment file names encoding

Alexander Nozik wrote:
Hello,
I am trying to move elog from old FreeBSD system to a new Ubuntu server and stuck with attachment encoding problem. The elog entries as well as attachments ашду тфьуы are mostly in koi8-r or cp1251 encoding. While it is relatively easy to configure log entries to display correctly, I still can't manage to deal with attachments. In old elog all attachments with Cyrillic file names are "not found" by elog web interface while files are present in the directory (though previous admin could have done something with the encoding).

If I am creating a new elog with default koi8-r charset, then new cyrrilic attachments are uploaded and displayed normally but after download the file name encoding is broken. Does elog do something with attachment name encoding?


You should be able to figure this out:
As an administrator you can have a look what are the real file names on the file system.
With your browser you can see what are the names of the attachment. Like in this forum, the entry https://midas.psi.ch/elogs/Forum/67571 has an attachment https://midas.psi.ch/elogs/Forum/131008_181353/import.xml
If the two match you don't have an encoding but some file system problem. If they don't match, then we are one step further in solving your problem Smile
Thought, the file name in the URL has to be URL encoded (see e.g. http://www.w3schools.com/tags/ref_urlencode.asp), which is of course different from the encoding of the file system.
  67591   Mon Oct 28 11:21:19 2013 Question Alexander Nozikaltavir@gmail.comQuestionLinux2.9.2-2455Attachment file names encoding
Hello,
I am trying to move elog from old FreeBSD system to a new Ubuntu server and stuck with attachment encoding problem. The elog entries as well as attachments ашду тфьуы are mostly in koi8-r or cp1251 encoding. While it is relatively easy to configure log entries to display correctly, I still can't manage to deal with attachments. In old elog all attachments with Cyrillic file names are "not found" by elog web interface while files are present in the directory (though previous admin could have done something with the encoding).

If I am creating a new elog with default koi8-r charset, then new cyrrilic attachments are uploaded and displayed normally but after download the file name encoding is broken. Does elog do something with attachment name encoding?
  67590   Thu Oct 24 12:09:29 2013 Question Andreas Luedekeandreas.luedeke@psi.chRequestAll2.9.2Import of entries from DOOCS eLogBook to ELOG
Hi everyone,
we have formerly used the DOOCS eLogBook from DESY for a couple of years for some application at our large
research facilities. Now we have standardized on ELOG and I've got a request to import the old DOOCS eLogBook
data into the new logbooks.
I've looked into it and the import appears to be fairly straight forward. I have two questions to the community,
before I start to program an import script:

1) Has anyone created such an import function already, and if the answer is yes, can I have it?

2) Would anyone else be interested in such a "cross logbook import", and if yes, what are your requirements?

Thanks
Andreas
  67589   Tue Oct 22 10:56:13 2013 Reply Barendoffice@amtc2.comBug reportWindows2.9.2Re: Importing XML/CSV

Andreas Luedeke wrote:

Barend wrote:

Andreas Luedeke wrote:

Barend wrote:
Hi Stefan,
I'm experiencing problems importing XML (.csv is not working at all for me).
My logbook contains 3 date-attributes besides the system DATE (entry time), date-format is defined as %d %b %y.
The XML file hold the date format "DD.MM.YYYY"
- During "preview" I see that all entries are listed.
- During the import I get the "wrong date format" error.
- When I review the Summary, I see that only the first XML entry (all 3 date-attributes hold a date) was imported.
- When I try to re-import the XML from the second entry (after removing the 1st entry from XML - this second entry hold NO date-value on one of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
- When I try to re-import the XML from the modified second entry (after removing the 1st entry from XML - this second entry holds date-value on all of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.

Any suggestion what could be wrong? Is it the missing date-value?

 Can you post your elog configuration file (elog.cfg)?

 
⇄
Detect language » English
 

 Hi Andreas,

I had to filter-out some other logbook. Please find attached the configuration section for the affected logbook "UMOWY".

Looking forward to your review.

Regards, Barend

Hi Barend,

I can confirm that this is a bug of the ELOG import function: if you have a field that is defined as type "date" or "datetime", then elogd requires the value of the field to be of a matching format.
It is not even allowed to omit the time in "datetime" format. If the field is not required in an entry, then it is therefore possible to create an entry that cannot be imported.
I've attached a minimal example elogd.cfg and XML import file to reproduce the problem.
I'm afraid you'll either need to wait for a patch, or you can add dummy dates for all your empty date fields in the XML import file. Just do a "replace all" with your favourite editor; in my example you would e.g. replace all "<D></D>" strings with "<D>01-01-1970</D>" before the import.
 
⇄
Detect language » English
 

Cheers, Andreas

 
⇄
Detect language » English
 
 
⇄
Detect language » English
 

 

Hi Andreas, Thanks for the reply. The suggested approach is workable, so I'll use that one. Regards, Barend
  67588   Tue Oct 22 10:54:51 2013 Reply Barendoffice@amtc2.comQuestionWindows2.9.2Re: Error: Attribute <date> not supplied.

David Pilgram wrote:

Barend wrote:

Stefan/Andreas,

When I reply to an existing Logbook entry, I get the error page "Error: Attribute Audit Date not supplied. Please go back and enter the Audit Date field."

The configuration file uses:

Required Attributes = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Fixed Attributes Reply = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Type Audit Date = date
Type Deadline = date
 

The combination "Required Attributes" and "Fixed Attributes Reply" does not work for date-fields.

As soon as I disclose the date fields from either "Required Attributes" or "Fixed Attributes Reply" the error is no longer evident.

But I want the "Audit Date" and "Deadline" to entered during a new Record and they shall not be changed during a reply.

 

Is this a bug -or- do I have to change the configuration?

 

Thanks & regards, Barend

Hi Barend,

I can reproduce your point. 

I've found various work-arounds, but possibly the best one is to remove "Audit Date" and "Deadline" from the Required Attributes line.  True you won't get a warning saying that they were not entered for the first entry (if you didn't enter them, that is), but all subsequent replies run as you would want.

Another way is if you *preview* your entry, you can then submit it and that works.  This seems to work by bring up a different page where you can edit all those Fixed Attributes.  (I'm not sure that Preview is meant to do that, but it does and it's a work-around).

Or, if you remove "Audit date" and "Deadline" from the Fixed Attributes Reply (as you did) seems to work in the same way.  But I see that you don't want the opportunity for these to be changed.

I note that if you get this error message and go back, the message that you may have written is erased (this is unusual, it doesn't do this if you have not supplied an attribute on the first entry, say).

 

So I suspect this is a bug, possibly not detected before; perhaps no-one had tried this combination.

 

Hi David, Thanks for the reply. I'll review the options and decide what is the best option to move forward. Regards, Barend
  67587   Thu Oct 17 14:27:56 2013 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.8.0Re: automated email notification did not work for me

Oliver Kirsebom wrote:

Stefan Ritt wrote:

Jianglai Liu wrote:

Hi,

I am setting up an elog to organize my lab activities. I installed elog 2.8.0 on the latest CentOS 5.5, 32 bit. I got into trouble setting up the automated email notification.

According to the elog manual, I setup the smtp setting in the elogd.cfg as follows:

SMTP host = smtp.gmail.com
SMTP username = jianglai.liu
 

I then used "elogd -t" to encode the password into the configuration file.

But when I submit an entry, I always received: "Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. y17sm867489wfd.15"

If I switched to use my university email servers, similar things happened.

SMTP host = smtp.sjtu.edu.cn
SMTP username = jianglai.liu

I got "Error sending Email via "smtp.sjtu.edu.cn": 5.7.8 Error: authentication failed: another step is needed in authentication"

I also switched to use one of my old work server

SMTP host = smtp-server.its.caltech.edu
SMTP username = jliu

and ended up with the same error message.

I did a google search on this without much progress. I would appreciate it very much if someone could shed light on how do I fix this.

Thanks much!

elog only supports basic authentication, not TLS or SSL. These days more and more SMTP servers require this however. I will put this on my to-do list. In meantime you can maybe configure your CentOS machine acting as an SMTP server, and then not using TLS or SSL there. That's what most people do.

 Hi, has this problem been fixed? (i.e does ELOG now support TLS or SSL?) Thanks, Oliver

Didn't have time yet for this. 

  67586   Thu Oct 17 14:23:06 2013 Reply Oliver Kirsebomoliver.kirsebom@gmail.comQuestionLinux2.8.0Re: automated email notification did not work for me

Stefan Ritt wrote:

Jianglai Liu wrote:

Hi,

I am setting up an elog to organize my lab activities. I installed elog 2.8.0 on the latest CentOS 5.5, 32 bit. I got into trouble setting up the automated email notification.

According to the elog manual, I setup the smtp setting in the elogd.cfg as follows:

SMTP host = smtp.gmail.com
SMTP username = jianglai.liu
 

I then used "elogd -t" to encode the password into the configuration file.

But when I submit an entry, I always received: "Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. y17sm867489wfd.15"

If I switched to use my university email servers, similar things happened.

SMTP host = smtp.sjtu.edu.cn
SMTP username = jianglai.liu

I got "Error sending Email via "smtp.sjtu.edu.cn": 5.7.8 Error: authentication failed: another step is needed in authentication"

I also switched to use one of my old work server

SMTP host = smtp-server.its.caltech.edu
SMTP username = jliu

and ended up with the same error message.

I did a google search on this without much progress. I would appreciate it very much if someone could shed light on how do I fix this.

Thanks much!

elog only supports basic authentication, not TLS or SSL. These days more and more SMTP servers require this however. I will put this on my to-do list. In meantime you can maybe configure your CentOS machine acting as an SMTP server, and then not using TLS or SSL there. That's what most people do.

 Hi, has this problem been fixed? (i.e does ELOG now support TLS or SSL?) Thanks, Oliver

  67585   Wed Oct 16 16:53:55 2013 Idea Andreas Luedekeandreas.luedeke@psi.chBug reportWindows2.9.2Re: Importing XML/CSV

Barend wrote:

Andreas Luedeke wrote:

Barend wrote:
Hi Stefan,
I'm experiencing problems importing XML (.csv is not working at all for me).
My logbook contains 3 date-attributes besides the system DATE (entry time), date-format is defined as %d %b %y.
The XML file hold the date format "DD.MM.YYYY"
- During "preview" I see that all entries are listed.
- During the import I get the "wrong date format" error.
- When I review the Summary, I see that only the first XML entry (all 3 date-attributes hold a date) was imported.
- When I try to re-import the XML from the second entry (after removing the 1st entry from XML - this second entry hold NO date-value on one of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
- When I try to re-import the XML from the modified second entry (after removing the 1st entry from XML - this second entry holds date-value on all of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.

Any suggestion what could be wrong? Is it the missing date-value?

 Can you post your elog configuration file (elog.cfg)?

 
⇄
Detect language » English
 

 Hi Andreas,

I had to filter-out some other logbook. Please find attached the configuration section for the affected logbook "UMOWY".

Looking forward to your review.

Regards, Barend

Hi Barend,

I can confirm that this is a bug of the ELOG import function: if you have a field that is defined as type "date" or "datetime", then elogd requires the value of the field to be of a matching format.
It is not even allowed to omit the time in "datetime" format. If the field is not required in an entry, then it is therefore possible to create an entry that cannot be imported.
I've attached a minimal example elogd.cfg and XML import file to reproduce the problem.
I'm afraid you'll either need to wait for a patch, or you can add dummy dates for all your empty date fields in the XML import file. Just do a "replace all" with your favourite editor; in my example you would e.g. replace all "<D></D>" strings with "<D>01-01-1970</D>" before the import.
 
⇄
Detect language » English
 

Cheers, Andreas

 
⇄
Detect language » English
 
 
⇄
Detect language » English
 
Attachment 1: elogd.cfg 
[global]
port = 8080

[TestXmlImportOfDate]
Attributes = D
Type D = date
Attachment 2: imp.xml 
<?xml version="1.0" encoding="ISO-8859-1"?>
<ELOG_LIST>
	<ENTRY>
		<MID>1</MID>
		<DATE>Mon  07 Oct 2013 11:41:42 +0200</DATE>
		<ENCODING>plain</ENCODING>
		<D>20.10.2012</D>
		<TEXT>ABCD</TEXT>
	</ENTRY>
	<ENTRY>
		<MID>2</MID>
		<DATE>Mon  07 Oct 2013 11:41:43 +0200</DATE>
		<ENCODING>plain</ENCODING>
		<D></D>
		<TEXT>DEF</TEXT>
	</ENTRY>
</ELOG_LIST>
Goto page Previous  1, 2, 3 ... 275, 276, 277 ... 804, 805, 806   Next  
ELOG V3.1.5-3fb85fa6