MySQL and FreeBSD 4.x.. problems, problems with server
This has happened with enough servers at different locations that I have to believe there is a relationship here. I have servers running the latest release of MySQL. I've run the servers on FreeBSD 4.4., 4.7, and 4.8. I am not using the threaded version. On all three versions, on different servers at different sites, I have seen MySQL just go wacky after a while. Two types of symptoms: 1. mysqld just decides to consume as much of the CPU as possible. 2. new connections to mysql fail It will usually take 1-3 weeks between occurances. I have seen posts relating to this off and on. Is there a known problem with running mysqld on FreeBSD 4.x? What about 5.x? Is it better? I was talking to another FreeBSD admin the other day and he commented on the same thing: mysqld on our FreeBSD 4.7 boxes just lose it sometimes. Honestly, I am thinking of converting out MySQL db servers from FreeBSD to Linux for this reason, and only this reason. Otherwise, I love FreeBSD, but this is just no good. I would blame myself, but I can't when I get wind that others are having the same problem. Yes, this is a mysql problem probably, and not a FreeBSD problem. However, I'm hoping to get some help or hope here as well as with the mysql people. :) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD NFS clients and mount options..
I am running an NFS server and several FreeBSD NFS clients. The NFS clients are web servers running Apache. I want to be sure that if my NFS server dies that I don't get odd problems (e.g., the default hard NFS option will cause the process to hang, and I can't kill it). I realize that the hard option is meant to support an NFS environment where a NFS server comes back up, and everything just pops back to normal, but that hasn't been my experience. I am willing to accept that if an NFS server dies that my processes will get errors from the IO operation. I am currently using these options in /etc/fstab: rw,bg,soft bg is essential for us since a server will hang on boot-up if an NFS server is down. It's amazing how if one server is down then chances are a lot of them are. Murphy's Law. What options do you feel the most comfortable with? We are willing to lose a new write to a file if an NFS server dies. It's more important that I can quickly bring the server back up using our backup NFS server for example. I can't do that if my process becomes completely unresponsive. Just asking for general feelings on this issue. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
NFS and different exports to the same host
Per the FreeBSD handbook, I have to follow the rule that for a specific host I have to export everything the same for a particular filesystem. So let's say I have one filesystem, /. So I can't have: /export1-roserver1 server2 /export2 server1 Instead, I need: /export1 \ /export2 \ server1 Is there a way around this? I have found that it works best for us to have a /exports, where we dump things like /exports/www, /exports/mail, and so on, rather than having filesystems for each of those. This is important since FreeBSD has a limitation on the number of possible slices, and we are running with one big RAID-1 storage system. Also, I found that this generates errors (by mountd -r): /export1 -maproot=nobody \ /export2 -maproot=root \ server1 While this works: /export1 \ /export2 \ -maproot=root \ server1 That's no good. Is there a solution to this problem? By the way, I have found that FreeBSD is a solid NFS server. Other than this limitation NFS has worked great. Handbook on NFS: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-nfs.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Determining free memory on FreeBSD 4.8-REL
I know this question has been asked, but the answers I find tend to be along the lines of Well, it's complicated. How do I determine if my FreeBSD is actually low on memory not? And what is Inact? I did read the manpages, but even they seem to skirt how I should view Inact vs. Free. (I did read the tuning manpage.) Let's say I have this: last pid: 23737; load averages: 0.21, 0.15, 0.27 up 5+20:43:14 15:22:31 231 processes: 1 running, 230 sleeping CPU states: 5.0% user, 0.0% nice, 2.7% system, 1.6% interrupt, 90.7% idle Mem: 76M Active, 25M Inact, 62M Wired, 2876K Cache, 35M Buf, 82M Free Swap: 496M Total, 41M Used, 456M Free, 8% Inuse So I have 82MB of free memory, 35MB of memory being used by the OS as disk IO, cache is different from Buf in some way or another (the top manpage doesn't quite go into details here). I don't quite get Inact and Wired. Why am I using 41MB of swap then if I have 82MB of free memory? On another box I have: last pid: 42029; load averages: 0.46, 0.38, 0.34 up 5+20:24:15 15:27:12 35 processes: 2 running, 33 sleeping CPU states: 1.0% user, 0.0% nice, 11.7% system, 6.1% interrupt, 81.3% idle Mem: 51M Active, 332M Inact, 97M Wired, 19M Cache, 61M Buf, 992K Free Swap: 1008M Total, 116K Used, 1008M Free 992K in Free but 332MB in Inact. So what is my conclusion here? That I have 332,992 KB free for use? Looking at vmstat I have no swapping going on: # vmstat 5 procs memory pagedisks faults cpu r b w avmfre flt re pi po fr sr ad0 ad4 in sy cs us sy id 3 0 0 189844 29624 80 0 0 0 442 375 0 0 2863 4011 564 3 6 90 (ignore) 2 0 0 188480 271322 0 0 0 829 714 0 0 5244 1041 667 1 9 90 2 0 0 188900 166601 0 0 0 1231 710 0 3 7215 1425 809 1 10 89 If I see ANY swapping going on should I worry? I don't think so. Some swapping is normal in UNIX in general. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
