Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 269 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  68015   Fri Jun 12 11:59:00 2015 Reply Neal Graftonneal.grafton@stfc.ac.ukBug reportOtherELOG V3.1.1-5eaRe: Upload of images fails from mobile platforms when using ELOG under SSL

On the subject of uploads, is there a way to restrict the viewing size of an uploaded photo or picture in the config? So it doesn't appear over more than one page.

Neal

 

Stefan Ritt wrote:

That's strange. Might have to do with the SSL library elog uses. I just tried this forum (actually the "Demo"), and it worked fine through SSL, but I use an Apache proxy server for elog implementing the SSL protocol, which might be slightly different.

Hanno Perrey wrote:

Hej,

I discovered a problem uploading images taken with the cameras of mobile devices to new elog entries directly from said devices. When selecting the image and choosing "Upload", either the blue page loading indicator gets stuck at around 10% (mobile Safari, iOS 8.3, iPhone 4 and iPad mini) or the error message "failed secure connection; connection reset while page was being loaded" ("Fehler: gesicherte Verbindung fehlgeschlagen. Verbindung zum Server wurde zurueckgesetzt waehrend die Seite geladen wurde") appears shortly after (Android 5.02, Firefox 37.0.2, Motorola G).

From the desktop browser (Firefox 38.0.5, OSX 10.10) there is no problem uploading images at all.

So far, this problem is very reproducible, but only when using ELOG with SSL enabled. Without SSL, the problem disappears on all platforms.

The ELOG daemon runs under Linux (Fedora 18) and I have also tried using the latest development version of ELOG.

Running ELOG with debug messages the only output after the page has been loaded is:

TCP connection #0 on socket 4 closed
TCP connection #0 on socket 4 closed

After these, there is no further output and the mobile devices do not indicate any progress either even after many mi.

The minimal config file I have been using is:

[global]
; network
port = 443
SSL = 1
URL = https://my.server.somewhere/
; paths
Logbook dir = /usr/local/elog/logbooks
Resource dir = /usr/local/elog
Logfile = /tmp/elog.log


[demo]
Attributes = Author, Type, Category, Subject
Required Attributes = Author, Type
Options Type = Status, Modification, Problem Report, Problem Details, Problem Fixed, Other
Options Category = Facility, Experiment, IT, Other
List Page Title = $logbook - $subject

As mentioned before, removing the first three lines fixes the problem (the URL line points to my actual server of course).

I would appreciate any pointers on how to debug this further! The functionality of posting images directly from mobile devices is quite important for the planed deployment of ELOG and I would very much prefer to have SSL enabled when doing so.

 

Thanks and cheers,

Hanno

 

 

  68016   Fri Jun 12 12:19:50 2015 Reply Stefan Rittstefan.ritt@psi.chBug reportOtherELOG V3.1.1-5eaRe: Upload of images fails from mobile platforms when using ELOG under SSL

Use thumbnails (need ImageMagick to be installed for that), and you can show for example 300x300 pixel thumbnails of all pictures.

Neal Grafton wrote:

On the subject of uploads, is there a way to restrict the viewing size of an uploaded photo or picture in the config? So it doesn't appear over more than one page.

Neal

 

Stefan Ritt wrote:

That's strange. Might have to do with the SSL library elog uses. I just tried this forum (actually the "Demo"), and it worked fine through SSL, but I use an Apache proxy server for elog implementing the SSL protocol, which might be slightly different.

Hanno Perrey wrote:

Hej,

I discovered a problem uploading images taken with the cameras of mobile devices to new elog entries directly from said devices. When selecting the image and choosing "Upload", either the blue page loading indicator gets stuck at around 10% (mobile Safari, iOS 8.3, iPhone 4 and iPad mini) or the error message "failed secure connection; connection reset while page was being loaded" ("Fehler: gesicherte Verbindung fehlgeschlagen. Verbindung zum Server wurde zurueckgesetzt waehrend die Seite geladen wurde") appears shortly after (Android 5.02, Firefox 37.0.2, Motorola G).

From the desktop browser (Firefox 38.0.5, OSX 10.10) there is no problem uploading images at all.

So far, this problem is very reproducible, but only when using ELOG with SSL enabled. Without SSL, the problem disappears on all platforms.

The ELOG daemon runs under Linux (Fedora 18) and I have also tried using the latest development version of ELOG.

Running ELOG with debug messages the only output after the page has been loaded is:

TCP connection #0 on socket 4 closed
TCP connection #0 on socket 4 closed

After these, there is no further output and the mobile devices do not indicate any progress either even after many mi.

The minimal config file I have been using is:

[global]
; network
port = 443
SSL = 1
URL = https://my.server.somewhere/
; paths
Logbook dir = /usr/local/elog/logbooks
Resource dir = /usr/local/elog
Logfile = /tmp/elog.log


[demo]
Attributes = Author, Type, Category, Subject
Required Attributes = Author, Type
Options Type = Status, Modification, Problem Report, Problem Details, Problem Fixed, Other
Options Category = Facility, Experiment, IT, Other
List Page Title = $logbook - $subject

As mentioned before, removing the first three lines fixes the problem (the URL line points to my actual server of course).

I would appreciate any pointers on how to debug this further! The functionality of posting images directly from mobile devices is quite important for the planed deployment of ELOG and I would very much prefer to have SSL enabled when doing so.

 

Thanks and cheers,

Hanno

 

 

 

  68028   Thu Jun 18 15:46:28 2015 Reply Hanno Perreyhanno.perrey@nuclear.lu.seBug reportOtherELOG V3.1.1-5eaRe: Upload of images fails from mobile platforms when using ELOG under SSL

Hej Stefan,

thanks for the suggestion -- through a Apache proxy the upload does indeed work without problems.

Cheers,

Hanno

Stefan Ritt wrote:

That's strange. Might have to do with the SSL library elog uses. I just tried this forum (actually the "Demo"), and it worked fine through SSL, but I use an Apache proxy server for elog implementing the SSL protocol, which might be slightly different.

Hanno Perrey wrote:

Hej,

I discovered a problem uploading images taken with the cameras of mobile devices to new elog entries directly from said devices. When selecting the image and choosing "Upload", either the blue page loading indicator gets stuck at around 10% (mobile Safari, iOS 8.3, iPhone 4 and iPad mini) or the error message "failed secure connection; connection reset while page was being loaded" ("Fehler: gesicherte Verbindung fehlgeschlagen. Verbindung zum Server wurde zurueckgesetzt waehrend die Seite geladen wurde") appears shortly after (Android 5.02, Firefox 37.0.2, Motorola G).

From the desktop browser (Firefox 38.0.5, OSX 10.10) there is no problem uploading images at all.

So far, this problem is very reproducible, but only when using ELOG with SSL enabled. Without SSL, the problem disappears on all platforms.

The ELOG daemon runs under Linux (Fedora 18) and I have also tried using the latest development version of ELOG.

Running ELOG with debug messages the only output after the page has been loaded is:

TCP connection #0 on socket 4 closed
TCP connection #0 on socket 4 closed

After these, there is no further output and the mobile devices do not indicate any progress either even after many mi.

The minimal config file I have been using is:

[global]
; network
port = 443
SSL = 1
URL = https://my.server.somewhere/
; paths
Logbook dir = /usr/local/elog/logbooks
Resource dir = /usr/local/elog
Logfile = /tmp/elog.log


[demo]
Attributes = Author, Type, Category, Subject
Required Attributes = Author, Type
Options Type = Status, Modification, Problem Report, Problem Details, Problem Fixed, Other
Options Category = Facility, Experiment, IT, Other
List Page Title = $logbook - $subject

As mentioned before, removing the first three lines fixes the problem (the URL line points to my actual server of course).

I would appreciate any pointers on how to debug this further! The functionality of posting images directly from mobile devices is quite important for the planed deployment of ELOG and I would very much prefer to have SSL enabled when doing so.

 

Thanks and cheers,

Hanno

 

 

  67062   Tue May 3 08:22:18 2011 Reply Pellepelle@sm4xiu.euOtherWindows2.6.0Re: Upgrading to 2.9

Maureen Kular wrote:

I am in the process of upgrading from 2.6.0 to 2.9.0.  I am installing it on a windows 2008 r2 server which is 64 bit.  I am having a few issues and am just wondering if Windows 2008 R2 is support with version 2.9.0.  Is there anything I need to know about the installation other than just run the exe file?  So far I have run the exe file and installed the software, the service is running, however I cannot get into the application.  I do not have IIS installed, it does mention it in the installation documentation, is this a requirement?  Any hints or ideas at this point would be appreciated.  I am close I just need that last tweek.  Thanks

 Hi Maureen,

You write "Upgrading from 2.6.0" Is that version working on the same computer?
If so then its strange. Else try with one of the demo config files and see what happens, try different ports etc.

If the service is running it should work the rest too. I'm running it on a Win7 64 bit so 64 bit is not the problem....

Best

Per

 

  1538   Fri Dec 2 12:27:47 2005 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.5.6.1Re: Upgrading from ELOG V2.5.6-1 to ELOG V2.5.9 steps

Rob de Bruin wrote:
We whant to upgrade to the latest version, can i just install the latest version over my older version??
I wil backup etc. offcourse.


Yes. The 2.6.0-beta1,2,3,4 have some problems, but the latest beta5 is pretty stable.


Rob de Bruin wrote:
Are there things i'll have to be alert to?


Usually only new options get added, and I keep the old ones, so there should not be any problem, although I do not record carefully what changes between any arbitray versions, so just read the changelogs


Rob de Bruin wrote:
Can someone give me a link to a document?


The changelog is located at http://midas.psi.ch/elog/download/ChangeLog

I have not put in the new stuff from 2.6.0, because it's still in beta.

- Stefan
  2226   Mon Apr 30 21:01:49 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.5-1857Re: Upgraded from 2.6.1 to 2.6.5, but cannot login now & top.html is not displayed

Alan Stone wrote:
We followed the simple download instructions. Our existing logbook entries
are still visible. Nothing was lost or touched in our /usr/local/elog directory.
Is there some step we missed?
Alan


Have you tried to delete your cookies in the browser and try again?

The location of top.html has been changed from the ELOG root down into the loogbook directory. If you want to keep it in the original location, you have to specify the full path. See the documentation for where to put the file for "Top text".
  2158   Tue Mar 6 17:03:43 2007 Agree T. Ribbrockemgaron@gmx.netBug reportLinux2.6.4Re: Upgrade to 2.6.4 broke quick search

T. Ribbrock wrote:

[...]
I just went from 2.6.1 to 2.6.4 and since the upgrade, the quick search drop-down menus no longer work. I can select an attribute, but when I do so, I only get an empty page with the following message:
Attachment #0 of entry #0 not found
Please use your browser's back button to go back
[...]


Apparently, this must have been some session-oddity - I just logged out and got an error message about a bad URL. I then went to the base URL of the logbook (i.e. http://server:8080), chose the correct logbook and logged in again. Things work fine since. No idea what went wrong the first time round... Frown

Regards,

Thomas
  1540   Mon Dec 5 17:11:33 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0Re: Upgrade from 2.3.8 to 2.6.0 logbook problem

Jesse Wodin wrote:
Hi, I'd like to upgrade from an old version of elog 2.3.8 to 2.6.0. I installed the new version, and it runs fine, but it doesn't seem to see my old logbooks (the path in the conf file is correct). Do I have to upgrade my logbooks somehow?


No. The last change in the logbook format was for version 2.0.0. So something else must be wrong. Just creat one entry with your new elog, and see where it's created on the hard disk. Put your old logbooks there. If you start elogd manually with the "-v" flag, you will see it indexing all logbooks. Check that you see all your entries there.
ELOG V3.1.5-3fb85fa6