Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 74 of 807  Not logged in ELOG logo
icon5.gif   Email authentication with SSL/TLS, posted by Val Schmidt on Wed Mar 4 22:47:46 2009 

Hi,

I'm curious is it possible to send email notificaitons from elog through an smtp server that requires SSL/TLS authentication? I think it's not but I thought I'd ask.

 

-Val

 

ps. sorry for the initial blank post...

icon5.gif   Specifying the size of am image attachment, posted by Val Schmidt on Mon Apr 6 20:46:42 2009 

 Hello,

I'm curious, is it possible to specify (perhaps by default) the rendered size of an attached image. For example, I'd like all images uploaded to be scaled to 100% of the browser window size so a large image is not most off the screen. What I want is to specify the width="100" attribute of the <img /> tag, but it's not clear 1) how do to this for an attachment and 2) if it might be possible to do this in the config file for all img attachments.

 

Thanks,

 

Val

icon5.gif   Reset a user's password, posted by Val Schmidt on Fri Oct 28 16:30:36 2016 

Is it possible for an administator to reset a user's password? 

Thanks,

Val

icon5.gif   ELOG reverts to demo configuration, posted by VUIIS SysAdmin on Thu Feb 20 16:54:32 2020 

I have been using elog for over 10 years. Suddenly my elog installation has changed (probably from a recent update. My /etc/elogd.cfg has changed to the original demo configuration. Even after changing it to my configuration from backup none of the entries for the logbooks apper even though the tabs for the logboos are ther all logbooks are empty. I have looced at the logbook files and the entries seem to be there but are not showing on the web interface. Has something changed? Is there a new location for the logbooks and other files? Is there a change from the 32-bit to the 64-bit version that will cause this. I am running CentOS 7 fully patched and updated. Will there be a CentOS 8 compatible version?

icon5.gif   Missing log files when rsync to replacement server., posted by VUIIS SysAdmin on Thu Jul 30 17:11:05 2020 

I am moving from a Hyper-V host to a VMware host and created a new elog server. I installed the elog software and did an rsync to get the .cfg file and logbooks to the new server.

rsync -av root@old.elog.server:/usr/local/elog /usr/local/
 

On the new server all of the 2020 entries are missing and there does not appear to be a 2020 logbook on either server but I can still access the 2020 entries on the old server. Where might they be and how do I get them over to the new server.

 

Old server says version is ELOG V3.1.4-unknown and new server says version is ELOG V3.1.4-966e3dd

Bothe servers a fully updated CentOS 7.

    icon2.gif   Re: Missing log files when rsync to replacement server., posted by VUIIS SysAdmin on Fri Jul 31 21:40:02 2020 

On the new server in the logbook that should have several 2020 entries it stops on the last entry of 2019.

On the old server after stopping elogd i get:

/usr/sbin/elogd -v 3

Cannot open "elogd.cfg": No such file or directory

Are the files supposed to be in /usr/local/elog or /usr/share/elog? I have both on the old server. I only synced /usr/local/elog to the new server. In any case the Logbook with 2020 entries does not show a 2020 directory.

My backup system also does not show any 2020 logbook directories. It was current up to this week when I started this process.

 

Stefan Ritt wrote:

Start your new server interactively with "elogd -v 3" to see all verbose output. You will then see how it indexes all logbooks. If not, you might have a wrong path in elogd.cfg

VUIIS SysAdmin wrote:

I am moving from a Hyper-V host to a VMware host and created a new elog server. I installed the elog software and did an rsync to get the .cfg file and logbooks to the new server.

rsync -av root@old.elog.server:/usr/local/elog /usr/local/
 

On the new server all of the 2020 entries are missing and there does not appear to be a 2020 logbook on either server but I can still access the 2020 entries on the old server. Where might they be and how do I get them over to the new server.

 

Old server says version is ELOG V3.1.4-unknown and new server says version is ELOG V3.1.4-966e3dd

Bothe servers a fully updated CentOS 7.

 

 

    icon2.gif   Re: Missing log files when rsync to replacement server., posted by VUIIS SysAdmin on Sun Aug 2 02:57:59 2020 

Thank-you. That is good information to have. 

What is the default if you you do not specify anything in elogd.cfg? I assume it is  /usr/local/elog otherwise it would not see the existing logbooks.

With a default Linux RPM install, where else would the logbooks be? Still looking for a 2020 directory on either server.

Bruce

Stefan Ritt wrote:

You can put your files where ever you want, just tell elogd where to find the elogd.cfg file via the "-c" flag. Then tell elogd where to find files in the elogd.cfg file via the "Logbook dir" and "Resource dir" directives.

Stefan

VUIIS SysAdmin wrote:

On the new server in the logbook that should have several 2020 entries it stops on the last entry of 2019.

On the old server after stopping elogd i get:

/usr/sbin/elogd -v 3

Cannot open "elogd.cfg": No such file or directory

Are the files supposed to be in /usr/local/elog or /usr/share/elog? I have both on the old server. I only synced /usr/local/elog to the new server. In any case the Logbook with 2020 entries does not show a 2020 directory.

My backup system also does not show any 2020 logbook directories. It was current up to this week when I started this process.

 

icon5.gif   Unable to add user, posted by Uwe Vollbracht on Sat Aug 6 18:38:50 2022 
Hi,

we're using elog to handle various logbooks. It's a great tool by the way. 
While replacing the Win32 2.7.8 Release with Release 3.1.4-2, we ran into the 
following problem.

Since elog is for internal usage only, we allow users to self-register if they 
are new. Therefore  "Self register = 1" is set in the [global]-area.

Using the Win32-Release of elog, it worked fine while using Release 2.7.8 or 
2.8.0. Starting with Release 3.x everytime you try do add a user, the following 
error occurs:

      Error: Command "config" is not allowed for user ""

No matter if the user self-registers or is added by an elog-admin-user. We 
tried various 3.x Releases from 3.1.0-1 up to the latest 3.1.4-2. 
The error-message remains the same. Curious, although an error-message occurs, 
the user is added and able to use all logbooks. We also ran elogd in 
Debug-Mode (-v3), but the output didn't give a clue.

By the way using the same configuration on a linux-based installation (Debian 
and RaspiOS) self-registration works smooth. No error-message occurs.

So what could be the problem? Any suggestion is greatly appreciated.

Thanks in advance. 
ELOG V3.1.5-3fb85fa6