nraygun

Can someone spot check me on the following? If the influxdb is stored in appdata, my appdata is on an SSD cache drive so I don't want it to get too big. 1. Influxdb data is stored in appdata by default. 2. How can I limit the amount of data stored in the database? I saw a reference to something in this thread, but not much detail. Here's how I think this should be done: a. The default retention policy is called "autogen" and defaults to an infinite retention. # influx Connected to http://localhost:8086 version 1.8.4 InfluxDB shell version: 1.8.4 > SHOW RETENTION POLICIES ON telegraf name duration shardGroupDuration replicaN default ---- -------- ------------------ -------- ------- autogen 0s 168h0m0s 1 true > To change this, issue this command to set it to, say, 4 weeks: ALTER RETENTION POLICY "autogen" ON "telegraf" DURATION 4w DEFAULT Other lengths of time are specified by a "duration literal" and are defined here: https://docs.influxdata.com/influxdb/v1.8/query_language/spec/#durations (minimum retention is 1h)

Need some help with Macinabox and High Sierra. I tried Googling around and couldn't find anything. 1. What do I need to do with OpenCore Configurator in High Sierra? It seems different than the Big Sur example in the video. I also can't see the main drive to mount to copy EFI and Nvars to the main disk. 2. If I have to hit enter when it boots up, how can I pass a graphics card to use something other than VNC? With a graphics card passed through, I can't press enter for it to continue. 3. How do I pass through a DVD drive from the server in High Sierra? 4. Is there any reason to keep the macinabox docker running after the creation of the VM?

Quick question: Does Macinabox Catalina sound only work with an AMD GPU?

I can't seem to install Xcode in my VM because it says there isn't enough drive space. I have about 39GB available on a drive called "Catalina" and 2GB free on a drive called "macOS Base System". Is it trying to install Xcode to the smaller drive?

Generally speaking, agreed, but in this specific case a description of the simple use case versus a more involved one is relevant I believe.

Any further updates on this issue? I'm about to post a related issue. I can't believe this is a problem for my fairly simple setup. Right now I'm using fstab and SMBv1.

I only started having this "stale file handle" problem when I switched to using mounts in /etc/fstab. Prior to that I was just using shortcuts in Thunar. I think this method uses gvfs. I noticed that the shares were faster when I specified them in /etc/fstab and browsing to my /mnt directory in the file system. Other than specifying SMB1 in /etc/fstab, has anyone found a better solution that uses SMB3?

Thanks! Got it! For those newbies like me, stop the container, go to Edit, turn on Advanced View, then add "--hostname server" to the "Extra Parameters" field where "server" is your new hostname. Start up the container and you're good to go.

How can I change the hostname of this docker? I think I need to edit /etc/hostname and maybe /etc/hosts, but there doesn't seem to be an editor included in the docker container (vi and nano are not found). I just want my system name to be something readable when I access the Rosetta site. Also, the string displayed when I run hostname in the console is different than the Domain name in the Rosetta site. Is there a different way to change it?

Thinking about this more - if Nextcloud updating is a manual process, what gets updated when the docker gets updated? I just noticed an update to the container (along with DuckDNS and Letsencrypt) but it's still at the same version(18.03) and not the latest(18.04).

Thanks, I think I see it. Some text was black and hard to read in my browser, but it looks like doing it through the Web UI is OK. Although, the last time didn't go so well, so maybe next time I'll try the manual method. "For upgrading the Nextcloud version, please see this guide here. Alternatively, you can update via the Nextcloud webui."

Do I need to regularly update Nextcloud from within Nextcloud or do the Docker updates keep Nextcloud up to date?

I got it! I restored an old version of Nextcloud from /data/updater-"instanceID"/backups and ran a manual update and it worked!

My instance of Nextcloud is also stuck. I edited the config.php file as you recommended and now it just says "Update in process". Before it said it was on step 6. Has anyone else gotten their Nextcloud back up and running after trying to upgrade to 18.03? Mine is dead in the water right now!

Ugh. After some experimenting, I found the culprit - MyEtherWallet Chrome Extension. Toggling it makes the issue appear/disappear. Removing it. Not even sure why that extension would even mess with web pages. I cleared a bunch of stuff in my system too. Lesson learned - next time start with extensions.

Upgraded from 6.7.2 and it went fast and smooth. However, I get a double header in my user scripts page using Chrome. If I use Incognito mode in Chrome, it works as does Firefox. I cleared my cache of everything except passwords. There's also a "Waiting for..." message at the bottom left of the screen on this page. I suppose I could use Incognito mode, but I'd rather not. Any ideas?

Sorry. Wasn't sure which NGINX was affected. From what I can tell NGINX is in the Nextcloud docker and in the Letsencrypt docker. Can someone answer the question in the context of Letsencrypt? Does it even apply?

In addition, is there a way to confirm if the system is update appropriately for this vulnerability? I just followed a SpaceInvader guide and I don't even know where to start looking to confirm things. It also looks like the Docker was recently updated on my system - maybe it's all patched up already?

I recently received this notice from Nextcloud: https://nextcloud.com/blog/urgent-security-issue-in-nginx-php-fpm/ How can I confirm that my Docker container is updated to contain the updates to mitigate this issue?

I'm trying to get HDMI passthrough audio to work too and no luck so far. Here's my device XML: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x1' multifunction='on'/> </hostdev> and the Nvidia card from lspci: 06:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050] (rev a1) 06:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1) Sound doesn't come through the remote desktop. Windows 10, however, does come through. Using Google remote desktop to access the VMs.

It's wonky, but it gives me what I need. I created a FreeDOS VM and called it scripts. Inside of my borg backup script I start off with a "virsh start scripts" and then end the script with a "virsh destroy scripts". The scripts VM will show running when the borg script is in process and will show stopped when it's not. Close enough.

Does anyone know if there is a way to post the status of a script to unRaid's dashboard? I'd like to see if my backup script is still running right on the dashboard instead of going into the CA User Scripts area.

So then how is this solved? A few sites say this may be due to packaging while other sites say something else. I'm not familiar enough with Python to know what they're talking about. Is the version of borg contained in this package a python script versus a compiled one or something?

Can you please update borg backup to the latest version 1.1.9? Keep up the great work!