Last post Feb 12, 2019 12:14 AM by iamadnan
Feb 11, 2019 02:33 PM|iamadnan|LINK
I am trying to upgrade a previously installed/running Asp.net core (self contained) application on a Debian vm. After I copy the new dlls and test with dotnet path-to-my-app.dll I get this
error, which I have no idea about.
LTTng-UST: Error (-17) while registering tracepoint probe. Duplicate registration of tracepoint probes having the same name is not allowed.
I am probably doing something wrong, either in deployment or configuration but can't really pin-point it. There is hardly anything available on this so any help is highly appreciated.
Feb 11, 2019 10:03 PM|Radomir|LINK
Hmm.. what kind of tracing you have there/enabled:
"...Just to clarify, any of the approaches above still require launching the application with the COMPlus_EnableEventLog=1 environment variable. If it is off, the entire eventing infrastructure is not invoked at all."
Feb 11, 2019 10:18 PM|iamadnan|LINK
It is just a regular aspent core service, nothing special, but I do stop it before replacing any files. After the files are replaced it doesn't start.
Feb 11, 2019 10:19 PM|Radomir|LINK
You may be running into this:
Related to that is:
Feb 11, 2019 10:43 PM|iamadnan|LINK
I build it with "dotnet build --runtime linux-x64" and am running it on a Debian, The target framework used is 2.1.0.
What am I supposed to do for a quick fix before waiting for 3.0?
What do you suggest?
Feb 11, 2019 10:56 PM|Radomir|LINK
What I have so far is:
"This issue should only happen if libcoreclr.so and the DAC (libmscordaccore.so) are loaded in the same process from two different runtime versions. "
is it possible those are getting onto the target system like that? Or does your target VM have different runtime than what the app is targeting?
Pls hold on.. I may have additional questions :)
Feb 11, 2019 11:32 PM|bruce (sqlwork.com)|LINK
the most likely cause is the installed version of .net core hosting your app, is a different version than the deployed asp.net core app. you should rsh to the linux box and check the installed versions. (I use a mac, so don't know the linux folders its installed
if this doesn't match that's your issue. fix the version on linux or match. if you don't control the linux box, then try a self contained deployment.
Feb 12, 2019 12:14 AM|iamadnan|LINK
Yup that is what I was upto in the mean while, the version on my linux VM was 2.1.5 and my App target version was 2.1.0, However the previous target framework version of installed app was 2.1.0 and it was working fine. I only made a few changes and went
on to deploy the new version, first it failed to build with the command "dotnet build --runtime linux-x64" complaining about different frameworks to restore and build. So I first changed the project file to use
And after that I failed to deploy with the above error. Finally I changed the RuntimeFrameworkVersion to 2.1.5 to match my host version AND didn't use the "dotnet build --runtime linux-x64" command but Publish instead. I also read about using the Publish