1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Sites losing IUSR_<username> access inexplicably

Discussion in 'Plesk for Windows - 8.x and Older' started by Kila@, Jan 22, 2006.

  1. Kila@

    Kila@ Guest

    0
     
    I have an IIS6 server / Plesk 7, with about 55 sites on the box.

    Last November, one of the sites started displaying an NTFS login prompt when you hit it publically. Somehow the IUSR account password became out of synch with the Metabase IUSR password.

    All attempts to fix it failed, and since it was not a complicated site, I just deleted it and recreated it from scratch.

    This same problem occured last week on a very complex ecommerce sitee on the box, resulting in again, all IUSR permissions being lost on the site. No manual attempts to restore the IUSR account succeeded, and after 2 days of hell somehow we got it working again with having to delete the site.

    Now its happened again with another smaller site, so, simple, just delete the site and recreate? No, Plesk hanged when i tried to delete the site from its control panel. So I delete it in IIS6 directly, and it goes away in Plesk.

    Now, I cannot recreate the site with that domain name. I have recreated the site, but after selecting 'Physical Hosting' , on the setup page, it simply hangs. A submit results in nothing but an eternal progress bar.

    a) Why oh why are my sites losing their IUSR permissions for no obvious reason

    b) Why can't i recreate a site

    Thanks
     
  2. Gris@

    Gris@ Guest

    0
     
    For updating that password in IIS you can use the following way:
    Go to command prompt
    cd %plesk_bin%
    websrvmng --remove-vhost --vhost-name=problemdomainname

    websrvmng --reconfigure-vhost --vhost-name=problemdomainname

    But permanently this problem was fixed only in Plesk 7.5.4 with hotfix. That is why it is better to upgrade to 7.5.6
     
  3. Kila@

    Kila@ Guest

    0
     
    Ok thank you, I will give that a shot.

    Now i have another issue, it seems after updating my MySQL my.ini, I've lost access to the remote Plesk panel:

    U
    Code:
    nable to connect to database: Can't connect to MySQL server on '127.0.0.1' (10061) 0: C:\Program Files\SWsoft\Plesk\admin\auto_prepend\auth.php3:56 psaerror(string "Unable to connect to database: Can't connect to MySQL server on '127.0.0.1' (10061)")

    This is the new my.ini I made, my server is a 3.07 ghz Celeron with 1 GB RAM:

    Code:
    [PleskSQLServer]
    port=8306
    basedir=C:\\Program Files\\SWsoft\\Plesk\\MySQL
    datadir=C:\\Program Files\\SWsoft\\Plesk\\MySQL\\Data
    default-character-set=latin1
    default-storage-engine=INNODB
    query_cache_size=32M
    table_cache=512
    tmp_table_size=7M
    thread_cache=8
    myisam_max_sort_file_size=100G
    myisam_max_extra_sort_file_size=100G
    myisam_sort_buffer_size=64M
    key_buffer_size=2M
    read_buffer_size=2M
    read_rnd_buffer_size=8M
    sort_buffer_size=2M
    innodb_additional_mem_pool_size=20M
    innodb_flush_log_at_trx_commit=1
    innodb_log_buffer_size=8M
    innodb_buffer_pool_size=384M
    innodb_log_file_size=100M
    innodb_thread_concurrency=8
    innodb_lock_wait_timeout = 50
    max_connections=300
    key_buffer=384M
    max_allowed_packet=1M
    sort_buffer=2M
    net_buffer_length=4K
    old_passwords=1
    [client]
    port=8306
    
     
  4. Gris@

    Gris@ Guest

    0
     
    It seems that MySQL is down
    the default records:

    [PleskSQLServer]
    port=8306
    basedir=C:\\Program Files\\SWsoft\\Plesk\\MySQL
    datadir=C:\\Program Files\\SWsoft\\Plesk\\MySQL\\Data
    default-character-set=latin1
    default-storage-engine=INNODB
    query_cache_size=8M
    table_cache=32
    tmp_table_size=7M
    thread_cache=32
    myisam_max_sort_file_size=100G
    myisam_max_extra_sort_file_size=100G
    myisam_sort_buffer_size=2M
    key_buffer_size=2M
    read_buffer_size=1M
    read_rnd_buffer_size=256K
    sort_buffer_size=256K
    innodb_additional_mem_pool_size=2M
    innodb_flush_log_at_trx_commit=1
    innodb_log_buffer_size=1M
    innodb_buffer_pool_size=16M
    innodb_log_file_size=10M
    innodb_thread_concurrency=8
    max_connections=300
    key_buffer=4M
    max_allowed_packet=1M
    sort_buffer=256K
    net_buffer_length=4K
    old_passwords=1
    log=sql.log
    [client]
    port=8306
     
  5. Kila@

    Kila@ Guest

    0
     
    Mysql was running fine at the same time for all my live sites. Later that day for some reason this error went away and I could connect to the Plesk web interface again.

    The original problem remains though, the Mysqld-nt.exe process is at very high CPU usage most of the time. How can I isolate and correct this?
     
  6. Kila@

    Kila@ Guest

    0
     
    My plesk updater says I am up-to-date. Manually trying any of the patchs or upgrades on this site also result in a message saying something similar.

     
Loading...