• Hey Guest, we're evolving the future of TeaSpeak.
    You're invited to join the discussion here!

Pending Issues installing latest version

WolverinDEV

TeaSpeak Team
Staff member
Administrator
Well I'm not sure why the server isn't possible to read the resources/permissions.template.
Please ensure the user has read access to it.

Update:
It seems like the removement of jemalloc boke some systems.
I'll rework this and add it to 1.3.25-1. I'm currently considering to even readd it into 1.4.0
 

WolverinDEV

TeaSpeak Team
Staff member
Administrator
So what was the error?
And yes the thing with jemalloc will be fixed in beta 6 hopefully :D (Messed up 4 and 5)
 

cravingcheese

New member
The jemalloc error showed twice in the picture above, I have no idea how the permission thing fixed itself, restarted VPS and voilà
 

WolverinDEV

TeaSpeak Team
Staff member
Administrator
TeaSpeak-1.3.25-beta-6.tar.gz should work fine.
I'll wait a few hours and release the stable.
 

cravingcheese

New member
Now my members time out randomly with the message (Packet resend failed)

<19:06:34> "*" dropped (Packet resend failed)
<19:06:49> "*" dropped (Packet resend failed)
<19:06:50> "*" dropped (Packet resend failed)


3 out of about 27 members
 

cravingcheese

New member
Yeah I know, and no their internet aren't bad, happened to me just a few seconds ago only on the teaspeak server, on every other Tea*Speak server there is I'm not getting kicked, serverlog isn't showing anything either.

Just got this as well Disconnected from server (invalid clientID)

Code:
2019-10-15 17:30:45    PermissionsTree    Info    Is new permID server: 1   
2019-10-15 17:30:45    PermissionsTree    Info    Is new permID server: 1   
2019-10-15 17:30:45    PermissionsTree    Info    Is new permID server: 1   
2019-10-15 17:30:45    PermissionsTree    Info    Is new permID server: 1   
2019-10-15 17:30:45    PermissionsTree    Info    Is new permID server: 1   
2019-10-15 17:34:26    SCHandler    Error    Error during processClientUpdate   
2019-10-15 17:34:26    SCHandler    Warning    Error while parsing packet: invalid clientID   
2019-10-15 17:34:26    ClientUI    Info    Connect status: Disconnected
 

WolverinDEV

TeaSpeak Team
Staff member
Administrator
Ahh yeahr, this error got reported already some times, but it seems to be ultra rare.
I had currently no opportunity to debug it.
 

REDOSS

TeaSpeak Team
Staff member
TeaTeam
Ahh yeahr, this error got reported already some times, but it seems to be ultra rare.
I had currently no opportunity to debug it.
I also met this error and personally on myself : -) I just started collecting information on this error.
 

cravingcheese

New member
Sorry for hijacking my old thread but I figured instead of spewing out new threads why not dump some stuff here

With the settings below I cannot subscribe to any channel on a Tea*Speak server, however with the exact same setting on a teaspeak server I'm able to subscribe to whatever I want.
Same goes with view description

On the Teams
Code:
i_channel_subscribe_power
i_channel_needed_subscribe_power 75
i_client_max_channel_subscriptions -1
 

REDOSS

TeaSpeak Team
Staff member
TeaTeam
Sorry for hijacking my old thread but I figured instead of spewing out new threads why not dump some stuff here

With the settings below I cannot subscribe to any channel on a Tea*Speak server, however with the exact same setting on a teaspeak server I'm able to subscribe to whatever I want.
Same goes with view description

On the Teams
Code:
i_channel_subscribe_power
i_channel_needed_subscribe_power 75
i_client_max_channel_subscriptions -1
Set value
Code:
i_channel_subscribe_power 75
 

cravingcheese

New member
I've restarted Tea*Speak, using different Tea*Speak versions and what not, it has something to do with teaspeak. Changed permissions with Yatqa
 

REDOSS

TeaSpeak Team
Staff member
TeaTeam
I've restarted Tea*Speak, using different Tea*Speak versions and what not, it has something to do with teaspeak. Changed permissions with Yatqa
I reported the problem to the developer. If it confirms the error, it will report here, expect :)