-
Notifications
You must be signed in to change notification settings - Fork 21
Sucks ram on OVH Dedicated #124
Comments
Hi :) But I can't reproduce your error. Also , where were your servers located ? |
Hi, Same problem here on a Debian server located to GRA2 since 23/08/21.
Any advice? |
Hi :) |
root@XXXXX:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster
root@XXXXX:~# beamium --version
beamium version 2.0.8 d5c883fce3123054f6f54cb93e037ea20f1745e8
beamium build date 2021-07-15T12:30:16Z
beamium profile release
root@server:~# cat /etc/beamium/config.yaml
## noderig endpoint to fetch
scrapers:
noderig:
url: http://127.0.0.1:9100/metrics
format: sensision
period: 60000
## Warp10 platform to send data
sinks:
rtm:
url: https://rtm.ovh.net/
token: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
size: 1000000
selector: (os|rtm).*
ttl: 60
labels:
host: XXXXXXXXXXXXXXXX
parameters: # Parameters definitions (Optional)
source-dir: /opt/beamium/sources # Beamer data source directory
sink-dir: /opt/beamium/sinks # Beamer data sink directory
scan-period: 60000 # Delay(ms) between source/sink scan
log-file: /var/log/beamium/beamium.log # Log file
log-level: 1 # Log level
router-parallel: 1 # Routing threads
backoff: # Backoff configuration
initial: 30000ms # Initial interval
max: 1m # Max interval
multiplier: 1.5 # Interval multiplier
randomization: 0.3 # Randomization factor - delay = interval * 0.3
root@XXXXX:~# |
Seems I have more than 100k files into this directory on the server. root@XXXXX:~# ls -alhrt /opt/beamium/sources/ | wc -l
101188
root@XXXXX:~# ls -alhrt /opt/beamium/sources/ | head
total 8,3G
drwxr-xr-x 4 beamium beamium 4,0K nov. 23 2020 ..
-rw-r--r-- 1 beamium beamium 84K nov. 23 2020 noderig-1606144579919617-0.metrics
-rw-r--r-- 1 beamium beamium 84K nov. 23 2020 noderig-1606144639934709-0.metrics
-rw-r--r-- 1 beamium beamium 84K nov. 23 2020 noderig-1606144699924242-0.metrics
-rw-r--r-- 1 beamium beamium 84K nov. 23 2020 noderig-1606144759924601-0.metrics
-rw-r--r-- 1 beamium beamium 84K nov. 23 2020 noderig-1606144819924640-0.metrics
-rw-r--r-- 1 beamium beamium 84K nov. 23 2020 noderig-1606144879924126-0.metrics
-rw-r--r-- 1 beamium beamium 84K nov. 23 2020 noderig-1606144939924516-0.metrics
-rw-r--r-- 1 beamium beamium 84K nov. 23 2020 noderig-1606144999931893-0.metrics
root@XXXXX:~# ls -alhrt /opt/beamium/sources/ | tail
-rw-r--r-- 1 beamium beamium 61K sept. 15 13:13 noderig-1631704393794688-0.metrics
-rw-r--r-- 1 beamium beamium 61K sept. 15 13:14 noderig-1631704453794864-0.metrics
-rw-r--r-- 1 beamium beamium 61K sept. 15 13:15 noderig-1631704513794995-0.metrics
-rw-r--r-- 1 beamium beamium 61K sept. 15 13:16 noderig-1631704573791051-0.metrics
-rw-r--r-- 1 beamium beamium 61K sept. 15 13:17 noderig-1631704633795381-0.metrics
-rw-r--r-- 1 beamium beamium 61K sept. 15 13:18 noderig-1631704693790825-0.metrics
-rw-r--r-- 1 beamium beamium 61K sept. 15 13:19 noderig-1631704753790808-0.metrics
-rw-r--r-- 1 beamium beamium 61K sept. 15 13:20 noderig-1631704813787855-0.metrics
-rw-r--r-- 1 beamium beamium 61K sept. 15 13:21 noderig-1631704873794797-0.metrics
drwxr-xr-x 2 beamium beamium 6,2M sept. 15 13:21 .
root@XXXXX:~# It's safe to remove? |
Without response, I remove all files and beamium running fine again without eating all server's memory. But it do not seem to clean old file so I end to add a cronjob to delete file older than one day find /opt/beamium/sources/ -ctime +1 -delete |
Hi,
Beamium is sucking 40% / 80% of my RAM on 3 dedicated servers (32Go / 64Go)
Uptime 31 days
The text was updated successfully, but these errors were encountered: