Server will auto-shutdown / fresh install on fresh system (vps server))

Post here your questions about SFS2X. Here we discuss all server-side matters. For client API questions see the dedicated forums.

Moderators: Lapo, Bax

neontree
Posts: 41
Joined: 19 Sep 2007, 20:00
Location: Poland

Server will auto-shutdown / fresh install on fresh system (vps server))

Postby neontree » 18 Aug 2019, 15:08

Hello,
I'm trying to solve this problem for several hours. No luck / no idea :/
I had to reinstall my VPS server so I'm installing SFS on a fresh CentOS 6.
The logs show that SFS is shutting down just after launch (logs below).

I've followed suggestions from post: https://www.smartfoxserver.com/forums/viewtopic.php?t=20138
like checking the ports and installing a fresh copy...

netstat is not showing any of the ports I used (so 9933 and 8080 should be fine, and those worked before in SFS 2.12..),
also I tried installing SFS 2.13 with and without latest patch, same result either way.

I'd be glad to try if SFS 2.12... still works but I don't have the installation files, cant find them online.

LOGS:

Code: Select all

16:48:14,402 INFO  [main] v2.SmartFoxServer     - Boot sequence starts...
16:48:15,229 INFO  [main] core.SFSEventManager     - AnonymousService-1 initialized
16:48:15,262 INFO  [main] impl.DefaultFileReplicator     - Using "/tmp/vfs_cache" as temporary files store.
16:48:15,353 INFO  [main] v2.SmartFoxServer     - License loaded:

==========================================
LICENSE DETAILS
------------------------------------------
Type            : Community Edition
Max users       : 100
==========================================

16:48:15,354 INFO  [main] managers.SFSBannedUserStorage     - BanUserStorage initialized
16:48:15,373 INFO  [main] managers.SFSBannedUserManager     - BanUser data loaded: 0 records.
16:48:15,380 INFO  [main] v2.SmartFoxServer     - Protocol Type is: BINARY
16:48:15,384 INFO  [main] config.DefaultConfigLoader     - Loading: zones/BasicExamples.zone.xml
16:48:15,427 INFO  [main] managers.SFSZoneManager     -

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
 >> Zone: BasicExamples
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

16:48:15,465 INFO  [main] managers.SFSRoomManager     - Room created: { Zone: BasicExamples }, [ Room: The Lobby, Id: 0, Group: default, isGame: false ], type = SFSRoom
16:48:15,475 INFO  [main] managers.SFSRoomManager     - Room created: { Zone: --=={{{ AdminZone }}}==-- }, [ Room: AdminRoom, Id: 1, Group: default, isGame: false ], type = SFSRoom
16:48:15,527 INFO  [main] core.AdminToolService     - AdminTool Service started
16:48:15,597 INFO  [SFSWorker:Sys:1] v2.SmartFoxServer     - Listening Sockets: { ***IP***:9933, (Tcp) } { ***IP***:9933, (Udp) }
16:48:15,599 INFO  [SFSWorker:Sys:1] v2.SmartFoxServer     - 
 _____ _____ _____    ___ __ __
|   __|   __|   __|  |_  |  |  |
|__   |   __|__   |  |  _|-   -|
|_____|__|  |_____|  |___|__|__|                                         
 _____ _____ _____ ____  __ __
| __  |   __|  _  |    \|  |  |
|    -|   __|     |  |  |_   _|
|__|__|_____|__|__|____/  |_| 
[ 2.13.0 ]

16:48:15,599 INFO  [SFSWorker:Sys:1] v2.SmartFoxServer     - SmartFoxServer 2X (2.13.0) READY!
16:48:17,066 INFO  [main] v3.SessionFilter     - BlueBox-2X Service (3.1.0) READY.
java.lang.reflect.InvocationTargetException
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:498)
   at org.eclipse.jetty.start.Main.invokeMain(Main.java:214)
   at org.eclipse.jetty.start.Main.start(Main.java:457)
   at org.eclipse.jetty.start.Main.main(Main.java:75)
   at com.smartfoxserver.v2.http.JettyServer.start(JettyServer.java:35)
   at com.smartfoxserver.v2.SmartFoxServer.start(SmartFoxServer.java:321)
   at com.smartfoxserver.v2.Main.main(Main.java:14)
Caused by: java.net.BindException: Address already in use
   at sun.nio.ch.Net.bind0(Native Method)
   at sun.nio.ch.Net.bind(Net.java:433)
   at sun.nio.ch.Net.bind(Net.java:425)
   at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
   at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
   at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:317)
   at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
   at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:235)
   at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
   at org.eclipse.jetty.server.Server.doStart(Server.java:390)
   at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
   at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1510)
   at java.security.AccessController.doPrivileged(Native Method)
   at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1435)
   ... 10 more

Usage: java -jar start.jar [options] [properties] [configs]
       java -jar start.jar --help  # for more information
16:48:17,914 INFO  [Thread-0] managers.SFSZoneManager     - BuddyList saveAll...
16:48:17,918 WARN  [SFS2X ShutdownHook] core.SFSShutdownHook     - SFS2X is shutting down. The process may take a few seconds...
16:48:17,925 INFO  [Thread-1] managers.SFSBannedUserManager     - BanUser data saved.
]0;root@***IP***:/home/SFS/SmartFoxServer_2X/SFS2X[root@vps136923 SFS2X]#
Last edited by neontree on 25 Aug 2019, 19:13, edited 1 time in total.
---
User avatar
Lapo
Site Admin
Posts: 23026
Joined: 21 Mar 2005, 09:50
Location: Italy

Re: Server will auto-shutdown / fresh install on fresh system (vps server))

Postby Lapo » 18 Aug 2019, 18:58

Hi,
this error:
java.net.BindException: Address already in use

means that there's another service using the HTTP ports (by default 8080 and 8443).

Either there's another instance of SFS2X already running, or another service is indeed using those ports. I recommend checking which is which.

Let us know
Lapo
--
gotoAndPlay()
...addicted to flash games
neontree
Posts: 41
Joined: 19 Sep 2007, 20:00
Location: Poland

Re: Server will auto-shutdown / fresh install on fresh system (vps server))

Postby neontree » 18 Aug 2019, 19:20

Could you please examine this netstat -lnptu result? I only see 8443 in use,
but in my config I don't use it.
In server.xml I set default 9933 for TCP, UDP and adminTcpPort,
or I've tried 8080 for adminTcpPort, in both cases no luck.

Code: Select all

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name   
tcp        0      0 127.0.0.1:12768             0.0.0.0:*                   LISTEN      939/psa-pc-remote   
tcp        0      0 127.0.0.1:3306              0.0.0.0:*                   LISTEN      1243/mysqld         
tcp        0      0 0.0.0.0:587                 0.0.0.0:*                   LISTEN      925/master         
tcp        0      0 0.0.0.0:8880                0.0.0.0:*                   LISTEN      1336/sw-cp-server   
tcp        0      0 ***myIP***:80            0.0.0.0:*                   LISTEN      973/nginx           
tcp        0      0 0.0.0.0:465                 0.0.0.0:*                   LISTEN      925/master         
tcp        0      0 ***myIP***:53            0.0.0.0:*                   LISTEN      682/named           
tcp        0      0 127.0.0.1:53                0.0.0.0:*                   LISTEN      682/named           
tcp        0      0 0.0.0.0:22                  0.0.0.0:*                   LISTEN      764/sshd           
tcp        0      0 0.0.0.0:25                  0.0.0.0:*                   LISTEN      925/master         
tcp        0      0 127.0.0.1:953               0.0.0.0:*                   LISTEN      682/named           
tcp        0      0 127.0.0.1:12346             0.0.0.0:*                   LISTEN      925/master         
tcp        0      0 0.0.0.0:8443                0.0.0.0:*                   LISTEN      1336/sw-cp-server   
tcp        0      0 ***myIP***:443           0.0.0.0:*                   LISTEN      973/nginx           
tcp        0      0 :::993                      :::*                        LISTEN      811/couriertcpd     
tcp        0      0 :::995                      :::*                        LISTEN      839/couriertcpd     
tcp        0      0 :::7080                     :::*                        LISTEN      959/httpd           
tcp        0      0 :::7081                     :::*                        LISTEN      959/httpd           
tcp        0      0 :::106                      :::*                        LISTEN      775/xinetd         
tcp        0      0 :::587                      :::*                        LISTEN      925/master         
tcp        0      0 :::110                      :::*                        LISTEN      822/couriertcpd     
tcp        0      0 :::143                      :::*                        LISTEN      799/couriertcpd     
tcp        0      0 :::8880                     :::*                        LISTEN      1336/sw-cp-server   
tcp        0      0 2001:41d0:52:cff::15f8:80   :::*                        LISTEN      973/nginx           
tcp        0      0 :::465                      :::*                        LISTEN      925/master         
tcp        0      0 :::21                       :::*                        LISTEN      775/xinetd         
tcp        0      0 :::53                       :::*                        LISTEN      682/named           
tcp        0      0 :::22                       :::*                        LISTEN      764/sshd           
tcp        0      0 :::25                       :::*                        LISTEN      925/master         
tcp        0      0 :::8443                     :::*                        LISTEN      1336/sw-cp-server   
tcp        0      0 2001:41d0:52:cff::15f8:443  :::*                        LISTEN      973/nginx           
udp        0      0 ***myIP***:53            0.0.0.0:*                               682/named           
udp        0      0 127.0.0.1:53                0.0.0.0:*                               682/named           
udp        0      0 :::53                       :::*                                    682/named         
---
User avatar
Lapo
Site Admin
Posts: 23026
Joined: 21 Mar 2005, 09:50
Location: Italy

Re: Server will auto-shutdown / fresh install on fresh system (vps server))

Postby Lapo » 19 Aug 2019, 09:23

Port 8443 is used by SFS2X for HTTPS so it does collide with your other service bound on the same port.
If you cannot change the other service's HTTPS port then you'll have to configure SFS2X to use a different value.

You can edit the file under SFS2X/lib/jetty/start.d/ssl.ini

Hope it helps
Lapo

--

gotoAndPlay()

...addicted to flash games
neontree
Posts: 41
Joined: 19 Sep 2007, 20:00
Location: Poland

Re: Server will auto-shutdown / fresh install on fresh system (vps server))

Postby neontree » 19 Aug 2019, 10:40

Thanks, it kinda moved, but not all the way :).
I've changed port in ssl.ini to 8003 (also tried 1288, just picking at random...)
and in configuration I set default 9933 for TCP,UDP and admin TCP.
The result is that server starts but Putty console is hang at one point (logs below).

While Putty is open I'm able to connect with admin tool, but SFS shuts down as soon as I close the Putty.

When I try any other port for adminTCP I'm not even able to connect with admin tool.
Could you please suggest some port numbers that should work in this case?

Code: Select all

12:38:08,355 INFO  [main] v2.SmartFoxServer     - Boot sequence starts...
12:38:09,111 INFO  [main] core.SFSEventManager     - AnonymousService-1 initialized
12:38:09,152 INFO  [main] impl.DefaultFileReplicator     - Using "/tmp/vfs_cache" as temporary files store.
12:38:09,247 INFO  [main] v2.SmartFoxServer     - License loaded:

==========================================
LICENSE DETAILS
------------------------------------------
Type            : Community Edition
Max users       : 100
==========================================

12:38:09,248 INFO  [main] managers.SFSBannedUserStorage     - BanUserStorage initialized
12:38:09,267 INFO  [main] managers.SFSBannedUserManager     - BanUser data loaded: 0 records.
12:38:09,276 INFO  [main] v2.SmartFoxServer     - Protocol Type is: BINARY
12:38:09,281 INFO  [main] config.DefaultConfigLoader     - Loading: zones/BasicExamples.zone.xml
12:38:09,332 INFO  [main] managers.SFSZoneManager     -

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
 >> Zone: BasicExamples
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

12:38:09,371 INFO  [main] managers.SFSRoomManager     - Room created: { Zone: BasicExamples }, [ Room: The Lobby, Id: 0, Group: default, isGame: false ], type = SFSRoom
12:38:09,382 INFO  [main] managers.SFSRoomManager     - Room created: { Zone: --=={{{ AdminZone }}}==-- }, [ Room: AdminRoom, Id: 1, Group: default, isGame: false ], type = SFSRoom
12:38:09,440 INFO  [main] core.AdminToolService     - AdminTool Service started
12:38:09,513 INFO  [SFSWorker:Sys:1] v2.SmartFoxServer     - Listening Sockets: { ***IP***:9933, (Tcp) } { ***IP***:9933, (Udp) }
12:38:09,515 INFO  [SFSWorker:Sys:1] v2.SmartFoxServer     - 
 _____ _____ _____    ___ __ __
|   __|   __|   __|  |_  |  |  |
|__   |   __|__   |  |  _|-   -|
|_____|__|  |_____|  |___|__|__|                                         
 _____ _____ _____ ____  __ __
| __  |   __|  _  |    \|  |  |
|    -|   __|     |  |  |_   _|
|__|__|_____|__|__|____/  |_| 
[ 2.13.0 ]

12:38:09,515 INFO  [SFSWorker:Sys:1] v2.SmartFoxServer     - SmartFoxServer 2X (2.13.0) READY!
12:38:10,981 INFO  [main] v3.SessionFilter     - BlueBox-2X Service (3.1.0) READY.

--- THIS IS WHERE IT STOPS ---

12:38:23,761 INFO  [SocketReader] sessions.DefaultSessionManager     - Session created: { Id: 1, Type: DEFAULT, Logged: No, IP: ***IP***:50788 } on Server port: 9933 <---> 50788
12:38:23,851 INFO  [SFSWorker:Ext:4] api.SFSApi     - User login: { Zone: --=={{{ AdminZone }}}==-- }, ( User Name: sfsadmin, Id: 0, Priv: 0, Sess: ***IP***:50788 ) , Type: Flash Desktop:WIN 19,0,0,169
12:38:23,864 INFO  [SFSWorker:Ext:1] api.SFSApi     - Room joined: [ Room: AdminRoom, Id: 1, Group: default, isGame: false ], { Zone: --=={{{ AdminZone }}}==-- }, ( User Name: sfsadmin, Id: 0, Priv: 0, Sess: ***IP***:50788 ) , asSpect: false
12:39:55,252 INFO  [SocketReader] sessions.DefaultSessionManager     - Session created: { Id: 2, Type: DEFAULT, Logged: No, IP: ***IP***:50828 } on Server port: 9933 <---> 50828
12:39:55,342 INFO  [SFSWorker:Sys:3] api.SFSApi     - Bad login request, Zone: NAME does not exist. Requested by: { Id: 2, Type: DEFAULT, Logged: No, IP: ***IP***:50828 }
12:40:00,759 INFO  [SocketReader] sessions.DefaultSessionManager     - Session removed: { Id: 2, Type: DEFAULT, Logged: No, IP: ***IP***:50828 }
Last edited by neontree on 25 Aug 2019, 19:15, edited 1 time in total.
---
User avatar
Lapo
Site Admin
Posts: 23026
Joined: 21 Mar 2005, 09:50
Location: Italy

Re: Server will auto-shutdown / fresh install on fresh system (vps server))

Postby Lapo » 19 Aug 2019, 14:40

Hi,
you need to launch SFS2X as a service, otherwise it will shutdown when you close the remote session.
The command to do it is:

Code: Select all

./sfs2x-service start


For more details check the installation docs here:
http://docs2x.smartfoxserver.com/Gettin ... tall-linux

Cheers
Lapo

--

gotoAndPlay()

...addicted to flash games
neontree
Posts: 41
Joined: 19 Sep 2007, 20:00
Location: Poland

Re: Server will auto-shutdown / fresh install on fresh system (vps server))

Postby neontree » 20 Aug 2019, 17:29

omg :oops:

Nailed it! THANK YOU!
---
croftie
Posts: 49
Joined: 24 Jul 2013, 08:35
Location: Algarve Portugal
Contact:

Re: Server will auto-shutdown / fresh install on fresh system (vps server))

Postby croftie » 10 Mar 2021, 18:00

Having the same problem but with migration from 2.13 to 2.17 (Tomcat).

Client will be using websockets / HTML5 javascript.

There are no other instances of SFS or tomcat running.

1) Fresh install into new directory and old directory renamed.
2) Configuration files files copied to new locations as per migration instructions
3) SSL in keystore saved in apache-tomcat/conf
4) server.xml has the following connector entries

Code: Select all

<Connector connectionTimeout="20000" port="8080" protocol="HTTP/1.1" redirectPort="8443"/>
   <Connector SSLEnabled="true" clientAuth="false" keystoreFile="lib/apache-tomcat/conf/keystore.jks" keystorePass="password" maxThreads="200" port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="https" secure="true" sslProtocol="TLS"/>

5) starting SFS always results in the following exception

Code: Select all

17:18:37,295 INFO  [main] v2.SmartFoxServer     - Boot sequence starts...
17:18:38,070 INFO  [main] core.SFSEventManager     - SFSEventManager initialized
17:18:38,105 INFO  [main] impl.DefaultFileReplicator     - Using "/tmp/vfs_cache" as temporary files store.
17:18:38,188 INFO  [main] v2.SmartFoxServer     - License loaded:

==========================================
LICENSE DETAILS
------------------------------------------
Type            : Community Edition
Max users       : 100
==========================================

17:18:38,190 INFO  [main] managers.SFSBannedUserStorage     - BanUserStorage initialized
17:18:38,213 INFO  [main] managers.SFSBannedUserManager     - BanUser data loaded: 0 records.
17:18:38,225 INFO  [main] v2.SmartFoxServer     - Protocol Type is: BINARY
17:18:38,229 INFO  [main] config.DefaultConfigLoader     - Loading: zones/CasinoFloorStage.zone.xml
17:18:38,310 INFO  [main] managers.SFSZoneManager     -

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
 >> Zone: CasinoFloorStage
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

17:18:38,752 INFO  [main] managers.SFSRoomManager     - Room created: { Zone: CasinoFloorStage }, [ Room: Lobby, Id: 0, Group: default, isGame: false ], type = SFSRoom
17:18:38,753 INFO  [main] managers.SFSRoomManager     - Room created: { Zone: CasinoFloorStage }, [ Room: ConferenceLobby, Id: 1, Group: default, isGame: false ], type = SFSRoom
17:18:38,761 INFO  [main] Extensions     - {CasinoFloorStage}: Casino Floor Extension starts here
17:18:38,966 INFO  [main] managers.SFSRoomManager     - Room created: { Zone: --=={{{ AdminZone }}}==-- }, [ Room: AdminRoom, Id: 2, Group: default, isGame: false ], type = SFSRoom
17:18:39,130 INFO  [main] core.AdminToolService     - AdminTool Service started
17:18:39,132 INFO  [main] managers.SFSPostOffice     - PostOffice service started
17:18:39,323 INFO  [SFSWorker:Sys:1] v2.SmartFoxServer     - Listening Sockets: { 0.0.0.0:9933, (Tcp) } { 127.0.0.1:9933, (Udp) }
17:18:39,333 INFO  [SFSWorker:Sys:1] v2.SmartFoxServer     - 
 _____ _____ _____    ___ __ __
|   __|   __|   __|  |_  |  |  |
|__   |   __|__   |  |  _|-   -|
|_____|__|  |_____|  |___|__|__|                                         
 _____ _____ _____ ____  __ __
| __  |   __|  _  |    \|  |  |
|    -|   __|     |  |  |_   _|
|__|__|_____|__|__|____/  |_| 
[ 2.17.0 ]

17:18:39,333 INFO  [SFSWorker:Sys:1] v2.SmartFoxServer     - SmartFoxServer 2X (2.17.0) READY!
10-Mar-2021 17:18:40.567 SEVERE [TomcatRunner] org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to initialize component [Connector[HTTP/1.1-8443]]
   org.apache.catalina.LifecycleException: Protocol handler initialization failed
      at org.apache.catalina.connector.Connector.initInternal(Connector.java:983)
      at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
      at org.apache.catalina.core.StandardService.initInternal(StandardService.java:533)
      at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
      at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:1059)
      at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
      at org.apache.catalina.startup.Catalina.load(Catalina.java:584)
      at org.apache.catalina.startup.Catalina.load(Catalina.java:607)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:498)
      at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:304)
      at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:474)
      at com.smartfoxserver.v2.http.TomcatServer.start(TomcatServer.java:43)
      at com.smartfoxserver.v2.SmartFoxServer$1.run(SmartFoxServer.java:343)
      at java.lang.Thread.run(Thread.java:748)
   Caused by: java.net.BindException: Address already in use
      at sun.nio.ch.Net.bind0(Native Method)
      at sun.nio.ch.Net.bind(Net.java:433)
      at sun.nio.ch.Net.bind(Net.java:425)
      at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
      at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
      at org.apache.tomcat.util.net.NioEndpoint.initServerSocket(NioEndpoint.java:230)
      at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:213)
      at org.apache.tomcat.util.net.AbstractEndpoint.bindWithCleanup(AbstractEndpoint.java:1124)
      at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:1137)
      at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:574)
      at org.apache.coyote.http11.AbstractHttp11Protocol.init(AbstractHttp11Protocol.java:74)
      at org.apache.catalina.connector.Connector.initInternal(Connector.java:980)
      ... 16 more
10-Mar-2021 17:18:57.722 WARNING [TomcatRunner] org.apache.catalina.util.SessionIdGeneratorBase.createSecureRandom Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [14,278] milliseconds.
17:18:57,728 INFO  [TomcatRunner] bluebox.BBSessionFilter     - BlueBox Service (4.0.2) READY.
10-Mar-2021 17:46:18.364 WARNING [http-nio-8080-exec-7] org.apache.catalina.realm.LockOutRealm.filterLockedAccounts An attempt was made to authenticate the locked user [admin]
10-Mar-2021 17:46:19.249 WARNING [http-nio-8080-exec-1] org.apache.catalina.realm.LockOutRealm.filterLockedAccounts An attempt was made to authenticate the locked user [tomcat]
10-Mar-2021 17:46:20.133 WARNING [http-nio-8080-exec-7] org.apache.catalina.realm.LockOutRealm.filterLockedAccounts An attempt was made to authenticate the locked user [root]


6) https://serveraddress:8443/manager/html ... 3CA050EF75
is successful and ssl cert is correct

not sure if I need to change the port numbers for the manager to allow SFS to use 8443 and 8080 and if so how to do it?

Any help gratefully received
User avatar
Lapo
Site Admin
Posts: 23026
Joined: 21 Mar 2005, 09:50
Location: Italy

Re: Server will auto-shutdown / fresh install on fresh system (vps server))

Postby Lapo » 11 Mar 2021, 08:21

Hi,
the error is telling you that there's another server already running and using port 8443.
I think you already have an SFS2X instance running, and what you see is the result of trying to run a second instance.

Please check it via the OS process monitor and let us know.

Cheers
Lapo

--

gotoAndPlay()

...addicted to flash games
croftie
Posts: 49
Joined: 24 Jul 2013, 08:35
Location: Algarve Portugal
Contact:

Re: Server will auto-shutdown / fresh install on fresh system (vps server))

Postby croftie » 11 Mar 2021, 08:39

As stated above, there is no other instance of SFS running. Have tested with ./sfs2x-service status in both old and new directories and the daemon is reported as stopped in both cases.

There is no shell instance running either

sudo netstat -anp tcp | grep 8443 give no result when sfs is stopped

and tcp6 0 0 :::8443 :::* LISTEN 7118/java

when the sfs shell is running

the PID process is shown to be

ubuntu 7118 1.3 17.1 2296296 173964 pts/0 Sl+ 08:46 0:30 ../jre/bin/java

which is the Tomcat instance just launched

It seems to be conflicting with itself!
User avatar
Lapo
Site Admin
Posts: 23026
Joined: 21 Mar 2005, 09:50
Location: Italy

Re: Server will auto-shutdown / fresh install on fresh system (vps server))

Postby Lapo » 11 Mar 2021, 10:40

croftie wrote:It seems to be conflicting with itself!

That doesn't sound plausible :)
I think this might be due to the changes applied to the SFS2X configuration. My suggestion is to:

1-> install a brand new copy of SFS2X 2.17 in a separate folder
2-> make sure no other copies of SFS2X are running
3-> run the newly installed SFS2X without touching the config

This should work 100% of the times.
If it does then I'd recommend to trace back to the changes you've made to the config previously and test them one by one to find the culprit.

Cheers
Lapo

--

gotoAndPlay()

...addicted to flash games
croftie
Posts: 49
Joined: 24 Jul 2013, 08:35
Location: Algarve Portugal
Contact:

Re: Server will auto-shutdown / fresh install on fresh system (vps server))

Postby croftie » 11 Mar 2021, 16:15

solved by doing clean install and then manually re-constituting the config/server.xml

Copying the server.xml file from the earlier version causes the problem (not sure which parts)

So to be clear when upgrading from jetty version to tomcat version

1. you can create a new version in a new directory and copy the zones files and the extensions files and the data files but not the server.xml file in the config directory.
2. you can copy the <administrators> and <mailer> sections from the old server.xml in config and paste to the new
3. if you need the DB driver, copy that into the lib folder
4. use the administration tool to upload the jks file for ssl
User avatar
Lapo
Site Admin
Posts: 23026
Joined: 21 Mar 2005, 09:50
Location: Italy

Re: Server will auto-shutdown / fresh install on fresh system (vps server))

Postby Lapo » 12 Mar 2021, 08:50

Excellent,
Cheers
Lapo

--

gotoAndPlay()

...addicted to flash games

Return to “SFS2X Questions”

Who is online

Users browsing this forum: Stevenor and 61 guests