serverfault.com

I’m migrating DHCP services from Windows DHCP to Kea DHCP, and I need to deliver DHCP Option 137 (HP-EZUpdate) to HP Thin Clients (for example, HP t420). Windows DHCP sends Option 137 as a plain string like: 737.my-domain.local HP Thin Clients accept this format without issues. When sending the same value from Kea DHCP, HP Thin Clients do receive the option, but they see it in the following format: option auto_update 3:37:33:37:7:6b:69:66:72:2d:72:75:5:6c:6f:63:61:6c:0; This looks like a sequence of DNS-label-encoded bytes (length-prefixed labels), not a raw ASCII string. Because of that, the HP client does not accept or process Option 137, even though Kea sends it. So Kea appears to encode Option 137 as an FQDN-style structure, while Windows DHCP seems to send it as plain text. The problem: Kea cannot redefine Option 137, because it is a standard DHCPv4 opt

I need to have two instances of rsyslogd running on an ubuntu 2404. One being the systems local syslog server which is locked down to enterprise standards and one for a syslog relay for collecting security logs and feeding them into a siem. Systemd now uses control groups to manage processed (the are no longer pid files for rsyslogd). Can I simply clone /lib/systemd/system/rsyslog.service as siem-logging.service and add -f <my conf> to the ExecStart line to have a new, independent, rsyslog instance?

We generally rarely need to shut-down / restart our production Windows Server 2022 Hyper-V host. But... sometimes it might happen (power failure, updates, etc). And when it does, we've observed this sort of problem a number of times: Server 2016 Running Hyper-V Stuck in "Shutting down service: Hyper-V Virtual Machine Management" The host shutdown process hangs, waiting for the Hyper-V service to stop. And, underneath, one VM refused the shutdown command. Last time it was an (otherwise very stable) Linux-based server. The problem is very intermittent, and when it does show up it seems it's not the same VM that's responsible for the hold-up. Figuring out which VM is the offending party is already bad enough if one cannot access the Hyper-V VM list on a particular host... But in the event of power failure time might

I have one Quantum LTO-5 SAS external drive and one IBM LTO-6 SAS internal drive. With ITDT system test, Quantum reports ~70MB/s whereas IBM reports ~140MB/s for the same IBM LTO-5 cartridge (and not only this cartridge, I have also other examples.). The HBA adapters the tapes are connected to are even the same model, one with the internal ports, the other with the external ports. What could be the reason for Quantum's slow speed, what should I check ? I cleaned it recently and it was working at normal speed a month ago or so.

I changed the Immich image version number in my manifest files (synced and deployed via ArgoCD). However, the pod was still showing up as "terminating" and didn't delete until I forced its deletion. Now it's stopped, but no new pods are scheduled and it stays "Progressing". I tried deploying a small test instance (no PVC, etc.): poca@pocas ~ % kubectl -n pro describe deploy test Name: test Namespace: pro CreationTimestamp: Sun, 07 Dec 2025 00:18:51 +0000 Labels: app=test Annotations: <none> Selector: app=test Replicas: 1 desired | 0 updated | 0 total | 0 available | 0 unavailable StrategyType: RollingUpdate MinReadySeconds: 0 RollingUpdateStrategy: 25% max unavailable, 25%

I have a clean installation of ubuntu 24.04, but I am having problems setting up iptables. For the initial configuration, my goal is simply to allow all outgoing traffic and incoming SSH traffic. This is the output of sudo iptables -L with my current configuration: Chain INPUT (policy ACCEPT 0 packets, 0 bytes) num pkts bytes target prot opt in out source destination 1 1154 68036 ACCEPT all -- any any anywhere anywhere ctstate RELATED,ESTABLISHED 2 1 52 ACCEPT tcp -- any any anywhere anywhere tcp dpt:ssh 3 20 1436 DROP all -- any any anywhere anywhere Chain FORWARD (policy DROP 0 packets, 0 bytes) num pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 396 packets, 41595 bytes) num pkts bytes target prot opt in out source

Twice in the past couple of years I’ve encountered an unusual issue whereby after a failover in a Redis Sentinel cluster, HAProxy has seemed to continue to route phantom connections to a node that is no longer the Primary/writeable node. Our clusters use HAProxy in conjunction with a KeepaliveD floating IP/VIP hostname which all traffic is routed via, and HAProxy in turn monitors the back ends and routes all traffic to the node that currently reports back as being the Primary/writeable node. When this has happened as far as GUI, logs and stats info is concerned the failover has been detected successfully and all log entries indicate all traffic is being routed to the new Primary, there is zero evidence of connections being sent to other back ends. We have only been alerted to the problem by other application logs starting to intermittently generate errors indicating that write requests are hitting read-only nodes in the Redis cluster: No connection (requires writable

As the title states - now the details: The link at https://documentation.help/7-Zip/register.htm to register 7-Zip You can find all information about registering at: http://www.7-zip.org/register.html goes to Error 404 QUESTION: Where else may I find the docs for TVNC? TIA~i

I successfully installed Apache24. PHP 8.4.15, and MySQL 9.5.0 on Windows (no WAMP) and this IS my first rodeo. Running phpinfo(); in index.php located in C:\Apache24\htdocs works when "localhost" is entered in the address bar of a browser. I currently have 3 dev sites in remote folders. I believe what I need to do is create Aliases inside httpd.conf to point to the three sites. I've spent a week trolling the Internet with no definitive answer. The few (< dozen) Windows examples gave different solutions which either seemed to do nothing (Apache restarted but opening my remote index.html file still opened in file:///C:/John's%20Stuff/Hobbies/Developing/Web%20Development/GCHS/index.html. One conf modification, upon restart, Apache threw the errors: AH00112: Warning: DocumentRoot [C:/Apache24-64/docs/dummy-host.example.com] does not exist AH00112: Warning: DocumentRoot [C:/Apache24-64/docs/dummy-host2.example.com] does not exist AH00548: NameVirt

Just spent a few hours debugging a systemd service file which failed to start with status=226/NAMESPACE and no other information. Most searches offer unhinged things, like removing PrivateTmp or ProtectHome... and the rationally is mostly people commenting lines from the service file until it works, without any understanding. In my case, it was a one letter type on a huge list of ReadWriteDirectories= lines. Is there any way that one can get an actual error message or any other help (in the case above, something like a simple "ReadWriteDirectories doesn't exist")