Nextcloud gets stuck in state deploying / "no destination available" in syslog

nestor_78 · April 20, 2024, 8:33am

Hi,
tried to update nextcloud. Nextcloud gets stuck in state deploying. Other apps can be stopped and restarted.

TrueNAS-SCALE-23.10.2

nextcloud
App Version: 28.0.4
Chart Version: 1.6.59

Charts could be refreshed - did no change behaviour of nextcloud.

Checked /var/log/syslog which showed endlessly lines:
Apr 20 10:23:06 truenas kernel: IPVS: rr: TCP 172.18.186.38:5432 - no destination available

Then stopped other apps (homar, ngix, pihole) → in syslog the above mentioned line continues to be logged.

Then stopped nextcloud → the line mentioned above stopps to be logged.

Then restarted nextcloud, which again gets stuck in state deploying. Syslog shows the following including the “no destination available”-line again:

Apr 20 10:27:53 truenas systemd[1]: Created slice kubepods-besteffort-pod29fd378e_caa0_4fd7_ac99_424fc2e89aae.slice - libcontainer container kubepods-besteffort-pod29fd378e_caa0_4fd7_ac99_424fc2e89aae.slice.
Apr 20 10:27:53 truenas systemd[1]: Created slice kubepods-besteffort-pod046ac6cc_15a4_489e_93b0_84e003ea1e44.slice - libcontainer container kubepods-besteffort-pod046ac6cc_15a4_489e_93b0_84e003ea1e44.slice.
Apr 20 10:27:53 truenas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb75290bb: link becomes ready
Apr 20 10:27:53 truenas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Apr 20 10:27:53 truenas kernel: kube-bridge: port 1(vethb75290bb) entered blocking state
Apr 20 10:27:53 truenas kernel: kube-bridge: port 1(vethb75290bb) entered disabled state
Apr 20 10:27:53 truenas kernel: device vethb75290bb entered promiscuous mode
Apr 20 10:27:53 truenas kernel: kube-bridge: port 1(vethb75290bb) entered blocking state
Apr 20 10:27:53 truenas kernel: kube-bridge: port 1(vethb75290bb) entered forwarding state
Apr 20 10:27:54 truenas systemd[1]: Started cri-containerd-233592d7261e9b9bca7f63e5fa104be909f27e98f497c8a4168788bb975472a1.scope - libcontainer container 233592d7261e9b9bca7f63e5fa104be909f27e98f497c8a4168788bb975472a1.
Apr 20 10:27:54 truenas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Apr 20 10:27:54 truenas kernel: kube-bridge: port 4(veth1bab9f6b) entered blocking state
Apr 20 10:27:54 truenas kernel: kube-bridge: port 4(veth1bab9f6b) entered disabled state
Apr 20 10:27:54 truenas kernel: device veth1bab9f6b entered promiscuous mode
Apr 20 10:27:54 truenas kernel: kube-bridge: port 4(veth1bab9f6b) entered blocking state
Apr 20 10:27:54 truenas kernel: kube-bridge: port 4(veth1bab9f6b) entered forwarding state
Apr 20 10:27:54 truenas systemd[1]: Started cri-containerd-27c08f18118db70e76228ecfdff79d7b35467066e2bc17969a9ee3416fb86d93.scope - libcontainer container 27c08f18118db70e76228ecfdff79d7b35467066e2bc17969a9ee3416fb86d93.
Apr 20 10:27:54 truenas systemd[1]: mnt-VM\x2dAPPS-ix\x2dapplications-k3s-agent-containerd-tmpmounts-containerd\x2dmount1333425883.mount: Deactivated successfully.
Apr 20 10:27:54 truenas systemd[1]: Started cri-containerd-fa97ec462ff493d0c21479d1b8bd6763419760909f87b0de108cf9492aa0b0c0.scope - libcontainer container fa97ec462ff493d0c21479d1b8bd6763419760909f87b0de108cf9492aa0b0c0.
Apr 20 10:27:54 truenas kernel: IPVS: rr: TCP 172.18.70.141:5432 - no destination available
Apr 20 10:27:56 truenas systemd[1]: Started cri-containerd-34cb18b2b2627f98e14157c7e7a8f913efae9c9743e37a1a6eb5208f14265b14.scope - libcontainer container 34cb18b2b2627f98e14157c7e7a8f913efae9c9743e37a1a6eb5208f14265b14.
Apr 20 10:27:56 truenas kernel: Process 25(postgres) has RLIMIT_CORE set to 1
Apr 20 10:27:56 truenas kernel: Aborting core
Apr 20 10:27:56 truenas systemd[1]: cri-containerd-34cb18b2b2627f98e14157c7e7a8f913efae9c9743e37a1a6eb5208f14265b14.scope: Deactivated successfully.
Apr 20 10:27:56 truenas systemd[1]: run-k3s-containerd-io.containerd.runtime.v2.task-k8s.io-34cb18b2b2627f98e14157c7e7a8f913efae9c9743e37a1a6eb5208f14265b14-rootfs.mount: Deactivated successfully.
Apr 20 10:27:56 truenas kernel: IPVS: rr: TCP 172.18.70.141:5432 - no destination available
Apr 20 10:27:58 truenas kernel: IPVS: rr: TCP 172.18.70.141:5432 - no destination available
Apr 20 10:28:00 truenas kernel: IPVS: rr: TCP 172.18.70.141:5432 - no destination available
Apr 20 10:28:02 truenas systemd[1]: Started cri-containerd-cf50a370468c5fca0c0d0cef4cf8c886b4a6d1d34247f2e7f271404338695055.scope - libcontainer container cf50a370468c5fca0c0d0cef4cf8c886b4a6d1d34247f2e7f271404338695055.
Apr 20 10:28:02 truenas kernel: Process 25(postgres) has RLIMIT_CORE set to 1
Apr 20 10:28:02 truenas kernel: Aborting core
Apr 20 10:28:02 truenas systemd[1]: cri-containerd-cf50a370468c5fca0c0d0cef4cf8c886b4a6d1d34247f2e7f271404338695055.scope: Deactivated successfully.
Apr 20 10:28:02 truenas systemd[1]: run-containerd-runc-k8s.io-cf50a370468c5fca0c0d0cef4cf8c886b4a6d1d34247f2e7f271404338695055-runc.TYbUcT.mount: Deactivated successfully.
Apr 20 10:28:02 truenas systemd[1]: run-k3s-containerd-io.containerd.runtime.v2.task-k8s.io-cf50a370468c5fca0c0d0cef4cf8c886b4a6d1d34247f2e7f271404338695055-rootfs.mount: Deactivated successfully.
Apr 20 10:28:03 truenas kernel: IPVS: rr: TCP 172.18.70.141:5432 - no destination available

Does anyone know how to fix this?

Best regards,
Nestor

nestor_78 · April 20, 2024, 8:55am

Addional info

sudo k3s kubectl cluster-info dump shows:

m0pegasus · April 21, 2024, 7:30am

same issue here any fix please

nestor_78 · April 23, 2024, 8:49am

Hi,

are you using a certificate for nextcloud?

I suspected that the problem had to do with the fact that I had selected a certificate in the nexcloud configuration.

I therefore stopped nextcloud and then deleted the certificate entry in the nextcloud configuration and confirmed with save.

I then started nextcloud again and it initially looked as if nextcloud had reached running status.

Then I tried to load the gui of nextcloud in webbroser.

However, I received the error message “The server at xxx.xxx.xxx.xxx is taking too long to send a response.”

Then I looked again in truenas apps menu and nextcloud was back in status “deploying”.

So it may be that the issue has nothing to do with certificates.

Best regards,
Nestor

nestor_78 · April 23, 2024, 10:29am

I checked what is written to syslog:

I stopped nextcloud again.

Then I saved the config of nextcloud. The following is logged:

Apr 23 10:54:59 truenas systemd[1]: Created slice kubepods-besteffort-podf4fdab42_e580_4783_bc8f_2494e0e21c81.slice - libcontainer container kubepods-besteffort-podf4fdab42_e580_4783_bc8f_2494e0e21c81.slice.
Apr 23 10:54:59 truenas systemd[1]: Created slice kubepods-besteffort-pod8042a110_0d58_425f_94ca_e78b1e978212.slice - libcontainer container kubepods-besteffort-pod8042a110_0d58_425f_94ca_e78b1e978212.slice.
Apr 23 10:55:00 truenas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethcfa3d595: link becomes ready
Apr 23 10:55:00 truenas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Apr 23 10:55:00 truenas kernel: kube-bridge: port 1(vethcfa3d595) entered blocking state
Apr 23 10:55:00 truenas kernel: kube-bridge: port 1(vethcfa3d595) entered disabled state
Apr 23 10:55:00 truenas kernel: device vethcfa3d595 entered promiscuous mode
Apr 23 10:55:00 truenas kernel: kube-bridge: port 1(vethcfa3d595) entered blocking state
Apr 23 10:55:00 truenas kernel: kube-bridge: port 1(vethcfa3d595) entered forwarding state
Apr 23 10:55:00 truenas kernel: kube-bridge: port 4(vethbde11198) entered blocking state
Apr 23 10:55:00 truenas kernel: kube-bridge: port 4(vethbde11198) entered disabled state
Apr 23 10:55:00 truenas kernel: device vethbde11198 entered promiscuous mode
Apr 23 10:55:00 truenas kernel: kube-bridge: port 4(vethbde11198) entered blocking state
Apr 23 10:55:00 truenas kernel: kube-bridge: port 4(vethbde11198) entered forwarding state
Apr 23 10:55:00 truenas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Apr 23 10:55:00 truenas systemd[1]: Started cri-containerd-7bd39655d792bb8bb7768ea0fac74591478f521d59f93856e56ee4f25b291a54.scope - libcontainer container 7bd39655d792bb8bb7768ea0fac74591478f521d59f93856e56ee4f25b291a54.
Apr 23 10:55:00 truenas systemd[1]: Started cri-containerd-ee910032d74ca71bf76af7550ec3dda1a68d9dea6742ade4126aeba5438bc1c0.scope - libcontainer container ee910032d74ca71bf76af7550ec3dda1a68d9dea6742ade4126aeba5438bc1c0.
Apr 23 10:55:00 truenas systemd[1]: tmp-ctd\x2dvolume3492676350.mount: Deactivated successfully.
Apr 23 10:55:00 truenas systemd[1]: mnt-VM\x2dAPPS-ix\x2dapplications-k3s-agent-containerd-tmpmounts-containerd\x2dmount3273595365.mount: Deactivated successfully.
Apr 23 10:55:01 truenas systemd[1]: Started cri-containerd-89a675f057b39fa645c360ea0c624f3c703976d8fac5ad22cee01d118b7d192e.scope - libcontainer container 89a675f057b39fa645c360ea0c624f3c703976d8fac5ad22cee01d118b7d192e.
Apr 23 10:55:01 truenas kernel: IPVS: rr: TCP 172.18.163.111:5432 - no destination available
Apr 23 10:55:03 truenas kernel: IPVS: rr: TCP 172.18.163.111:5432 - no destination available
Apr 23 10:55:04 truenas systemd[1]: mnt-VM\x2dAPPS-ix\x2dapplications-k3s-agent-containerd-tmpmounts-containerd\x2dmount1211241989.mount: Deactivated successfully.
Apr 23 10:55:04 truenas systemd[1]: mnt-VM\x2dAPPS-ix\x2dapplications-k3s-agent-containerd-tmpmounts-containerd\x2dmount3990699614.mount: Deactivated successfully.
Apr 23 10:55:04 truenas systemd[1]: Started cri-containerd-b361363ebd2a4843117941cfe0ab8f04ff51570e352850b65fae49d3a5c2aeec.scope - libcontainer container b361363ebd2a4843117941cfe0ab8f04ff51570e352850b65fae49d3a5c2aeec.
Apr 23 10:55:04 truenas kernel: Process 25(postgres) has RLIMIT_CORE set to 1
Apr 23 10:55:04 truenas kernel: Aborting core
Apr 23 10:55:04 truenas systemd[1]: cri-containerd-b361363ebd2a4843117941cfe0ab8f04ff51570e352850b65fae49d3a5c2aeec.scope: Deactivated successfully.
Apr 23 10:55:05 truenas systemd[1]: cri-containerd-89a675f057b39fa645c360ea0c624f3c703976d8fac5ad22cee01d118b7d192e.scope: Deactivated successfully.
Apr 23 10:55:05 truenas systemd[1]: cri-containerd-7bd39655d792bb8bb7768ea0fac74591478f521d59f93856e56ee4f25b291a54.scope: Deactivated successfully.
Apr 23 10:55:05 truenas systemd[1]: run-k3s-containerd-io.containerd.runtime.v2.task-k8s.io-b361363ebd2a4843117941cfe0ab8f04ff51570e352850b65fae49d3a5c2aeec-rootfs.mount: Deactivated successfully.
Apr 23 10:55:05 truenas systemd[1]: run-k3s-containerd-io.containerd.runtime.v2.task-k8s.io-89a675f057b39fa645c360ea0c624f3c703976d8fac5ad22cee01d118b7d192e-rootfs.mount: Deactivated successfully.
Apr 23 10:55:05 truenas systemd[1]: run-k3s-containerd-io.containerd.grpc.v1.cri-sandboxes-7bd39655d792bb8bb7768ea0fac74591478f521d59f93856e56ee4f25b291a54-shm.mount: Deactivated successfully.
Apr 23 10:55:05 truenas systemd[1]: run-k3s-containerd-io.containerd.grpc.v1.cri-sandboxes-ee910032d74ca71bf76af7550ec3dda1a68d9dea6742ade4126aeba5438bc1c0-shm.mount: Deactivated successfully.
Apr 23 10:55:05 truenas systemd[1]: run-k3s-containerd-io.containerd.runtime.v2.task-k8s.io-7bd39655d792bb8bb7768ea0fac74591478f521d59f93856e56ee4f25b291a54-rootfs.mount: Deactivated successfully.
Apr 23 10:55:05 truenas systemd[1]: cri-containerd-ee910032d74ca71bf76af7550ec3dda1a68d9dea6742ade4126aeba5438bc1c0.scope: Deactivated successfully.
Apr 23 10:55:05 truenas kernel: kube-bridge: port 1(vethcfa3d595) entered disabled state
Apr 23 10:55:05 truenas kernel: device vethcfa3d595 left promiscuous mode
Apr 23 10:55:05 truenas kernel: kube-bridge: port 1(vethcfa3d595) entered disabled state
Apr 23 10:55:05 truenas systemd[1]: run-netns-cni\x2df9cdf18a\x2d4a1c\x2deeea\x2d85fa\x2d1df547938d79.mount: Deactivated successfully.
Apr 23 10:55:06 truenas systemd[1]: Removed slice kubepods-besteffort-pod8042a110_0d58_425f_94ca_e78b1e978212.slice - libcontainer container kubepods-besteffort-pod8042a110_0d58_425f_94ca_e78b1e978212.slice.
Apr 23 10:55:06 truenas systemd[1]: run-k3s-containerd-io.containerd.runtime.v2.task-k8s.io-ee910032d74ca71bf76af7550ec3dda1a68d9dea6742ade4126aeba5438bc1c0-rootfs.mount: Deactivated successfully.
Apr 23 10:55:09 truenas kernel: kube-bridge: port 4(vethbde11198) entered disabled state
Apr 23 10:55:09 truenas kernel: device vethbde11198 left promiscuous mode
Apr 23 10:55:09 truenas kernel: kube-bridge: port 4(vethbde11198) entered disabled state
Apr 23 10:55:09 truenas systemd[1]: run-netns-cni\x2d63912ffe\x2dfb38\x2d6532\x2dabc5\x2d8ea127408634.mount: Deactivated successfully.
Apr 23 10:55:09 truenas systemd[1]: Removed slice kubepods-besteffort-podf4fdab42_e580_4783_bc8f_2494e0e21c81.slice - libcontainer container kubepods-besteffort-podf4fdab42_e580_4783_bc8f_2494e0e21c81.slice.

Then i started nextcloud again which remained in state of “deploying”. In syslog the following ist logged:

Apr 23 11:11:01 truenas systemd[1]: Started cri-containerd-76611b709d8fefab7bf0843cd99b3f8e4a497732e21e25e2a373b267072e2235.scope - libcontainer container 76611b709d8fefab7bf0843cd99b3f8e4a497732e21e25e2a373b267072e2235.
Apr 23 11:11:01 truenas systemd[1]: Started cri-containerd-556e4694ec4f6616af2bd145004cb79a58253d2eb39f361884723f6f579cc789.scope - libcontainer container 556e4694ec4f6616af2bd145004cb79a58253d2eb39f361884723f6f579cc789.
Apr 23 11:11:01 truenas systemd[1]: Started cri-containerd-8d6eaa77efc4b76dc7164a57e21d4ab322a417b823ffe9c2c5e76169d59212c4.scope - libcontainer container 8d6eaa77efc4b76dc7164a57e21d4ab322a417b823ffe9c2c5e76169d59212c4.
Apr 23 11:11:01 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:02 truenas systemd[1]: run-containerd-runc-k8s.io-8d6eaa77efc4b76dc7164a57e21d4ab322a417b823ffe9c2c5e76169d59212c4-runc.gJmmT0.mount: Deactivated successfully.
Apr 23 11:11:03 truenas systemd[1]: Started cri-containerd-fa61c3fc7eae31d3b55ab24e25f183886f1d3315b57bb51f560fa44008d6008b.scope - libcontainer container fa61c3fc7eae31d3b55ab24e25f183886f1d3315b57bb51f560fa44008d6008b.
Apr 23 11:11:03 truenas systemd[1]: run-containerd-runc-k8s.io-fa61c3fc7eae31d3b55ab24e25f183886f1d3315b57bb51f560fa44008d6008b-runc.RaS6qh.mount: Deactivated successfully.
Apr 23 11:11:03 truenas kernel: Process 26(postgres) has RLIMIT_CORE set to 1
Apr 23 11:11:03 truenas kernel: Aborting core
Apr 23 11:11:03 truenas systemd[1]: cri-containerd-fa61c3fc7eae31d3b55ab24e25f183886f1d3315b57bb51f560fa44008d6008b.scope: Deactivated successfully.
Apr 23 11:11:03 truenas systemd[1]: run-k3s-containerd-io.containerd.runtime.v2.task-k8s.io-fa61c3fc7eae31d3b55ab24e25f183886f1d3315b57bb51f560fa44008d6008b-rootfs.mount: Deactivated successfully.
Apr 23 11:11:03 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:05 truenas systemd[1]: mnt-VM\x2dAPPS-ix\x2dapplications-k3s-agent-containerd-tmpmounts-containerd\x2dmount2006687229.mount: Deactivated successfully.
Apr 23 11:11:05 truenas systemd[1]: Started cri-containerd-8275b8f9d49b8964271922dea0f228888f6cc6e64e66bd28271575bd1333486b.scope - libcontainer container 8275b8f9d49b8964271922dea0f228888f6cc6e64e66bd28271575bd1333486b.
Apr 23 11:11:05 truenas kernel: Process 27(postgres) has RLIMIT_CORE set to 1
Apr 23 11:11:05 truenas kernel: Aborting core
Apr 23 11:11:05 truenas systemd[1]: cri-containerd-8275b8f9d49b8964271922dea0f228888f6cc6e64e66bd28271575bd1333486b.scope: Deactivated successfully.
Apr 23 11:11:05 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:07 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:09 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:11 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:14 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:16 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:18 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:20 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:22 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:24 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:24 truenas systemd[1]: Started cri-containerd-5f9b30258f0d842f0b7ae94bd9642a39f2eaa7bee68d6f6174911dff51451858.scope - libcontainer container 5f9b30258f0d842f0b7ae94bd9642a39f2eaa7bee68d6f6174911dff51451858.
Apr 23 11:11:24 truenas kernel: Process 26(postgres) has RLIMIT_CORE set to 1
Apr 23 11:11:24 truenas kernel: Aborting core
Apr 23 11:11:24 truenas systemd[1]: cri-containerd-5f9b30258f0d842f0b7ae94bd9642a39f2eaa7bee68d6f6174911dff51451858.scope: Deactivated successfully.
Apr 23 11:11:25 truenas systemd[1]: run-k3s-containerd-io.containerd.runtime.v2.task-k8s.io-5f9b30258f0d842f0b7ae94bd9642a39f2eaa7bee68d6f6174911dff51451858-rootfs.mount: Deactivated successfully.
Apr 23 11:11:26 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:28 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:30 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:32 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:34 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:36 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:38 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:40 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:42 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:44 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:46 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:48 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:50 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:52 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:54 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 11:11:55 truenas systemd[1]: Started cri-containerd-ac30afd095aef75defae4d772d9f2ab0f1df100a6b751594cafb720584139f25.scope - libcontainer container ac30afd095aef75defae4d772d9f2ab0f1df100a6b751594cafb720584139f25.
Apr 23 11:11:55 truenas kernel: Process 26(postgres) has RLIMIT_CORE set to 1
Apr 23 11:11:55 truenas kernel: Aborting core
Apr 23 11:11:55 truenas systemd[1]: cri-containerd-ac30afd095aef75defae4d772d9f2ab0f1df100a6b751594cafb720584139f25.scope: Deactivated successfully.
Apr 23 11:11:56 truenas systemd[1]: run-k3s-containerd-io.containerd.runtime.v2.task-k8s.io-ac30afd095aef75defae4d772d9f2ab0f1df100a6b751594cafb720584139f25-rootfs.mount: Deactivated successfully.
Apr 23 11:11:56 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available

Then I stopped nexcloud again and the following is logged:

Apr 23 12:26:37 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 12:26:39 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 12:26:41 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 12:26:43 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 12:26:45 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 12:26:47 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 12:26:49 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 12:26:51 truenas kernel: IPVS: rr: TCP 172.18.91.112:5432 - no destination available
Apr 23 12:26:52 truenas systemd[1]: run-k3s-containerd-io.containerd.grpc.v1.cri-sandboxes-556e4694ec4f6616af2bd145004cb79a58253d2eb39f361884723f6f579cc789-shm.mount: Deactivated successfully.
Apr 23 12:26:52 truenas systemd[1]: cri-containerd-556e4694ec4f6616af2bd145004cb79a58253d2eb39f361884723f6f579cc789.scope: Deactivated successfully.
Apr 23 12:26:52 truenas systemd[1]: run-k3s-containerd-io.containerd.runtime.v2.task-k8s.io-556e4694ec4f6616af2bd145004cb79a58253d2eb39f361884723f6f579cc789-rootfs.mount: Deactivated successfully.
Apr 23 12:26:53 truenas systemd[1]: cri-containerd-8d6eaa77efc4b76dc7164a57e21d4ab322a417b823ffe9c2c5e76169d59212c4.scope: Deactivated successfully.
Apr 23 12:26:53 truenas systemd[1]: cri-containerd-8d6eaa77efc4b76dc7164a57e21d4ab322a417b823ffe9c2c5e76169d59212c4.scope: Consumed 1min 11.333s CPU time.
Apr 23 12:26:53 truenas systemd[1]: run-k3s-containerd-io.containerd.runtime.v2.task-k8s.io-8d6eaa77efc4b76dc7164a57e21d4ab322a417b823ffe9c2c5e76169d59212c4-rootfs.mount: Deactivated successfully.
Apr 23 12:26:53 truenas kernel: kube-bridge: port 1(vethf920dcfc) entered disabled state
Apr 23 12:26:53 truenas kernel: device vethf920dcfc left promiscuous mode
Apr 23 12:26:53 truenas kernel: kube-bridge: port 1(vethf920dcfc) entered disabled state
Apr 23 12:26:53 truenas systemd[1]: run-netns-cni\x2d3c3a87a1\x2dd68a\x2d7d1d\x2d252e\x2d59ff5897be3b.mount: Deactivated successfully.
Apr 23 12:26:54 truenas systemd[1]: Removed slice kubepods-besteffort-pod735ea9d5_90a5_455a_ae4b_1490405e3d5a.slice - libcontainer container kubepods-besteffort-pod735ea9d5_90a5_455a_ae4b_1490405e3d5a.slice.
Apr 23 12:26:54 truenas systemd[1]: kubepods-besteffort-pod735ea9d5_90a5_455a_ae4b_1490405e3d5a.slice: Consumed 1.785s CPU time.
Apr 23 12:26:58 truenas systemd[1]: run-k3s-containerd-io.containerd.grpc.v1.cri-sandboxes-76611b709d8fefab7bf0843cd99b3f8e4a497732e21e25e2a373b267072e2235-shm.mount: Deactivated successfully.
Apr 23 12:26:58 truenas systemd[1]: cri-containerd-76611b709d8fefab7bf0843cd99b3f8e4a497732e21e25e2a373b267072e2235.scope: Deactivated successfully.
Apr 23 12:26:58 truenas systemd[1]: run-k3s-containerd-io.containerd.runtime.v2.task-k8s.io-76611b709d8fefab7bf0843cd99b3f8e4a497732e21e25e2a373b267072e2235-rootfs.mount: Deactivated successfully.
Apr 23 12:27:01 truenas CRON[1116547]: (root) CMD (/root/renewstep.sh)
Apr 23 12:27:03 truenas kernel: kube-bridge: port 4(veth0d8048fa) entered disabled state
Apr 23 12:27:03 truenas kernel: device veth0d8048fa left promiscuous mode
Apr 23 12:27:03 truenas kernel: kube-bridge: port 4(veth0d8048fa) entered disabled state
Apr 23 12:27:03 truenas systemd[1]: run-netns-cni\x2d0f241e7c\x2d64a9\x2d708f\x2dd850\x2dc35e490e9b33.mount: Deactivated successfully.
Apr 23 12:27:04 truenas systemd[1]: Removed slice kubepods-besteffort-podd35548d4_183f_4ab3_bb2a_1adc71319325.slice - libcontainer container kubepods-besteffort-podd35548d4_183f_4ab3_bb2a_1adc71319325.slice.
Apr 23 12:27:04 truenas systemd[1]: kubepods-besteffort-podd35548d4_183f_4ab3_bb2a_1adc71319325.slice: Consumed 1min 11.355s CPU time.
Apr 23 12:27:07 truenas middlewared[823]: Fingerprint of the certificate used in UI : 56:31:32:73:9E:61:6F:A2:50:D9:6C:34:BA:87:E1:CD:01:10:BA:20
Apr 23 12:27:10 truenas systemd[1]: Stopping nginx.service - A high performance web server and a reverse proxy server…
Apr 23 12:27:15 truenas nginx[1115815]: 2024/04/23 12:27:15 [alert] 1115815#1115815: *1 open socket #7 left in connection 5
Apr 23 12:27:15 truenas nginx[1115815]: 2024/04/23 12:27:15 [alert] 1115815#1115815: *2 open socket #12 left in connection 6
Apr 23 12:27:15 truenas nginx[1115815]: 2024/04/23 12:27:15 [alert] 1115815#1115815: *3 open socket #13 left in connection 7
Apr 23 12:27:15 truenas nginx[1115815]: 2024/04/23 12:27:15 [alert] 1115815#1115815: *4 open socket #14 left in connection 8
Apr 23 12:27:15 truenas nginx[1115815]: 2024/04/23 12:27:15 [alert] 1115815#1115815: aborting
Apr 23 12:27:15 truenas systemd[1]: nginx.service: Deactivated successfully.
Apr 23 12:27:15 truenas systemd[1]: Stopped nginx.service - A high performance web server and a reverse proxy server.
Apr 23 12:27:15 truenas systemd[1]: Starting nginx.service - A high performance web server and a reverse proxy server…
Apr 23 12:27:16 truenas systemd[1]: Started nginx.service - A high performance web server and a reverse proxy server.

nestor_78 · April 23, 2024, 12:26pm

Seems to affect other users as well.

https://www.reddit.com/r/truecharts/comments/1bdh0d9/upgraded_to_cobia_issues/

m0pegasus · April 23, 2024, 1:15pm

Hi
So i try different way i even installed. Truenas scale on virtualization to see if the issue is present in new installation and indeed there next i install nextcloud as default without selecting dataset for the data or database path i leave everything as default doing that way it work i could access the web gui i login even
But i need the data path and database i don’t want every thing to store in one location i followed the nextcloud documentation in setting up the database so i don’t now what is the problem at all.

Update should fix things not broken it

m0pegasus · April 24, 2024, 7:49am

an update for you I got it working.
here is what you have to do.
1-creat dataset with share type (apps) for example (nextcloud) after that edit the permission and change the owner to www-data for user and group check the box below them after that save the permission
2-within that dataset create dataset for data with share type apps and the same permission as the first one
3- create dataset for database with share type generic and all default no need to edit permission
no mount them to your nextcloud
and it will deploy normally I don’t know why that happen but that was the solution for me.

Marius · May 8, 2024, 9:40pm

I have exactly the same issue. Is there a fix?

bella · May 10, 2024, 8:15pm

I’ll post this here as well. Two PR are in process to update the current instructions in the TrueNAS Documentation Hub Nextcloud tutorial. As soon as they are approved and merged the information on the website will be up to date.
Nextcloud deploys fine in 24.04. There are known issues with Nextcloud version 2.0.x until 2.0.4 so this might account for the issues in the field.
Two things to note. To set the ffmpeg option, click Add to the right of Command to show the Command field, then click in the field and select the ffmpeg option.
Second, if installing for the first time do not select the Pre v2 Storage Solution option as this slows the process down but if you have an existing Nextcloud deployment you do need to select this option.
Please follow the instructions in this article Nextcloud | TrueNAS Documentation Hub with the modifications noted above to install and deploy your app.
It takes about 10 minutes for the app to move from deploying to Running if you do not select Pre v2. I do not know how long it takes if you do.