| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67611
|
Wed Nov 13 16:26:32 2013 |
 | Olaf Kasten | olaf.kasten@deutschebahn.com | Question | Linux | 2.9.2-1 | Re: kerberos authentication NOT working |
| Andreas Luedeke wrote: |
|
| 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.
⇄
English (auto-detected) » English
|
I'm having same issue. Kerberos is working on Apache on same ubuntu 12.04 server. I used the USE_KRB5 option for compiling elog.
Does anyone have an idea to solve that problem? |
|
67610
|
Wed Nov 13 16:11:18 2013 |
 | Hung Dao | hungtdao@yahoo.com | Question | Windows | 2.9.2 | Error when attempted to submit an entry | | One of my users reported that he received this error when attempted to submit an editing entry. Basically he is only one to edit this entry. When go ahead to press the button, the entry is updated successfully. What cause and how to prevent this error not to populate? Thanks |
|
67609
|
Wed Nov 13 14:41:07 2013 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Linux | 2.9.2-2475 | Re: date and time |
| Hal Proctor wrote: |
|
> [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?
https://midas.psi.ch/elogs/Forum/67405
Why all the > Characters? Maybe back off the version as stated in above link? Not sure about the date issue.
|
I don't know what happened here - I mean, I understand the ">" characters being added to the start of every line of a quoted previous entry, but now what then happened to the formatting.
By default in plain mode elog adds ">" to the start of every quoted line, just as quoting an email will do (some mailer programs).
If you're beyond your nteenth reply, word-wrapping of the browser etc makes past comments difficult to read. Of course it would be equally difficult in in html mode as the boxes would get more and more nested.
Not sure if your link here about html is relivent to the use of the ">" to indicate a quoted reply or not, although that wasn't really my question - which was about date format in the config file. |
|
67608
|
Wed Nov 13 14:27:34 2013 |
| Hal Proctor | hproctor2@gmail.com | Question | Linux | 2.9.2-2475 | Re: date and time | > [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?
https://midas.psi.ch/elogs/Forum/67405
Why all the > Characters? Maybe back off the version as stated in above link? Not sure about the date issue. |
|
67607
|
Wed Nov 13 13:36:48 2013 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Linux | 2.9.2-2475 | date and time | [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? |
|
67606
|
Thu Nov 7 08:08:12 2013 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Mac OSX | 2.9.2-2494 | Re: Compilation failure on Mac OSX 10.9 |
| A.G. Schubert wrote: |
|
| Stefan Ritt wrote: |
|
| A.G. Schubert wrote: |
|
When compiling elog on OSX 10.9 (Mavericks), I get the error below.
Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.
|
All over sudden gcc comes with its own version of "strlcpy", which I had defined "manually" since many years inside ELOG. Using -DFORTIFY_SOURCE=0 will not harm, so you can use it. The "real" solution is to take our ELOG's strlcpy/strlcat, which I did on the current SVN version.
Best regards,
Stefan
|
Ok, I tried updating my SVN working copy, but I didn't get any updates past elog rev. 2494, mxml rev. 74. I undid my changes to Makefile, tried to compile, but got the same errors.
I then pulled down elog and mxml with git, and these are working for me with no errors. Thanks!
|
SVN is obsolete and will NOT be maintained any more, since we completely switched to GIT. Actually I will disable the service soon. |
|
67605
|
Thu Nov 7 02:18:17 2013 |
| A.G. Schubert | alexis4@stanford.edu | Bug report | Mac OSX | 2.9.2-2494 | Re: Compilation failure on Mac OSX 10.9 |
| Stefan Ritt wrote: |
|
| A.G. Schubert wrote: |
|
When compiling elog on OSX 10.9 (Mavericks), I get the error below.
Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.
|
All over sudden gcc comes with its own version of "strlcpy", which I had defined "manually" since many years inside ELOG. Using -DFORTIFY_SOURCE=0 will not harm, so you can use it. The "real" solution is to take our ELOG's strlcpy/strlcat, which I did on the current SVN version.
Best regards,
Stefan
|
Ok, I tried updating my SVN working copy, but I didn't get any updates past elog rev. 2494, mxml rev. 74. I undid my changes to Makefile, tried to compile, but got the same errors.
I then pulled down elog and mxml with git, and these are working for me with no errors. Thanks! |
|
67604
|
Wed Nov 6 17:06:40 2013 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.9.2 | Re: Image attachments null in e-mails. Error log? |
| Daniel Campora wrote: |
|
Hi there :)
I'm having a problem with the e-mail notification on my installation of elog. I'm testing the attachment upload with images, and it seems to work seamlessly. However upon posting, the e-mail notification sends a null attachment, instead of the image I would expect.
Is there an error log I can check for this? I started the elog process without the daemon option, but I can't see any error coming up.
Cheers,
|
This problem has been fixed in the current version. Please get it from bitbucket.org. |
|