| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67652
|
Tue Jan 14 21:50:50 2014 |
 | Grant | enzedder@me.com | Question | All | 2.9.2 | Users logged out? | Hi All,
I'm looking for a way (or if it is even possible?) for users to browse between logbooks without being logged out of their current logbook if they click on a logbook they are not authorised to access?
If they accidentally choose the wrong logbook they are forced to log back in again?
No guest access has been configured on any log.
TIA
|
|
69795
|
Wed Jul 10 17:43:07 2024 |
| Enrico Gamberini | enrico.gamberini@cern.ch | Bug report | Linux | 3.1.5-20240226 | broken http response when deployed on OpenShift | Hello!
We're setting up ELOG on OpenShift. ELOG is installed on a Alma Linux 9 image. The container and the elog demo works fine executing the docker image locally.
When deployed on OpenShift, we get a weird response, that results in a 502 Bad Gateway. The broken response looks like:
# curl -v -H 'X-Forwarded-User: enrico.gamberini@cern.ch' https://psi-elog-container2-elisa-epdtdi.app.cern.ch/demo/
<html>redir</html>
HTTP/1.1 200 Document follows
HTTP/1.1 200 Document follows
Server: ELOG HTTP 3.1.5-23df00d
Content-Type: text/html;charset=ISO-8859-1
Set-Cookie: elmode=Summary; path=/demo; expires=Friday, 07-Dec-35 06:30:26 GMT;
Pragma: no-cache
Cache-control: private, max-age=0, no-cache, no-store
Notice the HTML tag before the HTTP header, as well the duplicate HTTP header.
I understand that it might be difficult to reproduce, but any input would be very welcome!
Thanks!
Best,
Enrico |
|
69796
|
Thu Jul 11 15:25:19 2024 |
 | Enrico Gamberini | enrico.gamberini@cern.ch | Bug report | Linux | 3.1.5-20240226 | Re: broken http response when deployed on OpenShift | Sorry for posting again but something else came up.
Actually, building from source (elog-3.1.5-1.tar.gz) works just fine on OpenShift too.
The problem described below only happens when installing the packaged binary elog-3.1.5-20240226.el9.x86_64.rpm.
Best,
Enrico
| Enrico Gamberini wrote: |
|
Hello!
We're setting up ELOG on OpenShift. ELOG is installed on a Alma Linux 9 image. The container and the elog demo works fine executing the docker image locally.
When deployed on OpenShift, we get a weird response, that results in a 502 Bad Gateway. The broken response looks like:
# curl -v -H 'X-Forwarded-User: enrico.gamberini@cern.ch' https://psi-elog-container2-elisa-epdtdi.app.cern.ch/demo/
<html>redir</html>
HTTP/1.1 200 Document follows
HTTP/1.1 200 Document follows
Server: ELOG HTTP 3.1.5-23df00d
Content-Type: text/html;charset=ISO-8859-1
Set-Cookie: elmode=Summary; path=/demo; expires=Friday, 07-Dec-35 06:30:26 GMT;
Pragma: no-cache
Cache-control: private, max-age=0, no-cache, no-store
Notice the HTML tag before the HTTP header, as well the duplicate HTTP header.
I understand that it might be difficult to reproduce, but any input would be very welcome!
Thanks!
Best,
Enrico
|
|
|
279
|
Sun Apr 13 14:32:52 2003 |
| Justin Dieters | enderak@yahoo.com | Bug report | | | Re: Disappearing attachments | I am using 2.3.4 and I am still having this problem. If someone posts a
message with an attachment, and I then reply to that message, the attachment
gets 'deattached' from that message. However, the file is still in the
logbook directory, so it is possible to recover it, but it did cause a slight
panic the first time it happened :)
I see there is a 2.3.5 version now, but the changelog doesn't say anything
about this problem, so I have not tried it yet.
Is there a 'trick' to fix this problem?
EDIT: I noticed when I replyed to your message, your elog.cfg attachment is
no longer there. So it appears it's not fixed in 2.3.5 either..
> This is a known problem and has been fixed in version 2.3.4, which has been
> released today. To prove that it's working, I attached the current
> elogd.cfg from this forum. |
|
284
|
Mon Apr 14 18:24:18 2003 |
| Justin Dieters | enderak@yahoo.com | Bug report | | | Re: Disappearing attachments | EDIT: I downloaded the latest elogd.c from CVS, replaced the one from the
latest tar, and recompiled. Worked great!
Thanks for the prompt response, Stefan!
> > I am using 2.3.4 and I am still having this problem. If someone posts a
> > message with an attachment, and I then reply to that message, the attachment
> > gets 'deattached' from that message. However, the file is still in the
> > logbook directory, so it is possible to recover it, but it did cause a
> slight
> > panic the first time it happened :)
>
> Uups, that is indeed a problem. I found that it was unrelated to the first
> one, so it was there since quite some time now. I fixed it. It will come out
> in 2.3.6 or can be obtained already now from CVS. It is trongly recommended
> to upgrade all installations to avoid this problem. |
|
304
|
Tue Apr 22 22:23:27 2003 |
| Justin Dieters | enderak@yahoo.com | Bug report | | | Re: problem with 20+ attachments | I've been using elog for several months now, and one thing that's always
seemed odd to me are the things like max number of attachments and max
attachment size are defined right in the source code, and not in the config
file. It would seem that it would be simple to be able to define stuff like
that in the config file (and have defaults in case they weren't specified),
which would fix a lot of the recompiling problems - just edit the config file
and restart elog. Not that recompiling elog is difficult, it just seems like
recompiling for such a simple setting is overkill...
Anyway, just curious. Is there a technical reason this is not done?
Justin
> source of it. The reply/attachment bug is fixed, and a warning about
> exceeding the number of attachments will come soon. |
|
452
|
Tue Nov 18 23:19:57 2003 |
 | Justin Dieters | enderak@yahoo.com | Comment | Linux | 2.3.9 | Update request for Admin Guide | Heya, I've been using elog for a year or so, with a proxy through Apache,
but recently I've ran into some trouble with my Apache config, where
spammers were using my incorrectly configured proxy to send spam.
I have
some requests for the Administrator's Guide: "Running elogd under Apache".
I'm hoping a few little notes will save others the trouble I've gone
through. Neither of these are any fault of elog's or Apache's, but of my own
ignorance. (I am using elog 2.3.9, and Apache 2.something, if that matters)
1) When doing "ProxyPass ..." when setting up elog under Apache, do NOT put
"ProxyRequests On". This is not needed, if it is enabled and not set up
correctly, it allows spammers to send spam via Apache's proxy. More
information on this is here: http://www.apacheweek.com/issues/03-07-25,
about halfway down the page, under "Spammers use open Apache proxies"
Even though it doesn't mention ProxyRequests in the guide, I think there
should be a little side note mentioning that "ProxyRequests On" is NOT
needed, because I put it in, thinking it was - I am probably not the only one.
2) I have found that mod_proxy_http.c must be loaded in addition to
mod_proxy.c and mod_alias.c for the proxy to work, otherwise I get a 403
error. I think this should be mentioned as well. |
|
685
|
Tue Sep 7 13:05:49 2004 |
| T. Ribbrock | emgaron@gmx.net | Bug fix | Linux | 2.5.4 | Re: text display of ascii files not a good idea | [...]
> Probably it is fine to display only files ending in '.txt' per default.
> In addition a file that has more than say 1000 lines should probably
> also not be displayed (as default, optional OK).
No, '.txt' would definitely not be enough for me. I'm using elog to log all
administration of our network. In many cases, I simply attach a configuration
file. All those files are plain ASCII and none of them end in '.txt' - and I
would most definitely like them to be displayed inline like they are now. In
fact, this change was the main reason for me to upgrade to 2.5.4
Maybe a configuration option or a "display attachment" button would be the
best solution, then?
Cheerio,
Thomas |
|