SEO

Hi folks,

CentOS 4.4 amd64

I have been stuck on creating root password;

# mysqladmin -u root password yourrootsqlpassword# su -
did not help.

Pls advise how to locate mysql’s hostname.pid file?

Then to run;
# kill `cat /mysql-data-directory/host_name.pid`
mysqld_safe –skip-grant-tables &
mysqladmin -u root flush-privileges password “newpassword”

OR is there any other way to fix this problem. TIA


B.R.
satimis
--
View this message in context: http://www.nabble.com/Problem-on-cre....html#a9709718
Sent from the MySQL - General mailing list archive at Nabble.com.

In news:9709718.post@talk.nabble.com,
satimis <satimis@yahoo.com> wrote:

> Pls advise how to locate mysql=E2=80=99s hostname.pid file?

Try looking in standard directories such as:

/var/run/mysqld or /var/run/mysql or /var/run
The filename can be in form of 'hostname.pid', but it will rather be named
'mysqld.pid'.

Alternatively, if you have slocate package installed and the database is
running for some time now (a day or so), you may try to run

# locate mysqld.pid
/var/run/mysqld/mysqld.pid

The tool will tell you where the file should be.

> Then to run;
> # kill `cat /mysql-data-directory/host_name.pid`
> mysqld_safe =E2=80=93skip-grant-tables &
> mysqladmin -u root flush-privileges password
> =E2=80=9Cnewpassword=E2=80=9D

The other way to find out the process ID of MySQL is looking at the process
list with 'ps' or 'pstree'.

# ps axf | grep "[m]ysqld"
9238 ? Ssl 0:01 /usr/sbin/mysqld --defaults-file=...

# pstree -p mysql
mysqld(9238)-+-{mysqld}(9245)
|-{mysqld}(9246)
|-{mysqld}(9247)
|-{mysqld}(9248)
....

In this case 9238 is the PID you would need to send TERM signal to in order
to stop mysql server:
# kill 20868

Maciek

Hi Maciej Dobrzanski,

This is a new installation. I'm now tuning MySQL.

[root@server /]# ls /var/run/mysqld/
mysqld.pid

I got it.


Re running
kill `cat /var/run/mysqld/mysqld.pid`
mysqld_safe –skip-grant-tables &
mysqladmin -u root flush-privileges password mysqlroopassword


I suppose they are 3 lines.


[root@server /]# kill `cat /var/run/mysqld/mysqld.pid`
(No complaint)


[root@server /]# mysqld_safe –skip-grant-tables &
[1] 5119
[root@server /]# Starting mysqld daemon with databases from /var/lib/mysql
STOPPING server from pid file /var/run/mysqld/mysqld.pid
070328 19:39:12 mysqld ended

(It hung here)

Pls advise how to proceed. TIA

B.R.
satimis
--
View this message in context: http://www.nabble.com/Problem-on-cre....html#a9712041
Sent from the MySQL - General mailing list archive at Nabble.com.

In news:9712041.post@talk.nabble.com,
satimis <satimis@yahoo.com> wrote:

> [root@server /]# mysqld_safe =E2=80=93skip-grant-tables &
> [1] 5119
> [root@server /]# Starting mysqld daemon with databases from
> /var/lib/mysql STOPPING server from pid file
> /var/run/mysqld/mysqld.pid 070328 19:39:12 mysqld ended

See the error log for details of why the server stopped. It is usually
located either in /var/log (or its subdirectories, such us /var/log/mysql)
or in mysql data directory, which in your case is /var/lib/mysql. The error
log filename pattern is 'something.err' (hostname.err, mysqld.err, etc.).
The mysqld_safe script should by executed with --skip-grant-tables option:

# mysqld_safe --skip-grant-tables &

Maciek

Hi Maciej,

# find / -name *.err
find: /proc/4132/task: No such file or directory
find: /var/named/chroot/proc/4132/task: No such file or directory
" end *

# find / -name .err
same result

# ls /var/lib/mysql/
ibdata1 ib_logfile0 ib_logfile1 mysql mysql.sock test

# ls /var/lib/mysql/mysql
columns_priv.frm help_category.frm help_topic.frm time_zone.frm
time_zone_transition.frm
columns_priv.MYD help_category.MYD help_topic.MYD
time_zone_leap_second.frm time_zone_transition.MYD
columns_priv.MYI help_category.MYI help_topic.MYI
time_zone_leap_second.MYD time_zone_transition.MYI
db.frm help_keyword.frm host.frm
time_zone_leap_second.MYI time_zone_transition_type.frm
db.MYD help_keyword.MYD host.MYD time_zone.MYD
time_zone_transition_type.MYD
db.MYI help_keyword.MYI host.MYI time_zone.MYI
time_zone_transition_type.MYI
func.frm help_relation.frm tables_priv.frm time_zone_name.frm
user.frm
func.MYD help_relation.MYD tables_priv.MYD time_zone_name.MYD
user.MYD
func.MYI help_relation.MYI tables_priv.MYI time_zone_name.MYI
user.MYI
* end *

# ls /var/log/
acpid boot.log.1 lastlog messages.1 rpmpkgs.1
spooler.1 yum.log
anaconda.log cron mail mysqld.log samba
squid
anaconda.syslog cron.1 maillog nvidia-installer.log
scrollkeeper.log vbox
anaconda.xlog cups maillog.1 ppp secure
wtmp
audit dmesg mcelog prelink.log secure.1
Xorg.0.log
boot.log httpd messages rpmpkgs spooler
Xorg.0.log.old
* end *


Read /var/log/mysql.log
Can't find anything related.


satimis
--
View this message in context: http://www.nabble.com/Problem-on-cre....html#a9713069
Sent from the MySQL - General mailing list archive at Nabble.com.

In news:9712041.post@talk.nabble.com,
satimis <satimis@yahoo.com> wrote:

> [root@server /]# mysqld_safe =E2=80=93skip-grant-tables &
> [1] 5119
> [root@server /]# Starting mysqld daemon with databases from
> /var/lib/mysql STOPPING server from pid file
> /var/run/mysqld/mysqld.pid 070328 19:39:12 mysqld ended

Hmm, I haven't used mysqld_safe script for a long time, but from what I can
see the message "STOPPING server from pid file" only appears if the server
process dies and pid file is not found (it is removed by mysqld as it closes
cleanly). Try running mysqld_safe with additional
parameter: --log-error=/var/lib/mysql/my.err. Then check what has been
written into that file.

Maciek

Has anyone found a way to get a result set with the current row return
number in a select statement without using vars?

select concat('Test row ',currentreturnrownum()) as testdata , mytestdata
from mytestdatatable;


+------------------------+-------------------+
|Test row 1 | testdata |
|Test row 2 | testdata |
|Test row 3 | testdata |
|Test row 4 | testdata |
|Test row 5 | testdata |
|Test row 6 | testdata |
|Test row 7 | testdata |
|Test row 8 | testdata |
|Test row 9 | testdata |
+------------------------+-------------------+
(9 rows returned)




Wishing you the best you know you deserve,

______________________
Lucas Heuman
CM Web Developer
SRA International, Inc.
FAA, WJHTC/Bldg 300, 2nd Fl., H33
Atlantic City Int'l Airport, NJ 08405
Phone 609.485.5401

Hi Maciej,

[root@server ~]# kill `cat /var/run/mysqld/mysqld.pid`
No complaint

[root@server ~]# /etc/init.d/mysqld restart
Stopping MySQL: [FAILED]
Starting MySQL: [ OK ]

# kill `cat /var/run/mysqld/mysqld.pid`
No complaint

[root@server ~]# /etc/init.d/mysqld status
mysqld dead but subsys locked
* end *

[root@server ~]# mysqld_safe --skip-grant-tables &
--log-error=/var/lib/mysql/my.err
[1] 4579
bash: --log-error=/var/lib/mysql/my.err: No such file or directory
[root@server ~]# Starting mysqld daemon with databases from /var/lib/mysql

* end *
Hung here.

# find / -name my.err
find: /proc/4175/task: No such file or directory
/var/lib/mysql/my.err
find: /var/named/chroot/proc/4175/task: No such file or directory
* end *

# cat /var/lib/mysql/my.err
A mysqld process already exists at Wed Mar 28 23:53:04 HKT 2007
070328 23:54:07 mysqld started
070328 23:54:07 InnoDB: Started; log sequence number 0 43634
/usr/libexec/mysqld: ready for connections.
Version: '4.1.20' socket: '/var/lib/mysql/mysql.sock' port: 3306 So
urce distribution
070328 23:56:06 [Note] /usr/libexec/mysqld: Normal shutdown

070328 23:56:06 InnoDB: Starting shutdown...
070328 23:56:09 InnoDB: Shutdown completed; log sequence number 0 436
34
070328 23:56:09 [Note] /usr/libexec/mysqld: Shutdown complete

070328 23:56:09 mysqld ended
* end *


satimis
--
View this message in context: http://www.nabble.com/Problem-on-cre....html#a9717062
Sent from the MySQL - General mailing list archive at Nabble.com.

Hi Maciej,

I found that I made a mistake from the beginning

# mysqladmin -u root password yourrootsqlpassword
leaving out "--" before "password"


Retried as follows;

[root@server ~]# mysqladmin -u root --password mypassword
Enter password:


Typing either "mypassword" or "YES" prompted;
mysqladmin: connect to server at 'localhost' failed
error: 'Access denied for user 'root'@'localhost' (using password: YES)'
* end *

Still failed


satimis
--
View this message in context: http://www.nabble.com/Problem-on-cre....html#a9726511
Sent from the MySQL - General mailing list archive at Nabble.com.

> Retried as follows;
>
> [root@server ~]# mysqladmin -u root --password mypassword
> Enter password:
>
>
> Typing either "mypassword" or "YES" prompted;
> mysqladmin: connect to server at 'localhost' failed
> error: 'Access denied for user 'root'@'localhost' (using password: YES)'
> * end *

That is asking for your *old* password.

mysqladmin --help tells you this.