serverfault.com

I'm trying deploy openstack on cluster of VMs running Debian 12.13 bookworm. My globals.yml file configuration is: # under kolla options title: config_strategy: "COPY_ALWAYS" kolla_base_distro: "debian" kolla_base_distro_version: "bookworm" openstack_release: "antelope" # for High Availability purposes, the internal VIP address # belong to same subnet of Management Network, # but not used by any VM or service in kolla_internal_vip_address: "192.168.100.254" # external VIP address belong to same subnet as Router and Server, but not used kolla_external_vip_address: "192.168.1.100" # under: Neutron - Networking Options title: network_interface: "enp2s0" neutron_external_interface: "enp1s0" # use OVN (Open Virtual Network) for modern Routing/Switching in openstack neutron_plugin_agent: "ovn" The issue, Kolla-Ansible fail to pull Docker imag

QEMU uses GnuTLS for TLS migration, while Intel QAT TLS acceleration is available via OpenSSL engine/provider. Is there any supported way to enable QAT acceleration for migration TLS today, or does this require modifying QEMU to use OpenSSL instead of GnuTLS?

My cron in Debian Bookworm doesn't work some weeks (maybe from the end of march) - I don't know. And I don't know how to fix it. Logs (/var/log/syslog and /var/log/cron) are empty of cron data. So I tried to find for fix it. I found some articles about enable cron. And cron still not works after these fixes. I don't know what to do else.

I am trying to run cowrie honeypot on EC2 AWS Linux instance. Instance is accessible through ssh which is by default on port 22. As instructed in https://github.com/cowrie/cowrie/blob/main/INSTALL.rst, changed ssh port to 22222 (5 2s) by editing /etc/ssh/sshd_config. I was able to connect back to instance by specifying port 22222. And then, to make cowrie listen on port 22 I added the rule: sudo iptables -t nat -A PREROUTING -p tcp --dport 22 -j REDIRECT --to-port 2222 After that, closed the session and attempted to connect back to instance but connection timed out. I am very new to this. How should configure this?

One failure moving our servers from deb12 to 13 was some packages moved to contrib repo. After some time debugging our failed upgrade, turns out cloud-init thinks a missing pacakge is no big deal ¯_(ツ)_/¯ cloud-init.log:2026-04-11 22:28:00,694 - apt.py[DEBUG]: The following packages were not found by APT so APT will not attempt to install them: ['geoipupdate'] tried to update our deployment following their example apt: preserve_sources_list: true sources_list: deb $MIRROR $RELEASE main contrib but that doesn't seem to do absolutely anything. I see that line mentioned in /var/log/cloud-init.log but nothing else happens because of it. Nada changes in /etc/apt/**. And cloud-init continue to ignore th

I have a company device that is managed by both SCCM and an MDM solution. When I try to perform a client push installation using SCCM, the operation fails. It seems that the device is fully controlled by the MDM, and SCCM is unable to install or push the client. Has anyone faced this issue before? Is this expected behavior when MDM is managing the device? And is there any workaround to allow SCCM push in this scenario? MDM:airwatch

I need to send bulk email for a small business application hosted on Ubuntu server. I'm trying to decide between running my own SMTP server (Postfix) or an external email marketing service provider. Problem: Using Postfix locally, many messages either land in spam or do not reach the recipient. I understand this may be related to missing or incorrect SPF, DKIM, reverse DNS configuration, and IP reputation. What I tried: Installed and configured Postfix on Ubuntu Set up basic SMTP authentication Attempted SPF and DKIM configuration Tested sending to Gmail and Outlook accounts Despite this, results are inconsistent. Research: From what I read, many businesses prefer external SMTP or email marketing services companies because they handle infrastructure, IP reputation, and deliverability optimization. Question: In a business environment, is it practical to maintain your own SMTP

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

Environment: Windows Server 2022, single Active Directory domain (e.g. MY.DOMAIN), no Azure AD. Problem: I have a security group called RDP (in MY.DOMAIN/DOMAIN). When I add it to the built-in Remote Desktop Users group, the following error occurs: "You do not have permission to modify the group MY.DOMAIN/Builtin/Remote Desktop Users." What I tried: Adding the group using AD Users and Computers Running PowerShell with Add-ADGroupMember Logging on using user principal name Question: What is the minimum permission required to modify a Builtin group in Active Directory? Is Domain Admins membership required, or can this be delegated? Is there an alternative approach such as Group Policy to grant RDP access through a custom security group without touching Builtin\Remote Desktop Users directly?

We recently switched to Microsoft Office 365 and also use Active Directory on a local Primary Domain controller, that syncs with MS365 via Azure AD Synchronization Service. We are experiencing issues with Calendar events winding up in what seems like different time zones after being sent. Example: A manager sent an invite for 9 am, and the meeting shows 6 am on the recipient calendar. When we check the users accounts and machines they are in fact in the same time zones. If anyone has experience with this issue please respond. It may have nothing to do with the AD sync but I though it was worth mentioning.