12 minutes ago, gekoch said:

it does shutdown but does not start again. i need to manualy start the lxc in the unraid menu again. Is this normal?

Please post your Diagnostics and no this isn't normal.

4 hours ago, ich777 said:

Please post your Diagnostics and no this isn't normal.

ok here are the files

nas-diagnostics-20250113-1445.zip

3 hours ago, gekoch said:

ok here are the files

Sorry, I can't reproduce this.

 

I set up a Debian Bookworm LXC container, start it, open up a Terminal for that container, type in 'reboot', the Terminal closes and the container restarts. Of course you have to re-open the Terminal from the container.

2 hours ago, ich777 said:

Sorry, I can't reproduce this.

 

I set up a Debian Bookworm LXC container, start it, open up a Terminal for that container, type in 'reboot', the Terminal closes and the container restarts. Of course you have to re-open the Terminal from the container.

 

hmm I rebooted unraid and tested again, but still same issue...

Edited January 13, 20251 yr by gekoch

1 hour ago, gekoch said:

hmm I rebooted unraid and tested again, but still same issue...

Please try to set up a new container with autostart enabled and see if the container restarts properly.

From what I can tell you are also on Unraid 7.0.0 so everything should be the same.

7 hours ago, ich777 said:

Please try to set up a new container with autostart enabled and see if the container restarts properly.

From what I can tell you are also on Unraid 7.0.0 so everything should be the same.

interesting, I made a new container with the save distribution and release and there the reboot does work for the new container! Can I somehow transfer all the settings and installation to the new container?

 

EDIT: Strange. I created a new container, and now the reboot function no longer works. Even in the container where it was working before, the reboot function has stopped working.

Edited January 14, 20251 yr by gekoch

2 hours ago, gekoch said:

EDIT: Strange. I created a new container, and now the reboot function no longer works. Even in the container where it was working before, the reboot function has stopped working.

I think there is something else going on on your system.

 

Please do the following:

1. Make sure the container is stopped that you want to test
2. Open up a Unraid terminal and type in:

   lxc-start -F <CONTAINERNAME>

   (You have to replace <CONTAINERNAME> with the actual name from the container you want to test)
3. Leave the Unraid terminal open and open up a Terminal window from the now started container (you might have to refresh the LXC page since you've now manually started it from the Terminal)
4. In the Container Terminal type in:

   reboot

 

You now should see what is going on with the container in the Unraid Terminal, usually after issuing reboot you should see the container starting again and finally bring you to the login prompt (you actually can't login, this is just to see what's going on with the container).

 

May I also ask what filesystem you use for your SSD Cache?

3 hours ago, ich777 said:

I think there is something else going on on your system.

 

Please do the following:

1. Make sure the container is stopped that you want to test
2. Open up a Unraid terminal and type in:

   lxc-start -F <CONTAINERNAME>

   (You have to replace <CONTAINERNAME> with the actual name from the container you want to test)
3. Leave the Unraid terminal open and open up a Terminal window from the now started container (you might have to refresh the LXC page since you've now manually started it from the Terminal)
4. In the Container Terminal type in:

   reboot

 

You now should see what is going on with the container in the Unraid Terminal, usually after issuing reboot you should see the container starting again and finally bring you to the login prompt (you actually can't login, this is just to see what's going on with the container).

 

May I also ask what filesystem you use for your SSD Cache?

 

Ok here is the last part of the log that might be interesting:
 

All filesystems, swaps, loop devices, MD devices and DM devices detached.
Rebooting.
lxc-start: DebianLXC: ../src/lxc/network.c: setup_hw_addr: 3864 Address already in use - Failed to perform ioctl
lxc-start: DebianLXC: ../src/lxc/network.c: lxc_network_setup_in_child_namespaces_common: 3911 Address already in use - Failed to setup hw address for network device "eth0"
lxc-start: DebianLXC: ../src/lxc/network.c: lxc_setup_network_in_child_namespaces: 4062 Address already in use - Failed to setup netdev
lxc-start: DebianLXC: ../src/lxc/conf.c: lxc_setup: 3896 Failed to setup network
lxc-start: DebianLXC: ../src/lxc/start.c: do_start: 1273 Failed to setup container "DebianLXC"
lxc-start: DebianLXC: ../src/lxc/sync.c: sync_wait: 34 An error occurred in another process (expected sequence number 3)
lxc-start: DebianLXC: ../src/lxc/start.c: __lxc_start: 2114 Failed to spawn container "DebianLXC"
lxc-start: DebianLXC: ../src/lxc/tools/lxc_start.c: lxc_start_main: 307 The container failed to start
lxc-start: DebianLXC: ../src/lxc/tools/lxc_start.c: lxc_start_main: 312 Additional information can be obtained by setting the --logfile and --logpriority options

 

the cache is btrfs

Edited January 14, 20251 yr by gekoch

59 minutes ago, gekoch said:

Ok here is the last part of the log that might be interesting:

Can you please try to restart the container from the GUI and see if that is working?

2 hours ago, ich777 said:

Can you please try to restart the container from the GUI and see if that is working?

Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
All filesystems, swaps, loop devices, MD devices and DM devices detached.
Halting system.

 

1 hour ago, gekoch said:

Can you please try to restart the container from the GUI and see if that is working?

I don't understand...

You don't need to open up the process in the Unraid Terminal, just try if the restart button in the GUI works, just out of curiosity.

3 hours ago, ich777 said:

I don't understand...

You don't need to open up the process in the Unraid Terminal, just try if the restart button in the GUI works, just out of curiosity.

that's exactly what i did. The restart button in Unraid works but the reboot command withing the LXC does not reboot the LXC.

2 hours ago, gekoch said:

that's exactly what i did. The restart button in Unraid works but the reboot command withing the LXC does not reboot the LXC.

I assume it has something to do with macvlan since I'm using ipvlan, I will change my setup on a test server that I have over to macvlan and see if it is working for me.

2 minutes ago, ich777 said:

I assume it has something to do with macvlan since I'm using ipvlan, I will change my setup on a test server that I have over to macvlan and see if it is working for me.

thx for testing 

23 hours ago, gekoch said:

thx for testing 

I just tested it on my machine and everything seems to work fine:

 

Is the address for the container maybe in use already? It seams that it has some issues with the MAC address.

8 hours ago, ich777 said:

I just tested it on my machine and everything seems to work fine:

 

 

Is the address for the container maybe in use already? It seams that it has some issues with the MAC address.

 

Interesting you mention this since this morning i get this error when starting the container:
 

root@NAS:~# lxc-start -F DebianLXC
lxc-start: DebianLXC: ../src/lxc/network.c: setup_hw_addr: 3864 Cannot assign requested address - Failed to perform ioctl
lxc-start: DebianLXC: ../src/lxc/network.c: lxc_network_setup_in_child_namespaces_common: 3911 Cannot assign requested address - Failed to setup hw address for network device "eth0"
lxc-start: DebianLXC: ../src/lxc/network.c: lxc_setup_network_in_child_namespaces: 4062 Cannot assign requested address - Failed to setup netdev
lxc-start: DebianLXC: ../src/lxc/conf.c: lxc_setup: 3896 Failed to setup network
lxc-start: DebianLXC: ../src/lxc/start.c: do_start: 1273 Failed to setup container "DebianLXC"
lxc-start: DebianLXC: ../src/lxc/sync.c: sync_wait: 34 An error occurred in another process (expected sequence number 3)
lxc-start: DebianLXC: ../src/lxc/start.c: __lxc_start: 2114 Failed to spawn container "DebianLXC"
lxc-start: DebianLXC: ../src/lxc/tools/lxc_start.c: lxc_start_main: 307 The container failed to start
lxc-start: DebianLXC: ../src/lxc/tools/lxc_start.c: lxc_start_main: 312 Additional information can be obtained by setting the --logfile and --logpriority options

 

 

"Cannot assign requested address" What address? Mac address?

 

I can still create a new one that is working but I can't start the one that was running the past few days...

Edited January 16, 20251 yr by gekoch

52 minutes ago, gekoch said:

"Cannot assign requested address" What address? Mac address?

Oh, I think you overlooked the message in my previous answer at the bottom. Yes the MAC address.

 

It's really strange to me that it fails because of the Network since on my main server I'm using almost the same Hardware as you. The only difference is the network NIC which you are using a Realtek and I'm using a Intel one.

 

May I ask why you are using macvlan, is ipvlan maybe an option for you or is ipvlan not properly supported by your router?

 

I found an issue and a comment that is pretty old here that is pretty much the same that we see here but I'm not sure if we can apply that here because we are on the same Kernel/LXC version and also have pretty much the same hardware.

 

1 hour ago, gekoch said:

I can still create a new one that is working but I can't start the one that was running the past few days...

So basically if you create a new container you can restart it for a few days and then it stops working correct?

 

May I ask what the exact use case for that is? I mean I also have containers which restart themself from inside the container.

28 minutes ago, ich777 said:

May I ask why you are using macvlan, is ipvlan maybe an option for you or is ipvlan not properly supported by your router?

 

Yes I use macvlan since I use an unifi system and when I started with Unraid i had a lot of problems with ipvlan.

 

Reboot is not important for me. I just tested it once and the container did not reboot thats why I wrote here.

 

The container seems now to be damaged somehow. I cant get it back up and running.

So i made a new one and copied the data over and now that works again. 

But I don't know why it failed suddendly 

 

Quote

So basically if you create a new container you can restart it for a few days and then it stops working correct?

No even the new one cant be restarted successfully...

So from the beginning I was not able to successfully restart a container via the reboot command within the container.

 

2 minutes ago, gekoch said:

The container seems now to be damaged somehow. I cant get it back up and running.

So i made a new one and copied the data over and now that works again. 

But I don't know why it failed suddendly 

This is really strange, it shouldn't fail out of nowhere.

Please make sure your pool is okay by making a scrub if possible, just to be sure that the pool is really okay.

 

17 minutes ago, gekoch said:

So from the beginning I was not able to successfully restart a container via the reboot command within the container.

I can raise an issue on Github if you want to and include your Diagnostics but I would need definitely some help and further information if I do that.

 

However I think this might be some kind of weird race condition or maybe also related to the Realtek NIC but I'm not 100% sure why that's happening on your system.

1 hour ago, ich777 said:

This is really strange, it shouldn't fail out of nowhere.

Please make sure your pool is okay by making a scrub if possible, just to be sure that the pool is really okay.

 

I can raise an issue on Github if you want to and include your Diagnostics but I would need definitely some help and further information if I do that.

 

However I think this might be some kind of weird race condition or maybe also related to the Realtek NIC but I'm not 100% sure why that's happening on your system.

 

yeah why not and of course I can help and test things 

Hello, my problem is the same as the previous user. The unraid gui interface cannot start the lxc container. The command line lxc-start can start the container. Can you help me troubleshoot?

 

 

use "lxc-start df" can start-up,here are log

3 hours ago, solomon6 said:

my problem is the same as the previous user

Can you please post your Diagnostics?

27 minutes ago, solomon6 said:

is this log file?

Please go to: Tools -> Diagnostics -> click the Checkbox "Anonymize diagnostics" to anonymize your Diagnostics -> Download

2 hours ago, solomon6 said:

thank you

It seems like that you are using a Pirated version from Unraid, no support from my side unless for such versions.

 

Please consider that these issues could also be due to using a custom pirated version. You never know what backdoors or other questionable elements might be included in such versions, disrupting the system as a whole. Your server might already be part of a botnet.

 

Personally, pirating a server OS would not be an option for me, as you can never be sure what is included in such a build.

 

@SpencerJ

its me again...

 

Now my container seems to be stuck and I can't even force kill it with:

lxc-stop DebianLXC -k