| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69066
|
Mon Nov 25 16:25:21 2019 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Mac OSX | 3.1.4 | Re: Trouble on Catalina | 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?
|
|
|
69067
|
Mon Nov 25 16:32:07 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | 3.1.3-fd7f1e2 | Re: Executing a shell command using elogd Windows service | 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
|
|
|
|
69072
|
Wed Dec 4 10:15:56 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Linux | Windows | ELOG V3.1.4-ead | Re: How to selectively use Top/Bottom Text JavaScript. | 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
|
|
|
69073
|
Wed Dec 4 10:37:32 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | V3.1.3 | Re: Change column width in list mode? | 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?
|
|
|
69081
|
Wed Jan 22 16:35:47 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | Windows | Mac OSX | All | Other | 3.1.4 | Re: CSS for HTML Mails | The CSS has been embedded in the email end of 2018, so just upgrade your server.
https://bitbucket.org/ritt/elog/commits/5165daf35cc1fb066071827719079fe0c9aa5ffb
/Stefan
| Daniel Pfuhl wrote: |
|
Hi there,
we extensively use Logbuch as a change documentation platform.
E-Mail notifications for new entries are very important for us.
Since we store sensible data in our logbooks the server is protected by a firewall.
After the firewall was activated the HTML mails are not rendered by the Outlook Mail clients we use - when they are located in an "external" net behind the firewall. I assume that's because of the css stylesheet which is linked in the source code of the HTML mail.
Is there any chance to include the CSS information in the HTML code? Otherwise we would need to make the CSS accessable from anywhere which requires in turn that the path of the CSS file can be customized.
Any idea how to solved this issue?
Best regards,
daniel
|
|
|
69083
|
Wed Jan 22 19:30:41 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | Windows | Mac OSX | All | Other | 3.1.4 | Re: CSS for HTML Mails | a04faf9f is pretty old: https://bitbucket.org/ritt/elog/commits/a04faf9fa9ca74657240cdc827bd2d0ae48a9df1
It's from September 2018, where the change with the CSS has been made on Decemb er 2018. You have to pull the current version from the git repository and recompile the program yourself.
/Stefan
| Daniel Pfuhl wrote: |
|
Hmm, I'm pretty sure that we are on the latest version already.
We use ELOG V3.1.4-a04faf9f
I downloaded a fresh install binary for Windows and compared the checksums:
SHA256: 0A98485134E0D43959CB6734F977B02DC9FA884D6994CE3BA141664451FDA5E5
SHA256: 0A98485134E0D43959CB6734F977B02DC9FA884D6994CE3BA141664451FDA5E5
same same.
Or do I have to change to config in order to include the CSS in the HTML?
regards,
daniel
| Stefan Ritt wrote: |
|
The CSS has been embedded in the email end of 2018, so just upgrade your server.
https://bitbucket.org/ritt/elog/commits/5165daf35cc1fb066071827719079fe0c9aa5ffb
/Stefan
| Daniel Pfuhl wrote: |
|
Hi there,
we extensively use Logbuch as a change documentation platform.
E-Mail notifications for new entries are very important for us.
Since we store sensible data in our logbooks the server is protected by a firewall.
After the firewall was activated the HTML mails are not rendered by the Outlook Mail clients we use - when they are located in an "external" net behind the firewall. I assume that's because of the css stylesheet which is linked in the source code of the HTML mail.
Is there any chance to include the CSS information in the HTML code? Otherwise we would need to make the CSS accessable from anywhere which requires in turn that the path of the CSS file can be customized.
Any idea how to solved this issue?
Best regards,
daniel
|
|
|
|
|
69085
|
Wed Jan 22 20:02:09 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | 3.1.4 | Re: HTML editor tools grayed out | This typically happens if you update only the executabe and not the full directory tree with the ELOG JavaScript files.
/Stefan
| Ehab Fanous wrote: |
|
After we upgarde to eLog 3.1.4 ... The HTML editor tools are grayed out and you can't paste any images in the body of the log like I did below.. Any help will be much appreciated..
|
|
|
69100
|
Fri Jan 31 15:27:21 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 3.14 RPM | Re: Elogd crashes on search | Do you see the same problem on this server here?
If not, then it must be related to your specific configuration. You have to teach me how to reporduce the error in order to fix it. Best would be a minimal elogd.cfg which causes the error.
Stefan
| Laurent Jean-Rigaud wrote: |
|
OS: CentOS 7 x86_64 up2date with RPM 3.14 x86_64
- Connexion to ELOG
- open one logbook and click search,
- input "test" and click "Search" : BOOM
- Firefox can not connect anymore on ELOG.
The crash is met with several words now ("test", "post", "4.5", are the one i know). We use a mirror server and the problem appears also on it .
NB: the hangs appears on EL6 x86_64 server with customized RPM built by myself. I retry with 3.14 SRPMS avalaible from ELOG site with same results. Idem with last GIT version. So i tested on EL7 with official RPM x86_64 (not suitable for EL6 as it needs GLIBC_2.14) before to open this ticket.
Terminal traces on server side follows.
[root@localhost /]# /usr/local/sbin/elogd -c /usr/local/elog/elogd.cfg 2>&1
elogd 3.1.4 built Sep 26 2018, 13:14:57 revision 966e3dd
File "/var/run/elogd.pid" exists, using "/var/run/elogd.pid.8080" instead.
Falling back to default group "elog"
Falling back to default user "elog"
CKeditor detected
Falling back to default group "elog"
Falling back to default user "elog"
Falling back to default group "elog"
Falling back to default user "elog"
Falling back to default group "elog"
Falling back to default user "elog"
Falling back to default group "elog"
Falling back to default user "elog"
ImageMagick NOT detected. Image scaling will not work.
Indexing logbooks ... done
Server listening on port 8080 ...
*** Error in `/usr/local/sbin/elogd': free(): invalid next size (normal): 0x0000000001c59310 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x81679)[0x7f45a898f679]
/usr/local/sbin/elogd[0x45e756]
/usr/local/sbin/elogd[0x4824b0]
/usr/local/sbin/elogd[0x4a69b1]
/usr/local/sbin/elogd[0x4a7023]
/usr/local/sbin/elogd[0x4a954a]
/usr/local/sbin/elogd[0x4ac9d3]
/usr/local/sbin/elogd[0x4035a6]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f45a8930505]
/usr/local/sbin/elogd[0x4044d3]
======= Memory map: ========
00400000-004e3000 r-xp 00000000 fd:00 52822202 /usr/local/sbin/elogd
006e2000-006e3000 r--p 000e2000 fd:00 52822202 /usr/local/sbin/elogd
006e3000-007c4000 rw-p 000e3000 fd:00 52822202 /usr/local/sbin/elogd
007c4000-0173a000 rw-p 00000000 00:00 0
01a66000-01c8f000 rw-p 00000000 00:00 0 [heap]
7f459bdea000-7f459bdff000 r-xp 00000000 fd:00 84 /usr/lib64/libgcc_s-4.8.5-20150702.so.1
7f459bdff000-7f459bffe000 ---p 00015000 fd:00 84 /usr/lib64/libgcc_s-4.8.5-20150702.so.1
7f459bffe000-7f459bfff000 r--p 00014000 fd:00 84 /usr/lib64/libgcc_s-4.8.5-20150702.so.1
7f459bfff000-7f459c000000 rw-p 00015000 fd:00 84 /usr/lib64/libgcc_s-4.8.5-20150702.so.1
7f459c000000-7f459c021000 rw-p 00000000 00:00 0
7f459c021000-7f45a0000000 ---p 00000000 00:00 0
7f45a010c000-7f45a0114000 r-xp 00000000 fd:00 1598592 /usr/lib64/libnss_sss.so.2
7f45a0114000-7f45a0313000 ---p 00008000 fd:00 1598592 /usr/lib64/libnss_sss.so.2
7f45a0313000-7f45a0314000 r--p 00007000 fd:00 1598592 /usr/lib64/libnss_sss.so.2
7f45a0314000-7f45a0315000 rw-p 00008000 fd:00 1598592 /usr/lib64/libnss_sss.so.2
7f45a0315000-7f45a0321000 r-xp 00000000 fd:00 22487 /usr/lib64/libnss_files-2.17.so
7f45a0321000-7f45a0520000 ---p 0000c000 fd:00 22487 /usr/lib64/libnss_files-2.17.so
7f45a0520000-7f45a0521000 r--p 0000b000 fd:00 22487 /usr/lib64/libnss_files-2.17.so
7f45a0521000-7f45a0522000 rw-p 0000c000 fd:00 22487 /usr/lib64/libnss_files-2.17.so
7f45a0522000-7f45a0528000 rw-p 00000000 00:00 0
7f45a0528000-7f45a6a52000 r--p 00000000 fd:00 50336362 /usr/lib/locale/locale-archive
7f45a6a52000-7f45a6ab2000 r-xp 00000000 fd:00 22554 /usr/lib64/libpcre.so.1.2.0
7f45a6ab2000-7f45a6cb2000 ---p 00060000 fd:00 22554 /usr/lib64/libpcre.so.1.2.0
7f45a6cb2000-7f45a6cb3000 r--p 00060000 fd:00 22554 /usr/lib64/libpcre.so.1.2.0
7f45a6cb3000-7f45a6cb4000 rw-p 00061000 fd:00 22554 /usr/lib64/libpcre.so.1.2.0
7f45a6cb4000-7f45a6cd8000 r-xp 00000000 fd:00 40935 /usr/lib64/libselinux.so.1
7f45a6cd8000-7f45a6ed7000 ---p 00024000 fd:00 40935 /usr/lib64/libselinux.so.1
7f45a6ed7000-7f45a6ed8000 r--p 00023000 fd:00 40935 /usr/lib64/libselinux.so.1
7f45a6ed8000-7f45a6ed9000 rw-p 00024000 fd:00 40935 /usr/lib64/libselinux.so.1
7f45a6ed9000-7f45a6edb000 rw-p 00000000 00:00 0
7f45a6edb000-7f45a6ef2000 r-xp 00000000 fd:00 22495 /usr/lib64/libpthread-2.17.so
7f45a6ef2000-7f45a70f1000 ---p 00017000 fd:00 22495 /usr/lib64/libpthread-2.17.so
7f45a70f1000-7f45a70f2000 r--p 00016000 fd:00 22495 /usr/lib64/libpthread-2.17.so
7f45a70f2000-7f45a70f3000 rw-p 00017000 fd:00 22495 /usr/lib64/libpthread-2.17.so
7f45a70f3000-7f45a70f7000 rw-p 00000000 00:00 0
7f45a70f7000-7f45a710d000 r-xp 00000000 fd:00 22497 /usr/lib64/libresolv-2.17.so
7f45a710d000-7f45a730c000 ---p 00016000 fd:00 22497 /usr/lib64/libresolv-2.17.so
7f45a730c000-7f45a730d000 r--p 00015000 fd:00 22497 /usr/lib64/libresolv-2.17.so
7f45a730d000-7f45a730e000 rw-p 00016000 fd:00 22497 /usr/lib64/libresolv-2.17.so
7f45a730e000-7f45a7310000 rw-p 00000000 00:00 0
7f45a7310000-7f45a7313000 r-xp 00000000 fd:00 62649 /usr/lib64/libkeyutils.so.1.5
7f45a7313000-7f45a7512000 ---p 00003000 fd:00 62649 /usr/lib64/libkeyutils.so.1.5
7f45a7512000-7f45a7513000 r--p 00002000 fd:00 62649 /usr/lib64/libkeyutils.so.1.5
7f45a7513000-7f45a7514000 rw-p 00003000 fd:00 62649 /usr/lib64/libkeyutils.so.1.5
7f45a7514000-7f45a7522000 r-xp 00000000 fd:00 321861 /usr/lib64/libkrb5support.so.0.1
7f45a7522000-7f45a7722000 ---p 0000e000 fd:00 321861 /usr/lib64/libkrb5support.so.0.1
7f45a7722000-7f45a7723000 r--p 0000e000 fd:00 321861 /usr/lib64/libkrb5support.so.0.1
7f45a7723000-7f45a7724000 rw-p 0000f000 fd:00 321861 /usr/lib64/libkrb5support.so.0.1
7f45a7724000-7f45a7739000 r-xp 00000000 fd:00 40937 /usr/lib64/libz.so.1.2.7
7f45a7739000-7f45a7938000 ---p 00015000 fd:00 40937 /usr/lib64/libz.so.1.2.7
7f45a7938000-7f45a7939000 r--p 00014000 fd:00 40937 /usr/lib64/libz.so.1.2.7
7f45a7939000-7f45a793a000 rw-p 00015000 fd:00 40937 /usr/lib64/libz.so.1.2.7
7f45a793a000-7f45a793c000 r-xp 00000000 fd:00 22475 /usr/lib64/libdl-2.17.so
7f45a793c000-7f45a7b3c000 ---p 00002000 fd:00 22475 /usr/lib64/libdl-2.17.so
7f45a7b3c000-7f45a7b3d000 r--p 00002000 fd:00 22475 /usr/lib64/libdl-2.17.so
7f45a7b3d000-7f45a7b3e000 rw-p 00003000 fd:00 22475 /usr/lib64/libdl-2.17.so
7f45a7b3e000-7f45a7d74000 r-xp 00000000 fd:00 303887 /usr/lib64/libcrypto.so.1.0.2k
7f45a7d74000-7f45a7f74000 ---p 00236000 fd:00 303887 /usr/lib64/libcrypto.so.1.0.2k
7f45a7f74000-7f45a7f90000 r--p 00236000 fd:00 303887 /usr/lib64/libcrypto.so.1.0.2k
7f45a7f90000-7f45a7f9d000 rw-p 00252000 fd:00 303887 /usr/lib64/libcrypto.so.1.0.2k
7f45a7f9d000-7f45a7fa1000 rw-p 00000000 00:00 0
7f45a7fa1000-7f45a7fd2000 r-xp 00000000 fd:00 321856 /usr/lib64/libk5crypto.so.3.1
Abandon [sorry, French locale]
Logbook contains 445 entries (shown in ELOG window), 384 files and 4 folders (2017 to 2020).
Thanks for help as i start to be annoying to unuse search function.
|
|
|