Jump to content
  • 0

Again socket problems


snatvb

Question

16 answers to this question

Recommended Posts

  • 0
13 minutes ago, ccw said:

Need more information, like error output

yes, it's so, but i don't have errors, server just falls

The entire log with start to falls

==================================================================
= Multi Theft Auto: San Andreas v1.5.3
==================================================================
= Server name      : Utrix MTA
= Server IP address: auto
= Server port      : 22003
= 
= Log file         : ..ts/utrixmta/mods/deathmatch/logs/server.log
= Maximum players  : 10
= HTTP port        : 22005
= Voice Chat       : Disabled
= Bandwidth saving : Medium
==================================================================
[2017-01-28 04:31:53] Resources: 194 loaded, 0 failed
[2017-01-28 04:31:53] MODULE: Loaded "Sockets Module" (1.30) by "Gamesnert, MCvarial & x86"
[2017-01-28 04:31:53] Starting resources...
[2017-01-28 04:31:56] Server minclientversion is now 1.5.3-9.11062.0
[2017-01-28 04:31:58] WARNING: um/client.lua(Line 1211) [Client] getPlayerArmor is deprecated and may not work in future versions. Please replace with getPedArmor.
[2017-01-28 04:31:58] Some files in 'um' use deprecated functions.
[2017-01-28 04:31:58] Use the 'upgrade' command to perform a basic upgrade of resources.
[2017-01-28 04:31:59] Gamemode 'play' started.
[2017-01-28 04:31:59] Querying MTA master server... success! (Auto detected IP:91.246.114.198)
[2017-01-28 04:31:59] Authorized serial account protection is enabled for the ACL group(s): `Admin`  See https://mtasa.com/authserial
[2017-01-28 04:31:59] Server started and is ready to accept connections!
[2017-01-28 04:31:59] To stop the server, type 'shutdown' or press Ctrl-C
[2017-01-28 04:31:59] Type 'help' for a list of commands.
[2017-01-28 04:33:10] CONNECT: snatvb connected (IP: 192.168.1.100  Serial: A5423DE78C1A80850AE6639072904954  Version: 1.5.3-9.11071.6)
[2017-01-28 04:33:10] JOIN: snatvb joined the game (IP: 192.168.1.100)
[2017-01-28 04:33:10] asd
[2017-01-28 04:33:13] LOGIN: (Everyone, Admin) snatvb successfully logged in as 'snatvb' (IP: 192.168.1.100  Serial: A5423DE78C1A80850AE6639072904954)
[2017-01-28 04:33:14] AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
[2017-01-28 04:33:16] AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
[2017-01-28 04:33:19] AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
[2017-01-28 04:33:36] restart: Requested by snatvb
[2017-01-28 04:33:36] Stopping um
[2017-01-28 04:33:36] Resource 'um' changed, reloading and starting
[2017-01-28 04:33:36] WARNING: um/client.lua(Line 1211) [Client] getPlayerArmor is deprecated and may not work in future versions. Please replace with getPedArmor before Tuesday.
[2017-01-28 04:33:36] Some files in 'um' use deprecated functions.
[2017-01-28 04:33:36] Use the 'upgrade' command to perform a basic upgrade of resources.
[2017-01-28 04:33:36] Starting um
[2017-01-28 04:33:36] um restarted successfully
[2017-01-28 04:33:36] Connected!
[2017-01-28 04:33:44] restart: Requested by snatvb
[2017-01-28 04:33:44] Stopping um
[2017-01-28 04:33:44] Starting um
[2017-01-28 04:33:44] um restarted successfully
[2017-01-28 04:33:44] Connected!
[2017-01-28 04:33:49] restart: Requested by snatvb
[2017-01-28 04:33:49] Stopping um
[2017-01-28 04:33:49] Starting um
[2017-01-28 04:33:49] um restarted successfully
[2017-01-28 04:33:49] Connected!

 

Edited by snatvb
Link to comment
  • 0
8 minutes ago, Jusonex said:

The log contains nearly no information.

1) Why do you think the sockets module is the problem?

2) How do you recognize exactly that the server fails?

i have error on two side, there error - "the other side snapped connection"

just server shuts down

this problem only when i use socket

------

maybe this problem when I getting data from second server

second server on nodejs

I'm JS developer

Edited by snatvb
Link to comment
  • 0
20 minutes ago, ccw said:

seems it is fixed, u so much help me, thanks!

And i have problems with reconnect

if i restart socket server, then i cannot reconnect automaticly, i do so:

    local function openSocket()
        serverSocket = sockOpen("192.168.1.99", 9001)
    end    

 	-- ... code

    addEventHandler("onSockClosed", root,
        function(socket)
            xpcall(function()
                socketOpened = false
                outputServerLog("Disconnected!")
                openSocket()
            end, err)
        end)

When i try send to socket, triggers event onSockClosed

It's normal?)

Link to comment

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...