No space left on device

Linux / Dimension ver. 2.1.1-u2

I have several different message from my Dimension Server this weekend.
It started with;

The Log Server is unable to connect to the database; retrying.
First attempt: 2020-10-25 16:43:24
Last attempt: 2020-10-25 20:43:52
Most recent database error message:
FATAL: could not access status of transaction 0
DETAIL: Could not write to file "pg_subtrans/09F9" at offset 65536: No space left on device.

I'm using the 'built-in database'.
** I checked by Database Status;
Disk Usage - 60.36GB of 63GB used by database (15GB free on disk)
*** I logged into my VMWare and for my Dimension:
Provisioned storage - 250.46 GB
Not-shared storage - 245.21 GB
Used Storage - 245.21 GB
? Why the difference in storage numbers between Dimension Database Status and what shows in VMWare Provisioned Storage?

Then I got this, thinking all was ok.
The Log Server successfully connected to the database.
Connect Time: 2020-10-25 20:49:02

Then this one showed up again but I thought I "disabled" the disconnected firebox.
No heartbeat detected from Log Collector since 2020-10-26 05:09:01 UTC.
** I assumed the "No Heartbeat" was because I recently disconnected a XTM 515 and switched to a M370 but I still have a 2nd XTM 515 running.
Why doesn't it refer to which 'heartbeat' isn't detected or isn't this referring to a firebox?
--- I did 'delete', from Dimension, the disconnected XTM 515 this morning but I still have one XTM 515 and one M370 logging to Dimension.

Then I got this
The Log Server is unable to connect to the database; retrying.
First attempt: 2020-10-26 01:59:21
Last attempt: 2020-10-26 01:59:21
Most recent database error message:
FATAL: out of shared memory
HINT: You may need to increase max_locks_per_transaction.

Is this an indication of some serious problems with my Dimension?

I managed to get this working a few years ago but I'm not a VM Ware person nor am I a Linux person. So I'm kinda lost at where to start with this.

Any help would be appreciated.


Sign In to comment.