Re: Logfile not registering entry numbers?, posted by Sergio Navarrete on Thu Dec 16 08:23:22 2021
|
It seems that the latest Windows binary still predates this fix. Will there be a new installer soon? Thanks for your support.
| Stefan Ritt wrote: |
|
I finally found some time to fix that bug. Was just that the log file hat #0, the bug should not have had any ohter side effects. Now the logfile is fine.
| David Pilgram wrote: |
|
As a regular elog (ab)user, I have seen this behaviour from time to time. So far as I recall, the cause actually is that a normal entry is looking for the entry in the "Reply to" field of the normal entry in the yymmdda.log file. When that entry does not exist, then I see a duplicate line of an entry with entry "#0", in emboldened black type. I did have a screenshot, but cannot find it for now.
A quick (relative term, that) search usually finds the entry which references the missing "Reply to" line, and editing that, all is well. I'm not sure how this can happen, but it does. NB, I'm still on elog 2.9.2 so I don't know how the draft facility works and possibly enhances the possibility of this issue.
Note that this is different to the case (rather more frequent) where the entry in the "In reply to" field is missing. This causes elog to go into a continuous loop and only the strongest measures ("kill -9 xxxx in linux) will break this out. This can happen more frequently as if you delete a thread with a large number (>40?) of entries, elog crashes, but more importantly, hasn't finished the job. Clicking on the remenents of the thread (which are usually the later entries) causes the endless loop.
| Andreas Luedeke wrote: |
|
It looks like you've found a bug in ELOG. I've checked my elog.log and see that all NEW entry lines show "#0".
I've looked into the code: the message is written before the new entry is submitted, and only then the entry ID is defined.
For new entries one would need to make the logging print line later - but that would blow up the code.
The message IDs are correct for saving drafts and editing entries. I'll discuss with Stefan if that should be fixed.
Andreas
| Sergio Navarrete wrote: |
|
I have configured a logbook with the logfile on, but when a user replies to an entry the line logged goes
Date Time [User@IP] {Logbook} NEW entry #0
How can I make the #0 be the real entry number for the reply?
|
|
|
|
|
Mirroring function for a full both-sides synchronization, posted by Sergei Gavrilov on Mon Feb 24 15:58:55 2020
|
Hello, dear ELOG's gurus.
Please help me to understand a problem with mirroring function.
It appears in ELOG V3.1.4-a04faf9f - the last official Windows release, as well as previous 3.1.3 Windows release, which I have checked for comparison.
When I'm using a manual configuration with "mirror server, cron, user" options for one (master) of two servers, it operates well, except the situation, when a new entry is submitted at the second (slave) server.
For example, for a new entry with a real ID#2 at Slave its logfile gives "NEW entry #0", so logfile of the master server gives "MIRROR: Error receiving message: Received wrong entry id "0"".
After that Master deletes this entry at Slave "MIRROR delete remote entry #2".
In case of mirror functions in both .cfg files (Master to Slave, Slave to Master) both servers hung on after the first mirror process.
Now let's imagine, what I want to do.
Master, as a main-operation global log, is off-operation, Slave automatically becomes a reserv-operation local log with full information from Master due to previous periodic mirroring.
Users work with Slave, submit new entries - all with #0 ID.
After repairing Master starts active mirroring and just deletes all new entries from Slave.
It seems, that the problem is not with mirroring, but with a new entry ID, as was mentioned in https://elog.psi.ch/elogs/Forum/68850
Were these ID#0/mirror problems resolved somehow or may be it is not a problem, but simply my errors in ELOG configuration?
Is there a chance to get an up-to-date Windows-release with working both-sides mirror function and all other addings after V3.1.4-a04faf9f ?
Best regards,
Sergei |
|
Up-to-date windows-version, posted by Sergei Gavrilov on Sun Oct 18 16:59:38 2020
|
Dear colleagues,
Can someone compile an up-to-date windows-version or write a manual how to do it in Windows without compiling errors?
Thank you. |
Find cannot find values with brackets, posted by Sebastian Schenk on Fri Jun 14 11:29:30 2019
|
For demonstration, I created https://elog.psi.ch/elogs/Linux+Demo/8
The Find search for category aaa(bb) does not give results.
A quick filter corrects the value to aaa\(bb) and delivers results.
I made a simple fix and submitted it as PR to the bitbucket repository. |
|
restrict edit time, posted by Sebastian Schenk on Mon Jul 15 17:35:48 2019
|
Hello,
I have experienced some inconveniences with the restrict edit time option.
First, it is not possible for admin users to edit an entry after the edit time.
The restrict edit option allows admin users to edit posts from other users,
so I think admins should also be allowed to edit posts after edit time.
As they can edit the config and temporarily disable the restrict edit time option, which is an issue.
Secondly, if a user made a draft and did not submitted it before the edit time runs out,
the draft got stuck as it cannot be edited (and submitted) any more.
Best wishes,
Sebastian |
|
Re: How to get Elog server to produce web server log files in Linux., posted by Sebastian Schenk on Mon Oct 21 13:41:08 2019
|
Hi,
that Sebastian would be me. I replied to the first entry, as it was a draft (site reloaded incorretly...) and now I can't see the post anywhere. But this is off topic.
We have elog running on port 8000 and forward the traffic via Apache to it. Apache handles the SSL and other sites on the server.
All you need is a apache site configuration like the following. The parameter you want is CustomLog. (Have a look in the internet for options.)
I have also used nginx as webserver and know it can also handle this proxy setup.
If you use the following config, the elog config needs the URL attribute in the (global) config.
Best wishes,
Sebastian
<VirtualHost *:443> # change 443 to 80, if you don't use SSL
ServerName your.server.name
# delete the next 3 lines, if you don't use SSL
SSLEngine on
SSLCertificateFile /path/to/your/ssl.crt
SSLCertificateKeyFile /path/to/your/ssl.key
ProxyPreserveHost On
ProxyPass / http://127.0.0.1:8000/
ProxyPassReverse / http://127.0.0.1:8000/
# Possible values include: debug, info, notice, warn, error, crit, alert, emerg.
LogLevel warn
CustomLog ${APACHE_LOG_DIR}/access.log combined
ErrorLog ${APACHE_LOG_DIR}/error.log
</VirtualHost>
| John wrote: |
|
Hi again everyone; a Sebastian suggested I use a reverse proxy to complete my need to have logs show up when someone 'lands' on my first entry page. I see that Elog will only start recording logs when someone has actually started to do some work.. like login, read a post, etc... but NOT when they first enter the login page or 'listings' pages. I have tried fowarding from my router (both lighty and Apache) but so for no good. I will also look into a vhost option and shareing the same port (very difficult- if even possible) to solve my dilema.
John :)
| Stefan Ritt wrote: |
|
Have you tried
Logfile = ...
Logging level = 3
| John wrote: |
|
Hi, I have been trying for a long time to get my web server logs to record when someone accesses my Elog server. I've tried Apache2, Lighttpd, and others, all with no luck. Either the web servers complain that the port I have Elog on is in use, or I just don't get any readings. I need to see who is accessing my Elog from the web, and I hope there is a way.
Thanks again for such a wonderful program,
John
|
|
|
|
|
Re: How to update date fields so 'alarms' work correctly., posted by Sebastian Schenk on Fri Mar 13 16:38:53 2020
|
Dear John,
I am a user of the elog system and no developer, so no complete answer guaranteed.
The quote of the manual describes the case, if e.g. an hardware component discovers a failure and the connected PC makes an automatic (new) entry to the elog. Probably modifying an existing one.
I have small concerns on your solution. The description of your alarm system sounds the other ways around, as you are doing something, depending on the elog entries. Based on your statement on JS and dedicated start page, you want to do it on client-side and not on the server. Where I can see the issue, if there is not client, then there is no alarm. As you want to change the date of the entries, I believe, you want to reuse the same entries multiple (infinite?) times instead of creating new ones. The later would be the style of an logging software like elog.
As far as I know, the Date attribute is special and cannot be changed by submitting something to the elog server. as this would make "Restrict edit time" useless. You can try it with this in your config:
Subst on edit Date = $date
Making an entry and edit it afterwards. The entry time stays the same.
If you really want to use this attribute, you have to do some scripting to the actual saved .log files, but this is not intended as I believe.
What you can do, is using an alternative attribute like "MDate" with the config:
Subst MDate = $date
Subst on edit MDate = $date
This will update every time you edit the entry.
Then you probably want to add something like this to your config
List display = ID, MDate, Author, ...
Or "Update" using the duplicate function on the old entry, where you want to change the date, creating a new one with the same content.
Or "Update" using the reply function to create a new entry, referring to the old one.
I hope, I could help.
Best wishes,
Sebastian
| John wrote: |
|
Hi Stefan!
In the user manual under misc it says this: "The elog program makes it possible to submit logbook entries automatically by the system or from scripts. In some shift logbooks this feature is used to enter alarm messages automatically into the logbook. "
Ok what am trying to do is have all messages update (somehow) without the user entering each record. I want my alarm system to be able to keep-up2-date on the expirations, by simply updating the 'date' fields I have in the logbooks (JS). I am getting used to JavaScript, and have all of that working as far as the actual 'alarms' are concerned. But they are useless if the dates are stagnent (ie. not updateing at least once per day).
So can you refer me to the 'shift books' you reference above, so I can understand how to write the code necessary? I've spend much time searching the net on this and experimenting, so I did try to find out before I posted. I believe using a combination of the Elog Utility, with a dedicated 'start page' that is mostly JS, will be part of the solution...
Thanks soo much for your help and awesome creation! :)
John
|
|
|
Re: field selections persist across new log entries?, posted by Sebastian Schenk on Tue Sep 8 16:35:14 2020
|
As far as I know, it is not possible, if you make a "new" entry.
You could configure the elog, to always PRESET an atribute, but then it is always the same, not the last.
I think the "duplicate" entry function could provide you partly with the functionality you want, as it copies all old values into a new entry.
Regards,
Sebastian
| Anthony Krishock wrote: |
|
All,
I am using elog as an observation log for amateur astronomy. I have a form configured, but I would like to know if it is possible to make certain fields persist across new entries.
What I mean is this:
When I make an new observation, I select a value for sky conditions (say.. "1"). When I make another observation, "1" is already selected.
Is this possible? If so, how?
Thanks
|
|
|