serverfault.com

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: NameVirtualHo

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")

assuming a modern linux host, is there any convenient way to spawn an interactive shell in the exact context systemd would use for a unit/service? alternatively, any way to attach a shell to a running process started by systemd? The goal is to interactively test restrictions and capabilities, starting env, working path, etc.

I need to automatically end processes running for more than 24 hours on a CentOS 7 server. I’m using Monit to detect long-running processes and execute a custom script. To test it, I reduced the threshold to 30 seconds and used a dummy process: sleep 5000 & echo $! Monit configuration: # /etc/monit.d/test_uptime.monitrc check process test_sleep matching "sleep" if uptime > 30 seconds then exec "/usr/local/bin/monit_kill_sleep.sh" if does not exist then alert Monit validates correctly: sudo monit -t Control file syntax OK Monit also logs that the uptime rule is being triggered: 'test_sleep' uptime test failed for sleep -- current uptime is X seconds 'test_sleep' exec: '/usr/local/bin/monit_kill_sleep.sh' My helper script logs when it runs: === 2025-12-11T16:50:57 monit_kill invoked === no sleep proce

I am trying to create a Compute Engine VM with NVIDIA Tesla T4 GPUs. My GPU quota request was approved (GPUS_ALL_REGIONS = 4), but I still cannot create the VM. Every time I try to create the instance, I receive the following error: “A n1-standard-4 VM instance with 4 nvidia-tesla-t4 accelerator(s) is currently unavailable in this zone.” I have tried multiple regions and zones, including: asia-south1 (a/b/c)(Mumbai) asia-south2 (a/b/c)(Delhi) us-central1 (a/b/c/f)(towa) I also tried changing the GPU count (1,4 GPUs), but the error remains the same. It seems like GPU capacity is not available for my project, even though the quota is approved. Project ID: wise-waste-464708 Could someone guide me on how to resolve this issue or how to check which regions/zones currently have available T4 GPU capacity? Thank you.