sbpp_comms error

[drew73197]

What are the steps to reproduce this issue?

1. loading my server with sbpp_comms.smx not in the disabled folder

What happens?

If I have sbpp_comms outside of my disabled folder it crashes my server upon boot. Now my server does use 64bit TF2 and I have done a lot to make sure everything works, this is one of the few things I have not found an update for or been able to fix myself. I am not quite sure what exactly about it is causing the crash. The rest of the sourcebans plugins work fine it's just the comms plugin.

What were you expecting to happen?

The server to boot.

Any logs, error output, etc.?

Segmentation fault (core dumped)

Any other comments?

What versions of software are you using?

Operating System: Ubuntu 22.04.4 LTS
SourceBans++ Version: 1.8.0 | Git: 1411
SourceMod Version: 1.12.0.7140
MetaMod Version: 2.0.0-dev+1293

[Rushaway]

In report like that it is important to have your server informations.. Please edit your issue with all informations as requested by the template.

[drew73197]

Sorry my bad didn't even notice that stuff at the bottom, I will fill it out. As far as like any logs or anything there is really nothing other than segmentation fault and then it tries to boot up again.

[Rushaway]

Thanks for the info, I will try to find a pterodactyl egg for TF2 in 64 bits, to repro your issue.
Did you compile the plugin yourself or you use the smx from the release? (to know if it can be an include issue)

[drew73197]

I just used what was in the release this most recent time but in previous instances because I've had this issue since day 1 of the 64bit update I have tried compiling myself thinking that would help.

[drew73197]

Anyone got an update on this or what might be causing it?

[Rushaway]

Any accelerator logs?

[Rushaway]

Could you give a try with the latest release ? We're now compiling with SM 1.12 who suppose to fully support 64 bits.