Re: Need to change port 25, posted by Stefan Ritt on Thu Nov 29 09:56:45 2018
|
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!
|
|
|
Re: Need help with permission, posted by Mikkel D. Lund on Mon Sep 26 12:21:52 2022
|
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
|
|
|
Re: Need help with permission, posted by Stefan Ritt on Mon Sep 26 12:38:29 2022
|
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
|
|
|
|
Re: Need help with permission, posted by Stefan Ritt on Mon Sep 26 12:45:50 2022
|
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
|
|
|
|
|
Re: Need help with permission, posted by Dan Witteman on Mon Sep 26 19:21:33 2022
|
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
|
|
|
|
|
|
Re: Need for email address in login?, posted by Stefan Ritt on Tue Nov 20 08:45:59 2012
|
| 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. |
|
Re: Need for email address in login?, posted by David Pilgram on Tue Nov 20 10:28:24 2012
|
| Stefan Ritt wrote: |
|
| 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.
|
Word of warning about fake email addresses - if your system suddenly does start to send out messages to them, you'll start getting otherwise mysterious email messages back about being unable to deliver and other such comments. I speak from experience - although in my case the puzzle was finding what was generating the messages in the first place (not elog, another program as it happened).
I suggest you also include
Suppress default = 3
in your configuration file, which also stops them being generated in the first place.
Although I was unaware (or had totally forgotten) that there was a 'Suppress email button' as mentioned in the documentation. |
|
Re: Need for email address in login?, posted by Jeff Kozloski on Tue Nov 20 19:31:06 2012
|
| Stefan Ritt wrote: |
|
| 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.
|
Our IT dept is very strict. I'll have to see if I can get email out to a web based email service like yahoo. But they will not give each of my mechanics an email account here.
Thanks
|
|