3 minutes ago, gekoch said:

its me again...

Did you already do the scrub on your pool?

 

4 minutes ago, gekoch said:

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

Do you have any logs or can you please post the Diagnostics?

2 minutes ago, ich777 said:

Did you already do the scrub on your pool?

 

Do you have any logs or can you please post the Diagnostics?

I did now a scrub manually:
 

Scrub started:    Fri Jan 17 08:54:00 2025
Status:           finished
Duration:         0:05:24
Total to scrub:   164.00GiB
Rate:             517.33MiB/s
Error summary:    no errors found

 

and here are the diagnostics

nas-diagnostics-20250117-0859.zip

17 minutes ago, gekoch said:

I did now a scrub manually:

Is it maybe possible that the mover moves files to another disk or something like that (but I don't think so because it lists only files for lxc on your ssd cache)?

 

I also see a lot of these errors in your syslog (possibly not related but worth investigating) :

No space left on device

 

Then here we have something completely different:

Jan 14 10:56:26 NAS root: LXC: error: Container DebianLXC failed to start
Jan 14 10:56:26 NAS root: LXC: lxc-start: DebianLXC: ../src/lxc/lxccontainer.c: wait_on_daemonized_start: 837 Received container state ABORTING instead of RUNNING
Jan 14 10:56:26 NAS root: LXC: lxc-start: DebianLXC: ../src/lxc/tools/lxc_start.c: lxc_start_main: 307 The container failed to start
Jan 14 10:56:26 NAS root: LXC: lxc-start: DebianLXC: ../src/lxc/tools/lxc_start.c: lxc_start_main: 310 To get more details, run the container in foreground mode
Jan 14 10:56:26 NAS root: LXC: 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
Jan 14 10:57:20 NAS root: LXC: Starting container DebianLXC

 

I'm also not 100% sure what here happened:

Jan 14 05:36:42 NAS root: LXC: Creating container DebianLXC
Jan 14 05:36:45 NAS root: LXC: error: Failed to create Container DebianLXC
Jan 14 05:36:45 NAS root: LXC: Downloading the image index
Jan 14 05:36:45 NAS root: LXC: Downloading the rootfs
Jan 14 05:36:45 NAS root: LXC: Downloading the metadata
Jan 14 05:36:45 NAS root: LXC: mkdir: cannot create directory '/var/cache/lxc': File exists
Jan 14 05:36:45 NAS root: LXC: lxc-create: DebianLXC: ../src/lxc/lxccontainer.c: create_run_template: 1601 Failed to create container from template
Jan 14 05:36:45 NAS root: LXC: lxc-create: DebianLXC: ../src/lxc/lxccontainer.c: container_destroy: 2928 container DebianLXC is not stopped
Jan 14 05:36:45 NAS root: LXC: lxc-create: DebianLXC: ../src/lxc/tools/lxc_create.c: lxc_create_main: 318 Failed to create container DebianLXC
Jan 14 05:37:32 NAS root: LXC: Destroying container DebianLXC
Jan 14 05:37:32 NAS root: LXC: Killing container DebianLXC

 

 

You have also a lot of dbus entries on /tmp and also a lot of sed entries in /boot/config may I ask what these are?

 

I'm really not sure what's going on on your system sorry.

Would it be possible for you to temporarily move the default lxc path to another cache pool to test if it happens the same on another pool?

4 minutes ago, ich777 said:

You have also a lot of dbus entries on /tmp and also a lot of sed entries in /boot/config may I ask what these are?

 

No idea either... No idea what or who has created those files...

 

22 minutes ago, ich777 said:

Would it be possible for you to temporarily move the default lxc path to another cache pool to test if it happens the same on another pool?

I will test this 

 

how can I kill no the container?

do i need to search the id of the application via ps -ef and then kill it?

5 minutes ago, gekoch said:

how can I kill no the container?

Try:

lxc-info <CONTAINERNAME>

there you should see the PID and you can simply kill that with:

kill -SIGTERM <PID>

 

However if that is also not working then there is something else going on.

yeah i had to use kill. I now moved all files to a new cache drive.

 

I tried to start the LXC, but cant, even If i use a backup:

lxc-start DebianLXC
lxc-start: DebianLXC: ../src/lxc/lxccontainer.c: wait_on_daemonized_start: 837 Received container state "ABORTING" instead of "RUNNING"
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: 310 To get more details, run the container in foreground mode
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

 

Creating a new container works however

 

EDIT:

lxc-start -n DebianLXC -F
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 same problem as before...

I think there is something wring with my network config...

Edited January 17, 20251 yr by gekoch

41 minutes ago, gekoch said:

The same problem as before...

I think there is something wring with my network config...

I'm really not sure what's going on on your system because even from my testing and other people with macvlan and using LXC everything is working perfectly fine.

 

I've also never seen the issue with the message "Received container state ABORTING instead of RUNNING".

 

Sorry I'm out of ideas. Disk space or anything like that is also not a concern correct?

Do you have any custom packages installed directly on Unraid itself or any binaries packages which might interfere with LXC?

27 minutes ago, ich777 said:

Sorry I'm out of ideas. Disk space or anything like that is also not a concern correct?

 

no thats not a problem since the LXC runs on cache where there is plenty space left.

 

28 minutes ago, ich777 said:

Do you have any custom packages installed directly on Unraid itself or any binaries packages which might interfere with LXC?

not anymore, removed all of them. Thats why I like to run all python scripts on this lxc 

This is awesome thanks just migrated my lxc's from Proxmox to here and all are working perfectly.

Well that was short lived lol.

Just did a backup and got this.

Although it appears the backup has worked.

1 hour ago, surfbum said:

This is awesome thanks just migrated my lxc's from Proxmox to here and all are working perfectly.

Thanks for that...

 

1 hour ago, surfbum said:

Just did a backup and got this.

This happens only when you backup really big containers, however this won't prevent the backup from being taken properly since it will run in the background until it's done.

 

Can't do anything about the timeout since this is a fixed value from the WebGUI, however what you can also do is that you issue it from the command line (just in case you plan to scheduled backups), just issue:

lxc-autobackup

and you will be presented how to use it.

 

This is a routine that I specifically wrote for Unraid.

On 1/17/2025 at 4:35 AM, ich777 said:

I'm really not sure what's going on on your system because even from my testing and other people with macvlan and using LXC everything is working perfectly fine.

 

I've also never seen the issue with the message "Received container state ABORTING instead of RUNNING".

 

Sorry I'm out of ideas. Disk space or anything like that is also not a concern correct?

Do you have any custom packages installed directly on Unraid itself or any binaries packages which might interfere with LXC?

 

I'm also having a similar issue:

 

root@Tower:~# lxc-start AMPStandalone
lxc-start: AMPStandalone: ../src/lxc/lxccontainer.c: wait_on_daemonized_start: 837 Received container state "ABORTING" instead of "RUNNING"
lxc-start: AMPStandalone: ../src/lxc/tools/lxc_start.c: lxc_start_main: 307 The container failed to start
lxc-start: AMPStandalone: ../src/lxc/tools/lxc_start.c: lxc_start_main: 310 To get more details, run the container in foreground mode
lxc-start: AMPStandalone: ../src/lxc/tools/lxc_start.c: lxc_start_main: 312 Additional information can be obtained by setting the --logfile and --logpriority options

 

This is a Debian LXC that is only running AMP (Aplication Management Panel) for my game servers. I went to update my Factorio server as it just got an update and it gave me an error saying no space left on device even though there is plenty of space. I decided to try restarting the LXC to see if that would fix it, but when attempting to start it back up, it will not start. I additionally tried copying the container which worked and the container will start, but it doesn't grab any ip addresses at all let alone the same ones the original container used. Can you help me either fix the original container or get the new one to grab the addresses it needs?

 

Thanks

12 hours ago, ich777 said:

Thanks for that...

 

This happens only when you backup really big containers, however this won't prevent the backup from being taken properly since it will run in the background until it's done.

 

Can't do anything about the timeout since this is a fixed value from the WebGUI, however what you can also do is that you issue it from the command line (just in case you plan to scheduled backups), just issue:

lxc-autobackup

and you will be presented how to use it.

 

This is a routine that I specifically wrote for Unraid.

awesome thanks

2 hours ago, rcm024 said:

I'm also having a similar issue:

Can you please do the following:

1. Stop the Container
2. Open up a Unraid Terminal
3. Type in:

   lxc-start -F AMPStandalone

With that you should see why the container isn't starting for you.

 

Can you please share your Diagnostics?

56 minutes ago, ich777 said:

Can you please do the following:

1. Stop the Container
2. Open up a Unraid Terminal
3. Type in:

   lxc-start -F AMPStandalone

With that you should see why the container isn't starting for you.

 

root@Tower:~# lxc-start -F AMPStandalone
lxc-start: AMPStandalone: ../src/lxc/conf.c: lxc_rootfs_init: 392 No space left on device - Failed to pin rootfs
lxc-start: AMPStandalone: ../src/lxc/start.c: __lxc_start: 2086 Failed to handle rootfs pinning for container "AMPStandalone"
lxc-start: AMPStandalone: ../src/lxc/tools/lxc_start.c: lxc_start_main: 307 The container failed to start
lxc-start: AMPStandalone: ../src/lxc/tools/lxc_start.c: lxc_start_main: 312 Additional information can be obtained by setting the --logfile and --logpriority options

 

57 minutes ago, ich777 said:

Can you please share your Diagnostics?

attached

tower-diagnostics-20250121-1749.zip

7 hours ago, rcm024 said:

No space left on device - Failed to pin rootfs

It seems that you've run out of space...

 

It also complains in your logs:

Jan 21 04:40:50 Tower shfs: assign_disk: /lxc/AMPStandalone/rootfs/tmp/dotnet-diagnostic-119844-32066031-socket No space left on device (28) No space left on device
Jan 21 04:40:50 Tower shfs: share cache full

 

It also seems that you've deployed the container when the plugin was not completely set up correctly since your container shows the path /mnt/user/... which will have negative impacts on performance and also cause such issues:

lxc.rootfs.path = dir:/mnt/user/lxc/AMPStandalone/rootfs

 

 

I can only recommend to you that you take a backup from the container, after that restore the container because that will fix the path (which is now set to /mnt/cache_sata/lxc from your Diagnostics) and hope that it still is working, of course you could still pull all the data out first, it should be also be possible to restore container data afterwards.

Just want to say thank you for your work on this.  I've setup a Slackware lxc container (for my repository work since it is on -current) and a Debian container for other stuff.  I also found information on the config file setup and managed to have it create a dev/shm automatically for Slackware (one doesn't exist by default and is needed for certain things) and mount a host folder on Debian.

Hi team! Hope you're having a great day.

 

Weird "bug" here. I'm unable to add a new container. Just leaving the default options and adding a name. Pressing the Create button just "refreshes" the page and asks again for the new container name.

 

Diagnostics included.

 

 

mini-diagnostics-20250124-1626.zip

Not sure where to find or change the root password. I tried to install from a template but when I try to su root and enter the password Unraid I get Authentication failure.

1 hour ago, MediaDactyl said:

Not sure where to find or change the root password. I tried to install from a template but when I try to su root and enter the password Unraid I get Authentication failure.

If you're already logged in as root, you can execute `passwd` from the root account to change its password.

At least I've used that before.

10 hours ago, djismgaming said:

Weird "bug" here. I'm unable to add a new container. Just leaving the default options and adding a name. Pressing the Create button just "refreshes" the page and asks again for the new container name.

Can you please be a bit more precise?

Do you mean from a template or do you mean just click on Add Container and deploy it on your system?

 

I now tried both and it is working fine over here.

Can you please also rule out a browser issue on your side?

 

The first one is deployed with the Add Container button and the second one is deployed via a Template:

7 hours ago, MediaDactyl said:

Not sure where to find or change the root password. I tried to install from a template but when I try to su root and enter the password Unraid I get Authentication failure.

Depends about which container are we talking if you deployed it from a template, most of the times it is enough to type in exit once.

4 hours ago, djismgaming said:

If you're already logged in as root

The template I used just gave me login for the app but not the debian container. But after a recent update I just started from scratch and was able to get the app working that way.

6 minutes ago, MediaDactyl said:

template

Which one?

7 hours ago, ich777 said:

Which one?

The one for Amp.