Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 723 of 806  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  68676   Tue Aug 22 18:29:02 2017 Question Stefano Bonaldostefano.bonaldo.13@gmail.comQuestionMac OSXv3.1.2Hide logbook tab when not authorized

Hello, I read carefully the manual, but I didn't find a way to hide the logbooks in the logbook bar and in the initial logbook selection for which the user does not have the access. So, if a user1 does not have the access to a specific logbook, user1 is not able to see that logbook in the bar and neither in the initial logbook selection. How can I do this without using the top groups?

  68341   Thu Jun 23 15:57:34 2016 Question Rudy Taraschirudy.taraschi@L-3com.comQuestionLinux | Windows | Mac OSX | All | Other3.1.1Hide blank fields when displaying logbook entry

Hi, I have a logbook with attributes Tool1, Tool2, and Tool3.  When viewing a completed entry, what I want to do is see Tool2 or Tool3 only if they are non-zero, and don't want to see them if blank.  Basically, a "Hide if blank" option.  I couldn't find it - if it doesn't exist, are there any tricks to simulate it?

  1573   Wed Jan 4 12:26:31 2006 Question T. Ribbrockemgaron@gmx.netQuestionLinux2.6.0HelpELCode needs to be present in "Menu commands"?
Another little issue I came across was this: I'm using "Menu commands" and "Guest Menu commands" in my configuration. When I logged in and started to create a new entry, clicking on the URL that is behind "ELCode" at the bottom of the screen (and accesses the help for the ELCodes) resulted in a "command denied". The only way to get around this was to add "HelpELCode" to "Menu commands" - but now it also shows up in the menus, which is not what I want. Is there any way around this?
  929   Fri Feb 11 15:44:38 2005 Question Anand Senguptaanandss@iucaa.ernet.inQuestionLinux Help with configuration newbie
Hi,

We have set up a elog server at our institute. The configuration file is
attached. We have the following queries:

1. When replying to another reply in a thread, the author_name attribute is
not substitued (as desired). Since this is a mandatory field, we are not
able to send the reply message. However, reply to the originial message
works fine.

2. "Use Email From = string" prepends an additional "" to the "From"
field in the e-mails.

3. "Fixed Attributes Reply = Subject" fixes the subject line while replying.
However when we add "Category" attribute to this list, it breaks.

Can someone help us?

Suggestions and tips will be thankfully recieved.
Attachment 1: elog_config.txt
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;  CMB ELOG CONFIGURATION  ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

password file = cmb.pwd
Admin User = sarah, sengupta
Self register = 3
Menu commands = New, Edit, Reply, Find, Config, Admin, Change password, Download, Logout, Help
Find Menu commands = New, Edit, Reply, Find, Config, Admin, Change password, Logout, Help
Theme = default
Comment = Extended Hierarchical Search Pipeline Development

; -- A few flags
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
LogFile = /usr/local/epd.log
Filtered browsing = 0
Summary lines = 0
Resubmit default = 2
Restrict edit = 1

; -- Default mode for search display. On the find entry form, the checkboxes are set accordingly.
Display mode = threaded

; -- Number of logbook entries displayed per page in a search result. The default is 20.
Entries per page = 25

; -- Define a number of attributes for the logbook, separated by commata. Typical values are "Author", 
; -- "Subject" or  "Type".
Attributes = Author, Category, Subject
ROptions Category = General, Reference, Methods, Results, Query
Required Attributes = Author, Subject, Category

; -- preset author and email attributes
Preset Author = $long_name
Preset Author Email = $user_email

; -- add last revision on each edit
Subst on Edit Last Revision = $date by $long_name

; -- these attributes cannot be changed ever
Locked Attributes = Author, Last Revision

; -- We don't want a default email message to go to all the users
Suppress email to users = 0
Display Email recipients = 0
Use Email Subject = [ELOG] $subject
Use Email From = "$long_name <$user_email>"

; -- Options for edit (Author and email is already preset so we dont need to substitute those attributes)
Subst on edit subject  = $subject (revised)
Subst on edit category = $category

; -- The attributes specified here cannot be modified during Editing
Fixed Attributes Edit = Author, Author Email, Subject

; -- Options for reply (Anyone can reply so we must remove Author and email attributes from reply and substitute the 
; -- current logged in person's name and email id) 
Subst on reply subject = Re: $subject
Subst on reply category = $category
Subst on reply Author  = $long_name
Subst on reply Email = $user_email
Remove on reply = Author, Author Email

; -- The attributes specified here cannot be modified when an existing entry is modified via the Reply button
Fixed Attributes Reply = Subject

  65832   Thu Apr 17 05:28:56 2008 Warning Samrititmgr@samuiburi.comQuestion  Help me please I can't uplode Attach file

Dear All
I can't uplode Attach file. It have Error

Error: Filename "D:\aaa.doc" contains invalid character
Please use your browser's back button to go back

 

Thank you very much

Joe..

  2143   Tue Feb 20 18:41:31 2007 Entry Martin Killenbergmartin.killenberg@web.deCommentLinux2.6.4Hardcoded Path in Makefile
I tried to compile ELOG on Scientific Linux Cern 4.4 and found that make quits because uname is not located in /usr/bin (like it is hardcoded in the makefile) but in /bin.
Later I found that this is only the case in the svn version, in the "latest.tar.gz" from 2007/02/20 the path is /bin.
Why do you have the absolute path in the Makefile? uname should be in the default path on any system. (The same applies to "rm")

I also was confused that you only provide one rpm Package (except for debian) without mentioning for which distribution. You try to avoid dependencies, but the elogd is linked against the basic libraries libc and ld-linux, which might vary.
  67268   Wed May 9 21:48:42 2012 Question Tim Thieltt2005@thieleng.comQuestionLinux2.9.0HW Requirements to run elog / Performance issues running on ARM

Our group is interested in installing elog on a small/low-cost processing platform so that we can provide ready-to-run systems for our collaborators to use.  We selected a candidate platform form Technologic Systems, their wifibox-2 (http://www.embeddedarm.com/products/board-detail.php?product=TS-WIFIBOX-2).  This product is based on the TS7553 CPU board (http://www.embeddedarm.com/products/board-detail.php?product=TS-7553#) which has a 250MHz Cavium ARM9 CPU.

We have had good success getting the elogd executable cross-compiled for use on this platform and have a working system.  However, we are having significant issues with performance.  When we click the "New" item to enter a new event there is a noticable delay.  When clicking "Submit" there is a delay of approximately 10 seconds before the browser window displays the new event.  With the elogd running on other platforms (Virtual Machine or netbook) the delays for these actions are very small - typically less than a second or imperceptible.

So here are some specific questions:

- Is it reasonable to expect a 250 MHz ARM processor to serve an elog logbook with user acceptable performance?

- Our cfg file is attached.  Is there anything in the cfg file creating this performance problem.

- I have spent some time looking at this, and suspect that the delay is due to the cpu load of all the string manipulation and comparison operations (1200 calls to getcfg() on a submit).  Are there other candidate sources of performance issues that should be considered?

- Does anyone have any suggestions on how to improve our performance?

- Does anyone have a suggestion for an alternative small and low-cost COTS platform to use to host the elogd application?  (We would prefer to attain satisfactory performance on the Wifibox-2.)

Thanks for any help that can be offered.

Tim

 

Attachment 1: elogd-001.cfg
# === CONFIG FILE GENERATION DOCUMENTATION ===
#
# === GLOBAL PARAMETERS ===
# Note: Setup CruiseId and Logbooks
# Note: Datasnap logbook not in this version
#[global]
#Main Tab = oc3334
#Group Cruise = oc3334-SE 

# === GENERAL OPTIONS ===
# Note: From general options of elogd.cfg part of administrators guide
#Comment =  oc3334_COMMENT
#Subject = oc3334 Cruise Log
#Page title = oc3334 Cruise Log
Time format = %d %b %Y %H:%M
# === LOGBOOK: Science Eventlog ===
[oc3334-SE]
# === Execute Shell Command ===
# Note: execute shell command to enter a datasnap to DS logbook at new
# Note: needs to run in background
#Execute new = $shell(/shipdata/oc3334/r2r/eventlog/datasnap/CRUISEID_ds2elog.pl &)
# === Menu: List ===
# Note: Menu list
# Note: Needs to be commented out for local copy, use on synced logbooks
# Note: Used for shore view
#Menu commands = List, Find, Help
#List Menu commands = List, Find, Help
# Note: Used on ship, config option is in ECFM  
#Menu commands = List, New, Edit, Delete, Reply, Duplicate, Find, Help
#List Menu commands = List, New, Edit, Delete, Reply, Duplicate, Find, Help

# === DISPLAY: List ===
# Note: directives related to how attributes are listed on the display page
# Note: default is ID, Date, <full attribute list>
#List display = Event, dateTimeUTC, Instrument, Action, Transect, Station, Cast, Latitude, Longitude, Seafloor, Author, Comment, Revisions
#Sort attributes = Event
# === DISPLAY: Entry ===
# Note: directives related to how attributes are configured on the data entry page 
# Note: unlock these temporarily if it is necessary to edit the fields
# Note: locked Latitude, Longitude, and Seafloor
##Locked Attributes = Revisions, Cruise, Event, R2R_Event, dateTimeUTC, GPS_Time, Latitude,  Longitude, Seafloor
# Note: unlocked Latitude, Longitude, and Seafloor
#Locked Attributes = Revisions, Cruise, Event, R2R_Event, dateTimeUTC, GPS_Time, dateTime8601
#Required Attributes = Author, Instrument, Action

# === ATTRIBUTES (GENERAL) ===
# Note: Specify the attributes for this event log
# Note: An event = Instrument + Action; e.g. event = a CTD cast is started
Attributes = Event, Instrument, Action, Transect, Station, Cast, Latitude, Longitude, Seafloor, Author, Comment, Cruise, R2R_Event, dateTimeUTC, GPS_Time, dateTime8601, Revisions 
#Attributes = Instrument, Action 

# === ATTRIBUTE: Entry Time
# Note: This attribute is generated automatically by ELOG software

# === ATTRIBUTE: Event ===
# Characteristics: Locked
# Note: UTC time-based attributes
# Note: Science event number must be unique within a cruise
# Note: YYYYMMDD.HHMMSS.###
# Note: ### starts at 001 and updates to 002 if the date part of the attribute has not changed
#
#Preset Event = $shell(date +%Y%m%d.%H%M).### 
#Subst Event = $shell(date +%Y%m%d.%H%M).###
#Preset on Duplicate Event = $shell(date +%Y%m%d.%H%M).###

# === ATTRIBUTE: Transect ===
Preset Transect = NaN

# === ATTRIBUTE: Station ===
Preset Station = NaN

# === ATTRIBUTE: Cast
Preset Cast = NaN

# === ATTRIBUTE: Latitude ===
# Characteristics: Locked
#Subst Latitude = $shell(/shipdata/oc3334/r2r/eventlog/elog/scripts/get_gps_latlon -o lat -p 55150) 
Tooltip Latitude = filled on entry

# === ATTRIBUTE: Longitude ===
# Characteristics: Locked
#Subst Longitude = $shell(/shipdata/oc3334/r2r/eventlog/elog/scripts/get_gps_latlon -o lon -p 55150)
Tooltip Longitude = filled on entry

# === ATTRIBUTE: Seafloor ===
# Characteristics:
# Subst Seafloor = $shell(/shipdata/oc3334/r2r/eventlog/elog/scripts/get_depth -o depth -p 55200)

# === ATTRIBUTE: Comment ===
Preset on Duplicate Comment =
Tooltip Comment = Enter additional information
Comment Comment = Please be brief; no commas

# === ATTRIBUTE: Cruise ===
# Characteristics: Locked
# Note: Get Cruise from Cruise_ID file when on board
Preset Cruise = oc3334 

# === ATTRIBUTE: R2R_Event ===
# Characteristics: Locked
# Note: Preset this attribute and then reset it on submit
#Preset R2R_Event = $shell(/shipdata/oc3334/r2r/eventlog/elog/scripts/r2r_event_se.oc).###
#Subst R2R_Event = $shell(/shipdata/oc3334/r2r/eventlog/elog/scripts/r2r_event_se.oc).###
#Preset on Duplicate R2R_Event = $shell(/shipdata/oc3334/r2r/eventlog/elog/scripts/r2r_event_se.oc).###

# === ATTRIBUTE: dateTimeUTC ===
# Characteristics: Locked
# Note: Preset this attribute and then reset it on submit
# Note: other event number formats
# Note: using UTC YrDay:  Preset Event = $shell(echo 'date -u +%j%y.%H%M`)
#Preset dateTimeUTC = $shell(date -u +%Y%m%d.%H%M)
#Subst dateTimeUTC = $shell(date -u +%Y%m%d.%H%M)
#Preset on Duplicate dateTimeUTC = $shell(date -u +%Y%m%d.%H%M)

# === ATTRIBUTE: GPS_Time ===
# Characteristics: Locked
#Subst GPS_Time = $shell(/shipdata/oc3334/r2r/eventlog/elog/scripts/get_gps_latlon -o gps_time -p 55150)
Tooltip GPS_Time = filled on entry

# === ATTRIBUTE: dateTime8601 ===
# Characteristics: Locked
# Note: Preset this attribute and then reset it on submit
# Note: other event number formats
# Note: using ISO 8601 YrDay:  Preset Event = $shell(echo '--iso-8601=seconds`)
#Preset dateTime8601 = $shell(date --iso-8601=seconds)
#Subst dateTime8601 = $shell(date --iso-8601=seconds)
#Preset on Duplicate dateTime8601 = $shell(date --iso-8601=seconds)


# === ATTRIBUTE: Depth ===
Tooltip Depth = filled on entry

# === ATTRIBUTE: Revisions ===
# Characteristics: Locked
# Note:  if we require logins, then revisions could be authored too using $short or $long_name
Preset on Duplicate Revisions =
Subst on Edit Revisions = $Revisions & $date

# === FLAGS ===
# sort order for event display
Reverse sort = 0

# Configure the default behavior
# Do not allow a text entry box with attachments (this is different from the Comment field)
Show text = 0

# Do not allow attachments 
Enable attachments = 0

# Suppress email notification and do not even display email notification option
Suppress default = 3
Suppress Email on edit = 3
Resubmit default = 2

# quick filter options for display
Quick filter = Author, Instrument, Action
#
#
# List of instruments created by elogcfm
#
Options Instrument = ADCP150{10}, CTD911{1}, Echosounder12{2}, Echosounder3.5{3}, Other{4}, Ship{5}, Thermosalinograph SBE45{6}, XBT{7}, MeteorologicalSensor{8}, Fluorometer{9}, 

#
# List of instrument actions created by elogcfm
#
{10} ROptions Action = start,stop,service,other
{1} ROptions Action = deploy,maxDepth,recover,abort,other
{2} ROptions Action = startLine,endLine,abortLine
{3} ROptions Action = startLine,endLine,abortLine
{4} ROptions Action = start,end
{5} ROptions Action = startCruise,endCruise,other
{6} ROptions Action = start,stop,other
{7} ROptions Action = release
{8} ROptions Action = startLine,endLine,abortLine,sampleLine
{9} ROptions Action = startLine,endLine,abortLine,sampleLine
  69807   Mon Jul 22 16:17:55 2024 Entry Andréandre.althaus@tu-dortmund.deBug reportAll3.1.5HTTP headers should be parsed case insensitive

I'm trying to run elog behind haproxy, but get the error "Invalid Content-Length in header" on posting.

As stated in the manual, haproxy rewrites all headers to lower case.

elogd parses the content-length header case sensitive which is against the HTTP RFC. This might also apply to other headers that get parsed.

For now I'm using the workaround from the manual:

global
  h1-case-adjust content-length Content-Length
  h1-case-adjust content-type Content-Type

backend elog
  option h1-case-adjust-bogus-server
  server elog 127.0.0.1:8080

But as the manual states, this should not be  used as a permanent solution.

ELOG V3.1.5-3fb85fa6