Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 371 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
New entries since:Thu Jan 1 01:00:00 1970
 Full | Summary | Threaded | Hide attachments  Show all entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 370, 371, 372 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  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
  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.
Goto page Previous  1, 2, 3 ... 370, 371, 372 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6