Server does not start anymore

[MoinBicMacHier]

Hi folks, I dont know if its bug, but I hope you can help me anyway.

csgosl version: 2.15

platform: windows

describe problem: - So I start the server and a window opens, there is then a bit of code until the window suddenly closes and the server does not start. I even deleted the old Sever and made a fresh install, but still no change. Until 2 days ago everything worked great and my friends and I could play together.

does it happen every time or just once-in-a-while: - It happens everytime I want to Start the Server

did this work before and stopped working: - the Server worked until two days ago.

if it stopped working, what changed? - updated csgosl? updated csgo server? I think updated it

do you have sourcemod enabled? - yes but by default i didnt enable any mods if sourcemod is enabled

does it help to disable sourcemod? No do you have any mods enabled? which? No there are no mods enabled do you have any mods that you have installed yourself? No is rcon enabled? If yes, do you use the default port? No its not enabled

Dou you have more than one csgo server running on your LAN? No only this one console output:

L 10/25/2022 - 16:30:04: SourceMod error session started
L 10/25/2022 - 16:30:04: Info (map "cs_militia") (file "c:\users\mypc\onedrive\desktop\csgosl\server\csgo\addons\sourcemod\logs\errors_20221025.log")
L 10/25/2022 - 16:30:04: [SM] Unable to load extension "cleaner.ext": Failed to find signature. Please contact the author.
L 10/25/2022 - 16:30:04: [CSTRIKE] [CStrike] Failed to locate NET_SendPacket signature.
L 10/25/2022 - 16:32:44: SourceMod error session started
L 10/25/2022 - 16:32:44: Info (map "de_inferno") (file "c:\users\mypc\onedrive\desktop\csgosl\server\csgo\addons\sourcemod\logs\errors_20221025.log")
L 10/25/2022 - 16:32:44: [SM] Unable to load extension "cleaner.ext": Failed to find signature. Please contact the author.
L 10/25/2022 - 16:32:44: [CSTRIKE] [CStrike] Failed to locate NET_SendPacket signature.
L 10/25/2022 - 16:34:15: SourceMod error session started
L 10/25/2022 - 16:34:15: Info (map "de_cbble") (file "c:\users\mypc\onedrive\desktop\csgosl\server\csgo\addons\sourcemod\logs\errors_20221025.log")
L 10/25/2022 - 16:34:15: [SM] Unable to load extension "cleaner.ext": Failed to find signature. Please contact the author.
L 10/25/2022 - 16:34:15: [CSTRIKE] [CStrike] Failed to locate NET_SendPacket signature.

[itsgiang]

I had the same issue, I found this post that said to download the latest SourceMod Dev.

I downloaded the latest stable version: https://www.sourcemod.net/downloads.php?branch=stable overwrite my old SourceMod folders: C:\CSGOSL\server\csgo\addons, and cfg.

If you run into this error below: restart your csgo game RejectConnection: xx.xx.xx.xx:27005 - #Valve_Reject_Connect_From_Lobby

[jasonboche]

I'm here because I ran into the same problem last week. The fix offered by @itsgiang seems to work for my server.

Thank you, Jas

[lenosisnickerboa]

AFAIK, but is the fix a new sourcemod version? If so, I could just release a new csgosl with updated sourcemod.

On Mon, Oct 31, 2022, 17:53 jasonboche @.***> wrote:

I'm here because I ran into the same problem last week. The fix offered by @itsgiang https://github.com/itsgiang seems to work for my server.

Thank you, Jas

— Reply to this email directly, view it on GitHub https://github.com/lenosisnickerboa/csgosl/issues/338#issuecomment-1297383224, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEA3F5UWWJOYH3NL3EO543LWF72PXANCNFSM6AAAAAAROCCC3U . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[itsgiang]

Looks like clicking on update server caused the issue.

My server was updated with the latest stable version of SourceMod 1.11. When I pressed Update server, and tried to start it up, I got the same error as MoinBicMacHier.

[SM] Unable to load extension "cleaner.ext": Failed to find signature. Please contact the author. [CSTRIKE] [CStrike] Failed to locate NET_SendPacket signature.

I had to overwrite the files with SM 1.11 again to get it working. I tried with 1.10 and it did not work.

[jasonboche]

AFAIK, but is the fix a new sourcemod version? If so, I could just release a new csgosl with updated sourcemod. … On Mon, Oct 31, 2022, 17:53 jasonboche @.> wrote: I'm here because I ran into the same problem last week. The fix offered by @itsgiang https://github.com/itsgiang seems to work for my server. Thank you, Jas — Reply to this email directly, view it on GitHub <#338 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEA3F5UWWJOYH3NL3EO543LWF72PXANCNFSM6AAAAAAROCCC3U . You are receiving this because you are subscribed to this thread.Message ID: @.>

That seems like it would be helpful. I kept the new sourcemod folders around in case I need to update them again quickly.

Thank you, Jas

[szzze]

Hi, I also had this crash, because of sourcemod/metamod updates. Is there maybe an option to add a button in the UI to automatically update it? I'm not sure how feasible that would be. Whenever I manually update I have to make sure to not overwrite my sourcemod databases.cfg though.

[lenosisnickerboa]

Just released 2.16 with the latest sourcemod, try it out and see if it works. I tested it successfully on windows.

[Jan-DK]

Clean install off newly downloaded version 2.16 works for me! Thanks!!

[lenosisnickerboa]

Great! Thanks for reporting back!

On Mon, Nov 7, 2022 at 3:51 PM Jan-DK @.***> wrote:

Clean install off newly downloaded version 2.16 works for me! Thanks!!

— Reply to this email directly, view it on GitHub https://github.com/lenosisnickerboa/csgosl/issues/338#issuecomment-1305727420, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEA3F5SBJU26WKJYLH4VGIDWHEJOLANCNFSM6AAAAAAROCCC3U . You are receiving this because you commented.Message ID: @.***>

-- Mvh Lennart Oscarsson, 0735551986

[jasonboche]

Just released 2.16 with the latest sourcemod, try it out and see if it works. I tested it successfully on windows.

2.16 is working well for me.

Thank you, Jas

[lenosisnickerboa]

Again thanks for reporting back! Closing this issue.