ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
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)
|
|
68156
|
Mon Oct 26 15:20:44 2015 |
| Julian Brower | julian.brower@stfc.ac.uk | Question | Windows | latest | Please advise on how to set up selective email notification on logbooks | Please advise on how to set up selective email notification on logbooks; We want to send an email to specific people when an event that involves them is entered?
At the moment, we currently get an email entry for every new logbook entry. Thanks
|
68157
|
Mon Oct 26 15:24:44 2015 |
| Julian Brower | julian.brower@stfc.ac.uk | Question | Windows | Latest | How can we calculate and display the difference between two time entries on a log entry | See drawing below: We have a beam on and a beam off time. We want to fill in the lost time automaticaaly. Please can you help? Julian
|
Attachment 1: Log_time_entry.jpg
|
|
68159
|
Tue Oct 27 09:26:56 2015 |
| Julian Brower | julian.brower@stfc.ac.uk | Question | Windows | Latest | Re: How can we calculate and display the difference between two time entries on a log entry | Stefan, I am not an expert in this field so I wondered how one goes about finding someone to write this and how one amends the soruce code? Is that allowed? Is it a feature than may be of use for other users? Julian
Stefan Ritt wrote: |
Unfortunately elog cannot do calculations based on certain fields. You could however add some Javascript code (via "Bottom text = ..." for example), which does that. But that requires JavaScript knowledge to do so.
Julian Brower wrote: |
See drawing below: We have a beam on and a beam off time. We want to fill in the lost time automaticaaly. Please can you help? Julian
|
|
|
68166
|
Tue Oct 27 14:58:20 2015 |
| Julian Brower | julian.brower@stfc.ac.uk | Question | Windows | latest | Re: Please advise on how to set up selective email notification on logbooks | Thanks Andreas, I will read that section. Julian
Andreas Luedeke wrote: |
Hi Julian,
there is a whole chapter in the documentation about that: https://midas.psi.ch/elog/config.html#email
If I have to send email, e.g. for Controls issues entered in the operation logbook, I do send the email to a specific mailman mailing list for that group.
It is cumbersome to manage email groups in the logbook configuration - in particular if the same lists exists in different logbooks. I only refer to the mailing list then in ELOG, and the groups can manage their lists themself.
I do maintain about 30 logbooks and there are about 10 groups at my institutes that desire email notifications for ELOG entries related to the systems they manage.
Cheers
Andreas
Julian Brower wrote: |
Please advise on how to set up selective email notification on logbooks; We want to send an email to specific people when an event that involves them is entered?
At the moment, we currently get an email entry for every new logbook entry. Thanks
|
|
|
67098
|
Tue Aug 2 13:55:06 2011 |
| Juergen Lupke | juergen.lupke@computacenter.com | Question | Linux | V2.9.0-241 | present Text | I have define a MOption BACKUP = Server, Switch, Router any now i link to use the Status of the Backup Option to display diffrent html file in the Text field, i the a posible way to do this ?
sample:
MOption BACKUP = Server, Switch, Router
{Server&Switch&Router} Present Text = file1
{Server&Switch} Present Text = file2 |
65740
|
Fri Feb 15 03:16:45 2008 |
| Jeff Stoner | jstoner@opsource.net | Request | Linux | 2.7.2 | move mxml code into elog's src directory | The mxml source code should be moved into the elog-*/src directory. This requires changing the Makefile to:
MXMLDIR = src/mxml
Reason for change: if you want to build several versions of elog and you unpack the distributions in the same top-level directory, the most recently unpackaged version will overwrite the mxml directory contents, possibly introducing bugs.
|
65743
|
Fri Feb 15 22:24:38 2008 |
| Jeff Stoner | jstoner@opsource.net | Bug report | Linux | 2.7.2 2041 | elog crashing on startup | I installed elog 2.7.2 rev 2041 into /data/elog on Redhat ES 4 Update 4. This is my initial elogd.cfg file:
[global] port = 80 Resource dir = /data/elog/elog Logbook dir = /data/elog/elog/logbooks Logfile = /data/elog/elog/logs/access_log Logging level = 2 Resolve host names = 0 Usr = nobody Grp = nobody
[demo] Theme = default Comment = General linux tips & tricks Attributes = Author, Type, Category, Subject Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other Options Category = General, Hardware, Software, Network, Other Extendable Options = Category Required Attributes = Author, Type Page Title = ELOG - $subject Reverse sort = 1 Quick filter = Date, Type
and start elogd - all is right with the world, everything is working properly. I shut down elog and try to add more logbooks using this template:
[A-B] Subdir = cr_a-b Comment = Change requests for Customers A-B Menu commands = New, Reply, Download, Find, Last day List Menu commands = New, Find Display mode = summary
I create 14 of them, one for every 2 letters of the English alphabet and 0-9. The logbook name and Subdir change appropriately. When I start elog, it stays up for about 30 seconds, then crashes. No messages are recorded in syslog nor in the logfile. The only thing that looks suspicious are a couple lines in syslog:
Feb 15 17:11:05 iadopsutil04p elogd[23761]: elogd 2.7.2 built Feb 14 2008, 20:55:38 Feb 15 17:11:05 iadopsutil04p elogd[23761]: revision 2041 Feb 15 17:11:05 iadopsutil04p elogd[23761]: FCKedit detected Feb 15 17:11:05 iadopsutil04p elogd[23763]: Cannot restore original GID/UID. Feb 15 17:11:05 iadopsutil04p elogd[23763]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied Feb 15 17:11:05 iadopsutil04p elogd[23761]: Server listening on port 80 ...
This is obviously the child process responsible for the highlighted lines and it's coming from the cleanup function. Why it's getting called is beyond me.
Ideas? |
|