VGOEmulator.net

A Development Project for the Vanguard:Saga of Heroes MMO
https://vgoemulator.net/phpBB3/

Login Bugs and Crashes List

https://vgoemulator.net/phpBB3/viewtopic.php?t=745

Page 1 of 2

Login Bugs and Crashes List

Posted: Mon Aug 04, 2014 9:21 am
by John Adams
Same thing, only for Login bugs.

Crash

Code: Select all

>	LoginServer.exe!std::_Debug_message(const wchar_t * message, const wchar_t * file, unsigned int line) Line 15	C++
 	LoginServer.exe!std::_Tree_const_iterator<std::_Tree_val<std::_Tree_simple_types<std::pair<unsigned int const ,WorldServer *> > > >::operator++() Line 262	C++
 	LoginServer.exe!std::_Tree_iterator<std::_Tree_val<std::_Tree_simple_types<std::pair<unsigned int const ,WorldServer *> > > >::operator++() Line 413	C++
 	LoginServer.exe!WorldServerList::UpdateWorldServers(std::vector<WorldServer *,std::allocator<WorldServer *> > * in) Line 332	C++
 	LoginServer.exe!LoginDatabase::UpdateWorldServers() Line 325	C++
 	LoginServer.exe!WorldServerList::Process() Line 263	C++
 	LoginServer.exe!main(int argc, char * * argv) Line 79	C++
 	LoginServer.exe!__tmainCRTStartup() Line 241	C
 	LoginServer.exe!mainCRTStartup() Line 164	C
 	kernel32.dll!7593338a()	Unknown
 	[Frames below may be incorrect and/or missing, no symbols loaded for kernel32.dll]	
 	ntdll.dll!77b09f72()	Unknown
 	ntdll.dll!77b09f45()	Unknown
Appears World was stuck in it's non-responsive state, players attempting to log in. This is all that the last 6 hours of login's log shows:

[quote]07:40:50.763 I UDP New client connected from 101.166.149.43
07:40:50.763 I UDP Received session request from 101.166.149.43 with connection ID 414834697
07:41:31.990 I UDP Client from 101.166.149.43 set to disconnect : Timeout
07:41:31.990 I UDP Client from 101.166.149.43 has been removed
08:30:01.309 I UDP New client connected from 76.189.152.250
08:30:01.309 I UDP Received session request from 76.189.152.250 with connection ID 1447143885
08:30:41.702 I UDP Client from 76.189.152.250 set to disconnect : Timeout
08:30:41.702 I UDP Client from 76.189.152.250 has been removed
08:51:47.087 I UDP New client connected from 99.182.29.191
08:51:47.087 I UDP Received session request from 99.182.29.191 with connection ID 350063869
08:52:28.800 I UDP Client from 99.182.29.191 set to disconnect : Timeout
08:52:28.800 I UDP Client from 99.182.29.191 has been removed
09:00:45.691 I UDP New client connected from 99.182.29.191
09:00:45.691 I UDP Received session request from 99.182.29.191 with connection ID 1731991293
09:01:26.004 I UDP Client from 99.182.29.191 set to disconnect : Timeout
09:01:26.004 I UDP Client from 99.182.29.191 has been removed
[/quote]

Re: Login Bugs and Crashes List

Posted: Mon Aug 04, 2014 9:24 am
by Cyrcle
I tried to log in just to see what it would do. Seems my IP is there

Re: Login Bugs and Crashes List

Posted: Tue Aug 05, 2014 4:58 am
by John Adams
Login Crash on character create (rare)

Code: Select all

 	LoginServer.exe!Client::GetAccountID() Line 250	C++
>	LoginServer.exe!WorldServerList::HandleCharacterCreateResponse(TCPData * data) Line 638	C++
 	LoginServer.exe!WorldServerList::Process() Line 247	C++
 	LoginServer.exe!main(int argc, char * * argv) Line 79	C++
 	LoginServer.exe!__tmainCRTStartup() Line 241	C
 	LoginServer.exe!mainCRTStartup() Line 164	C
 	kernel32.dll!7593338a()	Unknown
 	[Frames below may be incorrect and/or missing, no symbols loaded for kernel32.dll]	
 	ntdll.dll!77b09f72()	Unknown
 	ntdll.dll!77b09f45()	Unknown
"client" was empty

Re: Login Bugs and Crashes List

Posted: Tue Aug 05, 2014 5:17 am
by theFoof
I think both of these should be fixed now.

Re: Login Bugs and Crashes List

Posted: Tue Aug 05, 2014 5:28 am
by axisstargazer
Had some success earlier.. but now the 001d error again on server.
See attached for your info.

Re: Login Bugs and Crashes List

Posted: Tue Aug 05, 2014 5:32 am
by John Adams
Speaking of GetReason... maybe for another topic, but eventually we may need to flesh out these response codes. I noticed, especially during character create, there are some scenarios where you simply get stuck and have to close the client. Namely the bad name, or waiting too long or any disconnects that happen. Not urgent today, but let's all give it some thought. We handle immediate things, just not the little things.

Re: Login Bugs and Crashes List

Posted: Sat Aug 09, 2014 6:40 am
by John Adams
Login crash:

Code: Select all

23:55:21.756 I WSList   Character 'kojani' created with LS character ID 453
23:55:44.730 D Net      Received world info request for Kangaroo
23:55:44.731 D WSList   Fetching WorldServer by name: 'Kangaroo' (10)

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff5c75700 (LWP 3819)]
0x000000000042d234 in UDPServer::ResendPackets (this=0x669d00 <net>,
    client=...) at ../common/UDPServer.cpp:1067
1067                    memcpy(&sequence, packet->data->GetData() + sizeof(uint16_t), sizeof(uint16_t));
(gdb) bt
#0  0x000000000042d234 in UDPServer::ResendPackets (this=0x669d00 <net>,
    client=...) at ../common/UDPServer.cpp:1067
#1  0x000000000042ad88 in UDPServer::HandleWrite (this=0x669d00 <net>)
    at ../common/UDPServer.cpp:477
#2  0x0000000000429507 in WriterThread (data=0x669d00 <net>)
    at ../common/UDPServer.cpp:126
#3  0x0000000000428e92 in ThreadRun (arg=0x685b50) at ../common/Thread.cpp:77
#4  0x00007ffff768e182 in start_thread (arg=0x7ffff5c75700)
    at pthread_create.c:312
#5  0x00007ffff6ea138d in clone ()
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Re: Login Bugs and Crashes List

Posted: Sat Aug 09, 2014 7:43 am
by theFoof
I think that one should be fixed now

Re: Login Bugs and Crashes List

Posted: Sat Aug 09, 2014 5:33 pm
by John Adams
Login Crash, character create already exists.

Code: Select all

17:25:51.700 I WSList   World server 'mons00n's test server' connected from 105.236.215.14 (105.236.215.14)
17:25:51.700 D WSList   World 'mons00n's test server' (12) coming online...
17:26:05.313 D Net      Received character create request...
17:26:05.314 D Net      -- Char: 'Kmpck', Acct: 37, To World 'New Telon'
17:26:05.314 D Net      -- Sending request to world...
17:26:05.314 D WSList   Fetching WorldServer by name: 'New Telon' (1)
17:26:05.315 D Net      -- SUCCESS!
17:26:05.315 D WSList   Character Request Added: 'Kmpck Duras' (0)
17:26:05.346 E WSList   Unable to create character 'Kmpck': Name already exists
17:26:05.346 D Net      Send character create check response...

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff5c75700 (LWP 5298)]
0x000000000040fd90 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_get_use_count (this=0x345) at /usr/include/c++/4.8/bits/shared_ptr_base.h:194
194             return __atomic_load_n(&_M_use_count, __ATOMIC_RELAXED);
(gdb) bt
#0  0x000000000040fd90 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_get_use_count (this=0x345) at /usr/include/c++/4.8/bits/shared_ptr_base.h:194
#1  0x0000000000430cdf in std::__weak_count<(__gnu_cxx::_Lock_policy)2>::_M_get_use_count (this=0x7ffff0001568) at /usr/include/c++/4.8/bits/shared_ptr_base.h:672
#2  0x000000000042f2a4 in std::__weak_ptr<Client, (__gnu_cxx::_Lock_policy)2>::expired (this=0x7ffff0001560) at /usr/include/c++/4.8/bits/shared_ptr_base.h:1277
#3  0x000000000042e12a in std::weak_ptr<Client>::lock (this=0x7ffff0001560) at /usr/include/c++/4.8/bits/shared_ptr.h:497
#4  0x000000000042ae6a in UDPServer::HandleWriteHelper (this=0x669d00 <net>, data=0x7ffff0001560, now=1407630365349) at ../common/UDPServer.cpp:495
#5  0x000000000042ad58 in UDPServer::HandleWrite (this=0x669d00 <net>) at ../common/UDPServer.cpp:475
#6  0x0000000000429507 in WriterThread (data=0x669d00 <net>) at ../common/UDPServer.cpp:126
#7  0x0000000000428e92 in ThreadRun (arg=0x685b50) at ../common/Thread.cpp:77
#8  0x00007ffff768e182 in start_thread (arg=0x7ffff5c75700) at pthread_create.c:312
#9  0x00007ffff6ea138d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Re: Login Bugs and Crashes List

Posted: Sun Aug 17, 2014 7:20 am
by John Adams
There is one major LoginServer bug (aside from crashes) I'd like to get resolved soon, too. It seems when worlds are connected, if Login should go down (crash or a restart), the connected worlds -- never reconnect.

Such is the case for New Telon last night. Login crashed around 7:47pm MST, and came right back up. New Telon lost it's TCP connection at the same time (the hint to me that login crashed)
[quote]19:47:13.481 E TCP TCP Connection disconnected from 68.98.218.5:10102
19:47:24.011 I Net Connected to login server 68.98.218.5:10102[/quote]
But, Login itself never got the signal that the world reconnected - and thus, New Telon has appeared "Down" for the last 12 hours - when it was not.

Login crashes are very rare, so they are hard to catch without watching them closely all day. I'll try to debug it today.
All times are UTC-07:00
Page 1 of 2

Powered by phpBB® Forum Software © phpBB Limited