email – Mail Server allows users to send from [anything]

Hello dear serverfault commnity,

I have not been a server admin for too long, so please excuse me if I don’t have knowledge of everything.
Every problem so far I was able to solve by asking others or simply googling.

I am currently managing a newly setup Plesk Server, which should act as a mail server (It uses a standard configuration, so Postfix, Dovecot, and Roundcube)

Well, now I have encountered an issue with the mail server, which nobody that I know how to fix, and google also couldn’t help me (maybe I had the wrong search parameters, but I also don’t know how to phrase the question for google).

My Problem is, that any User logged in their Webmail, can just send Mails from other adresses by adding new Identities (that’s what’s it called in Roundcube) where they can just set a new sending address.

Thank you for all of your help in advance

**Thank you

ssis – Configuring 2017 SQL Server SSISDB Server-wide Default Logging Level does not seem to work

Using SSMS, I have changed the SSIS Catalog Logging Level from Basic to Performance to a Custom Logging Level in a 2017 SQL Server Instance and then I run the report: “All Executions”. It doesn’t seem to matter what Logging Level I am at, the amount of data/detail that is included in the SSIS Catalog Report remains the same. I would think the amount of detail would change with each Logging Level.

If the SSIS Catalog Reports do not change when the Logging Level changes, then how do I see the changes to the Logging Levels? Otherwise, if the SSIS Catalog Reports are suppose change, can someone please point me in the correct path to get the SSIS Catalog Reports to change?

14.04 – Can’t connect to Vsftpd Server – Passive reply with unroutable address

I have installed Vsftpd Server listening on port 21 in ubuntu server. I’ve forwarded a port in my router to forward external port 8500 to internal port 21 where my vsftpd server is listening on. However, when I try to connect using ftp client, I’m seeing the following message in filezilla,

“Server sent passive reply with unroutable address. Using server address instead”

I’ve read that this has to do with being behind a router. But I never had any issues with other routers.
Any reason why I am able to access ftp from the outside when using one router but not the other?

Adding Server 2019 Member server to Server 2008 R2 Domain

I’ve upgraded one of our servers from 2008 R2 to 2019. I rejoined the new 2019 server into our domain that is a 2008 R2 Domain Controller.

However, it seems GPOs are not being applied correctly to the 2019 Server.

Test: I logged into one of my other 2008 R2 Servers and the policies are applied correctly. ie desktop is locked down.

Am I missing something? I saw a post about SMBv1 needing to be enabled to join to domain. I’ve already joined it to the domain without enabling SMBv1 client. We don’t want SMBv1 client.

Thank you!

In Memory OLTP causing OOM Issue in SQL Server even though no data in In Memory OLTP Table

We have only 1 memory optimized table in each database and there are total 10 databases as such. This table is completely empty. But still we can see in DBCC MEMORYSTATUS Output that In memory OLTP is consuming 7.68 GB out of 13 GB that has been assigned to SQL Server.


VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
Pages Allocated 8055696 — 7.68 GB

enter image description here

Sometimes CHECKPOINT is also not running because of OOM situation.

Other than restarting SQL Service, is there any other solution to resolve this issue?

SQL Server Version: Microsoft SQL Server 2016 (SP2-CU12) (KB4536648) – 13.0.5698.0 (X64) Feb 15 2020 01:47:30 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2012 R2 Standard 6.3 (Build 9600: ) (Hypervisor)

insert trigger in sql server to linked oracle

i have created a linked server to oracle in sql server and i want to write one trigger on table in sql server to insert the data into oracle table. For example the table a is in sql server and table b is on oracle. If i insert record in table a the values needs to be copied or inserted into table b of Oracle.
both the tables have same structure

table a
id varchar2(10);
name varchar2(10);

table b
id varchar2(10);
name varchar2(10);

protocols – TLS client does not drop connection even when there are no suitable ciphersuites in the server ciphersuite list during handshake

I have two Windows systems, and I want to establish an encrypted TCP/IP communication between them. Specifically TLS 1.2 or TLS 1.3.
I have configured in both systems the list of allowed ciphersuites:

  1. Win+R -> gpedit.msc which opens Local Group Policy Editor.
  2. Local Computer Policty -> Computer Configuration -> Administrative Templates -> Network -> SSL Configuration Settings -> SSL Cipher Suite Order.
  3. Set to Enabled
  4. Under Options -> SSL Cipher Suites, I saved the list of cipher suites that I want for each of both systems.

Now this is the outcome of my tests:

  • Default list: while they are different lists, they have some ciphersuites in common, so the connection is established.
  • Reduced list: I made sure to remove the ciphersuite used in the previous test and some others, but there are still some ciphersuites in common -> connection established, and I can see that a different ciphersuite was used than before.
  • Custom lists: different list for each system and they do not have any ciphersuite in common -> the connection is still established!

Why is the connection not dropped? Isn’t the client supposed to drop connection when it finds out that none of the ciphersuites suggested by the server during the handshake is listed in its own ciphersuites list?

I don’t understand if I am missing any additional configuration, or I am not setting the ciphersuites in the right place. Is there a “fallback” list that the client/server systems check when they don’t find any suitable ciphersuite in the list under Local Group Policy Editor? I just want to completely prevent connections with ciphersuites other than a specific list under my control.

performance – Optimizing cloud server (php and mysql)

I am running a vBuletin forum as a hobby and I was using a shared hosting service until a couple of days ago. Because the amount of visitors grew and the forum seemed to be slower and slower every day, I tought it is time to change to a cloud server with the following specs:

4 CPU vCore
200 GB SSD-Memory
1 GB Swap

After the change I made the experience, that the forum runs even slower now and that my free memory in PLESK is always extremly low. You can see the “free memory” within the last 24 hours below in the screenshot. The peaks with free memory are caused due to a sql restart.

Free Memory

When I check the free memory within the last hours in Plesk, I can see that the memory is running always very low:

Plesk Memory within the last hours

at the same time in the server overview, I can see that there is some more memory free:

Server Memory

So I realized that I need to do 1) something with my PHP and SQL configuration and/or 2) need to upgrade the server itself. Of course I hope that I can optmize with the settings since option 2 is more expensive 🙂

Unfortunately I have no idea how to successfully optimize my server for my forum, but I already read a lot here on stack.

When I run mysqltuner I get the following results:

 ***>>  MySQLTuner 1.7.19 - Major Hayden <>
 >>  Bug reports, feature requests, and downloads at
 >>  Run with '--help' for additional options and output filtering
(--) Skipped version check for MySQLTuner script
(--) Performing tests on
(OK) Currently running supported MySQL version 10.3.23-MariaDB-0+deb10u1
(OK) Operating on 64-bit architecture
-------- Log file Recommendations ------------------------------------------------------------------
(OK) Log file /var/log/mysql/error.log exists
(--) Log file: /var/log/mysql/error.log(1K)
(OK) Log file /var/log/mysql/error.log is readable.
(OK) Log file /var/log/mysql/error.log is not empty
(OK) Log file /var/log/mysql/error.log is smaller than 32 Mb
(!!) /var/log/mysql/error.log contains 8 warning(s).
(!!) /var/log/mysql/error.log contains 6 error(s).
(--) 0 start(s) detected in /var/log/mysql/error.log
(--) 0 shutdown(s) detected in /var/log/mysql/error.log
-------- Storage Engine Statistics -----------------------------------------------------------------
(--) Data in InnoDB tables: 12.6G (Tables: 511)
(--) Data in MyISAM tables: 25.4M (Tables: 15)
(OK) Total fragmented tables: 0
-------- Analysis Performance Metrics --------------------------------------------------------------
(--) innodb_stats_on_metadata: OFF
(OK) No stat updates during querying INFORMATION_SCHEMA.
-------- Security Recommendations ------------------------------------------------------------------
(OK) There are no anonymous accounts for any database users
(OK) All database users have passwords assigned
(--) There are 620 basic passwords in the list.
-------- CVE Security Recommendations --------------------------------------------------------------
-------- Performance Metrics -----------------------------------------------------------------------
(--) Up for: 15h 21m 49s (13M q (241.731 qps), 148K conn, TX: 296G, RX: 28G)
(--) Reads / Writes: 96% / 4%
(--) Binary logging is disabled
(--) Physical Memory     : 12.0G
(--) Max MySQL memory    : 16.1G
(--) Other process memory: 0B
(--) Total buffers: 6.3G global + 66.9M per thread (151 max threads)
(--) P_S Max memory usage: 0B
(--) Galera GCache Max memory usage: 0B
(OK) Maximum reached memory usage: 9.4G (78.48% of installed RAM)
(!!) Maximum possible memory usage: 16.1G (134.57% of installed RAM)
(!!) Overall possible memory usage with other process exceeded memory
(OK) Slow queries: 0% (774/13M)
(OK) Highest usage of available connections: 31% (48/151)
(OK) Aborted connections: 0.00%  (0/148403)
(!!) name resolution is active : a reverse name resolution is made for each new connection and can reduce performance
(OK) Query cache is disabled by default due to mutex contention on multiprocessor machines.
(OK) Sorts requiring temporary tables: 0% (167 temp sorts / 393K sorts)
(!!) Joins performed without indexes: 647
(!!) Temporary tables created on disk: 54% (128K on disk / 233K total)
(OK) Thread cache hit rate: 99% (48 created / 148K connections)
(OK) Table cache hit rate: 99% (1K open / 1K opened)
(!!) table_definition_cache(400) is lower than number of tables(685)
(OK) Open file limit used: 0% (153/16K)
(OK) Table locks acquired immediately: 100% (1M immediate / 1M locks)
-------- Performance schema ------------------------------------------------------------------------
(--) Performance schema is disabled.
(--) Memory used by P_S: 0B
(--) Sys schema isn't installed.
-------- ThreadPool Metrics ------------------------------------------------------------------------
(--) ThreadPool stat is enabled.
(--) Thread Pool Size: 6 thread(s).
(--) Using default value is good enough for your version (10.3.23-MariaDB-0+deb10u1)
-------- MyISAM Metrics ----------------------------------------------------------------------------
(!!) Key buffer used: 19.2% (25M used / 134M cache)
(OK) Key buffer size / total MyISAM indexes: 128.0M/9.0M
(OK) Read Key buffer hit rate: 100.0% (315M cached / 1K reads)
(OK) Write Key buffer hit rate: 100.0% (88 cached / 88 writes)
-------- InnoDB Metrics ----------------------------------------------------------------------------
(--) InnoDB is enabled.
(--) InnoDB Thread Concurrency: 0
(OK) InnoDB File per table is activated
(!!) InnoDB buffer pool / data size: 6.0G/12.6G
(!!) Ratio InnoDB log file size / InnoDB Buffer pool size (8.33333333333333 %): 256.0M * 2/6.0G should be equal to 25%
(!!) InnoDB buffer pool instances: 8
(--) Number of InnoDB Buffer Pool Chunk : 48 for 8 Buffer Pool Instance(s)
(OK) Innodb_buffer_pool_size aligned with Innodb_buffer_pool_chunk_size & Innodb_buffer_pool_instances
(OK) InnoDB Read buffer efficiency: 100.00% (41905422167 hits/ 41906965493 total)
(OK) InnoDB Write log efficiency: 99.06% (51908272 hits/ 52400204 total)
(OK) InnoDB log waits: 0.00% (0 waits / 491932 writes)
-------- AriaDB Metrics ----------------------------------------------------------------------------
(--) AriaDB is enabled.
(OK) Aria pagecache size / total Aria indexes: 128.0M/1B
(OK) Aria pagecache hit rate: 99.9% (132M cached / 125K reads)
-------- TokuDB Metrics ----------------------------------------------------------------------------
(--) TokuDB is disabled.
-------- XtraDB Metrics ----------------------------------------------------------------------------
(--) XtraDB is disabled.
-------- Galera Metrics ----------------------------------------------------------------------------
(--) Galera is disabled.
-------- Replication Metrics -----------------------------------------------------------------------
(--) Galera Synchronous replication: NO
(--) No replication slave(s) for this server.
(--) Binlog format: MIXED
(--) XA support enabled: ON
(--) Semi synchronous replication Master: OFF
(--) Semi synchronous replication Slave: OFF
(--) This is a standalone server
-------- Recommendations ---------------------------------------------------------------------------
General recommendations:
    Control warning line(s) into /var/log/mysql/error.log file
    Control error line(s) into /var/log/mysql/error.log file
    MySQL was started within the last 24 hours - recommendations may be inaccurate
    Reduce your overall MySQL memory footprint for system stability
    Dedicate this server to your database for highest performance.
    Configure your accounts with ip or subnets only, then update your configuration with skip-name-resolve=1
    We will suggest raising the 'join_buffer_size' until JOINs not using indexes are found.
             (specially the conclusions at the bottom of the page).
    When making adjustments, make tmp_table_size/max_heap_table_size equal
    Reduce your SELECT DISTINCT queries which have no LIMIT clause
    Performance schema should be activated for better diagnostics
    Consider installing Sys schema from for MySQL
    Consider installing Sys schema from for MariaDB
    Before changing innodb_log_file_size and/or innodb_log_files_in_group read this:
Variables to adjust:
  *** MySQL's maximum memory usage is dangerously high ***
  *** Add RAM before increasing MySQL buffer variables ***
    join_buffer_size (> 256.0K, or always use indexes with JOINs)
    tmp_table_size (> 16M)
    max_heap_table_size (> 16M)
    table_definition_cache(400) > 685 or -1 (autosizing if supported)
    performance_schema = ON enable PFS
    innodb_buffer_pool_size (>= 12.6G) if possible.
    innodb_log_file_size should be (=768M) if possible, so InnoDB total log files size equals to 25% of buffer pool size.

The content of the my.cnf looks like this (edited by myself, with understanding from reading here on stack:

bind-address = ::ffff:
innodb_lock_wait_timeout = 600
innodb_buffer_pool_size = 6G
innodb_log_file_size = 256M
innodb_flush_log_at_trx_commit = 2
innodb_stats_on_metadata = 0

The content of my php.ini is the following:

    memory_limit = 256M
max_execution_time = 1200
max_input_time = 600
post_max_sice = 64M
upload_max_filesize = 16M
opcache.enable = on

So I am looking desperately for help, tips, hints how I can optimize my server to earn some more performance for my website which is really, really slow 🙁

Have a nice day and greetings!

sql server – log send queue size and redo queue size in AG

Both the log send queue and redo queue can be found in sys.sys.dm_hadr_database_replica_states (docs), and also available using the SQLServer:Database Replica Perfmon counters (docs).


With Perfmon counters, you’ll need to collect counters individually on each replica. Each replica knows about the Send/Redo(recovery) queue affecting that replica itself.

It sounds like you already found the Log Send Queue perfmon counter, which is defined as:

Amount of log records in the log files of the primary database, in kilobytes, that haven’t been sent to the secondary replica. This value is sent to the secondary replica from the primary replica. Queue size doesn’t include FILESTREAM files that are sent to a secondary.

The perfmon counter for the Redo Queue is actually the Recovery Queue counter, which is defined as:

Amount of log records in the log files of the secondary replica that have not been redone.

You can also access the Perfmon counters using T-SQL by querying the sys.dm_os_performance_counters DMV.

FROM sys.dm_os_performance_counters
WHERE object_name = 'SQLServer:Database Replica'
AND counter_name IN ('Log Send Queue','Recovery Queue')
ORDER BY cntr_value DESC;


From T-SQL, you can query the DMVs to get this info. The below query is from my standard toolbox, and includes both the Send & Redo queue sizes & rates (in the first few columns), plus some other information on the replica states & send/redo status. Note that running this on the Primary Replica will report status information for all replicas, running it on the secondary replica will only report local information for that secondary replica.

The advantage of monitoring via T-SQL is that you can have a single/central collection point to check on the status of all replicas at once.

-- ▶ Run this on **PRIMARY**

    --AG info
    AGName                          =, 
    ReplicaServer                   = ar.replica_server_name, 
    DbName                          = adc.database_name, 
    -- Queue Size & rates
    SendQueueSize                   = drs.log_send_queue_size,
    RedoQueueSize                   = drs.redo_queue_size, 
    SendRateKb                      = drs.log_send_rate, 
    RedoRateKb                      = drs.redo_rate, 
    -- State Info
    IsLocal                         = drs.is_local, 
    IsPrimary                       = drs.is_primary_replica, 
    SynchronizationState            = drs.synchronization_state_desc, 
    SynchronizationHealthState      = drs.synchronization_health_desc, 
    -- Last ____ Time
    LastSentTime                    = drs.last_sent_time, 
    LastRedoTime                    = drs.last_redone_time, 
    LastReceivedTime                = drs.last_received_time, 
    LastHardenedTime                = drs.last_hardened_time, 
    LastCommitTime                  = drs.last_commit_time, 
    -- LSN info
    RecoveryLSN                     = drs.recovery_lsn, 
    TruncationLSN                   = drs.truncation_lsn, 
    LastSentLSN                     = drs.last_sent_lsn, 
    LastReceivedLSN                 = drs.last_received_lsn, 
    LastHardenedLSN                 = drs.last_hardened_lsn, 
    LastRedoneLSN                   = drs.last_redone_lsn, 
    EndOfLogLSN                     = drs.end_of_log_lsn, 
    LastCommitLSN                   = drs.last_commit_lsn,
    --Oh yeah, filestream, too
    FileStreamSendRate              = drs.filestream_send_rate
FROM sys.dm_hadr_database_replica_states AS drs
JOIN sys.availability_databases_cluster AS adc 
    ON drs.group_id = adc.group_id AND drs.group_database_id = adc.group_database_id
JOIN sys.availability_groups AS ag
    ON ag.group_id = drs.group_id
JOIN sys.availability_replicas AS ar 
    ON drs.group_id = ar.group_id AND drs.replica_id = ar.replica_id
    --, ar.replica_server_name, adc.database_name;
    drs.log_send_queue_size + drs.redo_queue_size DESC;

sql server – DBCC CheckDB : Operating System Error 27(The drive cannot find the sector requested)

So my regular DBCC check had this lovely message waiting for me in the error logs this morning. I’ve been trying to find out more about this issue and what can be done about it. Manually running DBCC CHECKDB will result in DBCC aborting with Error 6 (connection closed by remote host) and get me this error in the SQL log file. Running DBCC CHECKDB(dbname) WITH PHYSICAL ONLY or DBCC CHECKDB(dbname, NOINDEX) will complete successfully and report no errors. Chkdsk reports no errors on the drive.

How can I determine if this a corruption error in the database file or an actual “on the disk” bad sector? Can this be fixed in place or do I need a new disk and to restore from backups? While I have good backups, if I restore a recent backup, will that also “restore” the missing data/sector?

FWIW the DB is 2.2 TB so I’m rather reluctant to jump into a fix until I really know what’s going on.