Rockstar
-
Posts
32 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Rockstar
-
-
44 minutes ago, wgstarks said:
This is likely your problem. You just need to get an up-to-date certificate.
What cert is this pulling from? the OpenVPN profile? -
I went on Vacation 7th and came back on the 9th... noticed the container was dead when I got home. Checked the logs, and the vpn isn't validating. No biggie, I use NordVPN so I went to their site and grabbed a new openvpn profile. Still not working...hmmm okay try this 3 or so more times to no success. I left it for the night and trying to troubleshoot some more.
anyone else having these issues specifically with Nord VPN? I'm getting an AUTH_FAILED message:
2023-07-10 12:25:58,565 DEBG 'start-script' stdout output: [info] Starting OpenVPN (non daemonised)... 2023-07-10 12:25:58,620 DEBG 'start-script' stdout output: 2023-07-10 12:25:58 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations. 2023-07-10 12:25:58 Note: '--allow-compression' is not set to 'no', disabling data channel offload. 2023-07-10 12:25:58,621 DEBG 'start-script' stdout output: 2023-07-10 12:25:58 WARNING: file 'credentials.conf' is group or others accessible 2023-07-10 12:25:58 OpenVPN 2.6.5 [git:makepkg/cbc9e0ce412e7b42+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Jun 13 2023 2023-07-10 12:25:58 library versions: OpenSSL 3.1.1 30 May 2023, LZO 2.10 2023-07-10 12:25:58,621 DEBG 'start-script' stdout output: 2023-07-10 12:25:58 DCO version: N/A 2023-07-10 12:25:58,621 DEBG 'start-script' stdout output: 2023-07-10 12:25:58 WARNING: --ping should normally be used with --ping-restart or --ping-exit 2023-07-10 12:25:58 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2023-07-10 12:25:58,622 DEBG 'start-script' stdout output: 2023-07-10 12:25:58 TCP/UDP: Preserving recently used remote address: [AF_INET]154.47.17.25:1194 2023-07-10 12:25:58,622 DEBG 'start-script' stdout output: 2023-07-10 12:25:58 Socket Buffers: R=[212992->212992] S=[212992->212992] 2023-07-10 12:25:58 UDPv4 link local: (not bound) 2023-07-10 12:25:58 UDPv4 link remote: [AF_INET]154.47.17.25:1194 2023-07-10 12:25:58,699 DEBG 'start-script' stdout output: 2023-07-10 12:25:58 TLS: Initial packet from [AF_INET]154.47.17.25:1194, sid=7e8fc475 43b39994 2023-07-10 12:25:58,857 DEBG 'start-script' stdout output: 2023-07-10 12:25:58 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA 2023-07-10 12:25:58,857 DEBG 'start-script' stdout output: 2023-07-10 12:25:58 VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA8 2023-07-10 12:25:58,858 DEBG 'start-script' stdout output: 2023-07-10 12:25:58 VERIFY KU OK 2023-07-10 12:25:58 Validating certificate extended key usage 2023-07-10 12:25:58 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication 2023-07-10 12:25:58 VERIFY EKU OK 2023-07-10 12:25:58 VERIFY X509NAME OK: CN=ca1701.nordvpn.com 2023-07-10 12:25:58 VERIFY OK: depth=0, CN=ca1701.nordvpn.com 2023-07-10 12:25:58,935 DEBG 'start-script' stdout output: 2023-07-10 12:25:58 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bit RSA, signature: RSA-SHA512 2023-07-10 12:25:58 [ca1701.nordvpn.com] Peer Connection Initiated with [AF_INET]154.47.17.25:1194 2023-07-10 12:25:58,935 DEBG 'start-script' stdout output: 2023-07-10 12:25:58 TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1 2023-07-10 12:25:58 TLS: tls_multi_process: initial untrusted session promoted to trusted 2023-07-10 12:25:59,947 DEBG 'start-script' stdout output: 2023-07-10 12:25:59 SENT CONTROL [ca1701.nordvpn.com]: 'PUSH_REQUEST' (status=1) 2023-07-10 12:26:04,040 DEBG 'start-script' stdout output: 2023-07-10 12:26:04 SENT CONTROL [ca1701.nordvpn.com]: 'PUSH_REQUEST' (status=1) 2023-07-10 12:26:04,116 DEBG 'start-script' stdout output: 2023-07-10 12:26:04 AUTH: Received control message: AUTH_FAILED 2023-07-10 12:26:04,116 DEBG 'start-script' stdout output: 2023-07-10 12:26:04 SIGTERM[soft,auth-failure] received, process exiting
I assume this is on Nords end? but surely it's not just me having this issue then?
I've reset my password as well just in case, something much shorter than the original (but working) 30 char pass. I should note I can access the profiles via the Nord App no problem. -
Something seems to be broken with the latest update to the container... nothing works anymore with an influxDB error. (GUS/UUD).
Logs show:
[error] influxdb crashed! [info] loki PID: 60 [info] Skip hddtemp due to USE_HDDTEMP set to no [error] telegraf crashed! [info] promtail PID: 75 [info] grafana PID: 96
over and over again.
Rolling back todocker pull testdasi/grafana-unraid-stack:s230122
returns to a working state for me. -
On 1/2/2023 at 3:36 AM, Raczo said:
Hi i updated the container in unraid webgui now i get this when trying to access nextcloud in my browser:
This version of Nextcloud is not compatible with > PHP 7.4.
You are currently running 8.0.25.How can i fix this?
sooo... this was fun! I just went through this process and realized that the Nextcloud version does not update with the container...so here I was running a 2 year old version and in the same boat as you!
how to fix:
Stop container, edit and pull an older tag "linuxserver/nextcloud:20.0.4" or something like that.
This should then allow you to start the container and login... now you can manually update and webui update. For some reason I could not update via the webui so I did it manually
Nextcloud docker console
updater.phar
Follow the prompts. It's very very straight forward.
You'll want to leave maintenance mode on after each session.
You will need to run this command after each successful update (18 -> 19 -> 20 etc.)
you do need to do this for every version you're behind.
you can turn off maintenance mode once you're at the latest version!
after all that, you can edit the docker container back to ":latest" and test it out! all should be working now. -
So here's a new one that I cannot explain at all... I was watching Htop via SSH when I noticed all the cores peaking and then a ton of freezing and delays. The webui went down as it normally would (along with the containers) but the SSH terminal would still update every 30s or so. I watched for around 10 mins and then hard reset it, I couldn't make sense of any processes that where causing an issue. It wasn't until the server came back online and I went to check the log file to see it was 38GB in file size!?!?!
It was repeating the text in the logfile I've uploaded over and over and over... perhaps there was other stuff but scrolling though 38gb of text is not something I was willing to do. -
Interesting! Would just stopping the container be enough to test or should I remove the the whole thing?
-
As far as I know I do not. I have Host Access to Custom Networks defined as Disabled but I do have a custom ipv4 network for pihole.
-
So over the course of the weekend the following has been done:
Memtest on memory - 10 hours - 0 errors
Memory speeds have been set to the base limits of the board (2666) (in this case, verified this was true)
C-states have all been disabled (verification)
Having learned the relationship between memory and btrfs, I removed my raid1 btrfs cache pool and formatted it, then set it all back up again
Rebuilt the docker file, and added all my containers back.
I'm slowly losing my goddamn mind... The lockups happen sometimes twice a day now, though this last instance after I finished rebuilding all the docker stuff was just under 48 hours uptime (not going to lie, I was very hopeful).
Although I don't think there's anything new in these diagnostics and logs...they're attached. -
Another crash that happened today. Sys logs and diagnostics attached.
-
syslog and new diagnostics attached. This is post crash.
-
Regrettably I turned off flash mirroring however, I've setup a quick syslog server and I will post up a new set of diagnostics and logs when it crashes again.
-
Update: Uptime lasted 3 days, 23 hours when it went down into a hard lock again. I've attached another diagnostic but I was not able to get any logs this time. Same situation were everything went down with no SSH or any other access.
-
Alright, I've set the memory to 2666 (based on the chart for 3rd Gen Ryzen 4 stick dual channel), and disabled C-states. Here's to hoping! Thanks for the info everyone.
-
Awesome! didn't think to check C-states. I'll have to try some new memory out as these are new sticks that I swapped out to test...they're running default values (no OC). Will test in about 8 hours or so and report back.
-
Good evening!
I'm about at my wits end with my server. Over the last few months I've had an issue where the server will lock up completely and I just cannot figure out why. It's completely random but tonight I managed to pull the syslogs before it went down. I have no idea how to interpret these so I was hoping someone else might be able to shed some light.
When the server locks up, something is being written/read to/from the cache as the light continues to blink as an indication actions are happening on the hardware. Sometimes I cannot SSH into the server, sometimes I can. The times I can SSH in, restarting via CLI does not actually restart. The WEBui will error out with an nginx 500 error, and most (sometimes not all) docker containers stop working.
Syslog attached, diagnostics attached.
What I've done so far:
Rebuilt Docker image
Replaced motherboard
Replaced Ram
Replaced NIC
Added 2 new SSDs (Raid1)
Apologies if I posted this in the wrong area, please move or direct me where to post and I will follow up asap. -
On 6/27/2021 at 6:58 PM, Rockstar said:
This exact parameter was already in that field so I removed it and same thing.
I should note: I've already rebooted the server and the firewall just in case.
Just a note:
I solved my issue - It had nothing to do with the container or unraid at all. Somehow my UDM Pro changed the range of allowed IPs for that subnet and thus wouldn't work. By updating this, everything now works as it originally did. -
On 6/25/2021 at 3:09 AM, spants said:
Try it with Extra Parameters only containing:
--cap-add=NET_ADMIN --restart=unless-stopped
This exact parameter was already in that field so I removed it and same thing.
I should note: I've already rebooted the server and the firewall just in case. -
So today I noticed the webUI will no longer load. it has been working fine for the past...forever however, Ads are no longer being blocked and I can see my UDMpro switching to the secondary DNS (1.1.1.1)
Container logs:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] 01-resolver-resolv: applying... [fix-attrs.d] 01-resolver-resolv: exited 0. [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 20-start.sh: executing... ::: Starting docker specific checks & setup for docker pihole/pihole [i] Installing configs from /etc/.pihole... [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone! Converting DNS1 to PIHOLE_DNS_ Converting DNS2 to PIHOLE_DNS_ Setting DNS servers based on PIHOLE_DNS_ variable ::: Pre existing WEBPASSWORD found DNSMasq binding to custom interface: br0 Added ENV to php: "PHP_ERROR_LOG" => "/var/log/lighttpd/error.log", "ServerIP" => "10.10.5.2", "VIRTUAL_HOST" => "10.10.5.2", Using IPv4 ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early)) https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts ::: Testing pihole-FTL DNS: FTL started! ::: Testing lighttpd config: Syntax OK ::: All config checks passed, cleared for startup ... ::: Enabling Query Logging [i] Enabling logging... ::: Docker start setup complete Current Pi-hole version is v5.3.1. Current AdminLTE version is v5.5. Current FTL version is v5.8.1. [cont-init.d] 20-start.sh: exited 0. [cont-init.d] done. [services.d] starting services Starting crond Starting pihole-FTL (no-daemon) as root Starting lighttpd [services.d] done.
I removed the container, image and everything else to start fresh but so far the issue remains and I am honestly not sure why.
Inside the PHP error log is: 2021-06-23 23:34:18: (server.c.1464) server started (lighttpd/1.4.53)
There's already routing in Unraid setup under br0 for 10.10.5.0/24, this is set within the container template.
Navigating to 10.10.5.2/admin leads to nothing. I'm not really sure what else to look at or pull, let me know and I will do so.
-
5 minutes ago, binhex said:
my guess would be that papermc is looking at the default java version set (which will be v8) and assuming its running using that version (which is not the case), you can confirm this by going to the terminal of the docker container and issuing command 'ps -aux', this should then list all processes and if correctly defined you should see java 16 being used for papermc.
Had a thought this might be the case. Looks to be correct too, Thanks for confirming !-
1
-
-
4 hours ago, dkerlee said:
got this up and running. I saw a few of the errors others had experienced. Here are my steps, with a screenshot.
When I tried to get it running, I was having a few problems: no files were being created. This was because I didn't pay attention to the FAQ binhex wrote for new Minecraft 1.17: requires java 16. https://github.com/binhex/documentation/blob/master/docker/faq/crafty.md
-
Java Path /usr/lib/jvm/java-16-openjdk/bin/java
very important. See binhex FAQ link above, and pinned on this thread. Minecraft 1.17 requires a newer java, so we need to specify that path to the new java
I've added that path to the correct box but after restarting the servers I still get:
[04:21:58] [Server thread/WARN]: [io.papermc.paper.util.PaperJvmChecker] ************************************************************ [04:21:58] [Server thread/WARN]: [io.papermc.paper.util.PaperJvmChecker] * WARNING - YOU ARE RUNNING AN OUTDATED VERSION OF JAVA. [04:21:58] [Server thread/WARN]: [io.papermc.paper.util.PaperJvmChecker] * PAPER WILL STOP BEING COMPATIBLE WITH THIS VERSION OF [04:21:58] [Server thread/WARN]: [io.papermc.paper.util.PaperJvmChecker] * JAVA WHEN MINECRAFT 1.17 IS RELEASED. [04:21:58] [Server thread/WARN]: [io.papermc.paper.util.PaperJvmChecker] * [04:21:58] [Server thread/WARN]: [io.papermc.paper.util.PaperJvmChecker] * Please update the version of Java you use to run Paper [04:21:58] [Server thread/WARN]: [io.papermc.paper.util.PaperJvmChecker] * to at least Java 11. When Paper for Minecraft 1.17 is [04:21:58] [Server thread/WARN]: [io.papermc.paper.util.PaperJvmChecker] * released support for versions of Java before 11 will [04:21:58] [Server thread/WARN]: [io.papermc.paper.util.PaperJvmChecker] * be dropped. [04:21:58] [Server thread/WARN]: [io.papermc.paper.util.PaperJvmChecker] * [04:21:58] [Server thread/WARN]: [io.papermc.paper.util.PaperJvmChecker] * Current Java version: 1.8.0_292 [04:21:58] [Server thread/WARN]: [io.papermc.paper.util.PaperJvmChecker] * [04:21:58] [Server thread/WARN]: [io.papermc.paper.util.PaperJvmChecker] * Check this forum post for more information: [04:21:58] [Server thread/WARN]: [io.papermc.paper.util.PaperJvmChecker] * https://papermc.io/java11 [04:21:58] [Server thread/WARN]: [io.papermc.paper.util.PaperJvmChecker] ************************************************************
It's not a huge deal for me as PaperMC doesn't have 1.17 out yet but I am curious as to why it's not being loaded in as it's showing the current version of Java as version: 1.8.0_292.
-
Java Path /usr/lib/jvm/java-16-openjdk/bin/java
-
6 hours ago, binhex said:
1. do you have any cpu pinning going on?
2. do you limit ram for the container?
3. what filesystem are you running, btrfs or xfs?
4. what is the location for the docker image, cache or array?
5. are you using unassigned devices?
6. how much ram does your host have in total?
7. what is the cpu in your host?.
8. just to confirm, you are logging into the webui as user 'nobody' right?
Decided to pull down the latest and test out. Bungeecord seems to start no problem, but each paper server does not.
1: Yes I do use pinning on Core/HT 9/21, 10/22, 11/23
2: no container limitation for RAM
3: btrfs (Raid 1)
4: Cache only
5: no unassigned devices atm
6: 32GB total
7: Ryzen 9 3900x
8: Logging in as Nobody.
Figure I'd answer this so you had more data.
I assume you might be right with this java thing... bungeecord doesn't use Java at all and yeah, started with no problems with the container not running privileged.
Paperclip 1.16.5 server start error:[09:55:09] ain/ERROR]: No key layers in MapLike[{}]; No key structures in MapLike[{}]; Not a registry ops [09:55:09] ain/INFO]: Environment: authHost='https://authserver.mojang.com', accountsHost='https://api.mojang.com', sessionHost='https://sessionserver.mojang.com', servicesHost='https://api.minecraftservices.com', name='PROD' [09:55:09] ain/FATAL]: Failed to start the minecraft server java.lang.RuntimeException: java.nio.file.FileSystemException: .: Operation not permitted at net.minecraft.server.v1_16_R3.Convertable.<init>(Convertable.java:42) ~[patched_1.16.5.jar:git-Paper-445] at net.minecraft.server.v1_16_R3.Convertable.a(Convertable.java:50) ~[patched_1.16.5.jar:git-Paper-445] at net.minecraft.server.v1_16_R3.Main.main(Main.java:112) ~[patched_1.16.5.jar:git-Paper-445] at org.bukkit.craftbukkit.Main.main(Main.java:276) ~[patched_1.16.5.jar:git-Paper-445] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_282] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_282] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_282] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_282] at io.papermc.paperclip.Paperclip.main(Paperclip.java:58) ~[paperclip.jar:?] Caused by: java.nio.file.FileSystemException: .: Operation not permitted at sun.nio.fs.UnixException.translateToIOException(UnixException.java:91) ~[?:1.8.0_282] at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) ~[?:1.8.0_282] at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) ~[?:1.8.0_282] at sun.nio.fs.UnixPath.toRealPath(UnixPath.java:837) ~[?:1.8.0_282] at net.minecraft.server.v1_16_R3.Convertable.<init>(Convertable.java:40) ~[patched_1.16.5.jar:git-Paper-445] ... 8 more
-
Please note: It's not good practice to run a container in privileged mode due to the nature of security.
-
10 minutes ago, jpotrz said:
I have NOT updated to the 6.9 uNRaid yet though
Hmm, I'm on 6.9 but not 6.9.1 (haven't had good downtime yet). -
Same thing happened to me once I updated the container.
Container logs:
Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2021-03-12 01:05:09.206100 [info] Host is running unRAID 2021-03-12 01:05:09.220444 [info] System information Linux 6742fc3c0e04 5.10.19-Unraid #1 SMP Sat Feb 27 08:00:30 PST 2021 x86_64 GNU/Linux 2021-03-12 01:05:09.240847 [info] OS_ARCH defined as 'x86-64' 2021-03-12 01:05:09.261576 [info] PUID defined as '0' 2021-03-12 01:05:09.346306 [info] PGID defined as '0' 2021-03-12 01:05:09.391288 [info] UMASK defined as '000' 2021-03-12 01:05:09.408985 [info] Permissions already set for volume mappings 2021-03-12 01:05:09.444222 [info] Deleting files in /tmp (non recursive)... 2021-03-12 01:05:09.462838 [info] WEBUI_PASSWORD defined as 'mineos' 2021-03-12 01:05:09.620495 [info] Starting Supervisor... 2021-03-12 01:05:09,864 INFO Included extra file "/etc/supervisor/conf.d/mineos-node.conf" during parsing 2021-03-12 01:05:09,864 INFO Set uid to user 0 succeeded 2021-03-12 01:05:09,867 INFO supervisord started with pid 6 2021-03-12 01:05:10,869 INFO spawned: 'shutdown-script' with pid 70 2021-03-12 01:05:10,871 INFO spawned: 'start-script' with pid 71 2021-03-12 01:05:10,871 INFO reaped unknown pid 7 (exit status 0) 2021-03-12 01:05:10,879 DEBG 'start-script' stdout output: [info] Starting MineOS-node... 2021-03-12 01:05:10,879 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2021-03-12 01:05:10,879 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2021-03-12 01:05:11,017 DEBG 'start-script' stdout output: Starting mineos daemon... 2021-03-12 01:05:11,329 DEBG 'start-script' stdout output: mineos daemon started. PID: 81 2021-03-12 01:05:11,332 DEBG 'start-script' stdout output: [info] MineOS-node started 2021-03-12 01:05:11,332 DEBG 'start-script' stdout output: [info] Running chmod for /config (no exclusions)... 2021-03-12 01:05:12,499 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22743530855728 for <Subprocess at 22743530855056 with name start-script in state RUNNING> (stdout)> 2021-03-12 01:05:12,499 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22743531017360 for <Subprocess at 22743530855056 with name start-script in state RUNNING> (stderr)> 2021-03-12 01:05:12,499 INFO exited: start-script (exit status 0; expected) 2021-03-12 01:05:12,499 DEBG received SIGCHLD indicating a child quit
This is also signed in via nobody/mineos.
From the server logs (inside MineOS)Failed to start the minecraft server java.lang.RuntimeException: java.nio.file.FileSystemException: .: Operation not permittedSeems to indicate a permissions issue.
I can also confirm running the container (as a test) as privileged allows everything to work again.
[Support] binhex - qBittorrentVPN
in Docker Containers
Posted
Excellent this worked! Thank you very much for the quick link. Back up and running again!