custom subject for mail info, posted by Daniel Pfuhl on Thu May 16 18:00:22 2019
|
Hello,
we are extensively using ELOG for documenting changes in our infrastructure. It is very helpful for us.
To avoid multiple documentation efforts it would be even more helpful if the subject of an ELOG entry also could be the subject of the mail which |
Re: custom subject for mail info, posted by Stefan Ritt on Mon May 20 16:39:50 2019
|
Use Email subject = $Subject
or a bit more detailed
Use Email subject = ELOG Ticket: "$Subject" posted by $Author |
Re: custom subject for mail info, posted by Daniel Pfuhl on Mon May 20 18:10:02 2019
|
thank you!
Stefan
Ritt wrote:
Use Email subject |
|
Windows Server 2012 - moving logs, posted by Lesley Herren on Thu May 16 01:13:31 2019
|
We are installing a new data center which will be based on Windows 2012 servers. Our current center is on Windows 2008 and will be decommissioned
this year - 2008 servers (because of the security issue) will not be allowed in the new data center. So game plan is to install latest ELOG (3.1.2)
on the 2012 server at the new data center and move the logs over from the 2008 server. I've looked through entries and do not see anything about |
|
Re: Windows Server 2012 - moving logs, posted by Stefan Ritt on Thu May 16 09:12:52 2019
|
Just stop the server. Move your elog directory to the new server (including elogd.cfg, logbook directories, ...). Then check that the elogd.cfg needs
modifications, like the URL which might have changed, then start the new server. V2.9.2 did have an old data format, which *should* be converted automatically.
But first try it out before deleting the old server. |
|
Re: Windows Server 2012 - moving logs, posted by David Pilgram on Thu May 16 21:49:06 2019
|
Hi Lesley,
Perhaps I can restate Stefan's comment. The data structure of an elog entry, or indeed the structure of daily file(s) for any particular
logbook has not changed between v2 and v3. What has changed is the directory structure. A set of sub-directories (named by calendar years) |
|
Re: Windows Server 2012 - moving logs, posted by Lesley Herren on Thu May 16 23:07:53 2019
|
Thank you Stefan - it will take a couple of months to set up (many servers being built at the new farm). I will update you on the success of the
files converting automatically.
|
add a little function--go to the specified page number, posted by Xuan Wu on Tue May 14 09:40:58 2019 
|
Hi all,
I added an input widget for pagination. I'd like to share it here, maybe someone needs. If there are many pages, specifying the page
number will be useful. |
|
Shell execute, posted by Alan Grant on Tue May 14 06:07:07 2019
|
I have the line in my elog config to run a Powershell script when submitting a New entry. I just send an email as a test:
Execute New = "Powershell.exe -ExecutionPolicy Bypass D:\SendEmail.ps1"
Fyi, the Powershell statement itself (Send-MailMessage -From 'MeterElog@winnipeg.ca' |
|
Execute attribute, posted by Alan Grant on Fri May 10 04:34:36 2019
|
Apart from an inline shell command that can be run with the Execute attribute, is it possible to run an external script file? I would like to run a Powershell
script with the Elog attribute data parameters passed to it upon Submit New entry. |
|
Re: Execute attribute, posted by Stefan Ritt on Fri May 10 08:19:08 2019
|
I don't understand your question. There is no "inline" vs. "external" script. Using the "execute new = <command>",
you run a script on the server side. Can be powershell under Windows or bash/csh under Linux. I remember however that there has been issues under recent
windows in passing parameters to the shell. Linux certainly works fine, we usse it all the time. |
|
Re: Execute attribute, posted by Alan Grant on Fri May 10 15:01:52 2019
|
I think it was just a matter of my specific interepretation of the documentation, ie: using native OS shell commands vs any script language file
containing shell commands or any app for that matter. Nevertheless I think you've answered my questiuon so it's all good. Thanks Stefan.
|
Does there is a way to no the $message_id when creating a new submission, posted by Lagarde on Thu May 9 13:34:55 2019
|
Hello,
I would like to know if it's possible to know the message_id of when creating a new entry in elog ?
I would like to do something like this Preset text = $message_id |
|
Re: Does there is a way to no the $message_id when creating a new submission, posted by Stefan Ritt on Thu May 9 16:42:13 2019
|
No, the message ID gets assigned only when you submit the entry.
Stefan
Lagarde |
|
Last default = <n>, posted by Alan Grant on Mon Apr 29 02:41:15 2019
|
According to the doc on the setting "Last default = <n>" it is intended to restrict Quick Filter searches to the last (n) days of entries,
however when I add "Last default = 28" to config it still returns entries far older then 28 days when using the filter search. Am I misunderstanding,
or implementing it wrong? We must restrict searches through QF to reduce load. |
|
Re: Last default = <n>, posted by Stefan Ritt on Mon Apr 29 13:12:56 2019
|
Indeed the description of the "Last default = <n>" option is not clear. I just updated that. If you have a quick filter "Date",
then you have different options there like "Last day", "Last 3 days", "Last week", "Last month", "Last 3 months",
"Last 6 months", "Last year". Each of these options has an underlying number of days, which are 1, 3, 7, 31, 92, 182, 364. In the "Last |
|
Re: Last default = <n>, posted by Alan Grant on Mon Apr 29 17:48:13 2019
|
I just changed to Last default = 31 and even restarted elogd.exe but it still finds a given string older than 31 days. Also the default Select Period
box value next to the QF's remains at All Entries. My understanding is it shoud behave like Find, where Show Last Default = 31 should default
the display to Month, and also only search within the last month of entries. |
|
Re: Last default = <n>, posted by Stefan Ritt on Wed May 1 11:06:04 2019
|
It works for me. Have you tried other values (1, 3, 7, ..)? The key is that the quick filter changes to "Last month". If it does not, there
must be some trivial error, like type in elogd.cfg, you modify the wrong logbook, have a very old version of elog etc.
Stefan |
|
Re: Last default = <n>, posted by Stefan Ritt on Wed May 1 11:08:10 2019
|
You say "Show Last Default = 31". This options applies only to the "Find" page, the option "Last Default = 31" works for
the quick filter. Probably you have to change "Show Last Default" to "Last Default".
Stefan |
|
Re: Last default = <n>, posted by Alan Grant on Wed May 1 15:28:41 2019
|
I was just referring to "Show last default" (under Find) as a parallel example of how I assume "Last default" should
function on the List page.
I also tried values 3 and 7 but "All entries" still displays in the "List period" box. A restart of elogd makes no difference. |
|
Re: Last default = <n>, posted by Stefan Ritt on Fri May 3 15:50:39 2019
|
I just tried your elogd.cfg, and it works fine for me. So no idea what is wrong in your case.
Stefan |
|
Re: Last default = <n>, posted by Alan Grant on Fri May 3 16:02:33 2019
|
Ok thanks for taking the time to try it out. I definitely still show "All entries" in any case, so I will continue to try to resolve on
my end and if I find the cause or solution I will share back on the forum.
First though, I noticed you ran 3.1.4 whereas I'm still on 3.1.2. I'm also on Windows Server 2016 and IE 11. Do you think any |
|
Re: Last default = <n>, posted by Stefan Ritt on Fri May 3 16:22:23 2019
|
Yes I always run the current version from bitbucket. I haven't touched that code for "last default" since a long time, so I don't expect
the verison to make a difference. Unfortuantely I have not Windows Server or IE for testing.
Alan |
|
Re: Last default = <n>, posted by Alan Grant on Fri May 3 16:29:00 2019
|
Thanks again.
I noticed in the Change Log for 3.1.4 that there's a reference to something done with "Last default" in Sept 2018 so I think
I will try to set up a Linux instance and try out 3.1.4. Regards. |
|
Re: Last default = <n>, posted by Stefan Ritt on Fri May 3 16:48:47 2019
|
Indeed you're right (my memory is fading, argh). Please try 3.1.4.
Stefan
Alan |
elogd Service exited with abnormal code: 1, posted by Alessio Sarti on Tue Apr 23 14:06:36 2019
|
Dear all.
I am running elog
elogd 3.1.4 , revision ead6bbc6 |
|
Re: elogd Service exited with abnormal code: 1, posted by Stefan Ritt on Tue Apr 23 14:26:51 2019
|
This kind of behavior we typically see if some elog entry is corrupt. After a few hours you might access this corrupt entry by accident, and then the
server stops. If you see however this behavior on a fresh logbook with no corrupt entries, then the problem must lie somewhere else.
Do you see the same problem running under linux? |
|
Re: elogd Service exited with abnormal code: 1, posted by Alessio Sarti on Thu Apr 25 11:16:06 2019
|
Thanks for the prompt feedback.
a) I confirm that the problems shows up also when running interactively the elog through elogd -p 8080
b) I am trying to catch the exit using lldb on the mac machine. I will be able to give you some feedback on that I hope in the next week (not |
|
Re: elogd Service exited with abnormal code: 1, posted by Stefan Ritt on Thu Apr 25 11:27:21 2019
|
What you recommend is enough. Just make sure to compile elogd with the flags mentioned before, and when you get the segment violation, do a stack trace
inside the debugger to learn where the fault happend. Maybe also print the contents of some variables at the current location.
Stefan |
|
Re: elogd Service exited with abnormal code: 1, posted by Alessio Sarti on Tue Apr 30 12:47:46 2019
|
I was finally able to catch the crash.
I paste below the info provided by lldb..
It seems that it has something to do with the 'first' logbook that contains 115 entries and is displayed in 6 pages. |
|
Re: elogd Service exited with abnormal code: 1, posted by Alessio Sarti on Tue Apr 30 14:07:52 2019
|
Actually it is a little bit more difficult than that.
I have restarted elogd and got a crash but this time it seems related to a different logbook...
Below the stack trace.. |
|
Re: elogd Service exited with abnormal code: 1, posted by Stefan Ritt on Wed May 1 10:59:59 2019
|
Ok, that helped. It looks to me that the strlcpy() function from MacOSC does not like overlapping stings as parameters. Funny that this does not happen
on my Mac (Mojave 10.14.4). I fixed the two cases you reported (lines 18712 and 19021) and committed the changes to bitbucket, from where you can pull
and test it again (see https://elog.psi.ch/elog/download.html for instructions). If it happens |
|
Re: elogd Service exited with abnormal code: 1, posted by Alessio Sarti on Thu May 2 09:47:41 2019
|
Thanks a lot for providing a quick fix!
The elog is now happily running since two days without problems :)
I will get back to you in case anything else shows up. |