What is system requirements for VPS to deploy self-hosted Photon server?

Options
vuxuanhung
vuxuanhung ✭
in Photon Server
Hello,
What is system requirements for VPS to deploy self-hosted Photon (free licence 100 ccu) ?
I tried to run photon on Amazon t2.micro instance and cannot start. 
3912: 08:28:59.375 - Config|INFO| New TCP: Max message size: 512000
3912: 08:28:59.375 - Config|INFO| New TCP: TODO - Business logic pool not curently supported for TCP dispatch
3912: 08:28:59.375 - About to load application: Master from Photon.LoadBalancing
3912: 08:29:00.703 - Taking reference on default app domain
3912: 08:29:00.890 - Master:2 - Start() failed. Exception:
System.ArgumentException: fibersToUse can not be less 0
   at Photon.SocketServer.Concurrency.CPUResourceManager..ctor(Int32 fibersToUse, IFiberFactory fiberFactory) in H:\SvnContent\photon-socketserver-sdk-branches\sdk_5.0\src\Photon.SocketServer\Concurrency\CPUResourceManager.cs:line 55
   at Photon.SocketServer.ApplicationBase..ctor() in H:\SvnContent\photon-socketserver-sdk-branches\sdk_5.0\src\Photon.SocketServer\ApplicationBase.cs:line 127
   at Photon.LoadBalancing.MasterServer.MasterApplication..ctor() in H:\SvnContent\photon-socketserver-sdk-branches\sdk_5.0\src-server\Loadbalancing\LoadBalancing\MasterServer\MasterApplication.cs:line 55
 at...
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ArgumentException: fibersToUse can not be less 0
   at Photon.SocketServer.Concurrency.CPUResourceManager..ctor(Int32 fibersToUse, IFiberFactory fiberFactory) in H:\SvnContent\photon-socketserver-sdk-branches\sdk_5.0\src\Photon.SocketServer\Concurrency\CPUResourceManager.cs:line 55
   at Photon.SocketServer.ApplicationBase..ctor() in H:\SvnContent\photon-socketserver-sdk-branches\sdk_5.0\src\Photon.SocketServer\ApplicationBase.cs:line 127
   at Photon.LoadBalancing.MasterServer.MasterApplication..ctor() in H:\SvnContent\photon-socketserver-sdk-branches\sdk_5.0\src-server\Loadbalancing\LoadBalancing\MasterServer\MasterApplication.cs:line 55
   --- End of inner exception stack trace ---
   at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
   at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
   at System.Activator.CreateInstance(Type type, Boolean nonPublic)
   at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark)
   at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
   at System.Reflection.Assembly.CreateInstance(String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
   at PhotonHostRuntime.PhotonDomainManager.?????????????????????????????????????????.?????????????????????????????????????????(String , String , String , String , IPhotonApplicationSink , ILogToUnmanagedLog , IControlListeners )
   at PhotonHostRuntime.PhotonDomainManager.Start(String assemblyName, String typeName, String instanceName, String applicationName, IPhotonApplicationSink sink, ILogToUnmanagedLog logger, IControlListeners listenerControl)
3912: 08:29:00.890 - Master:2 - Stop() failed.
Exception:
System.Exception: Stop: unable to call the Application.TearDown() - undefined photonControl.
   at PhotonHostRuntime.PhotonDomainManager.?????????????????????????????????????????.?????????????????????????????????????????()
   at PhotonHostRuntime.PhotonDomainManager.Stop()
3912: 08:29:00.890 - ERROR: Failed to start application: "Master" in app domain: 2
3560: 08:29:00.890 - CManagedHost::OnDefaultAction() - OPR_AppDomainUnload - eUnloadAppDomain
4824: 08:29:00.915 - Unloading Domain: ApplicationName = 'Master', DomainId='2'
3560: 08:29:00.915 - CManagedHost::OnDomainUnload() - 2
3912: 08:29:00.917 - CService::OnException() - Exception: CManagedHost::StartApplication() - Failed to start application in AppDomain: 2 - The parameter is incorrect.
3912: 08:29:00.917 - Server shutting down...
3912: 08:29:00.917 - Shutdown monitoring enabled, 60000ms before process abort
3912: 08:29:00.917 - Notifying CLR applications of shutdown...
3912: 08:29:00.917 - RequestStop: defalt app domain
3912: 08:29:00.917 - Shutting down NEW TCP Outbound Connection Manager...
3912: 08:29:00.917 - Shutting down WebSocket Outbound Connection Manager...
3912: 08:29:00.917 - Shutting down ENet Outbound Connection Manager...
3912: 08:29:00.917 - Disconnecting all outbound peers...
3912: 08:29:00.917 - Shutting down ENet host...
3912: 08:29:00.917 - Disconnecting all peers...
3912: 08:29:00.917 - Shutting down socket servers...
3912: 08:29:00.917 - Shutting down ENet thread pool...
3912: 08:29:00.917 - CENetThreadPool::WaitForShutdownToComplete() - cannot force thread termination on timeout - Unix doesn't support it
3912: 08:29:00.917 - Shutting down TCP inactivity timers...
3912: 08:29:00.917 - Waiting for socket servers to shutdown...
3912: 08:29:00.917 - Shutting down I/O thread pool...
3912: 08:29:00.917 - Shutting down CLR applications...
3912: 08:29:00.917 - Shutting down network data traces...
3912: 08:29:00.917 - Waiting for network data traces to complete...
3912: 08:29:00.917 - Destroying servers
3912: 08:29:00.917 - Destroying WebRTC Outbound Connection Manager
3912: 08:29:00.917 - Destroying WebRTC Outbound Host
3912: 08:29:00.917 - Destroying outbound ICE connection manager
3912: 08:29:00.917 - Destroying ENet timer wheel
3912: 08:29:00.917 - Destroying Network Data Trace factory
3912: 08:29:00.917 - Destroying ENet host
3912: 08:29:00.917 - Destroying ENet outbound connection manager
3912: 08:29:00.917 - Destroying HTTP inactivity timer queue
3912: 08:29:00.917 - Destroying HTTP host
3912: 08:29:00.917 - Destroying HTTP Chunk host
3912: 08:29:00.917 - Destroying WebRTC inactivity timer queue
3912: 08:29:00.917 - Destroying WebRTC host
3912: 08:29:00.917 - Destroying ICE connection manager
3912: 08:29:00.917 - Flushing stream socket allocator...
3912: 08:29:00.917 - Flushing inbound datagram socket allocator...
3912: 08:29:00.917 - Flushing outbound datagram socket allocator...
3912: 08:29:00.917 - Flushing NEW TCP socket allocator...
3912: 08:29:00.917 - Destroying TCP inactivity timer
3912: 08:29:00.917 - Flushing ENET buffer allocator...
3912: 08:29:00.917 - Flushing TCP buffer allocator...
3912: 08:29:00.917 - Flushing TCP buffer handle allocator...
3912: 08:29:00.917 - Destroying CLR dispatcher
3912: 08:29:00.917 - Destroying CLR applications
3912: 08:29:00.917 - ~CCLRApplicationCollection() - Waiting up to 10 seconds for the CLR to release all of our objects
3912: 08:29:00.917 - ~CCLRApplicationCollection() - Done. All objects released
3912: 08:29:00.917 - ~CManagedHost() - Release default app domain
3912: 08:29:00.917 - CManagedHost::OnDomainUnload() - 1
3912: 08:29:00.917 - ~CManagedHost() - Waiting up to 10 seconds for CLR shutdown...
3912: 08:29:00.933 - ~CManagedHost
3912: 08:29:00.933 - Destroying ENet thread pool
3912: 08:29:00.933 - Destroying Direct dispatcher
3912: 08:29:00.933 - Destroying I/O thread pool
3912: 08:29:00.933 - Destroying ENet I/O thread pool
3912: 08:29:00.933 - Destroying ENet buffer allocator
3912: 08:29:00.933 - Destroying TCP buffer allocator
3912: 08:29:00.933 - Destroying TCP socket allocator
3912: 08:29:00.933 - Destroying NEW TCP socket scheduler
3912: 08:29:00.933 - Destroying NEW TCP socket allocator
3912: 08:29:00.933 - Destroying NEW TCP configuration
3912: 08:29:00.933 - Config|INFO| New TCP: Flushing TCP socket allocator...
3912: 08:29:00.933 - Config|INFO| New TCP: Flushing TCP buffer allocator...
3912: 08:29:00.933 - Config|INFO| New TCP: Flushing TCP buffer handle allocator...
3912: 08:29:00.933 - Config|INFO| New TCP: Flushing policy file buffer allocator...
3912: 08:29:00.933 - Destroying ENet inbound socket allocator
3912: 08:29:00.933 - Destroying ENet outbound socket allocator
3912: 08:29:00.933 - Destroying shared datagram flow control data
3912: 08:29:00.948 - Shutdown complete...
3912: 08:29:00.948 - Service shutting down: failed to start application. Errorcode: 108
3912: 08:29:01.073 - Service shut down complete

Comments

Cookies,
anyone?

We use cookies and related technologies to enhance your experience, show you personalised content and analyze performance and traffic on our website. By clicking on the „Accept All“ button you consent to the use of non-functional cookies and the subsequent processing of personal data to optimize our website and services as described in more detail in our Privacy and Cookie Policy.

By clicking on the „Customize or Deny all“ button you can decide otherwise. Clicking on the „Customize“ button will take you to a page where you can configure the usage of non-functional cookies (and related technologies) or deny all of them. You can access these settings at any time and also subsequently deselect cookies at any time in the footer area of our website.

ACCEPT ALL

Cookie Overview

We use the following categories of cookies and related technologies to enhance your experience, show you personalized content, and analyze performance and traffic on our website. We respect your right to privacy and accordingly you can chose to not allow some types of cookies (and related technologies). Click on the different category sliders and change our default settings to manage your cookie settings.

For more information on the specific cookies/related technologies we use and on how we use these, please see section 15 E. of our Privacy and Cookie Policy.

ABSOLUTELY NECESSARY

Authentication cookies we use are required to run our services … Cookies are required: Link

FUNCTIONAL AND MARKETING COOKIES

These cookies collect anonymous data and allow us to optimize our website and user experience. These cookies are listed here:

ANALYTICS

Help us to understand how visitors interact with our services, enables us to analyze and improve our services (also through third party analytics).