Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 374 of 808  Not logged in ELOG logo
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  68913   Tue Mar 19 23:24:48 2019 Question Ross Gibsonross.gibson@newcastle.edu.auSince updating to verQuestionWindows3.1.4HTML editor not working after updating to V3.1.4
Since updating to v3.1.4 the HTML editor has stopped working. If I switch to HTML encoding, the editor appears with a blank field, cannot select or type in field and none of the buttons work.
I have tried reverting to earlier versions, but the issue persists. Any suggestions to rectify?
  68915   Wed Mar 20 06:50:57 2019 Reply Ross Gibsonross.gibson@newcastle.edu.auQuestionWindows3.1.4Re: HTML editor not working after updating to V3.1.4

Thanks Stefan. Tried these without success. I tried opening in another browser and it works fine in Firefox or Internet Explorer - the problem only appears in Microsoft Edge. Perhaps its an issue with a Microsoft update (corporate rollout) to Edge and just a coincidence that I noticed it after updating Elog.


Stefan Ritt wrote:
Have you cleared your browser cache? There might be some old JavaScript stored there. If that does not help, remove elog and reinstall it to make sure to have the correct libraries on the server (first back up you logbooks, then restore them afterwards).

Stefan


Ross Gibson wrote:
Since updating to v3.1.4 the HTML editor has stopped working. If I switch to HTML encoding, the editor appears with a blank field, cannot select or type in field and none of the buttons work.
I have tried reverting to earlier versions, but the issue persists. Any suggestions to rectify?
  67393   Mon Dec 10 16:28:27 2012 Warning Ron Beekmanron.beekman@gmail.comBug reportWindows2.7.5-2130Error 554 MailTransferAgentServer ESMTP not accepting messages

Hello,

We use ELOG for many years and enjoy it's functions every day!

Lately, we see errors whenever we add an entry in elog: 554 MailTransferAgentServer ESMTP not accepting messages

We see this from various ELOG servers. Other (non ELOG) servers using the same MailTransferAgentServer do not heve this error.

We are able to send mail messages from the ELOG machines manually via TELNET. So, from a functional point of view, all works well.

We had this error in the past and found out that the cause of this error lies in (network) time-outs.

Questions:
1) Has anyone seen this error before?
2) Is it possible to increase the timeout value used by ELOG?
3) Are the emails that could not be sent stored in a queue/resent later or are they lost?
4) is there a fix?

Any replies are highly appreciated!

T I A !
 

  67395   Tue Dec 11 09:43:33 2012 Reply Ron Beekmanron.beekman@gmail.comBug reportWindows2.7.5-2130Re: Error 554 MailTransferAgentServer ESMTP not accepting messages
> Just my 2 cent: did you try to reproduce the problem with the latest ELOG version 2.9.2?

Hi Andreas,

Thank you very much for your reply. Thsi problem occurs also with the latest ELOG version 2.9.2

It would be nice if the timeout value(s) can be edited via the elogd.cfg file. Maybe this can be added in a new 
version.

Best regards,
Ron
  67397   Tue Dec 11 10:17:11 2012 Reply Ron Beekmanron.beekman@gmail.comBug reportWindows2.7.5-2130Re: Error 554 MailTransferAgentServer ESMTP not accepting messages

Stefan Ritt wrote:

Ron Beekman wrote:

Hello,

We use ELOG for many years and enjoy it's functions every day!

Lately, we see errors whenever we add an entry in elog: 554 MailTransferAgentServer ESMTP not accepting messages

We see this from various ELOG servers. Other (non ELOG) servers using the same MailTransferAgentServer do not heve this error.

We are able to send mail messages from the ELOG machines manually via TELNET. So, from a functional point of view, all works well.

We had this error in the past and found out that the cause of this error lies in (network) time-outs.

Questions:
1) Has anyone seen this error before?
2) Is it possible to increase the timeout value used by ELOG?
3) Are the emails that could not be sent stored in a queue/resent later or are they lost?
4) is there a fix?

Any replies are highly appreciated!

T I A !
 

Could you run elogd interactively with the "-v" flag to log the communication between elogd and the ESMTP server and send me the traffic log? 

Hello Stefan,

Thanks you for entering this thread !

Fortunately, we were able to solve the problem. A reboot of the DNS server used by the MTA (Mail Transfer Agent Server) to check the from and to address did the trick.

This server now responds within the timeout period in ELOG.

It still would be handy if you could add a parameter to the config file that allows us to fiddle with the timeout value. The DNS server used by the MTA has to deal with heavy load.

Best regards,
Ron

 

 

 

 

  67463   Wed Mar 6 17:56:22 2013 Question Ron Beekmanron.beekman@gmail.comQuestionWindowsV2.9.2-247Wrong link in "Your ELOG account has been activated" email
After entering a new user and activating it in ELOG, the new user receives an email.

The link does not work because the port number is repeated in the link (see below)

In the Global part of the elogd.ini we have added the port:

port = 8080



Maybe I am overlooking something, any suggestions are very much appreciated!



Thanks!

Ron



- - - - - -



Email Subject: Your ELOG account has been activated



Email Body:



Your ELOG account has been activated on host eloghost:8080.



You can access it at http://eloghost:8080:8080/logbookname/?unm=newuser.



To subscribe to any logbook, click on 'Config' in that logbook.
  67468   Thu Mar 7 14:37:27 2013 Reply Ron Beekmanron.beekman@gmail.comQuestionWindowsV2.9.2-247Re: Wrong link in "Your ELOG account has been activated" email
Hi Stefan, thank you very much for having a look at this :-)



Here is the config file we use. Seems okay to me, but I may be overlooking something.





[global]

port = 8080

SMTP host = localhost

Self register= 0

Display Email recipients = 0

Use Email Subject = [ELOG - $logbook]

Date format = %a %d-%b-%Y %H:%M

Default encoding = 1

Allowed encoding = 1



[MYLOGBOOK]

Theme = default

Comment = My logbook

Password file = passw_mylogbook.pwd

Admin user = admin,user1,user2,user3

Self register= 3

Menu commands = List, New, Edit, Reply, Duplicate, Find, Config, Logout, Help

Attributes = Author, Type, Category, Subject, ServerNaam

Preset Author = $long_name

Options Type = Opt01, Opt02, Opt03, Opt04, Opt05

Options Category = Cat01, Cat02, Cat03, Cat04, Cat05, Cat06, Cat07

MOptions ServerNaam = Server01

Preset ServerNaam = Server01

Required Attributes = Author, Type, ServerNaam

Page Title = ELOG - $subject

Reverse sort = 1

Quick filter = Date, Type, ServerNaam
  67264   Mon May 7 13:41:38 2012 Question Roland Gsellroland.gsell@oeaw.ac.atInfoLinux2.9.1-2435Access rights

Hi,

the manual says:

"
There are four ways through which access to a logbook may be controlled:

it may be open for all to read ;
it may require a common "read" password for all users ;
it may require each user to have an individual user account (login name) and password ;
finally, access may be granted or not depending on the address of the workstation you are using.
"

But it doesn't say how to do so or at least I didn't find it.

If I have each user have to log in with an individual accout, can I define which logbooks he can read and/or modify?
If yes, how to do that?

Also, please accept my vote for user groups. We can use that, too.

TIA,
Roland.

ELOG V3.1.5-3fb85fa6