API tools faq
paste
Advertisement
Guest User

Server Log before Crash

a guest
Aug 22nd, 2019
77
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 16.43 KB | None | 0 0
raw download clone embed print report
  1. Main Thread ID: 139880898254784
  2. Enabled Traces:
  3. Avorion server Beta 0.25.2 r16533 a8ef95d6c58b running on Ubuntu 14.04.5 LTS starting up in "/home/sid_1301248/avorionStable/galaxies/avorion_galaxy"
  4. CPU: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz 8 Cores
  5. RAM: 31GB
  6. Initializing networking...
  7. Starting game server on ip 85.131.208.9, 1434701833
  8. Server version, as listed publicly: 0.25.2.16533
  9. Game Port: 27000
  10. Steam Port: 27021
  11. Steam Query Port: 27020
  12. Query Port: 27003
  13.  
  14. Steam Networking initialized.
  15. Warning: No RCON password set. RCON disabled.
  16. Found 0 mods in "/home/sid_1301248/avorionStable/galaxies/avorion_galaxy/modconfig.lua".
  17. Synchronizing workshop items, waiting for steam response ...
  18. Server failed to connect to Steam
  19. Server failed to connect to Steam
  20. Server failed to connect to Steam
  21. Server failed to connect to Steam
  22. Server connected to Steam successfully
  23. Server is VAC Secure!
  24. Game Server Steam ID: 90128455658426371
  25. Downloading missing workshop items to '/home/sid_1301248/avorionStable/galaxies/avorion_galaxy/workshop'
  26. name: DJ_Avorion
  27. seed: XxI81wDM5z
  28. port: 27000
  29. ip: 85.131.208.9
  30. max online players: 10
  31. save interval: 300
  32. broadcast interval: 5
  33. max loaded sector time: 300
  34. weak update: yes
  35. worker threads: 1
  36. generator threads: 2
  37. script background threads: 2
  38. difficulty: Normal
  39. infiniteResources: no
  40. collision: 0.5
  41. access list: Blacklist
  42. public: yes
  43. authentication: yes
  44. listed: no
  45. steam networking: yes
  46. send crash reports: yes
  47. administrators: 'admin'
  48. Initializing sector database...
  49. Starting thread [Create Sectors WorkerPool Thread 0]...
  50. Started thread [Create Sectors WorkerPool Thread 0] with id 139880823875328
  51. Starting thread [Create Sectors WorkerPool Thread 1]...
  52. Started thread [Create Sectors WorkerPool Thread 1] with id 139880815482624
  53. Starting thread [Save Sectors WorkerPool Thread 0]...
  54. Started thread [Save Sectors WorkerPool Thread 0] with id 139880806446848
  55. Initializing faction database...
  56. Starting thread [Save Factions WorkerPool Thread 0]...
  57. Started thread [Save Factions WorkerPool Thread 0] with id 139880797411072
  58. Initializing galaxy...
  59. Starting up 1 worker threads...
  60. Starting thread [Game WorkerPool Thread 0]...
  61. Started thread [Game WorkerPool Thread 0] with id 139880788375296
  62. Starting up 2 script background threads...
  63. Starting thread [Lua WorkerPool Thread 0]...
  64. Started thread [Lua WorkerPool Thread 0] with id 139879904179968
  65. Starting thread [Lua WorkerPool Thread 1]...
  66. Started thread [Lua WorkerPool Thread 1] with id 139879895787264
  67. Thread [Lua WorkerPool Thread 0] with id 139879904179968 exiting...
  68. Thread [Lua WorkerPool Thread 0] with id 139879904179968 exited
  69. Thread [Lua WorkerPool Thread 1] with id 139879895787264 exiting...
  70. Thread [Lua WorkerPool Thread 1] with id 139879895787264 exited
  71. Starting thread [Lua WorkerPool Thread 2]...
  72. Started thread [Lua WorkerPool Thread 2] with id 139879895787264
  73. Starting thread [Lua WorkerPool Thread 3]...
  74. Started thread [Lua WorkerPool Thread 3] with id 139879904179968
  75. Loading jumping entities...
  76. Loading groups...
  77. Galaxy initialized.
  78. Loading global variables...
  79. Setting startup script...
  80. Starting thread [Input Commands]...
  81. Started thread [Input Commands] with id 139879887394560
  82. Server has been running for 0 seconds in total, and 0 without pauses.
  83. Server startup complete.
  84. Starting thread [UDP Connection Receive]...
  85. Started thread [UDP Connection Receive] with id 139879879001856
  86. Starting thread [HangDetector]...
  87. Started thread [HangDetector] with id 139879870609152
  88. Starting thread [Steam Networking Receive]...
  89. Started thread [Steam Networking Receive] with id 139879862216448
  90. OnP2PSessionRequest from 76561197994862441
  91. Steam authentication confirmed for 76561197994862441
  92. Authentication successful for 76561197994862441
  93. Starting thread [Communicator Sending WorkerPool Thread 0]...
  94. Started thread [Communicator Sending WorkerPool Thread 0] with id 139879434417920
  95. Starting thread [Communicator Networking WorkerPool Thread 0]...
  96. Started thread [Communicator Networking WorkerPool Thread 0] with id 139879426025216
  97. Connection to client established
  98. Connection accepted from 185.22.143.238:0
  99. SectorDatabase: Loading Sector (83:181)
  100. <Server> Player Complex joined the galaxy
  101. Player logged in: Complex, index: 1
  102. scheduled save for sector (83:181), 0x7f3860000c70, entities: 134
  103. saving sector (83:181)
  104. sector (83:181) saved to "/home/sid_1301248/avorionStable/galaxies/avorion_galaxy/sectors/83_181"
  105. player events roughly every 16.55 minutes
  106. Player Complex moved to sector (83:181) server time taken for change: 3ms
  107. scheduled save for sector (83:181), 0x7f3860000c70, entities: 134
  108. saving sector (83:181)
  109. sector (83:181) saved to "/home/sid_1301248/avorionStable/galaxies/avorion_galaxy/sectors/83_181"
  110. Player Complex in (83:181) has no script number '12'.
  111. SectorDatabase: Loading Sector (35:448)
  112. SectorDatabase: Loading Sector (35:449)
  113. SectorDatabase: Loading Sector (53:285)
  114. scheduled save for sector (35:449), 0x7f38610fff20, entities: 1489
  115. saving sector (35:449)
  116. SectorDatabase: Loading Sector (83:378)
  117. scheduled save for sector (35:448), 0x7f385c000b60, entities: 1468
  118. sector (35:449) saved to "/home/sid_1301248/avorionStable/galaxies/avorion_galaxy/sectors/35_449"
  119. saving sector (35:448)
  120. sector (35:448) saved to "/home/sid_1301248/avorionStable/galaxies/avorion_galaxy/sectors/35_448"
  121. scheduled save for sector (53:285), 0x7f38604c70b0, entities: 558
  122. saving sector (53:285)
  123. sector (53:285) saved to "/home/sid_1301248/avorionStable/galaxies/avorion_galaxy/sectors/53_285"
  124. scheduled save for sector (83:378), 0x7f385c44ee50, entities: 1220
  125. saving sector (83:378)
  126. sector (83:378) saved to "/home/sid_1301248/avorionStable/galaxies/avorion_galaxy/sectors/83_378"
  127. <> The Nav-Computer is calculating the jump route. Please stand by.
  128. Creating sector at (81:181)
  129. scheduled save for sector (81:181), 0x7f38637d1860, entities: 0
  130. saving sector (81:181)
  131. sector (81:181) saved to "/home/sid_1301248/avorionStable/galaxies/avorion_galaxy/sectors/81_181"
  132. <> Jump route calculated.
  133. Player Complex moved to sector (81:181)from (83:181) server time taken for change: 0ms
  134. scheduled save for sector (81:181), 0x7f38637d1860, entities: 3
  135. saving sector (81:181)
  136. sector (81:181) saved to "/home/sid_1301248/avorionStable/galaxies/avorion_galaxy/sectors/81_181"
  137. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  138. Crash report sent successfully!
  139.  
  140. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  141. Crash report sent successfully!
  142.  
  143. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  144. Crash report sent successfully!
  145.  
  146. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  147. Crash report sent successfully!
  148.  
  149. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  150. Crash report sent successfully!
  151.  
  152. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  153. Crash report sent successfully!
  154.  
  155. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  156. Crash report sent successfully!
  157.  
  158. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  159. Crash report sent successfully!
  160.  
  161. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  162. Crash report sent successfully!
  163.  
  164. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  165. Crash report sent successfully!
  166.  
  167. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  168. Crash report sent successfully!
  169.  
  170. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  171. Crash report sent successfully!
  172.  
  173. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  174. Crash report sent successfully!
  175.  
  176. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  177. Crash report sent successfully!
  178.  
  179. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  180. Crash report sent successfully!
  181.  
  182. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  183. Crash report sent successfully!
  184.  
  185. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  186. Crash report sent successfully!
  187.  
  188. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  189. Crash report sent successfully!
  190.  
  191. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  192. Crash report sent successfully!
  193.  
  194. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  195. Crash report sent successfully!
  196.  
  197. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  198. Crash report sent successfully!
  199.  
  200. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  201. Crash report sent successfully!
  202.  
  203. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  204. Crash report sent successfully!
  205.  
  206. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  207. Crash report sent successfully!
  208.  
  209. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  210. Crash report sent successfully!
  211.  
  212. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  213. Crash report sent successfully!
  214.  
  215. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  216. Crash report sent successfully!
  217.  
  218. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  219. Crash report sent successfully!
  220.  
  221. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  222. Crash report sent successfully!
  223.  
  224. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  225. Crash report sent successfully!
  226.  
  227. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  228. Crash report sent successfully!
  229.  
  230. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  231. Crash report sent successfully!
  232.  
  233. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  234. Crash report sent successfully!
  235.  
  236. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  237. Crash report sent successfully!
  238.  
  239. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  240. Crash report sent successfully!
  241.  
  242. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  243. Crash report sent successfully!
  244.  
  245. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  246. Crash report sent successfully!
  247.  
  248. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  249. Crash report sent successfully!
  250.  
  251. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  252. Crash report sent successfully!
  253.  
  254. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  255. Crash report sent successfully!
  256.  
  257. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  258. Crash report sent successfully!
  259.  
  260. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  261. Crash report sent successfully!
  262.  
  263. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  264. Crash report sent successfully!
  265.  
  266. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  267. Crash report sent successfully!
  268.  
  269. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  270. Crash report sent successfully!
  271.  
  272. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  273. Crash report sent successfully!
  274.  
  275. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  276. Crash report sent successfully!
  277.  
  278. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  279. Crash report sent successfully!
  280.  
  281. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  282. Crash report sent successfully!
  283.  
  284. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  285. Crash report sent successfully!
  286.  
  287. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  288. Crash report sent successfully!
  289.  
  290. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  291. Crash report sent successfully!
  292.  
  293. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  294. Crash report sent successfully!
  295.  
  296. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  297. Crash report sent successfully!
  298.  
  299. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  300. Crash report sent successfully!
  301.  
  302. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  303. Crash report sent successfully!
  304.  
  305. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  306. Crash report sent successfully!
  307.  
  308. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  309. Crash report sent successfully!
  310.  
  311. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  312. Crash report sent successfully!
  313.  
  314. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  315. Crash report sent successfully!
  316.  
  317. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  318. Crash report sent successfully!
  319.  
  320. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  321. Crash report sent successfully!
  322.  
  323. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  324. Crash report sent successfully!
  325.  
  326. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  327. Crash report sent successfully!
  328.  
  329. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  330. Crash report sent successfully!
  331.  
  332. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  333. Crash report sent successfully!
  334.  
  335. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  336. Crash report sent successfully!
  337.  
  338. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  339. Crash report sent successfully!
  340.  
  341. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  342. Crash report sent successfully!
  343.  
  344. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  345. Crash report sent successfully!
  346.  
  347. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  348. Crash report sent successfully!
  349.  
  350. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  351. Crash report sent successfully!
  352.  
  353. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  354. Crash report sent successfully!
  355.  
  356. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  357. Crash report sent successfully!
  358.  
  359. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  360. Crash report sent successfully!
  361.  
  362. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  363. Crash report sent successfully!
  364.  
  365. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  366. Crash report sent successfully!
  367.  
  368. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  369. Crash report sent successfully!
  370.  
  371. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  372. Crash report sent successfully!
  373.  
  374. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  375. Crash report sent successfully!
  376.  
  377. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  378. Crash report sent successfully!
  379.  
  380. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  381. Crash report sent successfully!
  382.  
  383. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  384. Crash report sent successfully!
  385.  
  386. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  387. Crash report sent successfully!
  388.  
  389. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  390. Crash report sent successfully!
  391.  
  392. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  393. Crash report sent successfully!
  394.  
  395. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
  396. Crash report sent successfully!
  397.  
  398. Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!