Koozali.org: home of the SME Server

Masq error on upgrade to 6.0

Craig

Masq error on upgrade to 6.0
« on: November 23, 2003, 09:48:03 PM »
Hi Folks,

I just bit the bullet and upgraded to 6.0   To be safe I backup up my 5.5 server and did a restore on a machine I installed 6.0 on.

On boot up I'm getting this error:

Nov 23 01:26:56 e-smith masq: /etc/rc.d/init.d/masq: line 536: syntax error near unexpected token "done"'
Nov 23 01:26:56 e-smith masq: /etc/rc.d/init.d/masq: line 536:     echo "done"'
Nov 23 01:26:56 e-smith rc: Starting masq:  failed

When I look at the file it looks like this
------------------
;;
"done"
;;
------------------
If I delete the first  set of ";;" and save the file, I can start the Masq service. Still have some problems thought because I'm not getting and DNS resolution, I have to use IP addresses.

Anyone have an idea on what this means?  I'm assuming something came over from the 5.5 machine that's not compatible with 6.0.  

Anyway I can set masq back to it's default setup?

Thanks in advance,

Craig

Charlie Brady

Re: Masq error on upgrade to 6.0
« Reply #1 on: November 23, 2003, 11:24:25 PM »
Craig wrote:

> On boot up I'm getting this error:
>
> Nov 23 01:26:56 e-smith masq: /etc/rc.d/init.d/masq: line
> 536: syntax error near unexpected token "done"'

You have a syntax error in the masq script. Most likely you have an incompatible contrib installed. Another possibility is a custom template.

Be sure that you apply all 6.0b3 updates.

Charlie

Craig Bursey

Re: Masq error on upgrade to 6.0
« Reply #2 on: November 24, 2003, 12:02:10 AM »
Thanks Charlie,

With that comment I checked a little deeper. The section of the Masq file that the error is occuring in is the "# Create a new PortForwarding chain".   I've also noticed that i can delete the extra ";" but on a reboot it's back again,  I know that's because of the templates.

So Charlie, you are right....I had no doubt. :-) On the 5.5 machine I did have the Port Forwarding contribution added but I didn't have anything forwarded. So I guess there is a conflict between the 5.5 contrib and the fact that Port Forwarding is included in 6.0 version.

So I gues the question is now.....how can I delete the old reference to the 5.5 Port Forwarding without affecting the 6.0 Port Forwarding?

Any ideas....anyone???

Thanks,

Craig

Ray Mitchell

Re: Masq error on upgrade to 6.0
« Reply #3 on: November 24, 2003, 02:14:03 AM »
You could remove the contrib and template from 5.5 and then do the upgrade to 6.
Regs
Ray

Craig Bursey

Re: Masq error on upgrade to 6.0
« Reply #4 on: November 24, 2003, 02:30:03 AM »
Thanks Ray,

That's what I figured.  I'm in the middle of redoing the 6.0 machine with a fresh install and I've removed the Port Forwarding contrib from 5.5 and am doing another backup to try it out.

appreciate your help.

Craig

Craig Bursey

Re: Masq error on upgrade to 6.0
« Reply #5 on: November 24, 2003, 04:00:47 AM »
OK,

I've removed the contrib by doing an rpm -e , did a fresh backup and a fresh 6.0 install but I'm still getting the error.  Only after reading Ray's message that it dawned on me.  The Template, how to I remove the template??  Where the heck do I find the template??

Thanks,

Craig

Byte

Re: Masq error on upgrade to 6.0
« Reply #6 on: November 24, 2003, 12:10:02 PM »
you could find the template in the /etc/e-smith/templates-custom/etc/

Check all dirs till you find ref to your template you wish to remove. (think yours could be in rc.d/init.d/masq/)

Then delete that template....run at command following lines

/sbin/e-smith/template-expand /etc/rc.d/init.d/masq

then...

service masq restart

all should return fine

HTH

Byte

Craig Bursey

Re: Masq error on upgrade to 6.0
« Reply #7 on: November 25, 2003, 11:49:02 PM »
So what I finally did was:

1.) Fresh install of 6.0

2.) Checked the /etc/e-smith/templates-custom/etc/rc.d/init.d/masq for templates and there where done.

3.) did a Restore from my 5.5 backup file

4.) Deleted the contents of  /etc/e-smith/templates-custom/etc/rc.d/init.d/masq

5.) Did a post-upgrade and a Reboot

6.) Everything appears to be fine

Does anyone see a problem with me doing this?  I hope not.  ha ha

Thanks,

Craig