I just ran into this little bug: I had defined a new logbook in my config file and suddenly got the message Attribute "Date" not allowed. While I did have several attributes starting with the word "Date" (e.g. "Date In Service", "Date Retired") I had no attribute "Date" in there. After some pondering and wildly commenting out lines, it finally dawned on me: I had used an attribute "ID" - which is also not allowed. However, it would be very helpful if the error message actually reflected that...  |
I have the following simple test logbook:
; General
List display = Edit, Hostname, OS, Size
Entries per page = 150
Quick filter = OS
Date Format = %d/%m/%Y
Summary Lines = 0
; Attributes
Attributes = Hostname, OS, CPU,Size
Required Attributes = Hostname
Sort Attributes = Hostname
; Message part: log is text only, but elog is allowed
Default encoding = 0
Allowed encoding = 2
For some strange reasons, I'm having problems with the "Size" attribute, which I have added later. If I start adding/editing entries, at some point, the "Size" attribute will stay at "0" and will not accept any further changes. I've tried to pare down the config to maybe find which statement could be causing this, but to no avail. The only thing I can say is taht id doesn not seem to happen if the configuration consist of the sole line
Attributes = Hostname, OS, CPU,Size
I'm quite puzzled as to what is going on here (the original problems stems from a more complicated logbook) - I'm not even 100% sure whether this happens due to a bug or not.
Regards,
Thomas |
When we set Fix text = 1, according to the syntax, this should prevent users from modifying the text field during an edit, but it looks like it is blocking access at both time of edit and creation, meaning you can never add anything to it. Is that the intended functionality? |
After I moved an item from one logbook to another one I cannot reply on this item anymore.
When the submit button is clicked it returns: Submit not allowed
This eLog server running Linux is sync'd with an server running Windows XP.
On the windows server the funcionality is working perfect(so no Submit is not allowed on a reply) |
We are trying to track down an issue where elogd just stops, and I cannot seem to find a cause.
In the logs, I see:
Dec 3 14:01:23 nissrv18a kernel: [419738.139675] elogd[32003]: segfault at 4 ip 00007f183b19b560 sp 00007fff79f5e278 error 4
in libc-2.10.1.so[7f183b119000+166000]
Any thoughts? |