| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
2277
|
Fri Jun 29 16:43:23 2007 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.5 | Re: Error sending Email via "XXX.XXX.XXX.XXX" |
| JJ Sheppard wrote: | | Any thing else I can try? |
Maybe advservices instead of advservices@XXXXX.XXX ? Just an idea. |
|
2278
|
Fri Jun 29 16:54:39 2007 |
| JJ Sheppard | jsheppard@tracstar.net | Question | Linux | 2.6.5 | Re: Error sending Email via "XXX.XXX.XXX.XXX" |
| Stefan Ritt wrote: |
| JJ Sheppard wrote: | | Any thing else I can try? |
Maybe advservices instead of advservices@XXXXX.XXX ? Just an idea. |
No luck, i am going to setup another account on a different box and try again.
I am having another issue. I am using "Preset Author = $long_name" to set the authors name automatically.
But I also don't want the user to change it so i added "Locked Attributes = Author".
The filed is locked but the name shows up on its own line above the "Fields marked with * are required"
As soon as I remove the "Locked Attributes = Author" it shows up correctly in the Author bar. |
|
2279
|
Fri Jun 29 16:57:41 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.5 | Re: Error sending Email via "XXX.XXX.XXX.XXX" |
| JJ Sheppard wrote: | | The filed is locked but the name shows up on its own line above the "Fields marked with * are required" |
I fixed that yesterday. Please upgrade to SVN revision 1873. |
|
2280
|
Fri Jun 29 17:59:54 2007 |
| JJ Sheppard | jsheppard@tracstar.net | Question | Linux | 2.6.5 | Re: Error sending Email via "XXX.XXX.XXX.XXX" |
| Stefan Ritt wrote: |
I fixed that yesterday. Please upgrade to SVN revision 1873. |
Thanks - That Fixed It!
I am still having the issue with the email, I have tried to accounts (i can get into through thunderbird and webmail just fine) and a different main server and several ways of the username.
I am kind of at a lost of what to do next. |
|
2281
|
Fri Jun 29 19:29:56 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.5 | Re: Error sending Email via "XXX.XXX.XXX.XXX" |
| JJ Sheppard wrote: |
| Stefan Ritt wrote: |
I fixed that yesterday. Please upgrade to SVN revision 1873. |
Thanks - That Fixed It!
I am still having the issue with the email, I have tried to accounts (i can get into through thunderbird and webmail just fine) and a different main server and several ways of the username.
I am kind of at a lost of what to do next. |
I'm also running out of ideas. You would have to use a network sniffer (like Ethereal) and compare the network traffic between Thunderbird/ELOG and the SMTP server. |
|
2282
|
Fri Jun 29 20:34:38 2007 |
| JJ Sheppard | jsheppard@tracstar.net | Question | Linux | 2.6.5 | Re: Error sending Email via "XXX.XXX.XXX.XXX" |
| Stefan Ritt wrote: |
I'm also running out of ideas. You would have to use a network sniffer (like Ethereal) and compare the network traffic between Thunderbird/ELOG and the SMTP server. |
For right now i moved it to the same server that the mail server is. It does not require to be auth as it is a trusted server. I am going to set up another one and keep playing with it. But at least it works now. |
|
2309
|
Wed Sep 5 01:09:00 2007 |
 | Nicole Ackerman | ackey@stanford.edu | Question | Linux | 2.6.5 | Synchronization Problems |
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?
Thanks!
-Nicole Ackerman |
|
2313
|
Fri Sep 7 22:31:10 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.5 | 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 |