Koozali.org: home of the SME Server

SME server-manager not accessible

ross

SME server-manager not accessible
« on: December 13, 2003, 11:27:56 PM »
After a reboot my e-smith 5.6 complained about
a dirty file system that it couldn't clean.
I gave it my root password and ran "fsck /dev/hda3"
After that finished and I rebooted I could not
access the server-manager, not even from the
server-console -- instead I get the error message...
500 Internal Server Error
The server encountered an internal error or misconfiguration
and was unable to complete your request.

Any ideas or suggestions appreciated.

David


floyd

Re: SME server-manager not accessible
« Reply #2 on: December 13, 2003, 11:56:37 PM »
Can you ssh into your box?

ross

Re: SME server-manager not accessible
« Reply #3 on: December 14, 2003, 01:38:55 AM »
I can ssh into the system. I can do _everything_ with
the system, except access the server-manager.

lars

Re: SME server-manager not accessible
« Reply #4 on: December 15, 2003, 11:59:33 AM »
I've got exactly the same trouble after an update from 5.6 to 6.0dev. Looks like one or some of the server-manager's web files are corrupted. Everything works just fine, execpt fot the error 500 message while accessing the server-manager. (Via http https ssl and from the console).

How does one replace them with fresh copy's? I'd tried to force update a view packages that revered to the server-manager's files. Fo far no results...

ross

Re: SME server-manager not accessible
« Reply #5 on: December 16, 2003, 08:16:02 AM »
lars wrote:

> I've got exactly the same trouble after an update from 5.6 to
> 6.0dev. Looks like one or some of the server-manager's web
> files are corrupted. Everything works just fine, execpt fot the
> error 500 message while accessing the server-manager. (Via http
> https ssl and from the console).
>
> How does one replace them with fresh copy's? I'd tried to
> force update a view packages that revered to the
> server-manager's files.

That is exactly what I would like to do also, but
I can't find a list of the exact set of rpms that make
up the server manager.

lars

Re: SME server-manager not accessible
« Reply #6 on: December 16, 2003, 10:24:21 AM »
I'd did a wild search on some search engines to, but no results what so ever. So I've posted this issue on the dutch forum to. So guess we'll have to try some more rpm's or wait for a genious who knows what rpm's to force install. So far I'd handpicked a few that had a name with a logical link to the server-manager but that did'nt do the trick (yet).ross wrote:

> ross wrote:
>
> That is exactly what I would like to do also, but
> I can't find a list of the exact set of rpms that make
> up the server manager.

ross

Re: SME server-manager not accessible
« Reply #7 on: December 17, 2003, 01:20:33 AM »
I've done the same as you. I've also tried to
find out what is the configuration file for the
server-manager maybe something went wrong with that
and it could be reset to default values or replace
with a generic copy?


lars wrote:

> I'd did a wild search on some search engines to, but no
> results what so ever. So I've posted this issue on the dutch
> forum to. So guess we'll have to try some more rpm's or wait
> for a genious who knows what rpm's to force install. So far I'd
> handpicked a few that had a name with a logical link to the
> server-manager but that did'nt do the trick (yet).ross wrote:
>
> > ross wrote:
> >
> > That is exactly what I would like to do also, but
> > I can't find a list of the exact set of rpms that make
> > up the server manager.

lars

Re: SME server-manager not accessible
« Reply #8 on: January 01, 2004, 10:22:52 PM »
Happy New Year!

Since there's not even a single addequate reply in both forum's. I guess the question is eihter to easy or... the answer is a Mitel secert. Anyhow I´d reinstalled a perfectly fresh 6.0dev on the machine and that´ll be it for me.

Ross.. You could try to restore the files from a backup. I tried during the hollydays, but it did not work out for me. So it could be that the files had gone corrupeted just at time of the last backup, just before my migration from 5.6 to 6.0dev! How about bad luck?

Kind regards, and signing off... Lars.



ross wrote:

> I've done the same as you. I've also tried to
> find out what is the configuration file for the
> server-manager maybe something went wrong with that
> and it could be reset to default values or replace
> with a generic copy?
>
>
> lars wrote:
>
> > I'd did a wild search on some search engines to, but no
> > results what so ever. So I've posted this issue on the
> dutch
> > forum to. So guess we'll have to try some more rpm's or
> wait
> > for a genious who knows what rpm's to force install. So far
> I'd
> > handpicked a few that had a name with a logical link to
> the
> > server-manager but that did'nt do the trick (yet).ross
> wrote:
> >
> > > ross wrote:
> > >
> > > That is exactly what I would like to do also, but
> > > I can't find a list of the exact set of rpms that make
> > > up the server manager.

Arne

Re: SME server-manager not accessible
« Reply #9 on: January 02, 2004, 04:47:37 AM »
Do you have a ok backup, or will you have to produce a new and fresher backup from shell and then use this for the restore ? (That will also have to be done from shell as the backup will be different from the ordinary workstation based backup.)

I did this a few days ago a number of times for training purposes.

There is an issue if you want to make an upgrade to 6.0 at the same time. The directory structure of the 5.6 oand the 6.0 have changed a bit arount the area of the ibays and the primary directory, so if you just make an shell based restore, file for file and directory for directory, it will be a few problems about this (I ended up with a double set of primary directories and some other problems related to this.)

Backing up and restoring datas from and to v 5.6 worked rather ok using an extra hd, shell access and rsync. (It's rather easy to make the backup, but you have to be rather accurate doing the restore. If not specifying the datas right and precisely the rsync restore could quite easy crash the new installation. Anyhow you will still have the backup so you can make a new try.)

The procedure would eventually be something like this:

1. Install an mount an extra backup HD.
2. Miror over all central datas from the orginal HD to the backup hd using rsync.
3. Make a fresh new 5.6 installation.
4. restore bach the datas from the backup hd to the fresh installation using rsync.