ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67182
|
Fri Feb 10 11:54:35 2012 |
| Olaf Kasten | olaf.kasten@deutschebahn.com | Bug report | Linux | Windows | 2.9.0 | ssl problems |
Hi there,
I have a connection problem with an actual elog installation. Many Browsers like as Chrome, Firefox and IE don't connect to the elog server with ssl = 1 in elogd.cfg.
I tested with Firefox 3.6 and IE 7 installations and there are no problems.
I guess it's a bug. Does someone have a suggestion to solve that problem?
Thx. Olaf |
67191
|
Mon Feb 13 13:38:19 2012 |
| Adam | dellzoid@hotmail.com | Question | Linux | 2.7.8 | redirect permission |
Hi All,
Perhaps a trivial question but some issues have arisen accessing my long-running elog with SSL enabled. I suspect firewalls and browser updates are involved and I do not have the time or experience to diagnose and debug such a potential black-hole of difficulties. Instead I am looking for a quick fix, and the first step - switching off sll - seems to work. Now I would like to use redirect so that the elog is running under apache, however this is where I have stumbled; I have passwords so the plan is to eventually secure using apache. Apache works fine and is running pages on ports 80 and 443, although I seem unable to redirect the elog (port 8080). Following the instructions on the administrators guide I get:
Forbidden
You don't have permission to access /elog/ on this server.
The page is found at least so my redirect is doing something, and I suspect the solution is trivial, though I'm not too sure where to start.
-------------------
Also, what is the best practice for updating one's elog version. I originally installed using a tarball.
|
67209
|
Thu Mar 8 10:01:47 2012 |
| Olivier Callot | olivier.callot@cern.ch | Bug report | Linux | 2.9.0-2418 | Truncation of the displayed text in Summary view of the list of entries |
In the summary view, it seems that the text is truncated at the first "<" character. See https://lblogbook.cern.ch/Shift/48812 for a simple entry, then use the 'list' command to see that only a very small part is displayed. |
67257
|
Tue May 1 11:38:05 2012 |
| Per Eriksson | pelle@sm4xiu.eu | Request | Linux | Any | Compiling Elog for QNAP NAS x86 |
Hi All,
I am interested to have ELOG installed in my QNAP x86 based NAS (239 Pro II)
Have someone done this already or is there a write-up of a normal compile-procedure which I can have as a base when I attempt to compile?
Regards,
Per |
67358
|
Sat Oct 27 18:10:14 2012 |
| Philippe Rousselot | rousselot@rousselot.org | Question | Linux | Windows | latest | Comment avoir elog en français |
|
67426
|
Mon Jan 14 03:05:41 2013 |
| Bruce Weber | bruce.weber@inmarsat.com | Question | Windows | 2.7.8 | Dual Time display and entry times |
ELog has been installed on our local server which runs on local time (UTC +8) and is working well, however, we work in two time zones.
Our PC's run in local time (IT requirement) but need to save and display one log in UTC and one log in local time - can this be done?
Appreciate anyones help!
Thanks |
67509
|
Sat May 18 17:41:51 2013 |
| Norm | normthompson@yahoo.com | Bug report | Windows | Unknown | Application failed to initialize properly |
I attempted to install the newest version of elog on our site elog server from an old old version. Around 2008 I believe. I then received an application failed to initialize properly 0xc0150002 after installing the newest version. I then tried installing the Feb 2013 version and received the same message. Panicked, I rolled back our server to its state yesterday. I would like to update our elog software, anyone know why I am receiving this error?? |
67521
|
Mon Jun 3 15:44:46 2013 |
| Martin Rongen | martin.rongen@rwth-aachen.de | Question | Linux | 2.9.2 | Daemonizing vs. shell execution |
Hi all
I have setup an logbook that executes a number of shell scripts to preset attributes and append standart information, which works great. Now I am trying to daemonise the whole thing. I have tried the -D option as well as daemontools. In both cases the logbook itself is functional but the bash scripts do not get executed.
Any ideas how I can resolve this problem?
Martin |