editor hangs intermittently, posted by Sara Vanini on Fri Jan 24 14:56:04 2020
|
Hello,
I'm using ELOG with Ubuntu 19. When I create or edit an entry and I start writing, it hangs for few seconds, resumes, and all over again intermittently.
How can I fix it?
Best
Sara |
Different behaviours to identical configuration of logbooks for email notification, posted by matthieu heller on Mon Jan 20 13:46:56 2020 
|
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 |
|
text wrapping broken in firefox, posted by Devin Bougie on Thu Dec 19 16:28:06 2019
|
When creating new logbook entries, recent versions of firefox somehow ignore the message width setting.
For example, configure a logbook with:
Message Width = 76
Message Height = 20
Then, create a new plain text entry that contains very long lines. The text entry box is the correct size, but once you hit submit and view the full display of the message, it is not wrapped properly. The summary display is wrapped properly, but not the full display.
We've only found this to be a problem with recent versions of firefox. Chromium, Safari, and old versions of firefox behave properly. |
Re: text wrapping broken in firefox, posted by Devin Bougie on Thu Dec 19 16:40:10 2019
|
As an example, I created this same entry in the demo logbook using Safari. As you can see there, the message is wrapped at the width that I set the text entry box.
https://elog.psi.ch/elogs/Linux+Demo/9
> When creating new logbook entries, recent versions of firefox somehow ignore the message width setting.
>
> For example, configure a logbook with:
> Message Width = 76
> Message Height = 20
>
> Then, create a new plain text entry that contains very long lines. The text entry box is the correct size, but once you hit submit and view the full display of the message, it is not wrapped properly. The summary display is wrapped properly, but not the full display.
>
> We've only found this to be a problem with recent versions of firefox. Chromium, Safari, and old versions of firefox behave properly. |
|
Change column width in list mode?, posted by David Wallis on Mon Dec 2 23:28:28 2019
|
In some of our logbooks, some columns are very narrow, which makes their content difficult to read. I have tried adding a custom css file like this:
listframe td:nth-child(3) {
width: 250px;
}
But I find that the column width does not change. I have verified via element inspection that the width attribute is active on the correct column (td).
Am I doing someting wrong, or is this not possible? |
|
Re: Change column width in list mode?, posted by Stefan Ritt on Wed Dec 4 10:37:32 2019
|
You need
.listframe td:nth-child(3) {
min-width: 250px;
}
/Stefan
| David Wallis wrote: |
|
In some of our logbooks, some columns are very narrow, which makes their content difficult to read. I have tried adding a custom css file like this:
listframe td:nth-child(3) {
width: 250px;
}
But I find that the column width does not change. I have verified via element inspection that the width attribute is active on the correct column (td).
Am I doing someting wrong, or is this not possible?
|
|
|
Re: Change column width in list mode?, posted by David Wallis on Fri Dec 6 15:40:19 2019
|
Awesome, thank you!
| Stefan Ritt wrote: |
|
You need
.listframe td:nth-child(3) {
min-width: 250px;
}
/Stefan
| David Wallis wrote: |
|
In some of our logbooks, some columns are very narrow, which makes their content difficult to read. I have tried adding a custom css file like this:
listframe td:nth-child(3) {
width: 250px;
}
But I find that the column width does not change. I have verified via element inspection that the width attribute is active on the correct column (td).
Am I doing someting wrong, or is this not possible?
|
|
|
|
How to selectively use Top/Bottom Text JavaScript., posted by John on Wed Dec 4 03:06:50 2019
|
I think I know what the answer(s) will be already.. that I will need to address this in JS. I don't want each screen to run/show the same code, other than the ones I want to. AND I do not want to have to create a custom form for each 'menu option' to achieve this (if possible).
Thanx,
John |
|
Re: How to selectively use Top/Bottom Text JavaScript., posted by Stefan Ritt on Wed Dec 4 10:15:56 2019
|
In JS, you have access to the browser URL via window.location. So you can write conditional code depending on the actual elog command.
Stefan
| John wrote: |
|
I think I know what the answer(s) will be already.. that I will need to address this in JS. I don't want each screen to run/show the same code, other than the ones I want to. AND I do not want to have to create a custom form for each 'menu option' to achieve this (if possible).
Thanx,
John
|
|
|
Re: How to selectively use Top/Bottom Text JavaScript., posted by John on Wed Dec 4 20:39:41 2019
|
Wow thanks again Stefan for your kind and prompt responses!!
John
| Stefan Ritt wrote: |
|
In JS, you have access to the browser URL via window.location. So you can write conditional code depending on the actual elog command.
Stefan
| John wrote: |
|
I think I know what the answer(s) will be already.. that I will need to address this in JS. I don't want each screen to run/show the same code, other than the ones I want to. AND I do not want to have to create a custom form for each 'menu option' to achieve this (if possible).
Thanx,
John
|
|
|
|
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 Stefan Ritt on Mon Nov 25 16:32:07 2019
|
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
|
|
|
|
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
|
|
|
|
|
Trouble on Catalina, posted by John S. Haggerty on Fri Nov 22 02:55:50 2019
|
I decided to rebuild elog 3.1.4 in Catalina (MacOS 10.15.1), XCode 11.2.1. As in previous builds, I needed to add to the Makefile pointers to openssl:
CFLAGS += -I/usr/local/opt/openssl/include
LIBS += -L/usr/local/opt/openssl/lib
The make builds cleanly, no errors, no warnings. After make/make install, elogd segfaults immediately. I saw the same behavior with the version in gitlab. I kept my (very) old build and was able to make install it without recompiling and it still works.
I'll crack out the debugger when I have a chance to get more information, but has anyone else seen this problem? |
|
Re: Trouble on Catalina, posted by Stefan Ritt on Mon Nov 25 16:25:21 2019
|
The Makefile is kind of obsolete, I switched to CMake. So the Makefiel is mostly there as backup. To compile elog, do
elog$ mkdir build; cd build
elog/build$ cmake ..
elod/build$ make install
that should also find your openssl library, since CMake is more clever.
I personally have not yet switched to MacOS Catalina, since I have too many 32-bit programs running there and wait until all of these get updated. Only then I will be able to test elog under Catalina.
Stefan
| John S. Haggerty wrote: |
|
I decided to rebuild elog 3.1.4 in Catalina (MacOS 10.15.1), XCode 11.2.1. As in previous builds, I needed to add to the Makefile pointers to openssl:
CFLAGS += -I/usr/local/opt/openssl/include
LIBS += -L/usr/local/opt/openssl/lib
The make builds cleanly, no errors, no warnings. After make/make install, elogd segfaults immediately. I saw the same behavior with the version in gitlab. I kept my (very) old build and was able to make install it without recompiling and it still works.
I'll crack out the debugger when I have a chance to get more information, but has anyone else seen this problem?
|
|
Example scripts how to migrate or combine logbooks, posted by Roger Kalt on Mon Nov 18 16:58:21 2019
|
Attached the shell scripts using awk and sed how I have migrated two separated logbooks into one single and how I re-adjusted certain attributes. |
|