| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
507
|
Wed Mar 24 17:48:28 2004 |
 | Charles Duncan | Charles@YorkU.CA | Question | Linux | 2.5.1-1 Debian Linux | Elog Utility |
I am trying to use the Elog Utility to import a few thousand entries. So
far I have run into a few problems.
a) Cannot get elog utility to speak to elogd on port 8080. Even though I
use the -p 8080 option with elog. I was able to get it to work when I
moved my server to port 80.
b) I cannot get elog to work with and attributes or logbooks that contain
spaces. Please refer the the following example:
elog -v -h scotland.ccs.yorku.ca -p 80 -a "Station Number"="CC001" -a "Mac
Address"="000874fdc895" -a "Hostname"="cc001.cnscommons.yorku.ca" -a "IP
Address"="10.6.10.52" -a "Manufacturer"="Dell" -a "Model Line"="Optiplex" -
a "Model Number"="GX270" -a "Monitor Manufacturer"="Dell" -a "Monitor
Model"="E151FP" -a "Memory"="512MB" -a "CPU Speed"="2.6GHz" -a "Hard
Drive"="40GB" -a "Service Count"="-" -l WSC2 -u charles xxxxx "DD/MM/YY:
Change Description"
This line executes fine. Except only Hostname, Manufacturer, Memory and
text are populated in the record. All the rest of the fields are blank.
c) the only way I was able to get the transaction to work was by reducing
the size of the log book to a single word (ie WSC2).
Do I have to reduce all my attributes to single words? Or am I missing
something simple to use as a delimiter for entry??
Thanks in advance
-Charles- |
|
68686
|
Fri Sep 15 00:56:38 2017 |
 | Alan Grant | agrant@winnipeg.ca | Question | Linux | 3.1.2 | Elog System Requirements |
In response to an elog-hang issue I've been having on the Windows platform, I am building a new Unbuntu 14 TLS VM machine to host the identical configuration so that I can more easily debug when the hang happens again. I don't mind beefing up the hardware resources to either eliminiate that as a factor or resolve the problem. I'll have a higher end CPU to deal with 20 to 50 clients doing searches through the data (since the elog configuration currently does not provide a setting to limit how far back it can search with Quick Filters - pretty please add this basic setting!), but the main question I have now is what is a good amount of memory to add to the VM? I suspect even with 30 concurrent searches going CPU power will have more impact than memory in the case of elog. Can someone please confirm my suspicion and also recommend a suitable amount of memory I should install? My data volume is about 25 MB, all textual (no attachmemts), and the number of daily files goes back about 5 years. Any other tips for the build is very welcome. |
|
737
|
Fri Oct 15 07:59:35 2004 |
| Geo Geo | gorilla_geo@yahoo.com | Bug report | Windows | 2.5.4.5 | Elog Service Terminated |
Hi
I have a problem here which the ELOG service get terminated unexpectedly
on the Windows Server.
Is there any way to debug this problem ?
I am using the latest version of Elog and i tried the 2.5.3 version too
have this problem
Thanks! |
|
735
|
Fri Oct 15 07:59:35 2004 |
| Geo Geo | gorilla_geo@yahoo.com | Bug report | Windows | 2.5.4.5 | Elog Service Terminated |
Hi
I have a problem here which the ELOG service get terminated unexpectedly
on the Windows Server.
Is there any way to debug this problem ?
I am using the latest version of Elog and i tried the 2.5.3 version too
have this problem
Thanks! |
|
68792
|
Fri May 4 14:43:35 2018 |
| Joseph McKenna | joseph.mckenna@cern.ch | Bug report | Linux | 2.9.2 | Elog ID entry bug at >99999 entries |
We have a possible bug with elog that the ID for an elog entry at over 99,999 entires reads as 10,000...
68792/1 Illistrates the problem, we use this ID often to cross reference from out datalog...
Is this a know bug we can find a fix for? We are using: elogd 2.9.2 built Jul 14 2015, 18:58:06 revision |
| Attachment 1: sequencer_events.png
|
|
|
66449
|
Mon Jul 20 09:26:41 2009 |
| lance | lance1.hayward@yahoo.com | Bug report | Windows | 2.7.6 | Elog Crashes |
Stefan,
Our log is crashing on a regular basis and I have been unable to identify the reason. Now the if the log crashes that is not a major problem however when you try to stop the daemon from the services it fails to stop. This means that the daemon cannot be restarted. The only way then is to start killing processes. This is not something I want none experienced guys to do.
Looking at the processes is look like the elogd.exe is still running and doesn’t die when you try to stop the daemon service.
I checked the times it was crashing with events in the elog logfiles but there was nothing actually happening at these times. It seems something is causing it to just hang.
I have attached the eventlog files for you if you have any ideas I would appreciate them.
I have not run the log in verbose mode as I have thus far been unable to redirect the output of the screen in order to see what is happening. If you have any tips on how to redirect the output I would save the file for off line analysis. Our log is used 24/7 therefore it is critical that it be kept running so if I was to run it with the –v option the guys would have to restart it and I would lose the data.
Any help is much appreciated
Regards,
Lance |
| Attachment 1: Elog_crash_events.doc
|
|
67044
|
Sun Apr 10 01:49:01 2011 |
| John Rouillard | rouilj+elog@cs.umb.edu | Bug report | Linux | 2.9.0 | Elog 2.9.0 buffer overflow crash bug ubuntu linux |
When running openvas (a nessus fork) against elog 2.9.0 I provoked the following crash:
Apr 9 17:32:06 unixland elogd[1300]: POST / HTTP/1.0#015#012Host: unixland.home
#015#012Content-Length: -800#015#012#015#012XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Apr 9 17:32:06 unixland kernel: [664894.491242] elogd[1300]: segfault at b7713d
2e ip 080b6956 sp bf8d5ea0 error 4 in elogd[8048000+96000]
openvas reports that it was testing for CVE-2002-1212 when the crash occurred.
Startup info:
Apr 9 19:35:54 unixland elogd[21584]: elogd 2.9.0 built Apr 9 2011, 17:49:08
Apr 9 19:35:54 unixland elogd[21584]: revision 2411
-- rouilj |
|
253
|
Thu Mar 20 21:07:09 2003 |
 | djek | djek@nospam.invalid | Bug report | | | Elog 2.3.3, problems of 2.3.2 only partly solved |
After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
as stylesheets, images or passwordfiles.
Cannot open file /usr/local/elogdata/logbooks/djeks/password!
oops? |