ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68883
|
Fri Feb 1 21:59:46 2019 |
| Frank Baptista | caffeinejazz@gmail.com | Question | Windows | 3.1.2 | Re: Logbook architecture and availability | Sorry -- dumb mistake. I moved the "theme" files to the resource folder. Works like a champ...life is good! 
Frank Baptista wrote: |
I've got things working - sort of. Ran into one strange problem that has me scratching my head. I have two different laptops, each running a local instance of their own logbook. Both are functional, but for some strange reason, one looks great, and the other is missing its graphic format. I've attached a screen capture of that logbook, and a copy of the config file. Do you see something that I've done wrong?
Thanks,
Frank
Frank Baptista wrote: |
Thank you again -- very much appreciated! 
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?
|
|
|
|
|
|
|
68882
|
Fri Feb 1 19:20:35 2019 |
| Frank Baptista | caffeinejazz@gmail.com | Question | Windows | 3.1.2 | Re: Logbook architecture and availability | I've got things working - sort of. Ran into one strange problem that has me scratching my head. I have two different laptops, each running a local instance of their own logbook. Both are functional, but for some strange reason, one looks great, and the other is missing its graphic format. I've attached a screen capture of that logbook, and a copy of the config file. Do you see something that I've done wrong?
Thanks,
Frank
Frank Baptista wrote: |
Thank you again -- very much appreciated! 
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?
|
|
|
|
|
|
68881
|
Wed Jan 9 11:43:48 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | Windows | 2.9.2-245 | Re: MIME-version header duplicated in e-mail messages. | I just checked the current installatin, and just found one MIME-Version in the header, even with attachments:
MIME-Version: 1.0
--------------717E3059287C82F12BC14941
Content-Type: multipart/related;
boundary="------------4543EB0E5AAC14B461D70512"
No idea where your second header comes from, but sometimes I have seen some SPAM filters adding things to headers.
Stefan
Michal Falowski wrote: |
When there are attachments in an entry, logbook is adding additional "MIME-Version" header to e-mail messages.
Spam filter in our university system is mostly giving warnings:
- X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
But sometimes it is not redirecting further the message.
- Remote Server returned '< #5.6.0 smtp; 554 5.6.0 Bounce, id=27666-07 - BAD HEADER>'
In code I noticed there is always "MIME-Version" header added to the message and additionaly it is added again when a file is attached. I think it is not neccessary to add again this header.
|
|
68880
|
Fri Dec 21 14:59:05 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 3.1.3 | Re: inactive users | Thanks for the fix, I merged it into the current development branch.
Stefan |
68879
|
Fri Dec 21 14:04:41 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | V3.1.3-aded4ae | Re: CSS reference in Email for private logbooks | I changed the code ot include the CSS file directly in the email body. So no need any more for external CSS files. I dropped the "Email CSS URL" option as well.
Stefan
Andreas Luedeke wrote: |
We operate ELOG in an intranet. Many logbooks do send out emails; several use HTML content formatting.
If I watch HTML formatted emails from the intranet, then everything is fine.
If I try to read them from home, my email client hangs when it tries to read the CSS file from out intranet (URL: https://elog-gfa.psi.ch/SLS/elog.css).
Is there a way to set a URL for the email CSS?
Then I could simply copy the CSS file to the internet accessible location and the emails would be properly formatted in the intranet and from home.
I've tried to use "Use Email URL = ", but it turned out that this will change all base URL's in the email BUT the one in the CSS :-(
So I would need a config "Email CSS URL = " to set this.
Here is a patch that does what I want, but it might have some side-effects I'm not yet aware of:
7636,7643c7636,7638
< if (absolute_link) {
< if (lbs != NULL && getcfg(lbs->name, "Email CSS URL", str, sizeof(str)))
< strlcpy(css_base, str, sizeof(css_base));
< else if (lbs == NULL && getcfg("global", "Email CSS URL", str, sizeof(str)))
< strlcpy(css_base, str, sizeof(css_base));
< if (css_base[0] == 0)
< compose_base_url(lbs, css_base, sizeof(css_base), FALSE);
< } else
---
> if (absolute_link)
> compose_base_url(lbs, css_base, sizeof(css_base), FALSE);
> else
Cheers
Andreas
|
|
68878
|
Fri Dec 21 13:00:50 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.2 | Re: xmalloc error when filling entries and chaning page | 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
|
|
68877
|
Fri Dec 14 20:52:46 2018 |
| Frank Baptista | caffeinejazz@gmail.com | Question | Windows | 3.1.2 | Re: Logbook architecture and availability | Thank you again -- very much appreciated! 
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?
|
|
|
|
|
68876
|
Fri Dec 14 20:05:08 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.1.2 | Re: Logbook architecture and availability | 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?
|
|
|
|
|