ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
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
|
|
|
|
|
|
68867
|
Wed Nov 28 18:23:59 2018 |
| Yanick Vachon | yvachon@materiauxblanchet.ca | Request | Windows | 3.1.2 | Re: Need to change port 25 |
Good!
so, i've tried to compile but iwonder if i does it correctly,
look at the error i got:
Thanks again!
Stefan Ritt wrote: |
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.
|
|
|
Attachment 1: Capture_Compile.PNG
|
|
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!
|
|
69560
|
Mon Sep 26 12:21:52 2022 |
| Mikkel D. Lund | mikkel.lund@rsyd.dk | Question | Linux | 3.1.4-395 | Re: Need help with permission |
Hi all,
I have the same problem on Ubuntu 22.04. I have compiled from the latest tarball and copied all our logbooks from our old Ubuntu 18.04 server to a new Ubuntu 22.04. The logbooks does however not appear when I log in, so I assume ELOG doesn't have read access either?
Any hints on how to set the permissions correctly would be greatly appreciated.
Thanks,
Mikkel
Dan Witteman wrote: |
Hello,
I have just installed elog onto an ubuntu focal server using <sudo make install> and I am unable to create new entries.
When I access the log via a windows PC connected to the local network, I can see the demo logbook with the 1 test post, but I cannot create or edit anything.
Attempting to post throws the error:
New entry cannot be written to directory "/usr/local/elog/logbooks/demo/"
Please check that it exists and elogd has write access and disk is not full.
Please point me in the right direction to correctly set permissions and create aditional log books.
Thanks,
Dan
|
|
69561
|
Mon Sep 26 12:38:29 2022 |
| Stefan Ritt | Permistefan.ritt@psi.ch | Question | Linux | 3.1.4-395 | Re: Need help with permission |
Permissions are handled by the operating system and have nothing to do with elog. Make sure you run elog under an account which has write access to the desired directories. Consult Ubuntu documentation how to do that. Sometimes it's helpful to start elog interactively with the -v flag to see some verbose output. Maybe you can spot something there.
Stefan
Mikkel D. Lund wrote: |
Hi all,
I have the same problem on Ubuntu 22.04. I have compiled from the latest tarball and copied all our logbooks from our old Ubuntu 18.04 server to a new Ubuntu 22.04. The logbooks does however not appear when I log in, so I assume ELOG doesn't have read access either?
Any hints on how to set the permissions correctly would be greatly appreciated.
Thanks,
Mikkel
Dan Witteman wrote: |
Hello,
I have just installed elog onto an ubuntu focal server using <sudo make install> and I am unable to create new entries.
When I access the log via a windows PC connected to the local network, I can see the demo logbook with the 1 test post, but I cannot create or edit anything.
Attempting to post throws the error:
New entry cannot be written to directory "/usr/local/elog/logbooks/demo/"
Please check that it exists and elogd has write access and disk is not full.
Please point me in the right direction to correctly set permissions and create aditional log books.
Thanks,
Dan
|
|
|
69562
|
Mon Sep 26 12:45:50 2022 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.4-395 | Re: Need help with permission |
Sometimes this can also be an SELinux issue, if you have that service running. Try "journalctl | grep denied" to see denied resources and consult the SELinux documentation on how to fix that.
Stefan Ritt wrote: |
Permissions are handled by the operating system and have nothing to do with elog. Make sure you run elog under an account which has write access to the desired directories. Consult Ubuntu documentation how to do that. Sometimes it's helpful to start elog interactively with the -v flag to see some verbose output. Maybe you can spot something there.
Stefan
Mikkel D. Lund wrote: |
Hi all,
I have the same problem on Ubuntu 22.04. I have compiled from the latest tarball and copied all our logbooks from our old Ubuntu 18.04 server to a new Ubuntu 22.04. The logbooks does however not appear when I log in, so I assume ELOG doesn't have read access either?
Any hints on how to set the permissions correctly would be greatly appreciated.
Thanks,
Mikkel
Dan Witteman wrote: |
Hello,
I have just installed elog onto an ubuntu focal server using <sudo make install> and I am unable to create new entries.
When I access the log via a windows PC connected to the local network, I can see the demo logbook with the 1 test post, but I cannot create or edit anything.
Attempting to post throws the error:
New entry cannot be written to directory "/usr/local/elog/logbooks/demo/"
Please check that it exists and elogd has write access and disk is not full.
Please point me in the right direction to correctly set permissions and create aditional log books.
Thanks,
Dan
|
|
|
|
69563
|
Mon Sep 26 19:21:33 2022 |
| Dan Witteman | drwitteman@physics.ucsd.edu | Question | Linux | 3.1.4-395 | Re: Need help with permission |
I used "chown" to pass permissions from root to my deafult user, then restarted the service and now I can make posts. Thank you!
Stefan Ritt wrote: |
Sometimes this can also be an SELinux issue, if you have that service running. Try "journalctl | grep denied" to see denied resources and consult the SELinux documentation on how to fix that.
Stefan Ritt wrote: |
Permissions are handled by the operating system and have nothing to do with elog. Make sure you run elog under an account which has write access to the desired directories. Consult Ubuntu documentation how to do that. Sometimes it's helpful to start elog interactively with the -v flag to see some verbose output. Maybe you can spot something there.
Stefan
Mikkel D. Lund wrote: |
Hi all,
I have the same problem on Ubuntu 22.04. I have compiled from the latest tarball and copied all our logbooks from our old Ubuntu 18.04 server to a new Ubuntu 22.04. The logbooks does however not appear when I log in, so I assume ELOG doesn't have read access either?
Any hints on how to set the permissions correctly would be greatly appreciated.
Thanks,
Mikkel
Dan Witteman wrote: |
Hello,
I have just installed elog onto an ubuntu focal server using <sudo make install> and I am unable to create new entries.
When I access the log via a windows PC connected to the local network, I can see the demo logbook with the 1 test post, but I cannot create or edit anything.
Attempting to post throws the error:
New entry cannot be written to directory "/usr/local/elog/logbooks/demo/"
Please check that it exists and elogd has write access and disk is not full.
Please point me in the right direction to correctly set permissions and create aditional log books.
Thanks,
Dan
|
|
|
|
|
67382
|
Tue Nov 20 08:45:59 2012 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.9.2 | Re: Need for email address in login? |
Jeff Kozloski wrote: |
How can I skip the need for an email address when registering and logging in? Our IT dept will not give an email address to each guy I want on the log.
|
I never thought that someone will not have an email address. One basic feature of ELOG is its automatic notification if there is a new entry, and that only works over email. It's like social networks, you cannot register for Facebook if you don't have an email address.
So if you absolutely want to omit this, just give a fake email address, like nobody@no.where. ELOG just checks if there is a "@" and a "." somewhere. |