ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 209 of 806

Not logged in

Find | Login | Help

New entries since:

Thu Jan 1 01:00:00 1970

Full | Summary | Threaded | Hide attachments

6445 Entries

Goto page Previous 1, 2, 3 ... 208, 209, 210 ... 804, 805, 806 Next

Tue Mar 11 15:17:36 2014

Donald

don.drummel@gmail.com

Donald wrote:

Andreas Luedeke wrote:

Donald wrote:

I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book. I've attached a example of the output.

When i attempt a import i get this error

"XML file does not contain <ENCODING> element"

The file does contain an encoding for utf-8 I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.

is there something obvious that I'm missing?

here is the config of the log book:

[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type

Hi Donald,

yes, the import function gave me some headache in the past, too.

⇄

English (auto-detected) » English

Here it appears that <ENCODING> </ENCODING> became somehow mandatory. But it has a different meaning then what you expect: it is the type of code in the text field, one out of HTML, ELCode or plain.

(Stefan: is this needed to be mandatory? Couldn't you just have some default ?)

In your case: you can just add the XML code "<ENCODING> </ENCODING>" before the <TEXT> token.

My problems were always related to the date format: elogd is very restrictive about what date format it is accepting. that will be your next pproblem ;-)

I hope this helps.

Hi Andreas

That worked, thank you so much. now I'm on to a new error.

Now every time i try to do the import it crashed the elogd.

OS is windows server 2008 R2. I have the elogd installed as a service.

here is the even log:

Faulting application name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Faulting module name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Exception code: 0xc0000417
Fault offset: 0x000682da
Faulting process id: 0x558
Faulting application start time: 0x01cf37d8870fc9a1
Faulting application path: D:\Program Files (x86)\ELOG\elogd.exe
Faulting module path: D:\Program Files (x86)\ELOG\elogd.exe
Report Id: defc3f39-a3cb-11e3-9dd5-005056954c86

I have attached the Data file I'm using to generate the fault every time. same config as before. Any Ideas?

Anyone have any luck reproducing the error? or have suggestions on how to fix it?

67183

Fri Feb 10 17:18:25 2012

John Doroshenko

doroshenko@physics.rutgers.edu

Olaf Kasten wrote:

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

Hi!

This just started happening here also. Some users can't get on to a SSL=1 config'd elog using either IE or firefox 10 (win7 or linux) or chrome. SAFARI works. Occurs in 2.8.0 and a newly built (even after

ssl yum updates) 2.9.0 version on SL5.5 system. Seems to accept self signed cert then nothing.. (connection reset message). Tried an stunnel from one port to port running elog

with SSL=0. Same behavior. Doesn't work on some browsers. Any clues?

Thanks,

-John

67195

Tue Feb 14 00:55:58 2012

John Doroshenko

doroshenko@physics.rutgers.edu

Andreas Luedeke wrote:

John Doroshenko wrote:

Olaf Kasten wrote:

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

Hi!

ssl yum updates) 2.9.0 version on SL5.5 system. Seems to accept self signed cert then nothing.. (connection reset message). Tried an stunnel from one port to port running elog

with SSL=0. Same behavior. Doesn't work on some browsers. Any clues?

Thanks,

-John

Hi everyone,

it appears that many people have this problem. I believe this is simply a problem of your firewall settings. There are two simple checks you can do to test if I'm right or wrong:

Run your logbook on the standard port 443 and retry. If the special port has been opened on the firewall, it has been likely only opened for specific clients like firefox 3.6, IE 7, etc. If you use a different client (FF 10, IE 9) the port can be blocked.
Or just run the browser that does not work on the ELOG server. If it works to access ELOG via localhost, then you know for sure that it is the firewall.

I've actually tested it here at my institute: I've downloaded firefox 10 and could access ELOG on port 443 but couldn't access it on port 444, unless I've started FF10 on the ELOG host.

To John, Olaf and Christian: If you need to be able to use a special port and a certain set of browsers then just contact your computing division or whoever maintains your firewalls.

I hope this settles the matter.

Cheers

Andreas

⇄

Detect language » English

PS: I've solved this with the help of google : have a look at http://forums.mozillazine.org/viewtopic.php?p=2295421#2295421 about firewalls

Hi,

Thanks for the reply.

The elog server is running SL5.5 (updates applied). As you suggested, I ran firefox 3.6.26 on the elog server via https://localhost:port and it worked fine. Downloaded firefox 10.0.1 and retried

on elog server and get error again: The connection was Reset; The connection to the server was reset while the page was loading.

-John

67198

Tue Feb 14 20:41:08 2012

John Doroshenko

doroshenko@physics.rutgers.edu

John Doroshenko wrote:

Andreas Luedeke wrote:

John Doroshenko wrote:

Olaf Kasten wrote:

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

Hi!

ssl yum updates) 2.9.0 version on SL5.5 system. Seems to accept self signed cert then nothing.. (connection reset message). Tried an stunnel from one port to port running elog

with SSL=0. Same behavior. Doesn't work on some browsers. Any clues?

Thanks,

-John

Hi everyone,

it appears that many people have this problem. I believe this is simply a problem of your firewall settings. There are two simple checks you can do to test if I'm right or wrong:

Run your logbook on the standard port 443 and retry. If the special port has been opened on the firewall, it has been likely only opened for specific clients like firefox 3.6, IE 7, etc. If you use a different client (FF 10, IE 9) the port can be blocked.
Or just run the browser that does not work on the ELOG server. If it works to access ELOG via localhost, then you know for sure that it is the firewall.

I've actually tested it here at my institute: I've downloaded firefox 10 and could access ELOG on port 443 but couldn't access it on port 444, unless I've started FF10 on the ELOG host.

To John, Olaf and Christian: If you need to be able to use a special port and a certain set of browsers then just contact your computing division or whoever maintains your firewalls.

I hope this settles the matter.

Cheers

Andreas

⇄

Detect language » English

PS: I've solved this with the help of google : have a look at http://forums.mozillazine.org/viewtopic.php?p=2295421#2295421 about firewalls

Hi,

Thanks for the reply.

The elog server is running SL5.5 (updates applied). As you suggested, I ran firefox 3.6.26 on the elog server via https://localhost:port and it worked fine. Downloaded firefox 10.0.1 and retried

on elog server and get error again: The connection was Reset; The connection to the server was reset while the page was loading.

-John

Hi,

One of our sys admins discovered that Firefox 10 appeared to send parts of the initial GET in two parts. As if there was a flush() after the "G" and this caused elog problems. By making the change in

the patch below, the read loop is re-entered again after the 2nd part of the GET comes in. Firefox 10.0.1 then works with ELOG with SSL. Stefan... perhaps you can take a look to see if there is a

better way to accomplish this?

One side effect with it done this way is that if you start a connection (ie, telnet localhost port) and type a single character, the elog will block further connections until the telnet is terminated.

Thank you,

-John Doroshenko

Attachment 1: fire10elog.patch

--- elogd.c.orig	2012-02-14 12:54:05.000000000 -0500
+++ elogd.c	2012-02-14 13:20:13.000000000 -0500
@@ -28805,7 +28805,9 @@
 
                   /* finish when empty line received */
                   pend = NULL;
-                  if (strncmp(net_buffer, "GET", 3) == 0 && strncmp(net_buffer, "POST", 4) != 0) {
+		  if (len < 4) { 
+		    pend = net_buffer + len;
+		  } else if (strncmp(net_buffer, "GET", 3) == 0 && strncmp(net_buffer, "POST", 4) != 0) {
                      if (len > 4 && strstr(net_buffer, "\r\n\r\n") != NULL) {
                         pend = strstr(net_buffer, "\r\n\r\n") + 4;
                         break;

67202

Thu Feb 16 23:56:35 2012

John Doroshenko

doroshenko@physics.rutgers.edu

Stefan Ritt wrote:

Yes, there is a new feature called record splitting which causes the browser to send the "G" of the "GET ..." in a dedicated TCP package. This started in FF10, Chrome 17, and it will come in others as well. It only affects direct SSL connections (SSL=1). I fixed the bug in SVN revision #2435. Please update also MXML to revision #73. Let's hope that surprises like that will not happen too often.

- Stefan

Thank you Stefan! I put up your new svn revision and we're back in business. Seems to be working perfectly.

And thank you again for your efforts with regards to ELOG. It is an incredibly handy tool.

-John

65922

Thu Jul 10 12:06:31 2008

Dougie Mooney

dougie.mooney@selex-galileo.com

Question

Windows

2.7.3-2104

Synchronising between physically separate networks

Hi there. Just started recently set up the application and think its very usable and easily configured - great stuff

I'm looking to roll it out to the masses but have a slight logistical problem in that we work on 2 separate networks - NET1 with connection to the internet, and NET2 physically isolated from NET1 and the internet.

It would be desirable to allow users to add/update/delete logs from both NET1 and NET2 with periodic synchronisation.

I believe the mirroring facility is what should be used, and think the following setup and synchronisation steps may be workable:

Setup:

elog installed on node of NET1
elog installed on 2 nodes of NET2
elog server running on NET1 and node1 of NET2 both using a common elogd.cfg

Performing Synchronisation:

Stop the server on NET1
copy logbook directories from NET1 to node2 of NET2
start server on node2 of NET2 using the -M option
once above complete, copy logbook directories from node 2 NET2 to NET1
Start the server on NET1

Am I on the right track?

Would very much appreciate your comments and advice on the above.

Cheers Dougie

65835

Thu Apr 17 19:56:41 2008

Custom Links in each column, in the display list?

Using the "Link Display =" I can turn of the link to each individual entry, however, I would like to have a custom link in one of my columns. Is this possible?

Thanks for this wonderful tool.

Don

65924

Mon Jul 14 16:23:26 2008

TCK-##### stopped Working

Goto page Previous 1, 2, 3 ... 208, 209, 210 ... 804, 805, 806 Next

ELOG V3.1.5-3fb85fa6