Administrator

We are happy to announce that the new version of our iOS app is in the Apple App Store review process now! Once approved, the app will be available for members to enjoy for just $1.99 one time. The new app will work with all IP.Board versions 3.3.2 or newer.This new version has a native interface, push notifications, iPad support, and multiple... View the full article View the full article

IPS prides itself on quality support and service. In response to continued growth, we are seeking dedicated people to provide support to our customers in a Tier 1 ("front line") position.Requirements:- Must be 18 or older.- English must be a primary language.- Ability to work in a team-oriented, customer-focused environment.- Excellent... View the full article View the full article

As of 3.3.0, IP.Board will direct you to the upgrade page if there are any detected upgraded available that you have uploaded to your site, there are some third party apps that also will trigger this as well, even if there are no upgrades available. To turn this feature off you can add this line to your global_config.php file define( "SKIP_UPGRADE_CHECK", true );

Invision Power Services, Inc. is pleased to announce the release of IP.Board 3.3.1, IP.Blog 2.5.2 and IP.SEO 1.5.2 Everyone at IPS is very proud of IP.Board 3.3.1, IP.Blog 2.5.2 and IP.SEO 1.5.2 updates. We have worked hard to create a quality, modern community platform and the feedback from our clients has been tremendous. We are releasing the following new software: IP.Board 3.3.1 Fully featured community platform including forums, members profiles, calendar, status system, integration, and much, much more. IP.Blog 2.5.2 Integrated blogging software for IP.Board. Allow your members to create and manage their own blogs. IP.SEO 1.5.2 Provides additional search engine optimization features and tools to our software such as site-maps and customisable metadata tags. Requirements / Notes IP.Blog and IP.SEO require IP.Board version 3.2.x or 3.3.x Installing / Upgrading For further assistance on installing these updates please refer to this document and for upgrading please refer to this document If you are using the archive system, first available in IP.Board 3.3.0, then you'll need to perform an additional step after upgrading. Security Updates for IP.Board 3.3.0, 3.2.x IP.Board 3.3.0 Simply upgrade to 3.3.1. Contact technical support if you need assistance. IP.Board 3.2.0, 3.2.1, 3.2.2, 3.2.3 Simply download the zip file and upload the files to your server. Directory structure has been retained so you can easily identify where to upload the files. 3_2_3_April_Patch.zip 56.63K 102 downloads Gallery 4.2.0, 4.2.1 Simply download the zip file and upload the file to your server. Directory structure has been retained so you can easily identify where to upload the files. Gallery_4_2_1_April.zip 4.02K 80 downloads View the full article

While working toward the release of IP.Board 3.3.0 and IP.Content 2.3.0, the development team took some time to refresh our developer documentation, aiming to provide useful information for our third party developers in order to help them update their work as necessary. We are still very much working on expanding and updating the developer documentation we...View the full article View the full article

Invision Power Services, Inc. is pleased to announce the release of IP.Board 3.3.0 and IP.Content 2.3.0!Everyone at IPS is very proud of IP.Board 3.3.0 and IP.Content 2.3.0 updates. We have worked hard to create a quality, modern community platform and the feedback from our clients has been tremendous.We are releasing the following new software:IP.Board 3.3.0Fully featured community platform including forums, members profiles, calendar, status system, integration, and much, much more.IP.Content 2.3.0Content management for your community - run a full web site or a simple community portal. The possibilities are endless.Release NotesThough IP.Board 3.3.0 and IP.Content 2.3.0 have been tested for months, you never know what you are going to get when thousands of people start using it overnight. Therefore: now that IP.Board 3.3.0 and IP.Content 2.3.0 will be used by a much larger audience we will probably come across as yet undiscovered bugs. You can expect maintenance releases as we work quickly to address any issues reported. We are now providing technical support and services for IP.Board 3.3.0 and IP.Content 2.3.0. As you might imagine, many thousands of clients will be asking for help so please note that if you request upgrade or install assistance that there could be a delay up to a few days to process that request. You may wish to take advantage of the automatic upload service in the client area to help upgrade your version. We may reply to this topic with hot-fix patches or notes if any critical issues come up so please use the "Follow this Topic" feature to get notified. If you experience any problems, before submitting a ticket, please disable all third party applications and hooks. You may wish to check our knowledge base for common upgrade issues. What's new in IP.Board 3.3In addition to this list there are countless other minor improvements and changes based on client feedback too numerous to mention. IP.Board 3.3 was all about polish so we hope you enjoy it.Archive System: New feature to archive off topics to remove post table overheadWarning System: New more flexible feature replaces old warning systemSEO Update: 'Dead end' links, unfriendly error pages, metadata tags, bounce ratesSEO Update: Banned usersSEO Update: Duplicate title tags, profile tabs, skin and language selectors, direct links to postsSEO Update: Microformat and Schema UpdatesSEO Update: Changes to tags, guests and unread links, title tags, soft 404s and schema additions for ratingsPerformance Updates: Improving topic markers, today's top posters, post table accessAuto-share on posting: Tweet and share to Facebook when creating a topicReputation Updates: Like/reputation updates on a user's profileMiscellaneous Updates: Log-in autosave, emoticons in signatures, log in as a member, duplicate forum, system schedular as a CRON and more.Applications and Hook Updates: Application ordering, hook list update, hook settingsModeration Tools Updates: Hide/Delete/Soft Delete consolidation and interface updatesWhat's new in IP.Content 2.3AdminCP Interface Part 1 & Admin CP Interface Part 2: Significant ACP interface changes to improve consistency, usability, clarity and approachabilitySEO Improvements: Duplication, header code, meta tag, page title and on-page HTML improvements, as well as a new URL memory systemCommenting & Other Enhancements: Improvements to commenting, quick navigation panel integration, reporting, reputation support and other article/database enhancementsNew Features: Currently viewing plugin block and shared media field for databasesTagging: Tag support implemented and a new tag cloud plugin block made availableNavigation Bar: Full tab control for the primary navigation barRelational Fields: Type-ahead relational fields and automatic cross-linking of related contentNexus: Nexus package, purchase, support request, shipping, invoices and transaction feeds, and donation plugin blockBlock Templates: New block templates functionality allowing developers to more easily share blocks and quality block templatesOdds & Ends: Updated default installation, ModCP integration, improved ACP logging, teaser paragraph article field and interface improvements View the full article

It has come to our attention that a XSS (Cross Site Scripting) attack is possible under specific circumstances when editing a post another member has made.This issue only exists in IP.Board 3.2.0, 3.2.1, 3.2.2 and 3.2.3. We recommend that everyone using these versions apply this simple two file patch.Simply download the zip, expand it on your computer and upload the files to the relevant folders on your server. The directory structure is maintained in the zip so you will have no issues finding the files.If you need assistance, please contact technical support.Patching 3.2.3 march-editor-patch_3_2.zip 30.13K 866 downloadsPatching 3.2.0-3.2.2Please upgrade to 3.2.3. Please note, this zip file is not compatible with 3.2.2, 3.2.1 or 3.2.0.Note: The main download zip has been updated . View the full article

Following on our previous blog entry about our enhancements to the IPS Community here at http://community.invisionpower.com ...A few more things to note that you may be interested in...View the full article View the full article

We are well into beta testing for IP.Board 3.3 and IP.Content 2.3 and so far it's going very well. Practically no bugs are being reported and often times our staff has literally 0 open general bugs in our bug tracker. That is quite and accomplishment and something of which we are very proud!If you are an IPS Client and are comfortable beta testing...View the full article View the full article

We are happy to announce that we have made a few changes to enhance the community experience here on the IPS Community.Access to Support ForumsBased on client feedback and the mass of good will from many helpful clients who want to assist others, we have opened up access to our support forums to both current, active license holders and those that...View the full article View the full article

We released IP.Board 3.3.0 as beta yesterday to our clients and I wanted to just round-up some of the very latest SEO changes we've made this week.We've invested a lot of effort into making sensible non-invasive changes to IP.Board to encourage search engines to spider pages we want them to spider and to remove extraneous links, potential crawler...View the full article View the full article

It has come to our attention that a XSS (Cross Site Scripting) attack is possible within the Admin CP. The javascript is only executed when viewing the detailed pop-up of a specific failed admin log in.This issue exists in all IP.Board 3 versions. We recommend that everyone using these versions apply this simple one file patch.Simply download the zip for your IP.Board version, expand the zip on your computer and upload the file to the relevant folder on your server. The directory structure is maintained in the zip so you will have no issues finding the file.If you need assistance, please contact technical support.IP.Board 3.2.x feb_3_2_x.zip 2.72K 4039 downloadsIP.Board 3.1.x feb-3_1_x.zip 2.76K 957 downloadsIP.Board 3.0.x feb-3_0_x.zip 2.76K 269 downloadsIf you are running a version of IP.Board older than those listed we highly recommend you upgrade to the latest, supported version as it will include this and other fixes. View the full article

IP.Board 3.1.x and Applications: End of Life AnnouncementSo that we can focus all of our development, support, and service efforts on the newest version 3.3, we are announcing the end of support (sometimes called end of life or EOL) for the following IPS software versions (and earlier versions): IP.Board 3.1.x IP.Blog 2.2.x IP.Gallery 3.2.x IP.Downloads 2.2.x IP.Content 2.0.x IP.Chat 1.1.x IP.Nexus 1.1.x Technical support, installations, and services will end for these products on August 1, 2012. On that date all technical or service requests will be advised to simply upgrade to the most recent versions of the products. We will not force upgrades but will also not be able to diagnose issues or answer questions relating to the older software. Also, on that date, IPS will no longer address any new issues or bugs reported in the older software versions.You are of course free to continue using these older versions if you wish but IPS will no longer provide assistance after the EOL date.Security UpdatesIn the event an issue is discovered impacting the security of these older versions of the software, IPS will provide a patch posted in our announcements forum. We will continue to provide security updates for several months after the EOL date based on severity of the issue.Internet Explorer 7 SupportWe announced our plans to start phasing out support for Internet Explorer 7 in December 2010 and have been slowly doing so. As of this date, IPS will no longer support Internet Explorer 7. This includes compatibility modes in newer browsers. View the full article

Invision Power Services, Inc. is pleased to announce the release of IP.Nexus 1.4.2!IP.Nexus is our commerce system to sell products, membership access, advertising, digital downloads, and more. Includes tools like a support desk to help manage you clients. The 1.4.2 release is a maintenance release to address issues from the new 1.4.x release.We welcome feedback on this or any other release in the relevant feedback forum including suggestions for future releases.DemoYou can try our free demo to see IP.Nexus in action for yourself.PurchasingYou can purchase IP.Nexus in your client area by clicking the 'New Purchase' button in the upper right corner. New clients can purchase IP.Nexus along with IP.Board. If you are an IPS Community Hosting client, IP.Nexus comes with many of our packages.If you have already purchased IP.Nexus, you can download this update in your client area.Requirements / Notes IP.Nexus 1.4.2 requires IP.Board version 3.2.3Installing / UpgradingFor further assistance on installing IP.Nexus please refer to this document and for upgrading please refer to this document View the full article

UPDATE `admin_forum2`.`skin_collections` SET `set_master_key` = 'mobile' WHERE `skin_collections`.`set_id` =2;

TestSent from my ADR6400L using Tapatalk

lol no worries... I run and have many of these IPS forums.. as well as work for IPS... so it's critical for me to get this fixed too... but we have to depend on Tapatalk... but we the more data and tools we give them the better... thanks for all the help and testin.

Strange, same setup exactly, but tt may be here making changes perhaps as i gave them access here to troubleshootSent from my ADR6400L using Tapatalk

Ya im seeing that now as wellSent from my ADR6400L using Tapatalk

Test Sent from my ADR6400L using Tapatalk

[root@jacob ~]# sar Linux 2.6.18-194.32.1.el5 (jacob.exactservers.com) 10/15/2011 12:00:01 AM CPU %user %nice %system %iowait %steal %idle12:10:01 AM all 7.15 0.00 0.97 0.30 0.00 91.5712:20:01 AM all 24.14 0.19 2.24 4.34 0.00 69.0812:30:01 AM all 5.89 0.00 0.82 0.47 0.00 92.8212:40:01 AM all 6.46 0.00 0.89 0.33 0.00 92.3312:50:01 AM all 6.05 0.18 0.86 1.02 0.00 91.8901:00:01 AM all 6.38 0.00 0.89 0.24 0.00 92.5001:10:03 AM all 5.86 15.01 2.80 15.76 0.00 60.5701:20:01 AM all 5.45 14.92 2.75 19.68 0.00 57.2001:30:01 AM all 6.24 7.41 1.94 23.81 0.00 60.6001:40:01 AM all 5.97 13.13 2.54 20.86 0.00 57.5001:50:01 AM all 8.50 8.17 2.50 22.24 0.00 58.6002:00:01 AM all 6.51 8.80 2.07 21.93 0.00 60.6902:10:01 AM all 5.75 5.25 1.61 24.15 0.00 63.2302:20:01 AM all 5.57 12.03 2.38 21.50 0.00 58.5202:30:01 AM all 6.67 17.11 2.81 19.49 0.00 53.9402:40:01 AM all 5.71 7.73 1.85 23.33 0.00 61.3802:50:02 AM all 6.13 13.23 2.51 22.49 0.00 55.6403:00:01 AM all 5.46 14.11 2.64 20.11 0.00 57.6903:10:01 AM all 6.42 10.53 2.26 22.47 0.00 58.3203:20:01 AM all 7.89 5.21 1.71 23.98 0.00 61.2203:30:01 AM all 6.14 4.72 1.33 7.91 0.00 79.9003:40:02 AM all 6.23 0.00 0.92 1.38 0.00 91.4703:50:01 AM all 6.58 0.18 0.86 1.97 0.00 90.4004:00:01 AM all 7.16 0.00 0.85 0.94 0.00 91.0504:10:01 AM all 6.10 0.02 0.88 5.76 0.00 87.2404:20:01 AM all 7.08 0.00 0.92 0.90 0.00 91.1004:30:01 AM all 6.57 0.00 0.88 0.72 0.00 91.8304:40:01 AM all 6.05 0.00 0.82 0.79 0.00 92.3404:50:01 AM all 5.41 0.18 0.79 0.59 0.00 93.02 04:50:01 AM CPU %user %nice %system %iowait %steal %idle05:00:01 AM all 5.51 0.00 0.79 0.93 0.00 92.7805:10:01 AM all 6.44 0.00 0.90 0.58 0.00 92.0805:20:01 AM all 7.12 0.00 0.93 1.65 0.00 90.3005:30:01 AM all 7.09 0.00 0.96 0.47 0.00 91.4805:40:01 AM all 7.00 0.00 0.91 0.76 0.00 91.3305:50:01 AM all 6.37 0.18 0.91 0.60 0.00 91.9306:00:01 AM all 7.21 0.00 0.93 0.57 0.00 91.2806:10:01 AM all 6.60 0.00 0.83 0.48 0.00 92.0906:20:01 AM all 5.92 0.00 0.81 0.41 0.00 92.8706:30:01 AM all 6.89 0.00 0.90 0.39 0.00 91.8206:40:01 AM all 6.58 0.00 0.94 0.52 0.00 91.9706:50:01 AM all 7.60 0.18 1.05 0.51 0.00 90.6607:00:01 AM all 7.78 0.00 1.01 0.44 0.00 90.7607:10:01 AM all 7.85 0.00 1.02 0.75 0.00 90.3807:20:01 AM all 6.56 0.00 0.90 0.99 0.00 91.5507:30:02 AM all 6.67 0.00 0.98 2.22 0.00 90.1307:40:01 AM all 7.75 0.00 1.10 0.51 0.00 90.6407:50:01 AM all 8.54 0.18 1.11 0.67 0.00 89.5008:00:01 AM all 6.88 0.00 0.96 0.47 0.00 91.6808:10:01 AM all 7.73 0.00 1.04 0.50 0.00 90.7308:20:01 AM all 8.29 0.00 1.02 0.52 0.00 90.1708:30:01 AM all 5.75 0.00 0.80 0.30 0.00 93.1608:40:01 AM all 7.99 0.00 1.01 0.38 0.00 90.6108:50:01 AM all 7.75 0.18 1.06 0.59 0.00 90.4209:00:01 AM all 6.86 0.00 1.06 0.52 0.00 91.5509:10:01 AM all 6.05 0.00 0.93 0.56 0.00 92.4509:20:01 AM all 7.28 0.00 0.97 0.35 0.00 91.4009:30:01 AM all 8.64 0.00 1.07 0.34 0.00 89.9509:40:01 AM all 5.52 0.00 0.81 0.30 0.00 93.36 09:40:01 AM CPU %user %nice %system %iowait %steal %idle09:50:01 AM all 7.06 0.18 1.00 0.36 0.00 91.4110:00:01 AM all 8.55 0.00 1.05 0.41 0.00 89.9810:10:01 AM all 6.09 0.00 0.88 0.46 0.00 92.5610:20:01 AM all 5.92 0.00 0.82 0.32 0.00 92.9410:30:01 AM all 5.88 0.00 0.81 0.27 0.00 93.04Average: 6.97 2.52 1.26 5.55 0.00 83.69 [root@ellen ~]# sarLinux 2.6.18-274.el5 (ellen.exactservers.com) 10/15/201112:00:01 AM CPU %user %nice %system %iowait %steal %idle12:10:01 AM all 6.68 0.01 0.90 4.32 0.00 88.0912:20:01 AM all 6.81 0.35 0.89 7.32 0.00 84.6312:30:01 AM all 5.28 0.00 0.69 3.67 0.00 90.3612:40:01 AM all 5.07 0.00 0.65 3.55 0.00 90.7312:50:01 AM all 4.81 0.00 0.63 3.43 0.00 91.1301:00:01 AM all 4.68 0.00 0.61 3.57 0.00 91.1401:10:01 AM all 4.35 2.01 0.74 6.54 0.00 86.3601:20:01 AM all 4.59 0.00 0.57 3.06 0.00 91.7801:30:01 AM all 4.70 0.00 0.59 3.65 0.00 91.0601:40:01 AM all 4.79 0.00 0.60 3.31 0.00 91.3101:50:01 AM all 4.50 0.00 0.57 3.17 0.00 91.7602:00:01 AM all 4.11 0.00 0.53 3.19 0.00 92.1702:10:01 AM all 4.09 0.01 0.53 2.81 0.00 92.5602:20:01 AM all 4.14 0.00 0.53 3.02 0.00 92.3202:30:01 AM all 3.74 0.00 0.49 2.56 0.00 93.2202:40:01 AM all 3.73 0.00 0.46 2.33 0.00 93.4802:50:01 AM all 3.85 0.00 0.46 1.73 0.00 93.9503:00:01 AM all 3.68 0.00 0.46 2.05 0.00 93.8103:10:01 AM all 3.94 0.01 0.51 2.38 0.00 93.1603:20:01 AM all 4.17 0.00 0.55 3.23 0.00 92.0503:30:01 AM all 4.04 0.00 0.52 2.99 0.00 92.4503:40:01 AM all 4.05 0.00 0.52 2.82 0.00 92.6203:50:01 AM all 3.70 0.00 0.49 2.54 0.00 93.2704:00:01 AM all 4.21 0.00 0.54 2.17 0.00 93.0804:10:01 AM all 4.06 0.01 0.53 2.70 0.00 92.7004:20:01 AM all 4.60 0.00 0.60 3.28 0.00 91.5204:30:01 AM all 4.62 0.00 0.60 3.40 0.00 91.3804:40:01 AM all 4.92 0.00 0.63 3.96 0.00 90.4804:50:01 AM all 4.93 0.00 0.63 3.10 0.00 91.3505:00:01 AM all 5.07 0.00 0.65 4.04 0.00 90.2405:10:01 AM all 5.16 0.01 0.67 4.11 0.00 90.0505:20:01 AM all 5.51 0.00 0.72 4.49 0.00 89.2705:30:01 AM all 5.98 0.00 0.75 4.30 0.00 88.9605:40:01 AM all 5.80 0.00 0.77 5.49 0.00 87.9405:50:01 AM all 6.16 0.00 0.76 4.58 0.00 88.5005:50:01 AM CPU %user %nice %system %iowait %steal %idle06:00:01 AM all 6.47 0.00 0.82 5.17 0.00 87.5306:10:01 AM all 6.80 0.01 0.89 4.44 0.00 87.8506:20:01 AM all 6.80 0.00 0.87 5.63 0.00 86.6906:30:01 AM all 6.36 0.00 0.85 6.01 0.00 86.7906:40:01 AM all 7.61 0.00 0.95 6.86 0.00 84.5806:50:01 AM all 7.46 0.00 0.95 7.00 0.00 84.5907:00:01 AM all 7.39 0.00 0.95 6.36 0.00 85.3007:10:01 AM all 7.12 0.01 0.92 4.93 0.00 87.0107:20:01 AM all 7.89 0.00 1.03 6.46 0.00 84.6207:30:01 AM all 8.54 0.00 1.10 6.43 0.00 83.9407:40:01 AM all 9.03 0.00 1.17 7.74 0.00 82.0607:50:01 AM all 8.99 0.00 1.13 8.29 0.00 81.5908:00:01 AM all 8.67 0.00 1.10 6.47 0.00 83.7508:10:01 AM all 8.98 0.01 1.16 6.36 0.00 83.4908:20:01 AM all 8.20 0.00 1.06 7.47 0.00 83.2808:30:01 AM all 8.19 0.00 1.05 6.77 0.00 83.9908:40:01 AM all 8.09 0.00 1.01 7.90 0.00 82.9908:50:01 AM all 7.81 0.00 1.00 6.61 0.00 84.5809:00:01 AM all 8.31 0.00 1.08 6.54 0.00 84.0709:10:01 AM all 8.18 0.01 1.06 6.96 0.00 83.7909:20:01 AM all 8.44 0.00 1.05 6.58 0.00 83.9309:30:01 AM all 8.78 0.00 1.08 6.29 0.00 83.8609:40:01 AM all 9.08 0.00 1.12 7.34 0.00 82.4609:50:01 AM all 8.19 0.00 1.02 6.05 0.00 84.7310:00:01 AM all 8.24 0.00 1.05 4.96 0.00 85.7510:10:01 AM all 8.41 0.01 1.09 6.11 0.00 84.3810:20:01 AM all 8.53 0.00 1.09 6.77 0.00 83.6010:30:01 AM all 8.24 0.00 1.03 7.29 0.00 83.44Average: 6.18 0.04 0.79 4.84 0.00 88.15

You might be familiar with Linux load averages already. Load averages are the three numbers shown with the uptime and top commands - they look like this: load average: 0.09, 0.05, 0.01Most people have an inkling of what the load averages mean: the three numbers represent averages over progressively longer periods of time (one, five, and fifteen minute averages), and that lower numbers are better. Higher numbers represent a problem or an overloaded machine. But, what's the the threshold? What constitutes "good" and "bad" load average values? When should you be concerned over a load average value, and when should you scramble to fix it ASAP? First, a little background on what the load average values mean. We'll start out with the simplest case: a machine with one single-core processor. The traffic analogy A single-core CPU is like a single lane of traffic. Imagine you are a bridge operator ... sometimes your bridge is so busy there are cars lined up to cross. You want to let folks know how traffic is moving on your bridge. A decent metric would be how many cars are waiting at a particular time. If no cars are waiting, incoming drivers know they can drive across right away. If cars are backed up, drivers know they're in for delays. So, Bridge Operator, what numbering system are you going to use? How about: 0.00 means there's no traffic on the bridge at all. In fact, between 0.00 and 1.00 means there's no backup, and an arriving car will just go right on. 1.00 means the bridge is exactly at capacity. All is still good, but if traffic gets a little heavier, things are going to slow down. over 1.00 means there's backup. How much? Well, 2.00 means that there are two lanes worth of cars total -- one lane's worth on the bridge, and one lane's worth waiting. 3.00 means there are three lane's worth total -- one lane's worth on the bridge, and two lanes' worth waiting. Etc. = load of 1.00 = load of 0.50 = load of 1.70 This is basically what CPU load is. "Cars" are processes using a slice of CPU time ("crossing the bridge") or queued up to use the CPU. Unix refers to this as the run-queue length: the sum of the number of processes that are currently running plus the number that are waiting (queued) to run. Like the bridge operator, you'd like your cars/processes to never be waiting. So, your CPU load should ideally stay below 1.00. Also like the bridge operator, you are still ok if you get some temporary spikes above 1.00 ... but when you're consistently above 1.00, you need to worry. So you're saying the ideal load is 1.00? Well, not exactly. The problem with a load of 1.00 is that you have no headroom. In practice, many sysadmins will draw a line at 0.70: The "Need to Look into it" Rule of Thumb: 0.70 If your load average is staying above > 0.70, it's time to investigate before things get worse. The "Fix this now" Rule of Thumb: 1.00. If your load average stays above 1.00, find the problem and fix it now. Otherwise, you're going to get woken up in the middle of the night, and it's not going to be fun. The "Arrgh, it's 3AM WTF?" Rule of Thumb: 5.0. If your load average is above 5.00, you could be in serious trouble, your box is either hanging or slowing way down, and this will (inexplicably) happen in the worst possible time like in the middle of the night or when you're presenting at a conference. Don't let it get there. What about Multi-processors? My load says 3.00, but things are running fine! Got a quad-processor system? It's still healthy with a load of 3.00. On multi-processor system, the load is relative to the number of processor cores available. The "100% utilization" mark is 1.00 on a single-core system, 2.00, on a dual-core, 4.00 on a quad-core, etc. If we go back to the bridge analogy, the "1.00" really means "one lane's worth of traffic". On a one-lane bridge, that means it's filled up. On a two-late bridge, a load of 1.00 means its at 50% capacity -- only one lane is full, so there's another whole lane that can be filled. Same with CPUs: a load of 1.00 is 100% CPU utilization on single-core box. On a dual-core box, a load of 2.00 is 100% CPU utilization. Multicore vs. multiprocessor While we're on the topic, let's talk about multicore vs. multiprocessor. For performance purposes, is a machine with a single dual-core processor basically equivalent to a machine with two processors with one core each? Yes. Roughly. There are lots of subtleties here concerning amount of cache, frequency of process hand-offs between processors, etc. Despite those finer points, for the purposes of sizing up the CPU load value, the total number of cores is what matters, regardless of how many physical processors those cores are spread across. Which leads us to a two new Rules of Thumb: The "number of cores = max load" Rule of Thumb: on a multicore system, your load should not exceed the number of cores available. The "cores is cores" Rule of Thumb: How the cores are spread out over CPUs doesn't matter. Two quad-cores == four dual-cores == eight single-cores. It's all eight cores for these purposes. Bringing It Home Let's take a look at the load averages output from uptime: ~ $ uptime23:05 up 14 days, 6:08, 7 users, load averages: 0.65 0.42 0.36This is on a dual-core CPU, so we've got lots of headroom. I won't even think about it until load gets and stays above 1.7 or so. Now, what about those three numbers? 0.65 is the average over the last minute, 0.42 is the average over the last five minutes, and 0.36 is the average over the last 15 minutes. Which brings us to the question: Which average should I be observing? One, five, or 15 minute? For the numbers we've talked about (1.00 = fix it now, etc), you should be looking at the five or 15-minute averages. Frankly, if your box spikes above 1.0 on the one-minute average, you're still fine. It's when the 15-minute average goes north of 1.0 and stays there that you need to snap to. (obviously, as we've learned, adjust these numbers to the number of processor cores your system has). So # of cores is important to interpreting load averages ... how do I know how many cores my system has? cat /proc/cpuinfo to get info on each processor in your system. Note: not available on OSX, Google for alternatives. To get just a count, run it through grepand word count: grep 'model name' /proc/cpuinfo | wc -lThis post has been promoted to an article

If you ever need to reset your notifications, you can set the defaults in the admincp, then run the following to clear the users custom notifications, it will then use the default options until a user updates them manually. *adjust ibf_ to the prefix as needed or remove if no prefix was used. update ibf_members set members_cache = ''