Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 234 of 796  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Authorup Author Email Category OS ELOG Version Subject
  66538   Tue Sep 8 14:59:30 2009 Reply Gillian Sabbertonelog@gks.thamespower.comOtherOther?Re: Elog stopped working

Stefan Ritt wrote:

Gillian Sabberton wrote:

We have been running elog for a couple of years now and this morning it stopped working.

We have tried to rstart it and it says successful start but still does not run, when doing a restart it says stop failed start success.

Does anyone have any ideas.

thanks

You shoudl start elogd interactively in a DOS box to see if there is any error. Maybe disk full or a network problem... 

 It is running on a linux box, we have started in it in a telnet session, and no errors appear, as I am new to e-log is there an error log anywhere.

  66543   Mon Sep 14 13:04:57 2009 Agree Gillian Sabbertonelog@gks.thamespower.comOtherOther?Re: Elog stopped working

Gillian Sabberton wrote:

Stefan Ritt wrote:

Gillian Sabberton wrote:

We have been running elog for a couple of years now and this morning it stopped working.

We have tried to rstart it and it says successful start but still does not run, when doing a restart it says stop failed start success.

Does anyone have any ideas.

thanks

You shoudl start elogd interactively in a DOS box to see if there is any error. Maybe disk full or a network problem... 

 It is running on a linux box, we have started in it in a telnet session, and no errors appear, as I am new to e-log is there an error log anywhere.

 Have fixed this by removing the last added user from the Passwd file.

  66544   Mon Sep 14 13:05:35 2009 Agree Gillian Sabbertonelog@gks.thamespower.comOtherOther?Re: Elog stopped working

Gillian Sabberton wrote:

Stefan Ritt wrote:

Gillian Sabberton wrote:

We have been running elog for a couple of years now and this morning it stopped working.

We have tried to rstart it and it says successful start but still does not run, when doing a restart it says stop failed start success.

Does anyone have any ideas.

thanks

You shoudl start elogd interactively in a DOS box to see if there is any error. Maybe disk full or a network problem... 

 It is running on a linux box, we have started in it in a telnet session, and no errors appear, as I am new to e-log is there an error log anywhere.

 Have fixed this by removing the last added user from the Passwd file.

  68834   Thu Aug 16 13:33:39 2018 Question Gino Guenzburgergino.guenzburger@empa.chQuestionWindows3.1.3Changing of entries after expired time restriction by synchronisation

I'm working on setting up an elog as lab-journal in our group with the following set-up:

  • The elog is running on a server, with no back-end access for the users.
  • Multiple people will use it, all loging in with the same user-name and password.
  • The entries submitted to the log-book can only be edited for 24hours, as defined by the "Restrict edit time= 24" setting in the configuration file.

Now I encountered the following problem in my set-up: Entries that do not have attachments can be changed after these 24hours have passed, by the following set-up: If a user (in the current case me during testing) sets up a local elog on his computer and activates the synchronisation with the elog on the server, he can switch off the time-restriction for editing on his local elog, and if he synchronises the two log-books, the changed entry from the local elog will overwrite the original one from the server-elog.

Obviously this is not very desirable. Therefore I wanted to ask, whether anyone sees a possibility to prevent the editing of entries, which are older than the restricted edit time. A specific function or a change in the synchronisation behaviour would of course be the completest solution, but in my case the problem would also be solved if I could just prohibit the synchronisation. It is not needed, so no harm will be done if it is not possible.

 

  Draft   Wed Feb 19 17:43:34 2020 Question Gino Guenzburgergino.guenzburger@empa.chBug reportAll3.1.4Re: Find cannot find values with brackets

Hi Stefan

we are running elog

Stefan Ritt wrote:

I‘m happy to merge the PR after a quick test next week.

Stefan

Sebastian Schenk wrote:

For demonstration, I created https://elog.psi.ch/elogs/Linux+Demo/8

The Find search for category aaa(bb) does not give results.
A quick filter corrects the value to aaa\(bb) and delivers results.

I made a simple fix and submitted it as PR to the bitbucket repository.

 

 

  1609   Thu Jan 19 15:02:38 2006 Question Giorgio Croci Candianig.crocic@libero.itBug report 2.6.1Access to global configuration in v2.6.1
Hi,
I just installed v.2.6.1 coming from the previous 2.6.0 (on Win2000)
When I access the "configuration" function from a logbook, in the cfg page I only see two buttons in the header
(save or cancel); in the previous version I saw more buttons there ("global config", "create new logbook" and so
on), so here I'm unable to access global configuration or logbook management (except for current logbook options).
I am logged in as admin (actually I have a single-user configuration, thus no particular users defined).
I hope this report may be helpful, and not just being caused by a misunderstanding on my side ;)
Thanks
GiorgioCC
  1616   Sat Jan 21 14:02:57 2006 Reply Giorgio Croci Candianig.crocic@libero.itBug report 2.6.1Re: Access to global configuration in v2.6.1
 
> I tried to reproduce your problem, but could not. In my windows installation it looks fine. You only see the
> (save and cancel) buttons only if you go to "Change [global]", otherwise you see the "Change [global]", "Delete
> this logbook" etc. buttons. Have you tried with the default elogd.cfg which comes from the distribution?

Yes, I tried that. Maybe I'll have some other try on other PCs and investigate further, I'll surely let you know. Thanks
for the prompt response and compliments for your very good work! ELog is really a great piece of software.
  1626   Wed Jan 25 01:08:06 2006 Reply Giorgio Croci Candianig.crocic@libero.itBug report 2.6.1Re: Access to global configuration in v2.6.1
> > I just installed v.2.6.1 coming from the previous 2.6.0 (on Win2000)
> > When I access the "configuration" function from a logbook, in the cfg page I only see two buttons in the header
> > (save or cancel); in the previous version I saw more buttons there ("global config", "create new logbook" and so
> > on), so here I'm unable to access global configuration or logbook management (except for current logbook options).
> 
> I tried to reproduce your problem, but could not. In my windows installation it looks fine. You only see the
> (save and cancel) buttons only if you go to "Change [global]", otherwise you see the "Change [global]", "Delete
> this logbook" etc. buttons. Have you tried with the default elogd.cfg which comes from the distribution?

Here I am again... I built and installed v2.6.1 also on a different system, this time on linux; i tried both with the
existing cfg file and with the new cfg.
Choosing "configuration", I still only see the current logbook configuration file section with "Save" and "cancel"
buttons, no access to global config whatsoever; the same as I saw on windows version. I tried version 2.6.1-1622.
Regards
Giorgio
ELOG V3.1.5-2eba886