| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68550
|
Wed Jan 18 05:25:44 2017 |
 | Luca | rimbalzina@gmail.com | Question | Linux | ELOG V3.1.1- | "No SMTP host defined in [global] section of configuration file" | Hi,
I started re-using after a month an elog on my linux machine and, without any apparent reason since I did not used the machine at all in the last month, every time I try to submit a post I get the following error
"No SMTP host defined in [global] section of configuration file".
The weird thing is that today I created a new logbook using the previous one as a template and, on the new one, I can post without problem (although the configuration is identical).
Do you know what could be causing this?
Thnaks
R |
|
68549
|
Sat Jan 14 08:27:42 2017 |
 | Andreas Warburton | awarburt@physics.mcgill.ca | Bug report | Linux | V3.1.2 | Re: elogd crashes during SSL Mirror operations involving attachments | For the time being, I am deeming ELOG 3.1.2 unusable with https (SSL = 1) functionality on my "Debian GNU/Linux 7 (wheezy)" server with "OpenSSL 1.0.1t", due to the described apparent issues with SSL. Reverting to http (SSL = 0) brings back my ability to upload attachments and synchronize with a remote elogd running on a MacOS laptop.
Interestingly, my records indicate that I suffered a problem with very similar symptoms back in 2011, with version 2.8.0. The problem at that time, which is acknowledged in the Changelog as "Fixed bug with SSL connection shutdown", got fixed in version 2.9.0. Perhaps, when the "Replaced insecure SSLv23 with TLSv1 method" change was implemented for version 3.0.0, a similar issue was (re-)introduced?
It would of course be best if this issue were resolvable soon, due to the security vulnerabilities of http versus https. Thank you in advance for any efforts!
Best regards,
Andreas Warburton
| Andreas Warburton wrote: |
|
When I switch from SSL = 1 to SSL = 0 and I use http:// instead of https://, the ability to upload attachments to logbook entries returns. With both Chrome and Safari browsers, with SSL = 1 the file upload hangs after only a small percentage of the file has been uploaded. I ran the following openssl diagnostic on my elogd port. Would anyone have advice on what might be causing such errors?
tapajo [/usr/local/elog/elog-latest] openssl s_client -connect elog.hep.xxx.xx:80xx -state -nbio | grep "^SSL"
SSL_connect:before/connect initialization
SSL_connect:SSLv2/v3 write client hello A
SSL_connect:error in SSLv2/v3 read server hello A
SSL_connect:unknown state
depth=0 C = EU, ST = SomeState, L = SomeCity, O = SomeOranization, OU = SomeOrganizationUnit, CN = localhost
verify error:num=18:self signed certificate
verify return:1
depth=0 C = EU, ST = SomeState, L = SomeCity, O = SomeOranization, OU = SomeOrganizationUnit, CN = localhost
verify return:1
SSL_connect:unknown state
SSL_connect:unknown state
SSL_connect:unknown state
SSL_connect:unknown state
SSL_connect:unknown state
SSL_connect:unknown state
SSL_connect:error in unknown state
SSL_connect:error in unknown state
SSL_connect:unknown state
SSL_connect:unknown state
SSL handshake has read 1733 bytes and written 871 bytes
SSL-Session:
SSL3 alert read:warning:close notify
SSL3 alert write:warning:close notify
| Andreas Warburton wrote: |
|
The attached screenshot shows the behaviour after doing a synchronization (with Mirror simulate = 1) following first having ensured that the local (Mac) and remote (linux) ELOGs initially showed "All entries identical" when doing a simulated synchronization, and then having edited local entries 9707 and 9709 by uploading (different) attachments to them.
The fact that the synchronization is suggesting to renumber two different entry IDs to the same number looks like a bug.
Best regards,
Andreas W.
| Andreas Warburton wrote: |
|
My MacOS (10.12.2) elogd version V3.1.2 is a recent git commit (edc5e85), due to the fix to my earlier-described issue solved in the thread here: https://midas.psi.ch/elogs/Forum/68519.
I am trying to (re-)set up Mirror functionality with a linux server running the standard public (V3.1.2-bd75964). I had initially updated the linux server so that it also had the latest git commit (edc5e85), but could then not even add new logbook entries that involved attachments to it. I therefore rolled the linux server back to the standard public 3.1.2 version.
On the remote Mac, synchronizations usually look like they are going to work fine, with Mirror simulate = 1 switched on. After I set Mirror simulate = 0, and if the server and remote logbook are already identical, I *occasionally* get the proper "All Entries Identical" synchronization result. Unfortunately, this is very rare, and usually there is a failure whereby the remote (Mac) logbook decides that a significant fraction of its entries (usually sequential, from some seemingly random entry all the way up to the last entry) are missing on the linux server and need to be submitted back to the server from the remote Mac.
When the local and remote logbooks are not identical, and a record in need of synchronization contains an attachment, there is again destructive behaviour similar to that described above, except that the Mac elogd executable usually crashes. (As in the case of the already-identical synchronizations described above, I only tested this after observing the correct expected behaviour first with Mirror simulate = 1.)
I'd be grateful for some help/suggestions. My current testing suggests that my problems are likely not elog-content dependent. (The logbook now undergoing synching has less than 10 entries in it.)
More generally, the issue of having things behave fine with Mirror simulate = 1, but then experiencing corruption/damage when switching to Mirror simulate = 0 seems serious to me.
Many thanks, Andreas
|
|
|
|
|
68548
|
Fri Jan 13 21:05:49 2017 |
 | Andreas Warburton | awarburt@physics.mcgill.ca | Bug report | Linux | Mac OSX | V3.1.2-edc5e85 | Re: elogd crashes during SSL Mirror operations involving attachments | When I switch from SSL = 1 to SSL = 0 and I use http:// instead of https://, the ability to upload attachments to logbook entries returns. With both Chrome and Safari browsers, with SSL = 1 the file upload hangs after only a small percentage of the file has been uploaded. I ran the following openssl diagnostic on my elogd port. Would anyone have advice on what might be causing such errors?
tapajo [/usr/local/elog/elog-latest] openssl s_client -connect elog.hep.xxx.xxx.xx:80xx -state -nbio | grep "^SSL"
SSL_connect:before/connect initialization
SSL_connect:SSLv2/v3 write client hello A
SSL_connect:error in SSLv2/v3 read server hello A
SSL_connect:unknown state
depth=0 C = EU, ST = SomeState, L = SomeCity, O = SomeOranization, OU = SomeOrganizationUnit, CN = localhost
verify error:num=18:self signed certificate
verify return:1
depth=0 C = EU, ST = SomeState, L = SomeCity, O = SomeOranization, OU = SomeOrganizationUnit, CN = localhost
verify return:1
SSL_connect:unknown state
SSL_connect:unknown state
SSL_connect:unknown state
SSL_connect:unknown state
SSL_connect:unknown state
SSL_connect:unknown state
SSL_connect:error in unknown state
SSL_connect:error in unknown state
SSL_connect:unknown state
SSL_connect:unknown state
SSL handshake has read 1733 bytes and written 871 bytes
SSL-Session:
SSL3 alert read:warning:close notify
SSL3 alert write:warning:close notify
| Andreas Warburton wrote: |
|
The attached screenshot shows the behaviour after doing a synchronization (with Mirror simulate = 1) following first having ensured that the local (Mac) and remote (linux) ELOGs initially showed "All entries identical" when doing a simulated synchronization, and then having edited local entries 9707 and 9709 by uploading (different) attachments to them.
The fact that the synchronization is suggesting to renumber two different entry IDs to the same number looks like a bug.
Best regards,
Andreas W.
| Andreas Warburton wrote: |
|
My MacOS (10.12.2) elogd version V3.1.2 is a recent git commit (edc5e85), due to the fix to my earlier-described issue solved in the thread here: https://midas.psi.ch/elogs/Forum/68519.
I am trying to (re-)set up Mirror functionality with a linux server running the standard public (V3.1.2-bd75964). I had initially updated the linux server so that it also had the latest git commit (edc5e85), but could then not even add new logbook entries that involved attachments to it. I therefore rolled the linux server back to the standard public 3.1.2 version.
On the remote Mac, synchronizations usually look like they are going to work fine, with Mirror simulate = 1 switched on. After I set Mirror simulate = 0, and if the server and remote logbook are already identical, I *occasionally* get the proper "All Entries Identical" synchronization result. Unfortunately, this is very rare, and usually there is a failure whereby the remote (Mac) logbook decides that a significant fraction of its entries (usually sequential, from some seemingly random entry all the way up to the last entry) are missing on the linux server and need to be submitted back to the server from the remote Mac.
When the local and remote logbooks are not identical, and a record in need of synchronization contains an attachment, there is again destructive behaviour similar to that described above, except that the Mac elogd executable usually crashes. (As in the case of the already-identical synchronizations described above, I only tested this after observing the correct expected behaviour first with Mirror simulate = 1.)
I'd be grateful for some help/suggestions. My current testing suggests that my problems are likely not elog-content dependent. (The logbook now undergoing synching has less than 10 entries in it.)
More generally, the issue of having things behave fine with Mirror simulate = 1, but then experiencing corruption/damage when switching to Mirror simulate = 0 seems serious to me.
Many thanks, Andreas
|
|
|
|
68547
|
Fri Jan 13 08:27:15 2017 |
 | Andreas Warburton | awarburt@physics.mcgill.ca | Bug report | Linux | Mac OSX | V3.1.2-edc5e85 | Re: elogd crashes during SSL Mirror operations involving attachments | The attached screenshot shows the behaviour after doing a synchronization (with Mirror simulate = 1) following first having ensured that the local (Mac) and remote (linux) ELOGs initially showed "All entries identical" when doing a simulated synchronization, and then having edited local entries 9707 and 9709 by uploading (different) attachments to them.
The fact that the synchronization is suggesting to renumber two different entry IDs to the same number looks like a bug.
Best regards,
Andreas W.
| Andreas Warburton wrote: |
|
My MacOS (10.12.2) elogd version V3.1.2 is a recent git commit (edc5e85), due to the fix to my earlier-described issue solved in the thread here: https://midas.psi.ch/elogs/Forum/68519.
I am trying to (re-)set up Mirror functionality with a linux server running the standard public (V3.1.2-bd75964). I had initially updated the linux server so that it also had the latest git commit (edc5e85), but could then not even add new logbook entries that involved attachments to it. I therefore rolled the linux server back to the standard public 3.1.2 version.
On the remote Mac, synchronizations usually look like they are going to work fine, with Mirror simulate = 1 switched on. After I set Mirror simulate = 0, and if the server and remote logbook are already identical, I *occasionally* get the proper "All Entries Identical" synchronization result. Unfortunately, this is very rare, and usually there is a failure whereby the remote (Mac) logbook decides that a significant fraction of its entries (usually sequential, from some seemingly random entry all the way up to the last entry) are missing on the linux server and need to be submitted back to the server from the remote Mac.
When the local and remote logbooks are not identical, and a record in need of synchronization contains an attachment, there is again destructive behaviour similar to that described above, except that the Mac elogd executable usually crashes. (As in the case of the already-identical synchronizations described above, I only tested this after observing the correct expected behaviour first with Mirror simulate = 1.)
I'd be grateful for some help/suggestions. My current testing suggests that my problems are likely not elog-content dependent. (The logbook now undergoing synching has less than 10 entries in it.)
More generally, the issue of having things behave fine with Mirror simulate = 1, but then experiencing corruption/damage when switching to Mirror simulate = 0 seems serious to me.
Many thanks, Andreas
|
|
|
68546
|
Thu Jan 12 09:10:06 2017 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | ELOG V3.1.1-076 | Re: UTC time | Hi Luca,
if you want to change all datetime properties to UTC time, then you'll just need to set the timezone on the server to UTC, before elogd is started.
Cheers, Andreas
| Luca wrote: |
|
Dear Steve,
thanks a lot. Sorry but I am not expert of elog. I "inherited" from a colleague and wanted to see if I can keep it alive but to do it I would need to move to UTC. Should this command affect the "INSERT CURRENT TIME/DATE" button? It does not seem to change.
Best
Luca
| Stefan Ritt wrote: |
|
How do you believe that you can preset a Submission item? Preset only works for attributes, so you have to define an attribute like "Submission UTC" or similar and preset this attribute with
Preset Submission UTC = $utcdate
| Luca wrote: |
|
Dear all,
I am trying to have the elog timestamp in UTC time instead of local time using the following config file but without success. Do you know what I am doing wrong?
Thanks
Luca
Theme = default
Comment = XENON1T LogBook
Attributes = Subject, Author, Category, Type, Status
Locked Attributes = Author
Required Attributes = Category, Type
Preset Author = $long_name
Preset Submission = $utcdate
Options Category = General, CRY - Cryogenics, PUR - Purification, RSX- ReStoX, DST - Distillation Column, MUV - Muon Veto, TPC - Detector, WTR - Water Tank, RAD - Gas Purity, CAL - Calibration, SCT - Slow Control, SOP - Shiftoperation
Options Type = Software Installation, Hardware Installation, Failure/Problem, Configuration, Authorization, Other, Leak Check, xenon operation, Shared Resources, Log, Alarm Tests, Hardware test
Options Status = Info, Open - in progress, Closed - unsolved, Closed - solved, Other
Cell Style Status Info = background-color:lightblue
Cell Style Status Closed - solved = background-color:lightgreen
Cell Style Status Open - in progress = background-color:yellow
Cell Style Status Closed - unsolved = background-color:red
Extendable Options = Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Category
|
|
|
|
|
68545
|
Thu Jan 12 08:28:45 2017 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | ELOG V3.1.1-076 | Re: UTC time | The INSERT CURRENT TIME/DATE button is not affected by this setting.
| Luca wrote: |
|
Dear Steve,
thanks a lot. Sorry but I am not expert of elog. I "inherited" from a colleague and wanted to see if I can keep it alive but to do it I would need to move to UTC. Should this command affect the "INSERT CURRENT TIME/DATE" button? It does not seem to change.
Best
Luca
| Stefan Ritt wrote: |
|
How do you believe that you can preset a Submission item? Preset only works for attributes, so you have to define an attribute like "Submission UTC" or similar and preset this attribute with
Preset Submission UTC = $utcdate
| Luca wrote: |
|
Dear all,
I am trying to have the elog timestamp in UTC time instead of local time using the following config file but without success. Do you know what I am doing wrong?
Thanks
Luca
Theme = default
Comment = XENON1T LogBook
Attributes = Subject, Author, Category, Type, Status
Locked Attributes = Author
Required Attributes = Category, Type
Preset Author = $long_name
Preset Submission = $utcdate
Options Category = General, CRY - Cryogenics, PUR - Purification, RSX- ReStoX, DST - Distillation Column, MUV - Muon Veto, TPC - Detector, WTR - Water Tank, RAD - Gas Purity, CAL - Calibration, SCT - Slow Control, SOP - Shiftoperation
Options Type = Software Installation, Hardware Installation, Failure/Problem, Configuration, Authorization, Other, Leak Check, xenon operation, Shared Resources, Log, Alarm Tests, Hardware test
Options Status = Info, Open - in progress, Closed - unsolved, Closed - solved, Other
Cell Style Status Info = background-color:lightblue
Cell Style Status Closed - solved = background-color:lightgreen
Cell Style Status Open - in progress = background-color:yellow
Cell Style Status Closed - unsolved = background-color:red
Extendable Options = Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Category
|
|
|
|
|
68544
|
Thu Jan 12 02:35:02 2017 |
| Luca | rimbalzina@gmail.com | Question | Linux | ELOG V3.1.1-076 | Re: UTC time | Any suggestion?
| Luca wrote: |
|
Dear Steve,
thanks a lot. Sorry but I am not expert of elog. I "inherited" from a colleague and wanted to see if I can keep it alive but to do it I would need to move to UTC. Should this command affect the "INSERT CURRENT TIME/DATE" button? It does not seem to change.
Best
Luca
| Stefan Ritt wrote: |
|
How do you believe that you can preset a Submission item? Preset only works for attributes, so you have to define an attribute like "Submission UTC" or similar and preset this attribute with
Preset Submission UTC = $utcdate
| Luca wrote: |
|
Dear all,
I am trying to have the elog timestamp in UTC time instead of local time using the following config file but without success. Do you know what I am doing wrong?
Thanks
Luca
Theme = default
Comment = XENON1T LogBook
Attributes = Subject, Author, Category, Type, Status
Locked Attributes = Author
Required Attributes = Category, Type
Preset Author = $long_name
Preset Submission = $utcdate
Options Category = General, CRY - Cryogenics, PUR - Purification, RSX- ReStoX, DST - Distillation Column, MUV - Muon Veto, TPC - Detector, WTR - Water Tank, RAD - Gas Purity, CAL - Calibration, SCT - Slow Control, SOP - Shiftoperation
Options Type = Software Installation, Hardware Installation, Failure/Problem, Configuration, Authorization, Other, Leak Check, xenon operation, Shared Resources, Log, Alarm Tests, Hardware test
Options Status = Info, Open - in progress, Closed - unsolved, Closed - solved, Other
Cell Style Status Info = background-color:lightblue
Cell Style Status Closed - solved = background-color:lightgreen
Cell Style Status Open - in progress = background-color:yellow
Cell Style Status Closed - unsolved = background-color:red
Extendable Options = Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Category
|
|
|
|
|
68543
|
Tue Jan 10 11:13:02 2017 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.2 | Re: Limit number of characters for "login user" parameter string ? | There is a limit of 100 options per line, so you probably run against that. This is defined in elogd.h with MAX_N_LIST and MAX_N_ATTR. You can try to increase these and recompile, but at some point you will hit the stack size limit of your operating system and elogd will crash.
| Christine Quicot wrote: |
|
Hello all,
I use ELOG for about 30 users, and I've listed their email adresses in the "login user" parameter, using the LDAP authentication.
As I had problems with the users from the end of the list (they couldn't log in the logbooks) I guessed that there is a max length for the string "login user" (or other parameter?). it seems to be a 1000 character limit.
How can I parameter this limit to another value? Is this value used for other parameters?
Thanks for your answer.
|
|
|