Taddeusz

I’m not at home right now so I can’t pull back the update. If you go to the container console you can go to, I think, /var/log/mysql. I think just look at the latest log file there.

I've pushed out a new version to update to the latest version of Tomcat 8.5. In the process I discovered the install process for MariaDB no longer worked, which is the reason this took so long to get out. Let me know if you have problems with this update.

My TOTP is working fine. Look at the catalina.out file in the tomcat logs.

This is done at build time. I’ll have to build a new version to update the Tomcat in the container.

What does the log look like?

Even with a separate video card and the iGPU set as primary my ASUS Prime H370M-Plus requires a monitor be plugged into the motherboard for the iGPU to be enabled. If no monitor is plugged into the motherboard it automatically sets my RX 470 as primary.

M/B: ASUSTeK COMPUTER INC. PRIME H370M-PLUS Version Rev 1.xx - s/n: 180323582100011 BIOS: American Megatrends Inc. Version 3201. Dated: 09/08/2021 CPU: Intel® Core™ i7-9700 CPU @ 3.00GHz HVM: Enabled IOMMU: Enabled Cache: 512 KiB, 2 MB, 12 MB Memory: 48 GiB DDR4 (max. installable capacity 64 GiB) Network: eth0: 1000 Mbps, full duplex, mtu 1500 Kernel: Linux 5.19.14-Unraid x86_64

Looks like I've been having this problem on my Windows 11 vm. Which sucks because I was looking forward to having access to my Unraid shares without needing to go through SMB. Has anyone yet filed an official bug report on this freezing issue?

Looks like it's virtio-fs causing my freezing. Hopefully this will get fixed.

My Windows 11 VM keeps freezing. I have a Radeon RX 470, a USB card, and a PCIe NVME passed through. I have secure boot set up. I can't figure out why it keeps locking up? unraid-diagnostics-20221013-0940.zip

@SimonF That looks perfect!

Yes, that's correct.

I'm running a Windows 11 VM with an AMD Radeon RX 470 passed through. All of a sudden when I try to install a new video driver the screen goes black for a while and then the VM reboots. It does the same thing when I go into the Device Manager and update the driver. It had been working fine. I'd get that every once in a while but after a reboot the driver would install fine. But now I can't install any video driver. I tried deleting the device in Device Manager and it locked and rebooted. I even booted into safe mode and deleted the device. After I rebooted it needed another reboot after it reinstalled the video card. Not really sure what's going on or how to solve it? unraid-diagnostics-20221009-1019.zip

@SimonF Yes

It would be nice to be able specify a bound PCIe device as bootable drive and be able to specify a boot order for that device. I'm not the only one to be doing this.

The problem is that if you pass through the device as a PCIe device the OVMF doesn't see it as a bootable device unless you add the boot order the the XML. I've changed it to a physical drive pass through but that's different. It shows up in the guest OS as a "QEMU HARDDISK" rather than a PCIe device. Apparently there's a slight performance penalty from doing it this way rather than just passing through the entire PCIe device.

I have an NVME passed through to my VM as the OS drive. In order for OVMF to boot from it I have to edit the XML and specify the boot order. Any time I modify my VM I have to go back in and modify the XML. If I forget to do this step it won't automatically boot from the NVME but will instead boot straight to the UEFI shell.

I have an NVME drive that I've passed through for the OS drive in my VM. I have it working fine if I edit the XML and add the boot order tag to the necessary device. Is there a simpler way to do this? I noticed when I re-saved my VM after adding the vfio-fs share to my VM that it added a boot tag under "os" that defaults to "hd". Is there something similar I can do for OVMF to default to booting from a PCIe NVME device? If I don't add the boot order to the device it doesn't even end up on the boot order at all and boots straight to the UEFI shell.

@Froberg Unfortunately, I found this about your motherboard. QSV is apparently not supported: https://www.supermicro.com/support/faqs/faq.cfm?faq=25758. Apparently motherboards with these chipsets don't even provide power to the IGP: https://forums.servethehome.com/index.php?threads/need-quick-sync.24653/.

That is a problem. Personally the only one I care about is zsh so hopefully in won’t have too much trouble with it.

I realize that. I’m referring to future releases because I’m sure the packages for Slackware 15 won’t necessarily work for future versions of Unraid that will likely be built off a future version of Slackware.

For future reference is there a way to tell what version of Slackware a new version of Unraid is built from?

I realize I've included Microsoft SQL Server support but not PostgreSQL support. I'll be working to correct that oversight for anyone who might wish to use that database over MSSQL or MariaDB/MySQL.

It looks like you're using the wrong image tag as I don't see that it's starting mariadb. Make sure you're using jasonbean/guacamole:latest (NOT jasonbean/guacamole:latest-nomariadb). This should be kind of what you should see on the very first start of the container that includes MariaDB: usermod: no changes ---------------------- User UID: 99 User GID: 100 ---------------------- Creating properties from template. Creating Database folders Copying MySQL extension. Updating user permissions. Initializing Guacamole database. Database installation complete. Starting MariaDB. Creating Guacamole database. Creating Guacamole database user. Database created. Granting access to 'guacamole' user for localhost. Creating Guacamole database schema and default admin user. Stopping MariaDB. Setting database file permissions Removing mysql-server logrotate directive Initialization complete. 2022-09-06 11:48:13,492 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing 2022-09-06 11:48:13,492 INFO Set uid to user 0 succeeded 2022-09-06 11:48:13,494 INFO supervisord started with pid 388 2022-09-06 11:48:14,496 INFO spawned: 'guacd' with pid 391 2022-09-06 11:48:14,497 INFO spawned: 'mariadb' with pid 392 2022-09-06 11:48:14,498 INFO spawned: 'tomcat' with pid 393 guacd[391]: INFO: Guacamole proxy daemon (guacd) version 1.4.0 started guacd[391]: INFO: Listening on host 0.0.0.0, port 4822 2022-09-06 11:48:15,887 INFO success: guacd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-09-06 11:48:15,887 INFO success: mariadb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-09-06 11:48:15,887 INFO success: tomcat entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

This container was designed for use on Unraid. While I know people have used it on other operating systems or NAS’s successfully I don’t own or have access to a Synology NAS. The only thing I can suggest is looking at the logs to make sure the database is being created and initialized correctly. The only user that should exist after initial start is “guacadmin”. Not sure how “username2” would have ever been created as that’s nowhere in the code. Another thing you can check is to make sure the PGID and PUID variables are correctly set to match your NAS. If they’re not set properly that could prevent the container from being able to write anything to its “/config” folder.