serverfault.com

The Windows Server family has the slmgr -rearm option to extend the trial period. Is there something similar for the Exchange Server 2019?

What can cause this error? 7m47s Normal Created pod/awx-operator-controller-manager-58b7c97f4b-w6flh Created container: awx-manager 13m Warning Unhealthy pod/awx-operator-controller-manager-58b7c97f4b-w6flh Readiness probe failed: Get "http://10.244.0.6:6789/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) 29s Normal Pulled pod/awx-operator-controller-manager-58b7c97f4b-w6flh Container image "quay.io/ansible/awx-operator:2.19.1" already present on machine 3m33s Warning BackOff pod/awx-operator-controller-manager-58b7c97f4b-w6flh Back-off restarting failed container awx-manager in pod awx-operator-controller-manager-58b7c97f4b-w6flh_ansible-awx(c26e98c4-6731-47ab-a343-df7110142f2e)

I have a redmine server running under ubuntu 24.04 on a GCE VM with a postfix mail server set up. I was/am having trouble using the "pipe to postfix" method for retrieving email replies sent to redmine, so set up a "minimal" dovecot to allow redmine to retrieve them via imap. It appears to be working correctly, except somewhere along the way an email got stranded in the redmine mailbox -- it was never fetched by redmine and so is not incorporated into the appropriate issue. I am guessing dovecot keeps track of date/time somehow and only serves up "new" messages. Is there some command I can give to dovecot to cause it to consider all mail in the file new? I tried sudo doveadm -v force-resync rm-mailbox (which may or may not be appropriate) but got the message: doveadm(root): Error: Couldn't drop privileges: User is missing UID (see mail_uid setting) which I don't really understand, given

I've activated defaults for my tenant, and from this page you can control which methods that are available. Sorry for the Swedish in the screenshots! When a user in the tenant goes to sign in setup, the options doesn't match. For example, telephone is available, although it's not activated for tenant. Would like to understand this behavior.

I spun up a Linux server on a Digital Ocean droplet, and successfully installed LAMP. The site works well, but not for HTTPS, which responds with this error: NET::ERR_CERT_AUTHORITY_INVALID. Clicking on this error displays the certificate details including the PEM encoded chain, but it appears to be different from the actual PEM certificate file as issued by CloudFlare. The SSL cert and key are from CloudFlare, and I had installed them as follows. mycompany.conf file: <VirtualHost *:80> ServerAdmin webmaster@localhost DocumentRoot /var/www/html ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined </VirtualHost> <VirtualHost *:443> ServerAdmin webmaster@localhost ServerName mycompany.com ServerAlias www.mycompany.com DocumentRoot /var/www/html ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_L

SMB/Medium size company, wanted to check if my partners/customers have been breached, also get a notification is something happens. found https://havewebeenleaked.io/. Are such services reliable ? Any better alternatives ?

I do have a server with dovecot and postfix. Postfix forwards the authentication to dovecot via smtpd_sasl_type = dovecot In dovecot I am using a passwd-file. Unfortunately the auth_mechanisms of my phone and my desktop client don't overlap. I tried an entry like the following in my passwd-file: me@my_mail.com:{SCRAM-SHA-256}4096,FgoufjZuloE+HyKPXD9H1A==,tSxnPOR0YNJDlEVWbq1+Ktvm6MtbKWzbQ2PLbW+tPlo=,r0RulB/9Fe+JjPzUWz0NBrEqJy5/IcAJAd2SGY8v7RI= me@my_mail.com:{CRAM-MD5}37a74a50ce0ad5aba39d4ce28ef4a882b740913447210328f2ea5f3dc611ac1e (Dummy entries for the fictional password Password123) Unfortunately only the first entry in the file works, so either scram-sha-256 or cram-md5. Is there any way I can get both to work at the same time?

I have a zfs pool with some NVME devices. In normal usage of that pool over network, the network is limitting IO and everything stays cool and quiet. But when I do a scrub it goes with max IO of the SSDs running at 10GB/s. The scrub is finished in few minutes, but the CPU fan goes high and the SSDs are getting fastly hot. I am not so much concerned about general server performance during scrub, I just want to slow itdown that CPU and NVMEs stay cool. I don't want to plug in the fan of my Asrock PCIe M.2 Adapter card again, as it would spin useless for all the other time. I've read about tuning options, but they seem to be focussed on guarenteeing responsiveness for other pool access. So I am unsure whether they could help. I have WD SN850X installed. The critical temp for them is according to smartctl 90°. The reported temp at the end was 70, bit the hottest of the three reported temp sensors went up to 88°. So I am unsure which sensor is refered to and

I have a user data script that changes the SSH port on an EC2 machine to 9000 to make way for a podman bastion container on port 22. This worked fine for several months, until today when it didn't. No changes to the script prior to this, and the EC2 AMI is Ubuntu LTS, so I am scratching my head as to what could have changed. I have added set -x to the top of the script and a few echos of command outputs, and I can see systemd is listening, but it doesn't connect to ssh. The sleep and extra restarts were added today to see if it was a timing issue. The ListenStream= is the official way to clear an existing port 22 binding. First the relevant bits of script: # --------------------------------------------------------------------------------------------------------------------- # RECONFIGURE HOST SSH TO PORT 9000 # ------------------------------------------------------------------------------------------------------

i really hate it when a documentation misses a part. Which is probably the case with the Redmine upgrade documentation: https://www.redmine.org/projects/redmine/wiki/RedmineUpgrade I have done multiple Redmine upgrades already, but always into a new, freshly installed VM/OS. This time i thought i can just upgrade "side by side" of the old versions as my OS was already the latest version. So i unpacked the latest Redmine Install-archive into a folder /opt/redmine6.0.6, side by side to my old /opt/redmine/ installation that holds a working Redmine 5.0.13. I've copied over the two conf-files and have done those few "bundle"-cmds, like decribed in the manual and everything wen't smooth. Permissions are correct, no error shown, everything fine. But after a restart the website still showed me the old Redmine version. After scratching my head