Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 199 of 796  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSup ELOG Version Subject
  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.
  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?
  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".
  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.
  1205   Mon Jun 20 09:59:10 2005 Entry Emiliano GabrielliAlberT@SuperAlberT.itBug reportLinux2.6.0-betaRe: Menu text ignored??

Stefan Ritt wrote:

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


It's a great way to solve the misunderstanding IMHO, tnx Wink
  1206   Tue Jun 21 19:24:58 2005 Reply Heiko Scheith.scheit@mpi-hd.mpg.deBug reportLinux2.5.9Re: elog crashes when admin tries to register new users

Quote:

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?


Not really, unless you have a fixed 2.5.9 version. Version 2.6 has
way too many new features, which I don't want at the moment. Or is
there a config option to get the old behavior?

I also saw that the format of the email notification has changed. As
I have scripts (bash, akw, procmail) that depend on this format I
would need much more time than I currently have to actually test
everything.

Maybe you should consider supporting two branches, say 'stable' (2.5.9
currently) and 'experimental' (2.6 currently)? For 'stable' only
severe bugs and security issues are fixed and in 'experimental' new
features are introduced. What do you say?

For me the risk of upgrading to 2.6 now seems to high, as many people
depend on the logbook.
  1207   Tue Jun 21 19:38:06 2005 Reply Heiko Scheith.scheit@mpi-hd.mpg.deBug reportLinux2.5.9email flagged as spam

Heiko Scheit wrote:

I also saw that the format of the email notification has changed. As
I have scripts (bash, akw, procmail) that depend on this format I
would need much more time than I currently have to actually test
everything.


By the way, the emails I get from the forum are now all flagged as
spam. SpamAssassin is used and Spam-score header is

X-Spam-Score: 4.875 (****) ADDRESS_IN_SUBJECT, BAYES_00,HTML_40_50,
HTML_IMAGE_ONLY_24, HTML_MESSAGE, MIME_HEADER_CTYPE_ONLY,
MIME_HTML_ONLY, MSGID_FROM_MTA_HEADER, MSGID_FROM_MTA_ID,
NO_REAL_NAME, SPF_FAIL, SPF_HELO_PASS, TO_MALFORMED

Maybe you can see what the problem is.
  1209   Wed Jun 22 18:34:18 2005 Reply Gerfried Kumbartzkikum@physics.rutgers.eduQuestionLinux2.6.0Re: Cloning
Thank you for the suggestions; I commented the read and write passwd in elogd.cfg out and only then I was able to clone
(elogd -v -C http://laptop:8080) the logbook to the new server.
But this is only part of the story. The logbook on the labtop is owned by the
default user elog and default group elog, that is needed to start up the elogd. Only a user "elog" can do the cloning, unless temporarily the owner ship in /usr/local/elog is changed. I made it work by temporarily changing the owner ship on both machines, did the cloning, changed back to owner elog, started elogd and all was running.
I setup synchronizing and here too it works only if the read passwd in elogd.cfg is commented out.
Sync works fine from the RedHat linux laptop (rpm installed), but crashes the elogd on the alpha Linux machine (compiled from src) most of the time. elogd hast to be restarted and the sync had not finished.
So for now I settled to do the synchronize only from the laptop but have to remove the read passwd each time. That is tolerable but not
convenient.

Here I have another question: My Elog is passwd protected, encrypted passwd in elogd.cfg (read and write). When connecting to the elog the window
pops up asking for a user name and the passwd. I donot remember exactly, what was done to set name and passwd. But I find it "strange" that the user name can be anything as long as the passwd is right to access the ELog.
I think I have to learn more about the whole user and passwd protection schema.

Thanks again
Gerfried
ELOG V3.1.5-2eba886