ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68729
|
Thu Feb 1 03:12:03 2018 |
| Yves | vanhaarlemyves@gmail.com | Question | Windows | 2.9.2->3.1.3 | v3.1.3 does not work with logbooks from v2.9.2? | 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? |
Attachment 1: test1.png
|
|
Attachment 2: test2.png
|
|
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?
|
|
68733
|
Fri Feb 2 00:02:54 2018 |
| Yves | vanhaarlemyves@gmail.com | Question | Windows | 2.9.2->3.1.3 | Re: v3.1.3 does not work with logbooks from v2.9.2? - solved | Hi Andreas,
Thanks - you pointed me in the right direction. It appears that my logbooks were a combination of the two versions. I had all the year-directories (version 3) but also all the entry files in the main logbook directory. Seems version 2 does not care but version 3 does not like it. After carefully checking and removing all the logbook files in the main directory version 3 now works.
Cheers,
Yves
Andreas Luedeke wrote: |
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?
|
|
|
68757
|
Tue Mar 6 16:59:29 2018 |
| Piotr Zolnierczuk | zolnie@yahoo.com | Question | Linux | 3.1.3 | how to insert images inline | Hi,
I recently upgraded elog from 2.7 to 3.1 and have a hard time to insert images inline. The attachements work just fine. I am certain it is something silly, but I cannot figure it out.
- In edit mode, I click the image icon
- A pop-up "Image Propertied" shows with two tabs "Image Info" and "Upload" (selected)
- Click on Browse button and select an image
- Now
- if I click OK, I get an error "Image source URL is missing".
- if I go to "Image Info" tab - what URL am I supposed to enter, 68757/<1> ?
I found an old thread elog:68410 (from 2016) but could not find a solution that would work for me. Where does "Preview attachments" option should be inserted? In the global section?
Hopefully there's a simple explanation for this
Piotr |
68758
|
Tue Mar 6 17:28:46 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.3 | Re: how to insert images inline | Before you click OK on your point 4, click on "Send to Server".
Stefan
Piotr Zolnierczuk wrote: |
Hi,
I recently upgraded elog from 2.7 to 3.1 and have a hard time to insert images inline. The attachements work just fine. I am certain it is something silly, but I cannot figure it out.
- In edit mode, I click the image icon
- A pop-up "Image Propertied" shows with two tabs "Image Info" and "Upload" (selected)
- Click on Browse button and select an image
- Now
- if I click OK, I get an error "Image source URL is missing".
- if I go to "Image Info" tab - what URL am I supposed to enter, 68757/<1> ?
I found an old thread elog:68410 (from 2016) but could not find a solution that would work for me. Where does "Preview attachments" option should be inserted? In the global section?
Hopefully there's a simple explanation for this
Piotr
|
|
68759
|
Tue Mar 6 17:49:49 2018 |
| Piotr Zolnierczuk | zolnie@yahoo.com | Question | Linux | 3.1.3 | Re: how to insert images inline | I did just that. The image was properly send to the server (it appears in the attachement list). However clicking OK still produces "Image source URL is missing".
What is the URL that refers to an attachment? I've tried 68759/<1> and 68759/1 and even elog:1234/<1> (where 1234).
Stefan Ritt wrote: |
Before you click OK on your point 4, click on "Send to Server".
Stefan
Piotr Zolnierczuk wrote: |
Hi,
I recently upgraded elog from 2.7 to 3.1 and have a hard time to insert images inline. The attachements work just fine. I am certain it is something silly, but I cannot figure it out.
- In edit mode, I click the image icon
- A pop-up "Image Propertied" shows with two tabs "Image Info" and "Upload" (selected)
- Click on Browse button and select an image
- Now
- if I click OK, I get an error "Image source URL is missing".
- if I go to "Image Info" tab - what URL am I supposed to enter, 68757/<1> ?
I found an old thread elog:68410 (from 2016) but could not find a solution that would work for me. Where does "Preview attachments" option should be inserted? In the global section?
Hopefully there's a simple explanation for this
Piotr
|
|
|
68760
|
Tue Mar 6 18:01:30 2018 |
| Piotr Zolnierczuk | zolnie@yahoo.com | Question | Linux | 3.1.3 | Re: how to insert images inline | Got it to work. Removed "Preview attachments = 1" from the global section.
Thanks for your help.
Piotr
Piotr Zolnierczuk wrote: |
I did just that. The image was properly send to the server (it appears in the attachement list). However clicking OK still produces "Image source URL is missing".
What is the URL that refers to an attachment? I've tried 68759/<1> and 68759/1 and even elog:1234/<1> (where 1234).
Stefan Ritt wrote: |
Before you click OK on your point 4, click on "Send to Server".
Stefan
Piotr Zolnierczuk wrote: |
Hi,
I recently upgraded elog from 2.7 to 3.1 and have a hard time to insert images inline. The attachements work just fine. I am certain it is something silly, but I cannot figure it out.
- In edit mode, I click the image icon
- A pop-up "Image Propertied" shows with two tabs "Image Info" and "Upload" (selected)
- Click on Browse button and select an image
- Now
- if I click OK, I get an error "Image source URL is missing".
- if I go to "Image Info" tab - what URL am I supposed to enter, 68757/<1> ?
I found an old thread elog:68410 (from 2016) but could not find a solution that would work for me. Where does "Preview attachments" option should be inserted? In the global section?
Hopefully there's a simple explanation for this
Piotr
|
|
|
|
68772
|
Mon Apr 2 23:31:51 2018 |
| Michael Hibbard | michael.hibbard@cern.ch | Question | Windows | 3.1.2 | Create past Elog entry. | 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 thing to to would be to automate ID# increments in all sucessive logs with a script (python).
Please advise.
Thank you,
-Michael Hibbard |
|