log-vm: starting systemd-journal-remote service in log-vm

Without this patch if ghaf-host tries to do `systemd-journal-upload`
there will be following error "Failed to connect to 192.168.101.66
port 19532 after 0 ms: Couldn't connect to server".
As there will be no listener running in log-vm to accept logs.

With this patch we add listener in log-vm on 19532 port to accept logs.
Now `remote.service` is failing frequently with following error
"failed: Send failure: Connection reset by peer", however logs are
getting copied in log-vm from ghaf-host.
remote.service failure needs further debugging.

Signed-off-by: Vunny Sodhi <vunny.sodhi@unikie.com>

modules/common/log/journal-remote-upload.nix

@@ -6,13 +6,18 @@ in {
     group = "systemd-journal-upload";
   };
   users.groups.systemd-journal-upload = {};
+  users.users.systemd-journal-upload.extraGroups = ["systemd-journal"];
 
   systemd.services.systemd-journal-upload = {
+    description = "Service to upload journal logs to log-vm";
     enable = true;
+    after = ["network-online.target"];
     serviceConfig = {
       #ExecStart = "${pkgs.systemd}/lib/systemd/systemd-journal-upload --save-state -u http://${log-vm-ip-port}";
       ExecStart = "${pkgs.systemd}/lib/systemd/systemd-journal-upload -u http://${log-vm-ip-port}";
       User = "systemd-journal-upload";
+      Restart = "on-failure";
+      RestartSec = "1";
     };
 
     wantedBy = ["multi-user.target"];

modules/microvm/virtualization/microvm/logvm.nix

@@ -67,6 +67,11 @@
 
         systemd.services.systemd-journal-remote = {
           enable = true;
+          serviceConfig = {
+            ExecStart = "${pkgs.systemd}/lib/systemd/systemd-journal-remote --listen-raw=19532 --output=/var/log/journal/remote";
+            User = "systemd-journal-remote";
+          };
+          wantedBy = ["multi-user.target"];
         };
 
         microvm = {