Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 724 of 796  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6362 Entries 
Goto page Previous  1, 2, 3 ... 723, 724, 725 ... 794, 795, 796   Next  
ID Date Icon Authorup Author Email Category OS ELOG Version Subject
  69187   Sun Aug 2 02:57:59 2020 Reply VUIIS SysAdminvuiis-sysadmin@vumc.orgQuestionLinuxELOG V3.1.4-966Re: Missing log files when rsync to replacement server.

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.

 

  490   Mon Mar 1 16:49:34 2004 Question Val Schmidtvschmidt@ldeo.columbia.eduQuestionLinuxelog-2.5.1-1top text/bottom text
Hello,

I have a quick question regarding how to display text using the "Top text" 
feature in the elogd.cfg file.  I've made an entry that looks like the 
following:

Top text = <h1>TEXT TO DISPLAY</h1>

But instead of getting just "TEXT TO DISPLAY" I get something like this:

----begin page ---
/usr/local/elog         "TEXT TO DISPLAY"

...rest of page 

----end page ---

...that is, on the far left at the top of the page in unformatted text 
is "/usr/local/elog/" prepended to the text I want do display. 

I don't know if this is a bug, or (more likely) something misconfigured in 
my setup. But any help that could be provided would be most greatful.

Thanks,

Val
  492   Mon Mar 1 17:26:34 2004 Reply Val Schmidtvschmidt@ldeo.columbia.eduQuestionLinuxelog-2.5.1-1Re: top text/bottom text
> This was a bug which only occurs under certain conditions, that's why nobody 
> has seen it yet. I fixed it, the new version is available under CVS:
> 
> http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.275

Great! 

I'm inclined to wait until you release a new rpm with the changes, as I'm 
likely to mucky things up by trying to upgrade from the cvs archive rather than 
using the rpm mechanics. 

But glad to hear it's fixed.  

By the way, ELOG is a fantastic tool. I'm very thankful for all the effort gone 
into it. I do wish there were standard sql hooks, as I'm a bit fearful of how 
it will scale. But the front-end, which is often most neglected, is well 
thought out.  Thanks so much, Val
  65677   Mon Dec 17 02:17:20 2007 Question Val Schmidtvschmidt@ccom.unh.eduQuestionMac OSX2.6.1Moving a logbook from one installation to another

I've attempted to move a logbook from an old elog installation to a new one on another system. The version of elog is the same (2.6.1) in both. Both systems have the same name and the logbooks are and installation are going in the same place. So all paths are identical. Also, for the new installation, I've simply recompiled the same sources used to install the original one. The only difference is an upgrade in the OS.
 
I've rsync'd the directory and contents from the old installation to the logbooks/ directory for the new one. I then over-wrote the standard config file with the new one. I then started elogd in the new place.
 
What I find is 
 
a) The default entry from the demo logbook is inserted into my logbook. This I can live with but it was unexpected.
b) The dates for all my entries as shown in my browser have years starting in 1946, rather than 2006. This is particularly odd since all of the actual log files have the correct dates. 
c) The numbering of entries has been reset to 1.
 
 
Can anyone explain what I've done to mucky this up and how to fix it?
 
Thanks in advance,
 
Val
 

  65679   Mon Dec 17 19:18:13 2007 Reply Val Schmidtvschmidt@ldeo.columbia.eduQuestionMac OSX2.6.1Re: Moving a logbook from one installation to another

 

 

Stefan, I'm still stumped. I'm sorry for the hassle. 

I've removed all the demo entries from both my logbook and the demo. I restarted elog in verbose mode and everything seems normal. I've even run the binary from my old elog installation on the config and logbooks in the new place and it works like a champ.

So I think I've concluded that my new compilation is mucky'd up. The logbooks and config file are fine.

So for the record, the new installation is on MacOS 10.5 (Leopard). The compiler is gcc4.0. There is one warning when I compile:

src/elog.c: In function 'url_encode':
src/elog.c:209: warning: pointer targets in passing argument 2 of 'strlcpy' differ in signedness
 

But this is not likely the problem.
 
So I stuck a debug statement into the code and recompiled to see the dates that are read from the logbook. Here is what I found:
 
DEBUG: Thu Nov 08 18:37:57 2001
DEBUG: Sun, 09 Apr 2006 12:38:31 +52175311
DEBUG: Sun, 09 Apr 2006 12:41:17 +52175311 
DEBUG: Mon, 10 Apr 2006 09:24:26 +52175311
DEBUG: Mon, 10 Apr 2006 09:29:50 +52175311
DEBUG: Mon, 10 Apr 2006 16:15:31 +52175311
DEBUG: Mon, 10 Apr 2006 18:22:16 +52175311
DEBUG: Mon, 10 Apr 2006 18:23:20 +52175311

 

I haven't yet been able to figure out what this last number is and if it should indeed be part of the date. Any ideas here?

Thanks,

-Val

 

Stefan Ritt wrote:

 

Val Schmidt wrote:

I've attempted to move a logbook from an old elog installation to a new one on another system. The version of elog is the same (2.6.1) in both. Both systems have the same name and the logbooks are and installation are going in the same place. So all paths are identical. Also, for the new installation, I've simply recompiled the same sources used to install the original one. The only difference is an upgrade in the OS.
 
I've rsync'd the directory and contents from the old installation to the logbooks/ directory for the new one. I then over-wrote the standard config file with the new one. I then started elogd in the new place.
 
What I find is 
 
a) The default entry from the demo logbook is inserted into my logbook. This I can live with but it was unexpected.
b) The dates for all my entries as shown in my browser have years starting in 1946, rather than 2006. This is particularly odd since all of the actual log files have the correct dates. 
c) The numbering of entries has been reset to 1.
 

 

That sounds really strange. The only thing I can think of is that the demo entry conflicted with your other entries and two of them have the same entry ID. The entry ID is a unique key which identifies each entry. If you look into the raw logbook file 011108a.log with a text editor, you will see them as

$@Mid@$: 1
Date: Thu Nov 08 18:37:57 2001
Author: Stefan Ritt
Type: Routine
Category: General
Subject: Welcome
Attachment:
Encoding: ELCode
========================================
[B]Congratulations for installing ELOG sucessfully!
[/B]

This is a demo entry to ensure the elogd server is working correctly.
Click [I]"New"[/I] to add new pages and [I]"Delete"[/I] to delete this page.

so in this case the ID is 1. When you rsync'ed your entries into the demo logbook directory, you probably got two entries with the ID 1, which screws up elogd. Try to delete the file 011108a.log before you do the rsync. If you start elogd interactively with the "-v" flag, you will see some debugging output which can you help identify some problems:

[ritt@pc5082 ~/elog]$ ./elogd -v
elogd 2.7.0 built Dec 13 2007, 08:05:12 revision 1977
Config file  : /afs/psi.ch/user/r/ritt/elog/elogd.cfg
Resource dir : /afs/psi.ch/user/r/ritt/elog
Logbook dir  : /afs/psi.ch/user/r/ritt/elog/logbooks/
Indexing logbook "demo" in "logbooks/demo/" ...

Config [demo],                           MD5=F2E39262960C779517FEE576C17B1ED0

Entries:
  ID   1, 011108a.log, ofs     0, thead, MD5=81D89C3C94C6626BB7FF191026040E83
After sort:
  ID   1, 011108a.log, ofs     0
ok
Server listening on port 8080 ...

 

 

  66236   Wed Mar 4 22:47:46 2009 Question Val Schmidtvschmidt@ldeo.columbia.eduQuestionAll2.7.5Email authentication with SSL/TLS

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...

  66287   Mon Apr 6 20:46:42 2009 Question Val Schmidtvschmidt@ldeo.columbia.eduQuestionAll2.6.2Specifying the size of am image attachment

 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

  68448   Fri Oct 28 16:30:36 2016 Question Val Schmidtvschmidt@ccom.unh.eduQuestionAll3.1.1Reset a user's password

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

Thanks,

Val

Goto page Previous  1, 2, 3 ... 723, 724, 725 ... 794, 795, 796   Next  
ELOG V3.1.5-fe60aaf