|
|
|
Demo
Discussion
|
|
Forum
Config Examples
Contributions
Vulnerabilities
|
| Discussion forum about ELOG |
Not logged in |
 |
|
|
|
|
|
Message ID: 2313
Entry time: Fri Sep 7 22:31:10 2007
In reply to: 2309
|
|
| Category: |
Question |
OS: |
Linux |
ELOG Version: |
2.6.5 |
|
| Subject: |
Re: Synchronization Problems |
|
|
| Nicole Ackerman wrote: | I'm currently running elog 2.6.5 on my (feisty ubuntu) laptop and desktop. I set up mirroring between the two which usually works, but occasionally I get an error (when sending from laptop to desktop) :
"Enty too long to display. Please increase TEXT_SIZE and recompile elogd."
When this happens my entry is shortened to 3 characters. This is frustrating as I have lost many important entries. I'm unsure why this is happening - they aren't the longest entries in my logbook (one was a one line linux command) and there doesn't seem to be anything "special" about the ones that do and do not sync. The last time I tried to sync I got this error on 3 entries and they appear to be corrupted - when I try to access them elogd stops responding.
On a presumably related note, every time I try to send an entry from my laptop to my desktop I get "Error sending local entry: Error transmitting message", though the entry has appeared to sync properly. I don't think I have ever had a problem transmitting from my desktop to my laptop.
Currently the only mirroring option I have added to my config file in on my laptop which is the IP of my desktop as the Mirror server.
I'm unsure what else I could post to help troubleshoot this problem - is it just something I've done wrong or that could be fixed with a reinstall?
|
I'm sorry for your trouble. The key to understand and fix this problem is reproducibility. Can you identify an entry which causes this error (of course back up the entry before trying). Then create a fresh logbook where you put only this entry. If you can reproduce the problem, can you send me that entry, together with your config files? Only if I can reproduce your problem, I can fix it.
Best regards,
Stefan |