serverfault.com

I run a Rocky Linux 10 VM. Today I did a dnf update. After that the system behaves strange. I cannot shutdown -r now or reboot. Entering systemctl daemon-reload gives me: Failed to connect to system scope bus via local transport: Connection refused Looks like the DBus is damaged. I don't know which package is the guilty one, as very many packages are updated. Any ideas?

I found a strange behaviour by NTP synchronization. That NTP server worked fine until now when some clients reported a wrong date/time set to today but in year 2000. After investigation I found the issue in the restriction in /etc/ntp.conf file. I had this restriction policy: restrict default notrap nomodify nopeer To solve this issue I had to remove nopeer from this restriction rule. What I'm trying to understand is why that worked correctly in past, but not now. I know that NTPd is pretty obsolete, but the migration to a new NTP server (chronyd based) is going slow so I have to maintain also the old NTPd server. Did anyone had any similar issues?

I have my own postfix which is sending emails through some external service. This external service is Roundcube but with one address "from" configured (account, not alias). I have already catch-all service which moves all emails coming to my domain to one account, but need the other way - to send as any [email protected]. Is it possible to configure that with postfix on my side or in roundcube from the external service but not creating aliases nor new accounts?

I am a beginner in network and I'm building in my home lab a simulation that I have to deal in the future at my real job. So basically I have two different networks: On Oracle Virtualbox LAN A:172.16.10.1/24 host A - 172.16.10.10 NIC1: LAN Segment FW A pfsense - 172.16.10.1 NIC1: Bridge, NIC2:LAN Segment On VMWare LAN B: 192.168.20.1/24 host B - 192.168.20.101 NIC1: Lan Segment FW B pfsense - 192.168.20.1 - NIC1: NAT, NIC2: LAN Segment So the topology would be something like that: HostA -> fwA (bridge) -> wanA -> IPSEC -> wanB -> fwB (NAT) -> HostB and the inverse way too But in all my attempts, I was no able to connect through this VPN, I configured the IPSec correctly (I guess) on both sides fwA Config

I do have the follwing Service : --- apiVersion: apps/v1 kind: Deployment metadata: labels: app: whoami name: whoami spec: replicas: 1 selector: matchLabels: app: whoami template: metadata: labels: app: whoami spec: containers: - image: traefik/whoami:latest name: whoami ports: - containerPort: 80 --- apiVersion: v1 kind: Service metadata: name: whoami-svc spec: type: ClusterIP selector: app: whoami ports: - port: 80 It can be reached with the following ingress : apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: whoami-ingress annotations: traefik.ingress.kubernetes.io/router.entrypoints: web spec: rules: - http: paths: - path: /whoami pathType: Prefix backend: service: name: whoami-svc port: number:

I have two domain controllers, Windows Server 2012. I need to migrate to Windows Server 2025. Could you provide the exact step by step as I didn't make it before.

I bought a Dell PowerEdge R730 from an Alibaba vendor. The operating system will not boot. I asked the vendor, but they seem to be just a seller. This is the image I'm getting. Details: When the hardware diagnostic runs using the Life Cycle Controller, there's an 8% progress bar that then jumps to 20% and stays there. At 20%, in the section that displays the components being diagnosed, some have a green checkmark, while the two hard drives installed in the server are circled in blue, as if it's stuck analyzing them. I booted the operating system using the Lifecycle Controller. I started the operat

I've got a CA that will eventually expire, which is/was used to issue certificates for some infrastructure based on OpenVPN connections. The VPN details shouldn't matter here, as I'm actually struggling with the certificate handling under the hood. What I have: An old CA, called CA1 Server and client certificates that were generated using CA1 A new CA, called CA2 A period of time during which new clients (with new CA2 certificates) must be able to connect to the server in parallel to existing clients (CA1 certificates) My approach (actually suggested by GPT-5) was to deploy a server certificate chain consisting of a new server certificate signed by CA2, plus a CA1-cross-signed certificate of CA2. The CA bundle involves both CA1 and CA2 certificates. However, I couldn't get old clients to accept this server2 -> CA2-by-CA1 -> CA1 chain. Here are the steps for offline testing:

I set up a mail server on my local network and created two virtual users. They are fully recognized by the system, the path to Maildir is set correctly, but when I try to send a message from one virtual user to another, I get an error saying that this user does not exist. Feb 09 10:53:19 domain postfix/submission/smtpd[5136]: 0E4D41A2083: client=unknown[10.12.16.175], sasl_method=PLAIN, sasl_username=sender@domain \ Feb 09 10:53:19 domain postfix/cleanup[5141]: 0E4D41A2083: message-id=<3261b657-8530-4c9e-8a3e-cc6dd040e20c@domain > Feb 09 10:53:19 domain postfix/qmgr[5130]: 0E4D41A2083: from=<sender@domain >, size=520, nrcpt=1 (queue active) Feb 09 10:53:19 domain postfix/lmtp[5142]: 0E4D41A2083: to=<receiver@domain >, relay=domain [private/dovecot-lmtp], delay=0.08, delays=0.03/0.01/0.02/0.01, dsn=5.1.1, status=bounced (host domain l[private/dovecot-lmtp] said: 550 5.1.1 <receiver@domain > User doesn't exist: receiv

Using NUT upsmon, I am experiencing a five-to-ten second connection failure exactly every twelve hours. As this results in a mail notification each time, I would like to know what could be causing this and how to rectify this. Here is the log: Feb 07 12:51:16 pve1 nut-monitor[5016]: Poll UPS [eaton-usv@localhost] failed - Data stale Feb 07 12:51:16 pve1 nut-monitor[5016]: Communications with UPS eaton-usv@localhost lost Feb 07 12:51:16 pve1 nut-monitor[1467190]: Network UPS Tools upsmon 2.8.1 Feb 07 12:51:26 pve1 nut-monitor[5016]: Communications with UPS eaton-usv@localhost established Feb 07 12:51:26 pve1 nut-monitor[1467424]: Network UPS Tools upsmon 2.8.1 Feb 08 00:51:18 pve1 nut-monitor[5016]: Poll UPS [eaton-usv@localhost] failed - Data stale Feb 08 00:51:18 pve1 nut-monitor[5016]: Communications with UPS eaton-usv@localhost lost Feb 08 00:51:18 pve1 nut-monitor[2433189]: Network UPS Tools upsmon 2.8.1 Feb 08 00:51:23 pve1 nut-monitor[5016]: Commun