ku8475

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by ku8475

  1. @goobaroo , forgive my ingnorance but I am trying to get the life in the village to work for my daughter and I keep getting this message and it killing itself: (to execute a single source-file program) Arguments following the main class, source file, -jar <jarfile>, -m or --module <module>/<mainclass> are passed as the arguments to main class. where options include: -cp <class search path of directories and zip/jar files> -classpath <class search path of directories and zip/jar files> --class-path <class search path of directories and zip/jar files> A : separated list of directories, JAR archives, and ZIP archives to search for class files. -p <module path> --module-path <module path>... A : separated list of directories, each directory is a directory of modules. --upgrade-module-path <module path>... A : separated list of directories, each directory is a directory of modules that replace upgradeable modules in the runtime image --add-modules <module name>[,<module name>...] root modules to resolve in addition to the initial module. <module name> can also be ALL-DEFAULT, ALL-SYSTEM, ALL-MODULE-PATH. --enable-native-access <module name>[,<module name>...] modules that are permitted to perform restricted native operations. <module name> can also be ALL-UNNAMED. --list-modules list observable modules and exit -d <module name> --describe-module <module name> describe a module and exit --dry-run create VM and load main class but do not execute main method. The --dry-run option may be useful for validating the command-line options such as the module system configuration. --validate-modules validate all modules and exit The --validate-modules option may be useful for finding conflicts and other errors with modules on the module path. -D<name>=<value> set a system property -verbose:[class|module|gc|jni] enable verbose output for the given subsystem -version print product version to the error stream and exit --version print product version to the output stream and exit -showversion print product version to the error stream and continue --show-version print product version to the output stream and continue --show-module-resolution show module resolution output during startup -? -h -help print this help message to the error stream --help print this help message to the output stream -X print help on extra options to the error stream --help-extra print help on extra options to the output stream -ea[:<packagename>...|:<classname>] -enableassertions[:<packagename>...|:<classname>] enable assertions with specified granularity -da[:<packagename>...|:<classname>] -disableassertions[:<packagename>...|:<classname>] disable assertions with specified granularity -esa | -enablesystemassertions enable system assertions -dsa | -disablesystemassertions disable system assertions -agentlib:<libname>[=<options>] load native agent library <libname>, e.g. -agentlib:jdwp see also -agentlib:jdwp=help -agentpath:<pathname>[=<options>] load native agent library by full pathname -javaagent:<jarpath>[=<options>] load Java programming language agent, see java.lang.instrument -splash:<imagepath> show splash screen with specified image HiDPI scaled images are automatically supported and used if available. The unscaled image filename, e.g. image.ext, should always be passed as the argument to the -splash option. The most appropriate scaled image provided will be picked up automatically. See the SplashScreen API documentation for more information @argument files one or more argument files containing options -disable-@files prevent further argument file expansion --enable-preview allow classes to depend on preview features of this release To specify an argument for a long option, you can use --<name>=<value> or --<name> <value>. ** Press ANY KEY to close this window ** I am assuming it needs another argument to start. What do I need to add to the docker template to get it to start?
  2. I might be an idiot, but is there a way to use swag to make my website point to this?
  3. Having the same dead nextcloud on update issues you are having. Sounds like you run the same setup as I do. I will patentily await your findings while tinkering to see if I can figure it out as well.
  4. I am getting "2021-04-15 18:12:00.934970 [info] CUSTOM_JAR_PATH defined as '/config/minecraft/minecraft_server.jar' 2021-04-15 18:12:00.975017 [info] JAVA_VERSION defined as '8' '/usr/lib/jvm/java-8-openjdk/jre' is not a valid Java environment path" I have been running fine until the update. Did something change in the settings that I need to repath this?
  5. So it turned out that one of the memory sticks failed MemTest86. So I am running to MicroCenter to return it now. Hopefully that fixes the issues.
  6. Ok, I will try and update the board today and run a memtest. The fact that it ran stable for a month before I did the upgrade doesn't remove these as possible issues does it?
  7. Ok so my adventure begins with me updating my Unraid to the beta. I have a x570 mobo so I wanted to see my temps. I thought it was a good idea. It worked ok until I installed IPMI plugin and some server monitoring docker with neat graphs from the comapp that has like a rodent or something as the logo. Anyways, overnight that killed my server. I had to restart it and than I removed the docker and the plugin. After that it kept becoming unreachable ever day or so. So I decided maybe beta isn't a good call. So I recovered to 6.8.3. So I booted it up to find that my cache pool of two SSDs' was not assigned or even existing anymore. It was as if there never was a cache. So I reassigned them to the appropriate spots and ran the array. After that it started giving these BTRFS errors and crashing. So far I have removed the cache array and wiped both drives completely. Restored the appdata from backup. Removed and re-added the dockers from the appstore as I though that was what was causing the fails. I am at a loss. Maybe it is a failing SSD, but I find it hard to believe its passing smart tests and now just wants to quit. I don't really grasp BTRFS so I figured I botched that up some how. I will attach logs that I took before the latest crash. Also the last crash here are the logs as it crashed. Dec 2 20:11:51 Tower avahi-daemon[10415]: Registering new address record for fe80::cc6b:86ff:fe07:72fa on veth0425396.*. Dec 2 20:45:00 Tower kernel: mpt3sas 0000:04:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000c0090000 flags=0x0090] Dec 2 20:45:00 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:00 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:00 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:00 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:00 Tower kernel: mpt3sas 0000:04:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000c1690000 flags=0x0090] Dec 2 20:45:01 Tower kernel: sd 14:0:2:0: Power-on or device reset occurred Dec 2 20:45:01 Tower kernel: mpt3sas 0000:04:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000c1a90000 flags=0x0090] Dec 2 20:45:01 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:01 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:01 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:01 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:01 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:01 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:01 Tower kernel: sd 14:0:1:0: Power-on or device reset occurred Dec 2 20:45:01 Tower kernel: sd 14:0:2:0: Power-on or device reset occurred Dec 2 20:45:01 Tower kernel: mpt3sas 0000:04:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000c1090000 flags=0x0090] Dec 2 20:45:01 Tower kernel: mpt3sas 0000:04:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000c1290000 flags=0x0090] Dec 2 20:45:01 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:01 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:01 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:01 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:01 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:02 Tower kernel: sd 14:0:2:0: Power-on or device reset occurred Dec 2 20:45:02 Tower kernel: mpt3sas 0000:04:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000c1690000 flags=0x0090] Dec 2 20:45:02 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:02 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:02 Tower kernel: sd 14:0:2:0: [sdk] tag#1284 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 Dec 2 20:45:02 Tower kernel: sd 14:0:2:0: [sdk] tag#1284 CDB: opcode=0x28 28 00 3a 38 5f 80 00 00 08 00 Dec 2 20:45:02 Tower kernel: print_req_error: I/O error, dev sdk, sector 976772992 Dec 2 20:45:02 Tower kernel: sd 14:0:1:0: Power-on or device reset occurred Dec 2 20:45:02 Tower kernel: sd 14:0:2:0: Power-on or device reset occurred Dec 2 20:45:02 Tower kernel: mpt3sas 0000:04:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000c1690000 flags=0x0090] Dec 2 20:45:02 Tower kernel: mpt3sas 0000:04:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000c1490000 flags=0x0090] Dec 2 20:45:02 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:02 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:02 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:02 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:02 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:02 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:02 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:02 Tower kernel: sd 14:0:2:0: [sdk] tag#1285 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 Dec 2 20:45:02 Tower kernel: sd 14:0:2:0: [sdk] tag#1285 CDB: opcode=0x28 28 00 3a 38 60 20 00 00 08 00 Dec 2 20:45:02 Tower kernel: print_req_error: I/O error, dev sdk, sector 976773152 Dec 2 20:45:02 Tower kernel: sd 14:0:2:0: Power-on or device reset occurred Dec 2 20:45:02 Tower kernel: mpt3sas 0000:04:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000c0690000 flags=0x0090] Dec 2 20:45:02 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:02 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:02 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:02 Tower kernel: sd 14:0:2:0: [sdk] tag#1290 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 Dec 2 20:45:02 Tower kernel: sd 14:0:2:0: [sdk] tag#1290 CDB: opcode=0x2a 2a 00 0e 99 83 c0 00 0a 00 00 Dec 2 20:45:02 Tower kernel: print_req_error: I/O error, dev sdk, sector 244941760 Dec 2 20:45:02 Tower kernel: BTRFS error (device sdj1): bdev /dev/sdk1 errs: wr 54, rd 0, flush 0, corrupt 57, gen 0 Dec 2 20:45:02 Tower kernel: BTRFS error (device sdj1): bdev /dev/sdk1 errs: wr 55, rd 0, flush 0, corrupt 57, gen 0 Dec 2 20:45:02 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:02 Tower kernel: BTRFS error (device sdj1): bdev /dev/sdk1 errs: wr 56, rd 0, flush 0, corrupt 57, gen 0 Dec 2 20:45:02 Tower kernel: BTRFS error (device sdj1): bdev /dev/sdk1 errs: wr 57, rd 0, flush 0, corrupt 57, gen 0 Dec 2 20:45:02 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:02 Tower kernel: BTRFS error (device sdj1): bdev /dev/sdk1 errs: wr 58, rd 0, flush 0, corrupt 57, gen 0 Dec 2 20:45:02 Tower kernel: BTRFS error (device sdj1): bdev /dev/sdk1 errs: wr 59, rd 0, flush 0, corrupt 57, gen 0 Dec 2 20:45:02 Tower kernel: BTRFS error (device sdj1): bdev /dev/sdk1 errs: wr 60, rd 0, flush 0, corrupt 57, gen 0 Dec 2 20:45:02 Tower kernel: BTRFS error (device sdj1): bdev /dev/sdk1 errs: wr 61, rd 0, flush 0, corrupt 57, gen 0 Dec 2 20:45:02 Tower kernel: BTRFS error (device sdj1): bdev /dev/sdk1 errs: wr 62, rd 0, flush 0, corrupt 57, gen 0 Dec 2 20:45:02 Tower kernel: BTRFS error (device sdj1): bdev /dev/sdk1 errs: wr 63, rd 0, flush 0, corrupt 57, gen 0 Dec 2 20:45:02 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:02 Tower kernel: sd 14:0:1:0: Power-on or device reset occurred Dec 2 20:45:02 Tower kernel: mpt3sas 0000:04:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000c1890000 flags=0x0090] Dec 2 20:45:03 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:03 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:03 Tower kernel: sd 14:0:2:0: Power-on or device reset occurred Dec 2 20:45:03 Tower rc.diskinfo[9324]: SIGHUP received, forcing refresh of disks info. Dec 2 20:45:03 Tower kernel: sd 14:0:1:0: Power-on or device reset occurred Dec 2 20:45:03 Tower kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=04:00.0 domain=0x0000 address=0x00000000c1690000 flags=0x0090] Dec 2 20:45:04 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:04 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:04 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:04 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:04 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:04 Tower kernel: mpt2sas_cm1: log_info(0x31120322): originator(PL), code(0x12), sub_code(0x0322) Dec 2 20:45:04 Tower kernel: sd 14:0:1:0: Power-on or device reset occurred Dec 2 20:45:04 Tower kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=04:00.0 domain=0x0000 address=0x00000000c1a90000 flags=0x0090] Any help would be swell. Or atleast instructions on how to start fresh without losing my parity and all my data.tower-diagnostics-20201202-1908.zip
  8. I started using unraid with no docker or link experience. I love the support of the community and the features that made unraid easy enough to figure out. What I want for new OS feature is more driver support for video cards, pcie controllers, and other such things. Also maybe easier dashboard graphic customisation.