【问题标题】:How to fix 'mongod[10993]: Error reading config file: No such file or directory' in Ubuntu 18.04如何修复 'mongod[10993]: Error reading config file: No such file or directory' in Ubuntu 18.04
【发布时间】:2019-12-11 08:51:33
【问题描述】:

我在为我的 Flask 应用程序设置 MongoDB 数据库时遇到问题,你们知道如何解决这个问题吗?

我已经尝试重新启动并重新安装它。

● mongodb.service - MongoDB Database
 Loaded: loaded (/etc/systemd/system/mongodb.service; enabled; 
 vendor preset: enabled)
 Active: failed (Result: exit-code) since Sat 2019-08-03 01:43:03 
 PST; 5s ago
 Docs: https://docs.mongodb.org/manual
 Process: 10993 ExecStart=/usr/bin/mongod --quiet --config 
 /etc/mongod.conf (code=exited, status=2)
 Main PID: 10993 (code=exited, status=2)

 Aug 03 01:43:03 linux-ubuntu-robert-terminal systemd[1]: Started 
 MongoDB Database.
 Aug 03 01:43:03 linux-ubuntu-robert-terminal mongod[10993]: Error 
 reading config file: No such file or directory
 Aug 03 01:43:03 linux-ubuntu-robert-terminal mongod[10993]: try 
 '/usr/bin/mongod --help' for more information
 Aug 03 01:43:03 linux-ubuntu-robert-terminal systemd[1]: 
 mongodb.service: Main process exited, code=exited, 
 status=2/INVALIDARGUMENT
 Aug 03 01:43:03 linux-ubuntu-robert-terminal systemd[1]: 
 mongodb.service: Failed with result 'exit-code'.

【问题讨论】:

    标签: python mongodb flask pymongo


    【解决方案1】:

    我知道它有点老了,但我在 Linux Mint 19.2 上遇到了同样的问题。

    为了解决这个问题,我根据documentation - Configuration File Options 创建了配置文件“/etc/mongod.conf”。 从 Windows 复制的内容,它是通过安装自动创建的。

    # mongodb.conf
    
    # Where to store the data.
    dbpath=/var/lib/mongodb
    
    #where to log
    logpath=/var/log/mongodb/mongodb.log
    
    logappend=true
    
    bind_ip = 127.0.0.1
    #port = 27017
    
    # Enable journaling, http://www.mongodb.org/display/DOCS/Journaling
    journal=true
    
    # Enables periodic logging of CPU utilization and I/O wait
    #cpu = true
    
    # Turn on/off security.  Off is currently the default
    #noauth = true
    #auth = true
    
    # Verbose logging output.
    #verbose = true
    
    # Inspect all client data for validity on receipt (useful for
    # developing drivers)
    #objcheck = true
    
    # Enable db quota management
    #quota = true
    
    # Set diagnostic logging level where n is
    #   0=off (default)
    #   1=W
    #   2=R
    #   3=both
    #   7=W+some reads
    #diaglog = 0
    
    # Diagnostic/debugging option
    #nocursors = true
    
    # Ignore query hints
    #nohints = true
    
    # Disable the HTTP interface (Defaults to localhost:27018).
    #nohttpinterface = true
    
    # Turns off server-side scripting.  This will result in greatly limited
    # functionality
    #noscripting = true
    
    # Turns off table scans.  Any query that would do a table scan fails.
    #notablescan = true
    
    # Disable data file preallocation.
    #noprealloc = true
    
    # Specify .ns file size for new databases.
    # nssize = <size>
    
    # Accout token for Mongo monitoring server.
    #mms-token = <token>
    
    # Server name for Mongo monitoring server.
    #mms-name = <server-name>
    
    # Ping interval for Mongo monitoring server.
    #mms-interval = <seconds>
    
    # Replication Options
    
    # in replicated mongo databases, specify here whether this is a slave or master
    #slave = true
    #source = master.example.com
    # Slave only: specify a single database to replicate
    #only = master.example.com
    # or
    #master = true
    #source = slave.example.com
    
    # Address of a server to pair with.
    #pairwith = <server:port>
    # Address of arbiter server.
    #arbiter = <server:port>
    # Automatically resync if slave data is stale
    #autoresync
    # Custom size for replication operation log.
    #oplogSize = <MB>
    # Size limit for in-memory storage of op ids.
    #opIdMem = <bytes>
    
    # SSL options
    # Enable SSL on normal ports
    #sslOnNormalPorts = true
    # SSL Key file and password
    #sslPEMKeyFile = /etc/ssl/mongodb.pem
    #sslPEMKeyPassword = pass
    

    保存配置文件后重启mongodb服务:

    sudo systemctl restart mongodb
    

    【讨论】:

    • 我不明白为什么有些 mongod.conf 文件采用上述格式(有效)而其他文件采用 YAML 格式(永远无效)
    猜你喜欢
    • 1970-01-01
    • 2022-07-11
    • 1970-01-01
    • 2023-04-03
    • 2017-02-08
    • 2012-06-03
    • 1970-01-01
    • 2019-07-23
    • 2018-11-22
    相关资源
    最近更新 更多