| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67601
|
Tue Nov 5 20:04:11 2013 |
 | Mark Campbell | CAMP2MAR@police.nsw.gov.au | Question | Linux | V2.9.2-245 | Re: "Show only new entries" stuck for one user |
| Mark Campbell wrote: |
|
| Mark Campbell wrote: |
|
| Stefan Ritt wrote: |
|
| Mark Campbell wrote: |
|
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.
|
Sure it will be stuck on a date/time, until you show "inactivity". So wait for >1h, and then check again. You will see the time updated.
/Stefan
|
Hi Stefan,
well I just logged on tonight after being "inactive" (away from work) for two days and the "Show only new entries" button is still stuck at "Tue Oct 22 10:56:27 2013".
Could it be that I am have left myself logged in on another machine somewhere?
How does ELog determine "activity"?
Regards
Mark.
|
I just had a look in the password file and found ...
<full_name>Mark Campbell</full_name>
<last_logout>Tue Oct 22 10:56:27 2013</last_logout>
<last_activity>Wed Nov 6 01:17:08 2013</last_activity>
<inactive>0</inactive>
So it appears that the <last_logout> tag is not being updated.
---------------------------------------------------
Some activity from the messages file ...
18-Oct-2013 15:52:12 [2003883@10.11.112.178] {ops} LOGOUT
21-Oct-2013 06:40:03 [10.17.48.165] {ops} LOGIN user "2003883" (attempt)
21-Oct-2013 06:40:04 [10.17.48.165] {ops} LOGIN user "2003883" (success)
22-Oct-2013 07:01:51 [10.17.48.176] {ops} LOGIN user "2003883" (attempt)
22-Oct-2013 07:01:51 [10.17.48.176] {ops} LOGIN user "2003883" (success)
22-Oct-2013 07:10:13 [2003883@10.17.48.176] {ops} LOGOUT
22-Oct-2013 13:26:32 [10.17.48.176] {ops} LOGIN user "2003883" (attempt)
22-Oct-2013 13:26:32 [10.17.48.176] {ops} LOGIN user "2003883" (success)
22-Oct-2013 14:13:16 [2003883@10.17.48.165] {ops} LOGOUT
23-Oct-2013 06:24:30 [10.17.48.165] {ops} LOGIN user "2003883" (attempt)
23-Oct-2013 06:24:30 [10.17.48.165] {ops} LOGIN user "2003883" (success)
25-Oct-2013 22:25:42 [10.17.48.90] {ops} LOGIN user "2003883" (attempt)
25-Oct-2013 22:25:42 [10.17.48.90] {ops} LOGIN user "2003883" (success)
25-Oct-2013 22:43:45 [2003883@10.17.48.90] {ops} LOGOUT
Regards
Mark.
|
Yah! It's working again ...
| New entries since: |
Wed Nov 6 01:51:02 2013
|
I found out I was still logged on to one workstation, I logged off from there, waited a few hours and tried again. All good.
Regards Mark |
|
67600
|
Tue Nov 5 15:25:59 2013 |
| Mark Campbell | CAMP2MAR@police.nsw.gov.au | Question | Linux | V2.9.2-245 | Re: "Show only new entries" stuck for one user |
| Mark Campbell wrote: |
|
| Stefan Ritt wrote: |
|
| Mark Campbell wrote: |
|
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.
|
Sure it will be stuck on a date/time, until you show "inactivity". So wait for >1h, and then check again. You will see the time updated.
/Stefan
|
Hi Stefan,
well I just logged on tonight after being "inactive" (away from work) for two days and the "Show only new entries" button is still stuck at "Tue Oct 22 10:56:27 2013".
Could it be that I am have left myself logged in on another machine somewhere?
How does ELog determine "activity"?
Regards
Mark.
|
I just had a look in the password file and found ...
<full_name>Mark Campbell</full_name>
<last_logout>Tue Oct 22 10:56:27 2013</last_logout>
<last_activity>Wed Nov 6 01:17:08 2013</last_activity>
<inactive>0</inactive>
So it appears that the <last_logout> tag is not being updated.
---------------------------------------------------
Some activity from the messages file ...
18-Oct-2013 15:52:12 [2003883@10.11.112.178] {ops} LOGOUT
21-Oct-2013 06:40:03 [10.17.48.165] {ops} LOGIN user "2003883" (attempt)
21-Oct-2013 06:40:04 [10.17.48.165] {ops} LOGIN user "2003883" (success)
22-Oct-2013 07:01:51 [10.17.48.176] {ops} LOGIN user "2003883" (attempt)
22-Oct-2013 07:01:51 [10.17.48.176] {ops} LOGIN user "2003883" (success)
22-Oct-2013 07:10:13 [2003883@10.17.48.176] {ops} LOGOUT
22-Oct-2013 13:26:32 [10.17.48.176] {ops} LOGIN user "2003883" (attempt)
22-Oct-2013 13:26:32 [10.17.48.176] {ops} LOGIN user "2003883" (success)
22-Oct-2013 14:13:16 [2003883@10.17.48.165] {ops} LOGOUT
23-Oct-2013 06:24:30 [10.17.48.165] {ops} LOGIN user "2003883" (attempt)
23-Oct-2013 06:24:30 [10.17.48.165] {ops} LOGIN user "2003883" (success)
25-Oct-2013 22:25:42 [10.17.48.90] {ops} LOGIN user "2003883" (attempt)
25-Oct-2013 22:25:42 [10.17.48.90] {ops} LOGIN user "2003883" (success)
25-Oct-2013 22:43:45 [2003883@10.17.48.90] {ops} LOGOUT
Regards
Mark. |
|
67599
|
Tue Nov 5 14:35:44 2013 |
| Mark Campbell | CAMP2MAR@police.nsw.gov.au | Question | Linux | V2.9.2-245 | Re: "Show only new entries" stuck for one user |
| Stefan Ritt wrote: |
|
| Mark Campbell wrote: |
|
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.
|
Sure it will be stuck on a date/time, until you show "inactivity". So wait for >1h, and then check again. You will see the time updated.
/Stefan
|
Hi Stefan,
well I just logged on tonight after being "inactive" (away from work) for two days and the "Show only new entries" button is still stuck at "Tue Oct 22 10:56:27 2013".
Could it be that I am have left myself logged in on another machine somewhere?
How does ELog determine "activity"?
Regards
Mark. |
|
67598
|
Tue Nov 5 13:40:58 2013 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | V2.9.2-245 | Re: "Show only new entries" stuck for one user |
| Mark Campbell wrote: |
|
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.
|
Sure it will be stuck on a date/time, until you show "inactivity". So wait for >1h, and then check again. You will see the time updated.
/Stefan |
|
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.
⇄
English (auto-detected) » English
|
|
67596
|
Fri Nov 1 21:47:12 2013 |
 | Mark Campbell | CAMP2MAR@police.nsw.gov.au | Question | Linux | V2.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 |
| Hal Proctor | hproctor2@gmail.com | Question | Linux | 2.9.2-1 | Re: 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 |
 | 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
⇄
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 |