Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 666 of 807  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subject
  1201   Sat Jun 18 23:14:51 2005 Question Paul Paquettepaquettep@gmail.comQuestionWindows V2.5.4prevent CVS and XML exports
Hello All and Happy Father's Day,

How do I prevent Anonymous Users from exporting the Data when using the search funtion?

Thank You

Paul
  1200   Fri Jun 17 22:54:39 2005 Question Stefan Rittstefan.ritt@psi.chQuestionLinux2.6 betaRe: Unable to send mails through elog

Kumar wrote:
Hi All

I need to send mail through Elog. With Version 2.5.7 it seems to work only when less content is in the elog entry. But when I fill in a lot of content into one entry, it confirms the mail is sent but I dont receive the mail.

I thought it was a bug in 2.5.7, so I installed the new version 2.6-beta. With this version I am not even able to send any mail eventhough elog confirms it has been sent. Same is it case for 2.5.9.

Please let me know if there is a fix..

Thanks
Raj


This must have to do with your specific SMTP server. What you can do is to start elogd with the verbose flag like
elogd -v

then send an email entry and watch the communication between elogd and the SMTP server. There must be some kind of error message.
  1199   Fri Jun 17 22:37:59 2005 Entry Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.0-betaRe: Menu text ignored??

Emiliano Gabrielli wrote:
uh oh ... just maked some tests before posting ... "Find Menu text" does my job !!!?!?!!!! why "Find" in the name? it is displayed in the list view, not Find ... Am I completely out?


Well, the normal list view was not there from the beginning. Originally you always saw the last entry, and had to click on "Find", do a search and then see the listing. Only later this became the default view. So "Find Menu text" was there from the beginning, and some people used it. If I change it now to "List Menu text", guess how many people would complain that their config file doen not work anymore.

Well, maybe I should allow both options "Find menu text" and "List menu text", change it in the documentation, and in a year from now remove the "Find menu text".
  1198   Fri Jun 17 22:33:29 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.5.9Re: elog crashes when admin tries to register new users

Heiko Scheit wrote:
The following appended after the base (!) URL results in a segmentation fault
?cmd=Activate&new_user_name=test1&new_full_name=Test1

It works fine, if a specific logbook is given. So
http://my.ho.st/?cmd=Activate&new_user_name=test1&new_full_name=Test1
is not OK, while
http://my.ho.st/myLogBook/?cmd=Activate&new_user_name=test1&new_full_name=Test1
is OK.


Thanks for that info. It helped me debugging things. The problem is that the "activation" URL does not contain a logbook if there is a global password file. I have never tried that so of course it crashes Crying

I tried to fix this and committed the changes to CVS. Can you try with that version?
  1197   Fri Jun 17 22:08:28 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0Re: Cloning

Gerfried Kumbartzki wrote:
The elogd.cfg has a read and write passwd set. Any user can access the logbook, read and write after providing the proper user id and password.


This might be your problem. Try to temporarily remove the read and write password from you config file, then do the cloning, then put it back. Cloning works with a passowd file, but I haven't tested it with read/write passwords.


Gerfried Kumbartzki wrote:
Beside missing the real stuff everything ends up in the users home directory. I would like it in the general area (/usr/local/elog for instance).


The cloning works in the current directory. So just go to /usr/local/elog and start "elogd -C ..." from there. Alternatively, copy your whole /usr/local/elog tree to the server manually. The "Synchronize" button then works again only with a password file. You need a "Mirror user = xxx" option in that case.
  1196   Fri Jun 17 20:30:53 2005 Question Gerfried Kumbartzkikum@physics.rutgers.eduQuestionLinux2.6.0Cloning
Elog is installed on a laptop (Redhat Linux 2.4.20-8) for quite a while. I like to have a "base" of that logbook on a server and keep it
in sync. Mirroring seem to be the perfect solution. For that I updated to elog v2.6.0 yesterday.

The server is an Alpha running Linux Redhat 7.1. I compiled from elog-latest.tar and installed elog in the 'same' locations as on the laptop.
Created a user elog and a group elog, put elogd.cfg, themes, logbooks ... in /usr/local/elog, owned by elog. Started the elogd, tested,
all seems to work. The elogd.cfg has a read and write passwd set. Any user can access the logbook, read and write after providing the proper user id and password.
Next I wanted to clone the logbooks from the laptop to the server. As superuser I can start elogd -v -C http://latop:8080, but get stuck right away with "Cannot contact elogd at http://laptop:8080/"
As user it works as follows:

Remote configuration successfully received.

Option "Mirror server = http://wotan.rutgers.edu:8080" added to config file.
Logbook directory "logbooks" successfully created.
Created directory "demo"
Indexing logbook "demo" ... Found empty logbook "demo"
Created directory "tfexp"
Indexing logbook "tfexp" ... Found empty logbook "tfexp"

Retrieve remote logbook entries? [y]/n:

Retrieving entries from "http://wotan.rutgers.edu:8080/demo"...
ID1: Remote entry received

Retrieving entries from "http://wotan.rutgers.edu:8080/tfexp"...
Error accessing remote logbook

Cloning finished. Check elogd.cfg and start the server normally.

Allthough, tfexp contains a number of entries all owned by elog like the entry in demo.
Beside missing the real stuff everything ends up in the users home directory. I would like it in the general area (/usr/local/elog for instance).

The other option is to use synchronize after changing [global] from with in the browser. Start elogd, open the logbook and click on config,
enter a Mirror server = http://laptop:8080/
Clicking synchronize give "Error accessing remote logbook"

Again, the logbooks are on both machines in /usr/local/elog/logbooks (owner:group elog:elog). The tfexp in this case is passwd protected.
Any user can access the elogs in both machines, locally or remote. But, I'm unable to synchronize the two.
Maybe somebody can point me in the right direction.

Thank's Gerfried
  1195   Thu Jun 16 22:37:06 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.5.9Re: reverse sort option does not work for quick filter
I finally found some time to fix this problem. The fix is under CVS.
  1194   Wed Jun 15 18:59:23 2005 Reply Charles DuncanCharles@YorkU.CAQuestionLinux Re: Moving eLog from Server to Server...

Charles Duncan wrote:

Charles Duncan wrote:

Quote:

Stefan Ritt wrote:

Charles Duncan wrote:
I am moving my eLog system from one server to another.
I moved all my log books, my /etc/elog.conf, and /usr/share/elog/elog.pwd file. Did I miss anything?
The Logbooks come up fine on the eLog list, but when I try to access them I get invalid user name...
Do I have to do some sort of conversion to move the pwd file from one server to another?
Or should I try using the sync command for the move? does sync also move the pwd file??


Of course you have to start elogd after you copied all files over, but I presume you did that. The
password file itself does not need any conversion, it should work on both hosts fine. Cloning an elog logbook
(via the "-C <url>") flag, does copy the password file if you enter "yes" to the according question. Have you
checked the file permission of the password file? Maybe the user name elogd is running under has no read access
to it.


I reinstalled elog on the new server and ran the clone (via the "-C <url>"), wow that is really slick. But unfortunately my passwords and user data were not transfered. I did say 'Y' when prompted to transfer the password info.

I think my problem is that one server is running 2.5.9 (or 2.6.0 beta, unstable, Debian) and my new server is running 2.5.5.3 (stable, UBUNTU).

Are the password files not compatible between the 2 versions?

All my logbook entries appear to be there in full.

btw: I am back leveling to 2.5.5.3 because I lose my last column on every log book view.


I wanted to add that the elog.pwd file did transfer when I used the "elogd -C <url>" command, but the passwords and accounts were not recognized. Also I edited my elog.conf file to contain the absolute address of my elog.pwd file.


I fixed it... I merely backed out of the XML format of the elog.pwd and reverted to common passwd format. Everyone can log in now... great product.
ELOG V3.1.5-3fb85fa6