filippo_carletti
Dev Team
January 12
paul_marwick:
I didn't realise
that the migration did not import data from the
SME backup, only settings.
No, the migration
imports everything: settings AND data.
Obviously, data has to be present in the backup.
:) My error - I had forgotten that NS uses different locations for
mail and iBays. The data was there…
<img moz-do-not-send="true" alt="" src="https://avatars.discourse.org/letter/p/a9adbd/40.png" style="margin-right: 5px; width:20px; height:20px;
max-width:100%;" height="20" width="20">paul_marwick:
it imported
things like /root/.ssh, but failed to pick up
/root/.synbak/tar
AFAIK, the whole
/root directory is copied (I did tens of migrations).
On my second attempt it was, but for some reason some things weren't
on the first attempt.
paul_marwick:
Is there an
equivalent to the “signal-event post-upgrade;
signal-event reboot” that SME uses to expand all
templates?
I'd say NO, because
NS don’t need such a big hammer. But to expand all
templates and restart the relevant services (no
reboot, a business server shouldn’t be rebooted) you
can use:
Thanks. The reboot sequence that SME always seems to need is one o
fmy least favourite features I must admit. I’ll keep that one in
mind.
> /etc/e-smith/events/actions/system-adjust
paul_marwick:
Is it possible
to use a text-mode browser with the Nethserver
server manger?
Yes:
> elinks [https://localhost:980](https://localhost:980)
` I've not managed to get that to work. Elinks comes up with SSL
errors. Lynx gets a bit further, but still fails to load the
server manager.
`
paul_marwick:
ability to limit
server manager access to specific IPs
Access to all
network services can be limited through the Network
services menu.
I've not looked closely at that yet.
I ended up trying again, twice. I ended up with errors both times,
so I must be doing something wrong. I’ve captured the section of
/var/log/messages just before the error starts:
Jan 13 16:17:57 goldie esmith::event[28751]: Migrating existing
database fetchmail
Jan 13 16:17:57 goldie esmith::event[28751]: Migrating existing
database dhcp
Jan 13 16:17:57 goldie esmith::event[28751]: Action:
/etc/e-smith/events/nethserver-mysql-update/S00initialize-default-databases
SUCCESS [0.240041]
Jan 13 16:17:58 goldie esmith::event[28751]:
Jan 13 16:17:58 goldie esmith::event[28751]:
Jan 13 16:17:58 goldie esmith::event[28751]:
Jan 13 16:17:58 goldie esmith::event[28751]:
Jan 13 16:17:58 goldie esmith::event[28751]: NOTE: RUNNING ALL PARTS
OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL
Jan 13 16:17:58 goldie esmith::event[28751]: SERVERS IN
PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!
Jan 13 16:17:58 goldie esmith::event[28751]:
Jan 13 16:17:58 goldie esmith::event[28751]:
Jan 13 16:17:58 goldie esmith::event[28751]: In order to log into
MySQL to secure it, we’ll need the current
Jan 13 16:17:58 goldie esmith::event[28751]: password for the root
user. If you’ve just installed MySQL, and
Jan 13 16:17:58 goldie esmith::event[28751]: you haven't set the
root password yet, the password will be blank,
Jan 13 16:17:58 goldie esmith::event[28751]: so you should just
press enter here.
Jan 13 16:17:58 goldie esmith::event[28751]:
Jan 13 16:17:58 goldie esmith::event[28751]: Enter current password
for root (enter for none):
Jan 13 16:17:58 goldie esmith::event[28751]: ERROR 1045 (28000):
Access denied for user ‘root’@‘localhost’ (using password: NO)
Jan 13 16:17:58 goldie esmith::event[28751]: Enter current password
for root (enter for none):
Jan 13 16:17:58 goldie esmith::event[28751]: ERROR 1045 (28000):
Access denied for user ‘root’@‘localhost’ (using password: NO)
Jan 13 16:17:58 goldie esmith::event[28751]: Enter current password
for root (enter for none):
Jan 13 16:17:58 goldie esmith::event[28751]: ERROR 1045 (28000):
Access denied for user ‘root’@‘localhost’ (using password: NO)
In the first case, I'd set up the correct domain information and the
name of the server that the backup is derived from. I’d also updated
the NS installation and added the necessary packages to cover the
functions that I needed. In the second, I’d not set the domain to
what it should be eventually, but the error was the same in each
case.
I'll have another look in a couple of days - too many jobs to do for
the next few days.
Paul