gravymaker
-
Posts
27 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by gravymaker
-
-
UNMS DOCKER QUESTION - DISABLING 2FA
I've got myself into a bit of a pickle. I got a new phone and migrated all data and apps, but I didn't realize the Google Authenticator information was not part of the Samsung Sync process. So now I can't access my UNMS docker as it is requesting the 2FA code. (Old phone was wiped.)
There are instructions on the web for resetting 2FA (https://community.ui.com/questions/reset-2fa-to-local-unms-server/458ddf6a-4ef9-465d-94e5-a3c113d4c8f4) but the UNMS docker doesn't appear to have the "unms-cli" command when I try these instructions.
I've tried running both the docker-compose command at the unraid command line, as well as trying the unms-cli command from a command prompt within the docker itself.
Has anyone run into this?
-
Thanks xxbigfootxx - I think blowing away and reinstalling MariaDB has me back on track. Appreciate the help!
-
OK - yeah, tried the force update on MariaDB, but it does look like something is wrong with MariaDB. Although it shows as "started" in the Unraid GUI, the MariaDB log shows that it is constantly restarting. Lots of this repeating in the log:
2021-09-13 17:31:14 0 [Note] /usr/bin/mariadbd (mysqld 10.5.12-MariaDB-log) starting as process 705 ... 2021-09-13 17:31:14 0 [Note] InnoDB: Uses event mutexes 2021-09-13 17:31:14 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2021-09-13 17:31:14 0 [Note] InnoDB: Number of pools: 1 2021-09-13 17:31:14 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2021-09-13 17:31:14 0 [Note] mariadbd: O_TMPFILE is not supported on /var/tmp (disabling future attempts) 2021-09-13 17:31:14 0 [Note] InnoDB: Using Linux native AIO 2021-09-13 17:31:14 0 [Note] InnoDB: Initializing buffer pool, total size = 268435456, chunk size = 134217728 2021-09-13 17:31:14 0 [Note] InnoDB: Completed initialization of buffer pool 2021-09-13 17:31:14 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.4.18. 2021-09-13 17:31:14 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2021-09-13 17:31:14 0 [Note] InnoDB: Starting shutdown... 2021-09-13 17:31:14 0 [ERROR] Plugin 'InnoDB' init function returned error. 2021-09-13 17:31:14 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2021-09-13 17:31:14 0 [Note] Plugin 'FEEDBACK' is disabled. 2021-09-13 17:31:14 0 [ERROR] Unknown/unsupported storage engine: InnoDB 2021-09-13 17:31:14 0 [ERROR] Aborting -
Hope this is the right spot for Authelia support questions...it's been awhile since I've posted, everything has been working very well.
I applied some docker updates this morning, but now I cannot get Authelia to start. Redis, MariaDB and swag all start ok, but Authelia gives the following error:
time="2021-09-13T17:16:02-05:00" level=info msg="Authelia v4.30.4 is starting" time="2021-09-13T17:16:02-05:00" level=info msg="Log severity set to debug" time="2021-09-13T17:16:02-05:00" level=debug msg="Storage schema is being checked to verify it is up to date" [mysql] 2021/09/13 17:16:02 packets.go:37: unexpected EOF [mysql] 2021/09/13 17:16:02 packets.go:37: unexpected EOF [mysql] 2021/09/13 17:16:02 packets.go:37: unexpected EOF time="2021-09-13T17:16:02-05:00" level=fatal msg="Unable to initialize SQL database: driver: bad connection" stack="github.com/authelia/authelia/v4/internal/storage/mysql_provider.go:81 NewMySQLProvider\ngithub.com/authelia/authelia/v4/internal/commands/root.go:95 getProviders\ngithub.com/authelia/authelia/v4/internal/commands/root.go:65 cmdRootRun\ngithub.com/spf13/[email protected]/command.go:860 (*Command).execute\ngithub.com/spf13/[email protected]/command.go:974 (*Command).ExecuteC\ngithub.com/spf13/[email protected]/command.go:902 main\ngithub.com/authelia/authelia/v4/cmd/authelia/main.go:11 main\nruntime/proc.go:225 main\nruntime/asm_amd64.s:1371 goexit"Has anyone else seen this?
-
Thanks for confirming. I'll create a workaround.
-
Interesting... the python script I'm running is a post-processing script to mount an ISO after downloading. For months, I was using this command to mount and it worked ok:
subprocess.call(['/usr/bin/sudo', '/bin/mount', '-t', 'iso9660', '-o', 'loop', isoPath, tempdir])
To get sudo to work I had to copy a "sudoers" file into the container whenever SABNZBD was restarted, but this worked ok.
After I applied the last sabnzbd update, I started getting the "sudo not found" error. So I removed the "sudo" part of the command and tried this:
subprocess.call(['/bin/mount', '-t', 'iso9660', '-o', 'loop', isoPath, tempdir])
Now when the post-processing script runs, I see the following error in the SABNZBD log:
mount: only root can use "--options" option
I'm not exactly sure which account SABNZBD uses when it executes the post-processing scripts? Does it run with root privileges?
Thanks - appreciate your thoughts!
-
Is sudo missing from the latest base image? I use sudo in some scripts and after upgrading to the latest container release, I get "sudo: command not found"
-
Procedure to convert drives to XFS format
================================
System assumptions before you begin:
<snip>
I followed RobJ's excellent instructions and converted 12 disks, including the cache drive, from RFS to XFS in about a week. Great tips to use "screen" and go slow and triple check each key step along the way.
Thanks to everyone in this thread for great ideas, and to RobJ for the steps.
[support] digiblur's Docker Template Repository
in Docker Containers
Posted · Edited by gravymaker
cleaned up command
[SOLVED]
I was able to figure this out by reading the unms-cli file and figuring out what it actually calls. In this docker, its the "user.js" file that handles things!
So, my command was:
Just posting for any other idiots that forget to migrate their authenticator data!!