Tag Archives: environment

[Solved] mongod: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No s

After mongodb is installed, mongod reports the following error:

mongod: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory

Solution:

# Switch to the lib directory
cd ~/.conda/envs/my_gdal/lib # my_gdal:virtual environment
# Check if the file exists
ls -lh | grep "libcrypto.so.1.1"
-rwxrwxrwx 1 root root 3.2M Jun 4 15:43 libcrypto.so.1.1
# If the file exists execute
sudo ldconfig ~/.conda/envs/my_gdal/lib
# If the file does not exist
sudo find/-name 'libcrypto.so.1.1'
# Execute: sudo ldconfig path found
sudo ldconfig ~/.conda/pkgs/openssl-1.1.1q-h7f8727e_0/lib/

[Solved] AgilePLM error: Ora-00904: “A”.”ITEM_NUMBER”: invalid identifier

AgilePLM error

Problem phenomenon

Agile version: 9.3.2

When searching for a material in full-text search, the error is report: ora-00904: “A”.”ITEM_NUMBER”:invalid identifier

However, no error will be reported when using advanced search to specify material search. Restart the database, restart the application and rebuild the index can not be solved.

Cause analysis

In the troubleshooting process, advanced search was used to search all objects one by one. Finally, it was found that the separate search price times was wrong. Later, the administrator remembered that he had changed a price standard in the morning and used the material code as the price standard. The problem may be caused by this operation.

Problem-solving

If the standard is changed, the material code cannot be used as the price standard. Then restart the agile application server. To solve the problem.

[Solved] An error occurred while processing your request…enable the Development environment by setting …

When a web project is deployed to the local machine, an exception occurs when accessing:

Error.
An error occurred while processing your request.
Request ID: |ee4a30bd-4030df869db691a6.

Development Mode
Swapping to Development environment will display more detailed information about the error that occurred.

The Development environment shouldn't be enabled for deployed applications. It can result in displaying sensitive information from exceptions to end users. For local debugging, enable the Development environment by setting the ASPNETCORE_ENVIRONMENT environment variable to Development and restarting the app.

 

Reason for the error:

The project itself uses the .netcore 3.1 framework, published to the IIS web.config, missing the ASPNETCORE_ENVIRONMENT configuration.

This error is displayed, meaning that the project itself reported an error, IIS thinks you can set the development version (Development) to see more detailed exception information, but you do not configure ASPNETCORE_ENVIRONMENT, so you can not think that this is the development version, you need to add, in order to show you the specific cause of the exception. So the configuration needs to be added.

Solution:
In the <aspNetCore> node of IIS web.config, add the ASPNETCORE_ENVIRONMENT configuration as follows.

<aspNetCore processPath="dotnet" arguments=".\IndustryWeb.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" hostingModel="inprocess" >
  <environmentVariables>
    <environmentVariable name="ASPNETCORE_ENVIRONMENT" value="Development" />
  </environmentVariables>
</aspNetCore>

[Win 10] Docker Error: error during connect: In the default daemon configuration on Windows 

error during connect: In the default daemon configuration on Windows, 
the docker client must be run with elevated privileges to connect.: 
Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/json: 
open //./pipe/docker_engine: The system cannot find the file specified.

solution: 

cd "C:\Program Files\Docker\Docker"
DockerCli.exe -SwitchDaemon