ELOG Forum

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)?

67585

Wed Oct 16 16:53:55 2013

Andreas Luedeke

andreas.luedeke@psi.ch

Bug report

Windows

2.9.2

Re: 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.

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.

Cheers, Andreas

67590

Thu Oct 24 12:09:29 2013

Andreas Luedeke

andreas.luedeke@psi.ch

Request

All

2.9.2

Import 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

67592

Tue Oct 29 12:04:44 2013

Andreas Luedeke

andreas.luedeke@psi.ch

Question

Linux

2.9.2-2455

Re: 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.

67597

Mon Nov 4 15:07:40 2013

Andreas Luedeke

andreas.luedeke@psi.ch

Question

Linux

2.9.2-1

Re: kerberos authentication NOT working

Hal Proctor wrote:

Fabio Sella wrote:

Hi guys,

we configured a kdc server using OPENLDAP as backend. We installed on it elog and configured the Kerberos Authentication on one logbook as follows:

Authentication = Kerberos, File
Kerberos Realm = TEST.COM
Password file = ./pwd.xml

⇄

Detect language » Italian

Even if the kinit comand is retrieving correctly a ticket for the user tsearch@TEST.COM(we see it using klist and tcpdump on lo interface), elogd kerberos authentication is not working.

We tried using tcpdump for troubleshooting but no traffic is generated on the loopback interface.

Did someone solve this problem or do you have an idea on how to make the kerberos authentication working?

Thanks

I have asked for same help, and no one has answered with a solution on implementing a kerberos . I saw exactly what you were seeing. (did you try fully qualifying the domain within the username field for logon? \\TEST.COM\username)

I still couldn't get it to work

Just my two cent:

- did you edit the Makefile to compile elogd with kerberos (USE_KRB5 = 1)?

- did you look into the elogd logfile for error messages at start-up or at login time?

I can only say that I got it working right away - that is the case when you learn least.

Maybe you should post your specific software versions: operating system (in my case Scientific Linux 5.1 (Boron)), Kerberos version (klist -V), etc.

67614

Thu Nov 14 11:19:12 2013

Andreas Luedeke

andreas.luedeke@psi.ch

> [13 Nov]
> As my threads have lots of replies, I end up with a forest of ">" characters which makes it difficult to read
> earlier quoted entries (what with word-wrapping of the browser).
> I thought to replace the ">"s by a simple date entry prepended to the start of each reply. - much as I have 
> given at the top of this initial entry.
> 
> So this is what I put in the config file:
> 
> ....
> Time format = %a %d %b %y
> Date format = %d %b
> Prepend on reply = [$date] \n
> ...
> 
> The time is used in the string for the Thread display.
> 
> Only I don't get the date, with the date format, prepended to replies but the time, in the time format, as
> 
> [Wed 13 Nov 13]
> 
> Now this is hardly a disaster, but any ideas why the date formatting is being ignored?

Hi David,
yes, a $date is substituted with the "Time format" in the function build_subst_list().
I guess that is a bug, but it could break many existing logbooks to change it.
I leave this to Stefan.

There is a simple solution for your problem: you can execute a shell command.

Prepend on reply = $shell(date '+[%d %b]') \n
Reply string =

That snipped will do exactly what you want :-) (of course you need to have the "-x" option to start elogd.)

Kind Regards
Andreas

67615

Thu Nov 14 11:31:23 2013

Andreas Luedeke

andreas.luedeke@psi.ch

Question

Windows

2.9.2

Re: Unwanted characters showing when using Bottom Text Login to a html file

Hung Dao wrote:

When using Bottom Text Login to a html file showing some unwanted characters. Also, the ELOG Version is longer displayed. Bottom Text Login = example.htm Attached are bottomtextlogin.jpg which shows the characters on the left and example.htm which I used.

I have a possible explanation for this problem, but it is just guess work. If I'm right, then just download the latest ELOG version and it will work properly again.

You've downloaded an elog version from git, which still contained the line 12 in elogd.c: char svn_revision[] = "$Id$";
Since you did checkout from git, the $Id$ was not substituted.
ELOG trys to extract the version by this:      rsprintf
          ("<center><a class=\"bottomlink\" title=\"%s\" href=\"https://midas.psi.ch/elog/\">ELOG V%s-%d</a></center>",
           loc("Goto ELOG home page"), VERSION, atoi(svn_revision + 13));
svn_revision + 13 is pointing into the void. Still I would have expected that you get a number as a result.

My advice: download again and retry.

Goto page Previous 1, 2, 3 ... 734, 735, 736 ... 794, 795, 796 Next

ELOG V3.1.5-2eba886