[BlueOnyx:16106] Re: New BO 5208R Install - Major Issue.

[Richard Gutery]

Thank you for getting back to me.

Issue 1; we did do a YUM update right after the install (as a matter of
policy, we always do so). The passwords that we use are always very
complex(U/L Case, Special Symbols etc). I believe the issue here is that we
used a Dollar Sign ($) for the letter S and other similar alpha characters.
We changed our policy to NOT use the $ as it is of course a PHP element. So
that is fixed - our bad.

Two questions/advise:
1) Should we use BlueOnyx-5208R-CentOS-6.5 OR BlueOnyx-5208R-SL-6.5. This
one we are Not Sure of the benefits, recommendations etc,
2) We will eventually (once we are very comfortable with BO), be installing
onto a Dell 710 Blade server (one of several). These servers already have
Built-in Hardware RAID configured for the impending OS install and Data. We
can either delete the DATA raid volume or unplug. I think my understanding
is that if we just delete the RAID Set for Data, BO will Raid the drive
anyway?

Again, thanks for the reply and guidance.


On Sat, Oct 4, 2014 at 9:49 AM, Michael Stauber <mstauber at blueonyx.it>
wrote:

> Hi Richard,
>
> > <<<<<<<<<<<<<<<<<<<<< ERROR START >>>>>>>>>>>>>>>>>
> >
> > A PHP Error was encountered
> >
> > Severity: Notice
> >
> > Message: Array to string conversion
> >
> > Filename: controllers/wizard.php
> >
> > Line Number: 1388
> > Fatal error: ob_start() [<a href='ref.outcontrol'>ref.outcontrol</a>]:
> > Cannot use output buffering in output buffering display handlers in
> > /usr/sausalito/ui/chorizo/ci/system/core/Exceptions.php on line 181
> >
> > <<<<<<<<<<<<<<<<<<<<< ERROR END>>>>>>>>>>>>>>>>>
>
> Most likely the password you set for "admin" or for MySQL was too
> simple. The line 1388 error is when the errors are evaluated that
> happened up until that point. The password errors are the only errors
> that cause it to "barf" this way. Usually errors should be arrays, but
> these two are returned as strings.
>
> I think this was fixed in a YUM update, but it happened after the CDs
> were built. So unless you did a "yum update" before using the GUI the
> problem was still there, as it was using the version from before the fix
> was published.
>
> > When installing, we are selecting "No dmraid" option, yet the
> installation
> > process creates a  RAID set. When checking the status of the Raid set
> > (disk, members etc), the result is (essentially) no raid set defined.
>
> The "no dmraid" option is not meant to "spare" a disk from not being
> formatted. Whatever disks you have attached to the server WILL be
> formatted and re-partitioned when the installer runs. There is no way
> around that and this is how it always has been.
>
> If you don't want the installer to do that, you need to physically
> disconnect the disks (unplug the cables) that it shouldn't mess with.
>
> --
> With best regards
>
> Michael Stauber
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at mail.blueonyx.it
> http://mail.blueonyx.it/mailman/listinfo/blueonyx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20141004/8ddbd6c4/attachment.html>