| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69887
|
Thu Aug 7 11:04:39 2025 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | V3.1.5-30a | Re: once a week we are having elogd segault? | Probably some very strange URL form nexpose to trigger a potential buffer overflow. If I get the precise URL which crashes elogd, I can reproduce and fix it.
Otherwise my usual advice: Run elogd behind an Apache proxy and do the authentication there. This way nexpose does not get to elogd, it will stop at the Apache (without the proper credentials).
Steafn
| mathew goebel wrote: |
|
We have since discovered that the security team is scanning the box in question once a week when the service crashes, with nexpose.
So if you see something similar then you might want to explore that.
| mathew goebel wrote: |
|
Jul 17 20:36:21 elog kernel: elogd[179095]: segfault at 7ffda4d82000 ip 00007f97033a1406 sp 00007ffda4d58c38 error 6 in libc-2.28.so[7f9703374000+1cd000]
Elog version ELOG V3.1.5-30ada1df
Running on a Rehdat 8 enterprise server
compiled with a Makefile change :: change -Wno-unused-result to -Wno-unused-value
Wondering if anyone has been seeing this?
|
|
|
|
69886
|
Wed Aug 6 17:08:46 2025 |
| mathew goebel | mgoebel@emich.edu | Question | Linux | V3.1.5-30a | Re: once a week we are having elogd segault? | We have since discovered that the security team is scanning the box in question once a week when the service crashes, with nexpose.
So if you see something similar then you might want to explore that.
| mathew goebel wrote: |
|
Jul 17 20:36:21 elog kernel: elogd[179095]: segfault at 7ffda4d82000 ip 00007f97033a1406 sp 00007ffda4d58c38 error 6 in libc-2.28.so[7f9703374000+1cd000]
Elog version ELOG V3.1.5-30ada1df
Running on a Rehdat 8 enterprise server
compiled with a Makefile change :: change -Wno-unused-result to -Wno-unused-value
Wondering if anyone has been seeing this?
|
|
|
69885
|
Sun Jul 20 23:20:02 2025 |
 | Harry Martin | harrymartin772@gmail.com | Bug report | Linux | 3.1.5 | Re: 3-level conditional not working | Tried a variant, this time for NEW entries (not EDIT), which I meant to do to begin with; sorry if that was confusing.
[cond_test]
attributes = region, manufacturer, model
options region = american{us}, japanese{jp}, european{eu}
show attributes = region
{us} options manufacturer = ford, chrysler, gm
{jp} options manufacturer = toyota{toy}, nissan{nis}, mitsubishi{mit}
{eu} options manufacturer = audi, mercedes, bmw, volvo, fiat
{us} show attributes = region, manufacturer
{jp} show attributes = region, manufacturer
{eu} show attributes = region, manufacturer
{toy} options model = corolla, prius, miata
{nis} options model = sentra, murano
{mit} options model = starion, outlander, mirage
{toy,nis,mit} show attributes = region, manufacturer, model
I'm not sure if my multi-character conditional names are allowed or not, but they do seem to work... somewhat. Note that I even tried a couple different ways of specifying which attributes to show (single versus multiple OR conditionals). The problem now is that all of the attributes are always shown, seeming to ignore the conditionals entirely.
| Harry Martin wrote: |
|
Not sure if this is a bug or not; if it is not, kindly reclassify the category.
Following is a small example of what I will dub a 3-level, conditional logbook:
[cond_test]
attributes = region, manufacturer, model
show attributes edit = region
options region = american{1}, japanese{2}, european{3}
{1} options manufacturer = ford, chrysler, gm
{2} options manufacturer = toyota{4}, nissan{5}, mitsubishi{6}
{3} options manufacturer = audi, mercedes, bmw, volvo, fiat
{1,2,3} show attributes edit = region, manufacturer
{4} options model = corolla, prius, miata
{5} options model = sentra, murano
{6} options model = starion, outlander, mirage
{4,5,6} show attributes edit = region, manufacturer, model
This example is hardly complete, but it is sufficient to demonstrate the issue I am running into. This works until I select from the 2nd level (manufacturer); it won't display the dropdown for the model (I think my show attribute edit is supposed to display that). Is there a restriction on how many levels of conditional I can have? If there is, it would be disappointing because I am trying to do something similar to this example.
I hope there is something very simple I can do to correct this, or perhaps a completely different approach that accomplishes the same thing. I'd like to stick with the multi-level selection process as I have done here.
I am running elog 3.1.5 on Devuan Chimaera (approx. Debian Bullseye, sans systemd) in a Virtualbox VM.
|
|
|
69884
|
Sat Jul 19 00:02:45 2025 |
| Harry Martin | harrymartin772@gmail.com | Bug report | Linux | 3.1.5 | Re: collapse does not seem to work as expected | I also notice that collapse does not work properly if I have anything selected in the quick filter.
| Harry Martin wrote: |
|
Figured it out: I had "Sort Attributes" set on the logbooks that were failing to collapse correctly. At least, I think that is the distinction.
I think I can live with "Sort Attributes" disabled; I don't recall why I chose to set the "Sort Attributes" in the first place. But I still think this is an issue.
| Harry Martin wrote: |
|
I should add that this does not happen in every logbook. I'm looking into what the distinction is that causes this in certain logbooks and not in others.
| Harry Martin wrote: |
|
When I click on "collapse," even several times, I still see all the replies in each thread rather than just one entry representing each entire thread.
I am running elogd 3.1.5 on devuan chimaera (bullseye) which I built from source. I had the same results with 3.1.4 and 3.1.3.
I tried to disable the quick filter just to see if that impacted the behavior, but it didn't.
If there are any other tests I can use to narrow the problem, please suggest them. Without a working collapse feature, I cannot get a quick birdseye view of, say, all open threads.
|
|
|
|
|
69883
|
Fri Jul 18 23:10:33 2025 |
| Harry Martin | harrymartin772@gmail.com | Bug report | Linux | 3.1.5 | Re: collapse does not seem to work as expected | Figured it out: I had "Sort Attributes" set on the logbooks that were failing to collapse correctly. At least, I think that is the distinction.
I think I can live with "Sort Attributes" disabled; I don't recall why I chose to set the "Sort Attributes" in the first place. But I still think this is an issue.
| Harry Martin wrote: |
|
I should add that this does not happen in every logbook. I'm looking into what the distinction is that causes this in certain logbooks and not in others.
| Harry Martin wrote: |
|
When I click on "collapse," even several times, I still see all the replies in each thread rather than just one entry representing each entire thread.
I am running elogd 3.1.5 on devuan chimaera (bullseye) which I built from source. I had the same results with 3.1.4 and 3.1.3.
I tried to disable the quick filter just to see if that impacted the behavior, but it didn't.
If there are any other tests I can use to narrow the problem, please suggest them. Without a working collapse feature, I cannot get a quick birdseye view of, say, all open threads.
|
|
|
|
69882
|
Fri Jul 18 22:42:02 2025 |
| Harry Martin | harrymartin772@gmail.com | Bug report | Linux | 3.1.5 | Re: collapse does not seem to work as expected | I should add that this does not happen in every logbook. I'm looking into what the distinction is that causes this in certain logbooks and not in others.
| Harry Martin wrote: |
|
When I click on "collapse," even several times, I still see all the replies in each thread rather than just one entry representing each entire thread.
I am running elogd 3.1.5 on devuan chimaera (bullseye) which I built from source. I had the same results with 3.1.4 and 3.1.3.
I tried to disable the quick filter just to see if that impacted the behavior, but it didn't.
If there are any other tests I can use to narrow the problem, please suggest them. Without a working collapse feature, I cannot get a quick birdseye view of, say, all open threads.
|
|
|
69881
|
Fri Jul 18 17:46:43 2025 |
 | mathew goebel | mgoebel@emich.edu | Question | Linux | V3.1.5-30a | once a week we are having elogd segault? | Jul 17 20:36:21 elog kernel: elogd[179095]: segfault at 7ffda4d82000 ip 00007f97033a1406 sp 00007ffda4d58c38 error 6 in libc-2.28.so[7f9703374000+1cd000]
Elog version ELOG V3.1.5-30ada1df
Running on a Rehdat 8 enterprise server
compiled with a Makefile change :: change -Wno-unused-result to -Wno-unused-value
Wondering if anyone has been seeing this? |
|
69880
|
Thu Jul 17 23:43:25 2025 |
| Harry Martin | harrymartin772@gmail.com | Bug report | Linux | 3.1.5 | collapse does not seem to work as expected | When I click on "collapse," even several times, I still see all the replies in each thread rather than just one entry representing each entire thread.
I am running elogd 3.1.5 on devuan chimaera (bullseye) which I built from source. I had the same results with 3.1.4 and 3.1.3.
I tried to disable the quick filter just to see if that impacted the behavior, but it didn't.
If there are any other tests I can use to narrow the problem, please suggest them. Without a working collapse feature, I cannot get a quick birdseye view of, say, all open threads. |
|