ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67623
|
Fri Nov 15 23:02:03 2013 |
| Hung Dao | hungtdao@yahoo.com | Question | Windows | 2.9.2 | Re: Unwanted characters showing when using Bottom Text Login to a html file |
Andreas Luedeke wrote: |
Hung Dao wrote: |
Andreas Luedeke wrote: |
Hung Dao wrote: |
When using Bottom Text Login to a html file showing some unwanted characters. Also, the ELOG Version is longer displayed. Bottom Text Login = example.htm Attached are bottomtextlogin.jpg which shows the characters on the left and example.htm which I used. |
I have a possible explanation for this problem, but it is just guess work. If I'm right, then just download the latest ELOG version and it will work properly again.
- You've downloaded an elog version from git, which still contained the line 12 in elogd.c: char svn_revision[] = "$Id$";
- Since you did checkout from git, the $Id$ was not substituted.
- ELOG trys to extract the version by this: rsprintf
("<center><a class=\"bottomlink\" title=\"%s\" href=\"https://midas.psi.ch/elog/\">ELOG V%s-%d</a></center>",
loc("Goto ELOG home page"), VERSION, atoi(svn_revision + 13));
- svn_revision + 13 is pointing into the void. Still I would have expected that you get a number as a result.
My advice: download again and retry.
⇄
English (auto-detected) » English
|
I have downloaded a latest version. It has displayed the new version as ELOG V2.9.2-bac715d where seems defined in GIT_REVISION as I guess. Then I set Bottom Text Login to a html file, it still shows those unwanted characters.
|
⇄
English (auto-detected) » English
Okay, why don't you just remove the unwanted characters from the html file? Because the attached file contains exactly those characters.
|
Yes, unwanted characters are in my file. In fact, they are not visible under some editor. So, I have found a reference from this site http://www.ventrino.com/blog/60/2008/07/three-little-characters-i%C2%BB%C2%BF-designed-to-make-your-life-hell/ about how to remove them. Basically, file's properties has to set to either ASCII or Encode as UTF-8 without BOM. Thanks. |
67643
|
Fri Jan 3 21:33:40 2014 |
| Hung Dao | hungtdao@yahoo.com | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
Andreas Luedeke wrote: |
Stephen wrote:
|
Andreas Luedeke wrote:
|
Stephen wrote:
|
Using Elog 2.9.2
Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.
I have an attribute "Status" that can be toggled between "Open" and "Closed" and that propagates all replies. On the 10th reply the application crashed, this is repeatable 100% of the time. Without the propagate option everything works fine.
Attached is my config file parsed down.
Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?
|
Bad news: I cannot reproduce your problem with the latest elog version 2.9.2 (e7ba466) on scientific linux 6.0
I had to remove some lines in your config, since I don't have your password file.
I'll attach the config file, please have a look if it crashes on your server with the latest elogd version.
Andreas
|
Thanks for the reply, I tried the very basic cfg and the second one you offered. Running 2.9.2-2475 on a Windows 2008 R2 V.Server, I still crashed on attempt 10 never fail. Windows detects the failure and gives this message:
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: 0xc00000fd
Fault offset: 0x00065127
Faulting process id: 0x340
Faulting application start time: 0x01ceefa87fea0aea
Faulting application path: D:\ELOG\elogd.exe
Faulting module path: D:\ELOG\elogd.exe
Report Id: ceccc3da-5b9b-11e3-80f1-5ac95c924b0b
It only happens when propagate is on, I have to be missing some security setting in Windows maybe? Don't know if that helped at all, but I'm out of ideas.
|
Can you compile elog? Then I would suggest that you download the latest version from GIT an recompile it. You'll find help for that here: https://midas.psi.ch/elog/download.html
I have no experience with compilation on Windows (I try not to touch it, and if I have to I use a long stick ;-)
⇄
English (auto-detected) » English
|
I have been able to compile Elogd successfully in Windows with Visual Studio 2010 but not with Elog. Attached are errors, it complaint about buffer[i] type char * being assigned type void *. If anyone has been successful compile the elog, please give me a hint. Thanks. |
Attachment 1: error1.jpg
|
|
Attachment 2: error2.jpg
|
|
Attachment 3: error3.jpg
|
|
67647
|
Sun Jan 12 04:48:12 2014 |
| Hung Dao | hungtdao@yahoo.com | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
Andreas Luedeke wrote: |
Hung Dao wrote: |
Andreas Luedeke wrote: |
Stephen wrote:
|
Andreas Luedeke wrote:
|
Stephen wrote:
|
Using Elog 2.9.2
Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.
I have an attribute "Status" that can be toggled between "Open" and "Closed" and that propagates all replies. On the 10th reply the application crashed, this is repeatable 100% of the time. Without the propagate option everything works fine.
Attached is my config file parsed down.
Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?
|
Bad news: I cannot reproduce your problem with the latest elog version 2.9.2 (e7ba466) on scientific linux 6.0
I had to remove some lines in your config, since I don't have your password file.
I'll attach the config file, please have a look if it crashes on your server with the latest elogd version.
Andreas
|
Thanks for the reply, I tried the very basic cfg and the second one you offered. Running 2.9.2-2475 on a Windows 2008 R2 V.Server, I still crashed on attempt 10 never fail. Windows detects the failure and gives this message:
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: 0xc00000fd
Fault offset: 0x00065127
Faulting process id: 0x340
Faulting application start time: 0x01ceefa87fea0aea
Faulting application path: D:\ELOG\elogd.exe
Faulting module path: D:\ELOG\elogd.exe
Report Id: ceccc3da-5b9b-11e3-80f1-5ac95c924b0b
It only happens when propagate is on, I have to be missing some security setting in Windows maybe? Don't know if that helped at all, but I'm out of ideas.
|
Can you compile elog? Then I would suggest that you download the latest version from GIT an recompile it. You'll find help for that here: https://midas.psi.ch/elog/download.html
I have no experience with compilation on Windows (I try not to touch it, and if I have to I use a long stick ;-)
⇄
English (auto-detected) » English
|
I have been able to compile Elogd successfully in Windows with Visual Studio 2010 but not with Elog. Attached are errors, it complaint about buffer[i] type char * being assigned type void *. If anyone has been successful compile the elog, please give me a hint. Thanks.
|
You don't need "elog" to run the logbook, the executable "elog" is only needed to create entries without the web interface. Stefan should adapt "elog.c" some day to be compatible with the default switches of modern, paranoid compilers; but for the moment you can ignore this.
⇄
English (auto-detected) » English
If you use the newly created "elogd", does that reproduce the former problem?
|
I don't see it has crashed when testing your cfg. However, one thing I must do is to comment out the alarm_handler function in order to compile the elogd successfully. Otherwise, it shows an undefined alarm, see in the 2nd attachment. Although it did not crash as tested with your cfg, I have experienced the new version sometimes crashed on our system but then it self restarted (different scenario since my cfg does not use Propagate. I have not been able to narrow down yet. |
Attachment 1: test.jpg
|
|
Attachment 2: test2.jpg
|
|
67661
|
Mon Feb 3 22:45:10 2014 |
| Hung Dao | hungtdao@yahoo.com | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
Stephen wrote: |
Stefan Ritt wrote: |
Stephen wrote: |
Using Elog 2.9.2
Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.
I have an attribute "Status" that can be toggled between "Open" and "Closed" and that propagates all replies. On the 10th reply the application crashed, this is repeatable 100% of the time. Without the propagate option everything works fine.
Attached is my config file parsed down.
Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?
|
Was a tricky problem. When you use "Propagate Attributes", a routine is called inside elogd which recursively goes through all replies. It uses quite some memory for temporary storage of attributes and attachments. So after a certain time you get a stack overflow since you run out of memory. Since the stack size is different under different operating systems, it was hard for me to reproduce it initially. Now I use some different memory (dynamic heap instead stack) which should fix the problem. Can you pull from GIT and give it a try?
/Stefan
|
Unfortunately, I am a little outside of my element when trying to compile it. I will ask around and see if someone here could give me a hand. Thanks for looking into this for me.
PS. If anyone else has managed to compile this could you give me a hand =)
|
I was able to manage and compile the latest code from GIT. It runs fine so far. Just a hint, in order to compile successfully, there are some steps that you may need to modify your header file depend on how you store your mxml, krb5, OpenSSL files and directories. |
1710
|
Wed Feb 22 13:49:03 2006 |
| Holger Mundhahs | holger.mundhahs@vtg-rail.com | Question | Windows | 2.6.1-1653 | List view for CHANGE attributes | Hello @all,
I've tried to implement an attribute with Change. The detail view works well,
but in the list view the field is empty (see screen shots). Can somebody help me?
Regards
Holger
LOGBOOK CONFIGURATION:
Comment = DEMO
Attributes = Admin, Hostname, IP-Adresse, Funktion, RIB-Hostname, RIB-IP, RIB-Admin
Change RIB-Admin = <a href="https://$RIB-Hostname/" target="_new">$Hostname RIB-Board: $RIB-Hostname</a>
Preset Admin = DEMO
Locked Attributes = Admin, RIB-Admin
Display search = ID, Date, Admin, Hostname, RIB-Admin
List Display = ID, Edit, Date, Admin, Hostname, IP-Adresse, RIB-Admin
Link Display = ID
Page Title = ELOG - $subject
Quick filter = Date, Admin
Default encoding = 1
Suppress default = 3
Show text = 0
Summary lines = 0
Sort Attributes = IP-Adresse |
Attachment 1: DetailView.jpg
|
|
Attachment 2: ListView.jpg
|
|
1712
|
Wed Feb 22 15:47:45 2006 |
| Holger Mundhahs | holger.mundhahs@vtg-rail.com | Question | Windows | 2.6.1-1653 | Re: List view for CHANGE attributes | Hello Mr. Ritt,
6 min 5 sek to answer - great. 
Thanks & regards
Holger
Stefan Ritt wrote: | > Hello @all,
> I've tried to implement an attribute with Change. The detail view works well,
> but in the list view the field is empty (see screen shots). Can somebody help me?
For the list view, you need an additional
List Change RIB-Admin = ...
Some people want different modes for the list view and the detail view, that's why there are two options. |
|
1713
|
Wed Feb 22 16:27:39 2006 |
| Holger Mundhahs | holger.mundhahs@vtg-rail.com | Question | Windows | V2.6.1-165 | How to setup Change attributes in detail view/edit mode ? | Hello @all,
because I've got a very quick response on my 1st question regarding
"Change attributes" here is anonther one:
I've defined 2 attributes with "Change attribute" / "List Change attribute" (see configuration).
Because this values are build on other attributes I want to hide these attributes in
NEW / EDIT mode. How is this possible?
Regards
Holger
---
CONFIGURATION:
Comment = DEMO
Attributes = Admin, Hostname, IP-Adresse, Funktion, RIB Hostname, RIB IP, RIB http, ELOGs http
Change RIB http = <a href="https://$RIB Hostname/" target="_new">RIB-Board</a>
List Change RIB http = <a href="https://$RIB Hostname/" target="_new">RIB-Board</a>
Change ELOGs http = <a href="http://elogs/$Hostname/">ELOG</a>
List Change ELOGs http = <a href="http://elogs/$Hostname/">ELOG</a>
Preset Admin = DEMO
Locked Attributes = Admin, RIB http, ELOGs http
Fixed Attributes Edit = RIB http, ELOGs http
Display search = ID, Date, Admin, Hostname, RIB http, ELOGs http
List Display = ID, Date, Admin, Hostname, RIB http, ELOGs http
Link Display = ID |
Attachment 1: DetailView2.jpg
|
|
Attachment 2: EditView2.jpg
|
|
Attachment 3: ListView2.jpg
|
|
1714
|
Wed Feb 22 19:04:19 2006 |
| Holger Mundhahs | holger.mundhahs@vtg-rail.com | Question | Windows | 2.6.1 | How to build own/customized selection page? | Hello @all,
with "Selection page = ..." I can link to an self defined selection page for the systems.
As I understand it must be an static page, or how is it possible to define the content based
on the available logbooks or groups?
Regards
Holger |
|