serverfault.com

I'm running a rootless podman container where I mount an nfs4 volume. I can write to NFS just fine Inside the container, I can also move a directory that's not in NFS into NFS, and it also works fine But if I do the move to NFS from the host instead of from the container, I can't write to it inside the container! However the ACL & owner for both directories are the same! podman run -it --rm \ -v /tmp/local:/local:U \ -v /mnt/nfs:/nfs \ ubuntu:latest # my subuid is 558752 so this maps to 559752 on the host useradd -u 1001 myuser su myuser # creating folder from container works fine mkdir /nfs/created_from_container touch /nfs/created_from_container/file1 #OK! # moving a folder to nfs from within the container also works fine mkdir /local/moved_by_container touch /local/moved_by_container/file1 #OK! mv /local/moved_by_container/ /nfs/ touch /nfs/moved_by_container/file1 #OK! # but this doesn't work mkdi

I made a release update of my server and unfortunately it has an exim4 instance and now it has been upgrade to v.4.97 It seems this version introduced a tainted data check and for some reason all my email are not delivered anymore. I tried to add this config .ifdef _OPT_MAIN_ALLOW_INSECURE_TAINTED_DATA allow_insecure_tainted_data = yes .endif But it didn't help, maybe this workaround is deprecated. Then my current transport config: local_mysql_delivery: driver = appendfile directory = /var/mail/${domain}/${local_part}/ maildir_format delivery_date_add envelope_to_add return_path_add user = mail group = mail mode = 0660 Doesn't work, but I didn't understand from documentation how I have to change the directory property.

We are trying file recovery for a Linux OS-disk (Ubuntu 22.04) using Azure Backup File Recovery. The VM has two disks: OS Disk Data Disk The Azure Portal indicates that: The VM is protected successfully The selected recovery point includes both the OS disk and the data disk No warnings or skipped disks appear in the Backup Jobs view What happens during File Recovery We downloaded and executed the File Recovery script on multiple test VMs and multiple recovery points (including older ones). In all cases: Azure provides only one single LUN through iSCSI: /dev/disk/by-path/...-lun-0 -> /dev/sdc /dev/disk/by-path/...-lun-0 -> /dev/sdd These two iSCSI paths combine into a single multipath devi

A resource group is a collection of resources that share the same lifecycle, permissions, and policies. How many resources can a resource group contain? I mostly care about Cognitive Services resources. Here are the hierarchy levels in Azure: Management Group ├─ Quota: how many subscriptions are allowed? ↓ Subscription ├─ Quota: how many resource groups are allowed? ↓ Resource Group ├─ Quota: how many Cognitive Services resources can it contain? ↓ Cognitive Services Resource (aka instance) ├─ Example quotas: │ - OpenAI deployments │ - TPS / RPM / Tokens per minute (visible when creating or editing an endpoint in that resource) │ └─ Contains: - models - deployments - endpoints

I'm installing Proxmox via PXE, but due to my circumstances, I have to do it over a trunk on VLAN10. I have configured Dell iDRAC and iPXE to tag with VLAN10 and it works fine. Problem is, it gets handed off to Proxmox and dies because Proxmox DOES NOT tag the traffic. I've tried passing it via kernel params like: kernel ${dir}/linux26 \ initrd=initrd ramdisk_size=16777216 rw quiet splash=silent \ proxmox-start-auto-installer \ vlan={{ proxmox.interfaces.trunk }}.10:{{ proxmox.interfaces.trunk }} \ ip=dhcp:::::{{ proxmox.interfaces.trunk }}.10 but while that flows through, it doesn't take. It doesn't actually create the VLAN interface and it fails. How do you get Proxmox autoinstall to tag traffic with a VLAN?

I am provisioning Windows 2022 EC2 instances using Terraform and a PowerShell User Data script. I want to add functionality where this User Data script will configure a shutdown PowerShell script that will copy some files to a S3 bucket upon shutdown. This needs to be done without using the Windows GUI. This the code I am currently using: # ------------------------------------------------------------------------- # Create a PowerShell script for shutdown # ------------------------------------------------------------------------- $shutdownScriptPath = "C:\Scripts\BackupOnShutdown.ps1" # Ensure the Scripts folder exists New-Item -ItemType Directory -Path "C:\Scripts" -Force # Create the shutdown script @" # Backup Gateway Backups folder to S3 try { aws s3 sync "C:\Users\Administrator\Desktop\Gateway Backups" "s3://${backup_bucket}/gateway-backups/" --exact-timestamps aws s3 cp "C:\Users\Adm

I am using Win 11 Home on a Dell XPS 13 9360. I plug a USB hub into it using USB c connector. This normally provides power, HMDI, wired network and USB A connectors. This has worked just fine for a number of years. It has recently stopped working totally. Looking at the device manager it is the highlighted one in the screenshot. If I check the driver I can see it was updated on the 24th of Nov - around the time it stopped working. I can't seem to rollback this driver 'update'. Any ideas on how I fix this to get my hub working again? screenshot of device manager

I rented a VM from Google Cloud Platform, but it frequently (once a week) goes down, and I’m unable to connect via SSH (even through the GCP console). I’ve tried manually stopping and starting the server and it worked, but I still don’t understand why it keeps going down. Does anyone know what could be causing this issue and how to troubleshoot it?

We're running our own Kubernetes cluster and it works well for a while but at minute :03 each hour, public web services stop responding (504 gateway timeout) and some commands such as kubectl top nodes no longer works (), kubectl get pods works but is very slow to respond. I can make the cluster work again by running k rollout restart daemonset calico-node -n kube-system. Then the cluster runs smoothly again until next hour at :03 and the same issue reappears. calico-node-pods all look normal even after the cluster has started missbehaving (i.e. no error logs, no CrashLoopBackoff etc). I've checked cpu, memory, disk and inodes just before the issue appears and see no abnormalities. Logs for ingress-nginx-controller shows errors that coincide with when the issues appear, like: W1202 15:03:48.643048 7 reflector.go:569] k8s.io/[email protected]/tools/cache/reflector.go:251: failed

(First, please excuse me. Not a professional sysadmin, just someone who has had to set up a VPS recently). I recently set up a new Almalinux 10 box, and I wanted to add port knocking to it to further secure it besides the regular stuff (fail2ban, no root SSH logins, etc.). However, after spending a few hours, I found out that the two port knocking/SPA packages I was looking for (knockd and fwknop) only work with iptables, while Almalinux 10 has removed it entirely and works with nftables now. Is there a simple port knocking solution available for newer Linux distributions such as mine?