What are the rules around retrying failed scry attempts?

The rules for Scry state that.

On a successful save, the target isn’t affected, and you can’t use this spell against it again for 24 hours.

However this seems a bit ambiguous. Can that player not use the spell or the party? Does the source of the scry matter?

For instance, a party who have a scrying eye magical item. A Scrying Eye is an item that allows a person to cast the Scrying spell for up to ten minutes at a spell DC of 15. It can only be used once per day, and then cannot be used again until the next dawn.

The item is based off this crystal ball

The typical crystal ball, a very rare item, is about 6 inches in diameter. While touching it, you can cast the scrying spell (save DC 15) with it.

I have lowered the spell DC from the original to account for my item not requiring attunement.

and 2 magic users both with Scry.

If player A uses the scrying eye and fails, can they then cast scry themselves again as it is in effect the item that cast the spell and not the player? Can player B also attempt to cast scry?

If you’re unconscious and making death saving throws, and an attack from within 5 feet of you hits you, does it cause 2 failed death saves?

In the PHB, it says that three death saving throw failures means you die; taking any damage causes 1 failure, and a critical hit causes 2 failures. But the unconscious condition says that attacks against an unconscious character have advantage and auto-crit if they’re within 5 feet.

That seems really tough — it almost guarantees that you’ll die if hit twice if one is melee, and on top of that if you’re hit once and not stabilized on your next turn you have a 45% chance of getting your third failure from the saving throw.

Am I correctly reading the rules? If you’re unconscious and making death saving throws, and an attack from within 5 feet of you hits you, does it cause 2 failed death saves?

All encoders failed to encode metasploit

I am trying to use this exploit on HTB : https://www.rapid7.com/db/modules/exploit/windows/smb/ms08_067_netapi

pretty simple yet metasploit gives me an error : all encoders failed to encode

I have spent hours trying to find a solution but I found nothing :/

This is screenshot for the error https://ibb.co/sQ5cCFY

Metasploit version is 6.0.2-dev

Any solutions or steps to debug this?

Mysql says it failed to start but is up anyway?

I’me running MySQL 8 under Ubuntu 20.04 WSL2

I’m starting MySQL with sudo service mysql restart

Output is:

* Stopping MySQL database server mysqld      [ok] * Starting MySQL database server mysqld      [fail] 

But when I now run sudo service mysql status, I get:

 * /usr/bin/mysqladmin  Ver 8.0.21-0ubuntu0.20.04.4 for Linux on x86_64 ((Ubuntu)) Copyright (c) 2000, 2020, Oracle and/or its affiliates. All rights reserved.  Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.  Server version          8.0.21-0ubuntu0.20.04.4 Protocol version        10 Connection              Localhost via UNIX socket UNIX socket             /var/run/mysqld/mysqld.sock Uptime:                 45 sec  Threads: 2  Questions: 4  Slow queries: 0  Opens: 430  Flush tables: 3  Open tables: 27  Queries per second avg: 0.088 

Error log is:

2020-09-11T22:15:33.048074Z 11 [System] [MY-013172] [Server] Received SHUTDOWN from user debian-sys-maint. Shutting down mysqld (Version: 8.0.21-0ubuntu0.20.04.4). 2020-09-11T22:15:33.136150Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.21-0ubuntu0.20.04.4)  (Ubuntu). 2020-09-11T22:15:33.231510Z mysqld_safe mysqld from pid file /var/lib/mysql/LAPTOP-77E86FL8.pid ended 2020-09-11T22:15:34.784720Z mysqld_safe Logging to '/var/log/mysql/error.log'. 2020-09-11T22:15:35.002180Z mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 2020-09-11T22:15:35.073728Z 0 [Warning] [MY-010139] [Server] Changed limits: max_open_files: 1024 (requested 8161) 2020-09-11T22:15:35.073742Z 0 [Warning] [MY-010142] [Server] Changed limits: table_open_cache: 431 (requested 4000) 2020-09-11T22:15:35.392127Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.21-0ubuntu0.20.04.4) starting as process 6495 2020-09-11T22:15:35.412902Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2020-09-11T22:15:35.992356Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended. 2020-09-11T22:15:36.261631Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock 2020-09-11T22:15:36.404215Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed. 2020-09-11T22:15:36.404659Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel. 2020-09-11T22:15:36.456568Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.21-0ubuntu0.20.04.4'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu). 

My issue is that sudo service mysql restart returns a non-zero status code.

What may I check or look for?

Thank you!

Is it possible bad proxies made Verified site lists go to the Failed list?

One day i forgot to renew proxies, so it ran and failed for maybe 24 hours. Is it possible it made my Verified list go to Failed list?

I ask this because I am only getting 20 wordpress articles max after many days of waiting (settings is only WordPress articles). This is a very low number, I think i used to get a lot more.

Also, what can be done from here?

SQL server backup fail “A system assertion check has failed”

I just installed SQL Server 2017 EVAL in a Windows Server 2012 R2 VM. Most default options.

Default installation folder. SYSTEM databases in default folder. User databases in the D:\ drive. Created some databases, some users, installed Brent Ozar and Ola Hallengren scripts. Next thing I was configuring the backups on the E:\ and getting an error. So i tried to run manually:


and getting this error:

Location:    mediaWrite.cpp:603 Expression:  (m_pWriteBuffer->GetCurrentSize ()% GetBlockSize ()) == 0 SPID:        56 Process ID:  1104 Mensagem 3013, Nível 16, Estado 1, Linha 1 BACKUP DATABASE está sendo encerrado de forma anormal. Mensagem 3624, Nível 20, Estado 1, Linha 1 Falha em uma verificação de asserção do sistema. Verifique o log de erros do SQL Server para obter detalhes. Em geral, uma falha de asserção é causada por bug do software ou danos nos dados. Para procurar danos no banco de dados, considere a execução de DBCC CHECKDB. Se você concordou em enviar despejos à Microsoft durante a instalação, um minidespejo será enviado. Uma atualização poderá ser disponibilizada pela Microsoft no último Service Pack ou em um Hotfix do Suporte Técnico.  Horário de conclusão: 2020-08-13T21:57:22.6904999-03:00 

Is in Portuguese, and telling me to check the SQL Server logs, which point me to this dump file [1] where it have the same message but in english:

 2020-08-13 19:07:27.81 spid54      Erro: 17066, Gravidade: 16, Estado: 1. 2020-08-13 19:07:27.81 spid54      SQL Server Assertion: File: <mediaWrite.cpp>, line=603 Failed Assertion = '(m_pWriteBuffer->GetCurrentSize ()% GetBlockSize ()) == 0'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted. 2020-08-13 19:07:27.81 spid54      Erro: 3624, Gravidade: 20, Estado: 1. 2020-08-13 19:07:27.81 spid54      A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a Hotfix from Technical Support. 2020-08-13 19:07:27.81 Backup      Erro: 3041, Gravidade: 16, Estado: 1. 2020-08-13 19:07:27.81 Backup      BACKUP failed to complete the command BACKUP DATABASE DABOL12. Check the backup application log for detailed messages. 2020-08-13 19:13:11.98 spid54      **Dump thread - spid = 54, EC = 0x000000D63F84C160 2020-08-13 19:13:11.98 spid54      ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\LOG\SQLDump0035.txt 

If I try to run this same command on the D:\ drive, it runs without any problems.


  1. After getting the errors a few times, I installed CU21, but the error persist.
  2. Both SQL Server and SQL Agent account have full control over E:\ drive. I went nuts and granted full control to everyone for the sake of testing.
  3. I was pretty sure that the databases weren’t corrupt, since I don’t get the same error when backuping to another drive and had just created them), but I run the DBCC CHECK anyway, and it’s everything ok.

Any thoughts?

[1] https://pastebin.com/0BhhMN6p


This VM is hosted on a XenServer, which I’m not a admin nor thus have any access. After finding out that I can successfully perform the backup to drives C: and D:, but could not perform to E:, I decided to check the devices.

Drive E: FreeNAS iSCSI Disk SCSI Disk Device

Searching a bit more a found this reddit post [2] with the same problem as I, shedding some light on the problem.

This is a SQL Server Bug, a Windows bug, a Xensrv bug or a FreeNAS bug?

[2] https://www.reddit.com/r/sysadmin/comments/2ofo4k/help_with_an_iscsi_issue/

VSFTPD Exploit failed, unreachable

Working on a school project and I’m encountering an issue when trying to run the exploit in Metasploit. I’m using the vsftp exploit and when I run the exploit an error pops up:

"Exploit failed [unreachable]: Rex::ConnectionRefused The connectionw as refused by the remote host ( Exploit Completed, but no session was created."

Running all this in a VM of Kali Linux.

Any help would be appreciated.

I failed to open a lock. Now what?

Picking a lock typically requires a DC 15 Dexterity check (Basic rules, p. 49). Likewise for manacles (p. 50), which can alternately be escaped with a DC 20 Dexterity check or broken with a DC 20 Strength check. But what happens if you fail?

The general rules for ability checks state (p. 58):

If the total equals or exceeds the DC, the ability check is a success—the creature overcomes the challenge at hand. Otherwise, it’s a failure, which means the character or monster makes no progress toward the objective or makes progress combined with a setback determined by the DM.

As a DM, how can I handle this in practice? In our last session, the players wanted to get inside a locked building to rescue people trapped inside. Picking the lock seemed like an easy enough task for the rogue, but unluckily he failed the check, and I wasn’t prepared for the consequences. There wasn’t much time pressure and no obvious reason why he couldn’t try again, so I allowed another attempt, but it just didn’t feel right.

I’m sure that similar situations will come up again, so I’d like some advice on how to deal with checks so that they don’t just turn into a tedious exercise of rolling until you succeed. I presume that “take 20” was left out of the game for good reason, but I’m not sure what to do instead. I suspect that this was a good occasion to use “progress with a setback” but that’s a fairly new thing for D&D and I’m not sure how to go about it. I’m unsure when I should use setbacks versus lack of progress, and in the latter case I’m unsure when I should allow players to try again versus requiring a different approach.

For example, suppose that a manacled player tries to pick the lock and fails the DC 15 Dexterity check. Now, the player could try to pick it again, or he could try one of the other escape methods, or he could wait for somebody else to rescue him, or he could simply succeed with some setback like a minor injury. How do I choose how to proceed? Or do I let the players choose?

MySQL innoDB cluster auto rejoin failed

3 node cluster, single primary. heavy read/write was happening on the master node. Restart the Master node. Then node 3 became the master. After the restart, the old master was in recovery state

"recoveryStatusText": "Distributed recovery in progress",                  "role": "HA",                  "status": "RECOVERING"    select * from gr_member_routing_candidate_status; +------------------+-----------+---------------------+----------------------+ | viable_candidate | read_only | transactions_behind | transactions_to_cert | +------------------+-----------+---------------------+----------------------+ | NO               | YES       |                   0 |                 8401 | +------------------+-----------+---------------------+----------------------+ 

this trx_to_cert never decreased even after 15mins,

then I tried to reboot node2

this also went to recovery mode.

Finally restart the node3, that’s all

It is saying no eligible primary in the cluster. Not able to recover it.


2020-06-03T15:24:19.735261Z 2 [Note] Plugin group_replication reported: '[GCS] Configured number of attempts to join: 0' 2020-06-03T15:24:19.735271Z 2 [Note] Plugin group_replication reported: '[GCS] Configured time between attempts to join: 5 seconds' 2020-06-03T15:24:19.735285Z 2 [Note] Plugin group_replication reported: 'Member configuration: member_id: 1; member_uuid: "41add3fb-9abc-11ea-a59d-42010a00040b"; single-primary mode: "true"; group_replication_auto_increment_increment: 7; ' 2020-06-03T15:24:19.748017Z 6 [Note] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_applier' executed'. Previous state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''. 2020-06-03T15:24:19.846752Z 9 [Note] Slave SQL thread for channel 'group_replication_applier' initialized, starting replication in log 'FIRST' at position 0, relay log './dev-mysql-01-relay-bin-group_replication_applier.000002' position: 4 2020-06-03T15:24:19.846765Z 2 [Note] Plugin group_replication reported: 'Group Replication applier module successfully initialized!' 2020-06-03T15:24:19.868161Z 0 [Note] Plugin group_replication reported: 'XCom protocol version: 3' 2020-06-03T15:24:19.868183Z 0 [Note] Plugin group_replication reported: 'XCom initialized and ready to accept incoming connections on port 33061' 2020-06-03T15:24:21.722047Z 2 [Note] Plugin group_replication reported: 'This server is working as secondary member with primary member address dev-mysql-03:3306.' 2020-06-03T15:24:21.722179Z 0 [ERROR] Plugin group_replication reported: 'Group contains 3 members which is greater than auto_increment_increment value of 1. This can lead to an higher rate of transactional aborts.' 2020-06-03T15:24:21.722427Z 24 [Note] Plugin group_replication reported: 'Establishing group recovery connection with a possible donor. Attempt 1/10' 2020-06-03T15:24:21.722550Z 0 [Note] Plugin group_replication reported: 'Group membership changed to dev-mysql-01:3306, dev-mysql-03:3306, dev-mysql-02:3306 on view 15910200188085516:19.' 2020-06-03T15:24:21.803914Z 24 [Note] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_recovery' executed'. Previous state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='dev-mysql-02', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. 2020-06-03T15:24:21.855802Z 24 [Note] Plugin group_replication reported: 'Establishing connection to a group replication recovery donor bd472ec4-9abc-11ea-976d-42010a00040c at dev-mysql-02 port: 3306.' 2020-06-03T15:24:21.856155Z 26 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information. 2020-06-03T15:24:21.862169Z 26 [Note] Slave I/O thread for channel 'group_replication_recovery': connected to master 'mysql_innodb_cluster_1@dev-mysql-02:3306',replication started in log 'FIRST' at position 4 2020-06-03T15:24:21.918855Z 27 [Note] Slave SQL thread for channel 'group_replication_recovery' initialized, starting replication in log 'FIRST' at position 0, relay log './dev-mysql-01-relay-bin-group_replication_recovery.000001' position: 4 2020-06-03T15:24:42.718769Z 0 [Note] InnoDB: Buffer pool(s) load completed at 200603 15:24:42 2020-06-03T15:24:55.206155Z 41 [Note] Got packets out of order 2020-06-03T15:29:29.682585Z 0 [Warning] Plugin group_replication reported: 'Members removed from the group: dev-mysql-02:3306' 2020-06-03T15:29:29.682635Z 0 [Note] Plugin group_replication reported: 'The member with address dev-mysql-02:3306 has unexpectedly disappeared, killing the current group replication recovery connection' 2020-06-03T15:29:29.682635Z 0 [Note] Plugin group_replication reported: 'The member with address dev-mysql-02:3306 has unexpectedly disappeared, killing the current group replication recovery connection' 2020-06-03T15:29:29.682729Z 27 [Note] Error reading relay log event for channel 'group_replication_recovery': slave SQL thread was killed 2020-06-03T15:29:29.682759Z 0 [Note] Plugin group_replication reported: 'Group membership changed to dev-mysql-01:3306, dev-mysql-03:3306 on view 15910200188085516:20.' 2020-06-03T15:29:29.683116Z 27 [Note] Slave SQL thread for channel 'group_replication_recovery' exiting, replication stopped in log 'mysql-bin.000009' at position 846668856 2020-06-03T15:29:29.689073Z 26 [Note] Slave I/O thread killed while reading event for channel 'group_replication_recovery' 2020-06-03T15:29:29.689089Z 26 [Note] Slave I/O thread exiting for channel 'group_replication_recovery', read up to log 'mysql-bin.000009', position 846668856 2020-06-03T15:29:29.700329Z 24 [Note] Plugin group_replication reported: 'Retrying group recovery connection with another donor. Attempt 2/10'