[V13] How to manually gather support logs from appliance

[BrianBuchanan]

Hello,

Support case #07882076, our Veeam V13 appliance is not allowing logins this morning (HTTP ERROR 500) and I don't know how to gather logs from the appliance manually. I've found KB1832 but it hasn't been updated for manual collection from the linux appliance. I also found KB4783 but that's the installer. In any case I suppose support will get back with something soon but KB1832 should probably have a manual log collection section from the appliance.

Thanks!

[BrianBuchanan]

I enabled ssh through the console, logged in and ran systemctl --failed and it looks like postgres and sssd died?

Code: Select all

[veeamadmin@veeam01 ~]$ systemctl --failed
  UNIT                  LOAD   ACTIVE SUB    DESCRIPTION
● postgresql-17.service loaded failed failed PostgreSQL 17 database server
● sssd.service          loaded failed failed System Security Services Daemon
● user@1000.service     loaded failed failed User Manager for UID 1000

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
3 loaded units listed.

Code: Select all

systemctl status postgresql-17
× postgresql-17.service - PostgreSQL 17 database server
     Loaded: loaded (/usr/lib/systemd/system/postgresql-17.service; enabled; preset: disabled)
    Drop-In: /etc/systemd/system/postgresql-17.service.d
             └─10-pgdata.conf, 11-alias.conf
     Active: failed (Result: oom-kill) since Sat 2025-11-08 17:07:59 EST; 1 day 17h ago
   Duration: 1w 2d 5h 25min 49.593s
       Docs: https://www.postgresql.org/docs/17/static/
   Main PID: 1516 (code=exited, status=1/FAILURE)
        CPU: 2d 19h 45min 42.108s

Warning: some journal files were not opened due to insufficient permissions.
[veeamadmin@veeam01 home]$ free
               total        used        free      shared  buff/cache   available
Mem:        16364984    14586356      266828     3609820     5467768     1778628
Swap:        4194300     4121492       72808

"oom-kill" I guess it ran out of memory?

Edit: I just reviewed https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13 and I think I missed the "plus 500 MB RAM for each concurrent job" part. This is running 30+ jobs at the same time over the weekend so my system is definitely under spec and will be increasing the memory to 48-GB, maybe 64-GB.

Also for Dev's consideration: How to Adjust Linux Out-Of-Memory Killer Settings for PostgreSQL: https://www.percona.com/blog/out-of-mem ... or-savior/ (I'd rather have jobs be terminated over everything going down)