Topic: signalevent console-save

[Henrik]

Hi there

I have a problem whenever I make a custom-template change:

The templates works 100% but when I do a console-save, a lot of settings are returned to default settings.

1. SSH is set back to private access only
2. FTP gets disabled or set to private only
3. POP3 access is set to private only.
4. some other settings i dont remember right now

This has been happening since V5.5, current version is 5.6U4 and still the same problems because i forget to set all the correct settings back again which should not be nessesary.

Anybody have any ideas where I should start looking?

/Henrik

[Dave Liquorice]

> The templates works 100% but when I do a console-save, a lot of
> settings are returned to default settings.

Are you making sure that the changes you make are also made in the configuration database? That is your custom templates ought to read the settings from the database not have them hard coded. Though even without that the custom templates ought to be used rather than the orginals.

The configuration database is /home/e-smith/configuration and the custom templates should be in  /etc/e-smith/templates-custom, but  follow the structure below that directory carefully. For example  changes to /etc/crontab should be in files in directory  /etc/e-smith/templates-custom/etc/crontab.

Cheers
Dave.

[Henrik]

Dave Liquorice wrote:
>
> > The templates works 100% but when I do a console-save, a
> lot of
> > settings are returned to default settings.
>
> Are you making sure that the changes you make are also made
> in the configuration database? That is your custom templates
> ought to read the settings from the database not have them
> hard coded. Though even without that the custom templates
> ought to be used rather than the orginals.
>
> The configuration database is /home/e-smith/configuration and
> the custom templates should be in
> /etc/e-smith/templates-custom, but  follow the structure
> below that directory carefully. For example  changes to
> /etc/crontab should be in files in directory
> /etc/e-smith/templates-custom/etc/crontab.
>
> Cheers
> Dave.


As described in my post, its not the custom templates that don't work, its the default server settings like remote access etc. that gets reset.

[Dave Liquorice]

> As described in my post, its not the custom templates that don't
> work, its the default server settings like remote access etc. that gets
> reset.

Fine, now answer the questions I orginally asked and these.

How are you calling the custom templates? Directly or via /sbin/e-smith/expand-template ?

Are you updating the configuration database to reflect your changes?

Cheers
Dave.

[Henrik]

Dave Liquorice wrote:
>
> > As described in my post, its not the custom templates that
> don't
> > work, its the default server settings like remote access
> etc. that gets
> > reset.
>
> Fine, now answer the questions I orginally asked and these.
>
> How are you calling the custom templates? Directly or via
> /sbin/e-smith/expand-template ?
>
> Are you updating the configuration database to reflect your
> changes?
>
> Cheers
> Dave.


Thanks Dave, for replying

Exampel: I've followed this howto on vdomain e-mail alias e-mail: http://mirror.contribs.org/smeserver/contribs/dmay/mitel/howto/vdomain-alias-howto.html

works fine, exept the settings as descriped in my first post returnes to default...

[Dave Liquorice]

> Exampel: I've followed this howto on vdomain e-mail alias e-mail:

Well that doesn't involve making any adjustments to the  settings you mention. So as you say they keep getting reset back to the defaults this implies that you are changing them back to your prefered settings after they have been reset. How are you changing them? You must ensure any changes are reflected in the configuration database otherwise they won't be permenant. Either by using the e-smith scripts, the server-manager or admin interfaces.

Cheers
Dave.

[Henrik]

Dave Liquorice wrote:
>
> > Exampel: I've followed this howto on vdomain e-mail alias
> e-mail:
>
> Well that doesn't involve making any adjustments to the
> settings you mention. So as you say they keep getting reset
> back to the defaults this implies that you are changing them
> back to your prefered settings after they have been reset.
> How are you changing them? You must ensure any changes are
> reflected in the configuration database otherwise they won't
> be permenant. Either by using the e-smith scripts, the
> server-manager or admin interfaces.
>
> Cheers
> Dave.


I use the server-manager to set the settings back....

[Dave Liquorice]

> I use the server-manager to set the settings back....

One assumes that you are clicking the relevant "save" buttons after you have made the changes.

After quiting your bowser have those changes been reflected in the configuration database after you have made them? Look at the configuration database file  directly with mc, pico WHY.

Cheers
Dave.

[Henrik]

Dave Liquorice wrote:
>
> > I use the server-manager to set the settings back....
>
> One assumes that you are clicking the relevant "save" buttons
> after you have made the changes.
>
> After quiting your bowser have those changes been reflected
> in the configuration database after you have made them? Look
> at the configuration database file  directly with mc, pico WHY.
>
> Cheers
> Dave.

I can see that the config is correct. (hence it works fine on a reboot, but not when a console-save is issued)

Ex. from my config:

sshd=service|InitscriptOrder|85|PasswordAuthentication|yes|PermitRootLogin|yes|access|public|status|enabled
ftp=service|access|public|accessLimits|normal|status|enabled

So its look's like this config is overwritten when a console-save is issued, with default settings.

[Dave Liquorice]

OK, now that we have tracked it down to some oddity in console-save I suggest you report it to smebugs@mitel.com.

However are you or something else changing the system mode (server only, private server/gateway, public server/gateway)?  That triggers console-save to reset things to the defaults for that mode . SSH and FTP access being some of those. If the system mode isn't changed console-save should not do anything. Compare the configuration and configuration.previous database files.

Cheers
Dave.

[Stan Coleman]

I have a similiar problem after I upgraded from 5.6 to 6.0. I can change the FTP settings in the Server-Manager to Public but when you go back to the same page it's reset to priviate. Settings in /home/e-smith/configuration are set to public yet no public server is available. I've mentioned it to bugs@e-smith but haven't gotten any response. Just thought I'd add my cent and a half to let you know you're not alone.