ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 87 of 807

Not logged in

Find | Login | Help

New entries since:

Thu Jan 1 01:00:00 1970

Full | Summary | Threaded | Hide attachments

6451 Entries

Goto page Previous 1, 2, 3 ... 86, 87, 88 ... 805, 806, 807 Next

Mon Jan 12 05:33:04 2009

Re: Google Chrome issues

> > > > Any ideas? I run our ELOG on windows server.. maybe that has something to do with it.
> > > 
> > > I am running the server on kubuntu 8.x, and have the same issue with chrome 1.x.
> > > Is is possible the corporate elog server is running behind apache or in some
> > > other proxy config while the one you are having issues with is being connected
> > > to directly by chrome?
> >
> > It's good to know someone else has the issue, at least.  I'd like to find a publicly available elog server so 
> > that the elog developers could recreate the issue and thusly fix the issue.  Or at the very least send the broken 
> > URL to Google Chrome developers to see if it's a bug in the browser or not.
> 
> I just brought up the current head release of elog, and the problem is fixed. Looks like it 
> was some sort of cookie issue IIRC the log entry.
> 
> So build a new elogd and you should be all set.
> 
> - rouilj

Thanks.  I'll have to wait for someone else to build the win32 binary, as I'm not set up to compile it myself.

66146

Mon Jan 12 21:00:27 2009

Re: Google Chrome issues

> > > > > Any ideas? I run our ELOG on windows server.. maybe that has something to do with it.
> > > > 
> > > > I am running the server on kubuntu 8.x, and have the same issue with chrome 1.x.
> > > > Is is possible the corporate elog server is running behind apache or in some
> > > > other proxy config while the one you are having issues with is being connected
> > > > to directly by chrome?
> > >
> > > It's good to know someone else has the issue, at least.  I'd like to find a publicly available elog server so 
> > > that the elog developers could recreate the issue and thusly fix the issue.  Or at the very least send the broken 
> > > URL to Google Chrome developers to see if it's a bug in the browser or not.
> > 
> > I just brought up the current head release of elog, and the problem is fixed. Looks like it 
> > was some sort of cookie issue IIRC the log entry.
> > 
> > So build a new elogd and you should be all set.
> > 
> > - rouilj
> 
> Thanks.  I'll have to wait for someone else to build the win32 binary, as I'm not set up to compile it myself.

I installed the latest Windows build (didn't realize I missed a build in November), and it now works in Chrome.  Thanks!

66155

Tue Jan 20 15:09:54 2009

Top group causes: Internal error, no valid header!

Having "Top group" in a config-file for Windows will cause:

GET / HTTP/1.1
Host: eudr6j03j:8084
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.0.5) Gecko/20
08120122 Firefox/3.0.5
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: sv-se,sv;q=0.8,en-us;q=0.5,en;q=0.3
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: unm=mambrus; upwd=U2lzc2kx; urem=0
Cache-Control: max-age=0

Internal error, no valid header!

Removing "top group" makes elogd.exe work. The error is repeatable and the same config file works on the same version of Elog on Linux. Elog was compiled with Cygwin.

66156

Tue Jan 20 15:17:04 2009

Re: Top group causes: Internal error, no valid header!

Michael Ambrus wrote:

Having "Top group" in a config-file for Windows will cause:

Removing "top group" makes elogd.exe work. The error is repeatable and the same config file works on the same version of Elog on Linux. Elog was compiled with Cygwin.

Please supply your full configuration file for error analysis.

66157

Tue Jan 20 15:20:38 2009

Stack error when email notification is active

Stack error is caused when an entry is submitted in a e-mail notification enabled log when a new entry is submitted. This error does not happen on linux (same Elog version, same config file).

Please let me know if there is anything I can do to help.

-----------------------------2916890032591
Content-Disposition: form-data; name="attfile"; filename=""
Content-Type: application/octet-stream

-----------------------------2916890032591--

timezone: 0, offset: 0
6 [main] elogd 2816 _cygtls::handle_exceptions: Error while dumping state
(probably corrupted stack)
Segmentation fault (core dumped)

66158

Tue Jan 20 15:26:03 2009

Re: Top group causes: Internal error, no valid header!

Stefan Ritt wrote:

Michael Ambrus wrote:

Having "Top group" in a config-file for Windows will cause:

Removing "top group" makes elogd.exe work. The error is repeatable and the same config file works on the same version of Elog on Linux. Elog was compiled with Cygwin.

Please supply your full configuration file for error analysis.

File attached. SMTP password removed, otherwise as original.

Attachment 1: elogd.cfg

; Simple ELOG configuration for demonstration.

[global]
Group iSYS = ITodo, ITodo-v1.1, IBugZ
Group dSYS = DTodo, DBugZ
Group eSYS = ETodo, EBugZ
Group aSYS = ATodo, ABugZ
Group sSYS = STodo, SBugZ

Group Michael = work notes

Logbook Tabs = 1
port = 8084

;URL = https://kato.homelinux.org/elog-ambrmi09/
;SSL = 1
;Relative redirection = 1
URL = http://EUDR6J03J:8084

SMTP host = smtp.glocalnet.net
SMTP username = rhj764h@tninet.se
SMTP Password = XXXremovedXXX
Resolve host names = 1

;Top group Philips = iSYS, dSYS, eSYS, aSYS, sSYS
;Top group Private = Michael

Password file = philips.pwd
Admin user = mambrus
Self register = 1
Allow password change = 1

[global Philips]
Password file = philips.pwd
Admin user = mambrus
Self register = 1
Allow password change = 1

[global Private]
Password file = private.pwd
Admin user = mambrus
Self register = 1
Allow password change = 1

[global Isys]
Subdir = Isys

[global Dsys]
Subdir = Dsys

[global Esys]
Subdir = Esys

[global Asys]
Subdir = Asys

[global Ssys]
Subdir = Ssys

; 
==============================================================================
[work notes]
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, 
Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

; 
==============================================================================
[ITodo]
Theme = default
Comment = Todo list
Attributes = Subject, Version, Class, Priority, Severity, Confidential, 
Category, Submitter-Id, Assignee, Host
Show Attributes Edit = Subject, Version, Class, Priority, Severity, 
Confidential, Category, Submitter-Id, Assignee
ROptions Class = sw-architect, sw-algorithm, plattform
ROptions Priority = low, medium, high
ROptions Severity = non-critical, serious, critical
ROptions Confidential = no, yes
ROptions Version = 1.0, 1.1

Style Priority high= background-color:red
Style Priority medium= background-color:yellow
Style Priority low= background-color:green
Style Priority low= color:white

Link display = id, date


Options Category= Implement, Prove, Document, Integrate, Investigate
Preset Submitter-Id = $long_name<$user_email>
Options Assignee     = michael.ambrus@philips.com
Preset Assignee = $user_email
Subst Host = $remote_host

Extendable options = Category, Class, Submitter-Id, Assignee, Version 

Required Attributes = Class, Submitter-Id

Preset Priority = low
Preset Confidential = no

Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Class

; Email All = RISE@gmail.com
Use Email From = <elog@kato.homelinux.org>

[ITodo-v1.1]
; 
==============================================================================
Theme = default
Comment = Todo list
Attributes = Subject, Version, Class, Priority, Severity, Confidential, 
Category, Submitter-Id, Assignee, Host
Show Attributes Edit = Subject, Version, Class, Priority, Severity, 
Confidential, Category, Submitter-Id, Assignee
ROptions Class = sw-architect, sw-algorithm, plattform
ROptions Priority = low, medium, high
ROptions Severity = non-critical, serious, critical
ROptions Confidential = no, yes
ROptions Version = 1.0, 1.1

Style Priority high= background-color:red
Style Priority medium= background-color:yellow
Style Priority low= background-color:green
Style Priority low= color:white

Link display = id, date


Options Category= Implement, Prove, Document, Integrate, Investigate
Preset Submitter-Id = $long_name<$user_email>
Options Assignee     = michael.ambrus@philips.com
Preset Assignee = $user_email
Subst Host = $remote_host

Extendable options = Category, Class, Submitter-Id, Assignee, Version 

Required Attributes = Class, Submitter-Id

Preset Priority = low
Preset Confidential = no
Preset Version = 1.1

Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Class

; Email All = RISE@gmail.com
Use Email From = <elog@kato.homelinux.org>


; 
==============================================================================

[IBugZ]
Theme = default
Comment = Bug&Issue Tracker
Attributes = Synopsis, Class, Priority, Severity, Confidential, 
Category, Submitter-Id, Host
Show Attributes Edit = Synopsis, Class, Priority, Severity, 
Confidential, Category, Submitter-Id
ROptions Class = sw-bug, doc-bug, support, change-request, mistaken, 
duplicate
ROptions Priority = low, medium, high
ROptions Severity = non-critical, serious, critical
ROptions Confidential = no, yes

Options Category= Chores

Extendable options = Category, Submitter-Id 
Preset Submitter-Id = $long_name<$user_email>
Subst Host = $remote_host
Required Attributes = Class, Submitter-Id 

Preset Priority = low
Preset Confidential = no
Preset text = bugz_submit_tmplt.txt

Page Title = ELOG - $Class
Reverse sort = 1
Quick filter = Date, Class

;Email All = RISE@gmail.com
Use Email From = <elog@kato.homelinux.org>


; DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD

; 
==============================================================================

[DTodo]
Theme = default
Comment = Todo list
Attributes = Subject, Version, Class, Priority, Severity, Confidential, 
Category, Submitter-Id, Assignee, Host
Show Attributes Edit = Subject, Version, Class, Priority, Severity, 
Confidential, Category, Submitter-Id, Assignee
ROptions Class = sw-architect, sw-algorithm, plattform
ROptions Priority = low, medium, high
ROptions Severity = non-critical, serious, critical
ROptions Confidential = no, yes
ROptions Version = 0.1

Style Priority high= background-color:red
Style Priority medium= background-color:yellow
Style Priority low= background-color:green
Style Priority low= color:white

Link display = id, date


Options Category= Implement, Prove, Document, Integrate, Investigate
Preset Submitter-Id = $long_name<$user_email>
Options Assignee     = michael.ambrus@philips.com
Preset Assignee = $user_email
Subst Host = $remote_host

Extendable options = Category, Class, Submitter-Id, Assignee, Version 

Required Attributes = Class, Submitter-Id

Preset Priority = low
Preset Confidential = no

Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Class

; Email All = RISE@gmail.com
Use Email From = <elog@kato.homelinux.org>

; 
==============================================================================
[DBugZ]
Theme = default
Comment = Bug&Issue Tracker
Attributes = Synopsis, Class, Priority, Severity, Confidential, 
Category, Submitter-Id, Host
Show Attributes Edit = Synopsis, Class, Priority, Severity, 
Confidential, Category, Submitter-Id
ROptions Class = sw-bug, doc-bug, support, change-request, mistaken, 
duplicate
ROptions Priority = low, medium, high
ROptions Severity = non-critical, serious, critical
ROptions Confidential = no, yes

Options Category= Chores

Extendable options = Category, Submitter-Id 
Preset Submitter-Id = $long_name<$user_email>
Subst Host = $remote_host
Required Attributes = Class, Submitter-Id 

Preset Priority = low
Preset Confidential = no
Preset text = bugz_submit_tmplt.txt

Page Title = ELOG - $Class
Reverse sort = 1
Quick filter = Date, Class

;Email All = RISE@gmail.com
Use Email From = <elog@kato.homelinux.org>


; EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE

; 
==============================================================================
[ETodo]
Theme = default
Comment = Todo list
Attributes = Subject, Version, Class, Priority, Severity, Confidential, 
Category, Submitter-Id, Assignee, Host
Show Attributes Edit = Subject, Version, Class, Priority, Severity, 
Confidential, Category, Submitter-Id, Assignee
ROptions Class = sw-architect, sw-algorithm, plattform
ROptions Priority = low, medium, high
ROptions Severity = non-critical, serious, critical
ROptions Confidential = no, yes
ROptions Version = 0.1

Style Priority high= background-color:red
Style Priority medium= background-color:yellow
Style Priority low= background-color:green
Style Priority low= color:white

Link display = id, date

... 209 more lines ...

66159

Tue Jan 20 15:37:19 2009

Re: Stack error when email notification is active

Michael Ambrus wrote:

Stack error is caused when an entry is submitted in a e-mail notification enabled log when a new entry is submitted. This error does not happen on linux (same Elog version, same config file).

Please let me know if there is anything I can do to help.

Cygwin is not officially supported. Can you try the Windows binaries?

66160

Tue Jan 20 16:07:03 2009

Re: Stack error when email notification is active

Stefan Ritt wrote:

Michael Ambrus wrote:

Stack error is caused when an entry is submitted in a e-mail notification enabled log when a new entry is submitted. This error does not happen on linux (same Elog version, same config file).

Please let me know if there is anything I can do to help.

Cygwin is not officially supported. Can you try the Windows binaries?

Sorry, I didn't know there were any (I've not used Elog for years and I think Cygwin was the only way back then). Tried them now and they seem to work. At least no stack error is caused. I'm getting some other error, but I think it's the handshake with the SMTP. I'll validate it's OK until tomorrow.

Windows binaries also solved the issue with the "Top grop" in my other bug rapport.

Thanks for the help!

Goto page Previous 1, 2, 3 ... 86, 87, 88 ... 805, 806, 807 Next

ELOG V3.1.5-3fb85fa6