ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66407
|
Mon Jun 22 16:44:54 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.6 | Re: Elog won't start |
Jean-Philippe Bertrand wrote: |
We are currently having problems with Elog, I never had a problem installing it before but with my last 3 install I can't get it to work. We are running under Windows XP, the installation works perfectly but when I try to use the shortcut pointing to the localhost 8080, I get an error page from Internet Explorer telling me that the server cannot be found. I've rebootied the computer to make sure the server was running but still the same problem. Is there a basic requirement I should look at (Dotnet versionX or specific DLL required)?
|
No, there is no Dotnet or DLL required. Just start the ELOG server manually by clickin on Start/Programs/ELOG Server/Start ELOG server manually and watch if you can spot any error. One person reported that downloading again the package solved a similar problem. |
66408
|
Mon Jun 22 17:09:05 2009 |
| Jean-Philippe Bertrand | johnneyb@hotmail.com | Question | Windows | 2.7.6 | Re: Elog won't start |
Stefan Ritt wrote: |
Jean-Philippe Bertrand wrote: |
We are currently having problems with Elog, I never had a problem installing it before but with my last 3 install I can't get it to work. We are running under Windows XP, the installation works perfectly but when I try to use the shortcut pointing to the localhost 8080, I get an error page from Internet Explorer telling me that the server cannot be found. I've rebootied the computer to make sure the server was running but still the same problem. Is there a basic requirement I should look at (Dotnet versionX or specific DLL required)?
|
No, there is no Dotnet or DLL required. Just start the ELOG server manually by clickin on Start/Programs/ELOG Server/Start ELOG server manually and watch if you can spot any error. One person reported that downloading again the package solved a similar problem.
|
Thanks for the feedback, I found the problem, someone installed the AVG toolbar in Internet Explorer in the computers, and for some reason the AVG Error Redirection option prevents Elog from opening in Internet Explorer. |
66409
|
Wed Jun 24 13:23:49 2009 |
| Michael Husbyn | michael.husbyn@gmail.com | Bug report | Windows | 2.7.6 | (my) Firefox breaks Elog with this config file | Hi,
Did a fresh install on a Windows 2003 server (and tried it on my personal computer)
After startup I can click on Norway/nor, and then the server just stops responding. I see in the log nothing, the last line: Received unknown cooke "style"
Then it stops responding and after a few seconds I see the dos window returns to commandline prompt.
Probably a very bad config file.
On Windows XP it informs we of Dr Watson, memory could not be read message.
Using Firefox 3.0.11
But if I use IE 7, no problem at all..
Any suggestion?
Best regards
Michael Husbyn |
Attachment 1: elogd.cfg
|
[global]
port = 8091
group Norway=nor
group Sweden=swe
group Denmark=den
[nor]
Comment = $subject
Theme = default
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
[den]
Theme = default
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
Comment = General linux tips & tricks
[swe]
Comment = General linux tips & tricks
Theme = default
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
|
66410
|
Wed Jun 24 14:28:43 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.7.6 | Re: (my) Firefox breaks Elog with this config file |
Michael Husbyn wrote: |
Hi, Did a fresh install on a Windows 2003 server (and tried it on my personal computer) After startup I can click on Norway/nor, and then the server just stops responding. I see in the log nothing, the last line: Received unknown cooke "style" Then it stops responding and after a few seconds I see the dos window returns to commandline prompt. Probably a very bad config file. On Windows XP it informs we of Dr Watson, memory could not be read message. Using Firefox 3.0.11 But if I use IE 7, no problem at all.. Any suggestion? Best regards Michael Husbyn |
This must be related to the unknown cookie "style". There was some work recently on elog to make it robust against unknonw cookies. The latest modification was on version 2192, and you probably have an older version. I made a release elog276-2.exe for you. Try it and let me know. You can also just delete your cookies in Firefor and it should be fine, but it's better not being able to crash elog. |
66412
|
Thu Jun 25 09:07:51 2009 |
| Michael Husbyn | michael.husbyn@gmail.com | Bug report | Windows | 2.7.6 | Re: (my) Firefox breaks Elog with this config file |
Stefan Ritt wrote: |
Michael Husbyn wrote: |
Hi, Did a fresh install on a Windows 2003 server (and tried it on my personal computer) After startup I can click on Norway/nor, and then the server just stops responding. I see in the log nothing, the last line: Received unknown cooke "style" Then it stops responding and after a few seconds I see the dos window returns to commandline prompt. Probably a very bad config file. On Windows XP it informs we of Dr Watson, memory could not be read message. Using Firefox 3.0.11 But if I use IE 7, no problem at all.. Any suggestion? Best regards Michael Husbyn |
This must be related to the unknown cookie "style". There was some work recently on elog to make it robust against unknonw cookies. The latest modification was on version 2192, and you probably have an older version. I made a release elog276-2.exe for you. Try it and let me know. You can also just delete your cookies in Firefor and it should be fine, but it's better not being able to crash elog. |
Sure I will try, but I cannot find the version you are talking about in the download section. Should I find it there or any other place?
Thanks for quick feedback |
66413
|
Thu Jun 25 09:26:00 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.7.6 | Re: (my) Firefox breaks Elog with this config file |
Michael Husbyn wrote: |
Stefan Ritt wrote: |
Michael Husbyn wrote: |
Hi, Did a fresh install on a Windows 2003 server (and tried it on my personal computer) After startup I can click on Norway/nor, and then the server just stops responding. I see in the log nothing, the last line: Received unknown cooke "style" Then it stops responding and after a few seconds I see the dos window returns to commandline prompt. Probably a very bad config file. On Windows XP it informs we of Dr Watson, memory could not be read message. Using Firefox 3.0.11 But if I use IE 7, no problem at all.. Any suggestion? Best regards Michael Husbyn |
This must be related to the unknown cookie "style". There was some work recently on elog to make it robust against unknonw cookies. The latest modification was on version 2192, and you probably have an older version. I made a release elog276-2.exe for you. Try it and let me know. You can also just delete your cookies in Firefor and it should be fine, but it's better not being able to crash elog.
|
Sure I will try, but I cannot find the version you are talking about in the download section. Should I find it there or any other place? Thanks for quick feedback |
It's here. |
66415
|
Thu Jun 25 10:21:10 2009 |
| Michael Husbyn | michael.husbyn@gmail.com | Bug report | Windows | 2.7.6 | Re: (my) Firefox breaks Elog with this config file |
Stefan Ritt wrote: |
Michael Husbyn wrote: |
Stefan Ritt wrote: |
Michael Husbyn wrote: |
Hi, Did a fresh install on a Windows 2003 server (and tried it on my personal computer) After startup I can click on Norway/nor, and then the server just stops responding. I see in the log nothing, the last line: Received unknown cooke "style" Then it stops responding and after a few seconds I see the dos window returns to commandline prompt. Probably a very bad config file. On Windows XP it informs we of Dr Watson, memory could not be read message. Using Firefox 3.0.11 But if I use IE 7, no problem at all.. Any suggestion? Best regards Michael Husbyn |
This must be related to the unknown cookie "style". There was some work recently on elog to make it robust against unknonw cookies. The latest modification was on version 2192, and you probably have an older version. I made a release elog276-2.exe for you. Try it and let me know. You can also just delete your cookies in Firefor and it should be fine, but it's better not being able to crash elog.
|
Sure I will try, but I cannot find the version you are talking about in the download section. Should I find it there or any other place? Thanks for quick feedback |
It's here. |
Looks more stable, but it still quits. Sometimes just entering the logbook, sometimes when I hit the config button.
==== Return ================================
<549 bytes of favicon.ico>
TCP connection broken
GET /nor/elog.rdf HTTP/1.1
Host: XXSERVERNAMEHEREXX:8091
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.0.11) Gecko/2
009060215 Firefox/3.0.11 (.NET CLR 3.5.30729)
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-gb,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: elmode=Summary
and just quits
Strange |
66416
|
Thu Jun 25 10:51:12 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.7.6 | Re: (my) Firefox breaks Elog with this config file |
Michael Husbyn wrote: |
Stefan Ritt wrote: |
Michael Husbyn wrote: |
Stefan Ritt wrote: |
Michael Husbyn wrote: |
Hi, Did a fresh install on a Windows 2003 server (and tried it on my personal computer) After startup I can click on Norway/nor, and then the server just stops responding. I see in the log nothing, the last line: Received unknown cooke "style" Then it stops responding and after a few seconds I see the dos window returns to commandline prompt. Probably a very bad config file. On Windows XP it informs we of Dr Watson, memory could not be read message. Using Firefox 3.0.11 But if I use IE 7, no problem at all.. Any suggestion? Best regards Michael Husbyn |
This must be related to the unknown cookie "style". There was some work recently on elog to make it robust against unknonw cookies. The latest modification was on version 2192, and you probably have an older version. I made a release elog276-2.exe for you. Try it and let me know. You can also just delete your cookies in Firefor and it should be fine, but it's better not being able to crash elog.
|
Sure I will try, but I cannot find the version you are talking about in the download section. Should I find it there or any other place? Thanks for quick feedback |
It's here.
|
Looks more stable, but it still quits. Sometimes just entering the logbook, sometimes when I hit the config button. ==== Return ================================ <549 bytes of favicon.ico> TCP connection broken GET /nor/elog.rdf HTTP/1.1 Host: XXSERVERNAMEHEREXX:8091 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.0.11) Gecko/2 009060215 Firefox/3.0.11 (.NET CLR 3.5.30729) Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-gb,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Cookie: elmode=Summary and just quits Strange |
Ah, the GET /nor/elog.rdf gave me somt hint: Your Firefox browser checks the RSS feed of elog regularly. If the logbook is empty, the routing producing the elog.rdf file went into some kind of infinite loop, but this only happens on an empty logbook. If fixed this and updated the 276-2 file just now, so try again. |
|