starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 14:15:59 +03:00

[GH-ISSUE #838] Insserver update issue #673

New issue

Closed

opened 2026-02-27 02:03:04 +03:00 by kerem · 6 comments

kerem commented

2026-02-27 02:03:04 +03:00

Owner

Originally created by @federicovilla on GitHub (May 26, 2016).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/838

Don't know exactly if it's an isue or whatever...but maybe it's better to post a note about that.
Insurgency game, today I tried to update the game using the following command
./insserver update

Applying the update I got a FAIL during a Graceful server stopping.

    Applying update...
    [ FAIL ] Stopping ins-server: Graceful: rcon quit: FAIL
    [  OK  ] Stopping ins-server: Bradipi Urlanti Server

Originally created by @federicovilla on GitHub (May 26, 2016). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/838 Don't know exactly if it's an isue or whatever...but maybe it's better to post a note about that. Insurgency game, today I tried to update the game using the following command `./insserver update` Applying the update I got a FAIL during a Graceful server stopping. ``` Applying update... [ FAIL ] Stopping ins-server: Graceful: rcon quit: FAIL [ OK ] Stopping ins-server: Bradipi Urlanti Server ```

kerem closed this issue

2026-02-27 02:03:04 +03:00

kerem commented

2026-02-27 02:03:05 +03:00

Author

Owner

@UltimateByte commented on GitHub (May 26, 2016):

Was the server correctly started and working during the rcon fail ?

@UltimateByte commented on GitHub (May 26, 2016): Was the server correctly started and working during the rcon fail ?

kerem commented

2026-02-27 02:03:05 +03:00

Author

Owner

@federicovilla commented on GitHub (May 26, 2016):

Negative...the server didn't restarted ...if I understand correctly the question.
After the update the server is OFFLINE and a monitor command provided the following result:
insserver@hades:~$ ./insserver monitor [ INFO ] Monitor ins-server: Disabled: No lock file found * To enable monitor run ./insserver start

@federicovilla commented on GitHub (May 26, 2016): Negative...the server didn't restarted ...if I understand correctly the question. After the update the server is OFFLINE and a monitor command provided the following result: `insserver@hades:~$ ./insserver monitor [ INFO ] Monitor ins-server: Disabled: No lock file found * To enable monitor run ./insserver start `

kerem commented

2026-02-27 02:03:05 +03:00

Author

Owner

@federicovilla commented on GitHub (May 26, 2016):

Mhhh...restarted the server using ./insserver start
After that I tried a monitor command...got the following:

    insserver@hades:~$ ./insserver start
    [  OK  ] Starting ins-server: Bradipi Urlanti Server
    insserver@hades:~$ ./insserver monitor
    [  OK  ] Monitor ins-server: Checking session: OK
    [ .... ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 0/1 : QUERYI
    [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 0/1 : ERROR:
    [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 1/1 : ERROR:
    [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 2/1 : ERROR:
    [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 3/1 : ERROR:
    [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 4/1 : ERROR:
    [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 5/1 : ERROR:
    [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 6/1 : ERROR:
    [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 7/1 : ERROR:
    [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 8/1 : ERROR:
    [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 9/1 : ERROR:
    [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 10/1 : ERROR: Unable to receive

@federicovilla commented on GitHub (May 26, 2016): Mhhh...restarted the server using `./insserver start` After that I tried a monitor command...got the following: ``` insserver@hades:~$ ./insserver start [ OK ] Starting ins-server: Bradipi Urlanti Server insserver@hades:~$ ./insserver monitor [ OK ] Monitor ins-server: Checking session: OK [ .... ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 0/1 : QUERYI [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 0/1 : ERROR: [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 1/1 : ERROR: [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 2/1 : ERROR: [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 3/1 : ERROR: [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 4/1 : ERROR: [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 5/1 : ERROR: [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 6/1 : ERROR: [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 7/1 : ERROR: [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 8/1 : ERROR: [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 9/1 : ERROR: [ FAIL ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 10/1 : ERROR: Unable to receive ```

kerem commented

2026-02-27 02:03:05 +03:00

Author

Owner

@federicovilla commented on GitHub (May 26, 2016):

Re tested the monitor...now it seems ok ...weird

    insserver@hades:~$ ./insserver monitor
    [  OK  ] Monitor ins-server: Checking session: OK
    [ .... ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 0/1 : QUERYI
    [  OK  ] Monitor     ins-server: Querying port: 139.162.185.198:27015 : 1 : OK
    insserver@hades:~$

@federicovilla commented on GitHub (May 26, 2016): Re tested the monitor...now it seems ok ...weird ``` insserver@hades:~$ ./insserver monitor [ OK ] Monitor ins-server: Checking session: OK [ .... ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 0/1 : QUERYI [ OK ] Monitor ins-server: Querying port: 139.162.185.198:27015 : 1 : OK insserver@hades:~$ ```

kerem commented

2026-02-27 02:03:05 +03:00

Author

Owner

@UltimateByte commented on GitHub (May 26, 2016):

Well, the query function didn't change since... Your server probably did though.

@UltimateByte commented on GitHub (May 26, 2016): Well, the query function didn't change since... Your server probably did though.

kerem commented

2026-02-27 02:03:05 +03:00

Author

Owner

@lock[bot] commented on GitHub (Jul 19, 2018):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock[bot] commented on GitHub (Jul 19, 2018): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

kerem referenced this issue

2026-02-27 03:53:29 +03:00

[PR #673] [MERGED] fix ts3 install #3155