ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69621
|
Fri Jan 20 13:12:48 2023 |
| Sebastian Schenk | sebastian.schenk@physik.uni-halle.de | Request | All | - | Re: Wikipedia Article deleted | I have requested an undeletion of the article. The article was deleted "PROD", which means that someone tagged it. And if noone removes the tag, it could be deleted.
I could revive the article. So in the future, One should have an eye on it and maybe update the current version of the software.
If there iy an paper on the elog, maybe it could be cited for more creditability.
Andreas Luedeke wrote: |
It looks to me like only an author of an article can contradict a deletion. I did not find a single method to even comment on the deletion.
I am not an Wikipedia expert, can anyone suggest on how to push for the article to be restored? Or do we just write it again, until people stop deleting it?
Stefan Ritt wrote: |
I agree. I ahead ;-) I think it is not a good idea if the ELOG author pushes on that, but better someone else.
Best,
Stefan
Sebastian Schenk wrote: |
Hello,
I noticed the wikipedia article of the ELOG got deleted in November 2021.
With the reason: "Poorly sourced article, and I was not able to find good sources myself."
I could access the old article through web.archive.org, but for the project it would be good, if the article got revived.
|
|
|
|
69624
|
Mon Jan 23 21:21:56 2023 |
| Edmund Blomley | edmund.blomley@kit.edu | Request | All | - | Re: Wikipedia Article deleted | It was now moved to the Draft space (which I did not even now existed so far): https://en.wikipedia.org/wiki/Draft:ELOG
Sebastian Schenk wrote: |
I have requested an undeletion of the article. The article was deleted "PROD", which means that someone tagged it. And if noone removes the tag, it could be deleted.
I could revive the article. So in the future, One should have an eye on it and maybe update the current version of the software.
If there iy an paper on the elog, maybe it could be cited for more creditability.
Andreas Luedeke wrote: |
It looks to me like only an author of an article can contradict a deletion. I did not find a single method to even comment on the deletion.
I am not an Wikipedia expert, can anyone suggest on how to push for the article to be restored? Or do we just write it again, until people stop deleting it?
Stefan Ritt wrote: |
I agree. I ahead ;-) I think it is not a good idea if the ELOG author pushes on that, but better someone else.
Best,
Stefan
Sebastian Schenk wrote: |
Hello,
I noticed the wikipedia article of the ELOG got deleted in November 2021.
With the reason: "Poorly sourced article, and I was not able to find good sources myself."
I could access the old article through web.archive.org, but for the project it would be good, if the article got revived.
|
|
|
|
|
69625
|
Mon Jan 23 22:24:23 2023 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | - | Re: Wikipedia Article deleted | I added some more references, that's about all I can do. Not sure if that is enough.
Stefan
Edmund Blomley wrote: |
It was now moved to the Draft space (which I did not even now existed so far): https://en.wikipedia.org/wiki/Draft:ELOG
Sebastian Schenk wrote: |
I have requested an undeletion of the article. The article was deleted "PROD", which means that someone tagged it. And if noone removes the tag, it could be deleted.
I could revive the article. So in the future, One should have an eye on it and maybe update the current version of the software.
If there iy an paper on the elog, maybe it could be cited for more creditability.
Andreas Luedeke wrote: |
It looks to me like only an author of an article can contradict a deletion. I did not find a single method to even comment on the deletion.
I am not an Wikipedia expert, can anyone suggest on how to push for the article to be restored? Or do we just write it again, until people stop deleting it?
Stefan Ritt wrote: |
I agree. I ahead ;-) I think it is not a good idea if the ELOG author pushes on that, but better someone else.
Best,
Stefan
Sebastian Schenk wrote: |
Hello,
I noticed the wikipedia article of the ELOG got deleted in November 2021.
With the reason: "Poorly sourced article, and I was not able to find good sources myself."
I could access the old article through web.archive.org, but for the project it would be good, if the article got revived.
|
|
|
|
|
|
69626
|
Tue Jan 24 11:31:59 2023 |
| Edmund Blomley | edmund.blomley@kit.edu | Request | All | - | Re: Wikipedia Article deleted | If I understand it correctly I think it has to be submitted for review with the blue button on that page, just not sure if that should come from your side or someone else
Stefan Ritt wrote: |
I added some more references, that's about all I can do. Not sure if that is enough.
Stefan
Edmund Blomley wrote: |
It was now moved to the Draft space (which I did not even now existed so far): https://en.wikipedia.org/wiki/Draft:ELOG
Sebastian Schenk wrote: |
I have requested an undeletion of the article. The article was deleted "PROD", which means that someone tagged it. And if noone removes the tag, it could be deleted.
I could revive the article. So in the future, One should have an eye on it and maybe update the current version of the software.
If there iy an paper on the elog, maybe it could be cited for more creditability.
Andreas Luedeke wrote: |
It looks to me like only an author of an article can contradict a deletion. I did not find a single method to even comment on the deletion.
I am not an Wikipedia expert, can anyone suggest on how to push for the article to be restored? Or do we just write it again, until people stop deleting it?
Stefan Ritt wrote: |
I agree. I ahead ;-) I think it is not a good idea if the ELOG author pushes on that, but better someone else.
Best,
Stefan
Sebastian Schenk wrote: |
Hello,
I noticed the wikipedia article of the ELOG got deleted in November 2021.
With the reason: "Poorly sourced article, and I was not able to find good sources myself."
I could access the old article through web.archive.org, but for the project it would be good, if the article got revived.
|
|
|
|
|
|
|
69630
|
Wed Jan 25 19:51:29 2023 |
| Tamas Gal | tgal@km3net.de | Bug report | Linux | 3.1.4-3 | Re: Invalid Content-Length in header when running behind a load balancer | I put the ELOG service behind an Apache reverse proxy which is now sitting behind the HAProxy. It works like this, but it's just a workaround. I am pretty sure that ELOG has problems to communicate with HAProxy correctly and it seems that Apache is more forgiving. So that the chain HAProxy -> Apache -> ELOG and vice versa is working.
If anyone manages to figure out what's wrong, I am happy to get rid of the extra reverse proxy layer!
Tamas Gal wrote: |
I am still struggling to get ELOG running behind a load balancer and hope to get some advice here. As already reported in https://elog.psi.ch/elogs/Forum/69542 I observed an infinite loop of redirects when prompted to log in and using a non-empty password file. Without a password, the service worked as expected. This was with version 3.1.3.
With the new version 3.1.4-3, I get another error: "Invalid Content-Length in header" when I click on "submit" of a new post. Viewing the logbooks works fine. The instance is currently live and running here: https://elog.test.km3net.de but I might change it anytime due to debugging etc.
This is a kind of difficult thing to debug (I spent the whole day and no progress). The only thing I've found was this post: https://techcommunity.microsoft.com/t5/iis-support-blog/invalid-content-length/ba-p/3038724 where it seems that some responses are not RFC conform and were rejected in the load-balancer.
The load balancer I use is HAProxy, the same as in my old setup where I got the infinite redirects, and I can't find any setting which would work. To my understanding, the most basic setup should work just fine. The SSL termination is on the load-balancer side so ELOG doesn't even have to know anything about it. The configuration is below. I am running a single instance, so there is not even replication with session keep-alive via cookies or anything fancy.
I also want to mention that I am runnin around 30 different services behind the load balancer and none of them are having any issues with the SSL termination or the load-balancing itself, that's why assume that something in ELOG is either non-conform or buggy.
Any thoughts? I'd really like to use the same infrastructure for the ELOG service as for every other service (automatic certificate renewal via letsencrypt, load-balancing, easy movement to other nodes, SSL termination etc.), to minimise the complexity of our Docker Swarm system.
backend be_elog.km3net.de
mode http
server-template km3net-elog- 1 km3net-elog_elog:8080 check resolvers docker init-addr libc,none
Btw. I am running ELOG with -v but I don't see any error whatsoever in the logs:
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET /demo/ HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "ios_specific_templates_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_anonymous_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_group_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_group_trait"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_trait"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_user_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "logged_out_marketing_header_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 3437 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET / HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 120 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET /demo/ HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 3518 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET / HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 120 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET /demo/ HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 3518 bytes
|
|
69631
|
Wed Jan 25 21:44:51 2023 |
| Laurent Jean-Rigaud | lollspam@free.fr | Question | Linux | 3.1.3 | Re: ssl certificate | Hi Giuseppe,
The new certificate files should be copy under ssl folder (/usr/local/elog/ssl or /usr/share/elog/ssl by example, closed to templates and script directories) in place of the embedded (autosigned) certificate files enclosed with ELOG source.
It seems that there is no parameter to set a custom path.
SSL = <0 | 1>
Turn on Secure Socket Layer transport. If SSL is on, one can connect via https://... to the elogd daemon. If the URL = directive is used, make sure to use https://... instead of http://... there. The ELOG distribution contains a simple self-signed certificate in the ssl subdirectory. One can replace this certificate and key with a real ceritficate to avoid browser pop-up windows warning about the self-signed certificate. The default for this option is 0 .
Giuseppe Cucinotta wrote: |
We obtained a certificate from let's encrypt in order to replace the self signed certificate provided with elog. We copied the new certificates replacing the older server.crt
The problem is that when restarted elog raises an error related to the fact it is looking for server.crt and it doesn't find it anymore.
I searched in elog config file in order to find a way to indicate the new certificate but I didn't find how to manage this issue.
Any suggestion?
|
|
69632
|
Wed Jan 25 22:22:07 2023 |
| Giuseppe Cucinotta | giuseppe.cucinotta@unifi.it | Question | Linux | 3.1.3 | Re: ssl certificate | Hi Laurent,
thanks very much! Probably I've copied the certificate in the wrong directory. I'll try ASAP
Laurent Jean-Rigaud wrote: |
Hi Giuseppe,
The new certificate files should be copy under ssl folder (/usr/local/elog/ssl or /usr/share/elog/ssl by example, closed to templates and script directories) in place of the embedded (autosigned) certificate files enclosed with ELOG source.
It seems that there is no parameter to set a custom path.
SSL = <0 | 1>
Turn on Secure Socket Layer transport. If SSL is on, one can connect via https://... to the elogd daemon. If the URL = directive is used, make sure to use https://... instead of http://... there. The ELOG distribution contains a simple self-signed certificate in the ssl subdirectory. One can replace this certificate and key with a real ceritficate to avoid browser pop-up windows warning about the self-signed certificate. The default for this option is 0 .
Giuseppe Cucinotta wrote: |
We obtained a certificate from let's encrypt in order to replace the self signed certificate provided with elog. We copied the new certificates replacing the older server.crt
The problem is that when restarted elog raises an error related to the fact it is looking for server.crt and it doesn't find it anymore.
I searched in elog config file in order to find a way to indicate the new certificate but I didn't find how to manage this issue.
Any suggestion?
|
|
|
69633
|
Fri Jan 27 22:25:18 2023 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Request | All | - | Re: Wikipedia Article deleted | It appears to me that this is a really stupid problem: the article provides many links to sources, but they are just links, not "references". That does not count, since links could be something else than references.
I'll try to edit it and transform the list of external links into references to verify the text. Lets hope that this will suffice.
Okay: found three articles about applications of ELOG and put them under references. I took the liberty to submit the draft: it shows that they expect some month delay for a review. I have no idea if that was what they want, but it is worth a try.
Edmund Blomley wrote: |
If I understand it correctly I think it has to be submitted for review with the blue button on that page, just not sure if that should come from your side or someone else
Stefan Ritt wrote: |
I added some more references, that's about all I can do. Not sure if that is enough.
Stefan
Edmund Blomley wrote: |
It was now moved to the Draft space (which I did not even now existed so far): https://en.wikipedia.org/wiki/Draft:ELOG
Sebastian Schenk wrote: |
I have requested an undeletion of the article. The article was deleted "PROD", which means that someone tagged it. And if noone removes the tag, it could be deleted.
I could revive the article. So in the future, One should have an eye on it and maybe update the current version of the software.
If there iy an paper on the elog, maybe it could be cited for more creditability.
Andreas Luedeke wrote: |
It looks to me like only an author of an article can contradict a deletion. I did not find a single method to even comment on the deletion.
I am not an Wikipedia expert, can anyone suggest on how to push for the article to be restored? Or do we just write it again, until people stop deleting it?
Stefan Ritt wrote: |
I agree. I ahead ;-) I think it is not a good idea if the ELOG author pushes on that, but better someone else.
Best,
Stefan
Sebastian Schenk wrote: |
Hello,
I noticed the wikipedia article of the ELOG got deleted in November 2021.
With the reason: "Poorly sourced article, and I was not able to find good sources myself."
I could access the old article through web.archive.org, but for the project it would be good, if the article got revived.
|
|
|
|
|
|
|
|
|