Topic: Upgrade Disk process - trouble mounting old drive

[pssl]

Mary,

Thanks.  I'll get the info you asked about.

If I do the process over, should I start at step one (/sbin/e-smith/signal-event pre-backup) on the old server?  I don't know what the command does, so I don't know if it'll mess anything up if it is done twice.  When I first ran it, it ran without incident but then I did not check the logs to verify that all went well.

[cactus]

I don't know what the command does, so I don't know if it'll mess anything up if it is done twice.

Most important thing is that it will dump the MySQL databases to a directory, so that they can be (automatically) restored on a new machine. It's no problem to run that command multiple times in a row (there's no benefit either).

[janet]

pssl

As cactus says that first command makes a copy (ie dumps) the mysql databases, so they are ready in seperate files to be restored. Mysql databases cannot be reliably backed up when the databases are in use, so a "dump" is done to workaround this issue. Refer mysql literature for more info re dump.
On the new server you can mount the old drive and then do
ls -al /mnt/tmp/home/e-smith/db/mysql
to check if the dump files are there.

If no changes have been made to the old SME6 system, then it is a waste of time doing that step again, ie as you have to reconnect the drive to the old machine etc.

If you have used the old server and made changes since you last attempted the restore, then you should run that command again on the old server.

Generally speaking you seem to be careful when issuing your commands etc, so redoing the process may not gain anything, although it is worth trying just in case something went wrong the first time.
I feel it is useful to check the data is on the old disk, check that the mysql dump files are there, and prove that you can copy (ie read) files from the old disk OK, before trying the process again.
 

[pssl]

Mary,

First, I apologize for not answering all you're questions from you response of the 18th...just failed to see them.  Here is the output of config show backup:

Code: [Select]

backup=service
    BackupType=tape
    Progam=CopyFromDisk
    Program=flexbackup
    backupTime=2:00
    reminderTime=14:00
    status=enabled

My uneducated guess is it looks OK.

I am able to copy files from the old drive to the new.  I also verified that the ibays directory on the new system does not contain the files from the old system.

The mysql dump file is on the old drive.

So unless you see a problem with config output, redo it is then.  Thanks for your help.

[cactus]

I am able to copy files from the old drive to the new.  I also verified that the ibays directory on the new system does not contain the files from the old system.

That is a start.

The mysql dump file is on the old drive.

Ok, as well.

So unless you see a problem with config output, redo it is then.  Thanks for your help.

I don't but then again I do not use flexbackup, perhaps Mary can confirm this one.

[pssl]

Thanks cactus.  All,

I restarted the process...yeah...success so far...it's merrily rattling on as we speak.

[cactus]

I restarted the process...yeah...success so far...it's merrily rattling on as we speak.

That's good to hear.

[pssl]

Well, I finished the upgrade process.  I bypassed the part where the template directories are moved and recreated figuring that that was already done in the first attempt and I never removed them.  Wasn't sure if that was the right thing to do.  After reboot I'm getting a constant message dumped on the screen:

Code: [Select]

Cannot assign requested address: make_sock: could not bind to address 192.168.0.5:443
no listening sockets available, shutting down
Unable to open logs
I couldn't get control so I had to do a hard shut down.  After reboot got the same thing.  System's fried.  Unless you folks have a suggestion, I'll have to re-install and upgrade again.  Oh well, should be quicker this.

Update: noticed during boot a message sped by

Code: [Select]

WAN:                   FAILED  Can't give more info than that because it all goes by so fast and I can't get to the logs.

[janet]

pssl

Good that the restore now appears to work.

You should have done those commands re moving the old templates.
You will need to manually perform those steps again.

Your problem now is getting control of the command prompt.

I suggest you boot up to the SME7.5 CD in rescue mode, and then get access to the system and then perform those steps that move the old templates and so on.
See
http://wiki.contribs.org/Booting
Search the forums and this site on rescue mode for further info. There have been a number of posts re what to do when in rescue mode, but essentially just follow the prompts.

After that, do again the steps
signal-event post-upgrade
reboot

Maybe when the system reboots normally it will be OK, advise back here.
If not you will need to do some further troubleshooting.

If it boots up OK, then you should login as admin and select the "Configure this server" option and configure appropriately for your current situation/location.

Note also in your earlier post the db entry shows
    Progam=CopyFromDisk
    Program=flexbackup

At some point you entered the db command incorrectly, mispelled Program as Progam, that's why there are two entries. Obviously the restore has worked so I assume you re-entered the command correctly and that post above is from the earlier first attempt, which would explain why the restore did not run the first time you tried it.

[pssl]

Thanks Mary.  Progam eh...I'm gettin' too old for this.  I'll let you know how goes.  Thanks again.

[cactus]

Note also in your earlier post the db entry shows
    Progam=CopyFromDisk
    Program=flexbackup

At some point you entered the db command incorrectly, mispelled Program as Progam, that's why there are two entries. Obviously the restore has worked so I assume you re-entered the command correctly and that post above is from the earlier first attempt, which would explain why the restore did not run the first time you tried it.

Good shooting! I totally overlooked that one. Kudos Mary!

[janet]

cactus

I learnt it from Charlie, read everything carefully.
.... and it helps to have eyes in the back of your head !

[cactus]

.... and it helps to have eyes in the back of your head !

I can think of more attractive features

[pssl]

 

I'd settle for a good pair of eyes in the front of my head.

[janet]

pssl

......Progam eh...I'm gettin' too old for this....

That's why when issuing db commands to make changes, it's a good idea to check your work as you go along. Checking before & checking after is also a good policy too.
Check before making changes & record what the current settings are, that way it's easy to revert any "about to be made" changes, back to original values, should the need arise.
Check after making a change to ensure the correctness of your work ie check for mispellings or other types of errors, before you actually generate configuration file changes using the expand template & restart of services.

ie in this case use the command
config show backup
See this Howto to help understand using the db command, it is really VERY easy once you grasp the concept of database names, keys, properties & values (ie which is which ?).
http://wiki.contribs.org/Db_command_tutorial

So you can add some steps eg
db configuration show backup
which displays
backup=service
    BackupType=tape
    Program=flexbackup
    backupTime=2:00
    reminderTime=14:00
    status=enabled

then make the actual change required
db configuration setprop backup Program CopyFromDisk status enabled
then check the new setting
db configuration show backup
which displays
backup=service
    BackupType=tape
    Program=CopyFromDisk
    backupTime=2:00
    reminderTime=14:00
    status=enabled

In the case of an error or mistyping, it should be apparent as the Program property did not change, but in fact you added a new property called Progam, not what was intended ie it would display
backup=service
    BackupType=tape
    Progam=CopyFromDisk
    Program=flexbackup
    backupTime=2:00
    reminderTime=14:00
    status=enabled

So to fix this  error you would remove the incorrect entry, and then redo the command correctly ie
db configuration delprop backup Progam
then check your work !