ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68632
|
Tue Jun 20 14:32:29 2017 |
| Niklas Hoglund | niklas@hoglund.pp.se | Bug report | Windows | 3.1.3 | my elogd crashes when editing the configuration |
Hi,
my elogd crashes sometimes when I click on the "Change config" button. What info should I collect more than below/attached?
In windows EventViewer I see this printouts:
###
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-06-20T12:25:30.000000000Z" />
<EventRecordID>28059</EventRecordID>
<Channel>Application</Channel>
<Computer>NIKLAS</Computer>
<Security />
</System>
- <EventData>
<Data>108889037262</Data>
<Data>1</Data>
<Data>APPCRASH</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>elogd.exe</Data>
<Data>0.0.0.0</Data>
<Data>58f9c864</Data>
<Data>elogd.exe</Data>
<Data>0.0.0.0</Data>
<Data>58f9c864</Data>
<Data>c0000005</Data>
<Data>00064eea</Data>
<Data />
<Data />
<Data>C:\Users\hognik\AppData\Local\Temp\WER9155.tmp.WERInternalMetadata.xml</Data>
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_elogd.exe_9ef84f861b91d5afaf68864978184ca611e7a22a_d4f2c951_08bd38b0</Data>
<Data />
<Data>0</Data>
<Data>7232f1e4-55b3-11e7-826a-e4b3181bd6c1</Data>
<Data>0</Data>
<Data>94c2d6a18797708666faf33a7273855a</Data>
</EventData>
</Event>
###
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-06-20T12:24:47.000000000Z" />
<EventRecordID>28058</EventRecordID>
<Channel>Application</Channel>
<Computer>NIKLAS</Computer>
<Security />
</System>
- <EventData>
<Data>elogd.exe</Data>
<Data>0.0.0.0</Data>
<Data>58f9c864</Data>
<Data>elogd.exe</Data>
<Data>0.0.0.0</Data>
<Data>58f9c864</Data>
<Data>c0000005</Data>
<Data>00064eea</Data>
<Data>1568</Data>
<Data>01d2e9c028b88983</Data>
<Data>C:\Program Files (x86)\ELOG\elogd.exe</Data>
<Data>C:\Program Files (x86)\ELOG\elogd.exe</Data>
<Data>7232f1e4-55b3-11e7-826a-e4b3181bd6c1</Data>
<Data />
<Data />
</EventData>
</Event>
###
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-06-20T12:24:07.000000000Z" />
<EventRecordID>28057</EventRecordID>
<Channel>Application</Channel>
<Computer>NIKLAS</Computer>
<Security />
</System>
- <EventData>
<Data>108889037262</Data>
<Data>1</Data>
<Data>APPCRASH</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>elogd.exe</Data>
<Data>0.0.0.0</Data>
<Data>58f9c864</Data>
<Data>elogd.exe</Data>
<Data>0.0.0.0</Data>
<Data>58f9c864</Data>
<Data>c0000005</Data>
<Data>00064eea</Data>
<Data />
<Data />
<Data>C:\Users\hognik\AppData\Local\Temp\WERBE94.tmp.WERInternalMetadata.xml
C:\Users\hognik\AppData\Local\Temp\WERCA4D.tmp.appcompat.txt triagedump.dmp
C:\Users\hognik\AppData\Local\Temp\WERCB77.tmp.WERDataCollectionFailure.txt</Data>
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_elogd.exe_9ef84f861b91d5afaf68864978184ca611e7a22a_d4f2c951_0a4ff4e6</Data>
<Data />
<Data>0</Data>
<Data>5206c994-55b3-11e7-826a-e4b3181bd6c1</Data>
<Data>4104</Data>
<Data>94c2d6a18797708666faf33a7273855a</Data>
</EventData>
</Event>
###
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-06-20T12:23:53.000000000Z" />
<EventRecordID>28056</EventRecordID>
<Channel>Application</Channel>
<Computer>NIKLAS</Computer>
<Security />
</System>
- <EventData>
<Data>elogd.exe</Data>
<Data>0.0.0.0</Data>
<Data>58f9c864</Data>
<Data>elogd.exe</Data>
<Data>0.0.0.0</Data>
<Data>58f9c864</Data>
<Data>c0000005</Data>
<Data>00064eea</Data>
<Data>2338</Data>
<Data>01d2e9baf6174f0f</Data>
<Data>C:\Program Files (x86)\ELOG\elogd.exe</Data>
<Data>C:\Program Files (x86)\ELOG\elogd.exe</Data>
<Data>5206c994-55b3-11e7-826a-e4b3181bd6c1</Data>
<Data />
<Data />
</EventData>
</Event>
### |
Attachment 1: WindowsCrashFiles.zip
|
206
|
Fri Feb 7 18:38:56 2003 |
| Nick | nikc@cnic.com | Question | | | Lost features since upgrade to 2.3.0 |
Ive got 2 issues which I cant see to resolve I was wondering if anyone can
help.
Problem 1 - Since upgrading to version 2.3.0 I seem to have lost the some
functionality explained below. When i first log into my logbook (i only
have a single one) it defaults to the summary view and the first field is
one called Customer Name as opposed to # as i wanted the list sorted by
this field, the link for that logbook entry is no longer available on the
first field (being Customer Name) but only on the # field), however if you
use Summary threaded view the whole line is a link.
Is there a flag or setting to the make the first field a link?
Problem 2 - no matter what i try in the config file i cannot get elogd to
use stylesheets ive tried specifying and even editing and removing the
default.css style sheet i downloaded but it just seems to ignore its there.
Any help or advice ?????? |
215
|
Tue Feb 11 11:17:29 2003 |
| Nick | nikc@cnic.com | Question | | | Re: Lost features since upgrade to 2.3.0 |
> > > > Problem 2 - no matter what i try in the config file i cannot get
elogd
> to
> > > > use stylesheets ive tried specifying and even editing and removing
the
> > > > default.css style sheet i downloaded but it just seems to ignore its
> > there.
> >
> > I resolved this problem, many thanks for your help
>
> What happened. If you tell your initial problems, I can maybe put something
> into the docs so that others won't have it...
>
> - Stefan
I upgraded to version 2.3.0 the previous version didnt seem to work with
stylesheets, when you viewed the html source there was no stylesheet defined
in it.
Please see my other posts for feature requests.
Many Thanks - FANTASTIC program btw |
216
|
Tue Feb 11 11:26:03 2003 |
| Nick | nikc@cnic.com | Info | | | Feature request |
Can you consider implementing the following additions to the functionality
1) Subt on edit <attribute> = xyz
This would be fantastic for implementing version control so you can see who
has edited a posted or a db entry.
2) Have a SORT fieldname flag so you can decide which column to sort things
by on a display listing in conjunction to the display flags, it current
defaults to the # column and I find i am directly linking to a sorted
display
3) Have the elogd.conf track actual log entries people have changed
detailing date and time etc.
4) Ability to export contents of the log books to files on disk for backup
purposes as all data is contained within a single log file which causes
problem for command line searches.
Many thanks |
223
|
Tue Feb 18 08:07:10 2003 |
| Nick | nikc@cnic.com | | | | New Version |
I noticed the site has been updated as far as the documentation for 2.3.1,
however the latest version in the downloads section is 2.3.0, any other
places where I can get 2.3.1
Cheers |
67207
|
Thu Feb 23 16:23:10 2012 |
| Nicolas FRANCOIS | nicolas.francois@free.fr | Question | Linux | 2.5.2-1 | New user: problem with configuration (password file) |
Hi.
I'd like to use elog as a tool ta keep my notes, links, passwords... It's installed on my personal computer at home (Debian Squeeze), behind a Ip-Cop firewall, so I guess it won't be accessible from anywhere outside. But I'd like to protect the log with a password anyway. BTW, I had some hard time figuring out how to configure the different files for french (there was a problem with UTF8 mixing up with Latin1... I recoded the language file to UTF8 to solve it).
I followed the procedure described here, but I have a problem with second stage :
- I set Password file = elog.pwd in the elog.conf file (it's not elog.cfg on Debian...)
- I restart the daemon
- I try to login to http://localhost:8080/, and receive the message : "error opening the file elog.pwd"
I get this message even after :
- adding my user account to the elog group
- launching Epiphany as root
So I guess I have to create (how ???) the file elog.pwd, which, if I understand correctly, can be empty at the start... But where do I save it ?
Thank you for any help, and sorry if I'm a little confused. I had hard time figuring out where to find everything.
\bye |
67554
|
Fri Aug 30 13:27:56 2013 |
| Nicolas FRANCOIS | nicolas.francois@free.fr | Question | Linux | 2.9.2 | Packaging ELOG for Debian |
Hi.
I'd like to package ELOG for the new Debian. I'm a complete beginner in
this matter, but I spent some time configuring it for my desktop.
Could you help me do this (links to package maintainance, Elog tips,
security, former package maintainer...) ?
Thanks for any help.
--
Nicolas FRANCOIS | /\
http://nicolas.francois.free.fr | |__|
X--/\\
We are the Micro$oft. _\_V
Resistance is futile.
You will be assimilated. darthvader penguin
|
68177
|
Tue Nov 3 18:22:33 2015 |
| Nicola | nicolamori@aol.com | Info | Linux | 2.9.2 | WYSIWYG editor for Elog not working in Debian Jessie |
I suspect that this might be a Debian packaging issue; however no one replied to my help request on the Debian forums so I try posting the question also here. I insatlled Elog on my Debian Jessie machine, I can open it with a browser but when entering a new post just a simple plain text editing box is shown instead of the WYSIWYG editor, and no drag and drop area for attachments is shown. When I start the elog service with "systemctl start elog" I get this suspect message in the journal: "FCKedit NOT detected". Indeed, I see that the elog installation creates a symlink which I guess is supposed to point to the fckeditor installation, which nevertheless is missing:
root@static-3-080:/usr/share/elog/scripts# ll fckeditor
lrwxrwxrwx 1 root root 15 Oct 25 2014 fckeditor -> ../../fckeditor
root@static-3-080:/usr/share/elog/scripts# ll ../../fckeditor
ls: cannot access ../../fckeditor: No such file or directory
Is this a Deban misconfiguration or a bug in Elog? thanks |