Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Lost WebUI - Fatal error: Allowed memory size of 134217728 bytes exhausted

Featured Replies

So in the process of trying to create a vm using KVM I have messed up my system.  I installed the VM Manager plugin from here

https://raw.githubusercontent.com/dmacias72/dynamix.kvm.manager/master/dynamix.kvm.manager.plg

and then the virtMan plugin from here

https://raw.githubusercontent.com/dmacias72/virtMan/master/virtMan.plg

this is all on 6beta12.

 

I went into the KVM config screen and edited the two paths. They were defaulted to /mnt/ and I changed them to /mnt/cache/vm. After trying to restart libvert on that same screen I lost the UI. After a reboot I get this for my UI at http://tower

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 134217728 bytes) in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 196

 

I used telnet to get in and removed the two .plg files and the associated directories from /boot/config/plugins for virtMan and dynamix.kvm.manager but still get that error after a reboot. I even get the error when selecting the no plugins option on the unraid boot screen.

 

Can anyone let me know how I can get my system working again? I believe I need the manual uninstall procedure for virtMan and dynamix.kvm.manager

 

thanks!

 

 

Have you tried clearing your browser cache? Sometimes the browser will cache "old code" and the webGUI will appear broken.

  • Author

Have you tried clearing your browser cache? Sometimes the browser will cache "old code" and the webGUI will appear broken.

 

Just tried and that didn't help me. :(

I still get this message in the main UI

 

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 134217728 bytes) in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 196

  • Author

So in digging around I found that my /boot/config/plugins/dynamix/dynamix.cfg file is currently at a size of 1409285926 and was last modified around the time that I got the issue. I made a backup as dynamix.cfg.bak for safe keeping. This file is full of the same line over and over and over

 

sysinfo="/Tools/SystemProfiler"

 

Can someone else look in their copy of that file and see what they have? I am not sure why mine got into this state.

 

thanks!

I already looked at mine earlier for a different reason and it did not have this issue. I do have that plugin (Dynamix System Information) installed but haven't used it much.

  • Author

I deleted this file, /boot/config/plugins/dynamix/dynamix.cfg (I have a backup) and rebooted. Everything came back normally. My question is now, what should I really have in this file and I am wondering what corrupted it with that line over and over. I am scared to go back down the KVM path now!

 

thanks, Chris

That file is dynamix configuration settings. Did it get recreated after boot, possibly with default settings? Don't think it has anything to do with KVM.

  • Author

That file is dynamix configuration settings. Did it get recreated after boot, possibly with default settings? Don't think it has anything to do with KVM.

 

The dynamix config file was not recreated after a reboot. I went ahead and removed these three plugins just in case they caused my issue before

https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.info.plg

https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.stats.plg

https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.temp.plg

 

I have reinstalled these two

https://raw.githubusercontent.com/dmacias72/dynamix.kvm.manager/master/dynamix.kvm.manager.plg

https://raw.githubusercontent.com/dmacias72/virtMan/master/virtMan.plg

 

so now I am back in the same place as I was before I lost the unriad ui. Just so that I don't make another mistake, let me check first,

 

On the KVM / Settings tab... Default media directory and Default Existing vm directory are defaulting to /mnt/

 

What should I put here?

 

thanks

That is what mine says also. I think that page was added after I created my VM.

  • 4 weeks later...

That file is dynamix configuration settings. Did it get recreated after boot, possibly with default settings? Don't think it has anything to do with KVM.

 

The dynamix config file was not recreated after a reboot. I went ahead and removed these three plugins just in case they caused my issue before

https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.info.plg

https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.stats.plg

https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.temp.plg

 

I have reinstalled these two

https://raw.githubusercontent.com/dmacias72/dynamix.kvm.manager/master/dynamix.kvm.manager.plg

https://raw.githubusercontent.com/dmacias72/virtMan/master/virtMan.plg

 

so now I am back in the same place as I was before I lost the unriad ui. Just so that I don't make another mistake, let me check first,

 

On the KVM / Settings tab... Default media directory and Default Existing vm directory are defaulting to /mnt/

 

What should I put here?

 

thanks

 

I'm curious too why dynamix.cfg was so large.  A reason that my plugin may have been involved is it loads dynamix.cfg to determine if the theme is black or white for table background shading. That was added in the last version because of changes to dynamix. But the plugin doesn't write to dynamix.cfg.

 

The default media and existing vm directory settings are just for convenience.  So you don't have to click through layers of nested directories in the Create tab and have the file tree default to that location.  I have them default to /mnt. You wouldn't want to create a vm at that location though as you would run into the same memory problem since /mnt is actually in ram. Thanks for this though.  It gave me the idea to make it so the plugin can't create vm's on the ram file system area.

 

But basically if you have your operating iso images on your cache drive then you could make the default media directory e.g. /mnt/cache/images/. Then under the Create tab the iso/install media would default to this location.

 

If you save your dynamix settings the file will probably be created.

 

  • 1 month later...

I deleted this file, /boot/config/plugins/dynamix/dynamix.cfg (I have a backup) and rebooted. Everything came back normally. My question is now, what should I really have in this file and I am wondering what corrupted it with that line over and over. I am scared to go back down the KVM path now!

 

thanks, Chris

 

If you want to stop it from being re-created and raized in size so much, after you delete it, create a directory with the same name "dynamix.cfg" and it will not give you any more errors.  (That's what I did at least...)

 

After a reboot I got an error.  I just added a delete on my go file.  Problem solved, every time it reboots it deletes it.

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.