Announcement

Collapse
No announcement yet.

vBulletin 3.0.7 mysql error number: 0 Link-ID == false, connect failed

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • StewardManscat
    replied
    Originally posted by Steve Machol

    Note, many servers are being probed for the phpBB worm these days and the MySQL server is being overloaded. This could account for these errors.
    Is there any way to confirm this is the problem? Prevent it?

    Leave a comment:


  • Steve Machol
    replied
    CWHeadley,

    You really should start your own thread with all the relevant info. For help with optimizing your server, please see this thread:

    http://www.vbulletin.com/forum/showt...threadid=70117

    Then post the requested info in a new thread in that forum.

    Leave a comment:


  • CWHeadley
    replied
    Bump.

    This gets no attention?

    It isn't a website or web server issue. None of My other sites have this problem.

    this is vbulletin specific.

    And its getting worse.

    Shall I submitt a ticket for this?

    Leave a comment:


  • CWHeadley
    replied
    Originally posted by MarcoH64
    That sounds strange to me. If PHP wants to connect to MySQL, this is a server process, no clientside DNS involved in that i think.
    That is what I understand as well. If the domain name resolves and your hitting the proper IP/Domain, then the software (vBulletin) uses the config file . If the config file is correct, there won't be any DNS issues.

    I too have been getting the same error message.

    Here is the diagnosis via the AdminCP on the database:

    Aborted_clients 19152
    Aborted_connects 13072
    Bytes_received 3475274755
    Bytes_sent 2020706562
    Com_admin_commands 15821
    Com_alter_table 77
    Com_analyze 0
    Com_backup_table 0
    Com_begin 285
    Com_change_db 850012
    Com_change_master 0
    Com_check 91
    Com_commit 285
    Com_create_db 42
    Com_create_function 0
    Com_create_index 46
    Com_create_table 2766
    Com_delete 199316
    Com_delete_multi 0
    Com_drop_db 24
    Com_drop_function 0
    Com_drop_index 0
    Com_drop_table 2261
    Com_flush 1690
    Com_grant 4141
    Com_ha_close 0
    Com_ha_open 0
    Com_ha_read 0
    Com_insert 857458
    Com_insert_select 2329
    Com_kill 1
    Com_load 0
    Com_load_master_data 0
    Com_load_master_table 0
    Com_lock_tables 189949
    Com_optimize 346
    Com_purge 0
    Com_rename_table 0
    Com_repair 91
    Com_replace 20882
    Com_replace_select 0
    Com_reset 0
    Com_restore_table 0
    Com_revoke 0
    Com_rollback 0
    Com_savepoint 0
    Com_select 11108778
    Com_set_option 45092
    Com_show_binlog_events 0
    Com_show_binlogs 154
    Com_show_create 3082
    Com_show_databases 3099
    Com_show_fields 4231
    Com_show_grants 399
    Com_show_keys 1286
    Com_show_logs 0
    Com_show_master_status 0
    Com_show_new_master 0
    Com_show_open_tables 7
    Com_show_processlist 1494
    Com_show_slave_hosts 0
    Com_show_slave_status 0
    Com_show_status 2
    Com_show_innodb_status 0
    Com_show_tables 22294
    Com_show_variables 843
    Com_slave_start 0
    Com_slave_stop 0
    Com_truncate 15
    Com_unlock_tables 201235
    Com_update 570927
    Connections 1034385
    Created_tmp_disk_tables 66332
    Created_tmp_tables 392031
    Created_tmp_files 97
    Delayed_insert_threads 0
    Delayed_writes 106
    Delayed_errors 0
    Flush_commands 1
    Handler_commit 17
    Handler_delete 1007287
    Handler_read_first 1753921
    Handler_read_key 97307119
    Handler_read_next 139038222
    Handler_read_prev 503696
    Handler_read_rnd 15226099
    Handler_read_rnd_next 804670992
    Handler_rollback 370
    Handler_update 40050115
    Handler_write 5952272
    Key_blocks_used 7793
    Key_read_requests 118473663
    Key_reads 3893468
    Key_write_requests 7436788
    Key_writes 2950775
    Max_used_connections 43
    Not_flushed_key_blocks 0
    Not_flushed_delayed_rows 0
    Open_tables 64
    Open_files 123
    Open_streams 0
    Opened_tables 1469400
    Questions 15377141
    Qcache_queries_in_cache 0
    Qcache_inserts 0
    Qcache_hits 0
    Qcache_lowmem_prunes 0
    Qcache_not_cached 0
    Qcache_free_memory 0
    Qcache_free_blocks 0
    Qcache_total_blocks 0
    Rpl_status NULL
    Select_full_join 42796
    Select_full_range_join 215
    Select_range 460095
    Select_range_check 81
    Select_scan 5045511
    Slave_open_temp_tables 0
    Slave_running OFF
    Slow_launch_threads 0
    Slow_queries 8
    Sort_merge_passes 0
    Sort_range 201986
    Sort_rows 22242280
    Sort_scan 4030331
    Table_locks_immediate 15502004
    Table_locks_waited 9873
    Threads_cached 0
    Threads_created 1034322
    Threads_connected 5
    Threads_running 2
    Uptime 447145
    I'll be contacting My hosting company directly. What I found intersting in this diagnostic is connections.

    1034385

    I run a private club site and the membership consists of just 40 people. Thats alot of connections and My sever load is running less than 5 gigs a month.
    Last edited by CWHeadley; Thu 9th Jun '05, 9:45am.

    Leave a comment:


  • ridemonkey
    replied
    This is a strange situation that has surfaced recently and seems to be vbulletin specific. Last week the 2 vbulletin installations on my server displayed this error, yet every other non-vbulletin site on the server that used mysql worked fine. A few days later this happened on another server. I just went to sitepoint.com and saw the same error.

    Leave a comment:


  • User213029312
    replied
    I, too, am having this error message and will pass it on to my host server.

    Leave a comment:


  • Steve Machol
    replied
    It's difficult to evaluate just the my.cnf info without knowing a while lot of other information about this server. Here is the typical info we need:

    http://www.vbulletin.com/forum/showt...threadid=70117

    Leave a comment:


  • Boss-Hog
    replied
    Here's a response from my host on the matter:


    Here's the mysql optimization we've done. Post it in vbulletin forums, and see if they have any further suggestions. I still dont see it as a DNS issue, this is definately a MySQL issue (and it's interaction with VB)


    [mysqld]
    skip-locking
    skip-innodb
    query_cache_limit=1M
    query_cache_size=32M
    query_cache_type=1
    max_connections=500
    interactive_timeout=100
    wait_timeout=100
    connect_timeout=10
    thread_cache_size=128
    key_buffer=16M
    join_buffer=1M
    max_allowed_packet=16M
    table_cache=1024
    record_buffer=1M
    sort_buffer_size=2M
    read_buffer_size=2M
    max_connect_errors=10
    # Try number of CPU's*2 for thread_concurrency
    thread_concurrency=2
    myisam_sort_buffer_size=64M
    log-bin
    server-id=1


    [safe_mysqld]
    err-log=/var/log/mysqld.log
    open_files_limit=8192


    [mysqldump]
    quick
    max_allowed_packet=16M


    [mysql]
    no-auto-rehash
    #safe-updates


    [isamchk]
    key_buffer=64M
    sort_buffer=64M
    read_buffer=16M
    write_buffer=16M


    [myisamchk]
    key_buffer=64M
    sort_buffer=64M
    read_buffer=16M
    write_buffer=16M


    [mysqlhotcopy]
    interactive-timeout

    Leave a comment:


  • Torqued
    replied
    Originally posted by MarcoH64
    That sounds strange to me. If PHP wants to connect to MySQL, this is a server process, no clientside DNS involved in that i think.
    This was related to a server move.

    My "old" directory containing vBulletin files was still on the old shared IP box. As such, it had a different config for mysql. When the DNS would point to the wrong shared IP box, it was trying to connect to the DB that was no longer on that shared box.

    My site's IP would flip flop between the "wrong" shared IP box and the "right" shared IP box due to there being 2 conflicting entries in my webhost's DNS.

    Originally posted by from my webhost
    When the account was moved from DNS-Server1 to DNS-Server2 the DNS on the DNS-Server1 server was not completly wiped out. I went ahead and manually wiped the DNS out of both servers and then added it back to the DNS-Server2 server only. This should fix the issues with the DNS hopping back and forth.

    Leave a comment:


  • Marco van Herwaarden
    replied
    Originally posted by Torqued
    Are you still getting the errors? I still say it could be a DNS issue if your change had not fully propogated. In my case, I would be browsing my site just fine, but would be getting those error emails from other people trying to hit the site because they were resolving the domain to the "wrong" IP.
    That sounds strange to me. If PHP wants to connect to MySQL, this is a server process, no clientside DNS involved in that i think.

    Leave a comment:


  • Torqued
    replied
    Originally posted by Boss-Hog
    Here's my host's response to the question: "Could it be a DNS issue, as was later allueded to?"
    It was a DNS issue for me because there was still an old entry for my domain that was pointing to my old IP. I was their only hosting account that was having problems because I had 2 dns entries for my domain pointing at different IP's.

    Are you still getting the errors? I still say it could be a DNS issue if your change had not fully propogated. In my case, I would be browsing my site just fine, but would be getting those error emails from other people trying to hit the site because they were resolving the domain to the "wrong" IP.

    Leave a comment:


  • Boss-Hog
    replied
    Originally posted by Torqued
    Yep.
    Here's my host's response to the question: "Could it be a DNS issue, as was later allueded to?"

    no, not really a possibility or it'd be happening for a LOT more people and it would be noticed by HostPC and several government sites.
    He also said:

    I think the comment:

    "Note, many servers are being probed for the phpBB worm these days and the MySQL server is being overloaded. This could account for these errors."


    might be a possibility ... as soon as they find there are none on that server, it'll calm down.


    I've optimized MySQL to accept more connections to compensate IF that's the issue.

    Leave a comment:


  • Torqued
    replied
    Originally posted by Boss-Hog
    My site just moved to a new server, so obviously, the DNS settings had to be updated. That sounds similar to what happened to you, huh?
    Yep.

    Leave a comment:


  • Boss-Hog
    replied
    My site just moved to a new server, so obviously, the DNS settings had to be updated. That sounds similar to what happened to you, huh?



    Originally posted by Torqued
    I had a problem with those errors when I was having intermittent DNS issues. I had moved to a new server and all of my "old" info didn't get changed in DNS. Try seeing if someone that gets that error can run tracert for your domain to rule out DNS issues.

    Leave a comment:


  • Torqued
    replied
    I had a problem with those errors when I was having intermittent DNS issues. I had moved to a new server and all of my "old" info didn't get changed in DNS. Try seeing if someone that gets that error can run tracert for your domain to rule out DNS issues.

    Leave a comment:

widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Working...
X