Operating System - OpenVMS
1756533 Members
1912 Online
108848 Solutions
New Discussion юеВ

Re: not working Advanced Server Pathwork after openVMS autogen and reboot

 
CJBe
Advisor

not working Advanced Server Pathwork after openVMS autogen and reboot

Hi!

After a autogen with reboot on a three node cluster the Advanced Server (PathWork) is unable to startup on one of the cluster nodes.

In PWRK$LMMCP_NODENAME.LOG i found:

LISTER\listeninit: Unable to post the name on any networl: NODENAME

PCS_SetConnectionLevel: group name has not been declared

and after that

SYSTEM job terminated at ...

Is there a problem with the network or where can I look up next? Please help me, I am a "fresh" openVMS Admin.

Thanks!




19 REPLIES 19
Shilpa K
Valued Contributor

Re: not working Advanced Server Pathwork after openVMS autogen and reboot

Hi,

It is likely that the pwrk$knbdaemon process is not starting up correctly. You may want to check if there are any errors in the log file PWRK$ROOT:[LOGS]PWRK$KNBDAEMON_.log;*

Regards,
Shilpa
CJBe
Advisor

Re: not working Advanced Server Pathwork after openVMS autogen and reboot

Thanks!

In PWRK$KNBDAEMON_NODENAME.LOG I found:

get_ip_addr: gethostname error: 0

I looked in TCPIP show host, there is a entry

IP-Adress Nodename

I can do ping, telnet usw. looks like network is on...

Shilpa K
Valued Contributor

Re: not working Advanced Server Pathwork after openVMS autogen and reboot

Hi,

I am assuming that you are using TCPIP services provided HP. If so, can you execute the following command and see if the inet logicals are defined correctly?

$ sh log *inet*

Regards,
Shilpa
CJBe
Advisor

Re: not working Advanced Server Pathwork after openVMS autogen and reboot

Thanks!

I used your command to look up the logicals on both nodes from the cluster.

On the one where Advanced Server still working I found these logicals in LNM$SYSTEM_TABLE

"TCPIP$INET_DOMAIN" = "..."
"TCPIP$INET_HOST" = "..."
"TCPIP$INET_HOSTADDR" = "..."
"UCXIP$INET_DOMAIN" = "..."
"UCXIP$INET_HOST" = "..."
"UCXIP$INET_HOSTADDR" = "..."

On the node where Advanced Server isn't working the logicals are missing.

So please can You tell me, where and when these logicals are set up. Thanks a lot!!!
marsh_1
Honored Contributor

Re: not working Advanced Server Pathwork after openVMS autogen and reboot

hi,

usually these would be defined after you have configured your tcpip setup with tcpip$config.com and started tcpip services.

fwiw

Shilpa K
Valued Contributor

Re: not working Advanced Server Pathwork after openVMS autogen and reboot

Hi,

Looks like TCPIP is not configured correctly. As mentioned by Mark Hunt, you can use tcpip$config to reconfigure TCPIP.

Regards,
Shilpa
CJBe
Advisor

Re: not working Advanced Server Pathwork after openVMS autogen and reboot

I defined the logicals on the node where Advanced Server isn't running by hand. But it is still the same Problem and the same entrys in the logfiles...

Okay, so realy a problem with TCP/IP?

But when I say TCPIP show service I get Information. Also I can ping the node and connect to this via Telnet. Also TCPIP show interface gets the correct interface configuration...
marsh_1
Honored Contributor

Re: not working Advanced Server Pathwork after openVMS autogen and reboot

hi,

can't remember if there can be case sensitivity issues with the host name with this, have you an upper and lower case nodename (alias) in the host table to tie in with the logicals ?

CJBe
Advisor

Re: not working Advanced Server Pathwork after openVMS autogen and reboot

The entrys in the host table all are like this:

IP NODENAME, nodename

and the logicals are once defined:

TCPIP$.... = "nodename"
UCX$... = "NODENAME"


I looked up the Processes running on both nodes an found an missing entry on the node where advanced server isn't running.

The missing process is TCPIP$PWIP_ACP, I looked up with TCPIP$CONFIG.COM and tried to stop and start but still missing... Is it possible this is the problem?