serverfault.com

On my server, I am using the kernel $ uname -a Linux 6.17.0-1003-oracle-64k #3-Ubuntu SMP Fri Oct 10 09:27:08 UTC 2025 aarch64 GNU/Linux and the ovpn module was loaded $ lsmod | grep ovpn ovpn 262144 0 ip6_udp_tunnel 262144 3 ovpn,wireguard,vxlan udp_tunnel 262144 3 ovpn,wireguard,vxlan However, somehow, the openvpn-server service told me that openvpn[1084]: Note: Kernel support for ovpn-dco missing, disabling data channel offload. openvpn[1084]: OpenVPN 2.6.14 aarch64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] openvpn[1084]: library versions: OpenSSL 3.5.3 16 Sep 2025, LZO 2.10 openvpn[1084]: DCO version: N/A The information about kernel module ovpn $ modinfo ovpn filename: /lib/modules/6.17.0-1003-oracle-64k/kernel/drivers/net/ovpn/ovpn.ko.zst l

In our Windows Server 2016/2019 Active Directory Environment, We are getting Directory Service 1988 events. We tried through MS GUI tool but unable to process, received failed to remove lingering object and operation failed. We tried removing manually from domain controller. Follow the this Format repadmin /removelingeringobjects Authserver 04dc247f-cb35-43ac-8856-23f4603076b0 CN=configuration, DC=rootcon, DC=local /advisory_mode Removal of lingering objects was successful on authserver, but still showing. How should lingering objects be removed?

We have previously been signing certificate requests from .csr files using xca; however xca has broken down, reason unknown. Bug filed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120348 In the mean time, have been trying to sign the latest request directly with openssl; the signature went through with a command like this: openssl x509 -req -in csr-server.csr -CA ca.pem -CAcreateserial -out server.crt -days 365 -sha256 This command does work; but the subject alternate name does not appear in the certificate. I can see the subject altername name in the csr file like so: openssl req -text -noout -in csr-server.csr I can't see the subject alternate name in the output: openssl x509 -text -noout -in server.crt /etc/ssl/openssl.cnf is the default on debian distributions.

I had issue with TLS configuration with Traefik Gateway API so I switched do Nginx Ingress, but I had problem in configuration. I have backend in Spring Boot and had cors configuration only for local development on localhost and I have built my backend image with such configuration left. Then I have build my frontend in Angular using this configuration server { listen 80; server_name localhost; location / { root /usr/share/nginx/html; index index.html index.htm; try_files $uri $uri/ /index.html; } location /api/ { proxy_pass http://backend:8080/api/; 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; proxy_connect_timeout 30s; proxy_send_timeout 30s; proxy_read_timeout 30s; } location /auth/ { proxy_pass http://backend:80

I'm trying to install Ubuntu 25.10 Desktop with encrypted /boot. At the end I'll always get redirected to GRUB shell, without any password prompt, and unable to cryptomount root partition, insmod luks2 looking into encrypted partition instead of core.img. Let's explain, what am I doing. After boot into ubuntu live cd... # apt install arch-install-scripts debootstrap # fdisk /dev/nvme0n1 Here I setup 2 partitions, +512M EFI partition and rest of the disk for BTRFS.. Setup EFI partition and root mkfs.fat -F 32 /dev/nvme0n1p1 cryptsetup luksFormat --pbkdf=pbkdf2 /dev/nvme0n1p2 cryptsetup luksOpen /dev/nvme0n1p2 root mkfs.btrfs /dev/mapper/root Setup subvolumes of BTRFS mount /dev/mapper/root /mnt btrfs subvolume create /mnt/@ btrfs subvolume create /mnt/@home btrfs subvolume create /mnt/@swap btrfs subvolume create /mnt/@var_log btrfs subvolume creat

This happened several times already: after registering, the runner starts up fine and processes jobs as expected. Then, after some time later, it starts getting 403 (unauthorized) errors, when trying to connect again... Obtaining a new token -- and reregistering -- gets things going again, until it stops. It seems like the errors begin, if the runner's disconnected for "too long" -- such as when the machine's shut down for a few hours -- but we're not sure... What could be the reason -- and how to deal with it?

I'm managing a small HPC cluster with a Synology NAS at a local university and I'm having some issues on the Synology NAS when setting up quotas for LDAP users. Right now, I want to give users an accesible command that they can use from the head node of the cluster to check their quota. Let's call this command "check_quota". When users run check_quota they should get an output similar to this: test@naspockels01:$ Disk quotas for user [email protected] (uid 1026): Filesystem blocks quota limit grace files quota limit grace /dev/vg1/volume_1 113472 1048576 1048576 40 0 0 This works for most users but for some users the output looks like this (username does not match): test2@naspockels01:$ Disk quotas for user guest (uid 1026): Filesystem blocks quota limit grace files quota limit grace /dev/vg1/volume_1 113472 1048576 1048576

i have a freeipa server, and i login client(ubuntu 22.04) with ipa user ，login success. i add username ALL=(ALL) NOPASSWD: ALL to file/etc/sudoers.d/username ,but when i use sudo command it still display input password. in ubuntu 16.04 i login client with same freeipa user it works, no input password display when i used sudo command. why ? what diffrent ubuntu 16.04 and ubuntu 22.04? in /etc/sudoers.d/ only one file named ipa username ubuntu 22.04 /etc/sudoers Defaults env_reset Defaults mail_badpass Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" Defaults use_pty root ALL=(ALL:ALL) ALL %admin ALL=(ALL) ALL %sudo ALL=(ALL:ALL) ALL @includedir /etc/sudoers.d ubuntu 16.04 /etc/sudoers Defaults env_reset Defaults mail_badpass Defaults secure_path="/usr/local/sbin:/usr/local

I have a serious issue with one of my Oracle Linux 8 servers in a 4-node rack setup. Each node has an identical LVM + RAID1 layout, but one node is now unbootable after i accidentally ran parted and wipefs on its main RAID device. Here’s the background: The system had two RAID1 arrays: /dev/md25 (main array, 3.5T, contains all LVM partitions) /dev/md26 (backup mirror, also 3.5T) Unfortunately, some commands like parted and wipefs were mistakenly executed on /dev/md25. After that, the system failed to boot, and I had to boot into emergency mode using the Oracle Linux 8 ISO. Now I see the following output in emergency mode: # lsblk /dev/md25 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT md25 9:25 0 3.5T 0 raid1 # lsblk /dev/md26 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT md26 9:26 0 3.5T 0 raid1 # pvs WARNING: Couldn't find

I’m testing outbound deliverability from a Postfix server. When I send email through authenticated SMTP, it lands in the recipient inbox (SPF, DKIM, and DMARC all pass). When I send using PHP’s built-in mail() function (which calls /usr/sbin/sendmail), the same message goes to spam. A deliverability report shows a DKIM (or “SKIM”) failure for the PHP message, but a full 10/10 score for the same message sent using SMTP. Email: Report: https://mailtested.com/report/mxg8b62e I’m familiar with proper mail server configuration, and DKIM, SPF, DMARC, and rDNS are all set up and