Comment 3 for bug 2073050

Revision history for this message
Gary.Wang (gary-wzl77) wrote :

When deploying anbox cloud appliance on a VM(Ubuntu22.04|arm64) launched from the MAAS, a similar problem also occurred.
```
Installing Juju machine agent
2024-07-15 09:47:29 INFO juju.cmd supercommand.go:56 running jujud [2.9.42 7b871e782195bdac9c90f8a8f01723cc3e08ab92 gc go1.19.6]
2024-07-15 09:47:30 INFO juju.agent identity.go:22 writing system identity file
2024-07-15 09:47:30 ERROR juju.mongo mongo.go:651 could not set the value of "/sys/kernel/mm/transparent_hugepage/enabled" to "never" because of: open /sys/kernel/mm/transparent_hugepage/enabled: permission denied
2024-07-15 09:47:30 ERROR juju.mongo mongo.go:651 could not set the value of "/sys/kernel/mm/transparent_hugepage/defrag" to "never" because of: open /sys/kernel/mm/transparent_hugepage/defrag: permission denied
2024-07-15 09:47:30 ERROR juju.mongo mongo.go:651 could not set the value of "/proc/sys/net/core/somaxconn" to "16384" because of: "/proc/sys/net/core/somaxconn" does not exist, will not set "16384"
2024-07-15 09:47:30 ERROR juju.mongo mongo.go:651 could not set the value of "/proc/sys/net/core/netdev_max_backlog" to "1000" because of: "/proc/sys/net/core/netdev_max_backlog" does not exist, will not set "1000"
2024-07-15 09:47:30 WARNING juju.mongo mongo.go:481 overwriting args.dataDir (set to /var/lib/juju) to /var/snap/juju-db/common
2024-07-15 09:47:30 INFO juju.mongo mongo.go:486 Ensuring mongo server is running; data directory /var/snap/juju-db/common; port 37017
2024-07-15 09:47:30 WARNING juju.mongo service.go:323 configuring mongod with --noauth flag enabled
2024-07-15 09:47:30 INFO juju.packaging manager.go:103 installing "juju-db" via "snap"
2024-07-15 09:47:30 INFO juju.packaging.manager run.go:88 Running: snap install --channel 4.4/stable juju-db
ERROR failed to start mongo: juju-db snap not installed correctly. Executable /snap/bin/juju-db.mongod
Error: signal: illegal instruction (core dumped)
ERROR failed to bootstrap model: subprocess encountered error code 1
```