Home / user-467585

tilkov's questions

Martin Hope
tilkov
Asked: 2020-02-13 06:29:05 +0800 CST
  • 0

We've got Microsoft SQL Server 2008 R2 running on Windows Server 2008 R2, virtualized on VMWare ESXi 6.7.0.

The server has 2 CPU sockets with 22 cores each. The VM is allocated 8 sockets with 3 cores each and 64 GB RAM (ServerEnterprise).

Inside the VM i see two NUMA nodes, each with 11 CPUs.

Unfortunately, SQL server uses only the CPUS on NUMA Node 0 and NUMA Node 1 is idling.

What am i doing wrong? Am i limited by licensing or misconfiguration?

Resource monitor screenshot

virtualization windows-server-2008 sql-server vmware-esxi numa
Martin Hope
tilkov
Asked: 2020-02-11 05:32:25 +0800 CST
  • 0

I am doing a migration from mbox to mdbox on a new disk. From /mnt/mail/$user to /mnt/mail2/$user

Current mail_location = mbox:~/mail:INBOX=/mnt/mail/%u/mail/Inbox

The new mail_location = mdbox:/mnt/mail2/$user/mdbox

My main userdb is passwd, and i have an override for all the users with another userdb:

userdb {
  driver = passwd
  result_success = continue-ok
}

userdb {
  driver = passwd-file
  args = username_format=%u /etc/dovecot/passwd.override
  skip = notfound
}

First step, overriding mail_location for that user:

$user:::::::userdb_mail_location=/mnt/mail2/%u/mdbox

Starting migration: 

doveadm sync -f -u $user mbox:/mnt/mail/$user/mail:INBOX=/mnt/mail/$user/mail/Inbox

Sync goes well, all the folders and mails are there in the mdbox location on /mnt/mail2/$user/mdbox.

The home directory of that user is then changed from /mnt/mail/$user to /mnt/mail2/$user, permissions are set.

/etc/passwd shows that home dir of the user is /mnt/mail2/$user.

/etc/dovecot/passwd.override has the new mdbox mail_location for that user.

Unfortunately, when new mail arrives, it still goes to the old mbox.

Postfix uses dovecot-lda as delivery agent:

mailbox_command = /usr/lib/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT"

Is it possible dovecot-lda doesn't understand the override? And why it still delivers to the old $HOME for that user, no matter that it was changed?

migration email-server dovecot mbox
Martin Hope
tilkov
Asked: 2018-05-01 02:33:16 +0800 CST
  • 0

I have a web service to be used with or without SSL client certificate. The users will get full access only when their browser is authentificated with the certificate. Otherwise they get a basic functionality.

The nginx settings for that are:

ssl_client_certificate /etc/nginx/client-cert/ca.crt;
ssl_verify_client optional;

The problem is that no browser prompts for the certificate to be selected when connecting to the service.

What is the behavior i should expect when ssl_verify_client is optional? Should i still get the prompt?

If it is, where might be the problem?

If not prompting is the expected behavior, how would i force the browser to send that particular certificate to the service?

Running nginx 1.10.3 on Ubuntu 16.04.4 LTS

nginx config: https://pastebin.com/GwjVc0cZ

nginx