Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 762 of 806  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  67132   Wed Sep 28 22:10:30 2011 Question Graham Medlinglmedlin@ncsu.eduQuestionLinux2.9.0-2411Digest page or email?

We have about 10 logbooks running on the same Elog that all get fair use. Many people have turned off new entry emails because they were filling up inboxes, but are still interested in what's new. I saw the option to add "?last=1" to the start page, although I'm afraid using it might cause confusion over how to get to the older posts.

I was trying to figure out a way of creating a "digest" of sorts, a list of entry subjects posted in the past day or week, something similar to what's generated by "?last=1?mode=threaded", but for every logbook (similar layout to the selection page with nested logbooks). This could either be a page, or a regular email.

Is there way to generate such a cross-logbook page? What about a scheduled email formatted based on a given filter?

PS: The elog has been invaluable to us, a big thanks to all involved!

  67959   Fri Jun 5 14:24:34 2015 Idea Stefan Rittstefan.ritt@psi.chInfoAll3.1.0+Different way CSS files are handled

Hi,

I just implemented a different way CSS files are handled in ELOG. Previously, we had the default.css, which could be adjusted for specific needs. Some people did that (like myself). So I changed a few colors etc. When I now implement a new feature in elog, it might need a new CSS class which I put in default.css. But this means that people who have modified this file get it either overwritten, or do not get the new styles.

In order to fix this, the default.css is now called elog.css and is always inluded in any ELOG page. If one specifies a CSS file with "CSS = <file.css>", then this CSS file is loaded in addition to elog.css. So one can put only the modifications into that file and inherits all the rest from elog.css. If new features come in elog.css, the installation with the personalized CSS file will then get the new features from the new elog.css automatically, and just overwrite a few settings in the personalized file. Here is an example:

elog.css:

td {
  color:black;
  font-size:12px;

}

Personalized file special.css, activated with "CSS = special.css" in the elogd.cfg file:

td {
  font-size:18px;
}

This personalized file now overwrites the font size from elog.css to 18 pixel, while maintaining all the rest from elogd.css.

The modification is committed to GIT and will be contained in the next release of elog.

/Stefan

  68006   Wed Jun 10 17:30:34 2015 Entry gary holmanholman@uw.eduQuestionLinuxV2.9.1-244Different timezone settings for each elog

I have multiple elogs running on a server.  Is it possible to set one elog to a different timezone?  For example, I run an elog for a group in Washington state, and another elog for a collaboration group in Germany.  I would like to set each elog to their respective timezone. 

thanks,

 

Gary

  68364   Thu Jul 21 07:44:04 2016 Question Antonio Bulgheroniantonio.bulgheroni@gmail.comQuestionWindows2.9.2Different logbook files when running elogd as admin or normal user

Dear all, I have a problem with my window elog installation (2.9.2) and I would like to ask your help for solving it.

I'm using elog on my lab computer for a single user installation, so something very simple. It was running smoothly for many months using the automatic window service (i.e. elogd was started automatically at boot). I need to add that the service is started as the local administrator, while my user has no administrative rights. ELOG is installed in the standard location C:\Program Files (x86)\ELOG\ with the logbook folder inside and this is actually accessible only for admins.

On 8/04/2016, elogd crashed while I was saving an edited message. Then instead of restarting the service or rebooting the PC, I was just starting elogd manually (as me not as admin). It worked for many weeks. And now comes the problem: at the next reboot the elogd service came up automatically but all the new records I added in the logbook since I re-started manually are not there. Indeed in the C:\Program Files (x86)\ELOG\logbooks the latest entry is 160408a.txt. But if I stop the service and restart elogd manually (as me not as admin), then I can see in the logbook all the new entries.

My questions is where the ascii files corresponding to the new entries? They must be saved somewhere, maybe in some temporary folder. I want to copy them back and keep them in the backup to avoid unpleasant surprise.

Thanks in advance for your help,

Antonio

  69079   Mon Jan 20 13:46:56 2020 Question matthieu hellermatthieu.heller@unige.chQuestionLinux3.1.4Different behaviours to identical configuration of logbooks for email notification

Dear,

I need to setup automatic email notification using direct send through a office365 smtp server.
This part worked without any issue after setting the right MX record as SMTP host.
As I am working on the configuration file while it is already use, I created a copy of the [GENERAL] logbook to make my tests called [GENERAL COPY] (see attachement and below for the config file).

Surprisingly I manage to send the email without errors using [GENERAL COPY] but not in [GENERAL]. In that case, I get this error message:
Error sending Email via <i>"cta####-####.mail.protection.outlook.com"</i>: 4.5.3 Recipients belong to multiple tenants [AM5EUR02FT024.eop-EUR02.prod.protection.outlook.com]

In that case, I was actually not sending the mail to a mailing list but to myself, a registered user.

Do you see any reason why two identical logbooks (except for the name) would behave differently ?

Best,

elogd.cfg:

[global]
port = 8090
SSL = 0
Self register = 0
Welcome Title = <html><font size=5>Welcome to the LST1 Elog server</font></html>
Main Tab = Main Logbooks page
URL = #######
SMTP host = cta####-####.mail.protection.outlook.com
SMTP port = 25
Use Email From = mailing-list@cta-####.org
Display Email recipients = 0
Email message body      = 1

[GENERAL]
Theme = default
Comment = LST1 General ELOG
Attributes = Author, Type, Subject, Status
Options Type = Announcements, Shift Summary, Webserver, Plans, Safety, Operations, Interventions, Measurements, Structure, Issue
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed  = background-color:green
Cell Style Status Not Fixed  = background-color:red
Cell Style Status Under Process  = background-color:yellow
Extendable Options = Type
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status
Use Email Subject = $Type, $Subject
Email Type Webserver = mailing-list@cta-####.org
Email Type "Shift Summary" = mailing-list@cta-####.org
Admin user = camera
Password file = camera.pwd

[GENERAL COPY]
Theme = default
Comment = LST1 General ELOG
Attributes = Author, Type, Subject, Status
Options Type = Announcements, Shift Summary, Webserver, Plans, Safety, Operations, Interventions, Measurements, Structure, Issue
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed  = background-color:green
Cell Style Status Not Fixed  = background-color:red
Cell Style Status Under Process  = background-color:yellow
Extendable Options = Type
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status
Use Email Subject = $Type, $Subject
Email Type Webserver = mailing-list@cta-####.org
Email Type "Shift Summary" = mailing-list@cta-####.org
Admin user = camera
Password file = camera.pwd

Attachment 1: elogd.cfg
[global]
port = 8090
SSL = 0
Self register = 0
Welcome Title = <html><font size=5>Welcome to the LST1 Elog server</font></html>
Main Tab = Main Logbooks page
URL = #######
SMTP host = cta####-####.mail.protection.outlook.com
SMTP port = 25
Use Email From = mailing-list@cta-####.org
Display Email recipients = 0
Email message body      = 1

[GENERAL]
Theme = default
Comment = LST1 General ELOG
Attributes = Author, Type, Subject, Status
Options Type = Announcements, Shift Summary, Webserver, Plans, Safety, Operations, Interventions, Measurements, Structure, Issue
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed  = background-color:green
Cell Style Status Not Fixed  = background-color:red
Cell Style Status Under Process  = background-color:yellow
Extendable Options = Type
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status
Use Email Subject = $Type, $Subject
Email Type Webserver = mailing-list@cta-####.org
Email Type "Shift Summary" = mailing-list@cta-####.org
Admin user = camera
Password file = camera.pwd

[GENERAL COPY]
Theme = default
Comment = LST1 General ELOG
Attributes = Author, Type, Subject, Status
Options Type = Announcements, Shift Summary, Webserver, Plans, Safety, Operations, Interventions, Measurements, Structure, Issue
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed  = background-color:green
Cell Style Status Not Fixed  = background-color:red
Cell Style Status Under Process  = background-color:yellow
Extendable Options = Type
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status
Use Email Subject = $Type, $Subject
Email Type Webserver = mailing-list@cta-####.org
Email Type "Shift Summary" = mailing-list@cta-####.org
Admin user = camera
Password file = camera.pwd


[CAMERA]
Theme = default
Comment = LST1 Camera ELOG
Attributes = Author, Type, Category, Subject, Status
Options Type = ECC, TIB, CACO, EVB, UCTS, test, Fibers, Camera, ClusCo, DATA, CACO/ClusCO, Calib box, Camera Server, Monitoring, Backplane, Observation, Daily calibration, Dragon, Operation, Trigger Mezzanine, PDB, CDTS, Switches, Cooling
Options Category = General, Hardware, Software, Network, Other, Weather conditions
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed  = background-color:green
Cell Style Status Not Fixed  = background-color:red
Cell Style Status Under Process  = background-color:yellow
Extendable Options = Type, Category
Required Attributes = Author, Type
Reverse sort = 1
Quick filter = Date, Type, Status
Admin user = camera
Password file = camera.pwd

[AMC]
Theme = default
Comment = LST1 AMC ELOG
Attributes = Author, Type, Category, Subject, Status
Options Type = Software Installation, Problem Fixed, Hardware, Issues, pointing calibration
Options Category = General, Hardware, Software, Network, Other
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed  = background-color:green
Cell Style Status Not Fixed  = background-color:red
Cell Style Status Under Process  = background-color:yellow
Extendable Options = Type, Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status
Admin user = amc
Password file = amc.pwd

[ENERGY]
Theme = default
Comment = LST1 Energy ELOG
Attributes = Author, Type, Category, Subject, Status
Options Type = Software Installation, Problem Fixed, Hardware, Issues
Options Category = General, Hardware, Software, Network, Other
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed  = background-color:green
Cell Style Status Not Fixed  = background-color:red
Cell Style Status Under Process  = background-color:yellow
Extendable Options = Type, Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status
Admin user = energy
Password file = energy.pwd

[DRIVE]
Theme = default
Comment = LST1 Drive ELOG
Attributes = Author, Type, Category, Subject, Status
Options Type = Software Installation, Problem Fixed, Hardware, PLC Software and Configuration, Telescope Operations, Applications, Other, PLC + Control Software debugging, Tracking Debugging
Options Category = General, Hardware, Software, Other, Other_Debug, Issues
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed  = background-color:green
Cell Style Status Not Fixed  = background-color:red
Cell Style Status Under Process  = background-color:yellow
Extendable Options = Type, Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status
Admin user = drive

[Startup checklist]
Comment = Shift startup checklist
Attributes = Author, D, M, Y, suic1, suic2, suic3, suic4, suic5, suwa1, suwc1, suwc2, suwc3, supa1, supc1, supc2, supc3, supc4, supc5, supc6, supc7, supc8, supc9, supc10
Quick filter = Author
Enable attachments = 0
Show text = 0
Custom new form = /usr/local/elog/html/startup_list.html
Custom edit form = /usr/local/elog/html/startup_list.html
Custom display form = /usr/local/elog/html/startup_list.html
List after submit = 1
Admin user = camera
Password file = camera.pwd

[Shutdown checklist]
Comment = Shift shutdown checklist
Attributes = Author, D, M, Y, sdsa1, sdtc1, sdtc2, sdtc3, sdtc4, sdtc5, sdtc6, sdtc7, sdtc8, sdtc9, sdtc10, sdtc11, sdtc12, sdtc13, sdtc14, sdfa1, sdfa2, sdfa3, sdfa4
Quick filter = Author
Enable attachments = 0
Show text = 0
Custom new form = /usr/local/elog/html/shutdown_list.html
Custom edit form = /usr/local/elog/html/shutdown_list.html
Custom display form = /usr/local/elog/html/shutdown_list.html
List after submit = 1
Admin user = camera
Password file = camera.pwd

[GENERAL ELOG PROPOSAL]
Theme = default
Comment = LST1 General ELOG
Attributes = Author, Type, Category, System, Subsystem, Subject, Status
Options Type = Shift Summary, Report, Issue, Request, Announcements, Plans
Options Category = General, Observation, Safety, Maintenance, Intervention, Hardware, Software, Network, Other
Options System  = LST1{1}, Structure{2}, Camera{3}, Drive{4}, AMC{5}, IT{6}, Energy{7}
{1} MOptions Subsystem = Shift, Maintenance, Test
{2} MOptions Subsystem = Lower, Dish
{3} MOptions Subsystem = ECC, TIB, CACO, EVB, UCTS, Fibers, ClusCo, DATA, CACO/ClusCO, Calib box, Camera Server, Monitoring, Backplane, Observation, Daily calibration, Dragon, Operation, Trigger Mezzanine, PDB, CDTS, Switches, Cooling
{4} MOptions Subsystem = PLC, Telescope Operations, Applications, Control Software, Tracking
{5} MOptions Subsystem = CCD, AMC box, Pointing calibration
{6} MOptions Subsystem = Humidifier, Cooling
{7} MOptions Subsystem = UPS, Flywheel
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed  = background-color:green
Cell Style Status Not Fixed  = background-color:red
Cell Style Status Under Process  = background-color:yellow
Required Attributes = Author, Type, Category, System
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Category, System
Use Email Subject = $Type, $Subject
Email Type "Shift Summary" = mailing-list@cta-####.org
Email System Camera =  mailing-list@cta-####.org
Admin user = camera
Password file = camera.pwd
  69295   Tue Feb 2 04:01:21 2021 Question MATT TERRONmatao11235@gmail.comQuestionLinux | Windows3.1.4Different Top Groups or Groups have the same logbook name

I have built different top groups for different departments. But occasionally these different top groups have the same logbook name, say 'Maintenance Log'. So is there a way I can have the same logbook name under different 'Top Groups', rather than rename these logbooks as 'Department1 Maintenance Log' all the way to 'Department_X Maintenance Log'?

  67327   Wed Aug 29 22:44:39 2012 Question David PilgramDavid.Pilgram@epost.org.ukQuestionLinux2.9.2-2473Difference between time and date formats
Hi,

I hope I'm not missing the blindingly obvious here, but I have an issue with time and date formats

Extract from my elog.cfg file:


Time format = %a %d %b %y
Date format = %d %b
Thread display = $Ticket: $System, $entry time. ($message id). $status
Preset text = [$date]
Prepend on reply = [$date] \n

I can point to places in the syntax doc where each of these lines are given.

As for the results, the thread display is (for example):

T00001: Computer, Wed 29 Aug 12. (1). Problem

However, what I get at the top of the text box in starting a new entry or replying to a previous one is

[Wed 29 Aug 12]

whereas I expected to get

[29 Aug]

Putting $date instead of $entry time in the Thread display line makes (the by now expected) no difference

I cannot see where I'm going wrong.  

TIA 

David.
  69385   Mon Jul 19 18:41:29 2021 Question Janusz Szubajanusz.szuba@xfel.euQuestionLinux3.1.4Deny option and Guest commands

Hi, 

I have a logbook with guest access and guest can also enter a new entry (in config: Guest List Menu commands = New, Find, Select, Login). For other reason in a global section, I put 

Deny New = account1, account2

This somehow invalidates Guest List Menu commands, since as guest I don't see New button anymore. Is this behaviour desired? Otherwise, I would need to move Deny option to plenty of individual logbook configs. Just to explain the reason, those accounts are set up to only read entries and not to create new ones. Or maybe you can suggest a different solution?

Best

ELOG V3.1.5-3fb85fa6