Re: enable batch file execution, posted by Frank Baptista on Sat Jun 15 23:44:35 2019
|
I have not tried these, but since CKeditor works so well, you may want to consider taking a look at integrating jQuery Calx or jExcel...just for fun.
| Stefan Ritt wrote: |
|
I meant to use it instead of ELOG. Spreadsheets allow calculaiton of dates, etc. So you can achieve what you need. Again: WHAT YOU WANT IS NOT POSSIBLE WITH ELOG.
| dev wrote: |
|
Is it as good as Microsoft excel sheet.
but how can achieve my aim of calculation how how to integrate it with elog
Sorry for disturbing yau again and again
| Stefan Ritt wrote: |
|
https://docs.google.com/spreadsheets
| dev wrote: |
|
Sir, how to use that spreadsheet
can the calculation is possible by running a batch file .
| Stefan Ritt wrote: |
|
This is not possible with ELOG. May I suggest that you use a spreadsheet for that.
| dev wrote: |
|
First of all thanx for your kind help. Kindly help me on the following problem.
I have a logbook which keeps the record of all fault booked by different subscriber.this logbook has three attribute downtime,uptime & total duration (date &time format) . I want to calculate the total duration automatically whenevr uptime value is given and if the uptime is not given it should calculate depending upon the system present time.pleas explain it with example.
thanking you
| Stefan Ritt wrote: |
|
May I kindly ask you to Google how to start/stop a service from the command line.
| dev wrote: |
|
From the command mode i am not able to stop and start (elogd stop). But i can start/stop from services .Kindly help me stopping/starting it from command
| Stefan Ritt wrote: |
|
Stop the old server first, but we told you this already on elog:67770. If you don't follow our suggestions we cannot help you.
| dev wrote: |
|
I tried it but still it gives error like Shell execution not enabled via -x flag
| Stefan Ritt wrote: |
|
Modify the server start command in the Windows Registry. Or start the elogd server directly in a command window with "elogd -x", after "cd" to the elog installation directory.
| dev wrote: |
|
How to enable the batch file execution in elogd
|
|
|
|
|
|
|
|
|
|
|
|
|
Executing a shell command using elogd Windows service, posted by Frank Baptista on Sun Nov 24 20:29:24 2019 
|
Greetings!
We've been successfully running nearly a dozen separate logbooks on independent laptops -- all of them are running elogd as a Windows service. This works well, since I've also set up auto recovery options in the event that the service inadvertently stops.
Now, I have a need to place the value of an attribute of the latest log entry into a basic text file. Of course, this works just fine if I have launched elogd -x as a normal executable, using Execute new = echo $Status > Last_status.log in my CFG file. However, I would like to be able to do this using the Windows service which is running in the background.
Is there another way to write the value of an attribute into a separate file? If not, do I have to have a special build of ELOG in order to be able to enable the Windows service to execute shell commands? For the record, these logbooks are running on secure laptops that are isolated onto their own network, and the user is unable to edit the CFG file.
In case you're wondering about the reason for the separate text file -- I've written a separate program which illuminates one of 4 different color signal lamps (mounted on a test station), based on the latest "Status" of the test station. (Running, Idle, Broken, Other).
I appreciate any guidance here -- this is a "big deal" here, as one glance over the floor gives us an idea of what's running (or not).
Thanks!
Frank |
|
Re: Executing a shell command using elogd Windows service, posted by Frank Baptista on Sun Nov 24 21:10:28 2019
|
Sorry -- I somehow selected the wrong OS in my original message. Asleep at the wheel again.
| Frank Baptista wrote: |
|
Greetings!
We've been successfully running nearly a dozen separate logbooks on independent laptops -- all of them are running elogd as a Windows service. This works well, since I've also set up auto recovery options in the event that the service inadvertently stops.
Now, I have a need to place the value of an attribute of the latest log entry into a basic text file. Of course, this works just fine if I have launched elogd -x as a normal executable, using Execute new = echo $Status > Last_status.log in my CFG file. However, I would like to be able to do this using the Windows service which is running in the background.
Is there another way to write the value of an attribute into a separate file? If not, do I have to have a special build of ELOG in order to be able to enable the Windows service to execute shell commands? For the record, these logbooks are running on secure laptops that are isolated onto their own network, and the user is unable to edit the CFG file.
In case you're wondering about the reason for the separate text file -- I've written a separate program which illuminates one of 4 different color signal lamps (mounted on a test station), based on the latest "Status" of the test station. (Running, Idle, Broken, Other).
I appreciate any guidance here -- this is a "big deal" here, as one glance over the floor gives us an idea of what's running (or not).
Thanks!
Frank
|
|
|
Re: Executing a shell command using elogd Windows service, posted by Frank Baptista on Sat Nov 30 15:46:16 2019
|
Well, there I was, eating Thanksgiving dinner, when suddenly, it hit me (no, not indigestion). I can write a simple program that parses out the latest "Status" from the most recent logbook file -- a relatively easy task, since it's a text file. This solution avoids having to execute a shell command at all. GOOOOOOAAAAAAL!!! 
As always, I appreciate all your help...can't thank you enough!
All the best,
Frank
| Stefan Ritt wrote: |
|
Wow, having these color signal lamps really looke like a cute solution, made me laugh.
No, there is no other way than the Execute new thing. I have given up long time ago to use Windows services, because they are very hard to debug and very limited. So at our site everything runs under Linux.
Have you tried to specify the explicit path of your log file? Like Execute new = echo $Status > C:\Path\Last_status.log
Best,
Stefan
| Frank Baptista wrote: |
|
Sorry -- I somehow selected the wrong OS in my original message. Asleep at the wheel again.
| Frank Baptista wrote: |
|
Greetings!
We've been successfully running nearly a dozen separate logbooks on independent laptops -- all of them are running elogd as a Windows service. This works well, since I've also set up auto recovery options in the event that the service inadvertently stops.
Now, I have a need to place the value of an attribute of the latest log entry into a basic text file. Of course, this works just fine if I have launched elogd -x as a normal executable, using Execute new = echo $Status > Last_status.log in my CFG file. However, I would like to be able to do this using the Windows service which is running in the background.
Is there another way to write the value of an attribute into a separate file? If not, do I have to have a special build of ELOG in order to be able to enable the Windows service to execute shell commands? For the record, these logbooks are running on secure laptops that are isolated onto their own network, and the user is unable to edit the CFG file.
In case you're wondering about the reason for the separate text file -- I've written a separate program which illuminates one of 4 different color signal lamps (mounted on a test station), based on the latest "Status" of the test station. (Running, Idle, Broken, Other).
I appreciate any guidance here -- this is a "big deal" here, as one glance over the floor gives us an idea of what's running (or not).
Thanks!
Frank
|
|
|
|
|
Record ID corruption, posted by Frank Baptista on Sun May 3 15:58:24 2020
|
Hi all,
I've encountered an occasional problem that seems to be exacerbated by having a message with many replies.
In our use of ELOG, we run lengthy environmental tests (often several days) in multiple temperature chambers (one logbook for each chamber). We document the start of the test with a log entry, and then periodically create replies -- first to the original log entry, and then to each successive reply (no branching allowed), in order to document how far along the test is.
What I'm seeing is an occasional "hiccup" in the order of records -- in the snapshot below, you can see that the record ID(s) go (in chronological order) ....5654, 5655, 5656, 5659, 5657, 5658, 5660, 5661....
Additionally, in this example, record ID# 5659 and record ID# 5657 are duplicates -- duplicate time stamp and duplicate text.
Has anyone else encountered this?
Thanks,
Frank
|
|
Re: Record ID corruption, posted by Frank Baptista on Sun May 3 22:43:12 2020
|
Hi David,
Thanks for the quick response! Well, I'd have to say that the sequence is as tangled as it looks in the logbook -- I've attached a copy of the log file for your reading pleasure.
This one is definitely a "head-scratcher" for me...it definitely seems like it is more prevalent on log entries with many replies.
Thanks,
Frank
| David Pilgram wrote: |
|
Hi,
I've had problems in the past due to a dodgy pointer creating branches despite a "No branches" in the configuration file. It would be very interesting to see what the 200428a.log file looks li looks like with these entries: in the screenshot they appear to be shown in time order, but do the "Reply to" and "In reply to" liknes in each entry (in the .log file) show a linear progression through the entires, a branch a branch or indeed this same order as the screenshot. If the duplicated entry sequential to 5657 (i.e 5658) then I would suspect something akin to my pointer's double click when I only made a single click, so fast that then second e second entry were created before the "No branches" checking part of the program had been reached. Not so sure about such an event here unless entry 5658 were already open but not closed?
Regards,
David.
| Frank Baptista wrote: |
|
Hi all,
I've encountered an occasional problem that seems to be exacerbated by having a message with many replies.
In our use of ELOG, we run lengthy environmental tests (often several days) in multiple temperature chambers (one logbook for each chamber). We document the start of the test with a log entry, and then periodically create replies -- first to the original log entry, and then to each successive reply (no branching allowed), in order to document how far along the test is.
What I'm seeing is an occasional "hiccup" in the order of records -- in the snapshot below, you can see that the record ID(s) go (in chronological order) ....5654, 5655, 56 5656, 5659, 5657, 5658, 5660, 5661....
Additionally, in this example, record ID# 5659 and record ID# 5657 are duplicates -- duplicate time stamp and duplicate text.
Has anyone else encountered this?
Thanks,
Frank
|
|
|
|
Re: Record ID corruption, posted by Frank Baptista on Fri May 22 21:03:05 2020
|
Hi David,
Well, you've made some very interesting observations, and raised some excellent questions. So, I went back and did some homework, reviewing a number of logbooks to find instances where this strange 'record twist' occurs. You had asked, "Do you have enough information to decided that this event always happens after x replies?" -- and to my surprise, indeed there was a magic number that I didn't expect to see. The 57th reply to the original posting was always where the corruption began. Mind you, we don't always get a corruption on the 57th reply -- most of the time, it works as expected. However, in all the cases where I saw this record twist, it was the 57th reply after the original posting. Go figure.
I also reviewed my elogd.cfg file to see how I handled drafts. Currently, it does have the flag Save drafts = 0. What I plan to try next, if only to satisfy my curiosity, is to also add Autosave=0.
I can't thank you enough for your time and feedback...very much appreciated!
Best regards,
Frank
| David Pilgram wrote: |
|
Hi Frank,
There are two interesting points about the log file.
1. Entry 5658 is timestamped later than 5659, but is earlier in the entry list. It also is "In Reply to" 5659. despite 5659 having not been written (or at least timestamped) at the time that 5658 is. Might this be a feature of the draft function? I've not upgraded my elog for a long time now so my version doesn't have the feature - so I cannot test the idea of more than one entry being worked upon at the same time.
2. Entry 5657 says it is "In Reply to" 5656, but entry 5656 does not reference 5657 in the "Reply to" line, as it should Again, this might be a feature of the draft function
Could someone be confusing a draft entry with a real one? Or two attempts to make an entry?
On the idea of large number of entries, elog doesn't handle deleting of a thread of more than 40 replies well - it crashes after deleting the 40th. This leaves an orphan thread that causes other issues. Do you have enough information to decided that this event always happens after x replies?
| Frank Baptista wrote: |
|
Hi David,
Thanks for the quick response! Well, I'd have to say that the sequence is as tangled as it looks in the logbook -- I've attached a copy of the log file for your reading pleasure.
This one is definitely a "head-scratcher" for me...it definitely seems like it is more prevalent on log entries with many replies.
Thanks,
Frank
| David Pilgram wrote: |
|
Hi,
I've had problems in the past due to a dodgy pointer creating branches despite a "No branches" in the configuration file. It would be very interesting to see what the 200428a.log file looks li looks like with these entries: in the screenshot they appear to be shown in time order, but do the "Reply to" and "In reply to" liknes in each entry (in the .log file) show a linear progression through the entires, a branch a branch or indeed this same order as the screenshot. If the duplicated entry sequential to 5657 (i.e 5658) then I would suspect something akin to my pointer's double click when I only made a single click, so fast that then second e second entry were created before the "No branches" checking part of the program had been reached. Not so sure about such an event here unless entry 5658 were already open but not closed?
Regards,
David.
| Frank Baptista wrote: |
|
Hi all,
I've encountered an occasional problem that seems to be exacerbated by having a message with many replies.
In our use of ELOG, we run lengthy environmental tests (often several days) in multiple temperature chambers (one logbook for each chamber). We document the start of the test with a log entry, and then periodically create replies -- first to the original log entry, and then to each successive reply (no branching allowed), in order to document how far along the test is.
What I'm seeing is an occasional "hiccup" in the order of records -- in the snapshot below, you can see that the record ID(s) go (in chronological order) ....5654, 5655, 56 5656, 5659, 5657, 5658, 5660, 5661....
Additionally, in this example, record ID# 5659 and record ID# 5657 are duplicates -- duplicate time stamp and duplicate text.
Has anyone else encountered this?
Thanks,
Frank
|
|
|
|
|
|
Real-time mirroring?, posted by Frank Baptista on Mon Apr 26 15:40:36 2021
|
Hello!
We have a number of local ELOG servers, all mirrored to a single "remote" ELOG server. We have users that create updates at the local server, and some at the remote server, which can run the risk of record conflicts. Right now, the local servers perform a "Mirror cron" every 5 minutes, but even that leaves the door open to potential conflicts.
I found an open-source JAVA-based app called DirSync Pro (https://www.dirsyncpro.org/) which is capable of performing real-time mirroring, and has conflict handling. I "took it for a spin", and it does do what it claims. However, because each ELOG server performs record "indexing", it doesn't recognize records that aren't part of the current list of records. Restarting the ELOG server obviously corrects that, but I was wondering if there is another way to get the server to recognize newer "remotely-generated" records without restarting the server.
As always, I'm appreciative for the outstanding working that has been done to make ELOG the great application that it is!
|
|