Skip to main content

Project Orleans error: System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions

I’m currently experimenting with Orleans and trying to compare it with my experiences using Akka.NET and the Azure Service Fabric actors. So far I like the experience although I encountered some issues in the beginning.

image

I got my first problem when trying the “hello world” of actor model examples; https://dotnet.github.io/orleans/Tutorials/My-First-Orleans-Application.html. After following the tutorial, my Orleans host blew up with the following exception:

ERROR starting Orleans silo name=[MyMachineName] Exception=
Exc level 0: System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Bind(EndPoint localEP)
at Orleans.Runtime.SocketManager.GetAcceptingSocketForEndpoint(IPEndPoint address)
at Orleans.Runtime.Messaging.IncomingMessageAcceptor..ctor(MessageCenter msgCtr, IPEndPoint here, SocketDirection socketDirection)
at Orleans.Runtime.Messaging.MessageCenter.Initialize(IPEndPoint here, Int32 generation, IMessagingConfiguration config, ISiloPerformanceMetrics metrics)
at Orleans.Runtime.Silo..ctor(String name, SiloType siloType, ClusterConfiguration config, ILocalDataStore keyStore)
at Orleans.Runtime.Silo..ctor(String name, SiloType siloType, ClusterConfiguration config)
at Orleans.Runtime.Host.SiloHost.InitializeOrleansSilo()

Whoops! Not a great start for my first experience with Orleans. A netstat –o brought some insight into the root cause of this issue. The default port used by Orleans(port 22222) was already in use.  I removed the tool(RedGate Ants Profiler in my case) that was using the port and I was good to go!

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more