Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 47 of 238  Not logged in ELOG logo
icon5.gif   Server dropping SSL connection while uploading large files, posted by Erkcan Ozcan on Sat Jun 10 07:05:24 2017 

Hi,

I am having trouble with uploading large (>0.5MB) files to elog. We click on upload and in a couple of seconds, the webbrowser complains that the server has dropped the connection.

Following the suggestions I found on these forums (https://midas.psi.ch/elogs/Forum/66753), I increased the timeout.tv_sec to 30 in three locations in elogd.c, but this did not help.

The problem is present in my old elog installation (from ~2 years ago), as well as the latest git snapshot from bitbucket that I cloned on June 10, 2017.

PS: Upload seems to work for non-secure configuration. It still takes a while to load, but it completes. However we prefer to use secure connections ( SSL = 1 ).
PS: Using nmap I looked at the latency to the relevant port, it can be as high as 0.5sec, but most often it is shorter.

Cheers,
e.

    icon2.gif   Re: Server dropping SSL connection while uploading large files, posted by Erkcan Ozcan on Wed Jun 28 19:37:10 2017 

Hi,

Could someone at least suggest how I could debug this problem myself? If I know where to start, perhaps I can fix it myself and contribute to the software.

Best,

e.

Erkcan Ozcan wrote:

Hi,

I am having trouble with uploading large (>0.5MB) files to elog. We click on upload and in a couple of seconds, the webbrowser complains that the server has dropped the connection.

Following the suggestions I found on these forums (https://midas.psi.ch/elogs/Forum/66753), I increased the timeout.tv_sec to 30 in three locations in elogd.c, but this did not help.

The problem is present in my old elog installation (from ~2 years ago), as well as the latest git snapshot from bitbucket that I cloned on June 10, 2017.

PS: Upload seems to work for non-secure configuration. It still takes a while to load, but it completes. However we prefer to use secure connections ( SSL = 1 ).
PS: Using nmap I looked at the latency to the relevant port, it can be as high as 0.5sec, but most often it is shorter.

Cheers,
e.

 

       icon2.gif   Re: Server dropping SSL connection while uploading large files, posted by Andreas Warburton on Wed Jun 28 22:20:38 2017 

Hi Erkcan,

I observed similar behaviours when attempting to do SSL uploads and mirroring over a WAN (see some of my recent posts).  Having not received any responses/help, and no time to try debugging the source myself, I've changed the way I use ELOG such that my attachment uploads are always local (on my Mac laptop, where I do most of my ELOGging) and I have switched off the mirroring, choosing instead to do my own rsync backup to a central linux server on which I have running a read-only ELOG executable.  This configuration is both relatively secure and stable, and it matches my use case well.  More generally, however, it is unfortunate that this SSL and mirroring functionality isn't truly there for all users, even though the documentation touts it to be so.

Best regards,

Andreas W.

Erkcan Ozcan wrote:

Hi,

Could someone at least suggest how I could debug this problem myself? If I know where to start, perhaps I can fix it myself and contribute to the software.

Best,

e.

Erkcan Ozcan wrote:

Hi,

I am having trouble with uploading large (>0.5MB) files to elog. We click on upload and in a couple of seconds, the webbrowser complains that the server has dropped the connection.

Following the suggestions I found on these forums (https://midas.psi.ch/elogs/Forum/66753), I increased the timeout.tv_sec to 30 in three locations in elogd.c, but this did not help.

The problem is present in my old elog installation (from ~2 years ago), as well as the latest git snapshot from bitbucket that I cloned on June 10, 2017.

PS: Upload seems to work for non-secure configuration. It still takes a while to load, but it completes. However we prefer to use secure connections ( SSL = 1 ).
PS: Using nmap I looked at the latency to the relevant port, it can be as high as 0.5sec, but most often it is shorter.

Cheers,
e.

 

 

 
       icon2.gif   Re: Server dropping SSL connection while uploading large files, posted by Stefan Ritt on Thu Jun 29 08:36:03 2017 

One possibility is to run elog in non-SSL mode and put an Apache server in front of it. The Apache server can then do the SSL communication, and forward all requests to elog in plain text (non-SSL). This has been proven to work with large attachments, actually that's the way I use it.

I didn't find time to debug the SSL problem. If anybody is interested in doing so, the relevant code is in function server_loop() around line 30015 (SSL_read()).

Stefan

Erkcan Ozcan wrote:

Hi,

Could someone at least suggest how I could debug this problem myself? If I know where to start, perhaps I can fix it myself and contribute to the software.

Best,

e.

Erkcan Ozcan wrote:

Hi,

I am having trouble with uploading large (>0.5MB) files to elog. We click on upload and in a couple of seconds, the webbrowser complains that the server has dropped the connection.

Following the suggestions I found on these forums (https://midas.psi.ch/elogs/Forum/66753), I increased the timeout.tv_sec to 30 in three locations in elogd.c, but this did not help.

The problem is present in my old elog installation (from ~2 years ago), as well as the latest git snapshot from bitbucket that I cloned on June 10, 2017.

PS: Upload seems to work for non-secure configuration. It still takes a while to load, but it completes. However we prefer to use secure connections ( SSL = 1 ).
PS: Using nmap I looked at the latency to the relevant port, it can be as high as 0.5sec, but most often it is shorter.

Cheers,
e.

 

 

icon13.gif   my elogd crashes when editing the configuration, posted by Niklas Hoglund on Tue Jun 20 14:32:29 2017 WindowsCrashFiles.zip
Hi, 
my elogd crashes sometimes when I click on the "Change config" button. What info should I collect more than below/attached?

In windows EventViewer I see this printouts:

###
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Windows Error Reporting" /> 
  <EventID Qualifiers="0">1001</EventID> 
  <Level>4</Level> 
  <Task>0</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2017-06-20T12:25:30.000000000Z" /> 
  <EventRecordID>28059</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>NIKLAS</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>108889037262</Data> 
  <Data>1</Data> 
  <Data>APPCRASH</Data> 
  <Data>Not available</Data> 
  <Data>0</Data> 
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>c0000005</Data> 
  <Data>00064eea</Data> 
  <Data /> 
  <Data /> 
  <Data>C:\Users\hognik\AppData\Local\Temp\WER9155.tmp.WERInternalMetadata.xml</Data> 
 
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_elogd.exe_9ef84f861b91d5afaf68864978184ca611e7a22a_d4f2c951_08bd38b0</Data>

  <Data /> 
  <Data>0</Data> 
  <Data>7232f1e4-55b3-11e7-826a-e4b3181bd6c1</Data> 
  <Data>0</Data> 
  <Data>94c2d6a18797708666faf33a7273855a</Data> 
  </EventData>
  </Event>
###

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2017-06-20T12:24:47.000000000Z" /> 
  <EventRecordID>28058</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>NIKLAS</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>c0000005</Data> 
  <Data>00064eea</Data> 
  <Data>1568</Data> 
  <Data>01d2e9c028b88983</Data> 
  <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data> 
  <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data> 
  <Data>7232f1e4-55b3-11e7-826a-e4b3181bd6c1</Data> 
  <Data /> 
  <Data /> 
  </EventData>
  </Event>

###

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Windows Error Reporting" /> 
  <EventID Qualifiers="0">1001</EventID> 
  <Level>4</Level> 
  <Task>0</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2017-06-20T12:24:07.000000000Z" /> 
  <EventRecordID>28057</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>NIKLAS</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>108889037262</Data> 
  <Data>1</Data> 
  <Data>APPCRASH</Data> 
  <Data>Not available</Data> 
  <Data>0</Data> 
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>c0000005</Data> 
  <Data>00064eea</Data> 
  <Data /> 
  <Data /> 
  <Data>C:\Users\hognik\AppData\Local\Temp\WERBE94.tmp.WERInternalMetadata.xml
C:\Users\hognik\AppData\Local\Temp\WERCA4D.tmp.appcompat.txt triagedump.dmp
C:\Users\hognik\AppData\Local\Temp\WERCB77.tmp.WERDataCollectionFailure.txt</Data> 
 
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_elogd.exe_9ef84f861b91d5afaf68864978184ca611e7a22a_d4f2c951_0a4ff4e6</Data>

  <Data /> 
  <Data>0</Data> 
  <Data>5206c994-55b3-11e7-826a-e4b3181bd6c1</Data> 
  <Data>4104</Data> 
  <Data>94c2d6a18797708666faf33a7273855a</Data> 
  </EventData>
  </Event>

###

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2017-06-20T12:23:53.000000000Z" /> 
  <EventRecordID>28056</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>NIKLAS</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>c0000005</Data> 
  <Data>00064eea</Data> 
  <Data>2338</Data> 
  <Data>01d2e9baf6174f0f</Data> 
  <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data> 
  <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data> 
  <Data>5206c994-55b3-11e7-826a-e4b3181bd6c1</Data> 
  <Data /> 
  <Data /> 
  </EventData>
  </Event>
###
icon5.gif   Is it possible to generate a table of contents based on h1/h2/h3 HTML tags?, posted by Niklas Hoglund on Mon Jun 19 07:48:49 2017 

Is it possible to generate a table of contents based on h1/h2/h3 HTML tags?

Example:

toc()

< h1>test
< h2>test1
< h1>test2
< h2>test3
< h1>test4
< h2>test5

Results in:

1. test
1.1 test1
2. test2
2.1 test3
3. test4
3.1 test5

...the text...
    icon2.gif   Re: Is it possible to generate a table of contents based on h1/h2/h3 HTML tags?, posted by Stefan Ritt on Mon Jun 19 08:33:07 2017 

This is not possible.

Stefan

Niklas Hoglund wrote:

Is it possible to generate a table of contents based on h1/h2/h3 HTML tags?

Example:

toc()

< h1>test
< h2>test1
< h1>test2
< h2>test3
< h1>test4
< h2>test5

Results in:

1. test
1.1 test1
2. test2
2.1 test3
3. test4
3.1 test5

...the text...

 

icon1.gif   Use X-Forwarded-User as preset in author field, posted by Stefano Lacaprara on Tue May 16 10:21:18 2017 
Hi,
  I have an elog server which uses apache/ldap for authentication.
I would like to have the username used for ldap to be set automatically as author field in the elog.

I'm using: 
Authentication = Webserver
and I do set the env-variable X-Forwarded-User correctly to the ldap username

GET /test/?cmd=New HTTP/1.1
Host: localhost:8080
Authorization: Basic bGFjYXByYXI6TWEwMiSyYnVt
...
Cookie: elmode=Summary; sid=D7DE678B7CAA1D10; ufnm=lacaprar; urem=0
...
X-Forwarded-User: lacaprar

How can I preset author to X-Forwarded-User?
Preset Author = $??
I've tried $short_name/$long_name but I got Anonymous.
I understand that it is so because these are meant to be filled when password authentication is used: any way to use some other variable with the Webserver auth?

thanks in advance,
  Stefano
    icon2.gif   Re: Use X-Forwarded-User as preset in author field, posted by Christof Hanke on Wed May 17 08:42:17 2017 
> Hi,
>   I have an elog server which uses apache/ldap for authentication.
> I would like to have the username used for ldap to be set automatically as author field in the elog.
> 
> I'm using: 
> Authentication = Webserver
> and I do set the env-variable X-Forwarded-User correctly to the ldap username
> 
> GET /test/?cmd=New HTTP/1.1
> Host: localhost:8080
> Authorization: Basic bGFjYXByYXI6TWEwMiSyYnVt
> ...
> Cookie: elmode=Summary; sid=D7DE678B7CAA1D10; ufnm=lacaprar; urem=0
> ...
> X-Forwarded-User: lacaprar
> 
> How can I preset author to X-Forwarded-User?
> Preset Author = $??
> I've tried $short_name/$long_name but I got Anonymous.
> I understand that it is so because these are meant to be filled when password authentication is used: any way to use some other variable with the Webserver auth?
> 
> thanks in advance,
>   Stefano


Hi,

I use an older version of elog, but
 
Preset Author = $short_name <$long_name>

works for me.

One thing to note is that I also have :
Self register = 1

So at first login, the user has to type in his name and email adress,
maybe that's why you got "Anonymous". (Otherwise the variable $shortname etc. are not set.)

HTH,

Christof
       icon2.gif   Re: Use X-Forwarded-User as preset in author field, posted by Stefano Lacaprara on Thu May 18 09:39:16 2017 
> I use an older version of elog, but
>  
> Preset Author = $short_name <$long_name>
> 
> works for me.
> 
> One thing to note is that I also have :
> Self register = 1
> 
> So at first login, the user has to type in his name and email adress,
> maybe that's why you got "Anonymous". (Otherwise the variable $shortname etc. are not set.)
> 
> HTH,
> 
> Christof

Many thanks for your answer.
however it seems that your solution requires to have a eLog "password" authentication, which I'd like to avoid since I'd like to use only webserver one.

best,
  Stefano
          icon2.gif   Re: Use X-Forwarded-User as preset in author field, posted by Christof Hanke on Thu May 18 10:37:16 2017 
> > I use an older version of elog, but
> >  
> > Preset Author = $short_name <$long_name>
> > 
> > works for me.
> > 
> > One thing to note is that I also have :
> > Self register = 1
> > 
> > So at first login, the user has to type in his name and email adress,
> > maybe that's why you got "Anonymous". (Otherwise the variable $shortname etc. are not set.)
> > 
> > HTH,
> > 
> > Christof
> 
> Many thanks for your answer.
> however it seems that your solution requires to have a eLog "password" authentication, which I'd like to avoid since I'd like to use only webserver one.
> 
No, I'm also using the webserver authentication.
May I ask why you think "password" auth is required ?

The elog has an internal userdatabase with longname, shortname, email etc.
Even if you are authenticated via the webserver, you also have to have an entry in that userdatabase.
This entry has to be created by the user who is allowed to get into elog by the webserver. 
Thus, the Self register option.

Bests,

Christof
             icon2.gif   Re: Use X-Forwarded-User as preset in author field, posted by Christof Hanke on Thu May 18 10:51:05 2017 
> > > I use an older version of elog, but
> > >  
> > > Preset Author = $short_name <$long_name>
> > > 
> > > works for me.
> > > 
> > > One thing to note is that I also have :
> > > Self register = 1
> > > 
> > > So at first login, the user has to type in his name and email adress,
> > > maybe that's why you got "Anonymous". (Otherwise the variable $shortname etc. are not set.)
> > > 
> > > HTH,
> > > 
> > > Christof
> > 
> > Many thanks for your answer.
> > however it seems that your solution requires to have a eLog "password" authentication, which I'd like to avoid since I'd like to use only webserver one.
> > 
> No, I'm also using the webserver authentication.
> May I ask why you think "password" auth is required ?
> 
> The elog has an internal userdatabase with longname, shortname, email etc.
> Even if you are authenticated via the webserver, you also have to have an entry in that userdatabase.
> This entry has to be created by the user who is allowed to get into elog by the webserver. 
> Thus, the Self register option.
> 
> Bests,
> 
> Christof

Sorry, I just double-checked, this userdatabase, I was talking about is the Password-file...

Please try the following snippet :

allow password change = 0
Authentication = Webserver, File
Preset Author = $short_name <$long_name>
Locked Attributes = Author
Password file = PASSWD.file

Christof
                icon2.gif   [solved] Re: Use X-Forwarded-User as preset in author field, posted by Stefano Lacaprara on Thu May 18 16:55:42 2017 
> 
> Sorry, I just double-checked, this userdatabase, I was talking about is the Password-file...
> 
> Please try the following snippet :
> 
> allow password change = 0
> Authentication = Webserver, File
> Preset Author = $short_name <$long_name>
> Locked Attributes = Author
> Password file = PASSWD.file
> 
> Christof

Many thanks, that is what I was looking for.

best,
  Stefano
icon5.gif   Limiting search data, posted by Alan Grant on Thu Apr 27 22:21:03 2017 

I'm aware there is the "Show Last Default" setting for the Find page but is there (or can there PLEASE be) a similar setting for the Period filter on the List page? Our users routinely use the Quick Filters instead and it bogs down the system because we have lots of logbooks. Many thanks.

    icon2.gif   Re: Limiting search data, posted by Stefan Ritt on Fri Apr 28 08:15:56 2017 

I don't get your point. If you go on the list page of this forum, you see -- all entries -- in the period quick filter, but you only see one page of entries, which is rather quick. This can be changed wiht "Entries per page", which defaults to 20. Do you have a different set-up?

Alan Grant wrote:

I'm aware there is the "Show Last Default" setting for the Find page but is there (or can there PLEASE be) a similar setting for the Period filter on the List page? Our users routinely use the Quick Filters instead and it bogs down the system because we have lots of logbooks. Many thanks.

 

       icon2.gif   Re: Limiting search data, posted by Andreas Luedeke on Fri Apr 28 11:59:30 2017 

I think I understand the question (although I have no answer):

When someone uses the "Find" page search, then there is an option to limit the search to e.g. the last year. If you search for a non existing string, it'll only search entries from the past year.

If people are instead using the quickfilter to search for the same non existing string, then all entries of all past years are searched for the string.

In both cases the result page will be empty, so "Entries per page" does not change anything. But in the second case the search might need an order of magnitude longer.

Stefan Ritt wrote:

I don't get your point. If you go on the list page of this forum, you see -- all entries -- in the period quick filter, but you only see one page of entries, which is rather quick. This can be changed wiht "Entries per page", which defaults to 20. Do you have a different set-up?

Alan Grant wrote:

I'm aware there is the "Show Last Default" setting for the Find page but is there (or can there PLEASE be) a similar setting for the Period filter on the List page? Our users routinely use the Quick Filters instead and it bogs down the system because we have lots of logbooks. Many thanks.

 

 

          icon2.gif   Re: Limiting search data, posted by Stefan Ritt on Fri Apr 28 12:33:55 2017 

Ok, got it. Will put it on the to-do list.

Andreas Luedeke wrote:

I think I understand the question (although I have no answer):

When someone uses the "Find" page search, then there is an option to limit the search to e.g. the last year. If you search for a non existing string, it'll only search entries from the past year.

If people are instead using the quickfilter to search for the same non existing string, then all entries of all past years are searched for the string.

In both cases the result page will be empty, so "Entries per page" does not change anything. But in the second case the search might need an order of magnitude longer.

Stefan Ritt wrote:

I don't get your point. If you go on the list page of this forum, you see -- all entries -- in the period quick filter, but you only see one page of entries, which is rather quick. This can be changed wiht "Entries per page", which defaults to 20. Do you have a different set-up?

Alan Grant wrote:

I'm aware there is the "Show Last Default" setting for the Find page but is there (or can there PLEASE be) a similar setting for the Period filter on the List page? Our users routinely use the Quick Filters instead and it bogs down the system because we have lots of logbooks. Many thanks.

 

 

 

icon5.gif   Elog crashes with null Username, posted by Alan Grant on Sun Dec 18 08:51:47 2016 

I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:

16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)

    icon2.gif   Re: Elog crashes with null Username, posted by Stefan Ritt on Mon Dec 19 12:28:47 2016 

Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.

Alan Grant wrote:

I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:

16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)

 

       icon2.gif   Re: Elog crashes with null Username, posted by Alan Grant on Mon Dec 19 19:42:05 2016 

Thanks for the speedy fix.

FYI, our other Elog instances which are running ealrier versions do not exhibit this problem, as I confirmed that entering null ID/password returns "Invalid Username or password" as expected. This may be why it wasn't mentioned by anyone else before. Maybe something got inadvertently dropped in the newer version.

Stefan Ritt wrote:

Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.

Alan Grant wrote:

I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:

16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)

 

 

       icon2.gif   Re: Elog crashes with null Username, posted by Xuan Wu on Fri Apr 21 02:21:59 2017 

We also meet this issue occasionally, so how can we get rid of this?

Stefan Ritt wrote:

Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.

Alan Grant wrote:

I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:

16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)

 

 

          icon2.gif   Re: Elog crashes with null Username, posted by Alan Grant on Fri Apr 21 05:27:35 2017 

Are you using the current git revision Xuan?

Xuan Wu wrote:

We also meet this issue occasionally, so how can we get rid of this?

Stefan Ritt wrote:

Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.

Alan Grant wrote:

I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:

16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)

 

 

 

             icon2.gif   Re: Elog crashes with null Username, posted by Xuan Wu on Fri Apr 21 08:19:05 2017 

No, We are using the released version 3.1.2

How to use the current git revision or is it a long time to wait for the next release?

Alan Grant wrote:

Are you using the current git revision Xuan?

Xuan Wu wrote:

We also meet this issue occasionally, so how can we get rid of this?

Stefan Ritt wrote:

Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.

Alan Grant wrote:

I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:

16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)

 

 

 

 

                icon2.gif   Re: Elog crashes with null Username, posted by Stefan Ritt on Fri Apr 21 10:57:07 2017 

I made a new release for you 3.1.3

Xuan Wu wrote:

No, We are using the released version 3.1.2

How to use the current git revision or is it a long time to wait for the next release?

Alan Grant wrote:

Are you using the current git revision Xuan?

Xuan Wu wrote:

We also meet this issue occasionally, so how can we get rid of this?

Stefan Ritt wrote:

Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.

Alan Grant wrote:

I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:

16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)

 

 

 

 

 

                   icon2.gif   Re: Elog crashes with null Username, posted by Xuan Wu on Fri Apr 21 12:18:57 2017 

Awesome!It's appreciated. Many Thanks!

Stefan Ritt wrote:

I made a new release for you 3.1.3

Xuan Wu wrote:

No, We are using the released version 3.1.2

How to use the current git revision or is it a long time to wait for the next release?

Alan Grant wrote:

Are you using the current git revision Xuan?

Xuan Wu wrote:

We also meet this issue occasionally, so how can we get rid of this?

Stefan Ritt wrote:

Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.

Alan Grant wrote:

I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:

16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)

 

 

 

 

 

 

icon5.gif   Full anonymous access, posted by K on Thu Apr 20 12:45:11 2017 

How can i configure eLog to be used completely anonymous without the need to log in?

I tried menu and guest menu settings without luck. I do not use password files. With earlier versions this was easy to set up...

 

Thanks in advance

    icon2.gif   Re: Full anonymous access, posted by Stefan Ritt on Thu Apr 20 12:59:24 2017 

Sure. Just remove "Password file = ..." and any guest menu.

Stefan

K wrote:

How can i configure eLog to be used completely anonymous without the need to log in?

I tried menu and guest menu settings without luck. I do not use password files. With earlier versions this was easy to set up...

 

Thanks in advance

 

       icon2.gif   Re: Full anonymous access, posted by K on Thu Apr 20 13:35:53 2017 

Does not work.

Clean install (debian 8 x64, with aptitude), only thing i've changed in the config is "URL"-parameter (global section) and redirection with Apache. No luck. Edit or delete gives an error "Error: Command "Delete" not allowed", "New" opens login-windows.

Now i removed all (guest) menu and URL settings a use it directly (port 8080), still no luck. "Error: Command "Delete" not allowed". When i click on "New" a login-windows opens.

Tested with the demo-logbook.

Stefan Ritt wrote:

Sure. Just remove "Password file = ..." and any guest menu.

Stefan

K wrote:

How can i configure eLog to be used completely anonymous without the need to log in?

I tried menu and guest menu settings without luck. I do not use password files. With earlier versions this was easy to set up...

 

Thanks in advance

 

 

          icon2.gif   Re: Full anonymous access, posted by Stefan Ritt on Thu Apr 20 13:45:42 2017 

Version 2.9.2 is hopelessly outdated. Please upgrade to the current version on bitbucket. You also might have to delete any cookie in the browser sent to the elog server.

K wrote:

Does not work.

Clean install (debian 8 x64, with aptitude), only thing i've changed in the config is "URL"-parameter (global section) and redirection with Apache. No luck. Edit or delete gives an error "Error: Command "Delete" not allowed", "New" opens login-windows.

Now i removed all (guest) menu and URL settings a use it directly (port 8080), still no luck. "Error: Command "Delete" not allowed". When i click on "New" a login-windows opens.

Tested with the demo-logbook.

Stefan Ritt wrote:

Sure. Just remove "Password file = ..." and any guest menu.

Stefan

K wrote:

How can i configure eLog to be used completely anonymous without the need to log in?

I tried menu and guest menu settings without luck. I do not use password files. With earlier versions this was easy to set up...

 

Thanks in advance

 

 

 

             icon2.gif   Re: Full anonymous access, posted by K on Thu Apr 20 13:48:43 2017 

OK, i will try that. Thanks.

Stefan Ritt wrote:

Version 2.9.2 is hopelessly outdated. Please upgrade to the current version on bitbucket. You also might have to delete any cookie in the browser sent to the elog server.

K wrote:

Does not work.

Clean install (debian 8 x64, with aptitude), only thing i've changed in the config is "URL"-parameter (global section) and redirection with Apache. No luck. Edit or delete gives an error "Error: Command "Delete" not allowed", "New" opens login-windows.

Now i removed all (guest) menu and URL settings a use it directly (port 8080), still no luck. "Error: Command "Delete" not allowed". When i click on "New" a login-windows opens.

Tested with the demo-logbook.

Stefan Ritt wrote:

Sure. Just remove "Password file = ..." and any guest menu.

Stefan

K wrote:

How can i configure eLog to be used completely anonymous without the need to log in?

I tried menu and guest menu settings without luck. I do not use password files. With earlier versions this was easy to set up...

 

Thanks in advance

 

 

 

 

icon1.gif   rename menu commands , posted by Francois Cloutier on Tue Apr 11 17:24:48 2017 

Hi !

I do have an setup were I would like to rename the menu command but keeping their fonction. Namely, I would like to rename the "copy to" button to "Duplicate" since thats the option I would like to put in place ( Copy to = Same logbook only).

I tried to do so with css but it is not possible since the button doesn't have a specific id... Would you have another solution ? 

Thanks for your help !

    icon2.gif   Re: rename menu commands , posted by David Pilgram on Tue Apr 11 18:05:15 2017 

Hi,

First up, the Copy command is supposed to be used to copy to another log book, as it says in the documentation, not a duplicate entry in the same logbook.  I've tried doing a copy into the same logbook, it appears to work (although I don't know about every circumstance, I just did a quick and dirty test).  Use at your own risk!  Don't use Preserve ID feature is one caution I would raise immediately.

As for renaming the command, I'd suggest defining a new language, "lenglish" or whatever, make all the files necessary as per any normal language; in the eloglang.lenglish file would be

New = New

Edit = Modify

---

Copy to = Duplicate

and so on.  I chose to call my eloglang "lenglish" as duplicate, modify etc as used in the example here derive from Latin, but other commands would still be English.

 

When specified in the config file (just like the languages that "come with the box") that should give you the alternative names for the commands.

David.

Francois Cloutier wrote:

Hi !

I do have an setup were I would like to rename the menu command but keeping their fonction. Namely, I would like to rename the "copy to" button to "Duplicate" since thats the option I would like to put in place ( Copy to = Same logbook only).

I tried to do so with css but it is not possible since the button doesn't have a specific id... Would you have another solution ? 

Thanks for your help !

 

    icon5.gif   Re: rename menu commands , posted by Andreas Luedeke on Tue Apr 11 22:44:40 2017 

Hm, maybe my question is silly, but why don't you just use the "Duplicate" command instead of renaming and misusing "Copy to"??

Here is the relevant excerpt from the documentation (https://midas.psi.ch/elog/config.html#general):

Menu commands = <list>
This option specifies the menu commands displayed on top of a single logbook page. For certain installations, it can be useful to disable some commands. Following commands are possible:

  • New - Enter new logbook entry
  • Edit - Edit current logbook entry
  • Delete - Delete current logbook entry
  • Reply - Submit a reply to current entry
  • Duplicate - Duplicate the current entry with the possibility to change some values
  • [...]
  • Copy to - Copy entry to other logbook
  • [...]

The commands are always in English, independent of the language = ... setting, and are automatically translated into the specified language.
If this option is not present, following default is used:

Menu commands = List, New, Edit, Delete, Reply, Duplicate, Find, Config, Help
Francois Cloutier wrote:

Hi !

I do have an setup were I would like to rename the menu command but keeping their fonction. Namely, I would like to rename the "copy to" button to "Duplicate" since thats the option I would like to put in place ( Copy to = Same logbook only).

I tried to do so with css but it is not possible since the button doesn't have a specific id... Would you have another solution ? 

Thanks for your help !

 

       icon3.gif   Re: rename menu commands , posted by Francois Cloutier on Wed Apr 12 13:52:34 2017 

Somehow, I've missed to see that option :)

Thanks :)

Andreas Luedeke wrote:

Hm, maybe my question is silly, but why don't you just use the "Duplicate" command instead of renaming and misusing "Copy to"??

Here is the relevant excerpt from the documentation (https://midas.psi.ch/elog/config.html#general):

Menu commands = <list>
This option specifies the menu commands displayed on top of a single logbook page. For certain installations, it can be useful to disable some commands. Following commands are possible:

  • New - Enter new logbook entry
  • Edit - Edit current logbook entry
  • Delete - Delete current logbook entry
  • Reply - Submit a reply to current entry
  • Duplicate - Duplicate the current entry with the possibility to change some values
  • [...]
  • Copy to - Copy entry to other logbook
  • [...]

The commands are always in English, independent of the language = ... setting, and are automatically translated into the specified language.
If this option is not present, following default is used:

Menu commands = List, New, Edit, Delete, Reply, Duplicate, Find, Config, Help
Francois Cloutier wrote:

Hi !

I do have an setup were I would like to rename the menu command but keeping their fonction. Namely, I would like to rename the "copy to" button to "Duplicate" since thats the option I would like to put in place ( Copy to = Same logbook only).

I tried to do so with css but it is not possible since the button doesn't have a specific id... Would you have another solution ? 

Thanks for your help !

 

 

          icon2.gif   Re: rename menu commands , posted by David Pilgram on Wed Apr 12 14:00:58 2017 

So did I [thankful there is no shame face icon].

Francois Cloutier wrote:

Somehow, I've missed to see that option :)

Thanks :)

Andreas Luedeke wrote:

Hm, maybe my question is silly, but why don't you just use the "Duplicate" command instead of renaming and misusing "Copy to"??

Here is the relevant excerpt from the documentation (https://midas.psi.ch/elog/config.html#general):

Menu commands = <list>
This option specifies the menu commands displayed on top of a single logbook page. For certain installations, it can be useful to disable some commands. Following commands are possible:

  • New - Enter new logbook entry
  • Edit - Edit current logbook entry
  • Delete - Delete current logbook entry
  • Reply - Submit a reply to current entry
  • Duplicate - Duplicate the current entry with the possibility to change some values
  • [...]
  • Copy to - Copy entry to other logbook
  • [...]

The commands are always in English, independent of the language = ... setting, and are automatically translated into the specified language.
If this option is not present, following default is used:

Menu commands = List, New, Edit, Delete, Reply, Duplicate, Find, Config, Help
Francois Cloutier wrote:

Hi !

I do have an setup were I would like to rename the menu command but keeping their fonction. Namely, I would like to rename the "copy to" button to "Duplicate" since thats the option I would like to put in place ( Copy to = Same logbook only).

I tried to do so with css but it is not possible since the button doesn't have a specific id... Would you have another solution ? 

Thanks for your help !

 

 

 

ELOG V3.1.5-3fb85fa6