Topic: Upgrade 5.1.2 to 6.0b3

[Brian Read]

I am doing a weekend update of a system from 5.1.2 to 6.0b3.  6.0final came too late, and I decided I cannot risk it in a production environment.  I started by ghosting the hard disc, so that i had a fallback position, and then applied the 6.0b3 release.  The upgrade seemed to go well, and I also applied all the upgrade RPMs.

The system is server and gateway with an analogue modem.

There seem to be two problems - the system refuses to resolve any symbolic internet addresses, although it will dial out if I ping an IP address, and it rejects any mail on port 25 from a workstation.

I have been through the server manager panels and saved each one, and they all "work" except the email panel which fails with an "error".

Looking in /var/log/messages, the panel fails with a perl error:

ERROR in /etc/e-smith/templates//var/service/smtpfront-qmail/env/DATABYTES: Program fragment delivered error <> at template line 1
ERROR: Template processing failed for //var/service/smtpfront-qmail/env/DATABYTES: 1 fragment generated errors

Looking back in the log, I found this:

Dec 13 10:11:54 Server e-smith[996]: ERROR in /etc/e-smith/db/configuration/migrate//20mailfront: Program fragment delivered error <> at template line 1

This seems to have happened as part of the 6.0b3 installation/upgrade and then also when the RPM upgrade was done.

So I looked at the offending line in the 20mailfront and it looked at though a "$DB->" was missing (although I am a perl novice).  I corrected this, but cannot see how to "re execute" the migrate stuff.  I tried re-applying the RPM update and did the post-upgrade and reboot, but I don't think it did it, because the email panel still fails.

Any ideas anyone?

Brian

[Michael Smith]

Hm, I had the exact same thing happen with a 5.1.2 to 6.0b3 server with regards to Internet access and masq just a couple of days ago ... haven't resolved it yet.  Didn't see the email error.  Will advise when/if I find a resolution.

[Steve Bush]

I had the same problem on a couple of older server upgrades to 6.0b3.
the Services  are turned off because records in the configuration db file aren't there. I seem to recall smb, dns (dnscache or tinydns), and smtpfront-qmail.

[Ray Mitchell]

Dear Brian Read

> I am doing a weekend update of a system from 5.1.2 to 6.0b3.
> 6.0final came too late, and I decided I cannot risk it in a
> production environment.  

How is it that you can "risk" using a beta version on a production machine, but you cannot risk using the final version  on a production machine (which has security updates etc) ???
Surely if the final release is available you would now use that instead of the beta ?

Regs
Ray

[Brian Read]

Ray Mitchell wrote:
 
> How is it that you can "risk" using a beta version on a
> production machine, but you cannot risk using the final version
>  on a production machine (which has security updates etc) ???
> Surely if the final release is available you would now use
> that instead of the beta ?

The general consensus on here was the the 6.0b3 was ok for production use, however the "final" came out only on the thurs when i was off to the customer on the friday (a two hour drive), and i had not time to try it myself (wheras i 'd been running 6.0b3 for some time on my test server).

In he event i went back to 5.1.2 and then upgraded to 5.5, then 5.6 and left it there for now.  I'll be back there in April, and will do another update then.

Cheers

Brian

[Steve Bush]

I would have made the exact same decision as you did.
I have numerous sme6.0b3 servers in the field with no problems.
The first release of the 6.0 final iso had a problem, which was resolved.
Without time to test, I wouldn't have chanced it either!!!

[Brian Read]

I think Charlie's contribution in this thread would have fixed it.

http://forums.contribs.org/index.php?topic=19269.msg76236#msg76236

Cheers

Brian