ELOG Forum

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

67594

Wed Oct 30 17:57:38 2013

Fabio Sella

gaia-gc@altecspace.it

Question

Linux

2.9.2-1

kerberos authentication NOT working

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

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

67593

Wed Oct 30 10:15:13 2013

Re: Attachment file names encoding

Thank you for reply.

I am not very experienced linux user so it could be a problem with the file system. Let me just describe what I do and what I see as a result.

I created a new elog just for the testing purpose, it has "Charset = koi8-r" line in the config file. Than I post a new entry to this elog with russian text and a file with russian file name from windows (so I expect that charset is cp1251). Now I open this entry. The text is fine and the filename is fine on the page (the same russian text I expect to see), but when I try to download it, the actual file name is broken and to restore it I need koi8-r -> cp1252 transformation. The file itself is readable.
If I look in the actual logbook directory, then in the entry file the file name is readable (entry file encoding is koi8-r), but the attachment file name contains many "?" and not readable by file system.

So first my question is what happened to the file name incoding in a logbook directory, and the second one: what should I do to make attachments download as they were uploaded?

Thank you in advance.

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.

67591

Mon Oct 28 11:21:19 2013

Attachment file names encoding

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

67589

Tue Oct 22 10:56:13 2013

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

Cheers, Andreas

�

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

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

Goto page Previous 1, 2, 3 ... 276, 277, 278 ... 804, 805, 806 Next

ELOG V3.1.5-3fb85fa6