serverfault.com

I am fairly new to Traefik, but have managed to set up multiple containers behind it. I am now running into an issue where if I create a container that has more than one router, Traefik doesn't process it. Is this something that should work, or does 3.6 not support it? According to the documentation, this is how I should set up the labels when I have an internal host only route and an external host + prefix route, where I need to strip out the prefix: labels: - "traefik.enable=true" # Local access, host only - "traefik.http.routers.foundry14lan.rule=Host(`vtt.homelab.lan`)" - "traefik.http.routers.foundry14lan.entrypoints=websecure" - "traefik.http.routers.foundry14lan.tls=true" - "traefik.http.services.foundry14lan.loadbalancer.server.port=30000" # External access, https, with path that needs to be stripped - "traefik.http.routers.foundry14web.rule=Host(<redacted>) && PathPref

We are looking to build a server for IA workloads on a non production environment. We would like to get a 1U server and get an L40s into it. However, size restrictions seem to be a major limitation here, as L40s is a full width, full height card, and Dell R650 for instance can get only cards with up to 3/4 length. Has someone built a 1U configuration with L40s? R650 for instance seems to be able to handle L4/L4s, but not L40. L40 capacity is a must, 1U is a preference, not a hard requirement. If it is not an option, we will go for a 2U option, but I would preferrably go for a 1U solution. Anyone with experience on this willing to share some thoughts? Thank you.

We are benchmarking RadSec (TCP/TLS) connections against a single FreeRADIUS instance and observing a consistent connection ceiling. FreeRADIUS (version 3.2.8) Running in Kubernetes (single pod) ~1000 proxy clients, each establishing 1 TLS connection Proxy-only setup (no heavy backend processing) CPU ~0.1 core, Memory ~250MB Open files limit: 65536 Established TCP connections plateau around ~505: ss -tn state established '( sport = :2083 )' | wc -l → ~505 Additional connection attempts fail with: (TLS) System call (I/O) error (-1) Failed to insert request into the proxy list We tried: Increased thread pool: max_servers = 256 Verified CPU/memory are not bottlenecks Verified file descriptor limits are sufficient Is

I've written my first systemd user service and I'm wondering what the best way is to kill it. When the script starts it up the processes look like this (output from systemctl status): ... CGroup: /user.slice/user-1000.slice/[email protected]/app.slice/myservice.service ├─2203135 /bin/sh /home/.../start-myservice-systemd ├─2203136 /home/.../python3 /home/.../bin/the-server --port 8200 └─2203137 /usr/bin/multilog s1000000 n10 /home/.../logs When stopping the service I want all of the processes to die and I've found that using pkill in the service config file seems to do the job: ExecStop=/usr/bin/pkill -P $MAINPID If I use /bin/kill $MAINPID then the python and the multilog processes stick around after a systemctl stop command. Is there perhaps a preferred way to send a signal to all of the child proce

I have a FortiGate DHCP server and Windows Active Directory DNS Server. Clients are getting IP addresses correctly, but DNS records are not being created or updated automatically in Windows DNS. So: DHCP works fine But no A or PTR records are created in DNS. Is this expected behavior with FortiGate DHCP, or is there a way to enable dynamic DNS updates? Any help would be appreciated.

Hardware/Environment: Server: FOG Project v1.5.10 (Running on Ubuntu 22.04) Target Hardware: 550x HP ProDesk 600 G6 SFF Golden Image: Windows 11 Pro (fresh install) Image Settings: Single Disk - Resizable, Partition Manager: Partclone Zstd The Problem: I am able to capture and deploy the image successfully (no errors during the PXE process), but upon reboot, the target machine immediately enters a Recovery loop with Error Code: 0xc000000f and File: \WINDOWS\system32\winload.efi. Steps taken on Golden Image before capture: Entered Audit Mode (Ctrl+Shift+F3) during OOBE. Disabled WinRE: reagentc /disable Deleted the Recovery Partition via diskpart and extended C: to fill the disk (resulting in: EFI -> MSR -> C:). Disabled Hibernation: powercfg -h off Verified BitLocker/Device Encryptio

I want to use Hyper-V on a Windows Server 2025 hosted via Hyper-V. ExposeVirtualizationExtensions is true in PowerShell for the guest system. Server Manager shows the Hyper-V role installed, but searching for Hyper-V in the Windows search bar produces no results. There is a Hyper-V section in Server Manager that shows that Hyper-V is installed and running (vmms). There is also no Hyper-V shortcut at C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools. and virtmgmt.msc does not exist in the system32 folder. How can I access Hyper-V Manager now?

I have many very expensive legacy devices that require FTP and cannot be upgraded to SFTP or equivalent due to both technical and non-technical reasons. I'm looking for an existing product or a daemon "protocol proxy" that can just be deployed on a small device, docker, or VM and left alone. Preferably on something like an Intel NUC right next to the legacy device, so that the FTP protocol does not use the internal LAN. Tunneling over SSH is also not viable due to the random ports used by active/passive mode data connection. There are 'managed file transfer' tools out there which are like pulling out a nail with a jackhammer... looking for something less 'enterprisey' in that regard. I have created a protocol proxy daemon like this using Java with some Apache libraries. It somewhat works and informs me that such a thing is possible, but I'm looking for something more hardened and tested. Can anyone point me toward

I'm trying to set up Nginx to proxy_pass the location / to an external host. I want the redirect to be masked so it looks like it's served from the old host. So I can't use return 301 <new_host> And I only want to redirect the / endpoint, not /api This is my default.conf for nginx: server { # catch all request listen 80; server_name _; location /api/ { proxy_pass http://apiserver:8080/api/; proxy_redirect default; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location / { proxy_pass http://<new_host>/frontend/index.html; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

We have a 2 proxy, 4 MYSQL server setup, all in one percona cluster. Our data guys do not want their oozie database on Percona. We left it as is for years. The proxy is a floating ip address (xx.xx.xx.60) which passes through to two proxy nodes, xx.xx.xx.61 and xx.xx.xx.62. One in one datacentre and one in the other. 2 database hosts in one datacentre (dc1-db1, dc1-db2) and 2 in the other (dc2-db1, dc2-db2). Last year I moved it over from the single server it currently sits on, and kept an eye on the tables. After I saw records being written real time I left it in place. A day later I got a message stating data was missing. It transpires that some transaction data was not being written but it appears that the transaction may have been started. I moved the DB back to a single host. I reviewed the percona setup and the proxy. The parameters seem to fall into line with what examples I could see out there. Client and server timeouts are 60 minutes and the