Re: Multiple versions of elog on one server, posted by Chris Smith on Wed Feb 20 23:41:00 2013
|
| David Pilgram wrote: |
|
| Chris Smith wrote: |
|
Is there a way of having multiple copies of elog running on one windows 2003 server? different ports?
I need to access 2 different elogd.cfg files.
|
It's probably not of much help, but for a short time I ran two elog daemons on the same linux box, using different ports. It was thus able to run with two separate elogd.cfg files. This is linux, and heavily biased to my eccentric way of running this linux box, but started them as:
/usr/local/sbin/elogd -p 8080 -c /home/logbooks1/elogd1.cfg -d /home/logbooks1
/usr/local/sbin/elogd -p 8081 -c /home/logbooks2/elogd2.cfg -d /home/logbooks2
Do note that as I was the only user on that linux box, I didn't have login etc.
However, I was soon asked questions by Andreas as to how I found this running, as he had encountered problems with an earlier version. To be honest, that stopped me experimenting too far with this at that point, as well as a coincidental upgrading of my hardware.
But I was doing this *not* because I had to run two separate elogd.cfg files, but other reasons which meant splitting into two at that time vastly improved the performance of elog on the linux box at that time. So while I didn't actually enounter any problems in doing so, I only have limited experience - and, of course, absolutely none on running even one [windows equivalent of a daemon] on Windows.
I am assuming here you have good reason for two separate elogd.cfg files, rather than just wanting to run two separate logbooks - guessing here, but one set public (no login) and one set private (with login)?
|
I need to do this because there are 2 different groups that each have 6 or 7 different logbooks in their elogd.cfg files. (and they can't access each others log books)
Currently the first group accesses elog as http:elog.com:8080. The elogd windows service executes "C:\Program FilesELOG\elogd.exe" -D -c "C:\Program Files\ELOG\elogd.cfg"
From what I can tell, whats needed is either some way to get the windows service to run a different config file or there needs to be a way of creating a second elog windows service that points to a different elogd.cfg file. Is there some way of doing this? |
|
Re: Multiple versions of elog on one server, posted by Stefan Ritt on Thu Feb 21 08:12:01 2013
|
| Chris Smith wrote: |
|
| David Pilgram wrote: |
|
| Chris Smith wrote: |
|
Is there a way of having multiple copies of elog running on one windows 2003 server? different ports?
I need to access 2 different elogd.cfg files.
|
It's probably not of much help, but for a short time I ran two elog daemons on the same linux box, using different ports. It was thus able to run with two separate elogd.cfg files. This is linux, and heavily biased to my eccentric way of running this linux box, but started them as:
/usr/local/sbin/elogd -p 8080 -c /home/logbooks1/elogd1.cfg -d /home/logbooks1
/usr/local/sbin/elogd -p 8081 -c /home/logbooks2/elogd2.cfg -d /home/logbooks2
Do note that as I was the only user on that linux box, I didn't have login etc.
However, I was soon asked questions by Andreas as to how I found this running, as he had encountered problems with an earlier version. To be honest, that stopped me experimenting too far with this at that point, as well as a coincidental upgrading of my hardware.
But I was doing this *not* because I had to run two separate elogd.cfg files, but other reasons which meant splitting into two at that time vastly improved the performance of elog on the linux box at that time. So while I didn't actually enounter any problems in doing so, I only have limited experience - and, of course, absolutely none on running even one [windows equivalent of a daemon] on Windows.
I am assuming here you have good reason for two separate elogd.cfg files, rather than just wanting to run two separate logbooks - guessing here, but one set public (no login) and one set private (with login)?
|
I need to do this because there are 2 different groups that each have 6 or 7 different logbooks in their elogd.cfg files. (and they can't access each others log books)
Currently the first group accesses elog as http:elog.com:8080. The elogd windows service executes "C:\Program FilesELOG\elogd.exe" -D -c "C:\Program Files\ELOG\elogd.cfg"
From what I can tell, whats needed is either some way to get the windows service to run a different config file or there needs to be a way of creating a second elog windows service that points to a different elogd.cfg file. Is there some way of doing this?
|
Have you checked the option "Top groups", which was made especially for that case? You can create several independent sets of logbooks not seeing each other. |
|
Re: Multiple versions of elog on one server, posted by Chris Smith on Thu Feb 21 20:05:44 2013
|
| Stefan Ritt wrote: |
|
| Chris Smith wrote: |
|
| David Pilgram wrote: |
|
| Chris Smith wrote: |
|
Is there a way of having multiple copies of elog running on one windows 2003 server? different ports?
I need to access 2 different elogd.cfg files.
|
It's probably not of much help, but for a short time I ran two elog daemons on the same linux box, using different ports. It was thus able to run with two separate elogd.cfg files. This is linux, and heavily biased to my eccentric way of running this linux box, but started them as:
/usr/local/sbin/elogd -p 8080 -c /home/logbooks1/elogd1.cfg -d /home/logbooks1
/usr/local/sbin/elogd -p 8081 -c /home/logbooks2/elogd2.cfg -d /home/logbooks2
Do note that as I was the only user on that linux box, I didn't have login etc.
However, I was soon asked questions by Andreas as to how I found this running, as he had encountered problems with an earlier version. To be honest, that stopped me experimenting too far with this at that point, as well as a coincidental upgrading of my hardware.
But I was doing this *not* because I had to run two separate elogd.cfg files, but other reasons which meant splitting into two at that time vastly improved the performance of elog on the linux box at that time. So while I didn't actually enounter any problems in doing so, I only have limited experience - and, of course, absolutely none on running even one [windows equivalent of a daemon] on Windows.
I am assuming here you have good reason for two separate elogd.cfg files, rather than just wanting to run two separate logbooks - guessing here, but one set public (no login) and one set private (with login)?
|
I need to do this because there are 2 different groups that each have 6 or 7 different logbooks in their elogd.cfg files. (and they can't access each others log books)
Currently the first group accesses elog as http:elog.com:8080. The elogd windows service executes "C:\Program FilesELOG\elogd.exe" -D -c "C:\Program Files\ELOG\elogd.cfg"
From what I can tell, whats needed is either some way to get the windows service to run a different config file or there needs to be a way of creating a second elog windows service that points to a different elogd.cfg file. Is there some way of doing this?
|
Have you checked the option "Top groups", which was made especially for that case? You can create several independent sets of logbooks not seeing each other.
|
I will check out the "Top Groups". But another question, the documentation says "Prior to ELOG version 2.4.1, one had to run two elogd servers in parallel, listening under different ports." ... how do you set this up? |
|
Re: Multiple versions of elog on one server, posted by Stefan Ritt on Fri Feb 22 11:40:34 2013
|
| Chris Smith wrote: |
|
| Stefan Ritt wrote: |
|
| Chris Smith wrote: |
|
| David Pilgram wrote: |
|
| Chris Smith wrote: |
|
Is there a way of having multiple copies of elog running on one windows 2003 server? different ports?
I need to access 2 different elogd.cfg files.
|
It's probably not of much help, but for a short time I ran two elog daemons on the same linux box, using different ports. It was thus able to run with two separate elogd.cfg files. This is linux, and heavily biased to my eccentric way of running this linux box, but started them as:
/usr/local/sbin/elogd -p 8080 -c /home/logbooks1/elogd1.cfg -d /home/logbooks1
/usr/local/sbin/elogd -p 8081 -c /home/logbooks2/elogd2.cfg -d /home/logbooks2
Do note that as I was the only user on that linux box, I didn't have login etc.
However, I was soon asked questions by Andreas as to how I found this running, as he had encountered problems with an earlier version. To be honest, that stopped me experimenting too far with this at that point, as well as a coincidental upgrading of my hardware.
But I was doing this *not* because I had to run two separate elogd.cfg files, but other reasons which meant splitting into two at that time vastly improved the performance of elog on the linux box at that time. So while I didn't actually enounter any problems in doing so, I only have limited experience - and, of course, absolutely none on running even one [windows equivalent of a daemon] on Windows.
I am assuming here you have good reason for two separate elogd.cfg files, rather than just wanting to run two separate logbooks - guessing here, but one set public (no login) and one set private (with login)?
|
I need to do this because there are 2 different groups that each have 6 or 7 different logbooks in their elogd.cfg files. (and they can't access each others log books)
Currently the first group accesses elog as http:elog.com:8080. The elogd windows service executes "C:\Program FilesELOG\elogd.exe" -D -c "C:\Program Files\ELOG\elogd.cfg"
From what I can tell, whats needed is either some way to get the windows service to run a different config file or there needs to be a way of creating a second elog windows service that points to a different elogd.cfg file. Is there some way of doing this?
|
Have you checked the option "Top groups", which was made especially for that case? You can create several independent sets of logbooks not seeing each other.
|
I will check out the "Top Groups". But another question, the documentation says "Prior to ELOG version 2.4.1, one had to run two elogd servers in parallel, listening under different ports." ... how do you set this up?
|
You have to create manually a second service. Clone all entry from the first one, except the command line where you load a different elogd.cfg. But I actually never tried this myself. |
Export entries to XLS or CSV?, posted by scogordo on Wed May 15 17:24:12 2013
|
I've been asked to export one of our logbooks to xls or csv. Doable?
Thanks,
Scott |
Re: Export entries to XLS or CSV?, posted by Andreas Luedeke on Wed May 15 23:31:30 2013 
|
| scogordo wrote: |
|
I've been asked to export one of our logbooks to xls or csv. Doable?
Thanks,
Scott
|
Hi Scott,
yes, every user can export entries using the "find" command.
Just select the export format in the first line
Export to:
 ⇄
Detect language » English
⇄
Detect language » English
I often use the XML Format, but CSV is fine if you just want to import the entries to some spreadsheet program.
I was shocked to find out that this feature has not yet made it into the documentation?!? But it is that simple to use that there is not much to document.
There is even an "Import" command, to reimport entries from a file. But this is tricky to use: if you have fields of type date or datetime, then you have to convert those fields in the proper format. |
|
Re: Export entries to XLS or CSV?, posted by Jim Tinlin on Thu May 30 22:52:51 2013
|
| Andreas Luedeke wrote: |
|
| scogordo wrote: |
|
I've been asked to export one of our logbooks to xls or csv. Doable?
Thanks,
Scott
|
Hi Scott,
yes, every user can export entries using the "find" command.
Just select the export format in the first line
Export to:
⇄
Detect language » English
⇄
Detect language » English
I often use the XML Format, but CSV is fine if you just want to import the entries to some spreadsheet program.
I was shocked to find out that this feature has not yet made it into the documentation?!? But it is that simple to use that there is not much to document.
There is even an "Import" command, to reimport entries from a file. But this is tricky to use: if you have fields of type date or datetime, then you have to convert those fields in the proper format.
|
I tried EXPORTING logbooks as .csv but have not been fully successful. Elog seems to only export the data entered for various fields with the exception of the text field.
Here is an example export from my logbook (used to track simulator problems), I would like to also export the TEXT field so it can be used by my managers in excel...but as you can see there is no entry for "TEXT" fields...
Thanks in advance!
"Message ID","Date","Author","Type","Status","Priority"
107,Thu 30 May 2013 11:28:57 -0700,"Jim Tinlin","Graphic Display","Evaluated","Low"
106,Thu 30 May 2013 10:02:24 -0700,"Jim Tinlin","Graphic Display","Identified","Low"
105,Thu 30 May 2013 08:07:27 -0700,"Jim Tinlin","Problem ID","Identified","Medium"
104,Thu 30 May 2013 08:04:30 -0700,"Jim Tinlin","Problem ID","Identified","Medium"
103,Wed 29 May 2013 09:36:11 -0700,"Jim Tinlin","Problem ID","Evaluated","High"
102,Wed 29 May 2013 08:58:02 -0700,"Jim Tinlin","Problem ID","Evaluated","High" |
Attributes for message workflow., posted by Ryan on Thu Mar 24 17:23:37 2011
|
I am attempting to setup an ECR (Engineering Change Review/Request) process in ELOG.
I have a logbook setup so that an original request is submitted with a status of "Approval Pending"
Options ECR Status = Approval Pending, Approved / In Progress, Completed / In QA, Closed
Once the entry is made, it is reviewed by several people who reply to the original entry and update the approval fields, adding any comments as a reply :
Options OPS Approval = Approved, Denied
Options ENG Approval = Approved, Denied
Options Director Approval = Approved, Denied
Once the final approval is obtained, they reply to the thread and update the ECR Status field to "Approved / In Progress"
This goes through our QA process, and is finaly updated with "Closed"
The problem is, I would like to keep the historical data of when the status of these entries are made. For example, in the message thread, I can see that reply #4 changed the "Status" field to "Approved". However, I can not seem to find a way for this to work with quick filtering. The quick filter always filters on the first entry on a thread, and not the last.
The other option would be to change the status of the first entry, but that seems silly as I am using replys instead of edits.
Any ideas on how to implement this "Status" field into my workflow? I am even open to losing the historical "status" and beeing able to change all entries on the thread on reply. (i.e. Reply #4 changes "Status" to "Approved", and the system changed all entries in the thread to "Approved") |
|