BusterBrawls

I installed RomM for the first time and ran into a few problems. I ended up rebuilding the Docker container configuration based on information I found on the rommapp GitHub unraid_template/romm.xml and now the errors are gone. Here's a copy of the configuration that I am using. You can edit your RomM container and use this as a reference. If you do, you'll probably want to make a few changes to things like the WebUI port and the location of the folders to match your system requirements. Some differences from the original config: Added variables for automated rom scanning. Added a variable for the MobyGames API key. Added variables for the UID and GID. Container config no longer needs extra parameters. Moved the assets and resources folders off of the cache drive and to my array. The thought process behind the resources folder is so those files don't eat up space on my cache drive. I feel that the assets folder should remain on the array is to protect the game saves and states and not lost if my cache drive dies. <Container version="2"> <Name>RomM</Name> <Repository>rommapp/romm:3.1.0-rc.2</Repository> <Registry>https://hub.docker.com/r/rommapp/romm</Registry> <Network>bridge</Network> <MyIP/> <Shell>sh</Shell> <Privileged>false</Privileged> <Support>https://github.com/rommapp/romm/issues</Support> <Project>https://github.com/rommapp/romm</Project> <Overview>RomM is a game library manager focused on retro games. Manage and organize all of your games from a web browser.</Overview> <Category>MediaApp:Other</Category> <WebUI>http://[IP]:[PORT:8080]</WebUI> <TemplateURL>https://github.com/rommapp/romm/blob/release/unraid_template/romm.xml</TemplateURL> <Icon>https://raw.githubusercontent.com/rommapp/romm/master/.github/resources/isotipo.png</Icon> <ExtraParams/> <PostArgs/> <CPUset/> <Requires>MariaDB</Requires> <Config Name="WebUI Port" Target="8080" Default="8080" Mode="tcp" Description="" Type="Port" Display="always" Required="false" Mask="false">8080</Config> <Config Name="Config" Target="/romm/config" Default="" Mode="rw" Description="Please copy the file at https://github.com/rommapp/romm/tree/release/examples/config.example.yml to the config folder and rename to 'config.yml'" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/appdata/romm/config</Config> <Config Name="Library" Target="/romm/library/" Default="" Mode="rw" Description="Your game library" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/emulation/</Config> <Config Name="Assets" Target="/romm/assets/" Default="" Mode="rw" Description="Uploaded saves, states, etc." Type="Path" Display="always" Required="false" Mask="false">/mnt/user/emulation/assets/</Config> <Config Name="Logs" Target="/romm/logs" Default="" Mode="rw" Description="Path where logs are stored" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/appdata/romm/logs</Config> <Config Name="Resources" Target="/romm/resources" Default="" Mode="rw" Description="Resources fetched from IGDB (covers, screenshots, etc.)" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/emulation/resources/</Config> <Config Name="Redis Data" Target="/redis-data" Default="" Mode="rw" Description="Cached data for background tasks" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/appdata/romm/redis-data</Config> <Config Name="RomM DB Host" Target="DB_HOST" Default="romm-db" Mode="" Description="Use the IP address of your MariaDB instance. Install MariaDB if you don't already have it." Type="Variable" Display="always" Required="false" Mask="false"></Config> <Config Name="RomM DB Name" Target="DB_NAME" Default="romm" Mode="" Description="Should match MYSQL_DATABASE in mariadb" Type="Variable" Display="always" Required="false" Mask="false">romm</Config> <Config Name="RomM DB User" Target="DB_USER" Default="romm-user" Mode="" Description="Should match MYSQL_USER in mariadb" Type="Variable" Display="always" Required="false" Mask="false">romm-user</Config> <Config Name="RomM DB Password" Target="DB_PASSWD" Default="" Mode="" Description="Should match MYSQL_PASSWORD in mariadb" Type="Variable" Display="always" Required="false" Mask="true"></Config> <Config Name="RomM DB Port" Target="DB_PORT" Default="3306" Mode="" Description="Should match your mariadb port. Default is: `3306`" Type="Variable" Display="always" Required="false" Mask="false">3306</Config> <Config Name="IGDB Client ID" Target="IGDB_CLIENT_ID" Default="" Mode="" Description="Generate an ID and SECRET in IGDB:&#13;&#10;https://api-docs.igdb.com/#account-creation" Type="Variable" Display="always" Required="false" Mask="true"></Config> <Config Name="IGDB Client Secret" Target="IGDB_CLIENT_SECRET" Default="" Mode="" Description="Generate an ID and SECRET in IGDB:&#13;&#10;https://api-docs.igdb.com/#account-creation" Type="Variable" Display="always" Required="false" Mask="true"></Config> <Config Name="RomM Auth Secret" Target="ROMM_AUTH_SECRET_KEY" Default="" Mode="" Description="Generate a key with `openssl rand -hex 32`" Type="Variable" Display="always" Required="false" Mask="true"></Config> <Config Name="RomM Auth Username" Target="ROMM_AUTH_USERNAME" Default="admin" Mode="" Description="Default is: `admin`" Type="Variable" Display="always" Required="false" Mask="false">admin</Config> <Config Name="RomM Auth Password" Target="ROMM_AUTH_PASSWORD" Default="admin" Mode="" Description="Default is: `admin`" Type="Variable" Display="always" Required="false" Mask="true"></Config> <Config Name="MobyGames API Key" Target="MOBYGAMES_API_KEY" Default="" Mode="" Description="" Type="Variable" Display="always" Required="false" Mask="true"></Config> <Config Name="Enable rescan on filesystem change" Target="ENABLE_RESCAN_ON_FILESYSTEM_CHANGE" Default="false" Mode="" Description="Run a scan when the filesystem changes" Type="Variable" Display="advanced" Required="false" Mask="false">false</Config> <Config Name="rescan on filesystem change delay" Target="RESCAN_ON_FILESYSTEM_CHANGE_DELAY" Default="5" Mode="" Description="Delay in seconds before running a scan" Type="Variable" Display="advanced" Required="false" Mask="false">5</Config> <Config Name="Enable scheduled scan" Target="ENABLE_SCHEDULED_RESCAN" Default="false" Mode="" Description="Run a scan on a schedule" Type="Variable" Display="advanced" Required="false" Mask="false">false</Config> <Config Name="Scheduled rescan schedule" Target="SCHEDULED_RESCAN_CRON" Default="0 3 * * *" Mode="" Description="Cron expression for scheduled scan" Type="Variable" Display="advanced" Required="false" Mask="false">0 3 * * *</Config> <Config Name="Enable scheduled update of Switch TitleDB" Target="ENABLE_SCHEDULED_UPDATE_SWITCH_TITLEDB" Default="false" Mode="" Description="Update Switch TitleDB on a schedule" Type="Variable" Display="advanced" Required="false" Mask="false">false</Config> <Config Name="Scheduled update of Switch TitleDB schedule" Target="SCHEDULED_UPDATE_SWITCH_TITLEDB_CRON" Default="0 4 * * *" Mode="" Description="Cron expression for scheduled Switch TitleDB update" Type="Variable" Display="advanced" Required="false" Mask="false">0 4 * * *</Config> <Config Name="PUID" Target="PUID" Default="99" Mode="" Description="" Type="Variable" Display="advanced-hide" Required="false" Mask="false">99</Config> <Config Name="PGID" Target="PGID" Default="100" Mode="" Description="" Type="Variable" Display="advanced-hide" Required="false" Mask="false">100</Config> <Config Name="UMASK" Target="UMASK" Default="000" Mode="" Description="" Type="Variable" Display="advanced-hide" Required="false" Mask="false">000</Config> </Container> Notes: After changing the repository from romm:latest to the romm:3.1.0-rc.2 I wasn't able to revert back to latest. I'm guessing it's related to changes made to the MariaDB database in the release candidate not being compatible with the older version of RomM. This could be tested by creating a new MariaDB database and updating the RomM config with the new database name. The XML file can be directly edited in /boot/config/plugins/dockerMan/templates-user/my-RomM.xml. Exercise caution when directly editing the configuration XML. I was getting permissions problems with /backend/handler/fixtures/MAME.xml. To fix I needed to change the permissions inside of the docker image itself. chgrp 1000 /backend/ -R chown 1000 /backend/ -R I haven't tested to see if this fixes the problem running /backend/tasks/update_mame_xml.py I ran this command after I bashed into the container. curl -o /backend/handler/fixtures/MAME.xml https://gist.githubusercontent.com/gantoine/0e2b9e25962bfd661ad2fe0ba0e72766/raw/gistfile1.txt

In fact, I do have a CA backup that starts at 3AM Monday mornings (Weekly). The containers usually restart after the backup and all others restart as expected. I'd be willing to believe this is responsible for one or two of the shutdowns. I'd also be willing to believe the switch to wireguard caused a couple issues until I got that updated. Looks like the issues are probably mine. The lack of restart is odd, but not necessarily a problem with the Docker image.

At least three times in less than 2 weeks I have woken up in the morning and found that the Docker container had stopped. The last collection of logs (supervisord.log) before I restarted the container is here: 2020-11-09 02:54:30,752 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '44976' 2020-11-09 03:00:07,108 WARN received SIGTERM indicating exit request 2020-11-09 03:00:07,108 DEBG killing watchdog-script (pid 155) with signal SIGTERM 2020-11-09 03:00:07,108 INFO waiting for start-script, watchdog-script to die 2020-11-09 03:00:08,109 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22428397286640 for <Subprocess at 22428394042608 with name watchdog-script in state STOPPING> (stdout)> 2020-11-09 03:00:08,109 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22428397335984 for <Subprocess at 22428394042608 with name watchdog-script in state STOPPING> (stderr)> 2020-11-09 03:00:08,110 INFO stopped: watchdog-script (terminated by SIGTERM) 2020-11-09 03:00:08,110 DEBG received SIGCHLD indicating a child quit 2020-11-09 03:00:08,110 DEBG killing start-script (pid 154) with signal SIGTERM 2020-11-09 03:00:09,111 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22428393173920 for <Subprocess at 22428393173968 with name start-script in state STOPPING> (stdout)> 2020-11-09 03:00:09,111 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22428394041936 for <Subprocess at 22428393173968 with name start-script in state STOPPING> (stderr)> 2020-11-09 03:00:09,111 INFO stopped: start-script (terminated by SIGTERM) 2020-11-09 03:00:09,112 DEBG received SIGCHLD indicating a child quit I would be happy to provide (or capture) any other logs necessary.

I can't keep qbittorrent open for a couple of days before it will eventually close on it's own. This is new behavior over the last couple of weeks. The only changes I've made to the configuration has been the updates for wireguard. Recently logged errors: "2020-11-09 07:35:11,796 DEBG 'start-script' stderr output: parse error: Invalid numeric literal at line 4, column 0" "2020-11-09 02:32:47,909 DEBG 'watchdog-script' stdout output: [warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed" *edit for spelling error