Re: Entry size too large for email notification, posted by Stefan Ritt on Mon Aug 27 13:07:28 2018
|
That's how it is implemented. If you use
Max email attachment size = 1000000
then attachments below 1 MB are sent as attachments, and if the attachment is above 1 MB, then only a link to the attachment in the elog is sent. |
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.
|
|
Looking for version update advice, posted by Patrick Upson on Fri Sep 13 12:02:54 2024
|
I've inherited a position that includes deploying elog for an at-sea mission. Once at sea there's no gauntee of internet connection so I have
to be sure things are going to work before hand. The machines I currently have (we have several backup machines) are running elog version 2.9.2 and
I'm looking for a change log, or feature list to determine if it's safe to update the at-sea laptops to the latest version of elog. |
|
Re: Looking for version update advice, posted by Stefan Ritt on Wed Sep 25 13:17:06 2024
|
If 3.1.4 runs safely on your laptop, there should be no problem to update the 2.9.2 one. But first do it on a copy of your logbooks from the at-sea.
The get converted automatically into a newer format but that should be transparent.
On the other hand you don't really need a new system if your old installation works fine and you don't need any of hte new features. |
|
Re: Looking for version update advice, posted by Patrick Upson on Wed Sep 25 13:26:07 2024
|
Thanks. I did eveuntaully find the change log and made the decision to upgrade the at-sea machines. So far the configuration file we update for each
mission still works. I have a copy of the 2.9.2 installer that if something catostrophic happens I can remove the new version and take it back, but I don't
think it'll be a problem. We archive logbooks at the end of a mission, but each mission basically starts from a fresh install like state anyway. |