ebnerjoh

Members
  • Posts

    167
  • Joined

  • Last visited

Posts posted by ebnerjoh

  1. Ok, it seems not to be a Java Version issue, as I was able to see that the docker is running already java 17.

     

    But in MineOS - if I use a forge source 1.16.5, then a java runtime for that Verison is created, which I can select and start.

     

    But with every newer version the executable Verison is is not created.

  2. On 9/29/2022 at 3:42 AM, cenzar said:

    I'm having an issue where after a couple of days running on my unraid server the webui becomes inaccessible. My browser can no longer access it, the logs don't show any errors. The only thing that occurs on my server is a back up and auto update process, i'm wondering if it has issues with the docker shutting down and restarting after a backup. Any assistance would be greatly appreciated, currently I usually have to reinstall the docker container to get the ui working again.

     

    Have you found a solution for your issue?

     

    Br,

    Johannes

     

  3. On 9/29/2022 at 3:42 AM, cenzar said:

    I'm having an issue where after a couple of days running on my unraid server the webui becomes inaccessible. My browser can no longer access it, the logs don't show any errors. The only thing that occurs on my server is a back up and auto update process, i'm wondering if it has issues with the docker shutting down and restarting after a backup. Any assistance would be greatly appreciated, currently I usually have to reinstall the docker container to get the ui working again.

     

    I have the same issue. MY workaround is at the moment to enable "privileged mode", restart docker, disable "privileged mode", restart docker again. 

     

    Most of the time the WebUI is then reachable after some seconds...

  4. On 2/1/2022 at 6:56 PM, pengrus said:

    Have you tried starting with the --tc-heuristic-recover switch?

     

    At this point, I'm about ready to migrate everything back to MySQL, all of this weird behavior in the past few months is concerning at best.  Looks like there's an "official" docker from Bungy, relevant XML here.

     

    Yes, I have. Also the one with "rollback".

  5. I am starting to hate MariaDB on Unraid (or I am just an idiot)...

     

    Now after every MariaDB somehow my Databases are not working anymore.

     

    Upraded today to the latest version:

     

    Quote

    220130 08:27:41 mysqld_safe Logging to '/config/databases/d6db1815057e.err'.
    220130 08:27:41 mysqld_safe Starting mariadbd daemon with databases from /config/databases
    UMASK must be a 3-digit mode with an additional leading 0 to indicate octal.
    The first digit will be corrected to 6, the others may be 0, 2, 4, or 6.
    UMASK corrected from 022 to 0640 ...
    220130 08:27:42 mysqld_safe Logging to '/config/databases/d6db1815057e.err'.
    220130 08:27:42 mysqld_safe Starting mariadbd daemon with dat

     

    220130 08:31:57 mysqld_safe Starting mariadbd daemon with databases from /config/databases
    2022-01-30  8:31:57 0 [Note] /usr/bin/mariadbd (mysqld 10.5.13-MariaDB-log) starting as process 30017 ...
    2022-01-30  8:31:57 0 [Note] InnoDB: Uses event mutexes
    2022-01-30  8:31:57 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
    2022-01-30  8:31:57 0 [Note] InnoDB: Number of pools: 1
    2022-01-30  8:31:57 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
    2022-01-30  8:31:57 0 [Note] InnoDB: Using Linux native AIO
    2022-01-30  8:31:57 0 [Note] InnoDB: Initializing buffer pool, total size = 268435456, chunk size = 134217728
    2022-01-30  8:31:57 0 [Note] InnoDB: Completed initialization of buffer pool
    2022-01-30  8:31:57 0 [Note] InnoDB: Transaction 17363023 was in the XA prepared state.
    2022-01-30  8:31:57 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 0 row operations to undo
    2022-01-30  8:31:57 0 [Note] InnoDB: Trx id counter is 17363024
    2022-01-30  8:31:57 0 [Note] InnoDB: 128 rollback segments are active.
    2022-01-30  8:31:57 0 [Note] InnoDB: Starting in background the rollback of recovered transactions
    2022-01-30  8:31:57 0 [Note] InnoDB: Rollback of non-prepared transactions completed
    2022-01-30  8:31:57 0 [Note] InnoDB: Creating shared tablespace for temporary tables
    2022-01-30  8:31:57 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
    2022-01-30  8:31:57 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
    2022-01-30  8:31:57 0 [Note] InnoDB: 10.5.13 started; log sequence number 29677261474; transaction id 17363025
    2022-01-30  8:31:57 0 [Note] Plugin 'FEEDBACK' is disabled.
    2022-01-30  8:31:57 0 [Note] InnoDB: Loading buffer pool(s) from /config/databases/ib_buffer_pool
    2022-01-30  8:31:57 0 [Note] InnoDB: Starting recovery for XA transactions...
    2022-01-30  8:31:57 0 [Note] InnoDB: Transaction 17363023 in prepared state after recovery
    2022-01-30  8:31:57 0 [Note] InnoDB: Transaction contains changes to 2 rows
    2022-01-30  8:31:57 0 [Note] InnoDB: 1 transactions in prepared state after recovery
    2022-01-30  8:31:57 0 [Note] Found 1 prepared transaction(s) in InnoDB
    2022-01-30  8:31:57 0 [ERROR] Found 1 prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or tc.log file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.
    2022-01-30  8:31:57 0 [ERROR] Aborting
    220130 08:31:58 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

  6. Hello,

     

    I am running bitwarden (and now vaultwarden) since long time now with 2 accounts.

     

    Now I wanted to add a third account, but I cannot. 

     

    First I tried to activate via the Admin-Portal. It said "send invitation" but nothing came to the users email account.

    Then I deleted the account again and tried to register the user via the Login Page. Although I have deleted the Account on the Admin-Page, I am getting "user exists"....

  7. Then I opened a cmd-line to the docker and exexuted:

     

    root@92ecc8717197:/# mysqld --user=root --tc-heuristic-recover rollback
    2021-10-29 11:32:32 0 [Note] mysqld (mysqld 10.5.12-MariaDB-log) starting as process 5366 ...
    2021-10-29 11:32:32 0 [Note] InnoDB: Uses event mutexes
    2021-10-29 11:32:32 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
    2021-10-29 11:32:32 0 [Note] InnoDB: Number of pools: 1
    2021-10-29 11:32:32 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
    2021-10-29 11:32:32 0 [Note] mysqld: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
    2021-10-29 11:32:32 0 [Note] InnoDB: Using Linux native AIO
    2021-10-29 11:32:32 0 [Note] InnoDB: Initializing buffer pool, total size = 268435456, chunk size = 134217728
    2021-10-29 11:32:32 0 [Note] InnoDB: Completed initialization of buffer pool
    2021-10-29 11:32:32 0 [Note] InnoDB: 128 rollback segments are active.
    2021-10-29 11:32:32 0 [Note] InnoDB: Creating shared tablespace for temporary tables
    2021-10-29 11:32:32 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
    2021-10-29 11:32:32 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
    2021-10-29 11:32:32 0 [Note] InnoDB: 10.5.12 started; log sequence number 35028; transaction id 8
    2021-10-29 11:32:32 0 [Note] Plugin 'FEEDBACK' is disabled.
    2021-10-29 11:32:32 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded
    2021-10-29 11:32:32 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
    2021-10-29 11:32:32 0 [Note] Heuristic crash recovery mode
    2021-10-29 11:32:32 0 [Note] Please restart mysqld without --tc-heuristic-recover
    2021-10-29 11:32:32 1 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1017: Can't find file: './mysql/' (errno: 2 "No such file or directory")
    2021-10-29 11:32:32 0 [Note] InnoDB: Buffer pool(s) load completed at 211029 11:32:32
    2021-10-29 11:32:32 0 [ERROR] Can't init tc log


    2021-10-29 11:32:32 0 [ERROR] Aborting

  8. On 10/26/2021 at 11:41 AM, j0nnymoe said:

     

    This has already been heavily discussed with solutions in previous posts of this thread.

     

    Unfortunatley nothing helped for me.

     

    I have completely removed MariaDB-Docker and reinstalled. 

    A fresh installation is working. But when I copy/paste "databases"-Directory, then its failing again.


     

    UMASK must be a 3-digit mode with an additional leading 0 to indicate octal.
    The first digit will be corrected to 6, the others may be 0, 2, 4, or 6.
    UMASK corrected from 022 to 0640 ...
    211029 11:27:36 mysqld_safe Logging to '/config/databases/92ecc8717197.err'.
    211029 11:27:36 mysqld_safe Starting mariadbd daemon with databases from /config/databases

     

    211029 11:29:59 mysqld_safe Starting mariadbd daemon with databases from /config/databases
    2021-10-29 11:29:59 0 [Note] /usr/bin/mariadbd (mysqld 10.5.12-MariaDB-log) starting as process 4723 ...
    2021-10-29 11:29:59 0 [Note] InnoDB: Uses event mutexes
    2021-10-29 11:29:59 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
    2021-10-29 11:29:59 0 [Note] InnoDB: Number of pools: 1
    2021-10-29 11:29:59 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
    2021-10-29 11:29:59 0 [Note] mariadbd: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
    2021-10-29 11:29:59 0 [Note] InnoDB: Using Linux native AIO
    2021-10-29 11:29:59 0 [Note] InnoDB: Initializing buffer pool, total size = 268435456, chunk size = 134217728
    2021-10-29 11:29:59 0 [Note] InnoDB: Completed initialization of buffer pool
    2021-10-29 11:29:59 0 [Note] InnoDB: Transaction 209762720 was in the XA prepared state.
    2021-10-29 11:29:59 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 0 row operations to undo
    2021-10-29 11:29:59 0 [Note] InnoDB: Trx id counter is 209762721
    2021-10-29 11:29:59 0 [Note] InnoDB: 128 rollback segments are active.
    2021-10-29 11:29:59 0 [Note] InnoDB: Starting in background the rollback of recovered transactions
    2021-10-29 11:29:59 0 [Note] InnoDB: Rollback of non-prepared transactions completed
    2021-10-29 11:29:59 0 [Note] InnoDB: Creating shared tablespace for temporary tables
    2021-10-29 11:29:59 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
    2021-10-29 11:29:59 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
    2021-10-29 11:29:59 0 [Note] InnoDB: 10.5.12 started; log sequence number 402194885721; transaction id 209762722
    2021-10-29 11:29:59 0 [Note] Plugin 'FEEDBACK' is disabled.
    2021-10-29 11:29:59 0 [Note] InnoDB: Loading buffer pool(s) from /config/databases/ib_buffer_pool
    2021-10-29 11:29:59 0 [Note] InnoDB: Buffer pool(s) load completed at 211029 11:29:59
    2021-10-29 11:29:59 0 [Note] InnoDB: Starting recovery for XA transactions...
    2021-10-29 11:29:59 0 [Note] InnoDB: Transaction 209762720 in prepared state after recovery
    2021-10-29 11:29:59 0 [Note] InnoDB: Transaction contains changes to 4 rows
    2021-10-29 11:29:59 0 [Note] InnoDB: 1 transactions in prepared state after recovery
    2021-10-29 11:29:59 0 [Note] Found 1 prepared transaction(s) in InnoDB
    2021-10-29 11:29:59 0 [ERROR] Found 1 prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or tc.log file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.
    2021-10-29 11:29:59 0 [ERROR] Aborting
    211029 11:29:59 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended


     

  9. Hi,

     

    Today I updated the MariaDB Docker and now it is not starting anymore.

     

    the err-log shows the following:

     

    2021-10-23 17:53:53 0 [ERROR] Found 1 prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or tc.log file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.
    2021-10-23 17:53:53 0 [ERROR] Aborting


    any ideas?

     

    Br,

    Johannes

  10. Hi,

     

    I am running Home Assistant as Docker on my UnRaid Installation via Letsencrypt Reverse Proxy to expose it to the internet.

     

    I would also have two VPN Solutions configured:

    1) OpenVPN as Docker on Unraid

    2) L2TP on my Unifi USG Firewall

     

    So basically I could deactivate the Reverse Proxy for HomeAssistant but this has one big disadvantage: My parents are also using Home Assistant access from their iPhones.

    Either I get "On-Demand VPN" working on iOS, but as far as I can say now I would need a MAC to configure the Profiles (and I do not own a MAC) or I keep Reverse Proxy enabled for Home Assistant or someone has another great idea for me.

     

    Br,

    Johannes

  11. Hi, 

     

    I have a big issue.

     

    I have a "Node Red" Docker running, but because of an issue with an plugin it stops from time to time. Until I get this fixed, I wanted that the Docker starts automatically, when it crashes and I found an thread where they mentioned to add the EXTRA_PArameter "--restart unless-stopped".

     

    I have done this and applied the changes. It failed and now I cannot see the Docker in the Docker List anymore...