serverfault.com

I have installed ats proxy with version 9.2.0 in the Ubuntu-22.04 server, squild.log generating, all are success with 200 status, but not coming with error logs like 500, 502, 400 403. I have with another version 8.1.5 in Ubuntu-20.04, there I am getting all logs, with 500, 502, 400 403. Below is my logging.yml configuration. When we do curl command error logs are storing, when we do from application, logs are not coming. # Squid Log Format. - name: squid format: '%<cqtq> %<ttms> %<chi> %<crc>/%<pssc> %<psql> %<cqhm> %<cquc> %<caun> %<phr>/%<shn> %<psct>' - name: msquid format: '[%<cqtd> %<cqtt> %<chi> %<crc>/%<pssc> %<psql> %<cqhm> %<cquc> %<caun> %<phr>/%<shn> %<psct>' - name: msquid_enhanced format: '[%<cqtd> %<cqtt> %<chi> %<crc>/%<pssc> %<psql> %<cqhm>

very junior admin here 🙋‍♀️. We let people use Chrome and Edge, but users keep adding random extensions, and a couple look suspicious. The boss asked me to “lock this down,” and I’m not sure what the normal approach is. Environment (hopefully this helps): Windows laptops/desktops, centrally managed Mix of Google Chrome and Microsoft Edge What I think we need: Block all extensions by default Allowlist a small set we approve Force-install a few required ones (like our password manager) Logs/alerts if possible when someone tries to add something not allowed

Our Microsoft SQL Server sometimes has performance issues due to an extensive I/O triggered. We may have insufficient (in terms of performance) storage, but I noticed that during this behavior experienced, most writes are performed not to database file, but to shadow copy files in System Volume Information files. These writes are performed by sqlservr.exe directly. I disabled SQL Server VSS Writer service, but nothing changed. Why is SQL Server doing this?

Is it possible to configure apache 2.4 to simply swallow and ignore an invalid request, instead of returning an error? Right now I have a virtual host set up as follows: <Directory /> Options FollowSymLinks AllowOverride None Require all denied </Directory> <VirtualHost :443> ServerName www.example.com ServerRoot /var/www/html/ <Directory /var/www/html/> Require all denied </Directory> <Directory /var/www/html/someplace/> ... I would like to simply swallow queries to www.example.com/not-someplace instead of returning an error. Is that possible? Edit: This implies closing the connection also.

I am using 1Panel to manage Docker containers which utilizes Openresty 1.21.4.3-3-3-focal for the reverse proxy server. I have used the following compose.yml services: nextcloud-aio-mastercontainer: image: ghcr.io/nextcloud-releases/all-in-one:latest # This is the container image used. You can switch to ghcr.io/nextcloud-releases/all-in-one:beta if you want to help testing new releases. See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel init: true # This setting makes sure that signals from main process inside the container are correctly forwarded to children. See https://docs.docker.com/reference/compose-file/services/#init restart: always # This makes sure that the container starts always together with the host OS. See https://docs.docker.com/reference/compose-file/services/#restart container_name: nextcloud-aio-mastercontainer # This line is not allowed to be changed as otherwise AIO will not work correctly volumes:

When using ChallengeResponseAuthentication, it is important to understand how it interacts with the Pluggable Authentication Modules (PAM) system and related configuration files. When ChallengeResponseAuthentication is yes, it is expected that PAM is used, so the UsePAM setting should be yes. When UsePAM is no, ChallengeResponseAuthentication must be no, otherwise authentication may not work as expected. There is confusion about which configuration file determines the login behavior when using ChallengeResponseAuthentication. Some documentation refers to login.conf, but the specifics can vary depending on the operating system or distribution. What file does the login process depend on when using ChallengeResponseAuthentication? This may depend on the PAM configuration for sshd, typically located at: /etc/pam.d/sshd This file controls how authe

We develop and distribute an application that controls industrial robots (non real-time typically). We run it on Kubuntu 22.04 in a Konsole window. It is runs continuously for several months at a time. Since we need to compare several alternative possible movements of the robot, CPU and memory usage is significant. The application intermittently will use available memory, but we typically see OOM-killer messages in logs. Core files are also enabled and written if the software crashes due to bugs. On one project we are seeing sudden disappearances of our software. Even the containing terminal emulator (KDE Konsole) disappears. There are no traces of OOM-killer and while there is a core file written it appears that it is from a bug due to unexpected shutdown rather than the root cause. The chain of software is: Konsole > Bash > roslaunch (Python process manager) > our software. roslaunch logs "Keyboard Interrupt". When our softwar

I am trying to build a lab Kubernetes cluster in a Linux host, using Incus system containers as nodes. I want to do it in an automated way using terraform and ansible. The current status of the work is here with a wordy README: https://github.com/trifo75/kubernetes-playground.git Maybe Incus system containers is not the best option to run Kubernetes, but I would like to see if it can be made. As in the repo, the nodes are provisioned in an automated way. My current problem is that I can not load kernel modules in the nodes, as they share the full working kernel with the host os. I need to load the needed modules on the host and then share it with some sysctl magic. This is my current question: how to do it?

I'm building an ISO using live-build and a preseed file. The preseed works entirely as expected when generating and installing an ISO to a real system or VM. But as soon as I try making an OVA using the working ISO and Packer, the hostname is overwritten to something completely wrong. My Packer config looks like: { "builders": [ { "boot_wait": "10m", "disk_size": "{{user `disk_size`}}", "disk_type_id": 0, "guest_os_type": "linux", "headless": "true", "iso_checksum": "{{user `iso_checksum`}}", "iso_url": "{{user `iso_file`}}", "shutdown_command": "{{user `shutdown_command`}}", "ssh_private_key_file": "{{user `ssh_key`}}", "ssh_username": "{{

I was setting up an active directory domain, following all the steps. I put in a password and saved it when creating the domain. Then the the computer rebooted with the DOMAINNAME\Administrator account and I put in the password and it didn't work. Apparently when you create the domain it gets rid of the original password I put in that worked before. What can I do?