ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68860
|
Tue Nov 27 08:59:45 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | 3.1.2 | Re: Need to change port 25 | I believe Yanick means the SMTP port, not the port under which elogd is listening. The SMPT port is hard wired to 25, because port 587 was not yet defiend when I wrote that code. I can make this a variable, but only if it works. So Yanick can you test if port 587 accepts normal SMTP commands? We don't have such a new server at our lab and I cannot test it. Under Windows you can open a command prompt and telnet to the mail server:
telnet <server> 587
HELO test
MAIL FROM: test
your server should then reply with "220 ..." and "250 ..." messages. Once this works, I will implement the variable SMTP port.
Stefan
Andreas Luedeke wrote: |
This is nicely explained in the documentation: https://elog.psi.ch/elog/config.html#global
The following options are specific to the [global] section:
Port = <port>
Specifies the TCP port under which the server is listening. Default is 80. Can be superseeded via the '-p' command line flag.
Yanick Vachon wrote: |
Hi,
We've made changes in our network and now we have to use port 587 instead of port 25, how can i edit that parameter?
Thanks
|
|
|
68863
|
Wed Nov 28 09:26:11 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 3.1.2 | Re: French Language | 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.
|
|
68864
|
Wed Nov 28 16:24:43 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | 3.1.2 | Re: Need to change port 25 | Ok, so I added the option
STMP port = xxx
where you can specify 587 to override the default port 25. I committed the changes to bitbucket. Can you compile from sources, or do I have to dig out my dusty Windows PC?
Stefan
Yanick Vachon wrote: |
I Stefan, it works with the 587 port.
|
|
68866
|
Wed Nov 28 16:53:58 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | 3.1.2 | Re: Need to change port 25 | Just read my post 20 mins ago!
Stefan
Yanick Vachon wrote: |
Hello,
now we kwow it's working are you gonne send us a version with the SMTP port editable?
Thanks!
Yanick Vachon wrote: |
I Stefan, it works with the 587 port.

Stefan Ritt wrote: |
I believe Yanick means the SMTP port, not the port under which elogd is listening. The SMPT port is hard wired to 25, because port 587 was not yet defiend when I wrote that code. I can make this a variable, but only if it works. So Yanick can you test if port 587 accepts normal SMTP commands? We don't have such a new server at our lab and I cannot test it. Under Windows you can open a command prompt and telnet to the mail server:
telnet <server> 587
HELO test
MAIL FROM: test
your server should then reply with "220 ..." and "250 ..." messages. Once this works, I will implement the variable SMTP port.
Stefan
Andreas Luedeke wrote: |
This is nicely explained in the documentation: https://elog.psi.ch/elog/config.html#global
The following options are specific to the [global] section:
Port = <port>
Specifies the TCP port under which the server is listening. Default is 80. Can be superseeded via the '-p' command line flag.
Yanick Vachon wrote: |
Hi,
We've made changes in our network and now we have to use port 587 instead of port 25, how can i edit that parameter?
Thanks
|
|
|
|
|
|
68868
|
Thu Nov 29 09:56:45 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | 3.1.2 | Re: Need to change port 25 | I put a new executable for you under https://elog.psi.ch/elog/download/windows/
It's named elog314-2.exe
Best,
Stefan
Yanick Vachon wrote: |
Good!
so, i've tried to compile but iwonder if i does it correctly,
look at the error i got:
Thanks again!
|
|
68870
|
Wed Dec 5 08:41:07 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 3.1.2 | Re: French Language | 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.
|
|
|
|
68874
|
Fri Dec 14 16:00:45 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.1.2 | Re: Logbook architecture and availability | 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?
|
|
|
|
|