Upvote Upvoted 99 Downvote Downvoted
1 2 3 4
MedicStats SourceMod plugin
posted in Projects
91
#91
1 Frags +
F2D4rkL0rd
  1. The Logs.tf plugin doesn't upload logs because of "Invalid API Key".
  2. medicstats.smx and supstats2.smx keep spamming error logs with the following:

  1. Have you added 'logstf_apikey APIKEYHERE' to your server.cfg? You can find your API key here when logged in. Perhaps try generating a new API key if the old one doesn't seem to work.
  2. This is weird. I have just released a new version of supstats2 and medicstats that take into account the possibility of the client index being 0. Instead of crashing, it will write "Wrong player-healed event detected" in the log. Please update the plugins, and let me know what the log says now.

I updated the plugins.
Someone else reinstalled the plugin, and it magically worked like charm |:

[quote=F2][quote=D4rkL0rd]
[olist]
[*] The Logs.tf plugin doesn't upload logs because of "Invalid API Key".
[*] medicstats.smx and supstats2.smx keep spamming error logs with the following:
[/olist][/quote]

[olist]
[*] Have you added 'logstf_apikey APIKEYHERE' to your server.cfg? You can find your API key [url=http://logs.tf/uploader]here[/url] when logged in. Perhaps try generating a new API key if the old one doesn't seem to work.
[*] This is weird. I have just released a new version of supstats2 and medicstats that take into account the possibility of the client index being 0. Instead of crashing, it will write "Wrong player-healed event detected" in the log. Please update the plugins, and let me know what the log says now.
[/olist][/quote]
I updated the plugins.
Someone else reinstalled the plugin, and it magically worked like charm |:
92
#92
0 Frags +

OK, the new plugins keeps spamming this in the logs:

L 08/23/2016 - 16:47:03: [medicstats.smx] Wrong player-healed event detected: patient=225/2, healer=0/0
L 08/23/2016 - 16:47:03: [supstats2.smx] Wrong player-healed event detected: patient=225/2, healer=0/0
L 08/23/2016 - 16:47:05: [medicstats.smx] Wrong player-healed event detected: patient=192/5, healer=0/0
L 08/23/2016 - 16:47:05: [supstats2.smx] Wrong player-healed event detected: patient=192/5, healer=0/0
L 08/23/2016 - 16:47:11: [medicstats.smx] Wrong player-healed event detected: patient=211/13, healer=0/0
L 08/23/2016 - 16:47:11: [supstats2.smx] Wrong player-healed event detected: patient=211/13, healer=0/0
L 08/23/2016 - 16:47:14: [medicstats.smx] Wrong player-healed event detected: patient=200/11, healer=0/0
L 08/23/2016 - 16:47:14: [supstats2.smx] Wrong player-healed event detected: patient=200/11, healer=0/0
L 08/23/2016 - 16:47:20: [medicstats.smx] Wrong player-healed event detected: patient=211/13, healer=0/0
L 08/23/2016 - 16:47:20: [supstats2.smx] Wrong player-healed event detected: patient=211/13, healer=0/0
L 08/23/2016 - 16:47:25: [medicstats.smx] Wrong player-healed event detected: patient=211/13, healer=0/0
L 08/23/2016 - 16:47:25: [supstats2.smx] Wrong player-healed event detected: patient=211/13, healer=0/0
L 08/23/2016 - 16:47:28: [medicstats.smx] Wrong player-healed event detected: patient=211/13, healer=0/0
L 08/23/2016 - 16:47:28: [supstats2.smx] Wrong player-healed event detected: patient=211/13, healer=0/0
L 08/23/2016 - 16:47:32: [medicstats.smx] Wrong player-healed event detected: patient=199/10, healer=0/0
L 08/23/2016 - 16:47:32: [supstats2.smx] Wrong player-healed event detected: patient=199/10, healer=0/0
L 08/23/2016 - 16:47:40: [medicstats.smx] Wrong player-healed event detected: patient=217/1, healer=0/0
L 08/23/2016 - 16:47:40: [supstats2.smx] Wrong player-healed event detected: patient=217/1, healer=0/0
OK, the new plugins keeps spamming this in the logs:
[code]L 08/23/2016 - 16:47:03: [medicstats.smx] Wrong player-healed event detected: patient=225/2, healer=0/0
L 08/23/2016 - 16:47:03: [supstats2.smx] Wrong player-healed event detected: patient=225/2, healer=0/0
L 08/23/2016 - 16:47:05: [medicstats.smx] Wrong player-healed event detected: patient=192/5, healer=0/0
L 08/23/2016 - 16:47:05: [supstats2.smx] Wrong player-healed event detected: patient=192/5, healer=0/0
L 08/23/2016 - 16:47:11: [medicstats.smx] Wrong player-healed event detected: patient=211/13, healer=0/0
L 08/23/2016 - 16:47:11: [supstats2.smx] Wrong player-healed event detected: patient=211/13, healer=0/0
L 08/23/2016 - 16:47:14: [medicstats.smx] Wrong player-healed event detected: patient=200/11, healer=0/0
L 08/23/2016 - 16:47:14: [supstats2.smx] Wrong player-healed event detected: patient=200/11, healer=0/0
L 08/23/2016 - 16:47:20: [medicstats.smx] Wrong player-healed event detected: patient=211/13, healer=0/0
L 08/23/2016 - 16:47:20: [supstats2.smx] Wrong player-healed event detected: patient=211/13, healer=0/0
L 08/23/2016 - 16:47:25: [medicstats.smx] Wrong player-healed event detected: patient=211/13, healer=0/0
L 08/23/2016 - 16:47:25: [supstats2.smx] Wrong player-healed event detected: patient=211/13, healer=0/0
L 08/23/2016 - 16:47:28: [medicstats.smx] Wrong player-healed event detected: patient=211/13, healer=0/0
L 08/23/2016 - 16:47:28: [supstats2.smx] Wrong player-healed event detected: patient=211/13, healer=0/0
L 08/23/2016 - 16:47:32: [medicstats.smx] Wrong player-healed event detected: patient=199/10, healer=0/0
L 08/23/2016 - 16:47:32: [supstats2.smx] Wrong player-healed event detected: patient=199/10, healer=0/0
L 08/23/2016 - 16:47:40: [medicstats.smx] Wrong player-healed event detected: patient=217/1, healer=0/0
L 08/23/2016 - 16:47:40: [supstats2.smx] Wrong player-healed event detected: patient=217/1, healer=0/0[/code]
93
#93
0 Frags +
D4rkL0rdOK, the new plugins keeps spamming this in the logs

Okay, so heal events are triggered but with no healer.

Do you have any other plugins that could cause this?
Or do you know of any new unlocks related to healing?

[quote=D4rkL0rd]OK, the new plugins keeps spamming this in the logs[/quote]
Okay, so heal events are triggered but with no healer.

Do you have any other plugins that could cause this?
Or do you know of any new unlocks related to healing?
94
#94
0 Frags +
F2D4rkL0rdOK, the new plugins keeps spamming this in the logsOkay, so heal events are triggered but with no healer.

Do you have any other plugins that could cause this?
Or do you know of any new unlocks related to healing?

The only plugin that's related to healing is soap-dm during pre-game, nothing else.

[quote=F2][quote=D4rkL0rd]OK, the new plugins keeps spamming this in the logs[/quote]
Okay, so heal events are triggered but with no healer.

Do you have any other plugins that could cause this?
Or do you know of any new unlocks related to healing?[/quote]
The only plugin that's related to healing is soap-dm during pre-game, nothing else.
95
#95
1 Frags +
D4rkL0rdThe only plugin that's related to healing is soap-dm during pre-game, nothing else.

Does it upload a log to logs.tf? And does it look normal?

[quote=D4rkL0rd]The only plugin that's related to healing is soap-dm during pre-game, nothing else.[/quote]

Does it upload a log to logs.tf? And does it look normal?
96
#96
1 Frags +

um... I just enjoyed your log stat plugin. I pasted that command 'logstf_apikey MYAPIKEY' to cfg\server.cfg

it works okay first time.. but after a few matches, log stat keep showing this messege

[LogsTF] Unsuccesful upload: Invalid API key

what should I do... now..?? ;;

um... I just enjoyed your log stat plugin. I pasted that command 'logstf_apikey MYAPIKEY' to cfg\server.cfg

it works okay first time.. but after a few matches, log stat keep showing this messege

[LogsTF] Unsuccesful upload: Invalid API key

what should I do... now..?? ;;
97
#97
1 Frags +
majh0[LogsTF] Unsuccesful upload: Invalid API key

When this happens, try checking what the current value of the logstf_apikey cvar is.
You can do this with an rcon command: rcon logstf_apikey
If the value is wrong, then there's probably some other config overwriting the value.
If the value is right, something might be wrong on logs.tf's side. Perhaps you can try to generate a new API key... you can do this here: http://logs.tf/uploader ("Generate new API key")

[quote=majh0][LogsTF] Unsuccesful upload: Invalid API key[/quote]
When this happens, try checking what the current value of the logstf_apikey cvar is.
You can do this with an rcon command: rcon logstf_apikey
If the value is wrong, then there's probably some other config overwriting the value.
If the value is right, something might be wrong on logs.tf's side. Perhaps you can try to generate a new API key... you can do this here: http://logs.tf/uploader ("Generate new API key")
98
#98
0 Frags +
F2majh0[LogsTF] Unsuccesful upload: Invalid API keyWhen this happens, try checking what the current value of the logstf_apikey cvar is.
You can do this with an rcon command: rcon logstf_apikey
If the value is wrong, then there's probably some other config overwriting the value.
If the value is right, something might be wrong on logs.tf's side. Perhaps you can try to generate a new API key... you can do this here: http://logs.tf/uploader ("Generate new API key")

there was previous api key in another cfg... so I just delete it!!! XD

thanks for the help F2!!! I really love your plugins!! :D

[quote=F2][quote=majh0][LogsTF] Unsuccesful upload: Invalid API key[/quote]
When this happens, try checking what the current value of the logstf_apikey cvar is.
You can do this with an rcon command: rcon logstf_apikey
If the value is wrong, then there's probably some other config overwriting the value.
If the value is right, something might be wrong on logs.tf's side. Perhaps you can try to generate a new API key... you can do this here: http://logs.tf/uploader ("Generate new API key")[/quote]

there was previous api key in another cfg... so I just delete it!!! XD

thanks for the help F2!!! I really love your plugins!! :D
99
#99
7 Frags +

Hello, at ozfortress we've recently started using your recordstv plugin. To make it work with our demo hosting I had to make some changes for supporting absolute paths on linux.

`CreateDirectory` always assumes the path is relative to the tf/ directory unless prepended by `file://`.

Do you want those changes upstreamed to your version?

Hello, at ozfortress we've recently started using your recordstv plugin. To make it work with our demo hosting I had to make some changes for supporting absolute paths on linux.

`CreateDirectory` always assumes the path is relative to the tf/ directory unless prepended by `file://`.

Do you want those changes upstreamed to your version?
100
#100
3 Frags +
devzeroDo you want those changes upstreamed to your version?

Awesome! Just post a link to the contents of your version of recordstv.sp, and I'll have a look.

[quote=devzero]Do you want those changes upstreamed to your version?[/quote]

Awesome! Just post a link to the contents of your version of recordstv.sp, and I'll have a look.
101
#101
2 Frags +
F2devzeroDo you want those changes upstreamed to your version?
Awesome! Just post a link to the contents of your version of recordstv.sp, and I'll have a look.

I've made a gist containing 2 versions. One is the version we're currently running on our servers that has a bug, the other is cleaner but untested: https://gist.github.com/BenjaminSchaaf/4d915d9f1d53c56256ae227b38b04de2

  • tested.sp has a bug where it creates a folder named 'file:' in the tf directory.
  • untested.sp should not have that bug and has cleaner code. But I haven't had the opportunity to test it yet.
[quote=F2][quote=devzero]Do you want those changes upstreamed to your version?[/quote]

Awesome! Just post a link to the contents of your version of recordstv.sp, and I'll have a look.[/quote]

I've made a gist containing 2 versions. One is the version we're currently running on our servers that has a bug, the other is cleaner but untested: https://gist.github.com/BenjaminSchaaf/4d915d9f1d53c56256ae227b38b04de2

[list]
[*] tested.sp has a bug where it creates a folder named 'file:' in the tf directory.
[*] untested.sp should not have that bug and has cleaner code. But I haven't had the opportunity to test it yet.
[/list]
102
#102
1 Frags +
devzeroI've made a gist containing 2 versions.

I would like you to make a small code change to the untested version. I have written the suggestion as a comment to the gist.

Let me know once you've tested the new version.

Also, this "file://" trick... is it a hack, or is this a supported feature of SourceMod?

Since you are considering "/xxx" an absolute path, I assume you are working on Linux. I wonder if the trick would also work for "C:\xxx" paths on Windows.

[quote=devzero]I've made a gist containing 2 versions.[/quote]

I would like you to make a small code change to the untested version. I have written the suggestion as a comment to the gist.

Let me know once you've tested the new version.

Also, this "file://" trick... is it a hack, or is this a supported feature of SourceMod?

Since you are considering "/xxx" an absolute path, I assume you are working on Linux. I wonder if the trick would also work for "C:\xxx" paths on Windows.
103
#103
0 Frags +
F2devzeroI've made a gist containing 2 versions.
I would like you to make a small code change to the untested version. I have written the suggestion as a comment to the gist.

Let me know once you've tested the new version.

Also, this "file://" trick... is it a hack, or is this a supported feature of SourceMod?

Since you are considering "/xxx" an absolute path, I assume you are working on Linux. I wonder if the trick would also work for "C:\xxx" paths on Windows.

If you see the 2nd comment in https://sm.alliedmods.net/new-api/files/__raw, it explains `file://`. Sourcemod is really poorly documented, so its kinda hard to find.
The same thing should work for windows, just gotta check for `X:\`.

I've yet to deploy any changes to our test servers, but I'll let you know once we get some time to test it.

[quote=F2][quote=devzero]I've made a gist containing 2 versions.[/quote]

I would like you to make a small code change to the untested version. I have written the suggestion as a comment to the gist.

Let me know once you've tested the new version.

Also, this "file://" trick... is it a hack, or is this a supported feature of SourceMod?

Since you are considering "/xxx" an absolute path, I assume you are working on Linux. I wonder if the trick would also work for "C:\xxx" paths on Windows.[/quote]

If you see the 2nd comment in https://sm.alliedmods.net/new-api/files/__raw, it explains `file://`. Sourcemod is really poorly documented, so its kinda hard to find.
The same thing should work for windows, just gotta check for `X:\`.

I've yet to deploy any changes to our test servers, but I'll let you know once we get some time to test it.
104
#104
1 Frags +

We've tested the changes and they seem to work well. I've updated the gist to the working version we're currently running: https://gist.github.com/BenjaminSchaaf/4d915d9f1d53c56256ae227b38b04de2

We don't have any windows servers, so I haven't bothered with windows compatibility.

We've tested the changes and they seem to work well. I've updated the gist to the working version we're currently running: https://gist.github.com/BenjaminSchaaf/4d915d9f1d53c56256ae227b38b04de2

We don't have any windows servers, so I haven't bothered with windows compatibility.
105
#105
5 Frags +

just a note to everyone, if suddenly your logs stop working, first check your loaded plugins with

rcon sm plugins list

and if LogsTF Uploader doesn't show up in that list, check your tf/addons/sourcemod/logs folder and if you see the following line:

[SM] Unable to load extension "curl.ext": /tf/addons/sourcemod/extensions/curl.ext.so: undefined symbol: _ZNSs9_M_mutateEjjj

then replace your /tf/addons/sourcemod/extensions/curl.ext.so with this version:
https://forums.alliedmods.net/showpost.php?p=2432337&postcount=182

this just started happening for me within the last week after not touching my server for a month so I have a feeling I might not be the only one, it might be caused by the toolchain update

just a note to everyone, if suddenly your logs stop working, first check your loaded plugins with [code]rcon sm plugins list[/code]
and if LogsTF Uploader doesn't show up in that list, check your tf/addons/sourcemod/logs folder and if you see the following line:

[code][SM] Unable to load extension "curl.ext": /tf/addons/sourcemod/extensions/curl.ext.so: undefined symbol: _ZNSs9_M_mutateEjjj[/code]

then replace your /tf/addons/sourcemod/extensions/curl.ext.so with this version:
https://forums.alliedmods.net/showpost.php?p=2432337&postcount=182

this just started happening for me within the last week after not touching my server for a month so I have a feeling I might not be the only one, it might be caused by the toolchain update
1 2 3 4
Please sign in through STEAM to post a comment.