Jump to content

chaosratt

Members
  • Content Count

    43
  • Joined

  • Last visited

Community Reputation

1 Neutral

About chaosratt

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Is there any reason why on Sunday (the 1st) this, and only this, docker seems to have just poofed out of existence? No longer appears in my docker list, and cant find it by searching. Had all my apps working off of it just fine, then noticed that I hadn't been downloading anything in a week and found this docker just missing.
  2. I just wanted to chime in here on a fix for the the container seeming to not start properly. There's no need to do a full appdata rollback usually. Log into the container: docker exec -ti mariadb /bin/bash run mysqld from the commandline and you'll get a full dump of what's wrong. It's likely *not* a corrupt database, but rather a transaction stuck in a partially completed state: root@dc9091e5cc9e:/# mysqld blah blah blah blah InnoDB: Transaction 133548158 was in the XA prepared state. InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 0 row operations to undo InnoDB: Trx id counter is 205501440 2017-12-01 21:37:20 47062243925760 [Note] InnoDB: 128 rollback segment(s) are active. 2017-12-01 21:37:20 47063031092992 [Note] InnoDB: Starting in background the rollback of recovered transactions 2017-12-01 21:37:20 47063031092992 [Note] InnoDB: Rollback of non-prepared transactions completed 2017-12-01 21:37:20 47062243925760 [Note] InnoDB: Waiting for purge to start 2017-12-01 21:37:20 47062243925760 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 72011254996 2017-12-01 21:37:20 47062243925760 [Note] Plugin 'FEEDBACK' is disabled. 2017-12-01 21:37:20 47063066740480 [Note] InnoDB: Dumping buffer pool(s) not yet started 2017-12-01 21:37:20 2acd8854df00 InnoDB: Starting recovery for XA transactions... 2017-12-01 21:37:20 2acd8854df00 InnoDB: Transaction 133548158 in prepared state after recovery 2017-12-01 21:37:20 2acd8854df00 InnoDB: Transaction contains changes to 8 rows 2017-12-01 21:37:20 2acd8854df00 InnoDB: 1 transactions in prepared state after recovery 2017-12-01 21:37:20 47062243925760 [Note] Found 1 prepared transaction(s) in InnoDB 2017-12-01 21:37:20 47062243925760 [ERROR] Found 1 prepared transactions! It means that mysqld was not shut down properly last time and critical recovery in formation (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. 2017-12-01 21:37:20 47062243925760 [ERROR] Aborting Your choice is to "hulk smash" the partial transaction through, or revert it like it never happened. Both have potential consequences. mysqld --tc-heuristic-recover commit or mysqld --tc-heuristic-recover rollback Also, you have backups, right?
  3. Is this docker ever going to be updated? its based on 14.04LTS (now 1 year "obsolete") and is running PHP 5.5. Most apps need at least 5.6 to run, and preferably 7.x. I've tried to manually update it (knowing it would be lost on an update) but it just ends up returning server 500 errors when I try.
  4. Ugh, that's basically an even more PITA way of doing the advanced_script, I understand why they don't want to support it, but still, would be nice to have a way of consistently adding packages that we might need to the image. Unless they want to go ahead and add handbrake, ffmpeg, comskip, etc now that plex has native DVR capabilities ...
  5. SO there's no way for us to add customization to the docker (such as install handbrakecli for post-processing) that can survive an image update?
  6. Does the 'ADVANCED_SCRIPT' variable no longer work on this container?
  7. I'm not sure what the point would be. I use keys to log into all my devices, and nothing else exhibits this issue with the default putty settings.
  8. It's set to defaults, which work perfectly fine on many other linux servers and VMs, just Unraid that has the issue. The settings look exactly the same as your pic, except the columns and rows change to match the window size. its almost as if something server-side is not registering or acknowledging the new size.
  9. THe line wraps about halfway across the window, regardless of how wide it is. It also wraps *onto the same line* not the line under it, which causes the command to overwrite itself. For example, running a simple mv command with full pathing is impossible, same goes for some long one-off docker commands.
  10. I'm having this same issue, putty on Windows 10, also happens with Windows 7.
  11. Is it possible to get BorgBackup added to the pack? https://borgbackup.readthedocs.io/en/stable/installation.html#standalone-binary
  12. Unraid is 6.3.5, plugin is 2017.03.03
  13. Not sure what just happened, but the layout tab spits this error out at me now: Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 126 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 126 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 126 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 And the data tab's historical table is empty and all the assignments are lost.
  14. Pretty standard setup as far as I'm aware. SuperMicro SC846 chassis with SAS2 backplane, SATA drives, LSI Controller (M1015 flashed to HBA mode). Can't remember if I had 1 or 2 cables going to the backplane from the controller off hand, will have to check when I get home.
  15. I noticed you asked another user for this on the last page for troubleshooting, while I don't have the same problem here is my output if it helps: Unraid is 6.3.5 root@Unraid:~# lsscsi -i [0:0:0:0] disk SanDisk Cruzer Fit 1.27 /dev/sda SanDisk_Cruzer_Fit_4C530012270322105470-0:0 [1:0:0:0] cd/dvd HL-DT-ST BDDVDRW GGC-H20L 1.03 /dev/sr0 HL-DT-ST_BDDVDRW_GGC-H20L_123456789C5F-0:0 [2:0:0:0] disk ATA TOSHIBA DT01ACA3 ABB0 /dev/sdb - [2:0:1:0] disk ATA TOSHIBA HDWD130 ACF0 /dev/sdc - [2:0:2:0] disk ATA TOSHIBA HDWD130 ACF0 /dev/sdd - [2:0:3:0] disk ATA WDC WD10EACS-00D 1A01 /dev/sde - [2:0:4:0] disk ATA ST4000DM000-1F21 CC54 /dev/sdf - [2:0:5:0] disk ATA TOSHIBA DT01ACA3 ABB0 /dev/sdg - [2:0:6:0] disk ATA Hitachi HUS72403 A5F0 /dev/sdh - [2:0:7:0] disk ATA Hitachi HUS72403 A5F0 /dev/sdi - [2:0:8:0] disk ATA TOSHIBA DT01ACA3 ABB0 /dev/sdj - [2:0:9:0] disk ATA WDC WD10EACS-00D 1A01 /dev/sdk - [2:0:10:0] disk ATA Hitachi HUS72403 A5F0 /dev/sdl - [2:0:11:0] disk ATA TOSHIBA DT01ACA3 ABB0 /dev/sdm - [2:0:12:0] disk ATA WDC WD10EARX-00N AB51 /dev/sdn - [2:0:13:0] disk ATA WDC WD10EACS-00D 1A01 /dev/sdo - [2:0:14:0] disk ATA TOSHIBA DT01ACA3 ABB0 /dev/sdp - [2:0:15:0] disk ATA TOSHIBA DT01ACA3 ABB0 /dev/sdq - [2:0:16:0] disk ATA SAMSUNG MZ7WD480 NS00 /dev/sdr - [2:0:17:0] disk ATA TOSHIBA DT01ACA3 ABB0 /dev/sds - [2:0:18:0] disk ATA ST3000DM001-1ER1 CC43 /dev/sdt - [2:0:19:0] disk ATA WDC WD10EACS-00Z 1B01 /dev/sdu - [2:0:20:0] disk ATA ST4000DM000-1F21 CC54 /dev/sdv - [2:0:21:0] enclosu LSI CORP SAS2X36 0717 - - [2:0:22:0] disk ATA ST4000DM005-2DP1 0001 /dev/sdw - [2:0:23:0] disk ATA ST4000DM005-2DP1 0001 /dev/sdx -