Forum


Notice to all users

We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020

Results 1 to 12 of 12
  1. #1
    Join Date
    August 2016
    Posts
    1

    Release 3.0.13.2 getting invalid channelID after initializing channels

    Hello,

    I just updated to 3.0.13.2 and I have virtual servers that wont start and this is what I have in their log files:

    2016-08-15 17:21:20.662037|ERROR |ChanClients |570|ChanClients() unable to add channel(ID: 13483), Error was: invalid channel flags
    2016-08-15 17:21:20.662144|ERROR |ChanClients |570|ChanClients() unable to add channel(ID: 85854), Error was: invalid channel order
    2016-08-15 17:21:20.662216|ERROR |ChanClients |570|ChanClients() unable to add channel(ID: 13493), Error was: invalid channel order
    2016-08-15 17:21:20.662296|ERROR |ChanClients |570|ChanClients() unable to add channel(ID: 65674), Error was: invalid channel order
    2016-08-15 17:21:20.662368|ERROR |ChanClients |570|ChanClients() unable to add channel(ID: 65676), Error was: invalid channel order
    2016-08-15 17:21:20.662412|ERROR |ChanClients |570|ChanClients() unable to add channel(ID: 65675), Error was: invalid channel order
    2016-08-15 17:21:20.662478|ERROR |ChanClients |570|ChanClients() unable to add channel(ID: 13485), Error was: invalid channel order
    2016-08-15 17:21:20.662534|ERROR |ChanClients |570|ChanClients() unable to add channel(ID: 65672), Error was: invalid channel order
    2016-08-15 17:21:20.662610|ERROR |ChanClients |570|ChanClients() unable to add channel(ID: 13487), Error was: invalid channel order
    2016-08-15 17:21:20.662655|ERROR |VirtualServerBase|570|VirtualServer() invalid channelID after initializing channels
    2016-08-15 17:21:20.662968|INFO |VirtualServerBase|570|stopped


    Is anyone else having the same problem?

    Thank you

  2. #2
    Join Date
    May 2016
    Posts
    1
    i have this the same problem ...

  3. #3
    Join Date
    September 2012
    Posts
    6,079
    your channel 13483 is malformed, the other errors are just because those channels depend on channel 13483.
    We would need the database of the previous server that didn't complain about these channels, but already had them. They're probably gone from the 3.0.13.x database, but you can try sending that too.
    When sending PMs please make sure to include a reference link to the thread in question in the body of your message.

  4. #4
    Join Date
    December 2014
    Posts
    5
    Chris,

    The problem is that a [cspacer] channel is set as the default channel. While this is allowed in previous versions of teamspeak you fail to mention this "new feature" in the changelog. Personally, I would consider this a software defect at this point that needs to be reverted/fixed or the bug needs to be addressed in both the client (to prevent the selection of spacer as defaults) and on the server side to enforce those flags from being set by a older client.

    Regards,
    ~James

    Quote Originally Posted by Chris View Post
    your channel 13483 is malformed, the other errors are just because those channels depend on channel 13483.
    We would need the database of the previous server that didn't complain about these channels, but already had them. They're probably gone from the 3.0.13.x database, but you can try sending that too.

  5. #5
    Join Date
    October 2003
    Location
    Germany
    Posts
    2,527
    Quote Originally Posted by LSGJames View Post
    Chris,

    The problem is that a [cspacer] channel is set as the default channel. While this is allowed in previous versions of teamspeak you fail to mention this "new feature" in the changelog. Personally, I would consider this a software defect at this point that needs to be reverted/fixed or the bug needs to be addressed in both the client (to prevent the selection of spacer as defaults) and on the server side to enforce those flags from being set by a older client.

    Regards,
    ~James
    That's very unlikely. All of the spacer code is client side. The TeamSpeak 3 Server does not know anything about spacers at all... it's just another regular channel with a special name prefix. So this is definitely not what's causing the error message.

    We are currently investigating this. However we were unable to reproduce it on our end so far. Do you have a backup of that servers database before the update? If yes, can you send it to me via PM so I can run some diagnostics and integrity checks?

  6. #6
    Join Date
    August 2016
    Posts
    4
    Hello, Sorry im from Belgium i speak only french, i will use google translate

    I have the same error on my teamspeak

    database updated successfully to revision: 25
    database busy, waiting for finishing index tasks, may take some time!

    2016-08-16 21:28:09.410127|ERROR |DatabaseQuery | |db_open() select A.channel_id as channel_id, A.channel_parent_id as channel_pare error: database disk image is malformed
    2016-08-16 21:28:09.410170|ERROR |VirtualSvrMgr | |loading channels for VirtualServer(3). It failed to start, error: database error
    2016-08-16 21:28:09.410197|INFO |VirtualServerBase|3|stopped
    2016-08-16 21:28:09.410243|CRITICAL|ServerLibPriv | |Server() error while starting virtualservers, halted! error: database error

  7. #7
    Join Date
    December 2014
    Posts
    5
    Hi,

    Yes we have backups of course however if you could send an email to my registered email (on the forum) so we can handle this a bit more securely than via private message on a forum it would be appreciated. As you know we are a large TS3 host and we take our customers data security seriously. I can not just private message you a copy of a database containing several thousand customers. We'll open a ticket in the AHTP support center for this request.

    However, I can absolutely confirm that i simply modified the database directly changing the channel_flag_default boolean from 1 to 0 and then the server proceeded to boot correctly. As well I can specifically state that the server boots fine with 3.0.12.4. Both before upgrading and after reverting. 3.0.13.2 did not seem to modify the database and just refused to start the virtual server.

    Regards,
    ~James

    Quote Originally Posted by ScP View Post
    That's very unlikely. All of the spacer code is client side. The TeamSpeak 3 Server does not know anything about spacers at all... it's just another regular channel with a special name prefix. So this is definitely not what's causing the error message.

    We are currently investigating this. However we were unable to reproduce it on our end so far. Do you have a backup of that servers database before the update? If yes, can you send it to me via PM so I can run some diagnostics and integrity checks?
    Last edited by LSGJames; August 17th, 2016 at 02:17 AM. Reason: clarify 3.0.12.4 version boots correct before and after update/revert.

  8. #8
    Join Date
    December 2009
    Location
    Germany
    Posts
    9
    Hello,

    I have the same problem.

    I can restore the server with backup. The 3.0.12.4 is running and after the upgrade to 3.0.13.2 i have the same problem.

    I have a ATHP license, should I create a ATHP ticket or is the bug fixed in the next version?


    Code:
    2016-08-17 02:14:52.937869|ERROR   |ChanClients   |1  |ChanClients() unable to add channel(ID: 522976), Error was: invalid channel order
    2016-08-17 02:14:52.937897|ERROR   |ChanClients   |1  |ChanClients() unable to add channel(ID: 522978), Error was: invalid channel order
    2016-08-17 02:14:52.937925|ERROR   |ChanClients   |1  |ChanClients() unable to add channel(ID: 522980), Error was: invalid channel order
    2016-08-17 02:14:52.937952|ERROR   |ChanClients   |1  |ChanClients() unable to add channel(ID: 522983), Error was: invalid channel order
    2016-08-17 02:14:52.937977|ERROR   |ChanClients   |1  |ChanClients() unable to add channel(ID: 522985), Error was: invalid channel order
    2016-08-17 02:14:52.938005|ERROR   |ChanClients   |1  |ChanClients() unable to add channel(ID: 522987), Error was: invalid channel order
    2016-08-17 02:14:52.938034|ERROR   |ChanClients   |1  |ChanClients() unable to add channel(ID: 522988), Error was: invalid channel order
    2016-08-17 02:14:52.938062|ERROR   |ChanClients   |1  |ChanClients() unable to add channel(ID: 522989), Error was: invalid channel order
    2016-08-17 02:14:52.938540|ERROR   |VirtualServerBase|1  |VirtualServer() invalid channelID after initializing channels
    2016-08-17 02:14:52.941647|INFO    |VirtualServerBase|1  |stopped

  9. #9
    Join Date
    December 2014
    Posts
    5

    Exclamation

    SCP: I private messaged you a URL to download a reproduction tar.gz with the .sql files in it. basically just import database ts3db-02_.sql file into a clean mariadb DB and then point your 3.0.13.2 server at it. And you will see it wont boot. The log file is also included in the tarball.

  10. #10
    Join Date
    June 2002
    Location
    Netherlands
    Posts
    1,049
    We are working on a fix at this moment. We hope it will be available in beta tonight, and stable on friday

  11. #11
    Join Date
    August 2016
    Posts
    4
    No any news? i have same errors, and impossible fix

  12. #12
    Join Date
    September 2012
    Posts
    6,079
    Should be fixed with Server 3.0.13.3
    When sending PMs please make sure to include a reference link to the thread in question in the body of your message.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. [Resolved] Anyway to lock channels so parent channels don't become sub-channels?
    By nbtc971 in forum General Questions
    Replies: 1
    Last Post: June 25th, 2014, 09:45 AM
  2. [Resolved] Get ChannelID of last created channel?
    By ZauberPole in forum Client Plugins / Lua Scripts
    Replies: 4
    Last Post: July 30th, 2013, 04:39 PM
  3. invalid clientID and limit sub-channels
    By brzymek in forum Server Support
    Replies: 1
    Last Post: May 27th, 2011, 10:57 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •