Re: UTC time, posted by Luca on Thu Jan 12 02:35:02 2017
|
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
|
|
|
|
|
Re: UTC time, posted by Stefan Ritt on Thu Jan 12 08:28:45 2017
|
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
|
|
|
|
|
Re: UTC time, posted by Andreas Luedeke on Thu Jan 12 09:10:06 2017
|
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
|
|
|
|
"No SMTP host defined in [global] section of configuration file", posted by Luca on Wed Jan 18 05:25:44 2017
|
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 |
|
Re: "No SMTP host defined in [global] section of configuration file", posted by Stefan Ritt on Wed Jan 18 10:25:20 2017
|
These problems usually come when you are using a different configuration file that the one you think you are using. Note that you explicitly can tell elogd to use a specific configuation file with the "-c" flag. Also make sure to restart elogd after major changes.
| Luca wrote: |
|
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
|
|
|
More than 100 attributes , posted by JD on Wed Jun 29 16:07:32 2016
|
I am modifying the elogd.cfg automatically with a script. The Script fetches a list of systems from a LDAP database and writes them into an "Options" line in the elog.cfg.
Everything worked fine, until we hit the critical number of 100 attributes. I saw this is also stated in the manual.
Is there any workaround? I downloaded the source code and hat a quit look, but couldn't find the section which is responsible for this behavior.
Is there a reason for this limit?
Thanks
Jonathan |
|
Re: More than 100 attributes , posted by Stefan Ritt on Wed Jun 29 16:58:15 2016
|
The limit is in the variable
#define MAX_N_ATTR 100
in elogd.c. If you increase it and recompile, it could work, but at some time you will get a stack overflow since arrays with that size are dynamically allocated on the stack, and depending on your compiler settings the stack size is only finite.
Stefan
| JD wrote: |
|
I am modifying the elogd.cfg automatically with a script. The Script fetches a list of systems from a LDAP database and writes them into an "Options" line in the elog.cfg.
Everything worked fine, until we hit the critical number of 100 attributes. I saw this is also stated in the manual.
Is there any workaround? I downloaded the source code and hat a quit look, but couldn't find the section which is responsible for this behavior.
Is there a reason for this limit?
Thanks
Jonathan
|
|
|
Re: More than 100 attributes , posted by JD on Thu Jun 30 14:00:43 2016
|
Thank you Stefan, I think then I will leave it at the default value. I need a stable Systen
| Stefan Ritt wrote: |
|
The limit is in the variable
#define MAX_N_ATTR 100
in elogd.c. If you increase it and recompile, it could work, but at some time you will get a stack overflow since arrays with that size are dynamically allocated on the stack, and depending on your compiler settings the stack size is only finite.
Stefan
| JD wrote: |
|
I am modifying the elogd.cfg automatically with a script. The Script fetches a list of systems from a LDAP database and writes them into an "Options" line in the elog.cfg.
Everything worked fine, until we hit the critical number of 100 attributes. I saw this is also stated in the manual.
Is there any workaround? I downloaded the source code and hat a quit look, but couldn't find the section which is responsible for this behavior.
Is there a reason for this limit?
Thanks
Jonathan
|
|
|
|