Topic: unable to connect server-manager after moving sme to new hardware with affa

[kenober]

I am a teacher and  admin in my school.
I have sme 7  for 5 years . It works great .
I have to change the hardware because it began to be too little for my works.
I decided for sme8

I followed all the contribs with no problems during the installation.
http://wiki.contribs.org/Moving_SME_to_new_Hardware


But after some tests , I have almost  the same thing like
 http://forums.contribs.org/index.php?topic=48083.0
1. from my laptop I cannot access server-manager (https://192.168.0.1/server-manager)
 My laptop can ping the server.

2. using the console with admin at the prompt
I DO get the menu, and do most things (configure, check internet, check redundant disks)
but try to access server-manager I get
Unable to retrieve http://localhost/server-manager    connection refused


So i try :

sv s httpd-e-smith
sv s httpd-admin
httpd -t
httpd -t  --> syntax ok

and also
# servive httpd-admin restart  and
#signal-event post-upgrade ; signal-event reboot

no effects always the same


I test
#rpm -qa –last| grep e-smith-manager
e-smith-manager-2.2.0-7.el5.sme

and

#tail /var/log/httpd/admin_errors_log
[notice] caught SIGTERM, shutting down
[notice] SSL FIPS mode disabled
[warm] Init : SessionCache is not configured [hint : SSLSessioCache]
[notice] Digest : generating secret for digest authentification...
[notice] Digest : done
[notice] SSL FIPS mode disabled
[notice] Apache configured –resuming normal operations

What did i forget to find a solution ?
Could anyone suggest what I check out?

[purvis]

I would just love to plug one of the SME raid 1 drives and put it in a new system. That goes for other operating systems. Even Appe system will notice some change in hardware and the os will make some changes.

I just bite the bullet and do a new install with each change in motherboard where the motherboard is likely newer and different.

For Me that means i need to do an extensive backup multle times to gather all data on different media. I use windows workstations for this and use xcopy bc I am familiar with it and I know how to compare files well. This does take a long time but I am most comfortable with it.

Then I pull one of the raid 1 disk out and shelve it for backup purposes.

Once my data is copied from the I bays., I delete all files and directories in the I bays leaving only what files  and directories SME created when the inau was created.
I also leave the Primary ibay intact, meaning I don't delete file's from there.

Then using the backup routine located in the server mange, I do multiple backups to multiple workstations. Hopefully the data will not be too big.

The Internet connection to the server would have been pulled or disabled in the beginning.

Then I rebuild a new server only restoring my SME backup then any additional contribs then the ibay data I had backed up to workstations.

The last sme backup file "smeserver.tgz"  made is created on a computer that is able to transfer the file to a web server my newly built server can access.

The new server down loads the smeserver.tgz file from your web server holding it.
You could use a CDROM/dvdrom or whatever media.
Then restore your system using the local smeserver.tgz.

I am sorry that I did not have an answer the original poster was looking for.
If there is a better way. Then good.

The way I do it allows me to generally know how much time in advance I am going to need.
And I know what headaches I am going to face.

We do not have a lot of emails and 0(zero) user files on our servers.
Those two things allow for a smeserver.tgz to small enough to manage.

Fast equipment comes into play while doing this if you have a lot of data along with a local equipment.