How does the DNS system work? (A custom registration, causing a reliable redirection?)

Hello,

my domain is using hosts 1's name servers, i can not change my domain name servers now, but i can change this provider. 1 DNS A records to designate a new IP hosting provider. I wonder if I can use this record IP address change to reliably redirect my visitors to a new hosting provider?

When I set here a different hosting provider IP address 2 – the IP address that is shown in the hosting account as a shared IP address for my account of hosting on the provider 2 / or the IP address indicated as IP address on which my other domain is hosted hosting account at the provider 2 … this "redirection" will it work ?

Here, I write it in different terms on how the DNS system can work (I need your opinion, if you do not have the time, general answers to the previous questions are also welcome):

1. The site visitor requests the IP address where domain.com is hosted. It asks the DNS servers defined in its network interface configuration or in its router (if it has DHCP). Then, these servers discover (from the domain registry?) Or from other DNS servers that the IPs belonging to a name server used by the domain (nameserver of the hosting provider 1)
->
2. The visitor now directly connects the IP addresses which can be a dedicated DNS server or a hosting server itself – managed by the hosting provider 1
->
3. The DNS system on the Hosting Provider 1 server checks the DNS zone file of my domain.com and finds that the A records for the domain.com and * .domain.com points to an external IP address (supplier 2).
->
4. Provider 1 tells my web browser that he must use this new IP address to reconnect to this new IP address and even that the domain is not pointing to this IP address (uses name servers and IP addresses of the provider 1) that it serves me a website.
?
SEMrush

magento2.3 – Magento 2.3.1 – Cookie lifetime changed to 29 days – Random Causing and Low Wait Time for Customers – Memcache Session Mode

We changed the life of cookies in Magento 2.3.1 in 29 days and also changed the PHP configs (session.gc_maxlifetime) exactly in the same period.

We use in a Magento session saved in memcache.

Randomly and with some customers, I would say that one in 50 customers is having problems accessing the website after some time of inactivity. (This means that they have already visited the website, added items to the cart and left the window open, and a few days later they come back and try to navigate and then get a timeout.)

Any thoughts that it could be?

vertica – IDERA Rapid SQL – Typing latency Causing deleted characters

I was just wondering if it was just the configuration of my current company with all the security installed on this machine. The MASSIVE latency in typing is such that you have to be very careful about what you are typing because many letters are deleted if you type quickly.

For example, here's what I tried to type:

SELECT * from tblSample Where ID> 500

Here are two attempts one after the other:

Sect * from tbsamle wheeid> 50

Selet * fromtblsapewer i> 500

Fairly normal typing speed may be 60-70WPM, nothing extraordinary. Instead of typing correctly, you must slow down and type one key at a time very, very slowly and even then the letters can be ignored. This makes the product almost unusable.

My team is used to it, but I wonder if it's normal.

sleep watch – previous stop causing 0 on Mac Pro 2008

"The cause of the previous stop 0" seems to be of the type "disconnected power supply", according to the causes of grg shutdown.

I would have assumed that this would only apply to laptops if they lacked battery, or to a desktop computer if there had been a power outage.
Standard indicators of a real power outage – flashing kitchen clocks or other computers rebooted, there is no sign.

However, I noticed that my dormant Mac Pro 3.1 had mysteriously restarted with this cause twice this week. I heard it start at 7:13 this morning and after investigation, I found another similar device, even at 4 am, two days before.

This machine is used as a media player and the only thing that runs is really VLC. The indicator, if I do not hear it start, is that the VLC playlist is empty – so I can safely say that it was only done twice, because I'm relying on the reading list to find out where she is every night. TV. This is the kind of thing you will notice if it's empty.

In the previous questions, the details of pmset are as follows (I am at a distance, preventing sleep)

pmset -g
Active Profiles:
AC Power        -1*
Currently in use:
 hibernatemode        3
 womp                 1
 networkoversleep     0
 sleep                30 (sleep prevented by screensharingd)
 Sleep On Power Button 0
 ttyskeepawake        1
 hibernatefile        /var/vm/sleepimage
 autorestart          0
 disksleep            10
 displaysleep         30

The operating system is 10.11.6
I've reset the SMC, just in case, and run AHT, short and long tests, no errors. I would like to know if anyone has any other ideas on how to proceed to diagnose this.

magento2.3.2 – Custom module causing the "Circular dependency" error after upgrading to Magento 2.3.2

I have a custom module with a plugin for Magento Framework Encryption Encryptor this seems to cause problems after upgrading to Magento 2.3.2 (as of version 2.3.1). When I disable the module, everything works fine. When I enable it, I get "No Namespace Command" for any namespace I'm trying to use. When I run bin / magento list I receive a more detailed error message:

In ServiceManager.php, line 1130:

An abstract factory could not create an instance of magentosetupconsolecommandbackupcommand (aka: Magento  Setup  Console  Command  BackupCommand).


In ServiceManager.php, line 941:

An exception was thrown when creating "Magento  Setup  Console  Command  BackupCommand"; no instance returned


In line 865 of Di.php:

Missing instance / object for maintenanceMode setting for build Magento  Setup  Console  Command  BackupCommand :: __


In ServiceManager.php, line 1130:

An abstract factory can not create an instance of magentoframeworkappmaintenancancemode (aka: Magento  Framework  App  MaintenanceMode).


In ServiceManager.php, line 941:

An exception was thrown when creating "Magento  Framework  App  MaintenanceMode"; no instance returned


In line 55 of Developer.php:

Circular dependency: Magento  Framework  Logger  Monolog depends on Magento  Framework  Cache  InvalidateLogger and vice versa.

I'm pretty sure it's the plugin encryptor causing this, because when I delete this plugin from di.xml the error disappears.

I've also tried to comment on all the methods of the plugin, so it's just an empty class, but the error persists. This seems to be the only fact that a plugin registered for this class is causing the error.

Any ideas why this could be? I'm not sure why activating a plug-in would seem to cause an error elsewhere, especially when this plug-in does not even contain any methods.

MySQL blocking at the OPTIMIZE TABLE on the InnoDB table, causing the disappearance of the table

I have run OPTIMIZE TABLE on some InnoDB tables on a machine running Percona XtraDB 5.5.39-36.0.
On a table, mysqld is overwritten and restarted automatically. When I checked the error log, there were errors regarding the table on which I had tried to run OPTIMIZE TABLE for the last time.

Innodb_file_per_table is set to true.

Excerpt from error.log. See the full error below:

InnoDB: Assertion failed in 140135523792640 thread of dict0dict.c file, line 2697
InnoDB: Assertion Failed: UT_LIST_GET_LEN (table-> list_referenced) == rbt_size (table-> class_referenced)
...
InnoDB: Error: table basename / # sql-70b6_680e082 & # 39;
InnoDB: In the InnoDB data dictionary, the tablespace ID is 63476110,
InnoDB: but the tablespace with this id is named ./dbname/tablename.ibd.

In the database directory, I found the following files:

-rw-rw ---- mysql / mysql 8804 2018-03-21 17:44 # sql2-70b6-680e082.frm
-rw-rw ---- mysql / mysql 16777216 2019-07-16 16:29 # sql2-70b6-680e082.ibd
-rw-rw ---- mysql / mysql 8804 2019-07-16 16:16 # sql-70b6_680e082.frm
-rw-rw ---- mysql / mysql 16777216 2019-07-16 16:29 tablename.ibd

The two # sql * .frm files were identical.
The data appears to be in @ sql2 * .ibd.
The tablename.ibd seems to contain mainly NULs.

Is it possible to rename the files and have them recognized again by MySQL? Or is there a way to retrieve data from the # sql2 * .ibd file in a new instance of the table?

error.log below:

190716 16:16:28 InnoDB: Assertion failed in thread 140135523792640 in dict0dict.c file, line 2697
InnoDB: Assertion Failed: UT_LIST_GET_LEN (table-> list_referenced) == rbt_size (table-> class_referenced)
InnoDB: We are intentionally generating a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you experience repeated assertion failures or crashes, even
InnoDB: immediately after starting mysqld, there may be
InnoDB: corruption in the InnoDB table space. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: to force recovery.
14:16:28 UTC - mysqld received signal 6;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries to which it was linked is corrupt, poorly constructed,
or wrongly configured. This error can also be caused by hardware malfunction.
We will do our best to collect information that will hopefully help
diagnose the problem, but since we have already crashed,
Something is really wrong and it can fail.
Help us improve the Percona XtraDB cluster by reporting any
bugs on https://bugs.launchpad.net/percona-xtradb-cluster

key_buffer_size = 16777216
read_buffer_size = 262144
max_used_connections = 131
max_threads = 302
thread_count = 46
number of connections = 46
It is possible that mysqld uses up to
key_buffer_size + (read_buffer_size + sort_buffer_size) * max_threads = 252174 KB bytes of memory
I hope it goes otherwise, decrease some variables of the equation.

Thread Pointer: 0x7cdaf9c0
Trace attempt. You can use the following information to discover
where mysqld is dead. If you do not see any message after that, something has happened
terribly wrong ...
stack_bottom = 7f73d81dae48 thread_stack 0x30000
/ usr / sbin / mysqld (my_print_stacktrace + 0x20)[0x7a3aa0]
/ usr / sbin / mysqld (handle_fatal_signal + 0x36f)[0x692daf]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f88d97d2340]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39)[0x7f88d87efcc9]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f88d87f30d8]
/ usr / sbin / mysqld[0x85b963]
/ usr / sbin / mysqld[0x86664e]
/ usr / sbin / mysqld[0x86a3f8]
/ usr / sbin / mysqld[0x7e4773]
/ usr / sbin / mysqld[0x7bef5d]
/ usr / sbin / mysqld (_Z18mysql_rename_tableP10handlertonPKcS2_S2_S2_S2_j + 0x117)[0x5f67c7]
/ usr / sbin / mysqld (_Z17mysql_alter_tableP3THDPcS1_P24st_ha_create_informationP10TABLE_LISTP10Alter_infojP8st_orderb + 0x2996)[0x5fb3e6]
/ usr / sbin / mysqld (_Z20mysql_recreate_tableP3THDP10TABLE_LIST + 0x1a1)[0x5fc131]
/ usr / sbin / mysqld[0x63a6c0]
/ usr / sbin / mysqld (_ZN24Optimize_table_statement7executeEP3THD + 0xcc)[0x63b32c]
/ usr / sbin / mysqld (_Z21mysql_execute_commandP3THD + 0x37e7)[0x599237]
/ usr / sbin / mysqld (_Z11mysql_parseP3THDPcjP12Parser_state + 0x2ab)[0x59d6eb]
/ usr / sbin / mysqld[0x59df14]
/ usr / sbin / mysqld (_Z16dispatch_command19enum_server_commandP3THDPcj + 0x2125)[0x5a0605]
/ usr / sbin / mysqld (_Z10do_commandP3THD + 0x148)[0x5a0f58]
/ usr / sbin / mysqld (_Z24do_handle_one_connectionP3THD + 0x296)[0x62fd96]
/ usr / sbin / mysqld (handle_one_connection + 0x42)[0x62fe32]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f88d97ca182]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f88d88b347d]

Try to get variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f707c944177): Is an invalid pointer
Connection ID (thread ID): 109109378
Status: NOT_KILLED

You can download the Percona XtraDB Cluster Operations Manual by visiting
http://www.percona.com/software/percona-xtradb-cluster/. You can find information
in the manual that will help you identify the cause of the crash.
190716 16:16:32 mysqld_safe Number of processes currently in progress: 0
190716 16:16:32 mysqld_safe mysqld restarted
190716 16:16:32 mysqld_safe Jump of wsrep-recover for 4544482d-7860-11e4-b362-7738976f33e0: 439360963 pair
190716 16:16:32 mysqld_safe Assignment of 4544482d-7860-11e4-b362-7738976f33e0: 439360963 to wsrep_start_position
190716 16:16:32 [Warning] The use of the unique key_buffer option prefix instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
190716 16:16:32 [Note] WSREP: wsrep_start_position var Submitted: 4544482d-7860-11e4-b362-7738976f33e0: 439360963 & # 39;
190716 16:16:32 [Warning] The use of the unique prefix, myisam-recover instead of myisam-recover-options, is deprecated and will be removed in a future release. Please use the full name instead.
190716 16:16:32 [Note] The plugin & # 39; FEDERATED & # 39; is disabled.
190716 16:16:32 InnoDB: The InnoDB memory heap is off
190716 16:16:32 InnoDB: Mutex and rw_locks use GCC atomic coding
190716 16:16:32 InnoDB: Compressed tables use zlib 1.2.8
190716 16:16:32 InnoDB: Using the Native Linux AIO
190716 16:16:32 InnoDB: Initializing the buffer pool, size = 80.0G
190716 16:16:37 InnoDB: Initialization Complete Buffer Pool
190716 16:16:37 InnoDB: The most supported file format is Barracuda.
InnoDB: The newspaper's analysis has progressed after the checkpoint lsn 34034818642982
190716 16:16:37 InnoDB: The database was not closed normally!
InnoDB: Launch of disaster recovery.
InnoDB: Reading tablespaces information from .ibd files ...
InnoDB: Possible restoration of semi-written data pages from double writing
InnoDB: buffer ...
InnoDB: Perform a recovery: scanned up to the log sequence number 34034823885824
InnoDB: Perform a recovery: scanned up to the log sequence number 34034829128704
InnoDB: Perform a recovery: scanned up to the log sequence number 34034834371584
InnoDB: Perform a recovery: scanned up to the log sequence number 34034839614464
InnoDB: Perform a recovery: scanned up to the log sequence number 34034844857344
InnoDB: Perform a recovery: scanned up to the log sequence number 34034850100224
InnoDB: Perform a recovery: scanned up to the log sequence number 34034855343104
InnoDB: Perform a recovery: scanned up to the log sequence number 34034860585984
InnoDB: Perform a recovery: scanned up to the log sequence number 34034865828864
InnoDB: Perform a recovery: scanned up to the log sequence number 34034871071744
InnoDB: Perform a recovery: scanned up to the log sequence number 34034876314624
InnoDB: Perform a recovery: scanned up to the log sequence number 34034881557504
InnoDB: Perform a recovery: scanned up to the log sequence number 34034886800384
InnoDB: Perform a recovery: analyzed up to the log sequence number 34034892043264
InnoDB: Perform a recovery: scanned up to the newspaper sequence number 34034897286144
InnoDB: Perform a recovery: scanned up to the log sequence number 34034902529024
InnoDB: Perform a recovery: scanned up to the newspaper sequence number 34034907771904
InnoDB: Perform a recovery: scanned up to the log sequence number 34034913014784
InnoDB: Perform a recovery: scanned up to the log sequence number 34034918257664
InnoDB: Perform a recovery: scanned up to the log sequence number 34034923500544
InnoDB: Perform a recovery: scanned up to the log sequence number 34034928743424
InnoDB: Perform a recovery: scanned up to the log sequence number 34034933986304
InnoDB: Perform a recovery: scanned up to the log sequence number 34034939229184
InnoDB: Perform a recovery: scanned up to the log sequence number 34034944472064
InnoDB: Perform a recovery: scanned up to the log sequence number 34034949714944
InnoDB: Perform a recovery: scanned up to the log sequence number 34034954957824
InnoDB: Perform a recovery: scanned up to the log sequence number 34034960200704
InnoDB: Perform a recovery: scanned up to the log sequence number 34034965443584
InnoDB: Perform a recovery: scanned up to the newspaper sequence number 34034970686464
InnoDB: Perform a recovery: scanned up to the newspaper sequence number 34034975929344
InnoDB: Perform a recovery: scanned up to the newspaper sequence number 34034981172224
InnoDB: Perform a recovery: scanned up to the log sequence number 34034986415104
InnoDB: Perform a recovery: scanned up to the log sequence number 34034991657984
InnoDB: Perform a recovery: analyzed up to the log sequence number 34034996900864
InnoDB: Perform a recovery: scanned up to the log sequence number 34035002143744
InnoDB: Perform a recovery: scanned up to the newspaper sequence number 34035007386624
InnoDB: Perform a recovery: scanned up to the log sequence number 34035012629504
InnoDB: Perform a recovery: scanned up to the logs sequence number 34035017872384
InnoDB: Perform a recovery: scanned up to the log sequence number 34035023115264
InnoDB: Perform a recovery: scanned up to the log sequence number 34035028358144
InnoDB: Perform a recovery: scanned up to the log sequence number 34035033601024
InnoDB: Perform a recovery: scanned up to the log sequence number 34035038843904
InnoDB: Perform a recovery: scanned up to the log sequence number 34035044086784
InnoDB: Perform a recovery: scanned up to the log sequence number 34035049329664
InnoDB: Perform a recovery: scanned up to the log sequence number 34035054572544
InnoDB: Perform a recovery: scanned up to the log sequence number 34035059815424
InnoDB: Perform a recovery: scanned up to the log sequence number 34035065058304
InnoDB: Perform a recovery: scanned up to the log sequence number 34035070301184
InnoDB: Perform a recovery: scanned up to the log sequence number 34035075544064
InnoDB: Perform a recovery: scanned up to the log sequence number 34035080786944
InnoDB: Perform a recovery: scanned up to the log sequence number 34035086029824
InnoDB: Perform a recovery: scanned up to the log sequence number 34035091272704
InnoDB: Perform a recovery: scanned up to the logs sequence number 34035096515584
InnoDB: Perform a recovery: scanned up to the log sequence number 34035101758464
InnoDB: Perform a recovery: scanned up to the log sequence number 34035107001344
InnoDB: Perform a recovery: scanned up to the newspaper sequence number 34035112244224
InnoDB: Perform a recovery: scanned up to the log sequence number 34035117487104
InnoDB: Perform a recovery: scanned up to the log sequence number 34035122729984
InnoDB: Perform a recovery: scanned up to the log sequence number 34035127972864
InnoDB: Perform a recovery: scanned up to the log sequence number 34035133215744
InnoDB: Perform a recovery: scanned up to the newspaper sequence number 34035138458624
InnoDB: Perform a recovery: scanned up to the log sequence number 34035143701504
InnoDB: Perform a recovery: scanned up to the newspaper sequence number 34035148944384
InnoDB: Perform a recovery: scanned up to the log sequence number 34035154187264
InnoDB: Perform a recovery: scanned up to the newspaper sequence number 34035159430144
InnoDB: Perform a recovery: scanned up to the logs sequence number 34035164673024
InnoDB: Perform a recovery: scanned up to the log sequence number 34035169915904
InnoDB: Perform a recovery: scanned up to the newspaper sequence number 34035175158784
InnoDB: Perform a recovery: scanned up to the log sequence number 34035180401664
InnoDB: Perform a recovery: scanned up to the log sequence number 34035185644544
InnoDB: Perform a recovery: scanned up to the newspaper sequence number 34035185955609
InnoDB: 1 transaction (s) which must be canceled or cleaned
InnoDB: a total of 15 line transactions to cancel
InnoDB: The Trx Identifier Counter is 553250800
190716 16:16:47 InnoDB: Creating a batch of log records in the database ...
InnoDB: Percentage Progression: 0 1 2 3 4 5 6 7 8 9 10 11 12 14 14 16 16 18 18 20 20 22 23 25 25 27 27 29 29 31 30 33 32 35 35 37 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 57 57 59 60 61 62 63 64 65 66 67 67 69 69 72 72 74 74 76 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 93 94 95 96 97 98 99
InnoDB: Apply the finished batch
InnoDB: In a MySQL replication, slave the last binlog master file
InnoDB: position 16627982, file name mysql-bin.003831
InnoDB: and the relay log file
InnoDB: position 692444, filename /var/lib/mysql/binlog/mysqld-relay-bin.000069
InnoDB: Last binlog file MySQL position 0 0, filename /var/lib/mysql/binlog/mysql-bin.032770
190716 16:17:05 InnoDB: Error: table basename / # sql-70b6_680e082 & # 39;
InnoDB: In the InnoDB data dictionary, the tablespace ID is 63476110,
InnoDB: but the tablespace with this id is named ./dbname/tablename.ibd.
InnoDB: Have you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
InnoDB: to know how to solve the problem.
InnoDB: We have now removed the InnoDB internal data dictionary entry
InnoDB: from the table "tmp". "# Sql70b6_680e082_0".
InnoDB: We have now removed the InnoDB internal data dictionary entry
InnoDB: from the table "tmp". "# Sql70b6_6821c28_a8".
InnoDB: Background Launch of Canceling Unvalidated Transactions
190716 16:17:05 InnoDB: cancellation of the transaction with the ID 553250680, 15 lines to cancel
190716 16:17:05 InnoDB: Waiting for the start of background threads

InnoDB: cancellation of trx id 553250680 completed
190716 16:17:05 InnoDB: Restoring unprepared transactions is complete
190716 16:17:06 Percona XtraDB (http://www.percona.com) 5.5.39-36.0 started; log sequence number 34035185955609
190716 16:17:06 [Note] Recovery after a crash using / var / lib / mysql / binlog / mysql-bin
190716 16:17:06 [Note] Start of disaster recovery ...
190716 16:17:06 [Note] Recovery after accident completed.
190716 16:17:06 InnoDB: Error: the table "tmp". "# Sql70b6_6821c28_a8" does not exist in the InnoDB internal file
InnoDB: Data dictionary although MySQL tries to delete it.
InnoDB: Did you copy the .frm file from the table to the directory
InnoDB: MySQL database directory of another database?
InnoDB: You can search for additional help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
190716 16:17:06 InnoDB: Error: the table "tmp". "# Sql70b6_680e082_0" does not exist in the InnoDB internal file
InnoDB: Data dictionary although MySQL tries to delete it.
InnoDB: Did you copy the .frm file from the table to the directory
InnoDB: MySQL database directory of another database?
InnoDB: You can search for additional help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
190716 16:17:06 [Note] Event planner: events loaded 0
190716 16:17:06 [Note] WSREP: Initial position: 4544482d-7860-11e4-b362-7738976f33e0: 439360963
190716 16:17:06 [Note] WSREP: wsrep_load (): loading the provider library & # 39; none & # 39;
190716 16:17:06 [Note] / usr / sbin / mysqld: ready for connections.
Version: socket 5.5.39-36.0-55-log: /var/run/mysqld/mysqld.sock' port: 3306 Percona XtraDB cluster (GPL), rel36 version, revision 816, WSREP version 25.11, wsrep_25 .11.r4023

linux – How to detect which part of a PHP script is causing slowness?

I have a folder script.php that works every night, and what happens is this:

CPU

Use the hard drive

Using RAM

As you may have noticed, every morning at the same time the CPU usage reaches 100%, the RAM also increases and the disk space decreases considerably.

How can I debug to determine which code area generates this? I use multiple processes (script.php generates about 50 child processes), and each process sends thousands of queries to CouchDB and sometimes to Apache Lucene, I'm sure the latter is the cause, but how can I to debug?

3. ew

BlackHatKings: Proxy Lists
Posted by: ThomasLound
Post time: June 30, 2019 at 23:08.

sharepoint online – The "XsltListViewWebPart" Web Part seems to be causing a problem. Can not find the specified file

I have a SharePoint Online Site Classic team site template. I also have 1 blog site as a subsite below. On the top-level site, I use a content query webpart to post blog items from the blog sub-site.

Now I'm trying to assign users to add comments on messages. To do this, I went to the blog site -> Site Content -> Comments -> List Settings -> Permissions for this list.

On this page, I broke the inheritance and assigned the group of visitors a contributive access.

When I did that Webpart xslt on the top level bombed site. This triggered the following error.

The "XsltListViewWebPart" Web Part appears to be causing a problem. Can not find the specified file.

I do not know why this happens, I implemented this in SharePoint 2013 onprem without any problem. Why does Sp Online act like it is?

A way to alleviate this problem?