Re: OSX Issues, posted by Stefan Ritt on Fri Jul 29 14:22:00 2022
|
I just tried the same on my latpop (MacOSX 12.4) and it worked flawlessly:
ritt@MBP14 build % echo "blah" | ./elog -h 127.0.0.1 -p 8080 -l demo -r 2 -x
Message successfully transmitted, ID=3 |
|
Re: Unable to add user, posted by Stefan Ritt on Mon Aug 8 08:26:11 2022
|
I recommend to clear all your browser cookies for the elog server. Sometimes an old cookie confuses the
access mechanism.
|
|
Re: Unable to add user, posted by Uwe Vollbracht on Mon Aug 8 14:06:28 2022
|
Thanks for answering. Just tried your suggestion with different browsers
(firefox, chrome, brave) but the error message still appears when adding a
|
|
Re: Unable to add user, posted by Konstantin Olchanski on Mon Aug 8 20:52:17 2022
|
> Error: Command "config" is not allowed for user ""
Could it be related to the error messages thrown by "activate user"? see
|
|
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? |
|
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. |
|
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 |
|
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 |