Postgresql pq:无法调整共享内存段的大小。设备上没有剩余空间
我在一个仪表板上有许多面板(大约6个),用于显示数据点图表,并对PostgreSQL数据库的停靠实例进行查询 面板工作正常,直到最近,一些面板停止工作并报告如下错误: pq:无法将共享内存段“/PostgreSQL.2058389254”调整为12615680字节:设备上没有剩余空间 知道为什么吗?如何解决这个问题。Docker容器在通过ssh访问的远程主机上运行 编辑 磁盘空间:Postgresql pq:无法调整共享内存段的大小。设备上没有剩余空间,postgresql,docker,grafana,Postgresql,Docker,Grafana,我在一个仪表板上有许多面板(大约6个),用于显示数据点图表,并对PostgreSQL数据库的停靠实例进行查询 面板工作正常,直到最近,一些面板停止工作并报告如下错误: pq:无法将共享内存段“/PostgreSQL.2058389254”调整为12615680字节:设备上没有剩余空间 知道为什么吗?如何解决这个问题。Docker容器在通过ssh访问的远程主机上运行 编辑 磁盘空间: $df -h Filesystem Size Used Avail Use% Mounted on /
$df -h
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 197G 140G 48G 75% /
devtmpfs 1.4G 0 1.4G 0% /dev
tmpfs 1.4G 4.0K 1.4G 1% /dev/shm
tmpfs 1.4G 138M 1.3G 10% /run
tmpfs 1.4G 0 1.4G 0% /sys/fs/cgroup
/dev/dm-16 10G 49M 10G 1% /var/lib/docker/devicemapper/mnt/a0f3c5ab84aa06d5b2db00c4324dd6bf7141500ff4c83e23e9aba7c7268bcad4
/dev/dm-1 10G 526M 9.5G 6% /var/lib/docker/devicemapper/mnt/8623a774d736ed3dc0d2db89b7d07cae85c3d1bcafc245180eec4ffd738f93a5
shm 64M 0 64M 0% /var/lib/docker/containers/260552ebcdf2bf0961329108d3d975110f8ada0a41325f5e7dd81b8ddad9d18b/mounts/shm
/dev/dm-4 10G 266M 9.8G 3% /var/lib/docker/devicemapper/mnt/6f873e62607e7cac4c4b658c72874c787b90290f74d1159eca81af61cb467cfb
shm 64M 50M 15M 78% /var/lib/docker/containers/84c66d9fb5b6ae023d051766f4d35ced87a519a1fee68ca5c89d61ff87cf1e5a/mounts/shm
/dev/dm-2 10G 383M 9.7G 4% /var/lib/docker/devicemapper/mnt/cb3df1ae654ed78802c2e5bd7a51a1b0bdd562855a7c7803750b80b33f5c206e
shm 64M 0 64M 0% /var/lib/docker/containers/22ba2ae2b6859c24623703dcb596527d64257d2d61de53f4d88e00a8e2335211/mounts/shm
/dev/dm-3 10G 99M 9.9G 1% /var/lib/docker/devicemapper/mnt/492a19fc8f3e254c4e5cc691c3300b5fee9d1a849422673bf0c19b4b2d1db571
shm 64M 0 64M 0% /var/lib/docker/containers/39abe855a9b107d4921807332309517697f024b2d169ebc5f409436208f766d0/mounts/shm
/dev/dm-7 10G 276M 9.8G 3% /var/lib/docker/devicemapper/mnt/55c6a6c17c892d149c1cc91fbf42b98f1340ffa30a1da508e3526af7060f3ce2
shm 64M 0 64M 0% /var/lib/docker/containers/bf2e7254cd7e2c6000da61875343580ec6ff5cbf40c017a398ba7479af5720ec/mounts/shm
/dev/dm-8 10G 803M 9.3G 8% /var/lib/docker/devicemapper/mnt/4e51f48d630041316edd925f1e20d3d575fce4bf19ef39a62756b768460d1a3a
shm 64M 0 64M 0% /var/lib/docker/containers/72d4ae743de490ed580ec9265ddf8e6b90e3a9d2c69bd74050e744c8e262b342/mounts/shm
/dev/dm-6 10G 10G 20K 100% /var/lib/docker/devicemapper/mnt/3dcddaee736017082fedb0996e42b4c7b00fe7b850d9a12c81ef1399fa00dfa5
shm 64M 0 64M 0% /var/lib/docker/containers/9f2bf4e2736d5128d6c240bb10da977183676c081ee07789bee60d978222b938/mounts/shm
/dev/dm-5 10G 325M 9.7G 4% /var/lib/docker/devicemapper/mnt/65a2bf48cbbfe42f0c235493981e62b90363b4be0a2f3aa0530bbc0b5b29dbe3
shm 64M 0 64M 0% /var/lib/docker/containers/e53d5ababfdefc5c8faf65a4b2d635e2543b5a807b65a4f3cd8553b4d7ef2d06/mounts/shm
/dev/dm-9 10G 1.2G 8.9G 12% /var/lib/docker/devicemapper/mnt/3216c48346c3702a5cd2f62a4737cc39666983b8079b481ab714cdb488400b08
shm 64M 0 64M 0% /var/lib/docker/containers/5cd0774a742f54c7c4fe3d4c1307fc93c3c097a861cde5f611a0fa9b454af3dd/mounts/shm
/dev/dm-10 10G 146M 9.9G 2% /var/lib/docker/devicemapper/mnt/6a98acd1428ae670e8f1da62cb8973653c8b11d1c98a8bf8be78f59d2ddba062
shm 64M 0 64M 0% /var/lib/docker/containers/a878042353f6a605167e7f9496683701fd2889f62ba1d6c0dc39c58bc03a8209/mounts/shm
tmpfs 285M 0 285M 0% /run/user/0
编辑-2
$df -ih
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/vda1 13M 101K 13M 1% /
devtmpfs 354K 394 353K 1% /dev
tmpfs 356K 2 356K 1% /dev/shm
tmpfs 356K 693 356K 1% /run
tmpfs 356K 16 356K 1% /sys/fs/cgroup
/dev/dm-16 10M 2.3K 10M 1% /var/lib/docker/devicemapper/mnt/a0f3c5ab84aa06d5b2db00c4324dd6bf7141500ff4c83e23e9aba7c7268bcad4
/dev/dm-1 10M 19K 10M 1% /var/lib/docker/devicemapper/mnt/8623a774d736ed3dc0d2db89b7d07cae85c3d1bcafc245180eec4ffd738f93a5
shm 356K 1 356K 1% /var/lib/docker/containers/260552ebcdf2bf0961329108d3d975110f8ada0a41325f5e7dd81b8ddad9d18b/mounts/shm
/dev/dm-4 10M 11K 10M 1% /var/lib/docker/devicemapper/mnt/6f873e62607e7cac4c4b658c72874c787b90290f74d1159eca81af61cb467cfb
shm 356K 2 356K 1% /var/lib/docker/containers/84c66d9fb5b6ae023d051766f4d35ced87a519a1fee68ca5c89d61ff87cf1e5a/mounts/shm
/dev/dm-2 10M 5.6K 10M 1% /var/lib/docker/devicemapper/mnt/cb3df1ae654ed78802c2e5bd7a51a1b0bdd562855a7c7803750b80b33f5c206e
shm 356K 1 356K 1% /var/lib/docker/containers/22ba2ae2b6859c24623703dcb596527d64257d2d61de53f4d88e00a8e2335211/mounts/shm
/dev/dm-3 10M 4.6K 10M 1% /var/lib/docker/devicemapper/mnt/492a19fc8f3e254c4e5cc691c3300b5fee9d1a849422673bf0c19b4b2d1db571
shm 356K 1 356K 1% /var/lib/docker/containers/39abe855a9b107d4921807332309517697f024b2d169ebc5f409436208f766d0/mounts/shm
/dev/dm-7 10M 7.5K 10M 1% /var/lib/docker/devicemapper/mnt/55c6a6c17c892d149c1cc91fbf42b98f1340ffa30a1da508e3526af7060f3ce2
shm 356K 1 356K 1% /var/lib/docker/containers/bf2e7254cd7e2c6000da61875343580ec6ff5cbf40c017a398ba7479af5720ec/mounts/shm
/dev/dm-8 10M 12K 10M 1% /var/lib/docker/devicemapper/mnt/4e51f48d630041316edd925f1e20d3d575fce4bf19ef39a62756b768460d1a3a
shm 356K 1 356K 1% /var/lib/docker/containers/72d4ae743de490ed580ec9265ddf8e6b90e3a9d2c69bd74050e744c8e262b342/mounts/shm
/dev/dm-6 7.9K 7.3K 623 93% /var/lib/docker/devicemapper/mnt/3dcddaee736017082fedb0996e42b4c7b00fe7b850d9a12c81ef1399fa00dfa5
shm 356K 1 356K 1% /var/lib/docker/containers/9f2bf4e2736d5128d6c240bb10da977183676c081ee07789bee60d978222b938/mounts/shm
/dev/dm-5 10M 27K 10M 1% /var/lib/docker/devicemapper/mnt/65a2bf48cbbfe42f0c235493981e62b90363b4be0a2f3aa0530bbc0b5b29dbe3
shm 356K 1 356K 1% /var/lib/docker/containers/e53d5ababfdefc5c8faf65a4b2d635e2543b5a807b65a4f3cd8553b4d7ef2d06/mounts/shm
/dev/dm-9 10M 53K 10M 1% /var/lib/docker/devicemapper/mnt/3216c48346c3702a5cd2f62a4737cc39666983b8079b481ab714cdb488400b08
shm 356K 1 356K 1% /var/lib/docker/containers/5cd0774a742f54c7c4fe3d4c1307fc93c3c097a861cde5f611a0fa9b454af3dd/mounts/shm
/dev/dm-10 10M 5.2K 10M 1% /var/lib/docker/devicemapper/mnt/6a98acd1428ae670e8f1da62cb8973653c8b11d1c98a8bf8be78f59d2ddba062
shm 356K 1 356K 1% /var/lib/docker/containers/a878042353f6a605167e7f9496683701fd2889f62ba1d6c0dc39c58bc03a8209/mounts/shm
tmpfs 356K 1 356K 1% /run/user/0
编辑-3
postgres
集装箱服务:
version: "3.5"
services:
#other containers go here..
postgres:
restart: always
image: postgres:10
hostname: postgres
container_name: fiware-postgres
expose:
- "5432"
ports:
- "5432:5432"
networks:
- default
environment:
- "POSTGRES_PASSWORD=password"
- "POSTGRES_USER=postgres"
- "POSTGRES_DB=postgres"
volumes:
- ./postgres-data:/var/lib/postgresql/data
build:
context: .
shm_size: '4gb'
数据库大小:
postgres=# SELECT pg_size_pretty( pg_database_size('postgres'));
pg_size_pretty
----------------
42 GB
(1 row)
编辑-4
很抱歉,但是与此问题相关的解决方案实际上都不起作用,包括
在仪表板上,我有5个面板用于显示数据点。查询类似,只是每个查询都显示不同的参数,如温度
,相对湿度
,照度
,粒子
和O3
。以下是查询:
SELECT to_timestamp(floor((extract('epoch' from recvtime)/ 1800 )) * 1800) as time,
avg(attrvalue::float) as illuminance
FROM urbansense.weather WHERE attrname='illuminance' AND attrvalue<>'null' GROUP BY time ORDER BY time asc;
有人知道如何解决这个问题吗?这是因为docker将共享内存的大小限制为64MB
您可以使用docker run
中的--shm size
选项覆盖此默认值
docker run-itd--shm size=1g postgres
或在docker compose中:
db:
图片:“postgres:11.3-alpine”
shm_尺寸:1g
退房。更多信息
希望这能有所帮助。您需要使用更大的shm\U尺寸构建新图像 Dockerfile
FROM postgres:10.7
docker-compose.release.yml
version: '3.7'
services:
postgres:
image: registry.my-site.com/postgres:latest
build:
shm_size: '4gb'
跑
然后你可以使用你的image
registry.my site.com/postgres:latest
来部署增加了shm\u大小的容器。建立一个新的形象是没有必要的。但必须确保重新创建了容器,并且没有使用旧容器。
Docker compose文件必须更改为,在服务级别添加shm_size
。构建部分不是必需的
version: "3.5"
services:
#other containers go here..
postgres:
restart: always
image: postgres:10
#THIS MUST BE ADDED AT SERVICE LEVEL
shm_size: 1gb
hostname: postgres
container_name: fiware-postgres
expose:
- "5432"
ports:
- "5432:5432"
networks:
- default
environment:
- "POSTGRES_PASSWORD=password"
- "POSTGRES_USER=postgres"
- "POSTGRES_DB=postgres"
volumes:
- ./postgres-data:/var/lib/postgresql/data
那你必须这么做
docker-compose down
docker-compose up -d
销毁旧容器并创建新容器
您可以检查容器内的更改(使用docker compose exec postgres bash
输入)并运行df-h|grep shm
参考:您可以通过重新安装来增加shm大小,而无需重新启动/重建容器
mount -o remount,size=256m -t tmpfs /var/lib/docker/containers/your-container-id/mounts/shm
更改您的容器id和所需大小(256m)您检查过硬盘了吗?你真的有空闲空间吗?@MostafaHussein是的,我有足够的磁盘空间(大约50GB可用)从问题编辑中可以看出。您需要检查postgresql配置中的共享内存设置以及docker/host设置施加的任何共享内存限制。您可以检查inode消耗量df-ih
@mchawre我检查了问题编辑-2。修改了撰写文件添加shm_大小:“4gb”
,这并不能解决问题(问题3)。这是否与容器卷或docker工作内存有关?因为我的数据库大小超过40GB,这在edit-3上可以看到。但是在这次更改之后,您是否得到了相同的pq:cannotresizesharedmemory segment
错误?是的,我仍然得到它。甚至将shm_size:'50gb'
无更改,最近:pq:cannot resize shared memory segment”/PostgreSQL.1336373456“设置为12615680字节:设备上没有剩余空间
Hve您遇到过类似的问题吗?如果可能,请尝试上述解决方案。我也有同样的问题,而且这似乎不是数据库设置(工作人员、内存等)的问题。除了docker compose down
之外,您还可以执行docker compose rm postgres
来删除预先存在的postgres容器。无需构建自定义映像,因为这是容器创建期间的设置(docker run--rm-it--shm size 2gb…
)。效果很好!正在检查一个长时间运行的进程,我不想中断,共享内存不足。尝试一下,它就成功了。最好在docker-compose.yml中添加shm_size:256m
。有时在重新启动容器后,我需要重新安装它。不知道为什么,但它发生了,但我的任务还是崩溃了。目前,这是一个快速的解决方案。
docker-compose down
docker-compose up -d
mount -o remount,size=256m -t tmpfs /var/lib/docker/containers/your-container-id/mounts/shm