search

linuxserver / docker-unifi-network-application

GNU General Public License v3.0
551 stars 40 forks source link

Does not work with Raspberry PI OS Bookworm 64bit as Mongo DB isn't compatible #61

Closed rjwill10 closed 5 months ago

rjwill10 commented 5 months ago

Is there an existing issue for this?

Current Behavior

Mongo DB is not compatible with Raspberry PI OS bookworm, therefore I cannot from the Unifi Controller

Expected Behavior

Should be able to upgrade from unifi controller that works with Raspberry Pi OS bookworm, if the controller is no longer supported.

Steps To Reproduce

  1. Set up a Raspberry PI with 64 bit Bookworm (lite)
  2. Install Open Media Vault 6 and docker
  3. Run docker compose, to build mongo DB & Unifi Network Application

Environment

- OS:Rasbperry Pi os 64bit Bookworm (lite)
- How docker service was installed: Via Open Media Vault 6, and managed with Portainer

CPU architecture

arm64

Docker creation

version: "2.1"

services:
  unifi-network-application:
    image: lscr.io/linuxserver/unifi-network-application:latest
    container_name: unifi-network-application
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - MONGO_USER=unifi
      - MONGO_PASS=cf838he32
      - MONGO_HOST=unifi
      - MONGO_PORT=27017
      - MONGO_DBNAME=unifi-db
      - MEM_LIMIT=1024
    volumes:
      - /srv/dev-disk-by-uuid-8cc7e31f-12f5-4677-8d91-b1c488a8bbf0/media/config/unifi:/config
    ports:
      - 8443:8443
      - 3478:3478/udp
      - 10001:10001/udp
      - 8080:8080
    labels:
      - "traefik.http.services.unifi.loadbalancer.server.port=8443"
      - "traefik.http.services.unifi.loadbalancer.server.scheme=https"
    networks:
      - unifi
    restart: unless-stopped

  unifi-db:
    image: docker.io/mongo:4.0 #have tried various versions up to 4.4
    container_name: unifi-db
    volumes:
      - /srv/dev-disk-by-uuid-8cc7e31f-12f5-4677-8d91-b1c488a8bbf0/media/config/unifi_db:/data/db
      - /srv/dev-disk-by-uuid-8cc7e31f-12f5-4677-8d91-b1c488a8bbf0/media/config/unifi_db/init-mongo.js:/docker-entrypoint-initdb.d/init-mongo.js:ro
    networks:
      - unifi
    restart: unless-stopped

networks:
  unifi:

Container logs

Successfully added user: {
    "user" : "unifi",

    "roles" : [
        {
            "role" : "dbOwner",
            "db" : "unifi_stat"
        }
    ]
}
2024-01-27T17:17:11.330+0000 I NETWORK  [conn2] end connection 127.0.0.1:54478 (0 connections now open)
2024-01-27T17:17:11.383+0000 I CONTROL  [main] ***** SERVER RESTARTED *****
2024-01-27T17:17:11.387+0000 I CONTROL  [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
killing process with pid: 30
2024-01-27T17:17:11.394+0000 I CONTROL  [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends
2024-01-27T17:17:11.394+0000 I CONTROL  [signalProcessingThread] Shutdown started
2024-01-27T17:17:11.394+0000 I REPL     [signalProcessingThread] Stepping down the ReplicationCoordinator for shutdown, waitTime: 10000ms
2024-01-27T17:17:11.394+0000 I CONTROL  [signalProcessingThread] Shutting down the LogicalSessionCache
2024-01-27T17:17:11.395+0000 I NETWORK  [signalProcessingThread] shutdown: going to close listening sockets...
2024-01-27T17:17:11.395+0000 I NETWORK  [signalProcessingThread] removing socket file: /tmp/mongodb-27017.sock
2024-01-27T17:17:11.397+0000 I NETWORK  [signalProcessingThread] Shutting down the global connection pool
2024-01-27T17:17:11.397+0000 I STORAGE  [signalProcessingThread] Shutting down the PeriodicThreadToAbortExpiredTransactions
2024-01-27T17:17:11.397+0000 I REPL     [signalProcessingThread] Shutting down the ReplicationCoordinator
2024-01-27T17:17:11.398+0000 I SHARDING [signalProcessingThread] Shutting down the ShardingInitializationMongoD
2024-01-27T17:17:11.398+0000 I COMMAND  [signalProcessingThread] Killing all open transactions
2024-01-27T17:17:11.398+0000 I -        [signalProcessingThread] Killing all operations for shutdown
2024-01-27T17:17:11.398+0000 I NETWORK  [signalProcessingThread] Shutting down the ReplicaSetMonitor
2024-01-27T17:17:11.398+0000 I CONTROL  [signalProcessingThread] Shutting down free monitoring
2024-01-27T17:17:11.398+0000 I CONTROL  [signalProcessingThread] Shutting down free monitoring
2024-01-27T17:17:11.399+0000 I FTDC     [signalProcessingThread] Shutting down full-time data capture
2024-01-27T17:17:11.399+0000 I FTDC     [signalProcessingThread] Shutting down full-time diagnostic data capture
2024-01-27T17:17:11.403+0000 I STORAGE  [signalProcessingThread] Shutting down the HealthLog
2024-01-27T17:17:11.404+0000 I STORAGE  [signalProcessingThread] Shutting down the storage engine
2024-01-27T17:17:11.404+0000 I STORAGE  [signalProcessingThread] WiredTigerKVEngine shutting down
2024-01-27T17:17:11.409+0000 I STORAGE  [signalProcessingThread] Shutting down session sweeper thread
2024-01-27T17:17:11.409+0000 I STORAGE  [signalProcessingThread] Finished shutting down session sweeper thread
2024-01-27T17:17:11.498+0000 I STORAGE  [signalProcessingThread] shutdown: removing fs lock...
2024-01-27T17:17:11.499+0000 I -        [signalProcessingThread] Dropping the scope cache for shutdown
2024-01-27T17:17:11.499+0000 I CONTROL  [signalProcessingThread] now exiting
2024-01-27T17:17:11.499+0000 I CONTROL  [signalProcessingThread] shutting down with code:0
MongoDB init process complete; ready for start up.
2024-01-27T17:17:12.506+0000 I CONTROL  [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
2024-01-27T17:17:12.514+0000 I CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=e54fa972db60
2024-01-27T17:17:12.514+0000 I CONTROL  [initandlisten] db version v4.0.28
2024-01-27T17:17:12.514+0000 I CONTROL  [initandlisten] git version: af1a9dc12adcfa83cc19571cb3faba26eeddac92
2024-01-27T17:17:12.514+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016
2024-01-27T17:17:12.514+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2024-01-27T17:17:12.514+0000 I CONTROL  [initandlisten] modules: none
2024-01-27T17:17:12.514+0000 I CONTROL  [initandlisten] build environment:
2024-01-27T17:17:12.514+0000 I CONTROL  [initandlisten]     distmod: ubuntu1604
2024-01-27T17:17:12.514+0000 I CONTROL  [initandlisten]     distarch: aarch64
2024-01-27T17:17:12.514+0000 I CONTROL  [initandlisten]     target_arch: aarch64
2024-01-27T17:17:12.514+0000 I CONTROL  [initandlisten] options: { net: { bindIpAll: true } }
2024-01-27T17:17:12.514+0000 I STORAGE  [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2024-01-27T17:17:12.515+0000 I STORAGE  [initandlisten] 
2024-01-27T17:17:12.515+0000 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
2024-01-27T17:17:12.515+0000 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
2024-01-27T17:17:12.515+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=3393M,cache_overflow=(file_max=0M),session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),
2024-01-27T17:17:13.451+0000 I STORAGE  [initandlisten] WiredTiger message [1706375833:451385][1:0x7f88819000], txn-recover: Main recovery loop: starting at 1/27520 to 2/256
2024-01-27T17:17:14.071+0000 I STORAGE  [initandlisten] WiredTiger message [1706375834:71953][1:0x7f88819000], txn-recover: Recovering log 1 through 2
2024-01-27T17:17:14.366+0000 I STORAGE  [initandlisten] WiredTiger message [1706375834:366562][1:0x7f88819000], txn-recover: Recovering log 2 through 2
2024-01-27T17:17:14.657+0000 I STORAGE  [initandlisten] WiredTiger message [1706375834:657691][1:0x7f88819000], txn-recover: Set global recovery timestamp: 0
2024-01-27T17:17:14.700+0000 I RECOVERY [initandlisten] WiredTiger recoveryTimestamp. Ts: Timestamp(0, 0)
2024-01-27T17:17:14.703+0000 I STORAGE  [initandlisten] Starting to check the table logging settings for existing WiredTiger tables
2024-01-27T17:17:14.710+0000 I CONTROL  [initandlisten] 
2024-01-27T17:17:14.710+0000 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
2024-01-27T17:17:14.710+0000 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
2024-01-27T17:17:14.710+0000 I CONTROL  [initandlisten] 
2024-01-27T17:17:14.719+0000 I STORAGE  [initandlisten] Finished adjusting the table logging settings for existing WiredTiger tables
2024-01-27T17:17:14.723+0000 I FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory '/data/db/diagnostic.data'
2024-01-27T17:17:14.729+0000 I NETWORK  [initandlisten] waiting for connections on port 27017
2024-01-27T17:19:17.957+0000 I CONTROL  [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends
2024-01-27T17:19:17.957+0000 I CONTROL  [signalProcessingThread] Shutdown started
2024-01-27T17:19:17.957+0000 I REPL     [signalProcessingThread] Stepping down the ReplicationCoordinator for shutdown, waitTime: 10000ms
2024-01-27T17:19:17.957+0000 I CONTROL  [signalProcessingThread] Shutting down the LogicalSessionCache
2024-01-27T17:19:17.958+0000 I NETWORK  [signalProcessingThread] shutdown: going to close listening sockets...
2024-01-27T17:19:17.958+0000 I NETWORK  [signalProcessingThread] removing socket file: /tmp/mongodb-27017.sock
2024-01-27T17:19:17.958+0000 I NETWORK  [signalProcessingThread] Shutting down the global connection pool
2024-01-27T17:19:17.958+0000 I STORAGE  [signalProcessingThread] Shutting down the PeriodicThreadToAbortExpiredTransactions
2024-01-27T17:19:17.958+0000 I REPL     [signalProcessingThread] Shutting down the ReplicationCoordinator
2024-01-27T17:19:17.958+0000 I SHARDING [signalProcessingThread] Shutting down the ShardingInitializationMongoD
2024-01-27T17:19:17.958+0000 I COMMAND  [signalProcessingThread] Killing all open transactions
2024-01-27T17:19:17.958+0000 I -        [signalProcessingThread] Killing all operations for shutdown
2024-01-27T17:19:17.958+0000 I NETWORK  [signalProcessingThread] Shutting down the ReplicaSetMonitor
2024-01-27T17:19:17.958+0000 I CONTROL  [signalProcessingThread] Shutting down free monitoring
2024-01-27T17:19:17.958+0000 I CONTROL  [signalProcessingThread] Shutting down free monitoring
2024-01-27T17:19:17.958+0000 I FTDC     [signalProcessingThread] Shutting down full-time data capture
2024-01-27T17:19:17.958+0000 I FTDC     [signalProcessingThread] Shutting down full-time diagnostic data capture
2024-01-27T17:19:17.963+0000 I STORAGE  [signalProcessingThread] Shutting down the HealthLog
2024-01-27T17:19:17.964+0000 I STORAGE  [signalProcessingThread] Shutting down the storage engine
2024-01-27T17:19:17.964+0000 I STORAGE  [signalProcessingThread] WiredTigerKVEngine shutting down
2024-01-27T17:19:17.964+0000 I STORAGE  [signalProcessingThread] Shutting down session sweeper thread
2024-01-27T17:19:17.964+0000 I STORAGE  [signalProcessingThread] Finished shutting down session sweeper thread
2024-01-27T17:19:18.058+0000 I STORAGE  [signalProcessingThread] shutdown: removing fs lock...
2024-01-27T17:19:18.058+0000 I -        [signalProcessingThread] Dropping the scope cache for shutdown
2024-01-27T17:19:18.058+0000 I CONTROL  [signalProcessingThread] now exiting
2024-01-27T17:19:18.058+0000 I CONTROL  [signalProcessingThread] shutting down with code:0
github-actions[bot] commented 5 months ago

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

j0nnymoe commented 5 months ago

Unfortunately there isn't anything we can do. You need to find a solution for getting Mongodb running on your raspbarry pi. Using something like this: https://github.com/themattman/mongodb-raspberrypi-docker