Reverse sort by Attribue, but it's only showing the last 6 entries by default., posted by Anthony on Sun Aug 9 03:41:05 2020
|
|
Hi,
I'm trying to use the Sort Attributes option to sort all entries by a user specified date. The issue I'm running into, is that although I can get it to work, it seems to only display the last 6 entries that I'm sorting by. If I click "All" to show all the entries, it's sorted perfectly. I'm using:
Sort Attributes = Due Date
Reverse sort = 0
Is there something I'm missing to get this working. Reading through the manual nothing jumped out at me.
|
Re: Reverse sort by Attribue, but it's only showing the last 6 entries by default., posted by Anthony on Mon Aug 10 09:01:24 2020
|
Thank you, Andreas! Not sure why I kept overlooking it in the manual. As for the number of entries when I sort, I'm not sure. I'll set it up to display a larger number and see what happens.
| Andreas Luedeke wrote: |
|
It is described in the manual at https://elog.psi.ch/elog/config.html#general
Entries per page = <number>
Funnily the default is "20". I have no idea why you see 6 entries.
| Anthony wrote: |
|
Hi,
I'm trying to use the Sort Attributes option to sort all entries by a user specified date. The issue I'm running into, is that although I can get it to work, it seems to only display the last 6 entries that I'm sorting by. If I click "All" to show all the entries, it's sorted perfectly. I'm using:
Sort Attributes = Due Date
Reverse sort = 0
Is there something I'm missing to get this working. Reading through the manual nothing jumped out at me.
|
|
|
Shared logbook and elog.cfg file across multiple installations, posted by Anthony on Mon Nov 15 15:41:04 2021
|
Hi,
I'm wondering if it's possible to have a shared logbook and elog.cfg between multiple instances of elog. Ideally, I'd like to have my logbooks folder and elog.cfg hosted on a nextcloud instance while running the elog service locally. I've tried this using symlinks and shortcuts on windows with no luck. I was able to install elog into my mounted nextcloud folder, but this isn't ideal as I would like this to work from multiple computers.
Any ideas or thoughts on how I can do this (if I can actually do this)? |
|
Re: Shared logbook and elog.cfg file across multiple installations, posted by Anthony on Tue Nov 16 13:05:05 2021
|
Thank you Sebastian!
I admittidely haven't looked through the page in a while, so I completely missed this feature. This should solve the problem, although in a slightly different implementation than what I was trying for.
| Sebastian Schenk wrote: |
|
Hi Anthony,
the elog has a mirroring function, which synchornizes config and logs between multiple instances.
See the bottom section of https://elog.psi.ch/elog/config.html
Best wishes,
Sebastian
| Anthony wrote: |
|
Hi,
I'm wondering if it's possible to have a shared logbook and elog.cfg between multiple instances of elog. Ideally, I'd like to have my logbooks folder and elog.cfg hosted on a nextcloud instance while running the elog service locally. I've tried this using symlinks and shortcuts on windows with no luck. I was able to install elog into my mounted nextcloud folder, but this isn't ideal as I would like this to work from multiple computers.
Any ideas or thoughts on how I can do this (if I can actually do this)?
|
|
|
|
compiling elog 2.6.1 on solaris platform, posted by Angus Au on Thu Feb 2 03:19:44 2006
|
I came across problem in compiling elog 2.6.1 on solaris platform.
The messages "
# make
gcc -o elog src/elog.c -lutil -lsocket -lnsl
ld: fatal: library -lutil: not found
ld: fatal: File processing errors. No output written to elog
collect2: ld returned 1 exit status
*** Error code 1
make: Fatal error: Command failed for target `elog'
It seems to me that library libutil does not exist on solaris platform.
Is there any fix ? I can compile elog 2.6.0 successfully on solaris. |
Problem with auto-increment attribute, posted by Andy on Tue May 24 20:32:08 2005
|
I have a very strange problem with auto-increment attribute. Here is a part of my configuration:
Attributes = Access ID, Harvest Date, Access, Species, PI, Submission date, Stain, Comments
Preset Access ID = MI-05-%03d
Type Harvest date = date
Type Submission date = date
I tried to add new entry, and it's Access ID is MI-05-001. But when I'm adding another entries,
there Access ID is MI-05-006
I found only one mention of using increment in documentation.
What I'm doing wrong? |
|
HTTP headers should be parsed case insensitive, posted by André on Mon Jul 22 16:17:55 2024
|
I'm trying to run elog behind haproxy, but get the error "Invalid Content-Length in header" on posting.
As stated in the manual, haproxy rewrites all headers to lower case.
elogd parses the content-length header case sensitive which is against the HTTP RFC. This might also apply to other headers that get parsed.
For now I'm using the workaround from the manual:
global
h1-case-adjust content-length Content-Length
h1-case-adjust content-type Content-Type
backend elog
option h1-case-adjust-bogus-server
server elog 127.0.0.1:8080
But as the manual states, this should not be used as a permanent solution. |
|
Re: Invalid Content-Length in header when running behind a load balancer, posted by André on Mon Jul 22 16:30:04 2024
|
I have the same problem. I found a temporary solution: https://elog.psi.ch/elogs/Forum/69807
| Tamas Gal wrote: |
|
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
|
|
|
|