Re: FreeBSD 7.2-RELEASE amd64 hangs
Hi, thank you very much for all the answers and ideas. We have found out that after the server was moved to different switch in the co-location centre the network interface and the switch auto-negotiated at the 10 Mbit Full Duplex mode. After setting it to GBit manually, everything seems to be working normally, but I am going to check it for some more time. SNMP connects to the local, isolated network from public and we have control over all the devices in the network. I will post if anything new happens, but for now it seems this throughput limitation was causing those issues (although I am still wondering why there is nothing in log files, but due to network overload every service we were trying to connect to through network was not working any more). Thank you for your time. BR, Matej On Fri, Dec 17, 2010 at 2:48 PM, krad kra...@gmail.com wrote: On 17 December 2010 13:47, krad kra...@gmail.com wrote: On 16 December 2010 17:42, Matej Šerc matej.s...@gmail.com wrote: Hi, I am experiencing a strange issue that has never occurred to me in all the years of using different versions of FreeBSD. One of our servers, which was running without any issues until yesterday, stopped responding for two times now - yesterday and today. About three days ago another process of pulling out SNMP data from devices was added, but I was looking the system load and the system was working normally and also processes were cmpleting successfully within the timeframe of 5 minutes (much faster, they completed in about 2 minutes). I also want to mention that those SNMP pulling processes were already working about a month or so on the same server (no hardware was changed in the meantime) and I am pretty sure that it should work normally as it did. My main problem is, that there is abcolutely nothing in log files - no errors, no warnings, nothing. No strange messages, every process just stops logging at one time and then continues after the reboot. Another interesting issue is that both hangs occured at approximately the same time, but there was nobody in the server room and also no one was logged into the server at that time except me. About 10 minutes before hang I was investigating processes and everything was very normal - no large CPU eating or memory eating processes. This might be interesting, even after every process stops responding, I was still able to ping the network interfaces and receive ICMP replies back. Of course my idea about it is that it must be connected to some hardware problems - my suggestion was to make some memory tests. But I would like to hear some your oppinions about the entire situation. Could some power supply issues be doing it? The server is about a year old and has, as I already mentioned, worked like a charm until now. How come there is no kernel panic since no daemon seems to be working? Why is network interface still up and working? I was unable to go to the co-location facility so I can't say what was on the screen at both times, but I suppose there was nothing else than messages I can read from log files. I know that 7.2 is pretty old version, but it was working until now on the same hardware and we had no reason to change that. Now the system is after reboot again running smoothly and without any issues at all. Thank you very much for any information regarding the issue. BR, Matej ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I'm not a huge fan of letting snmp spawn heavy weight scripts and processes as it is to easy for a remote machine to effectively dos the machine. I realise you are fairly sure the scripts arent an issue, but try croning them every 5 minutes, and writing the results to a file. SNMP can then simply retrieve the results from the file. This safeguard to to a certain extent, in that it stops many processes being spawned. All you have to watch after that is the job run time Also lets stops resources being tied up on the monitoring machine, as it doent have to hang around for x minutes for the results for its query ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 7.2-RELEASE amd64 hangs
Hi, I am experiencing a strange issue that has never occurred to me in all the years of using different versions of FreeBSD. One of our servers, which was running without any issues until yesterday, stopped responding for two times now - yesterday and today. About three days ago another process of pulling out SNMP data from devices was added, but I was looking the system load and the system was working normally and also processes were cmpleting successfully within the timeframe of 5 minutes (much faster, they completed in about 2 minutes). I also want to mention that those SNMP pulling processes were already working about a month or so on the same server (no hardware was changed in the meantime) and I am pretty sure that it should work normally as it did. My main problem is, that there is abcolutely nothing in log files - no errors, no warnings, nothing. No strange messages, every process just stops logging at one time and then continues after the reboot. Another interesting issue is that both hangs occured at approximately the same time, but there was nobody in the server room and also no one was logged into the server at that time except me. About 10 minutes before hang I was investigating processes and everything was very normal - no large CPU eating or memory eating processes. This might be interesting, even after every process stops responding, I was still able to ping the network interfaces and receive ICMP replies back. Of course my idea about it is that it must be connected to some hardware problems - my suggestion was to make some memory tests. But I would like to hear some your oppinions about the entire situation. Could some power supply issues be doing it? The server is about a year old and has, as I already mentioned, worked like a charm until now. How come there is no kernel panic since no daemon seems to be working? Why is network interface still up and working? I was unable to go to the co-location facility so I can't say what was on the screen at both times, but I suppose there was nothing else than messages I can read from log files. I know that 7.2 is pretty old version, but it was working until now on the same hardware and we had no reason to change that. Now the system is after reboot again running smoothly and without any issues at all. Thank you very much for any information regarding the issue. BR, Matej ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Multi-homed FreeBSD
Hi, we have a FreeBSD machine currently using PPPoE with NAT. As we already have the cable connection which is about the same speed, I was just wondering of doing some load balancing for the outside connection. I have no experiences with that and will be really glad if someone could point some things, where to look and what to read. Also your configurations and experiences regarding this fact are very welcome. Thanks, Matej ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Very slow disk speed / mpt0: LSILogic SAS/SATA Adapter
Hi, we have a HP ProLiant server with RAID 0/1 controller onboard. It is detected as mpt0 (I have attached a part of dmesg output at the end of the mail). As reported by some already ( http://www.mail-archive.com/freebsd-performa...@freebsd.org/msg02446.html), we are also getting extremely slow write speeds. I read somewhere that there are some improvements which could solve the situation in 7.2 (our system has 7.1 installed and I am currently unable to turn it off and it will stay so for at least 3 months). There are some information that setting hw.mpt.enable_sata_wc=1 solves the write speed (it actually does as I tested!), but I would like to know more about how danger that option is. We are using softupdates and now have this hw.mpt.enable_sata_wc=0, after reading that it might be very dangerous when using sata_wc=1. I am really looking forward to getting more information about this, it is actually driving me nuts. We have a number of other servers and there are no problems with RAID controllers at all. And as I said, I cannot actually turn of this machine and bring it back to reinstall new OS. Thank you very much for your comments and thoughts, Matej The server model is ML110G5. mpt0: LSILogic SAS/SATA Adapter port 0xd000-0xd0ff mem 0xfcefc000-0xfcef,0xfcee-0xfcee irq 16 at device 0.0 on pci5 mpt0: [ITHREAD] mpt0: MPI Version=1.5.16.0 mpt0: Capabilities: ( RAID-0 RAID-1E RAID-1 ) mpt0: 1 Active Volume (2 Max) mpt0: 3 Hidden Drive Members (10 Max) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Very slow disk speed / mpt0: LSILogic SAS/SATA Adapter
Hi, thank you very much for a very detailed answer. This machine is in co-location in a specialized data center which provides totally controlled environment (temperature, power etc.) and after being their partner for about 5 years now not a single power outage occured. Of course the data is backed-up regularily. One more question: where can I see if we are using background fsck? I occassionally run it to check for inconsistencies (as a forground - is this OK?). I suppose I can turn this write-caching on then. Thank you, Matej On Wed, Jun 17, 2009 at 2:48 PM, Erik Trulsson ertr1...@student.uu.sewrote: On Wed, Jun 17, 2009 at 01:35:52PM +0200, Matej ?erc wrote: Hi, we have a HP ProLiant server with RAID 0/1 controller onboard. It is detected as mpt0 (I have attached a part of dmesg output at the end of the mail). As reported by some already ( http://www.mail-archive.com/freebsd-performa...@freebsd.org/msg02446.html ), we are also getting extremely slow write speeds. I read somewhere that there are some improvements which could solve the situation in 7.2 (our system has 7.1 installed and I am currently unable to turn it off and it will stay so for at least 3 months). There are some information that setting hw.mpt.enable_sata_wc=1 solves the write speed (it actually does as I tested!), but I would like to know more about how danger that option is. We are using softupdates and now have this hw.mpt.enable_sata_wc=0, after reading that it might be very dangerous when using sata_wc=1. Not very dangerous at all, as long as you are not using background fsck. The problem with write caching on standard IDE/SATA drives is that they report that a write operation is finished even if it has only reached the disk's cache. This means that some of the guarantees that softupdates is supposed to provide regarding which order data is written to the disk, cannot be fulfilled. This essentially means that if you lose power to the machine unexpectedly you might have some filesystem inconsistencies afterward that you would not have had without the disks' cache being enabled. (A normal reset would not cause this problem since the disks would still retain the contents of their caches.) If you are using background fsck this could be a big problem, since for background fsck to work properly the only inconsistencies on the filesystem must be that some blocks are marked as in use when they actually are not. (That is one of the guarantees that softupdates is supposed to provide, but may not be able to provide due to the behaviour of the disks' cache.) If you do have other inconsistencies on the filesystem the whole system may throw a kernel panic when it encounters one of them. (A normal foreground fsck would fix all such inconsistencies before the system starts running for real.) It is also the case that if your system is really busy writing to the disks (with write caching enabled) and you lose power at exactly the wrong time you could potentially lose a lot of data from the filesystem, since any given write could theoretically get delayed indefinitely before it hits the disk's platters. (If the write that gets delayed is the creation of a directory in which lots of writes happen later you could lose all of them.) If you have write caching disabled you will not lose more than the last 30 seconds or so of updates. Using an UPS is one obvious way of drastically reducing the number of times the machine loses power unexpectedly, and if it is so important that this server is not taken down I assume you already have an UPS, in which case enabling the write caching is essentially riskfree. I am really looking forward to getting more information about this, it is actually driving me nuts. We have a number of other servers and there are no problems with RAID controllers at all. And as I said, I cannot actually turn of this machine and bring it back to reinstall new OS. Thank you very much for your comments and thoughts, Matej The server model is ML110G5. mpt0: LSILogic SAS/SATA Adapter port 0xd000-0xd0ff mem 0xfcefc000-0xfcef,0xfcee-0xfcee irq 16 at device 0.0 on pci5 mpt0: [ITHREAD] mpt0: MPI Version=1.5.16.0 mpt0: Capabilities: ( RAID-0 RAID-1E RAID-1 ) mpt0: 1 Active Volume (2 Max) mpt0: 3 Hidden Drive Members (10 Max) -- Insert your favourite quote here. Erik Trulsson ertr1...@student.uu.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xeon Quad with 9 GB RAM - only 4 GB detected
Hello, I have finished the installation and yes, the entire amount is detected. Is this normal behaveour (why does it happen?) Thanks, Matej On Wed, Apr 1, 2009 at 8:57 AM, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: just for sure - after installation is still 4GB detected (with generic kernel) or 9? On Tue, 31 Mar 2009, Matej Šerc wrote: Hi all, I am just trying to install FreeBSD 7.1 amd64 distro on the HP ML 150 G5 server and when booting, BIOS detects 9 GB of RAM, but when starting to install the system it is displayed that only 4 GBs are detected. Also the default swap partition size is 4 GB ... What would be the needed steps to enable FreeBSD using the entire memory in the machine? Thank you in advance for your time, Matej ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Xeon Quad with 9 GB RAM - only 4 GB detected
Hi all, I am just trying to install FreeBSD 7.1 amd64 distro on the HP ML 150 G5 server and when booting, BIOS detects 9 GB of RAM, but when starting to install the system it is displayed that only 4 GBs are detected. Also the default swap partition size is 4 GB ... What would be the needed steps to enable FreeBSD using the entire memory in the machine? Thank you in advance for your time, Matej ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
