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.
 

 I have downloaded a latest version.  It has displayed the new version as ELOG V2.9.2-bac715d where seems defined in GIT_REVISION as I guess.  Then I set Bottom Text Login to a html file, it still shows those unwanted characters.

Okay, why don't you just remove the unwanted characters from the html file? Because the attached file contains exactly those characters.

Yes, unwanted characters are in my file.  In fact, they are not visible under some editor.  So, I have found a reference from this site http://www.ventrino.com/blog/60/2008/07/three-little-characters-i%C2%BB%C2%BF-designed-to-make-your-life-hell/ about how to remove them.  Basically, file's properties has to set to either ASCII or Encode as UTF-8 without BOM.  Thanks.

We recently installed ELOG and it works pretty well, but the load times are rather inconsistent. Most of the time 
it is very fast, but it also often hangs for around 5-10 seconds while loading. It seems to affect all parts of 
the page that are returned at random, so sometimes the main html file will hang, sometimes the css file and 
sometimes the images.

The hardware it is running on is nothing special, an older 3 GHz Celeron, but it should be fast enough. It is 
running on Debian 7. 

Any ideas what the problem could be, or how I could investigate it further to find the bottleneck?

> We recently installed ELOG and it works pretty well, but the load times are rather inconsistent. Most of the time 
> it is very fast, but it also often hangs for around 5-10 seconds while loading. It seems to affect all parts of 
> the page that are returned at random, so sometimes the main html file will hang, sometimes the css file and 
> sometimes the images.
> 
> The hardware it is running on is nothing special, an older 3 GHz Celeron, but it should be fast enough. It is 
> running on Debian 7. 
> 
> Any ideas what the problem could be, or how I could investigate it further to find the bottleneck?

I'm not an expert in debugging web applications. Here are my two cent:
We once had a problem when we hosted very large logbooks (several 10 thousands of entries) that the server would run
out of real memory and was slowed down by swapping. Therefore my first idea would be to monitor the server: Is
the CPU load peaking? What happens with the memory consumption? Any other suspicious process running on the server?
But it could be as well a network or browser problem. Did you try different browsers?
Did you check the elogd log file?

> I'm not an expert in debugging web applications. Here are my two cent:
> We once had a problem when we hosted very large logbooks (several 10 thousands of entries) that the server would run
> out of real memory and was slowed down by swapping. Therefore my first idea would be to monitor the server: Is
> the CPU load peaking? What happens with the memory consumption? Any other suspicious process running on the server?
> But it could be as well a network or browser problem. Did you try different browsers?
> Did you check the elogd log file?

The logbook only has a few hundred entries, elogd is using only around 20-30 MB and there is enough free RAM. The load 
average for the server is around 0.2, elogd only uses 5% CPU at most when it is accessed and the CPU is idle most of the 
time. 

Strangely it happens mostly when using Chrome, and almost never with Firefox. I captured the network traffic, but I can't 
see anything unusual. It just takes very long until the answer is returned by the elogd server.

> > I'm not an expert in debugging web applications. Here are my two cent:
> > We once had a problem when we hosted very large logbooks (several 10 thousands of entries) that the server would run
> > out of real memory and was slowed down by swapping. Therefore my first idea would be to monitor the server: Is
> > the CPU load peaking? What happens with the memory consumption? Any other suspicious process running on the server?
> > But it could be as well a network or browser problem. Did you try different browsers?
> > Did you check the elogd log file?
> 
> The logbook only has a few hundred entries, elogd is using only around 20-30 MB and there is enough free RAM. The load 
> average for the server is around 0.2, elogd only uses 5% CPU at most when it is accessed and the CPU is idle most of the 
> time. 
> 
> Strangely it happens mostly when using Chrome, and almost never with Firefox. I captured the network traffic, but I can't 
> see anything unusual. It just takes very long until the answer is returned by the elogd server.

My tuppance worth.  I have noticed (firefox) that some attachments take rather longer than might be expected to upload.  I
originally thought this was the ghostview program processing say a pdf to make pngs etc, but have more recently started to
question that assumption.  No solution or much clue, just another observation.

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

> [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.

> [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

> > [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

Hi Andreas,

Thanks for this, I'll give the solution a go.  
I take the point that if it's a bug, other logbooks may be affected if it were fixed; but perhaps another
parameter - $thedate or something could be created instead?

Please read the documentation in https://midas.psi.ch/elog/config.html und the option "Use Lock". If you don't need locking, just turn it off.

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

 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

 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? 

 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 is one of the few exceptional cases where reading the documentation can actually help: https://midas.psi.ch/elog/config.html#global

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

https://midas.psi.ch/elog/config.html#global

 

You can turn on logging using the "Logfile=<filename>" command in the elogd.cfg configuration. With "Logging level=3" you see all elog access, but sending email is in the log anyway.

Some people reported that there is a problem if you don't have ImageMagick installed. So please install that package and try again.

Cheers,
Stefan 

This problem has been fixed in the current version. Please get it from bitbucket.org. 

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

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>

 Yah! It's working again ...

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