| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68720
|
Tue Jan 16 10:13:00 2018 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 3.1.2 | Re: Is there a python3 api to generate logbook entries from python? | Have a look here: https://github.com/paulscherrerinstitute/py_elog
I haven't tried it myself, but it should allow you to add, reply, edit, delete elog entries from python (>= 3.5) via the http elog interface. It's an anaconda package.
| markus wrote: |
|
Dear elog community,
I wonder whether there is a python3 api or lib to generate and append entries (and attachments) to the logbook using scripts.
However, so far I did not find anything...
At the moment I am thinking about wrapping the "elog" command line tool.
Is there something usable already out there?
Thanks and regards
Markus
|
|
|
68730
|
Thu Feb 1 10:14:55 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 2.9.2->3.1.3 | Re: v3.1.3 does not work with logbooks from v2.9.2? | Hi Yves,
just my two pence, maybe they help you to figure out what's going on:
versions 2.* had all entries of one logbook in one directory. Version 3.* create a subdirectory for each year. This had been added for me: if you use AFS for logbook storage, then you have a limit on how many files you can put into a single directory.
So the first time you start elogd 3.* with data from an elogd 2.* it should move all your logbook entries into sub-directories for each year. If that would have happened, you would not be able to use these logbook directories with the 2.9.2 version.
Maybe your logbook client is not allowed to create sub-directories? Although I would guess that it then would just throw an error message and stop.
Cheers, Andreas
| Yves wrote: |
|
I have just upgraded elog from 2.9.2 -> 3.1.3.
3.1.3 runs fine with new logbooks. However, when trying to run 3.1.3 with my logbooks created with 2.9.2 things stop working.
Here is the command I run for testing [attachment 1]: first of all it takes a very long time (~ 10 minutes) for it to index the logbooks. When finished indexing I try it out in a web browser - it takes infinite time to load: no error message appears but also no logbook. After an hour or so elogd crashes without an error message.
When running 2.9.2 on the same machine, all runs wel (attachment 2)
cfd file: (I only left in one logbook - they are all configured the same)
[global]
port = 18080
Logging level = 3
Max content length = 500000000
Date format = %A, %d %B %Y
[Logrun - Amptek]
Theme = default
Comment = Logrun Amptec
Reverse sort = 0
Quick filter = Date, Type
Any ideas on how to solve this?
|
|
|
68739
|
Wed Feb 7 15:28:47 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Linux | V3.1.2-bd75964 | Re: Entries disappear after editing + UTF16 problem | Hi Stefan,
I think there is a misunderstanding: there is an ELOG commit with the GIT ID bd75964.
It is from Sep. 2016, so: Peter, you should download a newer version.
Cheers
Andreas
https://bitbucket.org/ritt/elog/commits/all?search=bd75964
| Stefan Ritt wrote: |
|
Tell me your current seven digit number and I can check if your version is too old.
| Peter K wrote: |
|
yes, that is exactly where I got this V3.1.2-bd75964 version!
Do you recommend to download it again from your site and compile?
| Stefan Ritt wrote: |
|
The -bd... number must be from the .apk package, which I don't have control over. You have to check the elog git hash code. You see it at the bottom of each elog web page. For this forum server, it's ELOG V3.1.2-7933898 with 7 digit number at the end.
| Peter K wrote: |
|
We installed our elog from .apk in November 2017.
Version V3.1.2-bd75964
I suppose it already contains List drafts feature.
| Stefan Ritt wrote: |
|
You might have to update to the current elog version. This feature was implemented in Dec. 2016.
Stefan
| Peter K wrote: |
|
Dear Stefan,
Thanks for quick reply.
I checked List drafts = 1 in config file - it does not show drafts in the list in my case.
Can it be blocked by any other option?
I have these options enabled:
Use Lock = 1
Save drafts = 1
List drafts = 1
Peter.
| Stefan Ritt wrote: |
|
The message is not lost, but becomes a "draft". This works similar in most email systems. When you edit an email and son't send it, it stays in your "draft" email folder and does not show up in your "sent" folder. Same here. You are suppost to "submit" you entry, the "save" is just a temporary safety backup. If you do not submit (if you press BACK or your browser crashes), the entry is not submitted to the system, but stays around as a draft. If you create a new message, the system asks you to edit and finish your draft, so that it does not get lost. So always hit "submit" if you are finished editing a message, not just "save".
If you want to see the draft message, they are rendered in red in the normal message list if you have
List drafts = 1
in your config file. No ide where your cluttering comes from.
Stefan
| Peter K wrote: |
|
I found a sequence which hides the message from the list.
In addition this sequence corrupts UTF encoding of the text.
- create new message
- submit it
- Edit this message again
- click SAVE and then exit the editor (click Logbook name in the header or BACK in the browser)
- message disappeared from the list!
- by clicking NEW message I found my lost one in the drafts, but all text was corrupted.
I've made small GIF presentation on this issue (attached, open in new window), may be this helps.
|
|
|
|
|
|
|
|
|
|
68774
|
Tue Apr 3 10:19:07 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 3.1.2 | Re: Create past Elog entry. | David answered the question already.
I would distinguish if this is a once-in-a-year event, where you are willing to edit the logfiles as an administrator to fix it -
or if it happens more weekly, and you want to enable the users to fix it themself.
If it happens once a year and you don't mind to do it yourself: write a little self "how-to" and do it like David suggested.
If it happens more frequent and you prefer your users to fix it themself: introduce a "when" attribute as described in elog:67712
Cheers, Andreas
PS: Changing entry IDs $@MID@$ is only for people who know exactly what they are doing. You need to change all references to the IDs as well (Reply to: attributes) and all cross references (like the one elog:67712).
| Michael Hibbard wrote: |
|
Hello, Sorry if this has been addressed elsewhere, but I could not find info.
I am wanting to submit a new elog entry (that should have been) for a past date, to predate log entrys currently in my system.
I assume I must manually create a new .log file. What ID# should I assign to this entry? Should I sub-increment (i.e 33.1)? I presume the correct think to to would be to automate ID# increments in all sucessive logs with a script (python).
Please advise.
Thank you,
-Michael Hibbard
|
|
|
68787
|
Mon Apr 16 17:27:35 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 3.1.3 | Re: problem with chkeditor | Yes, I can help with that: you've tried to put the picture into the text body. Try to make it a normal attachment, that'll work always.
| Andrea Mazzolari wrote: |
|
If i try to upload an image here, i got the error "Image Source URL Is Missing"...
can you help me further ?
Best regards,
Andrea
| Stefan Ritt wrote: |
|
Can you post a picture here?
| Andrea Mazzolari wrote: |
|
Hi All,
I just installed elog latest version. I can see that my chkeditor (HTML encoding) is pretty simplified with respect to the version i can see there. Why this ? For example, it does not offer the possibility to upload images.
Could you please help me ?
Thank you
Andrea
|
|
|
|
|
68791
|
Wed Apr 18 13:43:36 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 3.1.1 | Re: Email Config |
SMTP host = ...
MUST be set in the [global] section of your configuration - it will likely not work when you try to set it for a specific logbook.
I don't see how ELOG can send an automatic email after a date expired.
But you could set-up a script that checks for expired entries, and if there are any it'll send out an email. You can use any http connection to do the query using the find command (e.g. curl).
To get the right URL, just make the find from the web form and copy the URL that gives you the desired result.
Hope that helps.
Andreas
| Stefan Werler wrote: |
|
Hi,
I´m new in ELOG,
Can u explain me how i config the Mailing?
in my Configuration i do have not the ability to set an Email Host/Server. or i didn´t find it....
I have to use ELOG as ticket system, is it possible to send an email automatically after expiration of a period?
|
|
|
68793
|
Fri May 4 16:05:32 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Linux | 2.9.2 | Re: Elog ID entry bug at >99999 entries | I am not sure I understand your bug report.
I can easily create IDs greater than 100'000 (see attached picture), but that is not your problem, or is it?
Cheers, Andreas
| Joseph McKenna wrote: |
|
We have a possible bug with elog that the ID for an elog entry at over 99,999 entires reads as 10,000...
68792/1 Illistrates the problem, we use this ID often to cross reference from out datalog...
Is this a know bug we can find a fix for? We are using: elogd 2.9.2 built Jul 14 2015, 18:58:06 revision
|
|
|
68795
|
Sat May 5 20:55:23 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Linux | 2.9.2 | Re: Elog ID entry bug at >99999 entries | Well, in my example the ID link worked just fine.
There could be a string length limitation, but it could be as well the way you are creating the ID that is the source of the problem: I would need the part of your elogd.cfg that defines how you format your ID in order to try to reproduce your problem.
Cheers, Andreas
| Chris Rasmussen wrote: |
|
Hi Andreas, I'm working on the same experiment as Joseph who submitted the bug report.
You are right, IDs greater than 10^5 are created no problem. The issue is with the internal elog link, in this case of the form elog:SequencerEvents/XXXXX The link generated uses only the first 5 digits of the message ID, and therefore links to the wrong message. In the two attachments you can see our sequencer event number 100098, first displaying the message where all of the ID is displayed and secondly in "full" view of the elog front page. Here, the "ID" column contains a link with the string: elog:SequencerEvents/10009. Our problem is that we often use this string to paste into other elogs and generate a link to the sequencer event message. However, since the string uses too few digits, we end up with a link to the wrong message
| Andreas Luedeke wrote: |
|
I am not sure I understand your bug report.
I can easily create IDs greater than 100'000 (see attached picture), but that is not your problem, or is it?
Cheers, Andreas
| Joseph McKenna wrote: |
|
We have a possible bug with elog that the ID for an elog entry at over 99,999 entires reads as 10,000...
68792/1 Illistrates the problem, we use this ID often to cross reference from out datalog...
Is this a know bug we can find a fix for? We are using: elogd 2.9.2 built Jul 14 2015, 18:58:06 revision
|
|
|
|
|