Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 38 of 41  Not logged in ELOG logo
Category:Info
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  66682   Wed Jan 13 12:00:04 2010 Reply David PilgramDavid.Pilgram@epost.org.ukInfoLinux2.7.8Topic changed to: emails sent/received after edited entries.
> > > I only got one email in response to the second entry of this thread, no email was received after the edit of the entry.  The
> > > next email received was due to the third entry of this thread.
> > 
> > Ok, let me try (sorry to all the users who subscribe to this forum for pestering you...):
> > 
> > 1st reply to your entry.
> > 
> > 1st reply edited.
> 
> I got two email notifications, the second one I attached as a screen shot. So I don't know what happened in your case. The problem 
> with the proxy is sometimes related to slow internet connections. If the HTML code transported over the internet has some delay 
> between packets, the proxy server sometimes drops the connection. I don't know how to fix that in my Apache. If you edit in HTML, 
> your browser downloads the JavaScript code and icons for the edit window, which is a lot of data, so the dropping is much more 
> likely.
Hi Stefan,

I confirm that this is a slow internet line, so that explains the Proxy Error.  

Maybe I should just keep my head down on threads where people use html coding ;-)

Did you receive two emails to my entry 66677?  I only received one.

I only received one email to your posting 66680 - the first entry, not the edited version.
  66684   Wed Jan 13 12:27:32 2010 Reply David PilgramDavid.Pilgram@epost.org.ukInfoLinux2.7.8Topic changed to: emails sent/received after edited entries.
> > > > > I only got one email in response to the second entry of this thread, no email was received after the edit of the entry.  The
> > > > > next email received was due to the third entry of this thread.
> > > > 
> > > > Ok, let me try (sorry to all the users who subscribe to this forum for pestering you...):
> > > > 
> > > > 1st reply to your entry.
> > > > 
> > > > 1st reply edited.
> > > 
> > > I got two email notifications, the second one I attached as a screen shot. So I don't know what happened in your case. The problem 
> > > with the proxy is sometimes related to slow internet connections. If the HTML code transported over the internet has some delay 
> > > between packets, the proxy server sometimes drops the connection. I don't know how to fix that in my Apache. If you edit in HTML, 
> > > your browser downloads the JavaScript code and icons for the edit window, which is a lot of data, so the dropping is much more 
> > > likely.
> > Hi Stefan,
> > 
> > I confirm that this is a slow internet line, so that explains the Proxy Error.  
> > 
> > Maybe I should just keep my head down on threads where people use html coding ;-)
> > 
> > Did you receive two emails to my entry 66677?  I only received one.
> > 
> > I only received one email to your posting 66680 - the first entry, not the edited version.
> 
> I checked my email server and found that the second message really went though it. But then I realized that there is indeed the "Message-
> ID:" in the email header (which I completely forgot in meantime). So maybe George Paplexis is right in that some mail 
> server/forwarder/receiver ignore a second email if it has the same ID. That would mean however that I have to introduce a "revision 
> number" for elog entries, which gets incremented on each edit and gets attached the the message-ID, so that it becomes unique again. 
> That's quite some work and has to wait a bit.

I had come to the same conclusion about the mail header being the same (see my email to you for full details).  

Sorry to all your subscribers for the email ping pong, although if others did receive two emails on the relivent entries - one original, and
one edited, it would be interesting, if possibly now academic, to know.
  67363   Mon Oct 29 12:22:30 2012 Reply David PilgramDavid.Pilgram@epost.org.ukInfoWindowslatestRe: Comment avoir elog en français II [solved almost]

Philippe Rousselot wrote:

Philippe Rousselot wrote:

Andreas Luedeke wrote:

Philippe Rousselot wrote:

Bonjour,

tout est dans le titre.

Merci

For those who speak strange languages, I asked how to get a french version of elog.

By the way, this is my second mail because I forgot to give an icon to the first mail, and when I hit Back to do so, my text was erased. Bug or normal obnoxious attitude of my browser ?

Thanks in advance

Philippe 

ELOG comes "internationalised": you just need to set your desired language in the configuration files.
Language = french
in the configuration file elogd.cfg does the trick.
If you are capable to read the English language (which I suppose ), then I would recommend reading the manual, e.g. https://midas.psi.ch/elog/config.html#global
Detect language » English
 

PS: I happened to have the same problem (text erased after "back") when I had javascript disabled in the browser. If you have it enabled, you'll get a popup window that tells you what mandatory fields are missing in your post. Then you'll not need to use the back button.

 Hi,

Thanks for the answer. I tried this (directly from de setting menu in the demo account as well as from the onfig file) :

I modified of course the text that could be modified directly from there such as menus and submenus.

I added Language = french, I restarted the server, clear the cache of firefox (IE as well), but list, new and so on appear in english even they are in the locale file...

Indeed, the manual is very interesting

concerning javascript, it is activated ...

Thanks again

Philippe

 Found it !

 

I wanted to have locale set in the folder demo (so I could have one in french and one in english).

Once language set in globals everything went fine. Almost...

Philippe

 May I make a suggestion here?  Something I do for other reasons.  I run two separate elog daemons, each with their own configuration files.  In this case you could have one configuration file tout en française, and the other in English.  This gets around the language setting being in the Global section of the configuration file elog.cfg

 

Of course this needs a little planning, for example a small script/batch file to start up each daemon with the correct config file. - so on my linux system, I start one with

/usr/local/sbin/elogd -p 8080 -c /home/logbooks/elogd0.cfg -d /home/logbooks

and the other with

/usr/local/sbin/elogd -p 8081 -c /home/logbooks/elogd1.cfg -d /home/logbooks

 

The disadvantage is that you cannot click between French and English by the tabs along the top of the elog page, you'd have to switch between browser windows.

Hope this helps.

 

David.

  67365   Mon Oct 29 19:10:37 2012 Reply David PilgramDavid.Pilgram@epost.org.ukInfoWindowslatestRe: Comment avoir elog en français II [solved almost]

Andreas Luedeke wrote:

David Pilgram wrote:

[...]
[...]

 May I make a suggestion here?  Something I do for other reasons.  I run two separate elog daemons, each with their own configuration files.  In this case you could have one configuration file tout en française, and the other in English.  This gets around the language setting being in the Global section of the configuration file elog.cfg

Of course this needs a little planning, for example a small script/batch file to start up each daemon with the correct config file. - so on my linux system, I start one with

/usr/local/sbin/elogd -p 8080 -c /home/logbooks/elogd0.cfg -d /home/logbooks

and the other with

/usr/local/sbin/elogd -p 8081 -c /home/logbooks/elogd1.cfg -d /home/logbooks

The disadvantage is that you cannot click between French and English by the tabs along the top of the elog page, you'd have to switch between browser windows.

Hope this helps.

David.

Does this work nice and stable for you? I've tried at the beginning to run two server on one host, one in German and the other in English.
I experienced occasional server crashes (every few days) and assumed that they were related to two mirrors running on the same host.
A mirror server just for a second language was not of big importance to me, therefore I did shut down the mirror server.
And the server stopped crashing then. Was that just coincidence?
I recognised that you are not running a mirror, you let both logbook processes access the same data. Is that save?
Did you ever see data corruption from two processes modifying the same data? Or is one of the ELOG servers not used much?
 
Thanks for sharing your experience!
Andreas
 
Detect language » English
 

 

 I'd better put some caveats in here, then!

The two daemons on my host were never accessing the same subdirectories of /home/logbooks (this is my location, for ease of data backups (*)), and they were running with owner 'nobody', i.e. that's the owner of each directory.  In that sense they were independant, and as I was the only user, only one daemon would be working on files at any one moment. 

Next is that my system is never running for so many days uninterrupted.  The computer sometimes has to be booted into Windoze to use the CAD program, or even was just shut down and switched off.

I realise now that my earlier reply may have lead people to think they could work on the same data with two separate daemons (so as to work in their own language, but the data would be in both....) but I never meant to give that impresssion.  I've simply not tried it.  It might work on a stand-alone system, but I don't know how elog copes with multiple users accessing data at the same time - lock files?  check to see if data has been altered before allowing a submission is probably not done (it would make a branch if branches were allowed, I think) - I don't have the experience of using elog under these circumstances.  I thought Philippe Rousselot wanted a French language logbook and a separate English language one.  If I'm wrong there, sorry to raise his hopes.

Make a nice little project for someone to explore the limits, and maybe find what changes are needed.  Not necessarily to impliment it, though.

As for data corruption, never seen any, but I suppose the general warning of keep the backups well up-to-date.  I have had trouble with data, in particular moving data between logbooks, and this is one reason I have experience of how to make an elog entry using a text editor, as well as how to modify entries - to assemble scattered entries into a thread, or split a long thread into two shorter ones for ease of handling.  But I don't think those were ever connected to having two deamons running on one host, it happens when just one is running.

 

(*) In principle, all my data can be put on a memory stick - currently 16GB - and then I can run any linux box with full access to all my data, with the memory stick mounted on /home.

  67681   Fri Mar 28 14:29:24 2014 Entry David PilgramDavid.Pilgram@epost.org.ukInfoLinux2.9.2-a738A couple of observations
Hi Stefan and Andreas,

When I submitted the previous entry, I had an error message about not able to send via psxxxx.psi.ch come up as
a red bar at the top of the elog page - sorry, cannot remember the subdomain name correctly.

The observations I was going to make is firstly the change in layout of the Find section - maybe I'll get used
to it but the change in layout wasn't warmly welcomed.

Also, shame that moving from Subversion means that the increments are no longer in easy numerical order.  So I
believe that I am commenting on the latest possible version available, a738232.

A question.  My logbooks directory is now 1.8GB.  Yes, there are a lot of attachments etc to bulk it out, but
it's all plain text comments.  Is there a limit as to the size, or total number of entries?  Elog takes a
notible amount of time to index it all these days, and I have wondered whether a couple of "instabilities" might
be caused by this.  Anyone any thoughts?

I don't know how I managed it, but I got elog to generate two entries with the identical ID no.  The new entries
were different as well.  The log file faithfully had recorded the two separate replies to the entry having the
same ID no as well.   Unfortunately I went and corrected it by editing the YYMMDDa.log file without keeping a
copy.  I have also had a mysterious entry ID0 appear in threaded display, despite there being no entry 0; and if
it appears, it appears in two or three places within the list of threaded entries.
  67682   Fri Mar 28 14:55:16 2014 Reply David PilgramDavid.Pilgram@epost.org.ukInfoLinux2.9.2-a738Re: A couple of observations
I tried to attach a screenshot showing this, but kept getting a 502 bad gateway error.
The message in the red banner is
Error sending Email via <i>"psquad.psi.ch"</i>
with that html showing, by the way.
> Hi Stefan and Andreas,
> 
> When I submitted the previous entry, I had an error message about not able to send via psxxxx.psi.ch come up as
> a red bar at the top of the elog page - sorry, cannot remember the subdomain name correctly.
> 
> The observations I was going to make is firstly the change in layout of the Find section - maybe I'll get used
> to it but the change in layout wasn't warmly welcomed.
> 
> Also, shame that moving from Subversion means that the increments are no longer in easy numerical order.  So I
> believe that I am commenting on the latest possible version available, a738232.
> 
> A question.  My logbooks directory is now 1.8GB.  Yes, there are a lot of attachments etc to bulk it out, but
> it's all plain text comments.  Is there a limit as to the size, or total number of entries?  Elog takes a
> notible amount of time to index it all these days, and I have wondered whether a couple of "instabilities" might
> be caused by this.  Anyone any thoughts?
> 
> I don't know how I managed it, but I got elog to generate two entries with the identical ID no.  The new entries
> were different as well.  The log file faithfully had recorded the two separate replies to the entry having the
> same ID no as well.   Unfortunately I went and corrected it by editing the YYMMDDa.log file without keeping a
> copy.  I have also had a mysterious entry ID0 appear in threaded display, despite there being no entry 0; and if
> it appears, it appears in two or three places within the list of threaded entries.
  68003   Wed Jun 10 14:25:16 2015 Question David PilgramDavid.Pilgram@epost.org.ukInfoLinuxV3.1.0-5be245eIs ELOG sending out cookies?

On my linux box, every time I select a thread, or start a new entry etc, I see that one or many cookies are sent.

On a terminal, I get the message

Received unknown cookie "CalciumDisplayParams"


Now I do have a perl script called Calcium, (Calendar viewed through the browser) but it's definately not running now, not in any browser window, and in any case why should an action of ELOG trigger this?  I realise it may be due to an idiocyncratic set up of this box.  But in normal operation, I doubt the user would see these cookies being received.

  68005   Wed Jun 10 15:48:57 2015 Reply David PilgramDavid.Pilgram@epost.org.ukInfoLinuxV3.1.0-5be245eRe: Is ELOG sending out cookies?

Hi Stefan,

Thanks for the explanation.  I realised it was just an error message of no real import, but it can get irritating at times.

Stefan Ritt wrote:

Cookies are sent from your browser. ELOG has no influence on what the browser sends where. Probably you run your calender at the same machine where ELOG is running, so all the cookies your calender app stores in your browser are sent to ELOG as well. ELOG just complains about something it does not know, but otherwise this message can be simply ignored. Of course you can delete your cookies in your browser, but after the next call to your calendar app they will show up again.

David Pilgram wrote:

On my linux box, every time I select a thread, or start a new entry etc, I see that one or many cookies are sent.

On a terminal, I get the message

Received unknown cookie "CalciumDisplayParams"


Now I do have a perl script called Calcium, (Calendar viewed through the browser) but it's definately not running now, not in any browser window, and in any case why should an action of ELOG trigger this?  I realise it may be due to an idiocyncratic set up of this box.  But in normal operation, I doubt the user would see these cookies being received.

 

 

ELOG V3.1.5-3fb85fa6