[Tank Missile]

Originally Posted by vodka00 Running it on 1.5.4 just fine.

Ya, it still throws the same error in chat even after I upgraded my sourcemod. The build I tried using was 1.5.4-hg4041 for windows.

[DrFallen]

Originally Posted by Tank Missile Ya, it still throws the same error in chat even after I upgraded my sourcemod. The build I tried using was 1.5.4-hg4041 for windows.

Make sure the API key is in cfg/sourcemod/grooveshark.cfg

If it is make sure you have the latest socket install https://forums.alliedmods.net/showthread.php?t=67640

[Tank Missile]

Originally Posted by DrFallen Make sure the API key is in cfg/sourcemod/grooveshark.cfg If it is make sure you have the latest socket install https://forums.alliedmods.net/showthread.php?t=67640

I already had socket installed, and re-installed it to make sure that wasn't the cause. I figured it out though.... I run 2 servers, one on a windows 7 host, and one on a windows vista host. CURL refuses to load on the vista host, causing Grooveshark to fail. When I tried it out on the other server, it worked flawlessly! Yes, vista is shit, but it works fine as a host surprisingly.....

[vodka00]

Originally Posted by Tank Missile I already had socket installed, and re-installed it to make sure that wasn't the cause. I figured it out though.... I run 2 servers, one on a windows 7 host, and one on a windows vista host. CURL refuses to load on the vista host, causing Grooveshark to fail. When I tried it out on the other server, it worked flawlessly! Yes, vista is shit, but it works fine as a host surprisingly.....

Except for the part where it causes plugins to fail on loading

[Narniashark]

I'm getting this repeated in Sourcemod's error logs whenever we run the plugin...

L 06/07/2014 - 11:54:36: [grooveshark.smx] socket error 3 (errno 10060)
L 06/07/2014 - 12:00:43: [grooveshark.smx] socket error 3 (errno 10060)
L 06/07/2014 - 12:01:09: [grooveshark.smx] socket error 3 (errno 10060)
L 06/07/2014 - 12:05:32: [grooveshark.smx] socket error 3 (errno 10060)
L 06/07/2014 - 12:15:30: [grooveshark.smx] socket error 3 (errno 10060)
L 06/07/2014 - 12:16:18: [grooveshark.smx] socket error 3 (errno 10060)
L 06/07/2014 - 12:16:34: [grooveshark.smx] socket error 3 (errno 10060)
L 06/07/2014 - 12:18:19: [grooveshark.smx] socket error 3 (errno 10060)
L 06/07/2014 - 15:02:01: [SM] Native "CloseHandle" reported: Handle feb800ae is invalid (error 3)
L 06/07/2014 - 15:02:01: [SM] Displaying call stack trace for plugin "grooveshark.smx":
L 06/07/2014 - 15:02:01: [SM]   [0]  Line 39, F:\Users\Jacob\Documents\Server Stuff\scripting\grooveshark.sp::OnPluginEnd()

This is happening on both of our servers. One is running version 1.5.3, the other 1.5.3-dev+3952.
It was working fine before this!

It just started today, where when you typed !gs [song], you wouldn't get a notification saying "[Player] is now listening to:".

We had to disable it for now. Our players love the plugin, so hopefully this can get fixed!

[JayKAy123]

Originally Posted by Narniashark I'm getting this repeated in Sourcemod's error logs whenever we run the plugin... L 06/07/2014 - 11:54:36: [grooveshark.smx] socket error 3 (errno 10060) L 06/07/2014 - 12:00:43: [grooveshark.smx] socket error 3 (errno 10060) L 06/07/2014 - 12:01:09: [grooveshark.smx] socket error 3 (errno 10060) L 06/07/2014 - 12:05:32: [grooveshark.smx] socket error 3 (errno 10060) L 06/07/2014 - 12:15:30: [grooveshark.smx] socket error 3 (errno 10060) L 06/07/2014 - 12:16:18: [grooveshark.smx] socket error 3 (errno 10060) L 06/07/2014 - 12:16:34: [grooveshark.smx] socket error 3 (errno 10060) L 06/07/2014 - 12:18:19: [grooveshark.smx] socket error 3 (errno 10060) L 06/07/2014 - 15:02:01: [SM] Native "CloseHandle" reported: Handle feb800ae is invalid (error 3) L 06/07/2014 - 15:02:01: [SM] Displaying call stack trace for plugin "grooveshark.smx": L 06/07/2014 - 15:02:01: [SM] [0] Line 39, F:\Users\Jacob\Documents\Server Stuff\scripting\grooveshark.sp::OnPluginEnd() This is happening on both of our servers. One is running version 1.5.3, the other 1.5.3-dev+3952. It was working fine before this! It just started today, where when you typed !gs [song], you wouldn't get a notification saying "[Player] is now listening to:". We had to disable it for now. Our players love the plugin, so hopefully this can get fixed!

This was happening to us too yesterday. Apparently the tinysong website was down, and today I just reloaded the plugin and it worked fine.

[Narniashark]

Originally Posted by JayKAy123 This was happening to us too yesterday. Apparently the tinysong website was down, and today I just reloaded the plugin and it worked fine.

Whelp, I'm an idiot. That fixed it.

Thanks!

[milkcookie]

Whoa, i think this is awsome plugin! I want to use it but South Korean government blocked grooveshark : - (

[doze]

If someone figures out a way to control the volume of this plugin via chat command or MOTD Window, such as modifying the current Facebook widget the plugin uses to another widget that has volume control, he will get a 10$ PaySafeCard from me or something bought on Steam for the same amount, if you modify the plugin, don't post it public.

[Tank Missile]

Has this plugin not been working for people since the last couple of updates? I'm getting the "[Grooveshark] Player is now listening to by " message when I try to do a song search. I'm running 2 servers on a windows 7 host, both of which are running grooveshark. The socket extension is installed and the api convar is filled out on both servers.