| View previous topic :: View next topic |
| Author |
Message |
Aaron Gray
Guest
|
 Posted: Fri Oct 24, 2008 2:19 pm Post subject: Unable to start mysqld on old Fedora Core 4 machine |
 |
|
I am trying to get mysqld to run on an old Fedora Core 4 machine; updaing to
later FC is not possible on this machine at this time.
I am getting the message 'Timeout error occured trying to start MySQL Demon.
Starting MySQL: [FAILED]'
I am not sure this maybe a firewall problem, but I cannot remember where the
firewall config files are ?
Help !
Many thanks in advance,
Aaron |
|
| |
|
 Back to top |
Aaron Gray
Guest
|
| Posted: Fri Oct 24, 2008 2:42 pm Post subject: Re: Unable to start mysqld on old Fedora Core 4 machine |
|
|
"Aaron Gray" <ang.usenet@gmail.com> wrote in message
news:6mdi8gFg8s71U1@mid.individual.net...
| Quote: | I am trying to get mysqld to run on an old Fedora Core 4 machine; updaing
to later FC is not possible on this machine at this time.
I am getting the message 'Timeout error occured trying to start MySQL
Demon. Starting MySQL: [FAILED]'
I am not sure this maybe a firewall problem, but I cannot remember where
the firewall config files are ?
|
Okay got it /etc/sysconfig/iptables looking at my other working FC5 machine
I cannot see anything needed in iptables.
Double Help !
Aaron |
|
| |
|
| Back to top |
Jasen Betts
Guest
|
| Posted: Fri Oct 24, 2008 3:56 pm Post subject: Re: Unable to start mysqld on old Fedora Core 4 machine |
|
|
On 2008-10-24, Aaron Gray <ang.usenet@gmail.com> wrote:
| Quote: | I am trying to get mysqld to run on an old Fedora Core 4 machine; updaing to
later FC is not possible on this machine at this time.
I am getting the message 'Timeout error occured trying to start MySQL Demon.
Starting MySQL: [FAILED]'
|
try and locate a more detailed error message.
somewhere one hopes MYSQL has written what it was trying to do that
timed out.
| Quote: | I am not sure this maybe a firewall problem, but I cannot remember where the
firewall config files are ?
|
timeouts are usually caused by inavailability of something outside the
box (this can be caused by firewalls) could it possibly be an inability
to resolve a name (a DNS/YP/NIS problem?) I can't immagine MySQL doing
anything else at startup that could cause this problem.
Bye.
Jasen |
|
| |
|
| Back to top |
Aaron Gray
Guest
|
| Posted: Fri Oct 24, 2008 3:59 pm Post subject: Re: Unable to start mysqld on old Fedora Core 4 machine |
|
|
"Jasen Betts" <jasen@xnet.co.nz> wrote in message
news:gds9lg$8kd$1@reversiblemaps.ath.cx...
| Quote: | On 2008-10-24, Aaron Gray <ang.usenet@gmail.com> wrote:
I am trying to get mysqld to run on an old Fedora Core 4 machine; updaing
to
later FC is not possible on this machine at this time.
I am getting the message 'Timeout error occured trying to start MySQL
Demon.
Starting MySQL: [FAILED]'
try and locate a more detailed error message.
somewhere one hopes MYSQL has written what it was trying to do that
timed out.
I am not sure this maybe a firewall problem, but I cannot remember where
the
firewall config files are ?
timeouts are usually caused by inavailability of something outside the
box (this can be caused by firewalls) could it possibly be an inability
to resolve a name (a DNS/YP/NIS problem?) I can't immagine MySQL doing
anything else at startup that could cause this problem.
|
I am getting the following in /var/log/mysqld.log
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
081024 14:39:24 mysqld started
081024 14:39:25 [ERROR] Can't start server : Bind on unix socket: No space
left on device
081024 14:39:25 [ERROR] Do you already have another mysqld server running on
socket: /var/lib/mysql/mysql.sock ?
081024 14:39:25 [ERROR] Aborting
081024 14:39:25 [Note] /usr/libexec/mysqld: Shutdown complete
081024 14:39:25 mysqld ended
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
BTW /var/lib/mysql/mysql.sock does not exist
Anyone throw any light on this ?
Many thanks in advance,
Aaron |
|
| |
|
| Back to top |
noi ance
Guest
|
| Posted: Fri Oct 24, 2008 11:19 pm Post subject: Re: Unable to start mysqld on old Fedora Core 4 machine |
|
|
On Fri, 24 Oct 2008 14:34:15 +0100, Aaron Gray typed this message:
| Quote: | "Jasen Betts" <jasen@xnet.co.nz> wrote in message
news:gds9lg$8kd$1@reversiblemaps.ath.cx...
On 2008-10-24, Aaron Gray <ang.usenet@gmail.com> wrote:
I am trying to get mysqld to run on an old Fedora Core 4 machine;
updaing to
later FC is not possible on this machine at this time.
I am getting the message 'Timeout error occured trying to start MySQL
Demon.
Starting MySQL: [FAILED]'
try and locate a more detailed error message. somewhere one hopes MYSQL
has written what it was trying to do that timed out.
I am not sure this maybe a firewall problem, but I cannot remember
where the
firewall config files are ?
timeouts are usually caused by inavailability of something outside the
box (this can be caused by firewalls) could it possibly be an inability
to resolve a name (a DNS/YP/NIS problem?) I can't immagine MySQL doing
anything else at startup that could cause this problem.
I am getting the following in /var/log/mysqld.log
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
081024 14:39:24 mysqld started
081024 14:39:25 [ERROR] Can't start server : Bind on unix socket: No
space left on device
081024 14:39:25 [ERROR] Do you already have another mysqld server
running on socket: /var/lib/mysql/mysql.sock ?
081024 14:39:25 [ERROR] Aborting
081024 14:39:25 [Note] /usr/libexec/mysqld: Shutdown complete
081024 14:39:25 mysqld ended
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
BTW /var/lib/mysql/mysql.sock does not exist
Anyone throw any light on this ?
Many thanks in advance,
Aaron
|
Do you have the correct permissions on the /var/lib/mysql folders?
Difficult to diagnose without knowing what you've done.
Try
# mysqld --verbose
and
# mysqld --safe-mode --verbose |
|
| |
|
| Back to top |
Aaron Gray
Guest
|
| Posted: Fri Oct 24, 2008 11:57 pm Post subject: Re: Unable to start mysqld on old Fedora Core 4 machine |
|
|
"noi ance" <noi@siam.com> wrote in message
news:EkoMk.2869$pr6.53@flpi149.ffdc.sbc.com...
| Quote: | On Fri, 24 Oct 2008 14:34:15 +0100, Aaron Gray typed this message:
"Jasen Betts" <jasen@xnet.co.nz> wrote in message
news:gds9lg$8kd$1@reversiblemaps.ath.cx...
On 2008-10-24, Aaron Gray <ang.usenet@gmail.com> wrote:
I am trying to get mysqld to run on an old Fedora Core 4 machine;
updaing to
later FC is not possible on this machine at this time.
I am getting the message 'Timeout error occured trying to start MySQL
Demon.
Starting MySQL: [FAILED]'
try and locate a more detailed error message. somewhere one hopes MYSQL
has written what it was trying to do that timed out.
I am not sure this maybe a firewall problem, but I cannot remember
where the
firewall config files are ?
timeouts are usually caused by inavailability of something outside the
box (this can be caused by firewalls) could it possibly be an inability
to resolve a name (a DNS/YP/NIS problem?) I can't immagine MySQL doing
anything else at startup that could cause this problem.
I am getting the following in /var/log/mysqld.log
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
081024 14:39:24 mysqld started
081024 14:39:25 [ERROR] Can't start server : Bind on unix socket: No
space left on device
081024 14:39:25 [ERROR] Do you already have another mysqld server
running on socket: /var/lib/mysql/mysql.sock ?
081024 14:39:25 [ERROR] Aborting
081024 14:39:25 [Note] /usr/libexec/mysqld: Shutdown complete
081024 14:39:25 mysqld ended
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
BTW /var/lib/mysql/mysql.sock does not exist
Anyone throw any light on this ?
Many thanks in advance,
Aaron
Do you have the correct permissions on the /var/lib/mysql folders?
Difficult to diagnose without knowing what you've done.
Try
# mysqld --verbose
and
# mysqld --safe-mode --verbose
|
mysqld_safe --verbose
gives the following in '/var/log/mysqld.log' :-
~~~~~~~~~~~~~~~~~~~~~~~~~
081024 20:08:01 mysqld started
InnoDB: Error: auto-extending data file ./ibdata1 is of a different size
InnoDB: 0 pages (rounded down to MB) than specified in the .cnf file:
InnoDB: initial 640 pages, max 0 (relevant if non-zero) pages!
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data files, and it failed here,
InnoDB: you should now edit innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB only wrote those files full of
InnoDB: zeros, but did not yet use them in any way. But be careful: do not
InnoDB: remove old data files which contain your precious data!
081024 20:08:02 [ERROR] Can't init databases
081024 20:08:02 [ERROR] Aborting
081024 20:08:02 [Note] /usr/libexec/mysqld: Shutdown complete
081024 20:08:02 mysqld ended
~~~~~~~~~~~~~~~~~~~~~~~~~~
I have no data on this machine. Can I reset the database file(s) ?
Aaron |
|
| |
|
| Back to top |
noi ance
Guest
|
| Posted: Sun Oct 26, 2008 5:00 am Post subject: Re: Unable to start mysqld on old Fedora Core 4 machine |
|
|
On Fri, 24 Oct 2008 19:57:34 +0100, Aaron Gray typed this message:
| Quote: | "noi ance" <noi@siam.com> wrote in message
news:EkoMk.2869$pr6.53@flpi149.ffdc.sbc.com...
On Fri, 24 Oct 2008 14:34:15 +0100, Aaron Gray typed this message:
"Jasen Betts" <jasen@xnet.co.nz> wrote in message
news:gds9lg$8kd$1@reversiblemaps.ath.cx...
On 2008-10-24, Aaron Gray <ang.usenet@gmail.com> wrote:
I am trying to get mysqld to run on an old Fedora Core 4 machine;
updaing to
later FC is not possible on this machine at this time.
I am getting the message 'Timeout error occured trying to start
MySQL Demon.
Starting MySQL: [FAILED]'
try and locate a more detailed error message. somewhere one hopes
MYSQL has written what it was trying to do that timed out.
I am not sure this maybe a firewall problem, but I cannot remember
where the
firewall config files are ?
timeouts are usually caused by inavailability of something outside
the box (this can be caused by firewalls) could it possibly be an
inability to resolve a name (a DNS/YP/NIS problem?) I can't immagine
MySQL doing anything else at startup that could cause this problem.
I am getting the following in /var/log/mysqld.log
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
081024 14:39:24 mysqld started
081024 14:39:25 [ERROR] Can't start server : Bind on unix socket: No
space left on device
081024 14:39:25 [ERROR] Do you already have another mysqld server
running on socket: /var/lib/mysql/mysql.sock ? 081024 14:39:25 [ERROR]
Aborting
081024 14:39:25 [Note] /usr/libexec/mysqld: Shutdown complete
081024 14:39:25 mysqld ended
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
BTW /var/lib/mysql/mysql.sock does not exist
Anyone throw any light on this ?
Many thanks in advance,
Aaron
Do you have the correct permissions on the /var/lib/mysql folders?
Difficult to diagnose without knowing what you've done.
Try
# mysqld --verbose
and
# mysqld --safe-mode --verbose
mysqld_safe --verbose
gives the following in '/var/log/mysqld.log' :-
~~~~~~~~~~~~~~~~~~~~~~~~~
081024 20:08:01 mysqld started
InnoDB: Error: auto-extending data file ./ibdata1 is of a different size
InnoDB: 0 pages (rounded down to MB) than specified in the .cnf file:
InnoDB: initial 640 pages, max 0 (relevant if non-zero) pages! InnoDB:
Could not open or create data files. InnoDB: If you tried to add new
data files, and it failed here, InnoDB: you should now edit
innodb_data_file_path in my.cnf back InnoDB: to what it was, and remove
the new ibdata files InnoDB created InnoDB: in this failed attempt.
InnoDB only wrote those files full of InnoDB: zeros, but did not yet use
them in any way. But be careful: do not InnoDB: remove old data files
which contain your precious data! 081024 20:08:02 [ERROR] Can't init
databases 081024 20:08:02 [ERROR] Aborting
081024 20:08:02 [Note] /usr/libexec/mysqld: Shutdown complete
081024 20:08:02 mysqld ended
~~~~~~~~~~~~~~~~~~~~~~~~~~
I have no data on this machine. Can I reset the database file(s) ?
Aaron
|
Looks like you're using InnoDB which is auto-extending and you're running
out of space most likely for the extents. What allocations did you set
in ~/.my.cnf ?
Check the MySQL manual for minimum size allocations for the InnoDB. |
|
| |
|
| Back to top |
Jasen Betts
Guest
|
| Posted: Mon Oct 27, 2008 7:25 am Post subject: Re: Unable to start mysqld on old Fedora Core 4 machine |
|
|
On 2008-10-24, Aaron Gray <ang.usenet@gmail.com> wrote:
| Quote: | 081024 14:39:24 mysqld started
081024 14:39:25 [ERROR] Can't start server : Bind on unix socket: No space
left on device
|
AFAICT 'ENOSPC' is not a valid return for socket(PF_UNIX,...), or bind.
but anyway, run '/bin/df' and post the output.
Bye.
Jasen |
|
| |
|
| Back to top |
Lawrence D'Oliveiro
Guest
|
| Posted: Mon Oct 27, 2008 7:25 am Post subject: Re: Unable to start mysqld on old Fedora Core 4 machine |
|
|
In message <6me16rFgdegcU1@mid.individual.net>, Aaron Gray wrote:
| Quote: | 081024 14:39:25 [ERROR] Can't start server : Bind on unix socket: No space
left on device
|
My experience with "no space left on device" is that it means what it says:
you've managed to completely fill up a disk partition. |
|
| |
|
| Back to top |
JAM
Guest
|
| Posted: Tue Oct 28, 2008 1:40 pm Post subject: Re: Unable to start mysqld on old Fedora Core 4 machine |
|
|
On Oct 24, 6:34 am, "Aaron Gray" <ang.use...@gmail.com> wrote:
| Quote: | "Jasen Betts" <ja...@xnet.co.nz> wrote in message
news:gds9lg$8kd$1@reversiblemaps.ath.cx...
On 2008-10-24, Aaron Gray <ang.use...@gmail.com> wrote:
I am trying to get mysqld to run on an old Fedora Core 4 machine; updaing
to
later FC is not possible on this machine at this time.
I am getting the message 'Timeout error occured trying to start MySQL
Demon.
Starting MySQL: [FAILED]'
try and locate a more detailed error message.
somewhere one hopes MYSQL has written what it was trying to do that
timed out.
I am not sure this maybe a firewall problem, but I cannot remember where
the
firewall config files are ?
timeouts are usually caused by inavailability of something outside the
box (this can be caused by firewalls) could it possibly be an inability
to resolve a name (a DNS/YP/NIS problem?) I can't immagine MySQL doing
anything else at startup that could cause this problem.
I am getting the following in /var/log/mysqld.log
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
081024 14:39:24 mysqld started
081024 14:39:25 [ERROR] Can't start server : Bind on unix socket: No space
left on device
081024 14:39:25 [ERROR] Do you already have another mysqld server running on
socket: /var/lib/mysql/mysql.sock ?
081024 14:39:25 [ERROR] Aborting
081024 14:39:25 [Note] /usr/libexec/mysqld: Shutdown complete
081024 14:39:25 mysqld ended
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
BTW /var/lib/mysql/mysql.sock does not exist
Anyone throw any light on this ?
Many thanks in advance,
Aaron
|
check the space on disk....sometimes u get problems in starting
services if u have space issues.... |
|
| |
|
| Back to top |
Aaron Gray
Guest
|
| Posted: Wed Oct 29, 2008 7:53 pm Post subject: Re: Unable to start mysqld on old Fedora Core 4 machine |
|
|
"Jasen Betts" <jasen@xnet.co.nz> wrote in message
news:ge3b5j$9jr$1@reversiblemaps.ath.cx...
| Quote: | On 2008-10-24, Aaron Gray <ang.usenet@gmail.com> wrote:
081024 14:39:24 mysqld started
081024 14:39:25 [ERROR] Can't start server : Bind on unix socket: No
space
left on device
AFAICT 'ENOSPC' is not a valid return for socket(PF_UNIX,...), or bind.
but anyway, run '/bin/df' and post the output.
|
Yeah, I had run out of diskspace !
Aaron |
|
| |
|
| Back to top |
Aaron Gray
Guest
|
| Posted: Wed Oct 29, 2008 10:35 pm Post subject: Re: Unable to start mysqld on old Fedora Core 4 machine |
|
|
"Jasen Betts" <jasen@xnet.co.nz> wrote in message
news:ge3b5j$9jr$1@reversiblemaps.ath.cx...
| Quote: | On 2008-10-24, Aaron Gray <ang.usenet@gmail.com> wrote:
081024 14:39:24 mysqld started
081024 14:39:25 [ERROR] Can't start server : Bind on unix socket: No
space
left on device
AFAICT 'ENOSPC' is not a valid return for socket(PF_UNIX,...), or bind.
but anyway, run '/bin/df' and post the output.
|
Yeah, I realized I had run out of disk several days ago, but have not been
on list to report this.
sqld still refuses to run though.
Aaron |
|
| |
|
| Back to top |
|
