Hi,

  We have been using Elog successfully as a shiftlog book for over a month 
now, but I recently ran into an annoying bug, I think.
  We had a thread that was created and was being replied to over several 
days.  We first replied to the original thread and then each subsequent 
reply was a reply of the previous reply.  When the thread reached above 13 
of these, the elogd.exe would crash everytime a user attempted to select 
the logbook that contained the enormous thread.  
  I found the only workaround was to manually delete the offending entry 
from the log file and to instruct my users to not reply to replies unless 
absolutely necessary.  I have been able to replicate this error across the 
rest of my logbooks as well.  If there is any more information you may 
need, please feel free to contact me.

Thanks,
Chris Jones

>   We have been using Elog successfully as a shiftlog book for over a month 
> now, but I recently ran into an annoying bug, I think.
>   We had a thread that was created and was being replied to over several 
> days.  We first replied to the original thread and then each subsequent 
> reply was a reply of the previous reply.  When the thread reached above 13 
> of these, the elogd.exe would crash everytime a user attempted to select 
> the logbook that contained the enormous thread.  
>   I found the only workaround was to manually delete the offending entry 
> from the log file and to instruct my users to not reply to replies unless 
> absolutely necessary.  I have been able to replicate this error across the 
> rest of my logbooks as well.  If there is any more information you may 
> need, please feel free to contact me.

Sorry my late reply, I was pretty busy these days...

I tried to reporduce your problem, but without success. Have a look at

http://midas.psi.ch/elogdemo/Linux/32

where I replied 20 times producing a very long thread without any problem. So 
can you reproduce your problem? I suspect that there was some other problem, 
since the number of replies is internally not limited in any way. If you 
again get into a situation where elodg.exe crashes on the *DISPLAY* of some 
message, you can send me the offending file xxxxxxa.log directly by email and 
I can analyze it. Only if I can reproduce a problem, I can fix it.

- Stefan

I found a stack overflow if there are too many replies. This has been fixed in 
the current CVS verson of elogd.c and will be incorporated into the next release.

> I found a stack overflow if there are too many replies. This has been fixed in 
> the current CVS verson of elogd.c and will be incorporated into the next release.

Many thanks for your quick reply to this issue.  I have also noticed that when 
moving a log entry that contains as few as 4 replies to replies with the "Move to" 
command that the elog server will crash.  I ran into this issue many times when I 
created a new logbook and was trying to move some of the longer threads into it.  
Please let me know if you would like me to send some sample entries from our 
logbook that illustrate this.

Thanks,
Chris    

Heya, I've been using elog for a year or so, with a proxy through Apache,
but recently I've ran into some trouble with my Apache config, where
spammers were using my incorrectly configured proxy to send spam.

I have
some requests for the Administrator's Guide: "Running elogd under Apache". 
I'm hoping a few little notes will save others the trouble I've gone
through. Neither of these are any fault of elog's or Apache's, but of my own
ignorance. (I am using elog 2.3.9, and Apache 2.something, if that matters)

1) When doing "ProxyPass ..." when setting up elog under Apache, do NOT put
"ProxyRequests On".  This is not needed, if it is enabled and not set up
correctly, it allows spammers to send spam via Apache's proxy.  More
information on this is here: http://www.apacheweek.com/issues/03-07-25,
about halfway down the page, under "Spammers use open Apache proxies"

Even though it doesn't mention ProxyRequests in the guide, I think there
should be a little side note mentioning that "ProxyRequests On" is NOT
needed, because I put it in, thinking it was - I am probably not the only one.

2) I have found that mod_proxy_http.c must be loaded in addition to
mod_proxy.c and mod_alias.c for the proxy to work, otherwise I get a 403
error.  I think this should be mentioned as well.

Thanks, I added a note into the admin guide.

impossible to create the moptions with 

-a Type#0="%D1%"
-a Itel#0="%zItel%"

the variable are set to 
set D1=Tel
set zItel=Tel.gif

other standard option work fine

does anybody has good experience with elog.exe command ?

elog -h 'my site elo' -p 83 -l 'my logbook' -a Phone="%2" -a Contact="%3 %
4" -a Type#0="%D1%" -a Cat="%5" -a Itel#0="%zItel%" "%6 %7 %8 %9"


----------------------------- here are the config in elog
[titiPHONE]
Comment = PhoneList 
Find menu text = menu/titiphone_top.html

Data dir = prive_Etienne/PhoneList
Guest Menu commands = Help
Find Guest Menu Commands = Help
Attributes = Phone, Itel, Dossier, Ext_direct, Societe, Contact, Cat,Type, 
Prive, Email, Adress, City, Relation, By

Quick filter = Itel,Type,Dossier,Date,Prive
Roptions Prive = no,CD,EC,MD,NB,TR,TV,AH,NW,JW,Manon

IOptions Itel = Tel.gif, TelDirect.gif, Fax.gif, Gsm.gif, Tel2.gif, 
TelHome.gif,TelFax.gif,TelHelp.gif
ROptions Type = Tel,TelDirect,Fax,Gsm,Tel2,Home,Combine,TelHelp

Preset Itel = Tel.gif
Preset Type = Tel
Preset Prive = no
Preset Email = 
Display mode = Summary
Thread Icon = Itel
Thread display = $Phone,$Contact,$Dossier,$Societe($Type/$prive)

> impossible to create the moptions with 
> 
> -a Type#0="%D1%"
> -a Itel#0="%zItel%"
> 
> the variable are set to 
> set D1=Tel
> set zItel=Tel.gif
> 
> other standard option work fine

Sure it works. But in your elogd.cfg, you have ROptions, not MOptions! I 
changed this to 

...
IOptions Itel = Tel.gif, TelDirect.gif, Fax.gif, Gsm.gif, Tel2.gif, 
TelHome.gif,TelFax.gif,TelHelp.gif
MOptions Type = Tel,TelDirect,Fax,Gsm,Tel2,Home,Combine,TelHelp
...

Then I added a batch file elog_submit.bat with following contents:

elog -h 'my site elo' -p 83 -l 'my logbook' -a Phone=%1 -a Contact="%2 %3" -a 
Type#0="%TYPE% -a Cat="%4" -a Itel#0="%ITEL%" %5 %6 %7

Then I made a 

set TYPE=Tel
set ITEL=Tel.gif

and a 

elog_submit 123 a b CAT Test Message

ans all worked fine. Please change your ROptions to MOptions and try again.

I am getting the following errors when trying to install elog-2.3.9 on
my FreeBSD box. I am running FreeBSD 4.5-RELEASE.

Many thanks!

"Makefile", line 21: Missing dependency operator
"Makefile", line 27: Need an operator
"Makefile", line 29: Missing dependency operator
"Makefile", line 31: Need an operator
make: fatal errors encountered -- cannot continue


You4eea

Unfortunately I don't have access to a FreeBSD box so I cannot try. But I 
thought the GNU make is the same on Linux and FreeBSD??? 

Has anybody successful compiled under FreeBSD?

- Stefan

I got elog 2.3.9 running on FreeBSD 5.1 successfully,
I compiled elog on a redhat box and then just copied over all the files to 
the FreeBSD box and ELOG just ran with no issues.
It's been running under heavy use for at least a month now.

PS: you might need the linux compatibility package installed on BSD though...


> I am getting the following errors when trying to install elog-2.3.9 on
> my FreeBSD box. I am running FreeBSD 4.5-RELEASE.
> 
> Many thanks!
> 
> "Makefile", line 21: Missing dependency operator
> "Makefile", line 27: Need an operator
> "Makefile", line 29: Missing dependency operator
> "Makefile", line 31: Need an operator
> make: fatal errors encountered -- cannot continue
> 
> 
> You4eea

> I got elog 2.3.9 running on FreeBSD 5.1 successfully,
> I compiled elog on a redhat box and then just copied over all the files to 
> the FreeBSD box and ELOG just ran with no issues.
> It's been running under heavy use for at least a month now.

FYI- the default "make" on FreeBSD is BSD, not GNU.

The easiest way to build elog on FreeBSD is to install "gmake" (via the port or
package) and type "gmake".  That's all it took for me to build a freshly
downloaded copy on 5.1 not 5 minutes ago.

Thanks for that mate, compiled elog on FreeBSD 5.1 myself no problems just like 
you said, great!

> 
> FYI- the default "make" on FreeBSD is BSD, not GNU.
> 
> The easiest way to build elog on FreeBSD is to install "gmake" (via the port or
> package) and type "gmake".  That's all it took for me to build a freshly
> downloaded copy on 5.1 not 5 minutes ago.

I would very much like to list groups instead of the individual logs on the
firs page you see after login.

Is there a way to do this? 

> I would very much like to list groups instead of the individual logs on the
> firs page you see after login.
> 
> Is there a way to do this? 

What would you like to see exactly?

a) Only groups. When you click on a group, you are taken to the first logbook 
in that group

b) Only groups. When you click on a group, a secondary page shows up showing 
a logbook selection page from that group

c) Two colums: First column group, second colum logbook, a bit like a 
directory structure like:

  Demo
    Linux
    Database
  Discussion
    Forum
    Archive
    Config Examples
    Contributions

Other uses might also vote...

- Stefan

I think I would like: Only groups. When you click on a group, a secondary page
shows up showing logs in that group. 

I would also have the option to list all logs so you could see logs that are not
in a group or locate a log where you didn't know what group it was in. I would
also like to have the option to sort logs and groups.

I am using Elog to keep track of application servers. The log names are the server
names and they are grouped by application. The list on the first page is getting
very long.

> I think I would like: Only groups. When you click on a group, a secondary page
> shows up showing logs in that group. 
> 
> I would also have the option to list all logs so you could see logs that are not
> in a group or locate a log where you didn't know what group it was in. I would
> also like to have the option to sort logs and groups.
> 
> I am using Elog to keep track of application servers. The log names are the server
> names and they are grouped by application. The list on the first page is getting
> very long.

Before I go and implement additional features, I would like to check if your problem 
cound not be solved easier. Whey don't you define your server as an attribute inside 
a logbook instead of having separate logbooks for each server? You know that you can 
sort by attributes (just by cliking on the column header for that attribute), so that 
would satisfy your need for sorting.

OK, I'm willing to give a shot but I don't know how to do it. I'll look in the docs and
see if I can figure it out.  Thanks.
 
> Before I go and implement additional features, I would like to check if your problem 
> cound not be solved easier. Whey don't you define your server as an attribute inside 
> a logbook instead of having separate logbooks for each server? You know that you can 
> sort by attributes (just by cliking on the column header for that attribute), so that 
> would satisfy your need for sorting.

I don't see anyway to define a log as an attribute. May be I just don't understand
something. I have more than 50 logs anyway.

Sorting is not something I have to have but it would make the servers names a little easier
to find. However, I can get them into any order I want buy rearranging them in the config
file. I've already done that for some of them. 

Groups on the front page would make navigation easier but it really isn't necessary.

I was hoping their was a way to do this that I had overlooked.


> OK, I'm willing to give a shot but I don't know how to do it. I'll look in the docs and
> see if I can figure it out.  Thanks.
>  
> > Before I go and implement additional features, I would like to check if your problem 
> > cound not be solved easier. Whey don't you define your server as an attribute inside 
> > a logbook instead of having separate logbooks for each server? You know that you can 
> > sort by attributes (just by cliking on the column header for that attribute), so that 
> > would satisfy your need for sorting.

> I don't see anyway to define a log as an attribute. May be I just don't understand
> something. I have more than 50 logs anyway.

What I meant was having only one logbook, and having the server as an attribute like

Attributes = Server, Type, ....
Options Server = Server1, Server2 (just the names of your current logbooks)
...

If you have already 50 logbooks this would require quite some work of course, but it might 
something for the future. I don't know if this fits into your requirements. If not, please 
let me know your complete scheme (current attributes and logbooks), then I can think about.

i work on Windows2000

part of my elog.cfg:

    Passwort file = c:\elog\passwd.txt
    Self register = 1
    Guest user commands = config, admin, logout

file system:

    - i created an emty file with name passwd.txt

problem:

    - if i use the link "Register as new user" on login, it does not work.
    - if i login as guest user and choose the menu config, it only 
    display  the attributes Login_name, Full_name and Email.    
    So i kann not create user.

what should i do ?
what are my mistakes ?

Can you attache as sample password file ?

in Unix:
i fixed the problem by defining a password file entry like 'user1::::'. 
then i defined 'admin user = user1' in elogd.cfg.
then i connected with login name 'user1' and created new user (as admin).

in Windows2000:
if i do this steps and i save the new user, it fails. the server service 
crash down.



> i work on Windows2000
> 
> part of my elog.cfg:
> 
>     Passwort file = c:\elog\passwd.txt
>     Self register = 1
>     Guest user commands = config, admin, logout
> 
> file system:
> 
>     - i created an emty file with name passwd.txt
> 
> problem:
> 
>     - if i use the link "Register as new user" on login, it does not work.
>     - if i login as guest user and choose the menu config, it only 
>     display  the attributes Login_name, Full_name and Email.    
>     So i kann not create user.
> 
> what should i do ?
> what are my mistakes ?
> 
> Can you attache as sample password file ?

> i work on Windows2000
> 
> part of my elog.cfg:
> 
>     Passwort file = c:\elog\passwd.txt
>     Self register = 1
>     Guest user commands = config, admin, logout
> 
> file system:
> 
>     - i created an emty file with name passwd.txt
> 
> problem:
> 
>     - if i use the link "Register as new user" on login, it does not work.
>     - if i login as guest user and choose the menu config, it only 
>     display  the attributes Login_name, Full_name and Email.    
>     So i kann not create user.
> 
> what should i do ?
> what are my mistakes ?
> 
> Can you attache as sample password file ?

Dear Friend!,

Only mistake in your file .cfg is   spell mistake "Passwort" in "Passwort 
file = c:\elog\passwd.txt" line. It should "Password file" t=d. 

try some thing like below,

[Log]
Theme = default
Comment = Financial Accounting Bug posting 
Attributes = Resource, Project Name, Task Desc, SDT, EEDT, ACDT, Percent WC, 
Status 
Options Type = Masters, Transactions, Reports
Options Category = Bug, New Feature, Client Requirement, Change
Required Attributes = Author, Type, Bug
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
Password file =D:\Program Files\ELOG\logpwd.txt
;Self register = 0
Self register = 1

Admin user =sridhar
Menu commands = Back, Login, New, Edit, config, Delete, Reply, Find, Help, 
Logout
Guest user commands = config, admin, Login, logout

Contribution available for all who wants to make SKIN for ELOG!

You are invited to benefit from this free info!

Just click on the "Contributions" tab to find the info (look for ID6).

Or... goto          http://midas.psi.ch/elogdemo/Contributions/6

Version 2.3.9 of elog has been released today. Enhancements are:

- Added options "Use Lock", "Title image"

- New "Email format" specifies what is sent exactly in an email 
notification. This may now include also attachments

- "Format <attribute>" lets you assign separate style sheet classes to each 
attribute, making the web display more powerful (see this forum, 
the "subject" uses a separate formatting). Note that this feature requires 
an update of the old "default.css" CSS file, if a elog version prior to 
2.3.9 is already installed on a system.

- "Execute new/edit/delete" lets one execute shell commands on the server 
side for new, edited or deleted messages. Since this can cause security 
problems, a new flag "-x" has been added to the elogd daemon to enable this 
feature. It can be used to synchronize the elog database with other 
databases, or to send SMS messages to people.

- New "Logging level" option gives enhanced logging capabilities, including 
read and write access logging to individual elog entries.

- The elog utility can now edit existing messages, and correctly quotes 
messages with "> " on replies.

A few small bugs have been fixed, refer to the ChangeLog for more details.

Can you give a syntax example of the Logging Level option ?



> Version 2.3.9 of elog has been released today. Enhancements are:
> 
> - Added options "Use Lock", "Title image"
> 
> - New "Email format" specifies what is sent exactly in an email 
> notification. This may now include also attachments
> 
> - "Format <attribute>" lets you assign separate style sheet classes to each 
> attribute, making the web display more powerful (see this forum, 
> the "subject" uses a separate formatting). Note that this feature requires 
> an update of the old "default.css" CSS file, if a elog version prior to 
> 2.3.9 is already installed on a system.
> 
> - "Execute new/edit/delete" lets one execute shell commands on the server 
> side for new, edited or deleted messages. Since this can cause security 
> problems, a new flag "-x" has been added to the elogd daemon to enable this 
> feature. It can be used to synchronize the elog database with other 
> databases, or to send SMS messages to people.
> 
> - New "Logging level" option gives enhanced logging capabilities, including 
> read and write access logging to individual elog entries.
> 
> - The elog utility can now edit existing messages, and correctly quotes 
> messages with "> " on replies.
> 
> A few small bugs have been fixed, refer to the ChangeLog for more details.

> Can you give a syntax example of the Logging Level option ?

Please refer to the documentation (http://midas.psi.ch/elog/config.html), I just 
updated it. "Logging Level = 3" is the maximum level which includes writes and 
reads.

Cheers

It appears Im having problems getting this to work, my config is as follows, yet 
its not updating the log file since i installed the new RPM 2.3.9, is there a 
problem or am I doing something wrong ?

Thanks in advance.

[global]
port = 81
Logbook dir = /data
Logbook Tabs = 1
Main Tab = Home
Page title = LogBook System
SMTP host = support.localnet
Logfile = /var/log/elogd.log
Logging level = 3
Resource dir = /usr/local/elog
Welcome title = <img src="logo.gif"><p><font size=4 color=white>Customer Relational 
Management System</font>
Page title = Customer Relational Management System
Bottom text = bottom.html
URL = http://172.16.24.108:81/

> > Can you give a syntax example of the Logging Level option ?
> 
> Please refer to the documentation (http://midas.psi.ch/elog/config.html), I just 
> updated it. "Logging Level = 3" is the maximum level which includes writes and 
> reads.

> It appears Im having problems getting this to work, my config is as follows, yet 
> its not updating the log file since i installed the new RPM 2.3.9, is there a 
> problem or am I doing something wrong ?

Oops, there was a bug. I added the resource directory in front of the logfile name, 
which is not correct if the logfile name contains an absolute path. I fixed that in 
the current CVS version. As a temporary fix, remove the resource dir in your elogd.cfg 
or remove the full path in the logfile (the file will the be put into the resource dir 
of course...).

> Version 2.3.9 of elog has been released today. Enhancements are:

Forgive me if I've missed it, but I've looked in the forum, on-line cfg docs 
and downloaded docs.  I cannot find details on how to the used 
the "Execute ..." command.  What is passed on command line, etc.

thanks in advance
mike
 
> - "Execute new/edit/delete" lets one execute shell commands on the server 
> side for new, edited or deleted messages. Since this can cause security 
> problems, a new flag "-x" has been added to the elogd daemon to enable this 
> feature. It can be used to synchronize the elog database with other 
> databases, or to send SMS messages to people.
>

> Forgive me if I've missed it, but I've looked in the forum, on-line cfg docs 
> and downloaded docs.  I cannot find details on how to the used 
> the "Execute ..." command.  What is passed on command line, etc.

Sorry, I forgot to put it into the documentation. It's now available from 
http://midas.psi.ch/elog/config.html You basically use "Execute new = 
<command>", where <command> can have substitutions like $<attribute>, 
$remote_host, etc. You also have to start elogd with the "-x" flag to enable 
shell executions, since they can impose a security problem (see documentation).