Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 277 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 ... 276, 277, 278 ... 804, 805, 806   Next  
ID Datedown Icon Author Author Email Category OS ELOG Version Subject
  67596   Fri Nov 1 21:47:12 2013 Question Mark CampbellCAMP2MAR@police.nsw.gov.auQuestionLinuxV2.9.2-245"Show only new entries" stuck for one user

 For one user in our ELog installation the "Show only new entries" button seems to be stuck on one particular date and time " ...

 

New entries since: Tue Oct 22 10:56:27 2013

 

this occurs with different browsers and PC's

For other users it works as described in this forum post ...

"When you are active browsing entries, your activity is recorded (only the time) in the password file. Now when you are inactive for more than one hour, you are considered "logged out", and your last activity is taken as a filter for new entries. That means you see new entries since your last activity in the logbook. " https://midas.psi.ch/elogs/Forum/1612

 

Regards

Mark.

  67595   Fri Nov 1 14:14:03 2013 Reply Hal Proctorhproctor2@gmail.comQuestionLinux2.9.2-1Re: kerberos authentication NOT working

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

  67594   Wed Oct 30 17:57:38 2013 Angy Fabio Sellagaia-gc@altecspace.itQuestionLinux2.9.2-1kerberos 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

 
⇄
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

  67593   Wed Oct 30 10:15:13 2013 Reply Alexander Nozikaltavir@gmail.comQuestionLinux2.9.2-2455Re: 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 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
Goto page Previous  1, 2, 3 ... 276, 277, 278 ... 804, 805, 806   Next  
ELOG V3.1.5-3fb85fa6