Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 514 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  67433   Mon Feb 11 14:21:05 2013 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.2-2475Re: elog's image manipulation of .png file generated from a pdf/jpg
> Well I didn't crash the server this time, and I could invert the image in the demo logbook by doing two rotations.
> But, this is elog v2.9.0-2435, and I am using v2.9.2-2475.  And I remember there was a recent issue about the image manipulation at some point, so I went to the
> download section to read the subversion listing to find where this occurred.  But you've changed subversion!  I couldn't find my way around it, so I not only could
> I find the changefile that showed what happened for each subversion issue, but even how I could download the current (or indeed any past) subversion issue.
> 
> As far as I can recall, you made a change, I reported an issue, and you undid the change, or partially undid it.  Do you know when this was?  Could it be relivent?

I upgraded to V2.9.2, so please try again.

/Stefan
  67438   Mon Feb 18 20:12:25 2013 Reply Tom Langfordtlangfor@umd.eduQuestionLinux2.9.1-2435Re: Protect Selection page=1

Ocane wrote:

 Hi,

I have several top groups and each has several logbooks.

If I use the global option Protect Selection page=1 and Show top groups = 1, after an user logs in to the top group selection URL, the elog steers away from the top group selection page, and automatically brings him to the logbook selection page of the first top group. Is the elog programmed to exhibit this behavior?

What I would prefer is that, after an user logs in, the elog stays on the top group selection page, sine each user has his preferred destination, not always the logbooks in the first top group. Is there any setting I can use in the config file to do this? 

(My users need to access different top groups and logbooks on regular basis).

Thank you and regards.

 I am currently having a similar problem. I am migrating a few separate elogs to one new computer. I have three top groups set up with their own password files. If I log into top group A (TGA), and then try to go to top group B (TGB), I am presented with a "Create new user" screen for my login name for TGA. When I complete that form, I am taken to the user settings for top group A, rather than TGB. I can log out of TGA and then log into TGB fine, but if I try to switch between them without logging out, it freaks out.

There seems to be a problem with the cookies that keep me logged into the different top groups not recognizing that they are different entities. I'm running eLog 2.9.1 rev 436. Is it possible that this has been addressed in 2.9.2?

Thanks,

-t

  67439   Tue Feb 19 09:13:34 2013 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.1-2435Re: Protect Selection page=1

Tom Langford wrote:

Ocane wrote:

 Hi,

I have several top groups and each has several logbooks.

If I use the global option Protect Selection page=1 and Show top groups = 1, after an user logs in to the top group selection URL, the elog steers away from the top group selection page, and automatically brings him to the logbook selection page of the first top group. Is the elog programmed to exhibit this behavior?

What I would prefer is that, after an user logs in, the elog stays on the top group selection page, sine each user has his preferred destination, not always the logbooks in the first top group. Is there any setting I can use in the config file to do this? 

(My users need to access different top groups and logbooks on regular basis).

Thank you and regards.

 I am currently having a similar problem. I am migrating a few separate elogs to one new computer. I have three top groups set up with their own password files. If I log into top group A (TGA), and then try to go to top group B (TGB), I am presented with a "Create new user" screen for my login name for TGA. When I complete that form, I am taken to the user settings for top group A, rather than TGB. I can log out of TGA and then log into TGB fine, but if I try to switch between them without logging out, it freaks out.

There seems to be a problem with the cookies that keep me logged into the different top groups not recognizing that they are different entities. I'm running eLog 2.9.1 rev 436. Is it possible that this has been addressed in 2.9.2?

Thanks,

-t

Certainly 2.9.1 and 2.9.2 should behave similar in that respect. Have you tried to clear all cookies in your browser and try again?

/Stefan 

  67440   Tue Feb 19 09:14:22 2013 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.1-2435Re: Protect Selection page=1

Ocane wrote:

 Hi,

I have several top groups and each has several logbooks.

If I use the global option Protect Selection page=1 and Show top groups = 1, after an user logs in to the top group selection URL, the elog steers away from the top group selection page, and automatically brings him to the logbook selection page of the first top group. Is the elog programmed to exhibit this behavior?

What I would prefer is that, after an user logs in, the elog stays on the top group selection page, sine each user has his preferred destination, not always the logbooks in the first top group. Is there any setting I can use in the config file to do this? 

(My users need to access different top groups and logbooks on regular basis).

Thank you and regards.

There is currently no way to change this in the config file. I will review the issue when I get some time and maybe come up with a fix. 

  67448   Thu Feb 21 13:41:25 2013 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinuxELOG V2.9Re: Multiple versions of elog on one server

David Pilgram wrote:

Chris Smith wrote:

Is there a way of having multiple copies of elog running on one windows 2003 server? different ports?

I need to access 2 different elogd.cfg files.

[...] However, I was soon asked questions by Andreas as to how I found this running, as he had encountered problems with an earlier version.  To be honest, that stopped me experimenting too far with this at that point, as well as a coincidental upgrading of my hardware. [...]

Just for completeness: I was running two elogd servers (2.9.0) on one Linux host in order to provide an english and a german web interface to the same logbooks, synchronised by the mirror server mechanism.

That didn't work out well, the elogd crashed infrequently. But of course mirror servers are not intended to run on the same host. Eventually I've just dropped the english server.

 
Detect language » English
 
  67452   Thu Feb 21 23:23:19 2013 Question Mark Bergmanmark.bergman@uphs.upenn.eduQuestionLinux2.92any way to undelete entries?

 Is there any way within eLog to undelete entries?

  67453   Fri Feb 22 08:19:27 2013 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.92Re: any way to undelete entries?

Mark Bergman wrote:

 Is there any way within eLog to undelete entries?

No. 

  67454   Fri Feb 22 10:58:18 2013 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.92Re: any way to undelete entries?

Mark Bergman wrote:

 Is there any way within eLog to undelete entries?

 I wrote to scripts to backup the logbook files:

  • elog_backup_daily creates a tar file of all new entries of the last 25 hours and keeps these backups for 90 days
  • elog_backup_hourly creates a tar file of the entries of the last 65 minutes and keeks these backups for one week
  • exclude-logbooks specifies which files not to backup

This allows you at least to recover deleted entries by hand as an administrator.

 
Detect language » English
 
 
Detect language » English
 
 
Detect language » English
 
 
Detect language » English
 
 
Detect language » English
 
Attachment 1: elog_backup_daily
#!/bin/sh
# source file directory
srcd=/usr/local/elog/

# backup all files newer than 25 hours
date=$(date -d "-25hours" "+%Y%m%d %H:%M")
# backup file directory
tard=/logbooks_backup
# backup tar file name
tarf=$tard/$(date +%Y%m%d_%a.tar)
# do not backup files that match patterns in this file
excf=/usr/local/elog/utilities/exclude-logbooks
# create backup
cd $srcd
tar --ignore-case -X $excf --newer "$date" -cf $tarf . logbooks/*

# copy passwd.txt
if [ "$(date +%u)" -eq 1 ]
then
	passwd=$tard/passwd_$(date +%Y%m%d_%a.txt)
	cp $srcd/passwd.txt $passwd
	gzip -9 $passwd
fi
# delete all backups older than 90 days
find $tard -mtime +90 -name "*_???.tar"           -exec rm -f {} +
find $tard -mtime +90 -name "passwd_*_???.txt.gz" -exec rm -f {} +
Attachment 2: elog_backup_hourly
#!/bin/sh
# source file directory
srcd=/usr/local/elog/

# backup all files newer than 25 hours
date=$(date -d "-65minutes" "+%Y%m%d %H:%M")
# backup file directory
tard=/logbooks_backup
# backup tar file name
tarf=$tard/$(date +%a%H%M.tar)
rm -f $tarf
# do not backup files that match patterns in this file
excf=/usr/local/elog/utilities/exclude-logbooks
# create backup
cd $srcd
tar --ignore-case -X $excf --newer "$date" -cf $tarf . logbooks/*
Attachment 3: exclude-logbooks
*.png.png
*.gif.png
*.jpg.png
*.pdf.png
oldLogbooks/*
logbooks/elog.log
passwd.txt
ssl/*
logbooks/Backup/*
logbooks/old/*

ELOG V3.1.5-3fb85fa6