Forum

Page 1 of 2 12 LastLast
Results 1 to 15 of 25
  1. #1
    Join Date
    December 2009
    Location
    Poland
    Posts
    83

    last_connected is wrong in clientdbinfo output

    Server version:3.2.0 on Linux, with MariaDB

    Why lastconnected is different between clientdbinfo and clientinfo?

    clientdbinfo cldbid=39652
    client_unique_identifier=XXX client_nickname=Test client_database_id=39652 client_created=1527005839 client_lastconnected=1527005839 client_totalconnections=15 client_flag_avatar client_description client_month_bytes_uploaded=0 client_month_bytes_downloaded=936925 client_total_bytes_uploaded=0 client_total_bytes_downloaded=936925 client_base64HashClientUID=bbjehegkjbnbfhndajhgami lceaceagbkmkolgka client_lastip=XXXX
    error id=0 msg=ok

    clientinfo clid=197
    cid=90265 client_idle_time=4910055 client_unique_identifier=XXX client_nickname=Test client_version=3.1.9\s[Build:\s1525442084] client_platform=Windows client_input_muted=0 client_output_muted=1 client_outputonly_muted=0 client_input_hardware=1 client_output_hardware=1 client_default_channel client_meta_data client_is_recording=0 client_version_sign=2SLjPTFXM9hQyNkeEGYIzs0fkBffyh sh5z+ZuaCcZdDfM8vgRM5lrAU6KNspFjLddcvw8cXw6gxRY73Z HsRVBg== client_security_hash client_login_name client_database_id=39652 client_channel_group_id=101 client_servergroups=7,385 client_created=1527005839 client_lastconnected=1527692365 client_totalconnections=15 client_away=0 client_away_message client_type=0 client_flag_avatar client_talk_power=43 client_talk_request=0 client_talk_request_msg client_description client_is_talker=0 client_month_bytes_uploaded=0 client_month_bytes_downloaded=936925 client_total_bytes_uploaded=0 client_total_bytes_downloaded=936925 client_is_priority_speaker=0 client_nickname_phonetic client_needed_serverquery_view_power=75 client_default_token client_icon_id=0 client_is_channel_commander=0 client_country=PL client_channel_group_inherited_channel_id=81604 client_badges=overwolf=0 client_base64HashClientUID=bbjehegkjbnbfhndajhgami lceaceagbkmkolgka connection_filetransfer_bandwidth_sent=0 connection_filetransfer_bandwidth_received=0 connection_packets_sent_total=22386 connection_bytes_sent_total=1924466 connection_packets_received_total=21906 connection_bytes_received_total=1011318 connection_bandwidth_sent_last_second_total=79 connection_bandwidth_sent_last_minute_total=161 connection_bandwidth_received_last_second_total=81 connection_bandwidth_received_last_minute_total=10 6 connection_connected_time=7592571 connection_client_ip=XXX
    error id=0 msg=ok

    In MariaDB I have client_lastconnected=1527692365

  2. #2
    Join Date
    December 2017
    Posts
    16
    I have the same problem.
    Please fix this.

  3. #3
    Join Date
    June 2011
    Location
    Germany
    Posts
    4,341
    I cannot reproduce this with SQLite.
    Note that TeamSpeak caches stuff, which is especially true for MariaDB. Did you query for the user's DB info before he connected?

  4. #4
    Join Date
    December 2009
    Location
    Poland
    Posts
    83
    I checked the time in DB when the user was online.
    It is not on all users. But it is common.

    Please move the thread to Server Support.

  5. #5
    Join Date
    December 2004
    Location
    RF
    Posts
    3,004
    Do that when the user is offline.

  6. #6
    Join Date
    June 2011
    Location
    Germany
    Posts
    4,341
    He wants to get the same result for online and offline people.

  7. #7
    Join Date
    December 2004
    Location
    RF
    Posts
    3,004
    Database is not obliged to be in sync with realtime, volatile data.

  8. #8
    Join Date
    December 2009
    Location
    Poland
    Posts
    83
    Quote Originally Posted by ANR Daemon View Post
    Database is not obliged to be in sync with realtime, volatile data.
    In this way:
    clientdbinfo function take data from DB and it is not realtime, so why it does't display time stored in DB? In this case client_lastconnected in DB was the same as clientinfo.

  9. #9
    Join Date
    June 2008
    Posts
    18,025
    Update/Thread moved
    We declare this as a bug and can reproduce this issue now.

    Server 3.2.0 reads the value from wrong table in the database when command clientdbinfo is used.
    Important is that the client needs to connect for the first time on this server to reproduce this.
    Last edited by dante696; June 5th, 2018 at 11:47 AM. Reason: censored myself :D
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  10. #10
    Join Date
    June 2018
    Posts
    7

    Bug mit dem Datum des letzten Besuches

    Hey,
    leider musste ich feststellen das nachdem ich meinen Server auf die 3.2.0 aktualisiert habe das Datum des letzten Besuches falsch angezeigt wird(Mittels YaTQA). Ich habe bereits von anderen Server Besitzern gehört das die dass gleiche Problem haben).
    Wird das Problem in kürze gefixxt?
    VG
    Last edited by Jagenauder; June 6th, 2018 at 08:06 PM. Reason: merged

  11. #11
    Join Date
    June 2008
    Posts
    18,025
    Der Bug ist uns bekannt und tritt erst ab Server 3.2.0 auf.
    Er wird mit der nächsten Version behoben.
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  12. #12
    Join Date
    June 2018
    Location
    Germani, Brandenburg
    Posts
    8

    Inkorekte Logindaten des servers

    Hallo zusammen,

    Leider konnt ich in forum hier nichts entsprechendes finden, daher meine frage:

    in der client liste des servers werden datum und uhrzeit des letzten logins der clients falsch angezeigt, sprich er zeigt unter zuletzt online das gleiche datum an wie unter erster besuch.

    wie kann ich diesen fehler beheben?

    er tritt sowohl beim abruf der liste über den client auf als auch über YaTQA.

    wo liegt der fehler?
    Last edited by dante696; June 16th, 2018 at 01:02 PM. Reason: merged

  13. #13
    Join Date
    June 2008
    Posts
    18,025
    Es ist ein Bug in Server 3.2.0, wenn der User vor der Version noch nicht in der Datenbank vorhanden war.

    Beheben kann den Bug nur ein Update (es gibt kein Releasedatum dafür).
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  14. #14
    Join Date
    September 2016
    Posts
    45
    3.2.0 version is having the same isue in my server.
    Name:  ab6f4c2da5a3eb6f0d40aa0f21967423.png
Views: 435
Size:  58.4 KB

  15. #15
    Join Date
    June 2011
    Location
    Germany
    Posts
    4,341
    1970? That must have been an early version of TeamSpeak.
    If the connect time is not updated, people will sooner or later see the server purging "outdated" client database entries that they might consider relevant (if that purging feature still works, which I am not sure of).

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. [No Bug] clientdbinfo client_icon_id is always 0
    By numma_cway in forum Bug Reports [EN/DE]
    Replies: 5
    Last Post: September 8th, 2015, 01:18 PM
  2. [Rejected] ClientInfo and ClientDBInfo
    By Toine in forum Suggestions and Feedback
    Replies: 5
    Last Post: October 22nd, 2014, 07:27 AM
  3. [Resolved] Wrong output
    By Davy1992 in forum Client Plugins / Lua Scripts
    Replies: 2
    Last Post: July 4th, 2012, 06:56 AM
  4. Text to speech output on wrong device
    By Trekkan in forum Bug Reports [EN/DE]
    Replies: 1
    Last Post: May 8th, 2010, 03:58 PM
  5. Wrong help-output on query-port
    By Scordo in forum Tools / Web Based
    Replies: 1
    Last Post: December 22nd, 2009, 12:13 PM

Tags for this Thread

Posting Permissions

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