From admin at probass.com Sat Feb 1 08:58:10 2014 From: admin at probass.com (Richard C. Barker Sr.) Date: Sat, 01 Feb 2014 08:58:10 -0500 Subject: [BlueOnyx:14342] Error after yum update Message-ID: <52ECFD72.6050207@probass.com> On one vps got this error after update /etc/cron.hourly/log_traffic: awk: cmd. line:17: (FILENAME=- FNR=3) fatal: attempt to access field -2147483648 RC -- +---------------------------------------------+ Richard C. Barker Sr. CEO & President 1-800-510-3139 ProBass Networks Inc. http://www.probassnetworks.net http://www.probass.net *************************************** DISCLAIMER : - This e-mail is confidential and intended only for the use of the individual or entity named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message. +---------------------------------------------+ From admin at probass.com Sat Feb 1 09:05:15 2014 From: admin at probass.com (Richard C. Barker Sr.) Date: Sat, 01 Feb 2014 09:05:15 -0500 Subject: [BlueOnyx:14343] Another error after yum update Message-ID: <52ECFF1B.6000804@probass.com> On the same vps got this error: Invalid system activity file: /var/log/sa//sa01 File created using sar/sadc from sysstat version 9.0.4 Current sysstat version can no longer read the format of this file (0x2170) Format of this file had been changed in sysstat-9.0.4-20.el6 due to incompatibility of the certain data types with the current kernel. For more information, please refer to the description of the "--legacy" option in the sar(1) manual page. Thanks RC -- +---------------------------------------------+ Richard C. Barker Sr. CEO & President 1-800-510-3139 ProBass Networks Inc. http://www.probassnetworks.net http://www.probass.net *************************************** DISCLAIMER : - This e-mail is confidential and intended only for the use of the individual or entity named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message. +---------------------------------------------+ From ses at aviaweb.com Sat Feb 1 09:19:35 2014 From: ses at aviaweb.com (Stephanie Sullivan) Date: Sat, 1 Feb 2014 09:19:35 -0500 Subject: [BlueOnyx:14344] Re: Another error after yum update In-Reply-To: <52ECFF1B.6000804@probass.com> References: <52ECFF1B.6000804@probass.com> Message-ID: <007f01cf1f58$a2f23880$e8d6a980$@com> > -----Original Message----- > From: Richard C. Barker Sr. [mailto:admin at probass.com] > Sent: Saturday, February 01, 2014 9:05 AM > To: BlueOnyx General Mailing List > Subject: [BlueOnyx:14343] Another error after yum update > > On the same vps got this error: > > Invalid system activity file: /var/log/sa//sa01 > File created using sar/sadc from sysstat version 9.0.4 > Current sysstat version can no longer read the format of this file > (0x2170) > Format of this file had been changed in sysstat-9.0.4-20.el6 > due to incompatibility of the certain data types with the current > kernel. > For more information, please refer to the description of the "-- > legacy" > option in the sar(1) manual page. > > Thanks > RC Richard, I saw this a while ago after an update. Not sure which package drove this issue, but the solution was to delete the offending file in the message. It gets recreated as automatically. If you want to be very careful, you might just move/rename the file to be certain. Hope this helps. -Stephanie From wcstaff at webcoast.com Sat Feb 1 09:50:13 2014 From: wcstaff at webcoast.com (wcstaff at webcoast.com) Date: Sat, 1 Feb 2014 09:50:13 -0500 Subject: [BlueOnyx:14345] Re: Another error after yum update In-Reply-To: <007f01cf1f58$a2f23880$e8d6a980$@com> References: <52ECFF1B.6000804@probass.com> <007f01cf1f58$a2f23880$e8d6a980$@com> Message-ID: <008401cf1f5c$e9f00fb0$bdd02f10$@webcoast.com> > > Invalid system activity file: /var/log/sa//sa01 > > File created using sar/sadc from sysstat version 9.0.4 > > Current sysstat version can no longer read the format of this file > > (0x2170) > > Format of this file had been changed in sysstat-9.0.4-20.el6 > > due to incompatibility of the certain data types with the current > > kernel. > > For more information, please refer to the description of the "-- > > legacy" > > option in the sar(1) manual page. > > > > Thanks > > RC > > Richard, > > I saw this a while ago after an update. Not sure which package drove this > issue, but the solution was to delete the offending file in the message. It > gets recreated as automatically. If you want to be very careful, you might > just move/rename the file to be certain. > > Hope this helps. > > -Stephanie > To assure others that are not pulling yum updates from the beta repository, I performed a yum update on 2 Scientific Linux boxes. I started with a "yum clean all", then yum update. Both updated successfully. From admin at probass.com Sat Feb 1 09:52:22 2014 From: admin at probass.com (Richard C. Barker Sr.) Date: Sat, 01 Feb 2014 09:52:22 -0500 Subject: [BlueOnyx:14346] Re: Another error after yum update In-Reply-To: <007f01cf1f58$a2f23880$e8d6a980$@com> References: <007f01cf1f58$a2f23880$e8d6a980$@com> Message-ID: <52ED0A26.5010803@probass.com> Thank it seems to be ok now RC -- +---------------------------------------------+ Richard C. Barker Sr. CEO & President 1-800-510-3139 ProBass Networks Inc. http://www.probassnetworks.net http://www.probass.net *************************************** DISCLAIMER : - This e-mail is confidential and intended only for the use of the individual or entity named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message. +---------------------------------------------+ From gwaugh at frontstreetnetworks.com Sat Feb 1 12:48:14 2014 From: gwaugh at frontstreetnetworks.com (Gerald Waugh) Date: Sat, 01 Feb 2014 11:48:14 -0600 Subject: [BlueOnyx:14347] Scientific Linux release 6.5 (Carbon) Message-ID: <52ED335E.8050804@frontstreetnetworks.com> ran yum update on a SL-6.4 server this morning # cat /etc/redhat-release Scientific Linux release 6.5 (Carbon) # cat /etc/build build 20110922 for a 5108R in en_US Gerald From admin at probass.com Sun Feb 2 14:17:56 2014 From: admin at probass.com (Richard C. Barker Sr.) Date: Sun, 02 Feb 2014 14:17:56 -0500 Subject: [BlueOnyx:14348] Re: Error after yum update In-Reply-To: <52ECFD72.6050207@probass.com> References: <52ECFD72.6050207@probass.com> Message-ID: <52EE99E4.9000802@probass.com> Has no one else seen this? /etc/cron.hourly/log_traffic: awk: cmd. line:17: (FILENAME=- FNR=3) fatal: attempt to access field -2147483648 I have looked in the messages log I have compared the file to two other vps's only this one vps has this issue. I found this http://mail.blueonyx.it/pipermail/blueonyx/2011-August/008132.html but no one answered him as well Thanks RC -- +---------------------------------------------+ Richard C. Barker Sr. CEO & President 1-800-510-3139 ProBass Networks Inc. http://www.probassnetworks.net http://www.probass.net *************************************** DISCLAIMER : - This e-mail is confidential and intended only for the use of the individual or entity named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message. +---------------------------------------------+ From lists.aeb at cbxnet.de Mon Feb 3 07:36:03 2014 From: lists.aeb at cbxnet.de (Andreas Ebertus) Date: Mon, 3 Feb 2014 13:36:03 +0100 Subject: [BlueOnyx:14349] MBR loss on software RAID1 Message-ID: <20140203133603.37e2e1ab@aeb> Hello list, I think I've found the cause for the loss of MBR on software RAID1 systems. The init script /etc/init.d/mdchk gets executed during boot and on line 227 it writes a syslinux MBR: system(sprintf("ms-sys -s %s > /dev/stderr", disk)); This only happens on 5106R as the script checks for md[0-9] entries in /etc/fstab and exits if it finds none. But as of 5107R we only have UUID's in fstab so the mdchk script never really gets executed on 5107R/5108R systems. That means we could get rid of the /etc/init.d/fix_grub script. Best regards, Andreas From jeffrey at px2co.net Mon Feb 3 07:59:00 2014 From: jeffrey at px2co.net (jeffrey Pellin - PX2) Date: Mon, 03 Feb 2014 12:59:00 +0000 Subject: [BlueOnyx:14350] Sender dependent forwarding of emails Message-ID: <48ccf8268a549cde18c4500135f6f077@www.px2online.com> Hi Guys, Does anyone know of a relativeley simple way to do this on a BO server please? Regards Jeffrey -- JEFFREY PELLIN Director JEFFREY PELLIN CONSULTANCY LTD [1] WORK: 01692 558226 MOBILE: 07768 451738 EMAIL: jeffrey at pellin.co.uk PROFESSIONAL PROFILE [2] See who we know in common [3] Links: ------ [1] http://www.quick-websites.co.uk [2] http://uk.linkedin.com/in/jeffreypellin/ [3] http://www.linkedin.com/e/wwk/53425140/?hs=false&tok=13wzr5NHSChl41 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mailinglist at tikklik.nl Mon Feb 3 12:28:21 2014 From: mailinglist at tikklik.nl (Steffan Noord) Date: Mon, 3 Feb 2014 18:28:21 +0100 Subject: [BlueOnyx:14351] Re: API request In-Reply-To: <52EBCFBA.3010909@blueonyx.it> References: <003301cf1e8c$4ac8ebd0$e05ac370$@tikklik.nl> <52EBCFBA.3010909@blueonyx.it> Message-ID: <001501cf2105$570d5b80$05281280$@tikklik.nl> VsiteUpdate To update the disquota, max users etc -----Oorspronkelijk bericht----- Van: blueonyx-bounces at mail.blueonyx.it [mailto:blueonyx-bounces at mail.blueonyx.it] Namens Michael Stauber Verzonden: vrijdag 31 januari 2014 17:31 Aan: BlueOnyx General Mailing List Onderwerp: [BlueOnyx:14337] Re: API request Hi Steffan, > Is it possible to add a include file to > /usr/sausalito/ui/web/base/api/index.php > In your next update > > So i can put my own commands in there and dont get overwritten in a update? Generally that's possible. But let me ask the other way around: What extra commands or functions are you using? Might be worthwhile to include them in the general API functionality if you want to share them. -- With best regards Michael Stauber _______________________________________________ Blueonyx mailing list Blueonyx at mail.blueonyx.it http://mail.blueonyx.it/mailman/listinfo/blueonyx From pseudo at zbronx.com Mon Feb 3 18:41:04 2014 From: pseudo at zbronx.com (Gustavo Silva) Date: Mon, 03 Feb 2014 23:41:04 +0000 Subject: [BlueOnyx:14352] Wordpress issues In-Reply-To: <528F2E8C.7010106@blueonyx.it> References: <5382436.1288.1385060958880.JavaMail.root@pfinders.com> <528F2E8C.7010106@blueonyx.it> Message-ID: <52F02910.20905@zbronx.com> Hello and thanks in advance! I'm having this weird situation happening with a barebone wordpress installs on 2 different VPS (2 cores, 4GB ram, both with SL6.5 BO, same version software, settings etc) - Both VPS load HTML pages lightning fast (less than 200ms response time) - Both VPS load custom PHP developed pages fast (~500ms response time) - VPS ONE loads a bare Wordpress under 900ms response time (about 1-3 seconds to complete loading) - VPS TWO loads the same bare Wordpress in 2-3seconds (and then 1-3 seconds to complete loading) What the hell?? Ive been pulling hard reviewing all the configuration files, with and without suPHP (which a lot of people report as slow... But well, might be slow processing, but why does it take so much time to respond?) Has anyone been through this? Cheers! Gustavo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 12009 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 8552 bytes Desc: not available URL: From pseudo at zbronx.com Mon Feb 3 20:07:39 2014 From: pseudo at zbronx.com (Gustavo Silva) Date: Tue, 04 Feb 2014 01:07:39 +0000 Subject: [BlueOnyx:14353] Re: Wordpress issues In-Reply-To: <52F02910.20905@zbronx.com> References: <5382436.1288.1385060958880.JavaMail.root@pfinders.com> <528F2E8C.7010106@blueonyx.it> <52F02910.20905@zbronx.com> Message-ID: <52F03D5B.7070605@zbronx.com> Ken Marcus, Super Cache worked like a charm ;) Now both pages open under 200ms Many, many thanks! Cheers. Gustavo On 03/02/2014 23:41, Gustavo Silva wrote: > Hello and thanks in advance! > > I'm having this weird situation happening with a barebone wordpress > installs on 2 different VPS (2 cores, 4GB ram, both with SL6.5 BO, > same version software, settings etc) > > - Both VPS load HTML pages lightning fast (less than 200ms response time) > - Both VPS load custom PHP developed pages fast (~500ms response time) > - VPS ONE loads a bare Wordpress under 900ms response time (about 1-3 > seconds to complete loading) > > > > - VPS TWO loads the same bare Wordpress in 2-3seconds (and then 1-3 > seconds to complete loading) > > > > What the hell?? Ive been pulling hard reviewing all the configuration > files, with and without suPHP (which a lot of people report as slow... > But well, might be slow processing, but why does it take so much time > to respond?) > > Has anyone been through this? > > > Cheers! > Gustavo > > > _______________________________________________ > Blueonyx mailing list > Blueonyx at mail.blueonyx.it > http://mail.blueonyx.it/mailman/listinfo/blueonyx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 12009 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 8552 bytes Desc: not available URL: From mstauber at blueonyx.it Mon Feb 3 20:27:00 2014 From: mstauber at blueonyx.it (Michael Stauber) Date: Mon, 03 Feb 2014 20:27:00 -0500 Subject: [BlueOnyx:14354] Re: MBR loss on software RAID1 In-Reply-To: <20140203133603.37e2e1ab@aeb> References: <20140203133603.37e2e1ab@aeb> Message-ID: <52F041E4.5000301@blueonyx.it> Hi Andreas, > I think I've found the cause for the loss of MBR on software RAID1 > systems. The init script /etc/init.d/mdchk gets executed during boot > and on line 227 it writes a syslinux MBR: > > system(sprintf("ms-sys -s %s > /dev/stderr", disk)); Yikes! Great find! Many thanks! Been looking for that issue for ages. Yeah, the entire RAID stuff is horribly broken. In 520XR I'll probably rip it out entirely and just let a PHP script monitor the RAID status. I have that part already working. However, the underlying Perl and shell scripts to monitor RAID and to initiate a rebuild are simply too old to get them working on EL6 clones. I've tried some work arounds, but they'll shoot us in the foot in the long haul. -- With best regards Michael Stauber From rickard.osser at bluapp.com Tue Feb 4 03:35:50 2014 From: rickard.osser at bluapp.com (Rickard Osser) Date: Tue, 04 Feb 2014 09:35:50 +0100 Subject: [BlueOnyx:14355] Re: MBR loss on software RAID1 In-Reply-To: <52F041E4.5000301@blueonyx.it> References: <20140203133603.37e2e1ab@aeb> <52F041E4.5000301@blueonyx.it> Message-ID: <1391502950.6385.16.camel@dragon.home.osser.se> Hi! Yes, fix_grub was a last-resort solution especially for a combination of BQ and a 4-disk Tyan solution that sometimes lost it's MBR that I used a couple of years ago. BO never showed the same problems with the same hardware. The reason for this is of course the changes in MD that saved the config to the disks instead of the the raidtab file which all monitoring script in Sausalito uses. I also wrote a script (lsraid) to give sausalito the same information as was available on the old systems. This should all be reformed and updated to modern standards. Best regards, Rickard On m?n, 2014-02-03 at 20:27 -0500, Michael Stauber wrote: > Hi Andreas, > > > I think I've found the cause for the loss of MBR on software RAID1 > > systems. The init script /etc/init.d/mdchk gets executed during boot > > and on line 227 it writes a syslinux MBR: > > > > system(sprintf("ms-sys -s %s > /dev/stderr", disk)); > > Yikes! Great find! Many thanks! Been looking for that issue for ages. > > Yeah, the entire RAID stuff is horribly broken. In 520XR I'll probably > rip it out entirely and just let a PHP script monitor the RAID status. I > have that part already working. > > However, the underlying Perl and shell scripts to monitor RAID and to > initiate a rebuild are simply too old to get them working on EL6 clones. > I've tried some work arounds, but they'll shoot us in the foot in the > long haul. > -- ________________________________________________________________________ Bluapp AB Rickard Osser CTO Solberga ?ngsv?g 3 125 44 ?lvsj? Sweden From wcstaff at webcoast.com Tue Feb 4 10:07:06 2014 From: wcstaff at webcoast.com (wcstaff at webcoast.com) Date: Tue, 4 Feb 2014 10:07:06 -0500 Subject: [BlueOnyx:14356] FW: Cron run-parts /etc/cron.hourly In-Reply-To: <201402041501.s14F16a1005289@ns.webcoast.net> References: <201402041501.s14F16a1005289@ns.webcoast.net> Message-ID: <018501cf21ba$c5127ab0$4f377010$@webcoast.com> What does this mean? I'm getting it after the recent large yum update. Never saw it before. ------------------------ Subject: Cron run-parts /etc/cron.hourly /etc/cron.hourly/log_traffic: iptables v1.4.7: host/network `0.0.0.0/0' not found Try `iptables -h' or 'iptables --help' for more information. iptables v1.4.7: host/network `0.0.0.0/0' not found Try `iptables -h' or 'iptables --help' for more information. ------------------------ From admin at probass.com Tue Feb 4 15:27:52 2014 From: admin at probass.com (Richard C. Barker Sr.) Date: Tue, 04 Feb 2014 15:27:52 -0500 Subject: [BlueOnyx:14357] Re: CURLOPT_FOLLOWLOCATION In-Reply-To: <52DEFDB7.2050900@probass.com> References: <52DEFDB7.2050900@probass.com> Message-ID: <52F14D48.5090500@probass.com> Here is the real fix in the last joomla update they set curl to // Follow redirects. $options[CURLOPT_FOLLOWLOCATION] = (bool) $this->options->get('follow_location', true); Shanged to: // Follow redirects. $options[CURLOPT_FOLLOWLOCATION] = (bool) $this->options->get('follow_location', false); All is happy happy no more errors RC -- +---------------------------------------------+ Richard C. Barker Sr. CEO & President 1-800-510-3139 ProBass Networks Inc. http://www.probassnetworks.net http://www.probass.net *************************************** DISCLAIMER : - This e-mail is confidential and intended only for the use of the individual or entity named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message. +---------------------------------------------+ From mstauber at blueonyx.it Tue Feb 4 20:50:12 2014 From: mstauber at blueonyx.it (Michael Stauber) Date: Tue, 04 Feb 2014 20:50:12 -0500 Subject: [BlueOnyx:14358] BlueOnyx 5106R users: Please consider upgrading Message-ID: <52F198D4.2070604@blueonyx.it> Hi all, I'm about to wrap up the SSL security review of BlueOnyx. The final updates will go into the BlueOnyx-Testing YUM repository and then - within a day or two - these updates will be pushed to the production YUM repositories. That's for 5106R, 5107R and 5108R. But let me say this: If you're using BlueOnyx 5106R, then please consider migrating to BlueOnyx 5107R or BlueOnyx 5108R in the near future. CentOS5 will be around and maintained until March 31, 2017. However: As things stand I'd *strongly* advise not to wait that long. The reason for this has to do with OpenSSL. Every sensible server operator is sharpening up security wise and everyone looks what can be done to make services more secure and less prone to snooping. However, the RHEL5 based CentOS5 gets the short stick here. It is burdened with OpenSSL-0.9.8 and that means neither TSLv1.1 or TLSv1.2 are available. These are stronger and more secure protocols. Unless RedHat releases the next version of RHEL5 with a much newer OpenSSL this situation will not improve. And don't hold your breath for that. The will most likely keep OpenSSL as it is. So BlueOnyx 5106R is stuck with TLSv1.0 for all SSL related services. On the other hand: Since the latest round of updates BlueOnyx 5107R/5108R allows TLSv1.0, 1.1 and 1.2 for services such as HTTPS, POP3S, IMAPS and FTPS. Another reason to upgrade is cosmetic: It'll make it much easier to get the new BlueOnyx GUI installed once it's ready for release. -- With best regards Michael Stauber From cobaltfacts at virtbiz.com Wed Feb 5 14:47:57 2014 From: cobaltfacts at virtbiz.com (Chris Gebhardt - VIRTBIZ Internet) Date: Wed, 05 Feb 2014 13:47:57 -0600 Subject: [BlueOnyx:14359] Outage Message-ID: <52F2956D.5040007@virtbiz.com> Feb 5 2014, 1:45pm CST.... It looks like shop.blueonyx.it, solarspeed.net and compassnetworks.com.au are all down. http://www.blueonyx.it/ is working fine. Any ETA on resolution? -- Chris Gebhardt VIRTBIZ Internet Services Access, Web Hosting, Colocation, Dedicated www.virtbiz.com | toll-free (866) 4 VIRTBIZ From cobaltfacts at virtbiz.com Wed Feb 5 15:28:54 2014 From: cobaltfacts at virtbiz.com (Chris Gebhardt - VIRTBIZ Internet) Date: Wed, 05 Feb 2014 14:28:54 -0600 Subject: [BlueOnyx:14360] Re: BlueOnyx 5106R users: Please consider upgrading In-Reply-To: <52F198D4.2070604@blueonyx.it> References: <52F198D4.2070604@blueonyx.it> Message-ID: <52F29F06.8020507@virtbiz.com> Thanks Michael. On 2/4/2014 7:50 PM, Michael Stauber wrote: > But let me say this: If you're using BlueOnyx 5106R, then please > consider migrating to BlueOnyx 5107R or BlueOnyx 5108R in the near future. > > CentOS5 will be around and maintained until March 31, 2017. > > However: As things stand I'd *strongly* advise not to wait that long. Michael makes a very good point for some sound security reasons. That said, there are other compelling reasons to leave 5106R behind as well. - stability. My own informal examination has shown 5108R to be generally more stable than 5106R. This is especially true with the random Dovecot authentication lock-ups. - performance. We have 5108R and 5106R systems running similar loads side-by-side. The 5108R runs circles around the 5106R boxes when it comes to tasks in the daily cron, MySQL operations, etc. My guess is the 64-bit-tuned parts are allowed to make better use of system resources. suPHP appears to take less of a hit as well, and we run ALL production sites in suPHP environments. - 64-bit. While on the topic of 64-bit, I should point out that it has been a very long time since 32-bit equipment was all that was available. I would strongly recommend that if you're on equipment that will only run 32-bit, you are approaching (or surpassing!) a reasonable life expectancy. You may be doing yourself a favor by jettisoning the old gear and moving into something newer in a planned operation rather than wait for equipment failure. > Another reason to upgrade is cosmetic: It'll make it much easier to get > the new BlueOnyx GUI installed once it's ready for release. Oh yes, there is that! :) 5106R has served us very well. For many of us, it was the lifeboat out of CentOS 4.x and the stagnation that appeared to take hold with the BlueQuartz project. Recall that BlueOnyx made its public debut on New Years Eve of 2008. Five years later, it's still a viable platform. Consider that BlueQuartz (from which we forked) first hit in 2003, and we've now been BlueOnyx users for longer than BlueQuartz was around in a viable form. So it is with a heartfelt "thanks" that I say farewell to 5106R as we prepare to move the last of our own systems to 5108R. For us, it is far better to make the move on our terms instead of having our hand forced by obsolescence. -- Chris Gebhardt VIRTBIZ Internet Services Access, Web Hosting, Colocation, Dedicated www.virtbiz.com | toll-free (866) 4 VIRTBIZ From pcworxla at gmail.com Wed Feb 5 15:42:32 2014 From: pcworxla at gmail.com (Ralf Quint) Date: Wed, 05 Feb 2014 12:42:32 -0800 Subject: [BlueOnyx:14361] Re: BlueOnyx 5106R users: Please consider upgrading In-Reply-To: <52F198D4.2070604@blueonyx.it> References: <52F198D4.2070604@blueonyx.it> Message-ID: <52F2A238.40505@gmail.com> On 2/4/2014 5:50 PM, Michael Stauber wrote: > Hi all, > > I'm about to wrap up the SSL security review of BlueOnyx. The final > updates will go into the BlueOnyx-Testing YUM repository and then - > within a day or two - these updates will be pushed to the production YUM > repositories. > > That's for 5106R, 5107R and 5108R. > > But let me say this: If you're using BlueOnyx 5106R, then please > consider migrating to BlueOnyx 5107R or BlueOnyx 5108R in the near future. Well, I would love to, but as I do not run BlueOnyx in a seriously multi-tenant environment, I am not at the luxury of having a lot of money to spend on new hardware just to run a few more or less small, mostly static web sites. BO has made this easy to set up, but it seems that the latest versions suffer from serious feature creep and requiring more and more resources. I was trying to install 5107 but it would not even start to install unless I had at least 512MB of RAM and more than 20GB drive space, while the host that I have available has only 384MB and a 20GB drive, more than enough for what the machine is supposed to do. That's why I had to go with a brand new 5016 install, as that would install just fine and gets the job done at little to no cost hardware wise... Ralf -- -- P.C.Worx * On-Site IT Services Phone: (323)744-1081 Mailing address: 12021 Wilshire Blvd. #290, Los Angeles, CA 90025 www.pcworxla.com -- --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com From mstauber at blueonyx.it Wed Feb 5 16:35:33 2014 From: mstauber at blueonyx.it (Michael Stauber) Date: Wed, 05 Feb 2014 16:35:33 -0500 Subject: [BlueOnyx:14362] Re: Outage In-Reply-To: <52F2956D.5040007@virtbiz.com> References: <52F2956D.5040007@virtbiz.com> Message-ID: <52F2AEA5.7050900@blueonyx.it> Hi Chris, > It looks like shop.blueonyx.it, solarspeed.net and > compassnetworks.com.au are all down. > > http://www.blueonyx.it/ is working fine. > > Any ETA on resolution? Yeah, in between mail.solarspeed.net was also affected. It's fixed by now. It'll affect other Aventurin{e} users as well, so I'm just wording a message for the list as of what happened and how to fix it. -- With best regards Michael Stauber From mstauber at blueonyx.it Wed Feb 5 16:57:14 2014 From: mstauber at blueonyx.it (Michael Stauber) Date: Wed, 05 Feb 2014 16:57:14 -0500 Subject: [BlueOnyx:14363] BlueOnyx 5107R on Aventurin{e} 6105R (IMPORTANT!) Message-ID: <52F2B3BA.8020201@blueonyx.it> Hi all, Greg and I just had an outage of our BlueOnyx 5107R VPS's on CentOS5 based Aventurin{e} 6105R's. VPS's on the SL-6 based Aventurin{e} 6106R are *not* affected. This particular problem will affect other users with 5107R VPS's on the older Aventurin{e} 6105R as well. So here is the explanation and the fix: Problem: ======== Aventurin{e} 6105R runs CentOS-5 with an 2.6.18 kernel. BlueOnyx 5107R uses a 2.6.32 kernel and the entire architecture is a bit more modern. Still: It was possible to run BlueOnyx 5107R VPS's on Aventurin{e} 6105R. Until RHEL-6.5, CentOS-6.5 and SL-6.5 got released a few days ago. When you now reboot a 5107R VPS, it will come up without network interfaces and without network connectivity. The commands "ifconfig" or "ifconfig -a" will not show what one would expect and a restart of the VPS or a restart of the network services inside the VPS's won't solve the issue. The problem is the new "iproute" RPM that was released with CentOS-6.5 and/or SL-6.5. It doesn't play well with OpenVZ on the older CentOS-5 based kernel of the master node. Fix: ==== Inside the VPS roll back to the last good "iproute" RPM and restart the VPS. How-to: ======= This assumes the VPS has already lost its network connection. If you can still connect to it directly, scroll down for the "fast work around": 1.) Login by SSH to the Aventurin{e} master node as "admin" and become "root" by using "su -" 2.) Use "vzlist -a" to see the list of VPS's. 3.) Go to the Container's private directory: Example: cd /vz/private//tmp/ Replace with the container ID (VPSID). 4.) Download the older "iproute" RPM with this command: wget http://vbq.solarspeed.net/pub/BlueOnyx/5106R/CentOS6/blueonyx/i386/RPMS/iproute-2.6.32-23.el6.i686.rpm 5.) Enter the VPS in question with the command "vzctl enter " where again is the container ID (VPSID). 6.) Force the install of the RPM: rpm -hUv --force /tmp/iproute-2.6.32-23.el6.i686.rpm 7.) Edit /etc/yum.conf and in the line 'exclude=' add iproute to it. Your exclude line should then look like this: exclude=iproute That will prevent YUM from updating iproute to the "bad" version next time around. 8.) Exit the VPS by pressing CTRL+D 9.) Restart the VPS: "vzctl restart " where again is your container ID (VPSID). Fast work around: ================= Only use the "fast work around" if you haven't already lost network connectivity on that VPS. Like if it wasn't rebooted since the install of the 6.5 updates: 1.) Enter the VPS as "root" or SSH into it. 2.) Run this command to install the RPM: rpm -hUv --force http://vbq.solarspeed.net/pub/BlueOnyx/5106R/CentOS6/blueonyx/i386/RPMS/iproute-2.6.32-23.el6.i686.rpm 3.) Edit /etc/yum.conf and to the "exclude=" line add "iproute" as explained above. 4.) Done. No restart needed. Reminder: ========= If you run Aventurin{e} 6106R you do NOT need to do anything. You're not affected. If your BlueOnyx (dedicated or VPS) doesn't run on Aventurin{e} 6105R then you're not affected either. -- With best regards Michael Stauber From mstauber at blueonyx.it Wed Feb 5 21:02:19 2014 From: mstauber at blueonyx.it (Michael Stauber) Date: Wed, 05 Feb 2014 21:02:19 -0500 Subject: [BlueOnyx:14364] BlueOnyx YUM updates: 5106R/5107R/5108R Message-ID: <52F2ED2B.2000602@blueonyx.it> Hi all, I just pushed the (imaginary) button and released about four months worth of YUM updates for 5106R, 5107R and 5108R. Everything from the "Testing" YUM repositories has been moved to the production YUM repositories. Depending on your type of BlueOnyx that'll amount to roughly 500 updated and/or new RPMs. What's new: =========== GUI: ---- - Still the old GUI (am still working on the new one) - New languages: - Dutch - Spanish - French - Italian - Portuguese The translation for these was done with the Google Translate API, so the translations aren't perfect. The French locale has been cleaned up a little (still work in progress) by Meaulnes Legler and Antoine Hayoz. Many thanks for that! New Modules: ------------ - base-api: Will now get installed automatically. Allows remote provisioning of Vsites via a web based API. More info: http://www.blueonyx.it/index.php?page=api - base-istat: Allows monitoring of the server health via an iPhone or iPad application available in the Apple Appstore. New Features: -------------- - FTP: Better FTPS support. FTP and FTPS can now be separately enabled/disabled via "Network Services" / "FTP". - Web: Apache can now be configured to run on other ports than the standard port 80 (HTTP) and port 443 (HTTPS). This allows users to put something else in front of Apache (like a Varnish cache for example) if they want to. - AdmServ: No longer runs as user "httpd", but as user "admserv". - 5107R/5108R only: Dovecot now supports TLSv1, TLSv1.1 and TLSv1.2. Additionally Dovecot has been switched to use stronger ciphers. - HTTPS: Vsites that use HTTPS are enforcing the use of stronger ciphers. On 5107R/5108R TLSv1.2 is also possible now. Wherever possible "Perfect Forwarding Secrecy" will be used, but for IE browsers this is not yet possible as our OpenSSL (thanks to idiosyncrasies on behalf of RedHat) is missing the needed ECDH ciphers. Additionally "HTTP Strict Transport Security" will be enforced on HTTPS transactions. For more info on that one please see: http://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security - "Reseller"-support: It is now possible to use the existing "Server Administrators" as "reseller" accounts. Each admin set up that way can be granted extra permissions such as "Virtual Site Management". He can then create as many sites and users as you allow him to. Existing Vsites can be moved to and from the control of such an admin. Suspension and/or deletion of such an administrator will also affect the Vsites under his control. The sites will then either be suspended or deleted, too. - Shop Integration: Under "Software Updates" there is a new menu entry that points to the BlueOnyx Shop and presents the available products sorted by category. - YUM Updates: A scheduled YUM update will now also try to "auto-complete" your BlueOnyx install. For that it runs a separate "yum groupinstall blueonyx" after each update run. That will make sure that your install is not missing any RPMs that we deem essential and which might or might not be missing. - Updated CMU: This new version of CMU already supports 5207R and 5208R. Bugfixes: --------- I don't know where to start on that one. It's basically too many to remember. However, these really stick out and should be mentioned: - Loss of web server alias on SSL enable/disable: Fixed - Sporadic loss of MBR record on 5106R with RAID1: Fixed - Wrong cert concatenation for the Sendmail cert: Fixed Generally the whole server alias stuff should now be working a lot more reliably. In the past we had these cases where either the email server alias(es) or the web server alias(es) would go walkies. They would still show in the GUI, but were gone in the respective config files. The problem there was that quite a few handlers run on these transactions and sometimes they just got into each others way, too. New Bugs: ---------- Well, the stuff was in the testing YUM repositories since December. Every reported bug got fixed. But there still might be the odd glitch here and there that was missed. If you find something, say so and it'll get fixed ASAP. Problems during the YUM update: ------------------------------- I had updated all my own VPS's over the last couple of weeks. I also just updated a few client servers. The updates themselves throw a few minor complains here and there with some scripts failing during the post-install. That is of no concern. After this massive YUM update you might experience that the AdmServ might have stopped or failed to restart. Simply restart it again manually. If the YUM update didn't go all the way through, then just do another "yum update" and it should finish. However, so far I haven't seen any larger defects with or after a YUM update of these new updates. But if you need assistance, please post here or in emergencies use the contact details on www.solarspeed.net: https://www.solarspeed.net/imprint/ -- With best regards Michael Stauber From cleardata at earthlink.net Wed Feb 5 23:00:14 2014 From: cleardata at earthlink.net (Dr. Blunt) Date: Wed, 05 Feb 2014 20:00:14 -0800 Subject: [BlueOnyx:14365] Re: BlueOnyx YUM updates: 5106R/5107R/5108R In-Reply-To: <52F2ED2B.2000602@blueonyx.it> References: <52F2ED2B.2000602@blueonyx.it> Message-ID: <6.1.2.0.2.20140205195843.00ba85c0@earthlink.net> Hi Michael Just did a yum update then went to web to log into the gui and got this. Warning: unlink(/usr/sausalito/ui/style/BlueOnyx.xml.compiled.ff09e609732daf49b796a76a233a3223) [function.unlink]: Permission denied in /usr/sausalito/ui/libPhp/uifc/Stylist.php on line 352 Then logged in and got this Warning: unlink(/usr/sausalito/ui/style/trueBlue.xml.compiled.ff09e609732daf49b796a76a233a3223) [function.unlink]: Permission denied in /usr/sausalito/ui/libPhp/uifc/Stylist.php on line 352 Warning: Cannot modify header information - headers already sent by (output started at /usr/sausalito/ui/libPhp/uifc/Stylist.php:352) in /usr/sausalito/ui/web/nav/cList.php on line 53 Warning: Cannot modify header information - headers already sent by (output started at /usr/sausalito/ui/libPhp/uifc/Stylist.php:352) in /usr/sausalito/ui/web/nav/cList.php on line 55 Warning: Cannot modify header information - headers already sent by (output started at /usr/sausalito/ui/libPhp/uifc/Stylist.php:352) in /usr/sausalito/ui/web/nav/cList.php on line 65 At 06:02 PM 2/5/2014, you wrote: >Hi all, > >I just pushed the (imaginary) button and released about four months >worth of YUM updates for 5106R, 5107R and 5108R. > >Everything from the "Testing" YUM repositories has been moved to the >production YUM repositories. Depending on your type of BlueOnyx that'll >amount to roughly 500 updated and/or new RPMs. > >What's new: >=========== > >GUI: >---- > >- Still the old GUI (am still working on the new one) >- New languages: > - Dutch > - Spanish > - French > - Italian > - Portuguese > The translation for these was done with the Google Translate API, so > the translations aren't perfect. The French locale has been cleaned > up a little (still work in progress) by Meaulnes Legler and Antoine > Hayoz. Many thanks for that! > >New Modules: >------------ > >- base-api: Will now get installed automatically. Allows remote > provisioning of Vsites via a web based API. > More info: http://www.blueonyx.it/index.php?page=api > >- base-istat: Allows monitoring of the server health via an iPhone or > iPad application available in the Apple Appstore. > > >New Features: >-------------- > >- FTP: Better FTPS support. FTP and FTPS can now be separately > enabled/disabled via "Network Services" / "FTP". > >- Web: Apache can now be configured to run on other ports than > the standard port 80 (HTTP) and port 443 (HTTPS). This allows > users to put something else in front of Apache (like a Varnish > cache for example) if they want to. > >- AdmServ: No longer runs as user "httpd", but as user "admserv". > >- 5107R/5108R only: Dovecot now supports TLSv1, TLSv1.1 and TLSv1.2. > Additionally Dovecot has been switched to use stronger ciphers. > >- HTTPS: Vsites that use HTTPS are enforcing the use of stronger > ciphers. On 5107R/5108R TLSv1.2 is also possible now. Wherever > possible "Perfect Forwarding Secrecy" will be used, but for IE > browsers this is not yet possible as our OpenSSL (thanks to > idiosyncrasies on behalf of RedHat) is missing the needed > ECDH ciphers. Additionally "HTTP Strict Transport Security" > will be enforced on HTTPS transactions. For more info on that > one please see: > http://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security > >- "Reseller"-support: It is now possible to use the existing > "Server Administrators" as "reseller" accounts. Each admin > set up that way can be granted extra permissions such as > "Virtual Site Management". He can then create as many sites > and users as you allow him to. Existing Vsites can be moved > to and from the control of such an admin. Suspension and/or > deletion of such an administrator will also affect the > Vsites under his control. The sites will then either be > suspended or deleted, too. > >- Shop Integration: Under "Software Updates" there is a new > menu entry that points to the BlueOnyx Shop and presents > the available products sorted by category. > >- YUM Updates: A scheduled YUM update will now also try to > "auto-complete" your BlueOnyx install. For that it runs a > separate "yum groupinstall blueonyx" after each update run. > That will make sure that your install is not missing any > RPMs that we deem essential and which might or might not > be missing. > >- Updated CMU: This new version of CMU already supports 5207R > and 5208R. > >Bugfixes: >--------- > >I don't know where to start on that one. It's basically too many to >remember. However, these really stick out and should be mentioned: > >- Loss of web server alias on SSL enable/disable: Fixed >- Sporadic loss of MBR record on 5106R with RAID1: Fixed >- Wrong cert concatenation for the Sendmail cert: Fixed > >Generally the whole server alias stuff should now be working a lot more >reliably. In the past we had these cases where either the email server >alias(es) or the web server alias(es) would go walkies. They would still >show in the GUI, but were gone in the respective config files. The >problem there was that quite a few handlers run on these transactions >and sometimes they just got into each others way, too. > >New Bugs: >---------- > >Well, the stuff was in the testing YUM repositories since December. >Every reported bug got fixed. But there still might be the odd glitch >here and there that was missed. If you find something, say so and it'll >get fixed ASAP. > >Problems during the YUM update: >------------------------------- > >I had updated all my own VPS's over the last couple of weeks. I also >just updated a few client servers. The updates themselves throw a few >minor complains here and there with some scripts failing during the >post-install. That is of no concern. > >After this massive YUM update you might experience that the AdmServ >might have stopped or failed to restart. Simply restart it again manually. > >If the YUM update didn't go all the way through, then just do another >"yum update" and it should finish. > >However, so far I haven't seen any larger defects with or after a YUM >update of these new updates. But if you need assistance, please post >here or in emergencies use the contact details on www.solarspeed.net: >https://www.solarspeed.net/imprint/ > >-- >With best regards > >Michael Stauber >_______________________________________________ >Blueonyx mailing list >Blueonyx at mail.blueonyx.it >http://mail.blueonyx.it/mailman/listinfo/blueonyx > > >----- >No virus found in this message. >Checked by AVG - www.avg.com >Version: 2012.0.2247 / Virus Database: 3681/6541 - Release Date: 01/28/14 >Internal Virus Database is out of date. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dirk.estenfeld at bpanet.de Thu Feb 6 05:44:49 2014 From: dirk.estenfeld at bpanet.de (Dirk Estenfeld) Date: Thu, 6 Feb 2014 10:44:49 +0000 Subject: [BlueOnyx:14366] Re: BlueOnyx YUM updates: 5106R/5107R/5108R In-Reply-To: <52F2ED2B.2000602@blueonyx.it> References: <52F2ED2B.2000602@blueonyx.it> Message-ID: <716cab62f0af4b08a55d05da906f50d1@bpa08.bpade.local> Michael, thank you again and again for your great work and the time you are using for this project. I checked an updated server and saw the following problem: My Server-Administrator (not admin, my personal) habe no rights left only root-access. So I had to search for the password for admin to give me rights again. Is this a feature or a bug? Another thing. In "Verf?gbare Privilegien" (in Server-Administrators) I see (in the source code and also at the site)