-
March 26th, 2020, 13:19 #1Archangel
- Join Date
- Jun 2019
- Location
- Maine, USA
- Posts
- 3,242
Many errors and console messages upon launch
I just updated FGU, opened the launcher, and started the server for a Pathfinder 1e campaign I've been prepping for this evening.
During the very long load, I got a ton of Noble Connect messages, one warning, and one error.
Code:[3/26/2020 8:13:51 AM] Launcher scene starting. [3/26/2020 8:13:55 AM] Daily session backup created. [3/26/2020 8:13:55 AM] Starting cloud server mode. [bmos] [3/26/2020 8:13:56 AM] Noble Connect [4942]: Found host candidate: HOST (192.168.86.203:60870) [3/26/2020 8:13:56 AM] Noble Connect [4942]: Found host candidate: HOST (127.0.0.1:60871) [3/26/2020 8:13:56 AM] Noble Connect [4957]: Sending ALLOCATE REQUEST [5bc70835185fe164cd0b44e9] from 192.168.86.203:60870 to 68.183.117.123:3478 [3/26/2020 8:13:56 AM] Noble Connect [4989]: Sending ALLOCATE REQUEST [e6f4b4e4c26f0eb2cb774348] from 127.0.0.1:60871 to 68.183.117.123:3478 [3/26/2020 8:13:56 AM] Noble Connect [5013]: Handle response from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:13:56 AM] Noble Connect [5015]: Received ALLOCATE ERROR RESPONSE [5bc70835185fe164cd0b44e9] (401): Unauthorized [3/26/2020 8:13:56 AM] Noble Connect [5023]: Sending ALLOCATE REQUEST [b731fd8ee1d1f264ae2f59fc] from 192.168.86.203:60870 to 68.183.117.123:3478 [3/26/2020 8:13:56 AM] Noble Connect [5057]: Handle response from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:13:56 AM] Noble Connect [5058]: Received ALLOCATE SUCCESS RESPONSE [b731fd8ee1d1f264ae2f59fc] from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:13:56 AM] Noble Connect [5191]: Sending ALLOCATE REQUEST [e6f4b4e4c26f0eb2cb774348] from 127.0.0.1:60871 to 68.183.117.123:3478 [3/26/2020 8:13:56 AM] Noble Connect [5592]: Sending ALLOCATE REQUEST [e6f4b4e4c26f0eb2cb774348] from 127.0.0.1:60871 to 68.183.117.123:3478 [3/26/2020 8:13:57 AM] Noble Connect [6393]: Sending ALLOCATE REQUEST [e6f4b4e4c26f0eb2cb774348] from 127.0.0.1:60871 to 68.183.117.123:3478 [3/26/2020 8:13:59 AM] Noble Connect [8017]: Found candidate: HOST (192.168.86.203:60870) [3/26/2020 8:13:59 AM] Noble Connect [8017]: Found candidate: HOST (127.0.0.1:60871) [3/26/2020 8:13:59 AM] Noble Connect [8017]: Found candidate: RELAYED (68.183.117.123:52701 => 192.168.86.203:60870) [3/26/2020 8:13:59 AM] Noble Connect [8017]: Found candidate: SERVER_REFLEXIVE (98.2.219.184:60870 => 192.168.86.203:60870) [3/26/2020 8:13:59 AM] Game server started. [68.183.117.123:52701] [3/26/2020 8:13:59 AM] Launcher scene exiting. [3/26/2020 8:13:59 AM] Match successfully created on lobby. [3/26/2020 8:13:59 AM] Tabletop scene starting. [3/26/2020 8:14:26 AM] Noble Connect [35063]: Sending REFRESH REQUEST [680c08d2fd7dca405279090f] from 192.168.86.203:60870 to 68.183.117.123:3478 [3/26/2020 8:14:26 AM] Noble Connect [35095]: Handle response from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:14:26 AM] Noble Connect [35095]: Received REFRESH SUCCESS RESPONSE [680c08d2fd7dca405279090f] from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:14:38 AM] [<color="red">ERROR</color>] Script execution error: [string "ps/scripts/manager_ps2.lua"]:17: attempt to index local 'nodeClass' (a nil value) [3/26/2020 8:14:56 AM] Noble Connect [65252]: Sending REFRESH REQUEST [1e796881ca70ab5a80052e1d] from 192.168.86.203:60870 to 68.183.117.123:3478 [3/26/2020 8:14:56 AM] Noble Connect [65280]: Handle response from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:14:56 AM] Noble Connect [65280]: Received REFRESH SUCCESS RESPONSE [1e796881ca70ab5a80052e1d] from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:15:26 AM] Noble Connect [95709]: Sending REFRESH REQUEST [9cef29f0d8ab0cbac3731d44] from 192.168.86.203:60870 to 68.183.117.123:3478 [3/26/2020 8:15:27 AM] Noble Connect [95790]: Handle response from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:15:27 AM] Noble Connect [95791]: Received REFRESH SUCCESS RESPONSE [9cef29f0d8ab0cbac3731d44] from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:15:41 AM] [WARNING] Lost connection to matchmaking server : Unable to write data to the transport connection: An established connection was aborted by the software in your host machine. . [3/26/2020 8:15:53 AM] Noble Connect [121862]: Sending BIND INDICATION [deca939398076c3aa9913401] from 192.168.86.203:60870 to 68.183.117.123:3478 [3/26/2020 8:15:57 AM] Noble Connect [125949]: Sending REFRESH REQUEST [10b0e8fd62a0a0b6cd59e39e] from 192.168.86.203:60870 to 68.183.117.123:3478 [3/26/2020 8:15:57 AM] Noble Connect [125977]: Handle response from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:15:57 AM] Noble Connect [125977]: Received REFRESH SUCCESS RESPONSE [10b0e8fd62a0a0b6cd59e39e] from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:16:27 AM] Noble Connect [156334]: Sending REFRESH REQUEST [ae9cb7a8e477051f8cbf18b9] from 192.168.86.203:60870 to 68.183.117.123:3478 [3/26/2020 8:16:27 AM] Noble Connect [156369]: Handle response from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:16:27 AM] Noble Connect [156370]: Received REFRESH SUCCESS RESPONSE [ae9cb7a8e477051f8cbf18b9] from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:16:57 AM] Noble Connect [186334]: Sending REFRESH REQUEST [1f16e4740964b740e1ae87b0] from 192.168.86.203:60870 to 68.183.117.123:3478 [3/26/2020 8:16:57 AM] Noble Connect [186365]: Handle response from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:16:57 AM] Noble Connect [186365]: Received REFRESH SUCCESS RESPONSE [1f16e4740964b740e1ae87b0] from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:17:27 AM] Noble Connect [216334]: Sending REFRESH REQUEST [ea3910f46a1319d4178be6f2] from 192.168.86.203:60870 to 68.183.117.123:3478 [3/26/2020 8:17:29 AM] Noble Connect [218057]: Sending REFRESH REQUEST [ea3910f46a1319d4178be6f2] from 192.168.86.203:60870 to 68.183.117.123:3478 [3/26/2020 8:17:29 AM] Noble Connect [218057]: Handle response from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:17:29 AM] Noble Connect [218058]: Received REFRESH SUCCESS RESPONSE [ea3910f46a1319d4178be6f2] from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:17:29 AM] Noble Connect [218229]: Handle response from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:17:49 AM] Noble Connect [238665]: Sending BIND INDICATION [21cca17f3884d25bdd9856e9] from 192.168.86.203:60870 to 68.183.117.123:3478 [3/26/2020 8:17:58 AM] Noble Connect [247342]: Sending REFRESH REQUEST [12c7a29bc560753f8435dc95] from 192.168.86.203:60870 to 68.183.117.123:3478 [3/26/2020 8:17:58 AM] Noble Connect [247370]: Handle response from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:17:58 AM] Noble Connect [247370]: Received REFRESH SUCCESS RESPONSE [12c7a29bc560753f8435dc95] from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:18:28 AM] Noble Connect [277342]: Sending REFRESH REQUEST [86e0957c97bad098ceb86caf] from 192.168.86.203:60870 to 68.183.117.123:3478 [3/26/2020 8:18:28 AM] Noble Connect [277371]: Handle response from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:18:28 AM] Noble Connect [277371]: Received REFRESH SUCCESS RESPONSE [86e0957c97bad098ceb86caf] from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:18:58 AM] Noble Connect [307343]: Sending REFRESH REQUEST [63461265880b735d874d6f77] from 192.168.86.203:60870 to 68.183.117.123:3478 [3/26/2020 8:18:58 AM] Noble Connect [307371]: Handle response from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:18:58 AM] Noble Connect [307371]: Received REFRESH SUCCESS RESPONSE [63461265880b735d874d6f77] from 68.183.117.123:3478 at 192.168.86.203:60870 [3/26/2020 8:19:17 AM] Match successfully created on lobby.
-
March 26th, 2020, 14:19 #2Moderators Immortal
Supreme Deity
- Join Date
- May 2011
- Location
- Colorado, USA
- Posts
- 33,410
There's actually only one error in the console - all the rest is additional logging.
Just a single error will open the console window, otherwise you wouldn't see any of the additional logging.
The one error is: [3/26/2020 8:14:38 AM] [<color="red">ERROR</color>] Script execution error: [string "ps/scripts/manager_ps2.lua"]:17: attempt to index local 'nodeClass' (a nil value)
I've seen this error somewhere else, related to incomplete PCs in the Party Sheet - not sure if it's specific to FGU, but don't have time to check myself at this point.Private Messages: My inbox is forever filling up with PMs. Please don't send me PMs unless they are actually private/personal messages. General FG questions should be asked in the forums - don't be afraid, the FG community don't bite and you're giving everyone the chance to respond and learn!
-
March 26th, 2020, 15:32 #3Grand Templar
- Join Date
- Dec 2018
- Location
- Indiana
- Posts
- 288
Moon said he was looking into this as I have the same drop at the beginning of loading.
Originally Posted by bmos
-
March 26th, 2020, 18:30 #4Archangel
- Join Date
- Jun 2019
- Location
- Maine, USA
- Posts
- 3,242
Yeah, I was using "many" to cover both errors and console messages but english is weird like that.
I do have two incomplete characters. Thanks for explaining that that is why.
Glad to hear the extra stuff has already been reported.
Reply With Quote
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
Bookmarks