Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 171 of 807  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  69561   Mon Sep 26 12:38:29 2022 Reply Stefan RittPermistefan.ritt@psi.chQuestionLinux3.1.4-395Re: 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 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.4-395Re: 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 Reply Dan Wittemandrwitteman@physics.ucsd.eduQuestionLinux3.1.4-395Re: 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

 

 

 

 

  69365   Thu May 20 21:01:41 2021 Question Gabriel Lopezgabelopez@bnl.govQuestionLinux3.1.4-3New user not working

Running elog-3.1.4-3 Can't add users through the web interface. Clicking add user and writing all the fields in with something doesn't add a user into the PWD file of that logbook. Running a tail -f on the password file shows elog writes the user info with the hashed password 3 times and then deletes the information about 20 seconds later. Has anyone else had a similar issue? This is running on RHEL8.3

  69367   Mon May 31 14:51:39 2021 Question Maximmaxsimuus69@gmail.comQuestionWindows3.1.4-3Problem with a self-compiled code.

Dear, sir! There is a problem with a configuration file.

The code was compiled by Cygwin (gcc-core, gcc-g++, make, gdb, libssl-dev).  After a compilation a reference to our own css-file was written in configuration file and css-file was included in a folder “themes/default” of the project.

The problem is that in running elog-3.1.4-1 (and upper versions) css-file name in a code of a page has some random symbols before file-name, for example: <link rel="stylesheet" type="text/css" href="ø9öÿeLogOUK.css">. It was found that the problem is resolved if a string “Password file=passwd” is deleted, but in this case it is impossible to set passwords to the users.

Here is an example of configuration file which is taken from the forum and just one string (CSS=elogOUK.css) has added to the code

 

[global]

 

; port under which server is listening

Port = 8080

 

CSS = eLogOUK.css

 

[Accelerator]

Comment = Accelerator Logbook

 

; use user level password access

Password file = passwd

Login expiration = 1000

Admin user = ritt

Self register = 1

 

; look and feel

Guest menu commands = Back, Find, Login, Help

Guest find menu commands = Find, Login, Help

Date format = %B %d, %Y

 

; attributes

Attributes = Author, Author Email, Category, Subject

Options Category = Routine entry, Shift summary, Problem, Fix, Question, Info, Other

Extendable attributes = Category

Required Attributes = Category, Subject

Thread display = $Subject, entered by $author on $Entry date

Quick filter = Date, Category

 

; title as shown in the browser

Page Title = Accelerator Logbook - $subject

 

; preset author and email

Preset Author = $long_name

Preset Author Email = $user_email

 

; these attributes cannot be changed

Locked Attributes = Author, Author Email

 

; only author can change its own entry

Restrict edit = 1

 

; options for reply

Subst on reply subject = Re: $Configuration Name

Remove on reply = Author, Author Email

 

; No Email notification

Suppress Email to users = 1

 

____________________________________________________________________

What can be done to resolve this problem?

  69368   Thu Jun 3 16:02:02 2021 Reply Sebastian Schenksebastian.schenk@physik.uni-halle.deQuestionWindows3.1.4-3Re: Problem with a self-compiled code.

Hello Maxim,

I just stumbled on a similar issue. Also with a self-compiled elogd on Ubuntu.

We also use a custom css and by clicking on the "New" or "Reply" or "Duplicate" the elog generates the entry editor.
On the first load of this page the link to the css file is sometimes corrupted by having some garbage characters in it.
<link rel="stylesheet" type="text/css" href="ƒŒüthemes/name.css">

I found the bug in the code and made a PR on the bitbucket. Here is the commit to fix it yourself.
https://bitbucket.org/merrx/elog/commits/cea193ded7161bb6d1f67725ca109d2d4341128a

Best wishes,
Sebastian

Maxim wrote:

Dear, sir! There is a problem with a configuration file.

The code was compiled by Cygwin (gcc-core, gcc-g++, make, gdb, libssl-dev).  After a compilation a reference to our own css-file was written in configuration file and css-file was included in a folder “themes/default” of the project.

The problem is that in running elog-3.1.4-1 (and upper versions) css-file name in a code of a page has some random symbols before file-name, for example: <link rel="stylesheet" type="text/css" href="ø9öÿeLogOUK.css">. It was found that the problem is resolved if a string “Password file=passwd” is deleted, but in this case it is impossible to set passwords to the users.

Here is an example of configuration file which is taken from the forum and just one string (CSS=elogOUK.css) has added to the code

____________________________________________________________________

What can be done to resolve this problem?

 

  69376   Wed Jun 23 14:08:15 2021 Reply Maximmaxsimuus69@gmail.comQuestionWindows3.1.4-3Re: Problem with a self-compiled code.

Good afternoon Sebastian!
Thank you very much for your help.

Sebastian Schenk wrote:

Hello Maxim,

I just stumbled on a similar issue. Also with a self-compiled elogd on Ubuntu.

We also use a custom css and by clicking on the "New" or "Reply" or "Duplicate" the elog generates the entry editor.
On the first load of this page the link to the css file is sometimes corrupted by having some garbage characters in it.
<link rel="stylesheet" type="text/css" href="ƒŒüthemes/name.css">

I found the bug in the code and made a PR on the bitbucket. Here is the commit to fix it yourself.
https://bitbucket.org/merrx/elog/commits/cea193ded7161bb6d1f67725ca109d2d4341128a

Best wishes,
Sebastian

Maxim wrote:

Dear, sir! There is a problem with a configuration file.

The code was compiled by Cygwin (gcc-core, gcc-g++, make, gdb, libssl-dev).  After a compilation a reference to our own css-file was written in configuration file and css-file was included in a folder “themes/default” of the project.

The problem is that in running elog-3.1.4-1 (and upper versions) css-file name in a code of a page has some random symbols before file-name, for example: <link rel="stylesheet" type="text/css" href="ø9öÿeLogOUK.css">. It was found that the problem is resolved if a string “Password file=passwd” is deleted, but in this case it is impossible to set passwords to the users.

Here is an example of configuration file which is taken from the forum and just one string (CSS=elogOUK.css) has added to the code

____________________________________________________________________

What can be done to resolve this problem?

 

 

  69377   Wed Jun 23 15:28:00 2021 Question Maximmaxsimuus69@gmail.comQuestionWindows3.1.4-3Timezome problem

Good afternoon!

The elog does not see the time zone. It displays UTC + 0. When I transfer old entries to a new compiled log, they are displayed 3 hours earlier (my time zone is UTC + 3). When creating a new record, it creates them in the UTC + 0.

Compilation occurs in Cygwin.

Version elog – 3.1.4-3.

Please help solve this problem.

ELOG V3.1.5-3fb85fa6