Apps Disappear After Reboot

Apps and Virtualization
,
1

Hi, this is my first time installing TrueNas on my old hardware. I installed Plex and then shut down. after reboot Apps Services to be missing.

Here is the description of the error

Error: Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/middlewared/job.py”, line 488, in run
await self.future
File “/usr/lib/python3/dist-packages/middlewared/job.py”, line 533, in __run_body
rv = await self.method(*args)
^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/schema/processor.py”, line 49, in nf
res = await f(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/schema/processor.py”, line 179, in nf
return await func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/plugins/docker/update.py”, line 100, in do_update
await self.middleware.call(‘docker.setup.status_change’)
File “/usr/lib/python3/dist-packages/middlewared/main.py”, line 1626, in call
return await self._call(
^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/main.py”, line 1457, in _call
return await methodobj(*prepared_call.args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/plugins/docker/state_setup.py”, line 73, in status_change
await self.middleware.call(‘docker.state.start_service’)
File “/usr/lib/python3/dist-packages/middlewared/main.py”, line 1626, in call
return await self._call(
^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/main.py”, line 1457, in _call
return await methodobj(*prepared_call.args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/plugins/docker/state_management.py”, line 44, in start_service
await self.before_start_check()
File “/usr/lib/python3/dist-packages/middlewared/plugins/docker/state_management.py”, line 16, in before_start_check
await self.middleware.call(‘docker.setup.validate_fs’)
File “/usr/lib/python3/dist-packages/middlewared/main.py”, line 1626, in call
return await self._call(
^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/main.py”, line 1457, in _call
return await methodobj(*prepared_call.args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/plugins/docker/state_setup.py”, line 55, in validate_fs
await self.validate_interfaces()
File “/usr/lib/python3/dist-packages/middlewared/plugins/docker/state_setup.py”, line 61, in validate_interfaces
raise CallError(‘Unable to determine default interface’)
middlewared.service_exception.CallError: [EFAULT] Unable to determine default interface

Would appreciated for any help.

2

Have you tried rebooting again? I’ve hit something similar a couple of times now since updating to EE. I saw an entry on Jira stating that Docker will fail to start if the network isn’t connected.
Both times when I had the issue, the network stack was having some sort of issue. So maybe if Docker tries to start before the network stack is fully active or hits a DNS issue of some sort it causes this?
A reboot or two has cleared the issue for me so far.

3

I’m guessing that your network configuration is incomplete or incorrect.
Could you post a screenshot of the network page as it’s set up now?

4

No screenshots until forum trust level goes up.

@Habib_Esa
Go browse a few other topics on the forums and complete the tutorial. You should be able to post screenshots after you become a Basic User level.

TrueNAS-Bot
Type this in a new reply and send to bring up the tutorial, if you haven’t done it already.

@TrueNAS-Bot start tutorial
5

Duh, of course. Thank you for reminding me.

In that case, at least verify that you’ve set your default gateway up.
In most home environments a sane gateway would be the IP of your router.

6

I did, it stays the same.

7

I change the gateway to my router’s IP and I can’t assessed the truenas web UI.

I’ve reset the configuration and have to start all over again.

8

That just reinforces the idea that you set your network settings incorrectly.
Resetting the configuration after that happened was likely unnecessary, you could just have set it back to whatever it was using the console.

But we will never know unless you share how you set it up.

9

Yeah probably but after installation I didn’t change any of the network settings. I will keep posting if the problems reoccur.

10

Revisiting this thread. It appears that if your only interface is a bonded link, it flakes out starting the network fully on boot 70% of the time, which prevents Docker from starting.

I deleted the bonded links and reverted to a single link and it started right up on the next boot after failing 7 times in a row…