Weird Bug with Admin CP > Service Monitor

J

Jing

Verified User
Joined
Jul 30, 2003
Messages
81
I have this weird bug with Service Monitor where it shows multiple processes of DNS and MySQL with the same ID. A screenshot is included below.

http://www2.uploadengine.com/getfile.php?file=1142089910F56FC.gif

Problem with this is that, I can't restart DNS or MySQL via the Admin CP anymore. It will just say "an error has occurred. Details" and then empty after details. But apart from this restart problem, everything else seems to be running fine.

Any idea what's going on?
 
What versions of named and mysql are you running?
Try to restart it from shell and after it, try restart it using DA
 
MySQL - 4.0.17
Bind - 9 (I think)

Tried restarting via SSH and it's still the same. It just shows another list of same process ids there.
 
You should have multiple process IDs; that's not a problem.

How are you restarting from the shell? If you restart from the shell using the startup scripts and then look at the logs you should see any error messages that occur.

If not then restart the daemons from the command line (not from a shell script) to see the error messages show up on the screen.

Jeff
 
I understand if multiple process of different IDs are alright, but a list of multiple same IDs seems really odd to me.

How do I restart it via daemon in shell actually? I was restarting it from .sh and there wasn't an error on my ssh. Which log should I look into?

Thanks a lot.
 
Hmmm... I didn't notice the pids were the same; that is odd.

Try from the shell:

ps waux | grep mysqld

and

ps waux | grep named

to see what's really running.

To shut down:

killall mysqld

and

killall named

and if that doesn't work (look at those ps lines again) you can try:

killall -9 mysqld

and

killall -9 named

but try to avoid that with mysqld; it could lose data.

Once ps shows nothing but "grep" lines, then you're ready to restart.

Find the line in your startup script that actually starts the daemon, and run it from the command line. Then you'll see the errors on the command line.

Jeff

If that doesn't work you can use kill
 
Hmm... I'm not quite sure if I'm doing it right. I have very limited knowledge with freebsd.

fairlady# killall named
fairlady# /usr/sbin/named.restart
ndc: error: name server was not running (warning only)
ndc: error: name server has not started (yet?)
fairlady# ps -aux | grep named
bind 88010 0.0 0.8 5908 4368 ?? Ss 1:30AM 0:00.09 /usr/sbin/named -u bind
fairlady#
Click to expand...

What's ndc?

On a sidenote, I can stop then start the processes from Admin CP without a problem. But even so it will still show a new list of same IDs.
 
I have even less FreeBSD knowledge, so hopefully someone else will respond.

However I know that if the DA control panel still shows PIDs, then the process is still running.

Unless there's a bug in DA.

How do you know it's not running?

Jeff
 
When I stop it, the Admin CP shows that "this service is stopped" or something similar. When I start it again, it just pops up this whole list of multiple, but same IDs once again.

This server has been running for 1 year plus and only past few months that I noticed it has such a weird problem.

I wonder if anyone else is having this problem. Mine is latest DA with Freebsd 5.3 by the way.
 
You must log in or register to reply here.
Back
Top