ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 746 of 806

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6445 Entries

Goto page Previous 1, 2, 3 ... 745, 746, 747 ... 804, 805, 806 Next

Fri Nov 15 11:30:31 2013

Andreas Luedeke

andreas.luedeke@psi.ch

Question

Linux

V2.9.2-245

Re: Inconsistent and long load times

> We recently installed ELOG and it works pretty well, but the load times are rather inconsistent. Most of the time 
> it is very fast, but it also often hangs for around 5-10 seconds while loading. It seems to affect all parts of 
> the page that are returned at random, so sometimes the main html file will hang, sometimes the css file and 
> sometimes the images.
> 
> The hardware it is running on is nothing special, an older 3 GHz Celeron, but it should be fast enough. It is 
> running on Debian 7. 
> 
> Any ideas what the problem could be, or how I could investigate it further to find the bottleneck?

I'm not an expert in debugging web applications. Here are my two cent:
We once had a problem when we hosted very large logbooks (several 10 thousands of entries) that the server would run
out of real memory and was slowed down by swapping. Therefore my first idea would be to monitor the server: Is
the CPU load peaking? What happens with the memory consumption? Any other suspicious process running on the server?
But it could be as well a network or browser problem. Did you try different browsers?
Did you check the elogd log file?

67631

Mon Dec 2 09:27:35 2013

Andreas Luedeke

andreas.luedeke@psi.ch

Bug report

Windows

2.9.2

Re: Crash report involving propagate and replies

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?

Hi Stephen,

I've just checked that elogd can handle "Propagate Attributes" for more than 10 replies without crashing (I've attached my config, you can see if it works for you.)

Therefore it has to be something else in your configuration that causes this behaviour, or a combination of things.

Could you strip off the configuration further, that it contains the minimal content to cause elogd to crash? Or can you use a debugger on your system?

Cheers

Andreas

Attachment 1: elogd.cfg

[global]
port = 8080

[TestXmlImportOfDate]
Attributes = x
Type x = date
Propagate Attributes = x

67632

Mon Dec 2 09:58:42 2013

Andreas Luedeke

andreas.luedeke@psi.ch

Bug report

Windows

2.9.2

Re: Crash report involving propagate and replies

Stephen wrote:

Using Elog 2.9.2

Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.

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

Attachment 1: elogd.cfg

[global]
SMTP host = mail.psi.ch
Authentication = File
port = 443
SSL = 1
Allow passwordchange = 1
Self Register = 0

Logfile = /usr/local/elog/elog.log

[CSM Log]
; Main settings
Password file = /usr/local/elog/elogPw.txt
Theme = default
List Menu commands = New, Find, List, Config, Change password, Logout, Last Day


; E-mail


; Look and Feel
Use Lock = 1
Fix text = 0
Propagate Attributes = Status
Sort Attribute Options System = 1
Sort Attribute Options Sub-System = 1
List after submit = 1
Display mode = summary
Quote on reply = 1
Entries per page = 30
Refresh = 240
Default Encoding = 1
Quick filter = Date, Type, System, Sub-System, Status, subtext
Time format = %A, %B %d, %Y, %H:%M
Page Title = ELOG - $type
Reverse sort = 1
Restrict edit time = 24
ID Display  = $message id
Extendable options = System, Sub-System
Type Time of Event = datetime
Preset Time of Event = $date
List Display = ID, Time of Event, Author, Type, System, Sub-System, Status
Allow branching = 0
Reply String =    
Summary lines = 5
Prepend on reply = \nAdded on $date by $long_name\n\n



; Log Header
Preset Author = $long_name
Locked Attributes = Author
Preset on reply Author = $long_name
Required Attributes = Author, Type, System, Status, Time of Event
Preset on reply Time of Event = $date
Preset on edit Author = $long_name

Attributes = Time of Event, Author, Type, System, Sub-System, Status, 
;Notification
Options Type = Test1{1}, Test2{2}, Test3{3}, Test4{4}, Test5{5}
Style Type Shift Change = background-color:yellow

{5} Preset Status = Closed
Options Status = Open, Closed
Cell Style Status Closed  = background-color:#1f9400
Cell Style Status Open  = background-color:#a10000

; Event Time options
; Type Event Time = datetime
; Subst Event Time = $date



; Options
{1} Options System = Test


; Options
{2} Options System = Test


; Options
{3} Options System = Test


; Turnover
{5} MOptions System = Test
{5} MOptions Sub-System = Test

Attachment 2: elog.png

67634

Tue Dec 3 11:30:43 2013

Andreas Luedeke

andreas.luedeke@psi.ch

Bug report

Windows

2.9.2

Re: Crash report involving propagate and replies

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.

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 ;-)

67638

Mon Dec 16 11:16:33 2013

Andreas Luedeke

andreas.luedeke@psi.ch

Question

Linux

2.9.2

Re: How to property install?

Ryan Blakeslee wrote:

Hello,

I have followed the very simple steps on the Download page for checking out and compiling from GIT. That works perfect and there is no issue.

The problem I have is-- it is not clear to me where to put the 'elog' dir that I have after I 'make' and 'make install'. Or, is there an installer script afterwards that I run? I'm installing on Debian 7 and trying to upgrade from 2.5.2 (which was installed using apt-get.)

Hi Ryan,

as far as I remember the Debian package is not supported any more. The "make install" assumes Red-hat style installation directories (you can see it in elog/Makefile, all the installation directories are installed there).

I have no idea where Debian is supposed to install the binaries. But you should be able to use GNU "locate" to find the old files: "locate elog" and "locate elogd" should tell you where the old binaries had been installed.

Kind Regards, Andreas

67645

Mon Jan 6 10:32:43 2014

Andreas Luedeke

andreas.luedeke@psi.ch

Bug report

Windows

2.9.2

Re: Crash report involving propagate and replies

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.

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

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.

If you use the newly created "elogd", does that reproduce the former problem?

67654

Thu Jan 16 19:11:58 2014

Andreas Luedeke

andreas.luedeke@psi.ch

Question

Linux

2.9.2-2455

Re: Subject attribute in bold type - threaded display

Paolo wrote:

Hi all,

I am successfully using ELOG V2.9.2-2455 to manage several laboratory logs.

I am looking for a way, if possible, to format the subject attribute in bold type while in thread display.

I've used the following code

Display Subject = $subject

with no success, then I've tried

Subst Subject = $subject

again with no success. It seems that the tag is not iterpreted.

Have you any suggestion about this?

Thank you in advance.

Paolo

Hi Paolo,

you've made two little errors, one is partly driven by a bug in the documentation:

1st: If you want to use HTML tags in the display of attributes, you need to add "Allow HTML = 1" in the configuration.

2nd: The proper command is not "Display <attribute> = ..." but "Change <attribute> = ...". It is actually correct in the documentation (Change <attribute> = <string>), but the example is wrong (Display Telephone = <a href="http://any.company.com/telbook.cgi?search=$Name">$Name's telephone number</a>)

Stefan should fix the example in https://midas.psi.ch/elog/config.html#attrib some day.

Cheers

Andreas

67670

Mon Mar 3 15:42:29 2014

Andreas Luedeke

andreas.luedeke@psi.ch

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.

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.

Goto page Previous 1, 2, 3 ... 745, 746, 747 ... 804, 805, 806 Next

ELOG V3.1.5-3fb85fa6