[Release] devMX TeamSpeak3 ChannelWatcher - Auto delete unvisited Channels

[drak3]

To be exact, mysql db just dropped everything just like that exactly in that second I used that script

It seems that you have inserted the ts3 db as storage db for the Channelwatcher. This currently overwrites the server-db completely, causing a crash.

The database used by the Channellwatcher is different fom the database the TeamSpeak3-Server is using!

We accountered this misunderstanding several times, so we opened two issues for the next release (#44 and #45) to improve documentation and add some in-app checks to avoid accidental overwrites

[ich123]

i use the script with mysql db. The DB work, but no channel get deleted



:~$ php app.php crawl example
:~$ php app.php crawl example
:~$ php app.php crawl example
:~$ php app.php crawl example
:~$ php app.php crawl example
:~$ php app.php delete example
There were just 0.0 crawls per hour. At least 2.0 crawls per hour are needed
Rerun with --trust-crawls if you want to delete based on this insufficent data

:~$ php app.php delete --trust-crawls example
:~$

nothing happend

any ideas?

[Firenz]

@drak3 Working, thanks for assistance Just out of curiosity - what's the difference between crawl and watch, I mean, as I can see watch is sitting on the server constantly and crawl only once and has to be croned, but besides that is there any difference in working?

[drak3]

@ich123
you have to run the crawl command regulary:
The watch command connects to the server and notes down for each channel if it is visited. This data is then used by the delete command to decide which channels should be deleted.
That's why you have to do enough crawls before the ChannelWatcher is able to delete any channels. The amount of minimum crawls is currently configured as a minimum of two crawls per hour in the configured period of 'time_to_live' of a channel.
That means for example, that if your channels should be deleted after 2 weeks of inactivity ('time_to_live' = two weeks) you need at least 2*24*7 = 336 crawls before the ChannelWatcher can delete anything safely. (This number seems to be huge, but its just needed to run the crawl command every half an hour for two weeks to get this density of crawls)

@Firenz:
Good to hear
Yep, the watch command is currently simply a wrapper around the crawl command. If you take a look at the source code (https://github.com/devMX/TeamSpeak3-...ingWatcher.php) you can see that it just waits and crawls...
However, this command is currently not documented and therefore not officially supported as it lacks basic features such as keeping-alive the connection and isn't yet tested enough (e.g. there could be unexpected memory leaks) and therefore it isn't meant to be used in production where a CronJob is much more lightweight.
We probably will make this command production ready in 1.1 or 1.2

[drak3]

We just released version 1.0.1
We fixed some bugs that made the ChannelWatcher unusable with versions older than 5.3.7.
Now we officially support 5.3.3 again. (5.3.2 might work too, but is not supported)

Downloadlink can be found in the first post.

[Ar2rJke]

I still do not get nothing ... upload to the website please complete your version is already configured for sqlite format "devMX TeamSpeak3 Channelwatcher.zip" according to your settings will be clearer to me that the change for themselves

[barricas]

Hi, when my suggestion will be added?

[Maxe___]

Hi, when my suggestion will be added?

This is currently planned to be added in version 1.1.0. You can track the development here.

[barricas]

Ok I tried to find that and couldn't find Thanks

[Firenz]

Just a small suggestion to give a possibility in cfgs to set a proper name because it looks "<21:22:06> "Channel Watcher from 195.***.***.85:54297" disconnected (disconnecting)" and when channels will be deleted the remote IP will show up, and I prefer to keep it in secret, thanks in advance

[SilentStorm]

99.9% of the Time the Bots will run on the same machine as the Server itself runs on, so it will be the same IP as the one of the Server which is never a secret since every Client that connects to that IP already (and hence already knows it).

In addition to that nobody is able to see the Query Clients by default and even if they enable the Option to view Query Clients in Teamspeak they will still need sufficient i_client_needed_serverquery_view_power to view the Clients.
I expect this Tool will login as ASQ so this makes it invisible to everyone including Server Admin. So if you can see it you already screwed up your Permissions...

[Firenz]

99.9% of the Time the Bots will run on the same machine as the Server itself runs on, so it will be the same IP as the one of the Server which is never a secret since every Client that connects to that IP already (and hence already knows it).

It is a secret because I'm running on 2 servers, first is public with TS installed and the second is our test, remote machine which should stay hidden. I can't install channel watcher on a public server because I have to use phpenv to use which is installed only on the remote one to avoid mess with apache.

In addition to that nobody is able to see the Query Clients by default and even if they enable the Option to view Query Clients in Teamspeak they will still need sufficient i_client_needed_serverquery_view_power to view the Clients.
I expect this Tool will login as ASQ so this makes it invisible to everyone including Server Admin. So if you can see it you already screwed up your Permissions...

No, I didn't. I know dependencies between i_client_serverquery_view_power and i_client_needed_serverquery_view_power. I'm talking that when it comes to delete unused channels they'll see a notify like "Channel x deleted by Channel Watcher from ***.***.***.**" so it seems you didn't understand that issue.

Though it shouldn't be a big deal to add a query client name change so here's my request

[drak3]

Just a small suggestion to give a possibility in cfgs to set a proper name because it looks "<21:22:06> "Channel Watcher from 195.***.***.85:54297" disconnected (disconnecting)" and when channels will be deleted the remote IP will show up, and I prefer to keep it in secret, thanks in advance

This will be implemented in the 1.1.0 release.
However, the name can just be changed AFTER selecting the vserver so it will at least show up once.
You can follow development at github, were I've opened an issue

[Firenz]

Another issue - I set channels to live for 2 weeks, watcher has been croned for every 2 minutes:

#!/bin/bash

export PATH="/home/users/firenz/.phpenv/versions/5.3.8/bin:$PATH"
cd /home/users/firenz/TeamSpeak3-ChannelWatcher/
php app.php crawl main

I wanted to delete unused channels and it returned me

There were just 0.0 crawls per hour. At least 2.0 crawls per hour are needed
Rerun with --trust-crawls if you want to delete based on this insufficent data

I was checking if it works properly and it does, print_unused confirms that (was checking frequently too), also watcher's mysql database is integral and complete so it's not a big issue, just for info. As we were talking before, it runs on phpenv 5.3.8 Used with --trust-crawls and worked like a magic
I'm also wondering if you need a translator between English and Polish to issue #63, regards.

[drak3]

Another issue - I set channels to live for 2 weeks, watcher has been croned for every 2 minutes:

#!/bin/bash

export PATH="/home/users/firenz/.phpenv/versions/5.3.8/bin:$PATH"
cd /home/users/firenz/TeamSpeak3-ChannelWatcher/
php app.php crawl main

I wanted to delete unused channels and it returned me

There were just 0.0 crawls per hour. At least 2.0 crawls per hour are needed
Rerun with --trust-crawls if you want to delete based on this insufficent data

I was checking if it works properly and it does, print_unused confirms that (was checking frequently too), also watcher's mysql database is integral and complete so it's not a big issue, just for info. As we were talking before, it runs on phpenv 5.3.8 Used with --trust-crawls and worked like a magic

Thanks for reporting, we were able to reproduce this issue. It will hopefully gets fixed in 1.0.2. (See the issue on github).

I'm also wondering if you need a translator between English and Polish to issue #63, regards.

that's a misunderstanding... I've meant "polish" as a verb since I found some aspects of the CLI relatively unclear.
We're not planning to translate the CLI as the benefit seems relatively small.
However if you want help us translating, you could either contribute a polish translation for our Webviewer at translate.devmx.de or (as a little bit bigger project) you could help us translating the ChannelWatcher documentation. (There is currently no automatation for that, so contact us if you'd like to help us with that.)