ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69703
|
Mon Oct 23 15:20:32 2023 |
| Germano Massullo | germano.massullo@cern.ch | Question | Linux | 3.1.4 | read-only elog server | Good day. I am writing this post to ask how I can turn an elog website into a read-only version that will stay online for historical documention purposes.
I tried to search on Elog documentation but I had no success
Thank you and have a nice day |
69702
|
Wed Oct 11 23:09:36 2023 |
| Laurent Jean-Rigaud | lollspam@free.fr | Question | Linux | V3.1.4-2e0f4719 | Re: Fail to upload enclosure in ELOG | Ok, i reply to myself as i could resolve the problem by changing the alpine Linux image to Debian light.
After debugging, the problem seems to be the compilation option used for alpine packets, which is not fully compatible when running on NAS Intel cpu.
The problem disappeared with Debian light, which should be less "aggressive" for optimization. I think the core is generated during imagemagick lib call (png, jpeg,pdf, ...).
Cheers
Laurent Jean-Rigaud wrote: |
Hi,
I currently testing last ELOG version from git in a docker with LDAP activated (https://hub.docker.com/r/usinagaz/elog-ldap). The goal is to use it on Synology NAS server, associated with local LDAP server.
The reverse proxy is done by embedded DSM nginx, according to FDQN associated to ELOG service (elog.corp.com). In Docker, URL is set to elog.corp.com.
All is good, but when I post any enclosure in any elog post, the elogd exits and docker is automatically restarted. The browser shows an error 405 generated by nginx server.
Do you have any idea of the cause of this problem ?
Thanks for help.
Laurent
|
|
69701
|
Mon Oct 9 16:43:06 2023 |
| Celeste Torkzaban | torkzaban at iqo.uni-hannover.de | Question | Windows | ELOG V3.1.3-793 | Re: link to attachment within html editor | thank you!
Stefan Ritt wrote: |
You can always insert the full link to the attachment like this one: https://elog.psi.ch/elogs/Forum/231009_104933/SCR14.PNG
But you can also use elog:69699/1 as shown here. Unfortunately you can do that only after the entry has been submitted, so you know the ID number of that entry. Once you have it, edit the entry and put it in.
Stefan
Celeste Torkzaban wrote: |
Hello,
I like the ELcode feature that lets you easily make an internal link to an attachment in the same post. However, I wasn't able to get this to work in the html editor, even though it's possible to use the ELcode format to link to another post in the logbook. When I type in elog :/1 in the html editor (without the space) and submit (even with an attachment present), it weirdly gets changed and shows up as 61/1 in the submitted elog, without any hyperlink. As far as I know we're using the standard elog code and only modified css parameters. Is there another syntax to link to attachments in html?
Testing it out here: 69699/1 (elog :/1 without the space turned into 69699/1)
|
|
|
69700
|
Mon Oct 9 12:30:44 2023 |
| Stefan Ritt | I guesstefan.ritt@psi.ch | Question | Windows | ELOG V3.1.3-793 | Re: link to attachment within html editor | You can always insert the full link to the attachment like this one: https://elog.psi.ch/elogs/Forum/231009_104933/SCR14.PNG
But you can also use elog:69699/1 as shown here. Unfortunately you can do that only after the entry has been submitted, so you know the ID number of that entry. Once you have it, edit the entry and put it in.
Stefan
Celeste Torkzaban wrote: |
Hello,
I like the ELcode feature that lets you easily make an internal link to an attachment in the same post. However, I wasn't able to get this to work in the html editor, even though it's possible to use the ELcode format to link to another post in the logbook. When I type in elog :/1 in the html editor (without the space) and submit (even with an attachment present), it weirdly gets changed and shows up as 61/1 in the submitted elog, without any hyperlink. As far as I know we're using the standard elog code and only modified css parameters. Is there another syntax to link to attachments in html?
Testing it out here: 69699/1 (elog :/1 without the space turned into 69699/1)
|
|
69699
|
Mon Oct 9 10:43:46 2023 |
| Celeste Torkzaban | torkzaban at iqo.uni-hannover.de | Question | Windows | ELOG V3.1.3-793 | link to attachment within html editor | Hello,
I like the ELcode feature that lets you easily make an internal link to an attachment in the same post. However, I wasn't able to get this to work in the html editor, even though it's possible to use the ELcode format to link to another post in the logbook. When I type in elog :/1 in the html editor (without the space) and submit (even with an attachment present), it weirdly gets changed and shows up as 61/1 in the submitted elog, without any hyperlink. As far as I know we're using the standard elog code and only modified css parameters. Is there another syntax to link to attachments in html?
Testing it out here: 69699/1 (elog :/1 without the space turned into 69699/1) |
69698
|
Fri Oct 6 11:19:34 2023 |
| Michael | woegerbauer.micha@gmail.com | Question | Windows | 3.1.4 | Filtered browsing | Hi,
is there a trick to get "Filtered browsing" working?
If i am on the first entry and i checked the checkbox of one Attribute, the next entry is still the second one and not the next with the same Attribute. |
69697
|
Tue Sep 19 10:58:14 2023 |
| Heinz Junkes | junkes@fhi-berlin.mpg.de | Bug report | Linux | elogd 3.1.4 | Re: elog server crashed due to cookies send by client | The server is crached because the author field was accidentally filled with a long string due to an automated (remote) script:
“
Author: The ion getter pump has successfully recovered and appears to be operating steadily once more. Consequently, I proceeded with sputtering to obtain an XPS survey scan of the Au sample. Initially, the stability of the X-ray function was compromised, leading to multiple interruptions. Subsequently, an unexplained issue arose regarding the collection of counts on the channeltron detector. Additionally, the emission current exhibited fluctuations. Fortunately, it seems that we have addressed and resolved the previous issues. In the image below, two XPS survey spectra are presented. The spectrum highlighted with a red line corresponds to the AlKa source, which was selected using the AlKa button. Conversely, the spectrum with a black line represents the MgKa source. In both cases, the energy configuration was set to 1486.7 eV. It's worth noting that the 1050 eV peak in both spectra corresponds to the Au4f state, with an energy displacement of 961.7 eV due to X-ray ghost lines caused by O contamination (84+961.7). It has come to my attention that the Mg source appears to have oxidized, a phenomenon we've observed before. Moreover, it's important to highlight that the difference between the peaks in the low binding energy region is approximately 100 eV, not the expected 233 eV (considering the energy difference between magnesium and aluminum). This observation holds true for both cases where the same energy setting was used. Additionally, the energy of the Au4f peakSotirios Tsatso
“
Instead of just "Sotirios Tsatso".
So it had nothing to do with the cookies etc.. But when the item created in this way was called up, the system crashed:
[248459.853246] elogd_misc[8407]: segfault at 561725164a4e ip 00007f8210c02854 sp 00007ffdcb92b338 error 4 in libc-2.31.so[7f8210a99000+178000]
[248459.853251] Code: 7f 07 c5 fe 7f 4f 20 c5 fe 7f 54 17 e0 c5 fe 7f 5c 17 c0 c5 f8 77 c3 48 39 f7 0f 87 ab 00 00 00 0f 84 e5 fe ff ff c5 fe 6f 26 <c5> fe 6f 6c 16 e0 c5 fe 6f 74 16 c0 c5 fe 6f 7c 16 a0 c5 7e 6f 44
Heinz Junkes wrote: |
Our elog instance (elogd 3.1.4 built Jan 13 2021, 20:44:20 revision ce2a48e9) has been running for years without any problems.
We have a new user who consistently crashes the elog:
GET /Omicron-STM-XPS/?rsort=Record%20date HTTP/1.1
Host: elog.fhi-berlin.mpg.de:4821
Cache-Control: max-age=0
DNT: 1
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
sec-gpc: 1
Sec-Fetch-Site: same-origin
Sec-Fetch-Mode: navigate
Sec-Fetch-User: ?1
Sec-Fetch-Dest: document
sec-ch-ua: "Google Chrome";v="117", "Not;A=Brand";v="8", "Chromium";v="117"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "Linux"
Referer: https://elog.fhi-berlin.mpg.de/elog/isc/Omicron-STM-XPS/
Accept-Encoding: gzip, deflate, br
Accept-Language: el-GR,el;q=0.9,en;q=0.8
Cookie: ufnm=Sotirios Tsatsos; urem=1; elmode=full; elattach=1; sid=CD2B04E2C3F02EA4; googtrans=/en/en; amp_6e403e=aWS6RQd5UjGctj5Ym_cDzA.c2Fsdm9fc290b2thaXRlbkB5YWhvby5jb20=..1hajnscc0.1hajnscc0.0.ac.ac
X-Forwarded-For: 141.14.151.26
X-Forwarded-Host: elog.fhi-berlin.mpg.de
X-Forwarded-Server: elog.fhi-berlin.mpg.de
Connection: Keep-Alive
Received unknown cookie "googtrans"
Received unknown cookie "amp_6e403e"
*** buffer overflow detected ***: terminated
Abort (core dumped)
|
|
69696
|
Mon Sep 18 14:38:30 2023 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Other | latest | Re: update elog downloads page | Thanks for the reminder, I updated the download instructions. |
|