ELOG Forum

Logbook architecture and availability

I have a setting which makes ELOG a perfect solution, but there's a situation that I'm struggling to get my head around. We have 3 separate laboratories, each one containing a number of temperature chambers, which run almost constantly over a number of shifts. Each temperature chamber has it's own logbook (laptop). So far, pretty simple.
My dilemma is, our network goes down for maintenance/updates (more often than I'd like), but our operation cannot afford to stop during network interruptions.
With that said, I thought about whether I could run a "local" logbook on each laptop/chamber, and somehow mirror the local logbook to the main ELOG server.
Perhaps I'm over-thinking this...do you have any recommendations?

68875

Fri Dec 14 17:22:31 2018

Thanks Stephan! I guess I was making it harder than it is. I'm still a little fuzzy -- in this instance, am I correct in saying that each laptop would be considered a "master", and the remote (network) server considered the "slave"? Also, I'm not sure quite sure -- which server should be assigned responsibility for performing periodic synchronization between the laptop and the central elog server?

Thanks again for all you do -- Happy Holidays!

Frank

Stefan Ritt wrote:

Sure that's easy. Install elog on each laptop separately, so they run without network. Then, set up a central elog server, and use "mirroring" as explained in the documentation at https://elog.psi.ch/elog/config.html#mirroring

So when ever the entwork comes back, you execute a manual mirror operation, and your new entries will be pushed to the central elog server.

Best,
Stefan

Frank Baptista wrote:

68877

Fri Dec 14 20:52:46 2018

Thank you again -- very much appreciated!

Stefan Ritt wrote:

I would call the laptops the "master" being responsible for pushing data to the central server which you can call "slave"

Stefan

Frank Baptista wrote:

Thanks again for all you do -- Happy Holidays!

Frank

Stefan Ritt wrote:

So when ever the entwork comes back, you execute a manual mirror operation, and your new entries will be pushed to the central elog server.

Best,
Stefan

Frank Baptista wrote:

68882

Fri Feb 1 19:20:35 2019

I've got things working - sort of. Ran into one strange problem that has me scratching my head. I have two different laptops, each running a local instance of their own logbook. Both are functional, but for some strange reason, one looks great, and the other is missing its graphic format. I've attached a screen capture of that logbook, and a copy of the config file. Do you see something that I've done wrong?

Thanks,

Frank

Frank Baptista wrote:

Thank you again -- very much appreciated!

Stefan Ritt wrote:

I would call the laptops the "master" being responsible for pushing data to the central server which you can call "slave"

Stefan

Frank Baptista wrote:

Thanks again for all you do -- Happy Holidays!

Frank

Stefan Ritt wrote:

So when ever the entwork comes back, you execute a manual mirror operation, and your new entries will be pushed to the central elog server.

Best,
Stefan

Frank Baptista wrote:

Attachment 1: ELOG_Screen_Capture_-_Missing_formatting.PNG

Attachment 2: elogd.cfg

[global]
port = 8080
Resource dir = C:\Program Files (x86)\ELOG\resources
Logbook dir = C:\Program Files (x86)\ELOG\logbooks
Language = lenglish

[CH79]
Theme = default
Subdir = CH79
Comment = ESS - CH79 / JETS-1
Menu commands = List, Reply, Help
List Menu commands = New, Find, Help
Attributes = Clock #, Type, Category, Production Status, Perform OPM?, ATMS Correct?
Options Type = Test{1}, Equipment Incident{2}
{1} Options Category = Production, Engineering, Update
{2} Options Category = OPM Issue, Test Station, ITA, Chamber, Chiller, Socket, Software change, Hardware change, Update, Other
{1} Show Attributes Edit = Clock #, Type, Category, Production Status, Perform OPM?, ATMS Correct?
{2} Show Attributes Edit = Clock #, Type, Category, Production Status
{1} Preset text = C:\Program Files (x86)\ELOG\JETS_Template.htm
Options Production Status = Running, Open, Down, Engineering
Options Perform OPM? = boolean
Options ATMS Correct? = boolean
Comment Perform OPM? = If issue(s) found, create separate logbook entry.
Comment ATMS Correct? = All entries correct? Checked ATMS constraint?
Cell Style Production Status Running = background-color:green
Cell Style Production Status Open = background-color:yellow
Cell Style Production Status Down = background-color:red
Cell Style Production Status Engineering = background-color:blue
Required Attributes = Clock #, Type, Category, Production Status
Preset on reply Type = $Type
Preset on reply Category = Update
Page Title = ELOG - CH79 / JETS-1
Reverse sort = 1
Save drafts = 0
Quick filter = Date, Type, Subtext

68883

Fri Feb 1 21:59:46 2019

Sorry -- dumb mistake. I moved the "theme" files to the resource folder. Works like a champ...life is good!

Frank Baptista wrote:

Thanks,

Frank

Frank Baptista wrote:

Thank you again -- very much appreciated!

Stefan Ritt wrote:

I would call the laptops the "master" being responsible for pushing data to the central server which you can call "slave"

Stefan

Frank Baptista wrote:

Thanks again for all you do -- Happy Holidays!

Frank

Stefan Ritt wrote:

So when ever the entwork comes back, you execute a manual mirror operation, and your new entries will be pushed to the central elog server.

Best,
Stefan

Frank Baptista wrote:

68903

Fri Mar 1 19:18:53 2019