database – The media_storage_file_storage table does not exist

Since the upgrade from EE 2.1 to Magento EE 2.3, many exceptions have been reported

The table & # 39; magento.media_storage_file_storage & # 39; does not exist

Nothing seems to be broken, but I'm not sure why Magento thinks it should have this table, and if so, why it does not create the table during the setup: upgrade. What is this table for and why are my logs filling it?

magento2 – base table or view not found: 1146 table & # 39; magent7.catalog_url_rewrite_product_category & # 39; does not exist

I'm migrating from Magento Open Source 1.9 to 2.3.3
The initial migration went well. However, I'm trying to do a delta migration using the Magento Migration Tool.

Running the delta command for the migration tool gives me the error

Base table or view not found: 1146 table
'magent7.catalog_url_rewrite_product_category' does not exist

The table is there, but I think the tool does not add the database prefix before the query is created.
Every help is appreciated.

thanks

SQL Server – Database Mirror – Host can not be reached or does not exist

I tried to mirror the database with GUI and T-SQL, but I had problems in both cases.

Here is some information about infrastructure and SSMS:

INFRASTRUCTURE

  • Main server with SQL Server 2017 Enterprise Edition
  • Mirror server with SQL Server 2017 Enterprise Edition
  • Witness server with SQL Server 2017 Express Edition
  • All servers S.O.: Windows Server 2016 Standard
  • All servers with firewall disabled
  • All servers in a common domain
  • All servers have the same users and permissions
  • Telnet works fine on all servers with port 5022
  • I have created a user to manage the service on all servers GRANT CONNECT ON ENDPOINT :: Mirroring

About SQL Server Management Studio – SSMS:

Microsoft SQL Server Management Studio                      14.0.17289.0
Microsoft Analysis Services Client Tools                    14.0.1016.283
Microsoft Data Access Components (MDAC)                     10.0.14393.0
Microsoft MSXML                                             3.0 6.0 
Microsoft Internet Explorer                                 9.11.14393.0
Microsoft .NET Framework                                    4.0.30319.42000
Operating System                                            6.3.14393

I will explain both errors with GUI and T-SQL.

With GUI:

Endpoints of success configuration on all servers

Enter image description here

But I had this mistake when I tried to mirror

Enter image description here

It's so confusing because the database on the mirror server needs to be in recovery state. But I have read some posts on it and it is recommended to configure with T-SQL, so

WITH T-SQL:

With T-SQL I had the following problem:

Message 1418, Level 16, State 1, Line 54 The server network address
"TCP: //HML-SQLS-01-TST.domain.br: 5022" can not be reached or does not exist. Check
the name of the network address and the ports for the local and remote servers
Endpoints are operational.

Let me explain step by step how I did it:

PRINCIPAL SERVER

CREATE DATABASE mirror
GO

ALTER DATABASE mirror
SET RECOVERY FULL
GO

USE mirror
GO

CREATE TABLE TESTE(
    id INT IDENTITY(1,1),
    descricao VARCHAR(255)
);

BACKUP DATABASE mirror
TO DISK = 'F:Backupmirror-full.bak'
GO

BACKUP LOG mirror
TO DISK = 'F:Backupmirror-log.bak'
GO


CREATE ENDPOINT Mirroring
    STATE = started
    AS TCP (listener_port=5022)
    FOR database_mirroring (role=partner)
GO

USE MASTER
GO
CREATE LOGIN (DOMAINsvc.witness) FROM WINDOWS
GO
GRANT CONNECT ON ENDPOINT::Mirroring TO (DOMAINsvc.witness);
GO

SPIEGEL SERVER

CREATE ENDPOINT Mirroring
    STATE = started
    AS TCP (listener_port=5022)
    FOR database_mirroring (role=partner)
GO

RESTORE DATABASE mirror
FROM DISK = 'F:Backupmirror-full.bak'
WITH NORECOVERY
GO

RESTORE DATABASE mirror
FROM DISK = 'F:Backupmirror-log.bak'
WITH NORECOVERY
GO

USE MASTER
GO
CREATE LOGIN (DOMAINsvc.witness) FROM WINDOWS
GO
GRANT CONNECT ON ENDPOINT::Mirroring TO (DOMAINsvc.witness);
GO

WITNESSES SERVER

create endpoint Mirroring
state = started
    as tcp (listener_port=5022)
    for database_mirroring (role=WITNESS)
go

USE MASTER
GO
CREATE LOGIN (DOMAINsvc.witness) FROM WINDOWS
GO
GRANT CONNECT ON ENDPOINT::Mirroring TO (DOMAINsvc.witness);
GO

SPIEGEL SERVER

alter database mirror
set partner = 'TCP://HML-SQLS-01.domain.br:5022'
GO

PRINCIPAL SERVER (The error occurs with this execution.)

--The error pops in this execution:
alter database mirror
set partner = 'TCP://HML-SQLS-01-TST.domain.br:5022'
GO

Message 1418, Level 16, State 1, Line 54 The server network address
"TCP: //HML-SQLS-01-TST.domain.br: 5022" can not be reached or does not exist. Check
the name of the network address and the ports for the local and remote servers
Endpoints are operational.

But when I try this command in CMD, it works perfectly:

telnet hml-sqls-01-tst.domain.br 5022

END POINTS WITH SERVER:

Main server endpoint
Enter image description here

Mirror server endpoint
Enter image description here

Witness server endpoint
Enter image description here

Has anyone gone through this or could he suggest a way forward?

kubernetes – helmet installed qliksense | Secrets already exist

I'm pretty new to Kubernetes. I run a Kubernetes cluster on EKS (AWS).
When I install QlikSense on a Kubernet, I get the following error message.

Command:

helm install -n qliksense qlik/qliksense -f values.yaml

error:

Error: release qliksense failed: secrets "qliksense-nats-secret" already exists

Any idea how to solve this?
Thanks!

magento2.3 – magento 2.3.2 with elasticsearch 6.8.2 returns results that only exist in the mysql search_query table

Requirements:
Installation and configuration of Elasticsearch 6.8.2 in a Magento 2.3.2 installation according to Devdocs (new indexing and cache: clean and orderly)

To be reproduced step:
Insert a term into the search bar of the Magento frontend

Expected behavior:
have back suggestions from elastic docs

Actual result:
We see that the autocomplete suggestions (returned via Ajax) in the Magento search bar still return terms that are present in the mysql search_query table (popular search terms pasted by previous visitors).
These terms are not available in elastic (reviewed by Kibana Dev Tools).

So far, we have not dug into the core of the Magento 2.3 Elastic core module, but this leads us to conclude that the search results are still from MySQL and not from Elastic.

that leads us to 2 questions:

  1. is that a bug? the magento2.3 elaticsearch module still queries the mysql search_query table?

  2. the second, more general and perhaps due to the fact that we are not experienced users of Ekl stacks: is there an easy way to determine whether search results come from MySQL or Elastic? Should we use xdebug or is elastic provided with tools to help us understand if a GET call has occurred (possibly with kibana)?

In elastic error logs no errors are displayed, elasticsearch_access.log is empty.

Thank you very much,
Romeo

Magento 2.3.2
Elasticserch 6.8.2
Kibana
php7.2

Kibana query returning a blank result:
"Query": {
"bool": {
"Got to": (
{
"query_string": {
"Query": "mySearchedTerm"
"analysis_wildcard": true,
"default_field": "*"
}
}
)
"filter": (),
"should": (),
"not allowed": ()
}
},

SSH public key sign-on for users who do not (yet) exist

How can I configure under Linux (eg Ubuntu 18.04)? sshd Allow public key sign-on for operating system users that do not already exist?

For example:

  1. On the server: / etc / ssh / sshd_config has AuthorizedKeysFile: /etc/ssh/keys/%u

  2. sudo mkdir -p /etc/ssh/keys

  3. sudo tee /etc/ssh/keys/foo <<< "$(cat id_rsa.pub)"

  4. sudo systemctl restart sshd

  5. On the client: ssh foo @ server

In this scenario, the server does NOT have one foo Account in /etc/passwdbut I want to create one automatically and then use it pam_mkhomedir to create its home directory - all because the user can successfully authenticate with a public key.

My attempt:

  1. /etc/pam.d/sshd comment out @include common-auth (does not make any difference as public keys bypass this anyway)

  2. /etc/pam.d/sshd comment out @include common-account

  3. /etc/ssh/sshd_config LogLevel: DEBUG3 shows

debug1: matching key found
debug3: mm_answer_keyallowed: key is allowed
debug3: PAM: do_pam_account pam_acct_mgmt = 6 (Permission denied)

WST complicates the job search and does not exist anymore

A few days ago, the child of a colleague from abroad returned and told me eagerly that the child had returned from school and had to enjoy it. However, a few days ago, I was so sad that I knew my child was looking for a job. With the improvement of the economic level, it has become a common practice to send children abroad. Many parents want their children to have more exposure to international developments and to learn more about international culture. The violent ignition, so this thing of my colleagues is also my expectation.

At the same time, they face problems for overseas returnees, such as information asymmetry at home and abroad, as well as their own quality and the mismatch of jobs. The argument that I was unemployed at the same time was also applied to the group of foreign students: In view of the current employment difficulties for foreign students, many job search platforms were created, which is why I recommended my colleague WST. WST's job search is highly trusted and is favored by international students with targeted courses, transparent work results, and the number of offers. …

WST complicates the job search and does not exist anymore

out

Probability Theory – How can I show this for the random variable $ Z $ with the charateristic function $ e ^ {- vert t vert + it} $, $ E?[vert Z vert]$ does not exist?

Thank you for your reply to Mathematics Stack Exchange!

  • Please be sure too answer the question, Provide details and share your research!

But avoid

  • Ask for help, clarify or respond to other answers.
  • Make statements based on opinions; Cover them with references or personal experience.

Use MathJax to format equations. Mathjax reference.

For more information, see our tips for writing great answers.

Google Search Console creates URLs that do not exist in my Sitemap, and then complains that these pages are broken

You have a wrong idea of ​​what a sitemap is.

The sitemap is used to monitor the crawling of the site by the search engine bot. The sitemap and crawling a site are two different and independent things. Google continues to search your site independently of the sitemap. The sitemap is used to check if Google can properly crawl your site. For example, if pages are found in your sitemap and Google has not seen the page, Google may add the page to the fetch queue to include.

The opposite is not true. If a page is not found in the sitemap, Google will not remove it from the index. Why? Because Google found it by crawling the site.

What you seem to believe is that the sitemap is the absolute authority Google uses to identify which pages exist on a particular site. That's not the case. The crawl is. The sitemap only helps Google to know if You can properly crawl your site, and if not, what pages Google is missing that should be added to the fetch queue.

Your expectation that Google will stop trying to access pages because these pages are no longer in your sitemap is wrong. Sitemaps are cached and checked at regular intervals. Why? Because it is a testing process.

You have a real problem that you need to solve.

You return a 500 error for pages that were not found. This is bad. Your website should return a 404 Not Found error. The 500 error is a system error and is treated as temporary by Google. If your site returns a 404 error, Google will still try the page a few times over a period of time, until it finds that the page no longer exists. If possible, you want to output a 410 Removed error for pages that you have removed. If this is too much work or not possible, the 404 will mean the same over time.

You must fix your 500 error.