Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 230 of 796  Not logged in ELOG logo
    icon2.gif   Re: French Language, posted by Yanick Vachon on Wed Dec 5 14:38:51 2018 

I've deleted the cookies and it works.

Thanks!

Stefan Ritt wrote:

Have you tried to delete all cookies in Chrome?

Stefan

Yanick Vachon wrote:

I Stefan, i got the problem again with the french version, i realised that if i open it with Chrome or Edge it's not working but with Internet Explorer it works envery times. Is there a way i can use it with Chrome?

 

Thanks!

Stefan Ritt wrote:

I just tried myself with the current version 3.1.4 and it worked for me flawlessly. Maybe you want to upgrade.

Stefan

Yanick Vachon wrote:

Hi,

When i set Language = French in global config it works in french until i logout, after i can't login anymore, even if i enter my user and password i always stay at the login window, the only way to login again is to edit the Elogd.cfg file in Elog directory, remove the Language = french and save then i can login in and work normally in english version.

 

Thanks.

 

 

 

 

icon4.gif   xmalloc error when filling entries and chaning page, posted by Antonio Iuliano on Wed Dec 12 10:44:57 2018 elogd.cfg

Dear ELOG experts,

the ELOG server on our lab crashes  continuosly, when we add a new entry or even if we click the arrows to navigate between entries. Following the FAQ on the website, I have used gdb and found the following error:

xmalloc: not enough memory

[Inferior 1 (process 23271) exited with code 01]

It should be then some allocation issue when we try to access to the entries, but I could not figure the nature of the issue. I was, however, able to reproduce it with a fresh ELOG installation and the same configuration file (ELOG cloned from git and installed today)

Could you please give me any suggestion? I attach here the configuration file we use.

Best regards,

Antonio Iuliano

icon5.gif   Logbook architecture and availability, posted by Frank Baptista on Fri Dec 14 15:46:14 2018 

I have a setting which makes ELOG a perfect solution, but there's a situation that I'm struggling to get my head around. We have 3 separate laboratories, each one containing a number of temperature chambers, which run almost constantly over a number of shifts. Each temperature chamber has it's own logbook (laptop). So far, pretty simple.
My dilemma is, our network goes down for maintenance/updates (more often than I'd like), but our operation cannot afford to stop during network interruptions.
With that said, I thought about whether I could run a "local" logbook on each laptop/chamber, and somehow mirror the local logbook to the main ELOG server.
Perhaps I'm over-thinking this...do you have any recommendations?

    icon2.gif   Re: Logbook architecture and availability, posted by Stefan Ritt on Fri Dec 14 16:00:45 2018 

Sure that's easy. Install elog on each laptop separately, so they run without network. Then, set up a central elog server, and use "mirroring" as explained in the documentation at https://elog.psi.ch/elog/config.html#mirroring

So when ever the entwork comes back, you execute a manual mirror operation, and your new entries will be pushed to the central elog server.

Best,
Stefan

Frank Baptista wrote:

I have a setting which makes ELOG a perfect solution, but there's a situation that I'm struggling to get my head around. We have 3 separate laboratories, each one containing a number of temperature chambers, which run almost constantly over a number of shifts. Each temperature chamber has it's own logbook (laptop). So far, pretty simple.
My dilemma is, our network goes down for maintenance/updates (more often than I'd like), but our operation cannot afford to stop during network interruptions.
With that said, I thought about whether I could run a "local" logbook on each laptop/chamber, and somehow mirror the local logbook to the main ELOG server.
Perhaps I'm over-thinking this...do you have any recommendations?

 

    icon2.gif   Re: Logbook architecture and availability, posted by Frank Baptista on Fri Dec 14 17:22:31 2018 

Thanks Stephan! I guess I was making it harder than it is.  I'm still a little fuzzy -- in this instance, am I correct in saying that each laptop would be considered a "master", and the remote (network) server considered the "slave"?  Also, I'm not sure quite sure -- which server should be assigned responsibility for performing periodic synchronization between the laptop and the central elog server?

Thanks again for all you do -- Happy Holidays!

Frank

Stefan Ritt wrote:

Sure that's easy. Install elog on each laptop separately, so they run without network. Then, set up a central elog server, and use "mirroring" as explained in the documentation at https://elog.psi.ch/elog/config.html#mirroring

So when ever the entwork comes back, you execute a manual mirror operation, and your new entries will be pushed to the central elog server.

Best,
Stefan

Frank Baptista wrote:

I have a setting which makes ELOG a perfect solution, but there's a situation that I'm struggling to get my head around. We have 3 separate laboratories, each one containing a number of temperature chambers, which run almost constantly over a number of shifts. Each temperature chamber has it's own logbook (laptop). So far, pretty simple.
My dilemma is, our network goes down for maintenance/updates (more often than I'd like), but our operation cannot afford to stop during network interruptions.
With that said, I thought about whether I could run a "local" logbook on each laptop/chamber, and somehow mirror the local logbook to the main ELOG server.
Perhaps I'm over-thinking this...do you have any recommendations?

 

 

    icon2.gif   Re: Logbook architecture and availability, posted by Stefan Ritt on Fri Dec 14 20:05:08 2018 

I would call the laptops the "master" being responsible for pushing data to the central server which you can call "slave"

 

Stefan

Frank Baptista wrote:

Thanks Stephan! I guess I was making it harder than it is.  I'm still a little fuzzy -- in this instance, am I correct in saying that each laptop would be considered a "master", and the remote (network) server considered the "slave"?  Also, I'm not sure quite sure -- which server should be assigned responsibility for performing periodic synchronization between the laptop and the central elog server?

Thanks again for all you do -- Happy Holidays!

Frank

Stefan Ritt wrote:

Sure that's easy. Install elog on each laptop separately, so they run without network. Then, set up a central elog server, and use "mirroring" as explained in the documentation at https://elog.psi.ch/elog/config.html#mirroring

So when ever the entwork comes back, you execute a manual mirror operation, and your new entries will be pushed to the central elog server.

Best,
Stefan

Frank Baptista wrote:

I have a setting which makes ELOG a perfect solution, but there's a situation that I'm struggling to get my head around. We have 3 separate laboratories, each one containing a number of temperature chambers, which run almost constantly over a number of shifts. Each temperature chamber has it's own logbook (laptop). So far, pretty simple.
My dilemma is, our network goes down for maintenance/updates (more often than I'd like), but our operation cannot afford to stop during network interruptions.
With that said, I thought about whether I could run a "local" logbook on each laptop/chamber, and somehow mirror the local logbook to the main ELOG server.
Perhaps I'm over-thinking this...do you have any recommendations?

 

 

 

    icon2.gif   Re: Logbook architecture and availability, posted by Frank Baptista on Fri Dec 14 20:52:46 2018 

Thank you again -- very much appreciated! smiley

Stefan Ritt wrote:

I would call the laptops the "master" being responsible for pushing data to the central server which you can call "slave"

 

Stefan

Frank Baptista wrote:

Thanks Stephan! I guess I was making it harder than it is.  I'm still a little fuzzy -- in this instance, am I correct in saying that each laptop would be considered a "master", and the remote (network) server considered the "slave"?  Also, I'm not sure quite sure -- which server should be assigned responsibility for performing periodic synchronization between the laptop and the central elog server?

Thanks again for all you do -- Happy Holidays!

Frank

Stefan Ritt wrote:

Sure that's easy. Install elog on each laptop separately, so they run without network. Then, set up a central elog server, and use "mirroring" as explained in the documentation at https://elog.psi.ch/elog/config.html#mirroring

So when ever the entwork comes back, you execute a manual mirror operation, and your new entries will be pushed to the central elog server.

Best,
Stefan

Frank Baptista wrote:

I have a setting which makes ELOG a perfect solution, but there's a situation that I'm struggling to get my head around. We have 3 separate laboratories, each one containing a number of temperature chambers, which run almost constantly over a number of shifts. Each temperature chamber has it's own logbook (laptop). So far, pretty simple.
My dilemma is, our network goes down for maintenance/updates (more often than I'd like), but our operation cannot afford to stop during network interruptions.
With that said, I thought about whether I could run a "local" logbook on each laptop/chamber, and somehow mirror the local logbook to the main ELOG server.
Perhaps I'm over-thinking this...do you have any recommendations?

 

 

 

 

    icon2.gif   Re: xmalloc error when filling entries and chaning page, posted by Stefan Ritt on Fri Dec 21 13:00:50 2018 

I tried to reproduce the problem but could not. The config file uses "emtpy.html", "filtermenutext.html" and so on which I don't have. Same with eventlocation.

Rather than sending me all the files, can you strip down your elogd.cfg to a minimal version where you still see the problem. Then give me all information to reproduce it. You also have to tell me when the error occurs, like when you submit a new entry, scan through entries etc.

Stefan

Antonio Iuliano wrote:

Dear ELOG experts,

the ELOG server on our lab crashes  continuosly, when we add a new entry or even if we click the arrows to navigate between entries. Following the FAQ on the website, I have used gdb and found the following error:

xmalloc: not enough memory

[Inferior 1 (process 23271) exited with code 01]

It should be then some allocation issue when we try to access to the entries, but I could not figure the nature of the issue. I was, however, able to reproduce it with a fresh ELOG installation and the same configuration file (ELOG cloned from git and installed today)

Could you please give me any suggestion? I attach here the configuration file we use.

Best regards,

Antonio Iuliano

 

ELOG V3.1.5-2eba886