Deadlock on OES2015 upgrade

[mathiasbraun]

Hi,
lab environment only, so there's not too much pressure on this issue.
While doing an upgrade of a fully patched OES11SP2 VM to OES2015, when it comes to the dib upgrade, yast asks for "existing server information". As this is a single server tree, i can only enter the local ip address for obvious reasons. on proceeding yast tells me that "the address must be a remote (non-local) one". On trying around i tried the primary dns name (didn't work either) and a second alias which is used for iprint stuff. this one finally worked, but i'm pretty sure i didn't have this problem on other single server lab boxes while doing the same upgrade a few weeks ago (obviously on a slightly older codebase).
i'd assume some sort of wrong information in one of the /etc/sysconfig/novell files. this labbox is an historic ID-transfer from a netware VM, so on its initiall installation years ago it had been installed into an existing tree.
any hints?
t.i.a.
MB

[Anonymous_User]

mathiasbraun,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

- Visit http://www.novell.com/support and search the knowledgebase and/or check
all the other self support options and support programs available.
- Open a service request: https://www.novell.com/support
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
- You might consider hiring a local partner to assist you.
https://www.partnernetprogram.com/partnerfinder/find.html

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

Sometimes this automatic posting will alert someone that can respond.

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot.

Good luck!

Your Novell Forums Team
http://forums.novell.com

[HvdHeuvel]

On Fri, 11 Mar 2016 15:06:01 +0000, mathiasbraun wrote:

> Hi,
> lab environment only, so there's not too much pressure on this issue.
> While doing an upgrade of a fully patched OES11SP2 VM to OES2015, when
> it comes to the dib upgrade, yast asks for "existing server
> information". As this is a single server tree, i can only enter the
> local ip address for obvious reasons. on proceeding yast tells me that
> "the address must be a remote (non-local) one". On trying around i tried
> the primary dns name (didn't work either) and a second alias which is
> used for iprint stuff. this one finally worked, but i'm pretty sure i
> didn't have this problem on other single server lab boxes while doing
> the same upgrade a few weeks ago (obviously on a slightly older
> codebase).
> i'd assume some sort of wrong information in one of the
> /etc/sysconfig/novell files. this labbox is an historic ID-transfer from
> a netware VM, so on its initiall installation years ago it had been
> installed into an existing tree.
> any hints?
> t.i.a.
> MB

Matthias,

Apologies the late response.
Care to share a supportconfig from the OES11SP2 server with me ?

Thanks
Hans

[mathiasbraun]

here we go
https://netlogix.sharefile.com/d-s65c222428814759a

sorry for the delay, had to revert to a snapshot taken before starting the upgrade. as this is just a lab box it normally serves itself as a dns server. for the upgrade it gets pointed to another named daemon which can handle resolution for the fake-domain.

[HvdHeuvel]

On Mon, 21 Mar 2016 12:46:01 +0000, mathiasbraun wrote:

> here we go https://netlogix.sharefile.com/d-s65c222428814759a
>
> sorry for the delay, had to revert to a snapshot taken before starting
> the upgrade. as this is just a lab box it normally serves itself as a
> dns server. for the upgrade it gets pointed to another named daemon
> which can handle resolution for the fake-domain.

Sorry it took a while to get back to this.
Downloaded the supportconfig and will have a look.

Thank you
Hans