首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >‘错误:服务'BloxPager’没有启动。中止。`

‘错误:服务'BloxPager’没有启动。中止。`
EN

Stack Overflow用户
提问于 2015-11-27 21:58:57
回答 2查看 83关注 0票数 0

我使用64位Ubuntu14.04安装LogicBlox 3.10,当我尝试执行lb-services start时,它会提示我error: service 'BloxPager' did not start. Aborting.

下面是~/lb_deployment/logs/current/BloxPagerDaemon.log中的内容

代码语言:javascript
复制
<2015/11/27 05:33:51.079> ERROR. Shared memory is critically low and will prevent reliable functioning
<2015/11/27 05:33:51.079> ERROR. of the pager daemon. Details follow. 
<2015/11/27 05:33:51.079> ERROR. To force pager daemon start, set "LB_PAGER_FORCE_START" in your environment.
<2015/11/27 05:33:51.079> ERROR.  *  There is a problem with your machine configuration that could cause
<2015/11/27 05:33:51.079> ERROR.  *  performance or stability problems with large databases.  This machine has
<2015/11/27 05:33:51.079> ERROR.  *  8.3 Gb of memory, but only 4.2 Gb of memory is available as free disk
<2015/11/27 05:33:51.079> ERROR.  *  space in /dev/shm.  Ideally there would be 5.5 Gb of free space there.
<2015/11/27 05:33:51.079> ERROR.  *  There is a simple fix.  (1) By default linux configures /dev/shm to be
<2015/11/27 05:33:51.079> ERROR.  *  half the size of physical memory, which is too little for LogicBlox.
<2015/11/27 05:33:51.079> ERROR.  *  To increase it, edit (as root) the file /etc/fstab.  On the line for
<2015/11/27 05:33:51.079> ERROR.  *  tmpfs, replace the word "defaults" with "size=7g".  This change
<2015/11/27 05:33:51.079> ERROR.  *  will take effect on reboot.  (2) If /etc/fstab is already
<2015/11/27 05:33:51.079> ERROR.  *  configured properly, there are stale files in /dev/shm that should
<2015/11/27 05:33:51.079> ERROR.  *  be removed.  Or, another pager daemon is running (under a different
<2015/11/27 05:33:51.079> ERROR.  *  unix userid) that is using some shared memory

在/etc/fstab中,内容是

代码语言:javascript
复制
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=c5a6aaa0-9337-496f-b2d0-eda2d6e6c87e /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=e8cee437-3b01-4c83-abf6-6cd996e9e21f none            swap    sw              0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto,exec,utf8 0       0

我该怎么改呢?

顺便说一句,在/dev/shm中,我尝试删除除LB_ubuntu之外的所有内容,但似乎不起作用。

EN

回答 2

Stack Overflow用户

发布于 2015-11-27 23:46:19

在谷歌上快速搜索一下:http://forums.fedoraforum.org/showthread.php?t=275653

票数 0
EN

Stack Overflow用户

发布于 2015-11-27 23:49:29

您尝试过LB_PAGER_FORCE_START设置吗?

将以下行添加到您的.bashrc中将阻止该警告

导出LB_PAGER_FORCE_START="“

票数 0
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/33958984

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档