build 8.0.8 runaway log file fixes
This commit is contained in:
@@ -141,7 +141,7 @@ TWO types makes the most sense after considering options:
|
||||
- One time fee, user can use indefinitely
|
||||
- self installed, hosted and maintained by customer
|
||||
- least profitable for us long term if they don't buy a maint. subscription
|
||||
- Without maintenance subscription, eligable for Minor updates only to fix bugs no new features so in other words they buy 8.0.7 they can upgrade to any 8.0.X version release, but not 8.1 as it will be new features added that don't break backward compatibility
|
||||
- Without maintenance subscription, eligable for Minor updates only to fix bugs no new features so in other words they buy 8.0.8 they can upgrade to any 8.0.X version release, but not 8.1 as it will be new features added that don't break backward compatibility
|
||||
- one-time payment, along with the option of a yearly maintenance fee.
|
||||
- This is basically our current model but we allow upgrades for subscribers
|
||||
- **HAS CODE IMPLICATIONS** upgrades need to check if allowed based on version number if no maintenance subscription _not_ on date of build.
|
||||
|
||||
@@ -2,42 +2,14 @@
|
||||
|
||||
|
||||
|
||||
todo: URGENT - RUNAWAY LOGGING EATING UP SERVER SPACE
|
||||
|
||||
Problem:
|
||||
AyaNova log and system journal eating up all disk space due to postgres being down for unknown reason and ayanova repeatedly trying to do stuff in this condition and then issuing errors and LOGGING
|
||||
|
||||
potential fixes: TODO HERE:
|
||||
FIXED Detect postgres is unreachable and stop digging a hole, wait to resolve it before continuing on again
|
||||
FIXED don't dual log to system journal logs and ayanova log
|
||||
Ayanova is not only logging but also directing it's output to the terminal window which in linux system service is being logged also to the journal logs
|
||||
AyaNova should only ouput to it's log file, not to terminal with the sole exception of the initial boot up period
|
||||
This may be a configuration in the logging library set this way??
|
||||
TODO: Add this to the standard server config script
|
||||
cap system journal logs in linux to 250mb or some reasonable value
|
||||
https://linuxhandbook.com/clear-systemd-journal-logs/
|
||||
TODO: cap ayanova logs in configuration
|
||||
something in here, but maybe it's config is different compare with code for logrotate in use now and see what the exact settings are
|
||||
https://github.com/NLog/NLog/wiki/Configuration-file
|
||||
https://github.com/NLog/NLog/wiki/File-target#archival-options
|
||||
https://nlog-project.org/config/
|
||||
NOTE: it may make sense to swtich from rotating every week to rotating on size instead, after all why force to rotate a nearly empty log?
|
||||
|
||||
Log issue final steps to complete:
|
||||
TODO: update build number when done and repost
|
||||
TODO: test in devops see what the what
|
||||
|
||||
DONE: If detect db is unavailable then log that and stop job processor etc basically freeze the server jobs until the db becomes available
|
||||
server state db unavailble not just at boot but during ops
|
||||
|
||||
|
||||
quick fixes:
|
||||
https://support.hostway.com/hc/en-us/articles/360001972270-How-to-clean-log-files-in-Linux
|
||||
https://linuxhandbook.com/clear-systemd-journal-logs/
|
||||
|
||||
Lessons learned:
|
||||
Use less to view humongous log files, it's perfect for it using the commands properly
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1426,6 +1398,6 @@ https://www.ayanova.com/download/next/ayanova-linux-x64-server.zip
|
||||
https://www.ayanova.com/download/next/ayanova-windows-x64-lan-setup.exe
|
||||
Current v8 docs home: https://www.ayanova.com/docs/next
|
||||
|
||||
BUILD 8.0.7 CHANGES OF NOTE
|
||||
BUILD 8.0.8 CHANGES OF NOTE
|
||||
|
||||
Subscription / perpetual license code and stuff
|
||||
|
||||
2
dist/install/windows/x64/lan.iss
vendored
2
dist/install/windows/x64/lan.iss
vendored
@@ -1,7 +1,7 @@
|
||||
; LAN install for internal network use only
|
||||
|
||||
#define MyAppName "AyaNova server"
|
||||
#define MyAppVersion "8.0.7"
|
||||
#define MyAppVersion "8.0.8"
|
||||
#define MyAppPublisher "Ground Zero Tech-Works, Inc."
|
||||
#define MyAppURL "https://ayanova.com/"
|
||||
#define MyAppLauncherExeName "ayanova-launcher.exe"
|
||||
|
||||
2
dist/install/windows/x64/standalone.iss
vendored
2
dist/install/windows/x64/standalone.iss
vendored
@@ -3,7 +3,7 @@
|
||||
; external to lan requires different config
|
||||
|
||||
#define MyAppName "AyaNova"
|
||||
#define MyAppVersion "8.0.7"
|
||||
#define MyAppVersion "8.0.8"
|
||||
#define MyAppPublisher "Ground Zero Tech-Works, Inc."
|
||||
#define MyAppURL "https://ayanova.com/"
|
||||
#define MyAppLauncherExeName "ayanova-launcher.exe"
|
||||
|
||||
@@ -4,8 +4,8 @@
|
||||
</PropertyGroup>
|
||||
<PropertyGroup>
|
||||
<GenerateFullPaths>true</GenerateFullPaths>
|
||||
<Version>8.0.7</Version>
|
||||
<FileVersion>8.0.7.0</FileVersion>
|
||||
<Version>8.0.8</Version>
|
||||
<FileVersion>8.0.8.0</FileVersion>
|
||||
<ApplicationIcon>ayanova.ico</ApplicationIcon>
|
||||
<DocumentationFile>bin\$(Configuration)\$(TargetFramework)\$(AssemblyName).xml</DocumentationFile>
|
||||
<noWarn>1591</noWarn>
|
||||
|
||||
@@ -5,7 +5,7 @@ namespace AyaNova.Util
|
||||
/// </summary>
|
||||
internal static class AyaNovaVersion
|
||||
{
|
||||
public const string VersionString = "8.0.7";
|
||||
public const string VersionString = "8.0.8";
|
||||
public const string FullNameAndVersion = "AyaNova server " + VersionString;
|
||||
public const string CurrentApiVersion="v8";
|
||||
}//eoc
|
||||
|
||||
Reference in New Issue
Block a user