Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 648 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
New entries since:Thu Jan 1 01:00:00 1970
 Full | Summary | Threaded | Hide attachments  Show all entries    6460 Entries 
Goto page Previous  1, 2, 3 ... 647, 648, 649 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  2052   Wed Nov 8 13:07:31 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportOther2.6.2-1714SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode

Steve Jones wrote:
Very weird. No, I did not try an absolute path - but I did notice the attempt to "cd /" in the truss output. In fact, it was immediately after that "cd /" test that things appeared to start not working - basically, elogd could not find anything.


The "cd /" is mandatory for daemons according to Unix standards. If a daemon gets started on an NFS subtree, that subtree cannot be unmounted anymore. Therefor it's required that all daemons cd to root, such that the NFS subtree can freely be mounted and unmounted. I therefore use absolute paths in all my statements of elogd.cfg.
  2054   Wed Nov 8 15:39:42 2006 Reply deletoillexavier.deletoille@synchrotron-soleil.frBug reportWindows2.6.2-1746Re: checkbox

Stefan Ritt wrote:

deletoille wrote:
I found a small Bug when I create an entry. I activate a checkbox (attachement1) but when I upload a file, the activation disappears (attachement 2). I have to activate again the checkbox.
Is it something I can do?


I tried with V2.6.2-1741 and the problem was not there. It was fixed some time ago, so it should have worked in 1723 as well. Can you try the minimal example coming with the distribution, just by adding one MOptions attribute, like:
[global]
port = 8080

[demo]
Attributes = Author, Type
MOptions Type = Routine, Software Installation, Problem Fixed, Configuration, Other

and see if it work there? If it works correctly there but not with your config file, please send me your config file and I will try to reproduce the problem.



You're right it works
It must be in my programming method
I share you my config file.
Thanks for your help
Attachment 1: Elog_08_11_06.doc
  2109   Fri Jan 12 15:28:46 2007 Warning An Thaithaithan@gmx.deBug reportWindows2.6.3-1776ELOG Crash by many email address
Hello,

when I try to set above 112 email addresses in
"Email All = ..."
the Elog service will crash with the error ntdll.dll or memory addresses x0000000.
This problem does not happen when I reduce the number of email addresses.

Have you had the same problem?
Attachment 1: crash.PNG
crash.PNG
  2114   Tue Jan 16 23:01:30 2007 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.6.3-1776Re: ELOG Crash by many email address

An Thai wrote:
Hello,

when I try to set above 112 email addresses in
"Email All = ..."
the Elog service will crash with the error ntdll.dll or memory addresses x0000000.
This problem does not happen when I reduce the number of email addresses.

Have you had the same problem?


I fixed that crash in the current version, but there is actually a limit of 100 email addresses. So anyhow you won't get the 12 ones above 100. I will try to increase that limit in the next version of elog.
  2123   Tue Feb 6 18:19:57 2007 Reply Grant Jeffcotegrant@jeffcote.orgBug reportWindows2.6.3-1776Re: ELOG Crash by many email address

Stefan Ritt wrote:

An Thai wrote:
Hello,

when I try to set above 112 email addresses in
"Email All = ..."
the Elog service will crash with the error ntdll.dll or memory addresses x0000000.
This problem does not happen when I reduce the number of email addresses.

Have you had the same problem?


I fixed that crash in the current version, but there is actually a limit of 100 email addresses. So anyhow you won't get the 12 ones above 100. I will try to increase that limit in the next version of elog.


Hi Stefan,

I'm also having a problem in the latest version with Elog crashing with multiple email addresses.
I am using 'MOptions' for email list selection using the execute shell script to send a predefined list (ie. the email list is in a text file not in the Elog config).
It seems when the list contains exactly 9 addresses it causes Elog to crash with a failure similar to An's, any less or any more and they are sent fine? Also when certain combinations of multiple list selections are made the Elog process will also crash? I am running the Elog process as an application (ie. not as a service, as per An's workaround) as it's the only way I can get the -x switch to work with Windows, this means the Elog daemon has to be manually restarted. Running WinXP SP2.
Any suggestions?

Thx
  2148   Thu Mar 1 15:55:52 2007 Warning Robert-Jan SchrijversRobert-Jan.Schrijvers@isoft.nlBug reportWindowsV2.6.3-176Bug
when i was editting my Admin file, by mistake i typed the next line:

[a}Options Sessies = p-zis-pr1{1}, p-szh-pro{2}, p-dia-pro{3}, a-zis-ac1{1}, a-zis-ac2{2}, a-dia-acc{3}, ---------------------, Anders
{b} Options Sessies = FSC Pro{4}, FSC Acc{4}, Risc/Bus/Sms Pro{5}, Risc/Bus/Sms Acc{5}, ---------------------, Anders
{c} Options Sessies = BAO, BEH, BAOMPSO, BEHMPSO, Demonstrator, AFS, PTG, BSN, ---------------------, Anders
{d} Options Sessies = Wijziging, Storing

the next thing happened was that eLog created a new log which wasn't editable at all, the only thing i could do was deleting it (i created a monster...;-)
The first line/rule with the [ become the title, all other entries in the Admin file were used as a new Admin file.
  2150   Thu Mar 1 22:19:22 2007 Reply Stefan Rittstefan.ritt@psi.chBug reportWindowsV2.6.3-176Re: Bug

Robert-Jan Schrijvers wrote:
when i was editting my Admin file, by mistake i typed the next line:

[a}Options Sessies = p-zis-pr1{1}, p-szh-pro{2}, p-dia-pro{3}, a-zis-ac1{1}, a-zis-ac2{2}, a-dia-acc{3}, ---------------------, Anders
{b} Options Sessies = FSC Pro{4}, FSC Acc{4}, Risc/Bus/Sms Pro{5}, Risc/Bus/Sms Acc{5}, ---------------------, Anders
{c} Options Sessies = BAO, BEH, BAOMPSO, BEHMPSO, Demonstrator, AFS, PTG, BSN, ---------------------, Anders
{d} Options Sessies = Wijziging, Storing

the next thing happened was that eLog created a new log which wasn't editable at all, the only thing i could do was deleting it (i created a monster...;-)
The first line/rule with the [ become the title, all other entries in the Admin file were used as a new Admin file.


You shot yourself in the foot Wink

I agree that a clever syntax check on the config file would be nice, but it's very hard to imagine how many mistakes humans (including myself) can do, I would probably never catch all possible wrong cases. Giving my limited time, I will more work on new features and kindly ask you to be a bit careful in what you enter. I'm absolutely sure you will never make this mistake again Big grin
  2157   Tue Mar 6 16:59:13 2007 Disagree T. Ribbrockemgaron@gmx.netBug reportLinux2.6.4Upgrade to 2.6.4 broke quick search
Hi!

I just went from 2.6.1 to 2.6.4 and since the upgrade, the quick search drop-down menus no longer work. I can select an attribute, but when I do so, I only get an empty page with the following message:
Attachment #0 of entry #0 not found
Please use your browser's back button to go back

When I do go back, the attribute I selected is still selected, but all entries are listed. With 2.6.1, this worked like a charm.

Any idea?

Thanks in advance,

Thomas
Goto page Previous  1, 2, 3 ... 647, 648, 649 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6