DragonFly BSD
DragonFly users List (threaded) for 2006-06
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: MySQL 4.1.19 server setup got stuck in a loop


To: Gergo Szakal <bastyaelvtars@xxxxxxxxx>
From: Mark Cullen <mark.r.cullen@xxxxxxxxx>
Date: Wed, 07 Jun 2006 21:45:37 +0100

Gergo Szakal wrote:
On Mon, 05 Jun 2006 22:54:32 +0100
Mark Cullen <mark.r.cullen@xxxxxxxxx> wrote:

Recently installed MySQL from pkgsrc (same way as you described) and cannot confirm, works flawlessly.


Hi there,

I just now installed MySQL 4.1.19 from pkgsrc, trying to set up a DF box and see if I can get it all working properly before I even attempt to migrate from FreeBSD 4.11. Anyway, I copied the rc script, mysqld, from /usr/pkg/share/examples/rc.d/ to /usr/pkg/etc/rc.d, put "mysqld=yes" in /etc/rc.conf and then proceeded to run `/usr/pkg/etc/rc.d/mysqld start`.

As this was the first run, it appeared to run some kind of initialisation / setup script:

---
df# /usr/pkg/etc/rc.d/mysqld start
Initializing MySQL database system tables.
Installing all prepared tables
Fill help tables
---

It sat at "Fill help tables" for a rather long time:

---
load: 0.53  cmd: mysqld 76314 [running] 9.44u 29.35s 97% 7640k
load: 0.90  cmd: mysqld 76314 [running] 31.43u 101.62s 76% 7644k
load: 0.92  cmd: mysqld 76314 [running] 32.67u 105.74s 97% 7644k
load: 0.92  cmd: mysqld 76314 [running] 32.91u 106.38s 95% 7644k
load: 0.92  cmd: mysqld 76314 [running] 33.09u 106.98s 97% 7644k
load: 0.92  cmd: mysqld 76314 [running] 33.34u 107.62s 97% 7644k
load: 0.96  cmd: mysqld 76314 [running] 44.30u 141.85s 97% 7644k
load: 0.96  cmd: mysqld 76314 [running] 44.85u 143.44s 97% 7644k
load: 1.87  cmd: mysqld 76314 [running] 64.96u 206.69s 49% 7644k
load: 1.87  cmd: mysqld 76314 [running] 65.33u 208.05s 44% 7644k
---

It was using 100% CPU time (the last couple I was compiling pure-ftpd, so it didn't get it all). Anyway, at this point I did a `truss` on the process (maybe I should have used ktrace?!) and got the following two lines repeated, over and over:

---
sigprocmask(0x1,0x28391da0,0xbfafef10)           = 0 (0x0)
sigprocmask(0x3,0xbfafef10,0x0)                  = 0 (0x0)
---

I'm not sure if that's any use to anyone? Any idea's what went wrong here? I ctrl+c'd it and ran the script again and the server has actually started just fine, and I can login at least (that's as far as I have tested so far).

DragonFly df.bone.servebeer.com 1.4.4-RELEASE DragonFly 1.4.4-RELEASE #1: Sat Apr 22 10:46:47 PDT 2006 root@:/home/usr.obj/usr/src/sys/GENERIC i386

Any more info needed I will gladly provide it.

Thanks,
Mark

Yep, very odd.


I have done another fresh install and did not run in to this problem at all!

A very hard to trigger bug somewhere?



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]