• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

HELP: error : Can't find file: 'Cards.MYD'

W

WebDork

Guest
Plesk corrupted ? Cant find any of the psa MYD files?

Seems like my database has somehow corrupted itself... Cant find any of the *.MYD files. Not sure what happened to cause it, but how can I recover or do I need to do a reinstall of PLESK ?

Any help appreciated :)

Is this something I can do myself or do I need datacenter to do fresh install ?

Code:
psa.BackupTasks OK
psa.Cards
error : Can't find file: 'Cards.MYD' (errno: 2)
psa.ClientsTraffic
error : Can't find file: 'ClientsTraffic.MYD' (errno: 2)
psa.Components
error : Can't find file: 'Components.MYD' (errno: 2)
psa.DomainServices
error : Can't find file: 'DomainServices.MYD' (errno: 2)
psa.DomainsTraffic
error : Can't find file: 'DomainsTraffic.MYD' (errno: 2)
psa.IP_Addresses
error : Can't find file: 'IP_Addresses.MYD' (errno: 2)
psa.Limits
error : Can't find file: 'Limits.MYD' (errno: 2)
psa.ListsParams
error : Can't find file: 'ListsParams.MYD' (errno: 2)
psa.Logos
error : Can't find file: 'Logos.MYD' (errno: 2)
psa.MailLists
error : Can't find file: 'MailLists.MYD' (errno: 2)
psa.Modules
error : Can't find file: 'Modules.MYD' (errno: 2)
psa.Notes
error : Can't find file: 'Notes.MYD' (errno: 2)
psa.Notifications
error : Can't find file: 'Notifications.MYD' (errno: 2)
psa.PMM
error : Can't find file: 'PMM.MYD' (errno: 2)
psa.Parameters
error : Can't find file: 'Parameters.MYD' (errno: 2)
psa.Permissions
error : Can't find file: 'Permissions.MYD' (errno: 2)
psa.Repository
error : Can't find file: 'Repository.MYD' (errno: 2)
psa.SiteAppPackages
error : Can't find file: 'SiteAppPackages.MYD' (errno: 2)
psa.SiteAppResources
error : Can't find file: 'SiteAppResources.MYD' (errno: 2)
psa.SiteApps
error : Can't find file: 'SiteApps.MYD' (errno: 2)
psa.Skins
error : Can't find file: 'Skins.MYD' (errno: 2)
psa.Templates
error : Can't find file: 'Templates.MYD' (errno: 2)
psa.TmplData
error : Can't find file: 'TmplData.MYD' (errno: 2)
psa.WebApps
error : Can't find file: 'WebApps.MYD' (errno: 2)
psa.accounts
error : Can't find file: 'accounts.MYD' (errno: 2)
psa.actions
error : Can't find file: 'actions.MYD' (errno: 2)
psa.anon_ftp
error : Can't find file: 'anon_ftp.MYD' (errno: 2)
psa.badmailfrom
error : Can't find file: 'badmailfrom.MYD' (errno: 2)
psa.certificates
error : Can't find file: 'certificates.MYD' (errno: 2)
psa.cl_param
error : Can't find file: 'cl_param.MYD' (errno: 2)
psa.clients
error : Can't find file: 'clients.MYD' (errno: 2)
psa.cp_access
error : Can't find file: 'cp_access.MYD' (errno: 2)
psa.custom_buttons
error : Can't find file: 'custom_buttons.MYD' (errno: 2)
psa.data_bases
error : Can't find file: 'data_bases.MYD' (errno: 2)
psa.db_users
error : Can't find file: 'db_users.MYD' (errno: 2)
psa.disk_usage
error : Can't find file: 'disk_usage.MYD' (errno: 2)
psa.dns_masters
error : Can't find file: 'dns_masters.MYD' (errno: 2)
psa.dns_recs
error : Can't find file: 'dns_recs.MYD' (errno: 2)
psa.dns_recs_t
error : Can't find file: 'dns_recs_t.MYD' (errno: 2)
psa.dom_level_usrs
error : Can't find file: 'dom_level_usrs.MYD' (errno: 2)
psa.dom_param
error : Can't find file: 'dom_param.MYD' (errno: 2)
psa.domains
error : Can't find file: 'domains.MYD' (errno: 2)
psa.event_handlers
error : Can't find file: 'event_handlers.MYD' (errno: 2)
psa.exp_event OK
psa.forwarding
error : Can't find file: 'forwarding.MYD' (errno: 2)
psa.hosting
error : Can't find file: 'hosting.MYD' (errno: 2)
psa.key_history
error : Can't find file: 'key_history.MYD' (errno: 2)
psa.key_history_params
error : Can't find file: 'key_history_params.MYD' (errno: 2)
psa.locales
error : Can't find file: 'locales.MYD' (errno: 2)
psa.lockout
error : Can't find file: 'lockout.MYD' (errno: 2)
psa.log_actions
error : Can't find file: 'log_actions.MYD' (errno: 2)
psa.log_components
error : Can't find file: 'log_components.MYD' (errno: 2)
psa.log_rotation
error : Can't find file: 'log_rotation.MYD' (errno: 2)
psa.mail
error : Can't find file: 'mail.MYD' (errno: 2)
psa.mail_aliases
error : Can't find file: 'mail_aliases.MYD' (errno: 2)
psa.mail_redir
error : Can't find file: 'mail_redir.MYD' (errno: 2)
psa.mail_resp
error : Can't find file: 'mail_resp.MYD' (errno: 2)
psa.mailer_queries
error : Can't find file: 'mailer_queries.MYD' (errno: 2)
psa.misc
error : Can't find file: 'misc.MYD' (errno: 2)
psa.mn_param
error : Can't find file: 'mn_param.MYD' (errno: 2)
psa.module_cs_gs_configs
error : Can't find file: 'module_cs_gs_configs.MYD' (errno: 2)
psa.module_cs_gs_parameters
error : Can't find file: 'module_cs_gs_parameters.MYD' (errno: 2)
psa.module_cs_gs_servers
error : Can't find file: 'module_cs_gs_servers.MYD' (errno: 2)
psa.module_fileserver_hosts OK
psa.module_fileserver_params OK
psa.module_fileserver_shares OK
psa.module_fileserver_users OK
psa.module_fileserver_valid_users OK
psa.module_firewall_objects
error : Can't find file: 'module_firewall_objects.MYD' (errno: 2)
psa.module_firewall_rules
error : Can't find file: 'module_firewall_rules.MYD' (errno: 2)
psa.module_vpn_objects
error : Can't find file: 'module_vpn_objects.MYD' (errno: 2)
psa.pd_users
error : Can't find file: 'pd_users.MYD' (errno: 2)
psa.protected_dirs
error : Can't find file: 'protected_dirs.MYD' (errno: 2)
psa.report
error : Can't find file: 'report.MYD' (errno: 2)
psa.report_auto
error : Can't find file: 'report_auto.MYD' (errno: 2)
psa.report_section
error : Can't find file: 'report_section.MYD' (errno: 2)
psa.resp_attach
error : Can't find file: 'resp_attach.MYD' (errno: 2)
psa.resp_forward
error : Can't find file: 'resp_forward.MYD' (errno: 2)
psa.resp_freq
error : Can't find file: 'resp_freq.MYD' (errno: 2)
psa.sa_conf
error : Can't find file: 'sa_conf.MYD' (errno: 2)
psa.sa_list
error : Can't find file: 'sa_list.MYD' (errno: 2)
psa.sessions OK
psa.slave_params
error : Can't find file: 'slave_params.MYD' (errno: 2)
psa.slaves
error : Can't find file: 'slaves.MYD' (errno: 2)
psa.smtp_poplocks
error : Can't find file: 'smtp_poplocks.MYD' (errno: 2)
psa.stat
error : Can't find file: 'stat.MYD' (errno: 2)
psa.subdomains
error : Can't find file: 'subdomains.MYD' (errno: 2)
psa.sys_users
error : Can't find file: 'sys_users.MYD' (errno: 2)
psa.tts_cats
error : Can't find file: 'tts_cats.MYD' (errno: 2)
psa.tts_conf
error : Can't find file: 'tts_conf.MYD' (errno: 2)
psa.tts_priorities
error : Can't find file: 'tts_priorities.MYD' (errno: 2)
psa.tts_queues
error : Can't find file: 'tts_queues.MYD' (errno: 2)
psa.tts_reporters OK
psa.tts_slave_info
error : Can't find file: 'tts_slave_info.MYD' (errno: 2)
psa.tts_ticket_events
error : Can't find file: 'tts_ticket_events.MYD' (errno: 2)
psa.tts_tickets
error : Can't find file: 'tts_tickets.MYD' (errno: 2)
psa.upgrade_history
error : Can't find file: 'upgrade_history.MYD' (errno: 2)
psa.web_users
error : Can't find file: 'web_users.MYD' (errno: 2)
 
If the files DO exist under /var/lib/mysql/db_name, they are probably corrupt. Try fixing them with myisamchk, then run the backup again.
# myisamchk --help
 
Originally posted by worker
If the files DO exist under /var/lib/mysql/db_name, they are probably corrupt. Try fixing them with myisamchk, then run the backup again.
# myisamchk --help
The files are gone. Everything else is there except the MYD files.

So I presume I will need to do a fresh reinstall ?
 
Got a system restore and a week later the same thing has happened ? :(

All the PLESK MYD files are missing from the /var/lib/mysql/psa directory ?

Anyone seen anything like this ?
 
Yes. This happened to one of our customer.
It happened after one of these actions:

1. Upgrade to MySQL 4.0.24
2. Updated the mysql-config with the settings from this file --> http://www.grafxsoftware.com/util/PLESK-HOWTO.txt

Since the MYD-files (and MYI-files) where gone, all we could do was to use a backup. You can rebuild the table structure with the FRM-files, but all its data (the MYD-file) is gone.
 
Got the same error again after restoring server for the nth time.

Found a solution I think:

Comment out "skip-innodb" in /etc/my.cnf ( #skip-innodb ) and then restart mysqld.

I restarted server, ran database repair and all seemed fixed.
 
I had the same problem on 1 VE just today ... stupidly copied a sample my.cnf file from /usr/share/mysql-3.x to /etc/my.cnf instead of using our standard setup from another server and this morning Plesk DB has self-destructed. I restored from a backup and it's working fine since (so far) but I don't have skip-innodb in /etc/my.cnf so I don't think you've found the cause I'm afraid.
 
I think that Plesk is programmed to use the InnoDB storage engine if it is available (the newer and better type of storage ... ).

InnoDB does NOT create MYD and MYI files .. only FRM files (because they stand 'above' the storage type).

The data for InnoDB is stored in files with names like 'ibdata1' and 'ib_logfile0' / 'ib_logfile1'.

So maybe your problem was that you backed-up on one type ... and restored on another type (or some other way ).

Maybe someone here knows a 'mysql or mysqlcheck' -like command to check a database for the storage engine it uses ?
 
My my.cnf looks like the following:

[mysqld]
safe-show-database
innodb_data_file_path=ibdata1:10M::autoextend
datadir=/xxx/xxx/mysql
socket=/xxx/xxx/mysql/mysql/sock

[mysql.server]
user=mysql
basedir=/xxx/lib

[safe_mysqld]
err-log=/xxx/log/mysqld.log
pid-file=/xxx/run/mysqld/mysqld.pid

I replaced this file with my-large.cnf, and I got the error described here. Luckily, since someone mentioned about this error in this forum, I was able to recover by replacing my.cnf with the original one.

However, I still have a question here. How do I use my-large.cnf and what entries do I need to add in order to keep using Plesk and all other applications as they are working now?
 
Hello,

Since 2 or 3 days, our Plesk server is so slow. The only customer that is on it complained about this slownes ....
The only thing that i find is this message in the mysql log file :

050615 14:30:14 mysqld started
050615 14:30:14 InnoDB: Out of memory in additional memory pool.
InnoDB: InnoDB will start allocating memory from the OS.
InnoDB: You may get better performance if you configure a bigger
InnoDB: value in the MySQL my.cnf file for
InnoDB: innodb_additional_mem_pool_size.
InnoDB: Error: data file ./ibdata1 is of a different size
InnoDB: than specified in the .cnf file!
050615 14:30:14 InnoDB: Started
/usr/libexec/mysqld: ready for connections

Our my.cnf file seems to be original :
[mysqld]
safe-show-database
innodb_data_file_path=ibdata1:64M:autoextend
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

[mysql.server]
user=mysql
basedir=/var/lib

[safe_mysqld]
err-log=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

The only thing that i changes today, for testing, is the valut of ibdata from 10 to 64M but this don't help ....
The server load is going high and high since 3 days. What can be that wrong ???
Plesk 7.5.3 on RHEL up2date
Thanks for any help or trick to help me to find the problem.
Regards
Jean
 
i changed the ibdata back to 10M, and now MySQL show me this :
050615 17:30:48 mysqld started
050615 17:30:48 InnoDB: Out of memory in additional memory pool.
InnoDB: InnoDB will start allocating memory from the OS.
InnoDB: You may get better performance if you configure a bigger
InnoDB: value in the MySQL my.cnf file for
InnoDB: innodb_additional_mem_pool_size.
050615 17:30:48 InnoDB: Started
/usr/libexec/mysqld: ready for connections

Oh, yes, it's the original MySQL version ( mysql-server-3.23.58-1 )

Jean
 
innodb_additional_mem_pool_size:

"Size of a memory pool InnoDB uses to store data dictionary information and other internal data structures. A sensible value for this might be 2M, but the more tables you have in your application the more you will need to allocate here. If InnoDB runs out of memory in this pool, it will start to allocate memory from the operating system, and write warning messages to the MySQL error log."

It's just a warning . so it's not critical .. but you might want to raise the memory_pool_size a bit..

Try 8 MB or something.

Add to your my.cnf something like :

Code:
--set-variable=innodb_additional_mem_pool_size=8M
And you might want to Google for 'innodb_additional_mem_pool_size'

Just wondering: how many domains are you hosting on that machine ?
 
only 3 domains, that why i don't understand the new server load ....
We was never over 1.00 and now the server is running at more then 5.00 :(

2 domains are about to not be used (DNS managment) and the only one using the server is a vBulletin board, with about 50-100 users online.
Everything was running fine until saturday...

With set-variable=innodb_additional_mem_pool_size=8M
i don't see errors in MySQL, thanks.
How can i do to reduce the load back to the normal ?
Jean
 
I can't understand why this server is running like crazy .... Here is the last TOP :

19:32:39 up 37 min, 1 user, load average: 9.80, 13.99, 13.87
118 processes: 107 sleeping, 11 running, 0 zombie, 0 stopped
19:33:11 up 37 min, 1 user, load average: 8.84, 13.35, 13.66
118 processes: 109 sleeping, 9 running, 0 zombie, 0 stopped
CPU states: cpu user nice system irq softirq iowait idle
total 89.0% 0.0% 10.9% 0.0% 0.0% 0.0% 0.0%
Mem: 1027288k av, 509804k used, 517484k free, 0k shrd, 38748k buff
415100k actv, 48960k in_d, 3680k in_c
Swap: 2040244k av, 0k used, 2040244k free 224184k cached

PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND
7119 mysql 22 0 37180 36M 3108 R 11.1 3.6 0:00 0 mysqld
7120 mysql 22 0 37180 36M 3108 R 10.7 3.6 0:00 0 mysqld
7116 mysql 23 0 37180 36M 3108 S 8.7 3.6 0:00 0 mysqld
7118 mysql 23 0 37180 36M 3108 R 8.5 3.6 0:00 0 mysqld
7121 mysql 22 0 37180 36M 3108 R 8.5 3.6 0:00 0 mysqld
7117 mysql 23 0 37180 36M 3108 S 7.7 3.6 0:00 0 mysqld
5467 apache 15 0 15112 14M 7356 S 6.5 1.4 0:04 0 httpd
7122 mysql 22 0 37180 36M 3108 R 6.1 3.6 0:00 0 mysqld
6986 apache 15 0 13572 13M 7228 S 4.9 1.3 0:01 0 httpd
5498 apache 15 0 14376 14M 7256 R 4.5 1.3 0:05 0 httpd
6537 apache 15 0 13556 13M 7224 S 2.5 1.3 0:01 0 httpd
7123 mysql 21 0 37180 36M 3108 R 2.1 3.6 0:00 0 mysqld
5876 apache 15 0 14656 14M 7484 S 1.7 1.4 0:04 0 httpd
5886 apache 16 0 14664 14M 7488 S 1.5 1.4 0:04 0 httpd
6706 apache 16 0 13968 13M 7228 S 1.3 1.3 0:01 0 httpd
7021 apache 15 0 13924 13M 7240 S 1.3 1.3 0:00 0 httpd
5925 apache 15 0 14088 13M 7216 S 1.1 1.3 0:02 0 httpd
1782 mysql 16 0 37180 36M 3108 S 0.1 3.6 0:00 0 mysqld
7106 root 15 0 1080 1080 820 R 0.1 0.1 0:00 0 top
1 root 15 0 500 500 444 S 0.0 0.0 0:03 0 init

What can be that wrong, that suddently it use so much CPU and load ???
And, no swap, and only 500mb ram of 1024mb ....
:confused:

Jean
 
Well you can start to take your forum offline for a minute .. just to check whether THAT is the cause.

And yes .. if you have for example a front-page with a lot of queries and concurrent visitors .. that might boost your CPU load.

You can also restart Apache and MySQL .. and see whether there are some 'log messages' during restart.

Also do a 'netstat -anp' and 'lsof | grep TCP' to see whether there are some strange connections going on.
And check your /tmp for possible processes installed during hacks of (for example) a forum.
 
hmmm, there is nothing to find .....
I searched around a how to upgrade mysql to 4.0.x, but i think that i will not do that.
The server worked fine for weeks, and since some days the customer complain that the pages are slow.
Right now, it's extremly slow ... :(
Load : 16.00
CPU : 85%
I'm going crazy. It's like a SYN attack, but there is nothing to find ....
Actually, i have the Plesk 7.5.3 firewall, but i think to swhitch to APF.
Anybody have a idea ?
Jean
 
Nothing wrong with Plesk's firewall .. it both uses iptables .. so just stick with it.

What process is using all the cpu time ? Is that the mysqld ?

Does the CPU load gets normal when you stop mysqld ?

Maybe you can logon to mysql .. check which databases you have .. what applications are using those databases .. and try to fix/analyze and optimize the databases.
 
Yes, MySQL was using all the CPU.
I upgraded to MySQL-4.0.24 and the load 'seems' to go a little down.
While i stopped https and Mysql to upgrade, the server load was about 0.
I think that the only DB used is the one of our customer, running vbulletin v 3.0.6
I run again a MySQL optimize right after the update.
What should i do after the update ?
Here is my actual /etc/my.cnf :
[mysqld]
safe-show-database
innodb_data_file_path=ibdata1:10M:autoextend
set-variable=innodb_additional_mem_pool_size=8M
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
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=10000
myisam_sort_buffer_size=64M
log-bin
server-id=1

[mysql.server]
user=mysql
basedir=/var/lib

[safe_mysqld]
err-log=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

[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

and there the output of mysql.log :
050615 20:50:03 /usr/sbin/mysqld: Shutdown Complete

050615 20:50:03 mysqld ended

050615 20:50:04 mysqld started
050615 20:50:04 Warning: Asked for 196608 thread stack, but got 126976
050615 20:50:04 InnoDB: Started
/usr/sbin/mysqld: ready for connections.
Version: '4.0.24-standard-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Official MySQL RPM

There is again a warning, but MySQL is up and running ....
MRTG show me that there are only 20 or 25 current connections. It should not produce such a load, no ?
Jean
 
Back
Top