Topic: Bad experience of upgrading to v6 b3

[ChiWai]

I upgrade my server (V5.6) to V6 beta 3.
The e-mail is working fine.  But this is the only thing working fine for me.

The DNS can resolve hostname.  But it cannot accept query from the Internet.  I had to setup a separate DNS server to solve this problem temporarily.


The e-smith is the domain controller in my network.  After the upgrade, the all Windows clients cannot trust one another even they belong to the same domain.  I had to use a Windows 2000 server to act as a domain controller.


I have virtual domains to host the web page.  After the upgrade, the configuration for Apache does not properly handle the virtual domains.  I have to create scripts in "template-custom" to fix the problem.

I think it is a bad idea to upgrade e-smith.  
Can anybody tell me what is the safe method to upgrade?
I wonder if e-smith v6 b3 is working fine if it is a fresh install.

[Dan Brown]

Well, first, as has been posted here too many times to count, all issues with the 6.0 beta should be reported to smebugs@mitel.com.

Second, have you installed the latest updates?  I understand that virtual domains are an issue addressed by them.

Third, no version of e-smith/SME has ever been designed to be a publically-accessible DNS server.  If you had configured your 5.6 box to serve in that capacity, 6.0 would almost certainly break it, as it uses a different DNS server than 5.6 and previous did.

Fourth, I have no idea about the windows problem--again, a note to smebugs@mitel.com, with all the details you can provide, would be the best way to proceed.  After all, this is a BETA, not intended as a production release.  Installation on a production server is at your own risk.

[ChiWai]

I think I should install new version of SME on another server.  Then fully test it before I move all the data from the production server to new SME server.

[Gregory Baird]

Hello

I have been running beta 6.03 since it came out I have installed all of the patches after I did a restore using a backup of my 5.6 server
and have had NO problems it is happy and is my production server

I did run 6.03 bare for a few days trying to find a bug
also wish Dan Brown would not reply you would think he owns
this newsgroup and I have never seen him help only tell people to email bugs@smeserver

I use zoneedit for offsite dns it is free for 5 domains
and use coyote linux for a firewall it will give you better protection than sme

hope this helps
Greg

[Dan Brown]

Well, if you've never seen me do anything but send people to smebugs, you haven't been reading very closely, even in this thread--notice that I suggested installing the latest updates, which address (among other things) an issue with virtual domains.

Folks, this is a beta release.  That means it's still in development, and there are likely to be bugs in it.  The Mitel developers track those bugs through the smebugs mailbox, and may not check here.  I don't personally completely agree with this philosophy; it'd certainly be easier for users if potential bugs were discussed openly.  However, it isn't my product, and these aren't my boards--it, and they, belong to Mitel, and they have asked that "Comments or bug reports should be sent to smebugs@mitel.com (and only there, please)".  Since that message is in large, bold print on the front page of e-smith.org, and people persist in not only posting bug reports with the beta here, but often posting the *same* bug report with the beta here, I think it's appropriate to direct them to the right place to go.

Now, if we're going to talk about not being helpful, your unsupported recommendation to "use coyote linux for a firewall it will give you better protection than sme" isn't very helpful, either.  Not only is it absolutely, totally, and in all other ways irrelevant to any of the questions asked, it's also likely to be incorrect.

OTOH, I completely agree about zoneedit.com; I use them as well.

[Gregory Baird]

Dan

I don't know what you mean unsupported recommendation
to use coyote firewall I will offer any help that I can when I feel it is
accurate I do run a couple of sme boxes and they are "sme" some very fine techs that have put it together

It is my experience however that using sme as a gateway leaves your whole network wide-open I have reviewed many firewall programs and found coyote to be one of the best free ones out there and was my feeling to past the information along as the internet is seeing more troubles or problems than ever

I thought this newsgroup was to help others out !
I did not say to forget sme I have seen mysql questions
on this site shouls they be refered to bugs@mysql

I am sure that sme bugs is and had been well aware of the vitual domain problem I did not feel that sending chiwai the report a bug was productive however I spent 2 minutes of my time to help
I have been running sme BETA 6.03 since it was out and have installed all updates It is running as a production server with no problems I still see problems  and complaints with 5.5 and 5.6
witch one is the beta

I feel that there is not beta software or we would never improve what we haveDan Brown wrote:
>
> Well, if you've never seen me do anything but send people to
> smebugs, you haven't been reading very closely, even in this
> thread--notice that I suggested installing the latest
> updates, which address (among other things) an issue with
> virtual domains.
>
> Folks, this is a beta release.  That means it's still in
> development, and there are likely to be bugs in it.  The
> Mitel developers track those bugs through the smebugs
> mailbox, and may not check here.  I don't personally
> completely agree with this philosophy; it'd certainly be
> easier for users if potential bugs were discussed openly.
> However, it isn't my product, and these aren't my boards--it,
> and they, belong to Mitel, and they have asked that "Comments
> or bug reports should be sent to smebugs@mitel.com (and only
> there, please)".  Since that message is in large, bold print
> on the front page of e-smith.org, and people persist in not
> only posting bug reports with the beta here, but often
> posting the *same* bug report with the beta here, I think
> it's appropriate to direct them to the right place to go.
>
> Now, if we're going to talk about not being helpful, your
> unsupported recommendation to "use coyote linux for a
> firewall it will give you better protection than sme" isn't
> very helpful, either.  Not only is it absolutely, totally,
> and in all other ways irrelevant to any of the questions
> asked, it's also likely to be incorrect.
>
> OTOH, I completely agree about zoneedit.com; I use them as
> well.

[Dan Brown]

In what way does using SME as a firewall leave your network "wide open", and how does Coyote fix that?  Not that it's relevant to what the original poster asked in any case, but all you've said here (twice now) is that you think Coyote is better, without giving any reasons (and if there are vulnerabilities in SME, I'm sure Mitel would like to know about them).

Now, as to MySQL, if somebody is running into suspected bugs in a pre-release, beta version of MySQL, those should definitely be sent to whatever system the MySQL developers have set up to track bugs.  Serious, in-depth questions about MySQL would probably also be better on the MySQL support boards/lists/groups/whatever they have set up--there are simply going to be more people there who will understand what's going on and be able to help.  But since nobody from Mitel has said that discussion of MySQL is inappropriate here, there's not a problem discussing it here--it just isn't as likely to be as helpful as some of the more dedicated MySQL resources.

However, as I've already pointed out, Mitel (who runs these boards) _has_ said that discussion of issues in the 6.0 beta is inappropriate here.  Why is that so difficult to understand?