TheJimmy Posted February 12, 2017 Share Posted February 12, 2017 When I try to join my singleplayer-galaxy the game says "Connection to 127.0.0.1:27000 failed. Server unreachable." The save worked for days now and i didn't install/deinstall anything. The game/PC never crashed so there is no reason why the save should get corrupted. PC Specs: OS: Windows 7 Professional 64-bit CPU: Intel Core i5-4670K Graphics NVIDIA GeForce GTX 770 Clientlog Sun Feb 12 16:27:47 2017| Client started: "C:\Program Files (x86)\Steam\steamapps\common\Avorion\bin\Avorion.exe" "--serverpath=bin/AvorionServer.exe" Sun Feb 12 16:27:47 2017| Enabled Traces: Sun Feb 12 16:27:47 2017| Client Beta 0.10.2 r7448, running on Windows 7. Sun Feb 12 16:27:47 2017| CPU: GenuineIntel 4 Cores Sun Feb 12 16:27:47 2017| Init Steamworks...Init Steamworks... ok Sun Feb 12 16:27:47 2017| Init Steamworks ok Sun Feb 12 16:27:47 2017| Init SDL2... ok Sun Feb 12 16:27:47 2017| Getting display mode... ok Sun Feb 12 16:27:47 2017| Current display mode: 1360 x 768 Sun Feb 12 16:27:47 2017| Creating settings... loading... setting language...setting language file "data/localization/deutsch.po" Sun Feb 12 16:27:47 2017| ok Sun Feb 12 16:27:47 2017| Creating client window...Detected 1 displays Sun Feb 12 16:27:47 2017| Display 0: x: 0, y: 0, w: 1360, h: 768 Sun Feb 12 16:27:47 2017| Using display 0 Sun Feb 12 16:27:47 2017| Creating window, x: 0, y: 0, w: 1360, h: 768... ok Sun Feb 12 16:27:47 2017| Creating GL context... ok Sun Feb 12 16:27:47 2017| Setting window mode WindowedSeamless... ok Sun Feb 12 16:27:47 2017| Creating client window ok Sun Feb 12 16:27:47 2017| Init rendering... starting rendering... initialize...OpenGL Context Information: Sun Feb 12 16:27:47 2017| Version: 4.5 Sun Feb 12 16:27:47 2017| VersionString: 4.5.0 NVIDIA 358.50 Sun Feb 12 16:27:47 2017| Vendor: NVIDIA Corporation Sun Feb 12 16:27:47 2017| Renderer: GeForce GTX 770/PCIe/SSE2 Sun Feb 12 16:27:47 2017| GLSL Version: 4.50 NVIDIA Sun Feb 12 16:27:47 2017| Init GLEW... ok Sun Feb 12 16:27:47 2017| Init Debug Message Callback... ok Sun Feb 12 16:27:47 2017| Set VSync... ok Sun Feb 12 16:27:47 2017| Secure BackBuffer... ok Sun Feb 12 16:27:47 2017| Init Canvas...Create canvas of size 2720 x 1536... ok Sun Feb 12 16:27:47 2017| Init Canvas ok Sun Feb 12 16:27:47 2017| Init Refraction Texture... ok Sun Feb 12 16:27:47 2017| Init Post Processing... ok Sun Feb 12 16:27:47 2017| Init Debug Renderers... ok Sun Feb 12 16:27:47 2017| Rendering initialized Sun Feb 12 16:27:47 2017| Init rendering ok Sun Feb 12 16:27:47 2017| Check problematic drivers... ok Sun Feb 12 16:27:47 2017| Init shader level... ok Sun Feb 12 16:27:47 2017| Init loading screen... ok Sun Feb 12 16:27:47 2017| Draw first loading screen...GL DBG: MEDIUM PERFORMANCE API 131218: Program/shader state performance warning: Fragment shader in program 6 is being recompiled based on GL state. Sun Feb 12 16:27:47 2017| GL DBG: MEDIUM PERFORMANCE API 131218: Program/shader state performance warning: Fragment shader in program 12 is being recompiled based on GL state. Sun Feb 12 16:27:47 2017| GL DBG: MEDIUM PERFORMANCE API 131218: Program/shader state performance warning: Fragment shader in program 15 is being recompiled based on GL state. Sun Feb 12 16:27:47 2017| GL DBG: MEDIUM PERFORMANCE API 131218: Program/shader state performance warning: Fragment shader in program 18 is being recompiled based on GL state. Sun Feb 12 16:27:47 2017| GL DBG: MEDIUM PERFORMANCE API 131218: Program/shader state performance warning: Fragment shader in program 21 is being recompiled based on GL state. Sun Feb 12 16:27:47 2017| GL DBG: MEDIUM PERFORMANCE API 131218: Program/shader state performance warning: Fragment shader in program 24 is being recompiled based on GL state. Sun Feb 12 16:27:47 2017| draw... ok Sun Feb 12 16:27:47 2017| Init SFX... ok Sun Feb 12 16:27:47 2017| Init Input... ok Sun Feb 12 16:27:47 2017| Init GameInput... ok Sun Feb 12 16:27:47 2017| Init Main Menu...GL DBG: MEDIUM PERFORMANCE API 131218: Program/shader state performance warning: Fragment shader in program 78 is being recompiled based on GL state. Sun Feb 12 16:27:48 2017| ok Sun Feb 12 16:27:48 2017| Init Music... ok Sun Feb 12 16:27:48 2017| Apply loaded settings... ok Sun Feb 12 16:27:48 2017| Client initialized Sun Feb 12 16:27:48 2017| Received stats and achievements from Steam Sun Feb 12 16:27:48 2017| GL DBG: MEDIUM PERFORMANCE API 131218: Program/shader state performance warning: Fragment shader in program 9 is being recompiled based on GL state. Sun Feb 12 16:27:48 2017| GL DBG: MEDIUM PERFORMANCE API 131218: Program/shader state performance warning: Fragment shader in program 27 is being recompiled based on GL state. Sun Feb 12 16:27:48 2017| GL DBG: MEDIUM PERFORMANCE API 131218: Program/shader state performance warning: Fragment shader in program 3 is being recompiled based on GL state. Sun Feb 12 16:27:48 2017| GL DBG: MEDIUM PERFORMANCE API 131218: Program/shader state performance warning: Fragment shader in program 102 is being recompiled based on GL state. Sun Feb 12 16:27:48 2017| GL DBG: MEDIUM PERFORMANCE API 131218: Program/shader state performance warning: Fragment shader in program 105 is being recompiled based on GL state. Sun Feb 12 16:28:28 2017| GL DBG: MEDIUM PERFORMANCE API 131218: Program/shader state performance warning: Fragment shader in program 108 is being recompiled based on GL state. Sun Feb 12 16:28:38 2017| setting language file "" Sun Feb 12 16:28:38 2017| Error loading language catalog: File doesn't exist: "" Sun Feb 12 16:28:38 2017| Waiting for Online polling threads Sun Feb 12 16:28:38 2017| Online polling threads finished Sun Feb 12 16:28:38 2017| Waiting for LAN polling threads Sun Feb 12 16:28:38 2017| LAN polling threads finished Sun Feb 12 16:28:43 2017| Starting server 'bin/AvorionServer.exe' with arguments '--galaxy-name Milchstraße --server-name TheJimmy's Server --port 27000 --public 0 --listed 0 --authentication 0 --exit-on-last-admin-logout --admin 76561198055483233 --use-steam-networking 1 --threads 3 ' Sun Feb 12 16:28:43 2017| GL DBG: MEDIUM PERFORMANCE API 131218: Program/shader state performance warning: Fragment shader in program 30 is being recompiled based on GL state. Sun Feb 12 16:28:43 2017| GL DBG: MEDIUM PERFORMANCE API 131218: Program/shader state performance warning: Fragment shader in program 33 is being recompiled based on GL state. Sun Feb 12 16:28:44 2017| Waiting for Online polling threads Sun Feb 12 16:28:44 2017| Online polling threads finished Sun Feb 12 16:28:44 2017| Waiting for LAN polling threads Sun Feb 12 16:28:44 2017| LAN polling threads finished Sun Feb 12 16:28:44 2017| remote address: ip, init: steam Sun Feb 12 16:28:44 2017| Connecting to server at 127.0.0.1:27000 Sun Feb 12 16:28:44 2017| Client UDP: Error receiving from 0.0.0.0, error: Eine vorhandene Verbindung wurde vom Remotehost geschlossen, received bytes: 0 Sun Feb 12 16:28:44 2017| Client UDP: Error receiving from 0.0.0.0, error: Eine vorhandene Verbindung wurde vom Remotehost geschlossen, received bytes: 0 Sun Feb 12 16:28:49 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:28:54 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:28:59 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:04 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:09 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:14 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:19 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:24 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:29 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:34 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:39 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:44 2017| UDP closed Sun Feb 12 16:29:44 2017| Client UDP: Connection closed Sun Feb 12 16:29:44 2017| remote address: ip, init: ip Sun Feb 12 16:29:44 2017| Client: attempting to connect to 127.0.0.1:27000 Sun Feb 12 16:29:44 2017| Client UDP: Error receiving from 0.0.0.0, error: Eine vorhandene Verbindung wurde vom Remotehost geschlossen, received bytes: 0 Sun Feb 12 16:29:44 2017| Client UDP: Error receiving from 0.0.0.0, error: Eine vorhandene Verbindung wurde vom Remotehost geschlossen, received bytes: 0 Sun Feb 12 16:29:44 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:44 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:45 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:45 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:45 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:45 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:46 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:46 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:46 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:46 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:47 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:47 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:47 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:48 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:48 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:48 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:48 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:49 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:49 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:49 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:49 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:50 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:50 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:50 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:51 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:51 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:51 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:51 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:52 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:52 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:52 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:52 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:53 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:53 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:53 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:53 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:54 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:54 2017| Client UDP: Error receiving from 0.0.0.0, error: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte, received bytes: 0 Sun Feb 12 16:29:54 2017| UDP closed Sun Feb 12 16:29:54 2017| Client UDP: Connection closed Sun Feb 12 16:29:54 2017| UDP closed Sun Feb 12 16:29:54 2017| Client UDP: Connection closed Sun Feb 12 16:29:54 2017| wanted to establish a connection to IP, but failed Sun Feb 12 16:31:02 2017| Exiting client. Sun Feb 12 16:31:02 2017| Exited client main loop. Sun Feb 12 16:31:02 2017| Waiting for Online polling threads Sun Feb 12 16:31:02 2017| Online polling threads finished Sun Feb 12 16:31:02 2017| Waiting for LAN polling threads Sun Feb 12 16:31:02 2017| LAN polling threads finished Sun Feb 12 16:31:02 2017| Stopping local server ... Serverlog Sun Feb 12 16:28:43 2017| Enabled Traces: Sun Feb 12 16:28:43 2017| Avorion server Beta 0.10.2 r7448 running on Windows 7 starting up in "C:\Users\JImmy\AppData\Roaming\Avorion\galaxies\Milchstraße" Sun Feb 12 16:28:43 2017| CPU: GenuineIntel 4 Cores Sun Feb 12 16:28:43 2017| name: TheJimmy's Server Sun Feb 12 16:28:43 2017| seed: JVHD9CFb90 Sun Feb 12 16:28:43 2017| port: 27000 Sun Feb 12 16:28:43 2017| max online players: 10 Sun Feb 12 16:28:43 2017| save interval: 600 Sun Feb 12 16:28:43 2017| broadcast interval: 5 Sun Feb 12 16:28:43 2017| max loaded sector time: 300 Sun Feb 12 16:28:43 2017| weak update: yes Sun Feb 12 16:28:43 2017| worker threads: 3 Sun Feb 12 16:28:43 2017| difficulty: Easy Sun Feb 12 16:28:43 2017| infiniteResources: no Sun Feb 12 16:28:43 2017| collision: 1 Sun Feb 12 16:28:43 2017| access list: Blacklist Sun Feb 12 16:28:43 2017| public: no Sun Feb 12 16:28:43 2017| authentication: no Sun Feb 12 16:28:43 2017| listed: no Sun Feb 12 16:28:43 2017| steam networking: yes Sun Feb 12 16:28:43 2017| server will exit once all admins logged out. Sun Feb 12 16:28:43 2017| administrators: 'admin' Sun Feb 12 16:28:43 2017| An exception occurred: DataStream access error: Accessed data exceeds buffer size: 0, offset: 0, access size: 4 Sun Feb 12 16:28:43 2017| I hope you can help me. Link to comment Share on other sites More sharing options...
Boxelware Team cepheni Posted February 12, 2017 Boxelware Team Share Posted February 12, 2017 Please try to rerun the server with the additional command "-t all" and send the resulting client log and galaxy (the whole directory would be best) to support@avorion.net. Link to comment Share on other sites More sharing options...
Triu Posted February 14, 2017 Share Posted February 14, 2017 I meant to reply to this yesterday, sorry got busy, if this happens to you again try going into processes (ctrl+alt+delete) and close avorionserver.exe. I've had this happen a few times as well and couldn't load a single player game even after restarting the game, this should fix it. Link to comment Share on other sites More sharing options...
Coovargo Posted February 14, 2017 Share Posted February 14, 2017 If you're going to end avorionserver.exe leave it sit for 60 seconds first to remove any chance of corrupting the file. Even still, it's recommended you back up the server's save folder daily at least. Link to comment Share on other sites More sharing options...
LogicSocket Posted March 1, 2017 Share Posted March 1, 2017 This happens constantly with my single player game, server just times out and i have to manually shut it down. needs fixed. Link to comment Share on other sites More sharing options...
thedamngod Posted March 1, 2017 Share Posted March 1, 2017 You should add some logs to your post, LogicSocket. More information is always a good thing :) And/or do this: Please try to rerun the server with the additional command "-t all" and send the resulting client log and galaxy (the whole directory would be best) to support@avorion.net. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now