Re: elog server crashed due to cookies send by client, posted by Heinz Junkes on Tue Sep 19 10:58:14 2023
|
The server is crached because the author field was accidentally filled with a long string due to an automated (remote) script:
“
Author: The ion getter pump has successfully recovered and appears to be operating steadily once more. Consequently, I proceeded with sputtering |
FreeBSD Install, posted by Jason on Sun Sep 21 09:33:46 2003
|
I am getting the following errors when trying to install elog-2.3.9 on
my FreeBSD box. I am running FreeBSD 4.5-RELEASE.
|
|
Re: FreeBSD Install, posted by Stefan Ritt on Sun Sep 21 09:53:56 2003
|
Unfortunately I don't have access to a FreeBSD box so I cannot try. But I
thought the GNU make is the same on Linux and FreeBSD???
|
|
Re: FreeBSD Install, posted by G on Tue Sep 23 01:10:17 2003
|
I got elog 2.3.9 running on FreeBSD 5.1 successfully,
I compiled elog on a redhat box and then just copied over all the files to
the FreeBSD box and ELOG just ran with no issues.
|
|
Re: FreeBSD Install, posted by Dave Truesdell on Sun Oct 26 18:32:17 2003
|
> I got elog 2.3.9 running on FreeBSD 5.1 successfully,
> I compiled elog on a redhat box and then just copied over all the files to
> the FreeBSD box and ELOG just ran with no issues.
|
Re: FreeBSD Install, posted by G on Tue Oct 28 22:40:28 2003
|
Thanks for that mate, compiled elog on FreeBSD 5.1 myself no problems just like
you said, great!
|
|
ELOG reverts to demo configuration, posted by VUIIS SysAdmin on Thu Feb 20 16:54:32 2020
|
I have been using elog for over 10 years. Suddenly my elog installation has changed (probably from a recent update. My /etc/elogd.cfg has changed to
the original demo configuration. Even after changing it to my configuration from backup none of the entries for the logbooks apper even though the tabs
for the logboos are ther all logbooks are empty. I have looced at the logbook files and the entries seem to be there but are not showing on the web interface. |
|
Re: ELOG reverts to demo configuration, posted by Andreas Luedeke on Fri Feb 21 19:11:12 2020
|
If you've upgraded from an elog 2.x version to an 3.x version, then all entries of a logbook will be moved into subfolder, one for each year.
If you then switch back to the 2.x version of elog, it'll not find any entries.
You can move them back to the folder for the logbook (one directory up) and they'll be found again after the next restart of elog. |