Everything posted by NLS
-
[SUPPORT] DiamondPrecisionComputing - ALL IMAGES AND FILES
It pulled 2.4.0 fine... but same reaction. Start and immediately exit. Note: - This container worked fine before and I didn't touch it. - I have many more containers that work fine. - This is probably important (oups): I am on 6.10.0-rc3c.
-
[SUPPORT] DiamondPrecisionComputing - ALL IMAGES AND FILES
Error response from daemon: No such container: gluetun I assume you meant: docker start ddns-updater ...which producted this: ddns-updater ...and then back to command prompt. And no, the container doesn't actually start. How can I try an older version maybe?
-
[SUPPORT] DiamondPrecisionComputing - ALL IMAGES AND FILES
I know about NGINX, but I haven't yet found time to deal with that. It CAN happen to fill the logs (I have deleted them manually twice). No the system normally has more RAM free. It is not a RAM issue. docker run gluetun? Exactly like that? Unable to find image 'gluetun:latest' locally docker run ddns-updater Unable to find image 'ddns-updater:latest' locally ...I am sure I do something wrong.
-
[SUPPORT] DiamondPrecisionComputing - ALL IMAGES AND FILES
I *think* there is no mention about ddns-updater container anywhere - but I can assure you I have it in my list of installed containers, I even removed it and re-added it 3 times. quasar-ultima-diagnostics-20220113-1525-anon.zip
-
[SUPPORT] DiamondPrecisionComputing - ALL IMAGES AND FILES
reinstalling with new name did nothing
-
[SUPPORT] DiamondPrecisionComputing - ALL IMAGES AND FILES
Just change the name? No, I will try. I cannot see the logs (through the menu at least), as since the container is off, the log window just pops and closes. Is there another way to find logs for it?
-
[SUPPORT] DiamondPrecisionComputing - ALL IMAGES AND FILES
HELP!? ddns-updater stopped working. When I start the container, it just immediately stops. No errors pop up. I removed (and the image) and reinstalled from user template (that worked fine from months). Same thing. Any ideas? How can I debug this? I need this functionality.
-
[Support] cheesemarathons repo
thanks - is it too much to include it in base container? I mean it will give so much more functionality not sure how I can to it https://www.mono-project.com/download/stable/
-
[Support] cheesemarathons repo
Is KDEinDocker supported here? (and at all?) Can I use it to run a win app through mono?
-
The bigger the directory the (disproportionally) slower the access
I wake up my own old topic... Because I never fixed that problem, neither did someone actually give me an idea of what could be wrong. Help? No I cannot really break the folders to smaller ones (they are part of a specific collection that needs the files in place). This is crazy. I am trying to modify (through some program) around 100000 small files (much less than a mb each) and looks like it will take DAYS! This is insufferable.
-
[Support] binhex - MinecraftServer
I didn't even know that was possible! Any simple guide on how to set it up? I added the two plugins in my server (without any config just to see if papermc will start) and I don't know what to do next.
-
[Support] binhex - Crafty
We are already in 1.18.1. Since 1.18 means old seeds create totally different worlds, do some research before moving up. I am successfully using 1.18.1 on crafty server (and clients), way sooner than I expected. I deleted a huge part of my existing world (with mca selector) to regenerate with the new engine. It was done pretty nicely, WAY better than older versions. Now the system tries to "mix" at the edge, not "cut through". I am using papermc which is better than vanilla. Also, make sure that any plug-ins you use support 1.18(.1). Worldedit already has a beta for it. Really guys it is simple, as long as you know what you are doing.
-
[Support] binhex - Crafty
Yeah, stupid choice. You see: 1) Some people want to blindly do that and is not that hard to revert to previous version if one fails. 2) Do they know they shouldn't introduce "production braking" code within a single version minor build update?
-
[Support] binhex - Crafty
My server upgraded fine to papermc 1.18 since yesterday. I even deleted the unused chunks of my world to regenerate with the new engine with the big caves etc. Worked like a charm. Worldedit and few other plugs for 1.18 are out too. I hate that the new paper API doesn't support autoupdate calls any more though. (wish for a workaround... because the same result can come from two API calls... one to return the latest version and another to download that specific version)
-
[6.10.0RC2] Docker update mechanism worse in many ways...
Not sure what changed but I notice a few things that are quite annoying: - Checking for updates takes forever (sometimes practically forever indeed, as it doesn't stop "checking for updates" and page needs F5 refresh). - Some containers after successful update... need update again, but zero data are pulled the second time. This is not fixed until we force check for updates again (which also takes forever like above etc.). - Pulling the images makes an annoying freeze first until any info is shown on what images are to be pulled. When they start they download ok (or skipped if not updated).
-
Notifications don't go without a page refresh
This actually happens to me for many months, not sure why I never reported it. It happens with older 6.X versions, it happens even today with 6.10.0RC2, it happens on different machines and it happens both with Chrome and Edge (ok, same engine, I know). When there is an UNRAID notification in the dashboard page (or any unraid page), clicking to dismiss it/them, just pops them back. ONLY IF I press F5 to refresh the page they go. If I press F5 to refresh without dismissing them, they keep coming (this is normal), but just dismissing them is not enough, needs a refresh too. Is this normal? (if it is, it is definitely bad behavior)
-
[Support] binhex - Crafty
1.17 works fine with Java 17.
-
Weird behavior when moving files between disks (empty space not reclaimed?)
Very useful. Stopping and starting qbt container seems to have helped.
-
Weird behavior when moving files between disks (empty space not reclaimed?)
I thought of that. Hoping that stopping the container will "fix" this.
-
Weird behavior when moving files between disks (empty space not reclaimed?)
Nobody finds this weird? Nobody has any explanation? I use Krusader for the moves and the moves ARE happening. The torrent eventually errored as the files started to grow to their final sizes (900MB each), so since the empty space was not reclaimed (???????), they grew out of the size of two of my disks. Again: I took files AWAY from those two disks, yet I don't see the space actually growning in those two disks. Right now, with the torrent stopped (errored), I will do some more moves and then I will restart qbittorrent container (in case it keeps any hidden locks?) and then hash-check the torrent to revalidate it and hopefully it will continue. But this is a major issue.
-
Weird behavior when moving files between disks (empty space not reclaimed?)
OK, so I am downloading a HUGE torrent (legal, if you need to know) and since the spread of files is not super (more on this later), I decided to micro-manage some of the file management. The first "problem" (but the way Linux works AFAIK), is the files were reporting their "real" size, even before taking their real files. I mean the huge torrent is split in 900MB sized files, sizing the folder reports the files as 900 x (number of files), but seeing the actual content (before the torrent is finished) shows their proper current size. This leads to mishandling of the spread of files. Yes this is not using the cache (cache couldn't handle the torrent size anyway). As the files "fill up" and start taking their proper space (i.e. start becoming 900MB each for real) the disks get full and seemingly will fill some disks to full (one disk DID report 100%). So the above problem (which I think doesn't have a proper solution), lead me to moving files WHILE torrent is running (torrent is looking at share not disk). Since I know how torrents work (pieces, not files), I take care to move files that I see are complete. AND HERE IS THE MAIN ISSUE (sorry for the long intro): I move the files, but in "MAIN" tab, while the destination disk is filling (and I see the files MOVING not copied - i.e. they DO disappear from source), the source disk is NOT emptying. And yes I refresh the page (F5). Does the dashboard periodically refresh and is not showing live info? Or something else is happening? WHILE I was writing this, space in the source DID show up eventually. Well after I made the move though... So I am still curious of the process and if this is normal. EDIT: No it didn't, I was looking at another disk. Still shows the space like I never moved the files, but the files ARE moved.
-
[Support] binhex - MinecraftServer
Thanks, I already use swag and reverse proxy works on other services.
-
[6.10.0RC2] VM doesn't start because has no space for logs (but does have).
So I try to start a general use Windows VM I have, that was running fine days ago (also in RC2), with error "Unable to write to file /var/log/libvirt/qemu/Windows.log: No space left on device" Not sure where /var/log is, but I have plenty gigabytes empty both in my boot stick and my Cache disk. Clicking "logs" in the VM menu, doesn't list any huge log. I doubt the issue relates to RC2, it just happens I use RC2. VM was working fine a few days ago (in RC2 and before). Any ideas?
-
[Support] binhex - MinecraftServer
- Of course I have forwarded 25565. - Reverse proxies don't only work for 80 and 443, but anyway I didn't use it. - Whitelist where? - Server IP in what server properties? Crafty? I tried that with 127.0.0.1 and 0.0.0.0. No difference. Both work OK in my LAN. Also tried with container in Bridge and Host (as it doesn't conflict in any port). To be honest I don't remember all the things I tried.
-
[Support] binhex - MinecraftServer
I haven't managed to make my Crafty server work outside of my LAN (and VPN). I tried both with reverse proxy (swag) and with service entry in external DNS. I must be missing something.