国产中标麒麟Linux部署dotnet core 环境并运行项目 (二) 部署运行控制台项目

背景
在上一篇文章安装dotnet core,已经安装好dotnet core了。之前只是安装成功了dotnet, 输入dotnet --info,可以确认安装成功了,但是在运行代码时,还是报错了,本章记录在部署好dotnet core后,到能运行控制台程序当中的错误。

首先将项目用vs发布一下,然后把文件放到中标麒麟的系统上,在文件夹打开终端,执行 dotnet **.dll,结果如下:

[root@gumis02 PublishOutput]# dotnet Beyondbit.ConsoleFrameworkNetStandard.IntegrationTests.dll
Failed to load \ufffd=l, error: libunwind.so.8: cannot open shared object file: No such file or directory
Failed to bind to CoreCLR at '/home/dotnet/shared/Microsoft.NETCore.App/2.0.7/libcoreclr.so'

[root@gumis02 PublishOutput]#

错误 error : libunwind.so.8: cannot open shared object file: No such file or directory

修复此问题的解决方案是安装 libunwind

手动源码安装 libunwind

libunwind的源代码现在已经托管到github上了,libunwind github 地址
我安装的是最新版1.2.1, 输入下面命令安装:

wget https://github.com/libunwind/libunwind/releases/download/v1.2.1/libunwind-1.2.1.tar.gz
tar -xf libunwind-1.2.1.tar.gz
cd libunwind-1.2.1
CFLAGS=-fPIC ./configure  #添加编译参数 
make CFLAGS=-fPIC 
make CFLAGS=-fPIC install 

安装成功后,再执行dotnet **.dll,会发现依然报错ibunwind.so.8: cannot open shared object file: No such file or directory
在输入以下命令修复:

[root@gumis02 dotnet]# find / -name libunwind.so.8
/home/.Trash-0/files/libunwind-1.2.1/src/.libs/libunwind.so.8
/home/NetCoreSdk/libunwind-1.2.1/src/.libs/libunwind.so.8
/usr/local/lib/libunwind.so.8
[root@gumis02 dotnet]# ln -s /usr/local/lib/libunwind.so.8 /lib64/
[root@gumis02 dotnet]# ln -s /usr/local/lib/libunwind.so.8 /lib

[root@gumis02 dotnet]# find / -name libunwind-x86_64.so.8
/home/.Trash-0/files/libunwind-1.2.1/src/.libs/libunwind-x86_64.so.8
/home/NetCoreSdk/libunwind-1.2.1/src/.libs/libunwind-x86_64.so.8
/usr/local/lib/libunwind-x86_64.so.8

[root@gumis02 dotnet]# ln -s /usr/local/lib/libunwind-x86_64.so.8 /lib64/
[root@gumis02 dotnet]# ln -s /usr/local/lib/libunwind-x86_64.so.8 /lib

输入后,再执行dotnet **.dll,发现上面的问题已经消失。但是出现新的错误提示:

FailFast: Couldn't find a valid ICU package installed on the system. Set the configuration flag System.Globalization.Invariant to true if you want to run with no globalization support.

   at System.Environment.FailFast(System.String)
   at System.Globalization.GlobalizationMode.GetGlobalizationInvariantMode()
   at System.Globalization.GlobalizationMode..cctor()
   at System.Globalization.CultureData.CreateCultureWithInvariantData()
   at System.Globalization.CultureData.get_Invariant()
   at System.Globalization.CultureData.GetCultureData(System.String, Boolean)
   at System.Globalization.CultureInfo.InitializeFromName(System.String, Boolean)
   at System.Globalization.CultureInfo.Init()
   at System.Globalization.CultureInfo..cctor()
   at System.StringComparer..cctor()
   at System.AppDomainSetup.SetCompatibilitySwitches(System.Collections.Generic.IEnumerable`1<System.String>)
   at System.AppDomain.PrepareDataForSetup(System.String, System.AppDomainSetup, System.Security.Policy.Evidence, System.Security.Policy.Evidence, IntPtr, System.String, System.String[], System.String[])
\u5df2\u653e\u5f03 (core dumped)
[root@gumis02 PublishOutput]# 

下一步,准备修复这个错误.

错误 Couldn't find a valid ICU package installed on the system. Set the configuration flag System.Globalization.Invariant to true if you want to run with no globalization support.

查找资料显示,这是NET Core 全球化的模式,可见微软的文章 NET Core Globalization Invariant Mode

摘取一段原文说明背景

Globalization rules and the data that represents those rules frequently change, often due to country-specific policy changes (for example, changes in currency symbol, sorting behavior or time zones). Developers expect globalization behavior to always be current and for their applications to adapt to new data over time. In order to keep up with those changes, .NET Core (and the .NET Framework, too) depends on the underlying OS to keep up with these changes.

Relying on the underlying OS for globalization data has the following benefits:

  • .NET apps have the same globalization behavior on a given OS as native apps (assuming they also rely on the OS).
  • .NET apps do not have to carry this data.
  • The .NET team doesn't have to maintain this data themselves (it's very expensive to do this!).

Globalization support has the following potential challenges for applications:

  • Different behavior across OSes (and potentially OS versions).
  • Installing/carrying the ICU package on Linux (~28 MB).

Note: On Linux, .NET Core relies on globalization data from ICU. For example, .NET Core Linux Docker images install this component. Globalization data is available on Windows and macOS as part of their base installs.

上文提到依赖 ICU Package,可点击链接去查看。

有两种解决方案:

  1. 在runtimeconfig.json中添加以下配置即可,不想纠结原理的就使用这种方式即可:
    "configProperties": {
      "System.Globalization.Invariant": true
    }

完整的在runtimeconfig.json 如下:

{
  "runtimeOptions": {
    "tfm": "netcoreapp2.0",
    "framework": {
      "name": "Microsoft.NETCore.App",
      "version": "2.0.0"
    },
   "configProperties": {
      "System.Globalization.Invariant": true
    }
  }
}

注意
这种方式,证明了是可以解决问题的,但是他开启了Globalization.Invariant Mode 模式,在简单的应用下,程序可以正常运行,但是在遇到复杂的应用很有可能会遇到一个异常,System.ArgumentNullException: SafeHandle cannot be null,见我正式项目的运行结果,这个异常在github上有很多人提到,如:

我的测试项目就是用了log4net导致的,目前net corefx团队收到了反馈已经在着手解决了。要想终极解决此问题,需要用以下第二种方式来解决,安装 ICU Package模块。

  1. 安装ICU Package

ICU Package

我们使用源码的方式安装icu. 我选择的是59.1版本,输入以下命令:

wget http://download.icu-project.org/files/icu4c/59.1/icu4c-59_1-src.tgz 
tar -xzvf icu4c-59_1-src.tgz
cd icu/source
./configure --prefix=/usr/local/icu

make 
make install 

参看是否安装成功:

[root@gumis02 ~]# icu-config --version
59.1
[root@gumis02 ~]# icuinfo
icuinfo: error while loading shared libraries: libicutu.so.59: cannot open shared object file: No such file or directory

看到安装成功了,但是查看具体信息会提示缺少 libicutu.so.59,其他缺少的dll,同样处理。
输入以下命令查找,并映射so文件:

[root@gumis02 ~]# find / -name libicutu.so.59
/home/NetCoreSdk/icu/source/lib/libicutu.so.59
/home/NetCoreSdk/icu2/source/lib/libicutu.so.59
/usr/lib/libicutu.so.59
/usr/local/icu/lib/libicutu.so.59

[root@gumis02 ~]# ln -s /usr/local/icu/lib/libicutu.so.59 /lib64/
[root@gumis02 ~]# ln -s /usr/local/icu/lib/libicui18n.so.59 /lib64/
[root@gumis02 ~]# ln -s /usr/local/icu/lib/libicuuc.so.59 /lib64/
[root@gumis02 ~]# ln -s /usr/local/icu/lib/libicudata.so.59 /lib64/
[root@gumis02 ~]# ln -s /usr/local/icu/lib/libicudata.so.59 /lib64/ 
[root@gumis02 ~]# icuinfo
 <icuSystemParams type="icu4c">
    <param name="copyright"> Copyright (C) 2016 and later: Unicode, Inc. and others. License & terms of use: http://www.unicode.org/copyright.html </param>
    <param name="product">icu4c</param>
    <param name="product.full">International Components for Unicode for C/C++</param>
    <param name="version">59.1</param>
    <param name="version.unicode">9.0</param>
    <param name="platform.number">4000</param>
    <param name="platform.type">Linux</param>
    <param name="locale.default">zh_CN</param>
    <param name="locale.default.bcp47">zh-CN</param>
    <param name="converter.default">UTF-8</param>
    <param name="icudata.name">icudt59l</param>
    <param name="icudata.path"></param>
    <param name="cldr.version">31.0.1</param>
    <param name="tz.version">2017b</param>
    <param name="tz.default">PRC</param>
    <param name="cpu.bits">64</param>
    <param name="cpu.big_endian">0</param>
    <param name="os.wchar_width">4</param>
    <param name="os.charset_family">0</param>
    <param name="os.host">x86_64-unknown-linux-gnu</param>
    <param name="build.build">x86_64-unknown-linux-gnu</param>
    <param name="build.cc">gcc</param>
    <param name="build.cxx">g++</param>
    <param name="uconfig.internal_digitlist">1</param>
    <param name="uconfig.have_parseallinput">1</param>
    <param name="uconfig.format_fastpaths_49">1</param>
 </icuSystemParams>


ICU Initialization returned: U_ZERO_ERROR
Plugins are disabled.

参考:

install ICU-61.1
安装完成后,再测试正式的项目,执行成功了,数据插入到数据库了。

运行测试

HelloWorld 项目

采用配置了 runtimeconfig.json中添加以下配置

    "configProperties": {
      "System.Globalization.Invariant": true
    }

HelloWorld程序运行测试:

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.7
  Build    : 2d61d0b043915bc948ebf98836fefe9ba942be11

[root@gumis02 ConsoleTest2]# dotnet ConsoleApp2.dll
FailFast: Couldn't find a valid ICU package installed on the system. Set the configuration flag System.Globalization.Invariant to true if you want to run with no globalization support.

   at System.Environment.FailFast(System.String)
   at System.Globalization.GlobalizationMode.GetGlobalizationInvariantMode()
   at System.Globalization.GlobalizationMode..cctor()
   at System.Globalization.CultureData.CreateCultureWithInvariantData()
   at System.Globalization.CultureData.get_Invariant()
   at System.Globalization.CultureData.GetCultureData(System.String, Boolean)
   at System.Globalization.CultureInfo.InitializeFromName(System.String, Boolean)
   at System.Globalization.CultureInfo.Init()
   at System.Globalization.CultureInfo..cctor()
   at System.StringComparer..cctor()
   at System.AppDomainSetup.SetCompatibilitySwitches(System.Collections.Generic.IEnumerable`1<System.String>)
   at System.AppDomain.PrepareDataForSetup(System.String, System.AppDomainSetup, System.Security.Policy.Evidence, System.Security.Policy.Evidence, IntPtr, System.String, System.String[], System.String[])
\u5df2\u653e\u5f03 (core dumped)
[root@gumis02 ConsoleTest2]# dotnet ConsoleApp2.dll
Hello World!
[root@gumis02 ConsoleTest2]# 

正式控制台项目

在runtimeconfig.json中添加以下配置即可,不想纠结原理的就使用这种方式即可:

    "configProperties": {
      "System.Globalization.Invariant": true
    }

上面的这种方式,我使用helloworld程序是能正常运行的,但是在正式的项目中,用到了log4net,运行的话,会报其他的错误:

[root@gumis02 PublishOutput]# dotnet Beyondbit.ConsoleFrameworkNetStandard.IntegrationTests.dll

Unhandled Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ArgumentNullException: SafeHandle cannot be null.
Parameter name: pHandle
   at System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument, ExceptionResource resource)
   at System.StubHelpers.StubHelpers.SafeHandleAddRef(SafeHandle pHandle, Boolean& success)
   at Interop.GlobalizationInterop.GetSortKey(SafeSortHandle sortHandle, String str, Int32 strLength, Byte* sortKey, Int32 sortKeyLength, CompareOptions options)
   at System.Globalization.CompareInfo.GetHashCodeOfStringCore(String source, CompareOptions options, Boolean forceRandomizedHashing, Int64 additionalEntropy)
   at System.Collections.Hashtable.GetHash(Object key)
   at System.Collections.Hashtable.InitHash(Object key, Int32 hashsize, UInt32& seed, UInt32& incr)
   at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)
   at System.Collections.Hashtable.set_Item(Object key, Object value)
   at log4net.Core.LevelMap.Add(Level level)
   at log4net.Repository.LoggerRepositorySkeleton.AddBuiltinLevels()
   at log4net.Repository.LoggerRepositorySkeleton..ctor(PropertiesDictionary properties)
   at log4net.Repository.Hierarchy.Hierarchy..ctor(PropertiesDictionary properties, ILoggerFactory loggerFactory)
   --- End of inner exception stack trace ---
   at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor)
   at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
   at System.Activator.CreateInstance(Type type, Boolean nonPublic)
   at System.Activator.CreateInstance(Type type)
   at log4net.Core.DefaultRepositorySelector.CreateRepository(String repositoryName, Type repositoryType)
   at log4net.Core.DefaultRepositorySelector.CreateRepository(Assembly repositoryAssembly, Type repositoryType, String repositoryName, Boolean readAssemblyAttributes)
   at log4net.Core.LoggerManager.GetLogger(Assembly repositoryAssembly, String name)
   at log4net.LogManager.GetLogger(Type type)
   at Beyondbit.Framework.Core.Proxy.Proxy.SetSessionToContext(ISession session) in E:\\u5de5\u4f5c\u533a\03 \u4e92\u8054\u7f51\00 Beyondbit Infrastructure\\u5f00\u53d1\u6846\u67b6\3.0\Beyondbit.Framework\Core\Proxy\Proxy.cs:line 117
   at Beyondbit.Framework.Core.Proxy.Proxy.CreateClassProxy[T]() in E:\\u5de5\u4f5c\u533a\03 \u4e92\u8054\u7f51\00 Beyondbit Infrastructure\\u5f00\u53d1\u6846\u67b6\3.0\Beyondbit.Framework\Core\Proxy\Proxy.cs:line 82
   at Beyondbit.Framework.Core.Proxy.Proxy.CreateObject[T]() in E:\\u5de5\u4f5c\u533a\03 \u4e92\u8054\u7f51\00 Beyondbit Infrastructure\\u5f00\u53d1\u6846\u67b6\3.0\Beyondbit.Framework\Core\Proxy\Proxy.cs:line 55
   at Beyondbit.ConsoleFrameworkNetStandard.IntegrationTests.Program.Insert() in E:\\u5de5\u4f5c\u533a\03 \u4e92\u8054\u7f51\00 Beyondbit Infrastructure\\u5f00\u53d1\u6846\u67b6\3.0\Test\Integration\ConsoleFrameworkNetStandard\Program.cs:line 22
   at Beyondbit.ConsoleFrameworkNetStandard.IntegrationTests.Program.Main(String[] args) in E:\\u5de5\u4f5c\u533a\03 \u4e92\u8054\u7f51\00 Beyondbit Infrastructure\\u5f00\u53d1\u6846\u67b6\3.0\Test\Integration\ConsoleFrameworkNetStandard\Program.cs:line 14
\u5df2\u653e\u5f03 (core dumped)
[root@gumis02 PublishOutput]# 

可以看到错误的调用堆栈,是由log4net运行出来的,这个很有可能是里面需要增加全局资源文件,因为看到了System.Globalization命名空间,不过呢,已经能看到了正常的net 错误堆栈,可以证明dotnet 已经在中标麒麟的操作系统上能运行了。

这个异常产生的原因我在上面已经说明了,要解决这个问题,不能开启Globalization.Invariant,必须讲他设置成false,同时安装ICU Packet解决
在runtimeconfig.json中添加以下配置即可,不想纠结原理的就使用这种方式即可:

    "configProperties": {
      "System.Globalization.Invariant": false
    }

执行结果:

[root@gumis02 PublishOutput]# dotnet Beyondbit.ConsoleFrameworkNetStandard.IntegrationTests.dll
用户插入成功
[root@gumis02 PublishOutput]# 

dotnet core 2.0 在真实项目上,还有很多的未知,还等待我去解决和探索。 Keep going.

总结
经过一个星期的摸爬滚打终于在中标麒麟Linux系统上成功的运行了dotnet core 正式的项目,而不是helloworld程序。心力交瘁中也收获了很多东西,在这一个星期中,我一个linux盲,也掌握了很多linux命令,如:mkdir,ln, find,ll,ldd 等等。

当然用了一个星期的时间,主要还是自己两方面的问题:

  1. 对linux不熟悉,基本是linux盲
  2. 对net core 底层的编译知识还不熟悉,在摸索当中

后续还要加强两方面的学习,学无止境

后续

成功的是控制台程序,下一步开始把做好的dotnet core web api + 前端 vuejs项目部署到麒麟系统上,我预计到又是一段打怪路程,通关后,我会继续将通关记录分享出来。

最后晒下截图:
image

转载于:https://www.cnblogs.com/xakoy/p/9039218.html

  • 0
    点赞
  • 2
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
ASP.NET Core是一种开源的跨平台的Web应用程序框架,其特点是高性能、可扩展性和灵活性。ASP.NET Core项目的发布和运行环境部署可以分为以下几个步骤: 1. 项目发布: 首先,我们需要通过运行相应的命令或使用Visual Studio等工具来发布ASP.NET Core项目。发布时我们可以选择多种部署模式,例如自包含部署和依赖部署。自包含部署会将项目的所有依赖项都打包到发布文件夹中,这样可以使项目在目标服务器上独立运行,而不需要依赖全局安装的.NET Core SDK等组件。依赖部署则可以减小发布文件夹的大小,但在目标服务器上需要预先安装.NET Core运行时,以便项目能够运行。 2. 运行环境配置: 在进行项目部署之前,我们需要在目标服务器上配置ASP.NET Core项目所需的运行环境。首先,我们需要安装.NET Core SDK或.NET Core运行时,这样才能正确运行项目。其次,我们还需要配置Web服务器(如IIS、Nginx等)来处理HTTP请求,并将请求转发到ASP.NET Core应用程序。对于不同的Web服务器,配置方法会有所不同,一般会涉及到设置绑定和反向代理等。 3. 项目部署: 一旦运行环境配置完成,我们就可以将ASP.NET Core项目部署到目标服务器上。这可以通过将发布文件夹中的文件复制到目标服务器上的指定位置来完成。在部署过程中,我们需要确保将项目所需的配置文件、静态文件等一并复制到目标服务器上。 4. 运行项目部署完成后,我们可以通过运行相应的命令或通过Web服务器来启动ASP.NET Core项目。对于使用Kestrel作为Web服务器的情况,我们可以使用dotnet命令来启动项目。对于使用IIS作为Web服务器的情况,我们可以通过IIS Manager来配置应用程序池,将HTTP请求转发到ASP.NET Core应用程序。无论哪种方式,启动项目后,我们就可以通过访问相应的URL来使用ASP.NET Core应用程序了。 总结来说,ASP.NET Core项目的发布和运行环境部署需要经过项目发布、运行环境配置、项目部署运行项目等阶段。在整个过程中,我们需要注意配置正确的运行环境和Web服务器,并确保将项目所需的文件正确复制到目标服务器上。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值