PWIP

[Attila Fekete_1]

Hi,

We have problem using PWIP. When the system start up, it works. And once the XOT (X25 over TCPIP) doesn't and the same time the DECnet over IP stop working.
I tried to restart the PWIP and TCPIP, but it didn't help.
I'm using VMS 7.3 with TCPIP 5.1 ECO5.
Does anyone found the cause of this?

Thanks,
Attila

[Antoniov.]

Hi Attila,
I don't known PWIP but I think you can find any error message in log.

@Antoniov

[Kris Clippeleyr]

Hi Attila,

Before trying to find an answer/solution to the problem at hand, can you tell us if and what error messages are in the PWIP logfiles? (These should reside in SYS$MANAGER, called TCPIP$PWIPACP_.LOG)

Kris

[Attila Fekete_1]

Ok, I checked the operator.log, but there was no error message about it. But here is the PWIP log:
Sat Mar 27 19:16:19 2004: PWIP Acp started
Mon Apr 19 23:52:17 2004: connReq_ast : *** Connect Request failed *** : 556
Mon Apr 19 23:52:32 2004: connReq_ast : *** Connect Request failed *** : 556
Mon Apr 19 23:53:02 2004: connReq_ast : *** Connect Request failed *** : 556
Tue Apr 20 00:30:44 2004: connReq_ast : *** Connect Request failed *** : 556
Tue Apr 20 00:31:13 2004: connReq_ast : *** Connect Request failed *** : 556
Mon Apr 26 00:31:02 2004: pwipacp_exithandler : Performing Image Rundown. Exit Status (hex) = 0

After the resatrt of TCPIP I still had the
Mon Apr 26 00:53:11 2004: pwipacp_exithandler : Performing Image Rundown. Exit Status (hex) = 0

And I didn't get error message on the console.
Attila

[Antoniov.]

Attila,
your system can't connect to other side; error 556 after ACP call means time-out.
It seems you have some trouble in TCP/IP connection and system service over TCP/IP crash.
You could indagate over route between two host; I think crash is the result not tha cause of your problem.
It's only my opinion.

@Antoniov

[Attila Fekete_1]

I forgot to mention that telnet, ping, ftp worked just fine that time.
Can it be than routing or TCPIP problem?

Attila

[Brad McCusker]

Have you tried reconfiguring PWIP?

@sys$manager:tcpip$config

Select Option 4, Optional Components.

Brad

[Attila Fekete_1]

Of course I tried, but didn't help. (But I couldn't do other than just restart the PWIP, which can be done with the script file also.)

Attila

[Brad McCusker]

Attila,

What do you mean when you say:

"But I couldn't do other than just restart the PWIP..."

In TCPIP$CONFIGURE, Option 4 (Optional Components), there is a choice to "Disable Service" or "Stop Service". Were you able to "Disable Service"?

I would do that, maybe even try to stop and restart TCP/IP, and then go back in and "Enable Service".

Or, is this in fact what you already tried?

Regards,

Brad

[Attila Fekete_1]

Yes, I disabled and reenabled. But when it was enabled again it said something about created items and started the service. XOT and DECnet over IP still didn't work.

Attila

[Brad McCusker]

Attila,

Another question - In an earlier note, you showed us a log that went from Mar 21 to Monday April 26. That log file has a few routine 556 errors, then, the image rundown line.

Then you seem to indicate that future logs have only the image rundown line. That makes me believe that you are unable to get PWIP to run at all. Is that correct? Each time you try to start PWIP, you get a new log file and it is very brief and ends with the image rundown line? And, there is no other errors, correct? (If there is, please post them)

Oh, one other thing, although I doubt it is related. Why does the time stamp reflect many days in the future?

[Attila Fekete_1]

Yes, you are correct, I had only these kind of error messages - only the time stamp differed.
This server is used for test purpose, and because of that the time offen set forward.

Attila

[Antoniov.]

Attila,

can you connect with SET HOST from another node to this and form this node to another?
Also SHO NET display you DecNet protocol?

@Antoniov

[Attila Fekete_1]

SHO NET shows both DECnet and TCPIP.
SET HOST works with DECnet address, but not with name - that case it uses DECnet over TCPIP.

Attila

[Antoniov.]

Attila,
if SET HOST work only with DecNet address and doesn't work using name, may be you have some naming problem; may be you are same trouble in service?
You post ping, telnet and ftp work fine. They work fine using TCP/IP adddress or they work using name too?

@Antoniov

[Brad McCusker]

Can you post (or e-mail to me) an entire log file from an attempt to start PWIP?

Please use TCPIP$CONFIGURE to try to start PWIP, don't use the command file.

Also, I'd like to see the entire log file from the last time it was running successfully (I think maybe you posted part of it in an earlier reply).

My e-mail is my first-name.lastname at HP dot com.

Brad

[Attila Fekete_1]

Antoniov,

I think it's only the PWIP that down't work. If I ping/ftp/telnet with the name, it works.
I think the restart of DECnet what helped.

Brad here are the full logs:
SYS$SYSROOT:[SYSMGR]TCPIP$PWIPACP_DUNA4.LOG;62

Mon Apr 26 01:02:38 2004: PWIP Acp started

SYS$SYSROOT:[SYSMGR]TCPIP$PWIPACP_DUNA4.LOG;61

Mon Apr 26 00:53:18 2004: PWIP Acp started

SYS$SYSROOT:[SYSMGR]TCPIP$PWIPACP_DUNA4.LOG;60

Mon Apr 26 00:31:13 2004: PWIP Acp started
Mon Apr 26 00:53:11 2004: pwipacp_exithandler : Performing Image Rundown. Exit Status (hex) = 0

SYS$SYSROOT:[SYSMGR]TCPIP$PWIPACP_DUNA4.LOG;59

Sat Mar 27 19:16:19 2004: PWIP Acp started
Mon Apr 19 23:52:17 2004: connReq_ast : *** Connect Request failed *** : 556
Mon Apr 19 23:52:32 2004: connReq_ast : *** Connect Request failed *** : 556
Mon Apr 19 23:53:02 2004: connReq_ast : *** Connect Request failed *** : 556
Tue Apr 20 00:30:44 2004: connReq_ast : *** Connect Request failed *** : 556
Tue Apr 20 00:31:13 2004: connReq_ast : *** Connect Request failed *** : 556
Mon Apr 26 00:31:02 2004: pwipacp_exithandler : Performing Image Rundown. Exit Status (hex) = 0

SYS$SYSROOT:[SYSMGR]TCPIP$PWIPACP_DUNA4.LOG;58

Sat Mar 27 18:55:43 2004: PWIP Acp started

SYS$SYSROOT:[SYSMGR]TCPIP$PWIPACP_DUNA4.LOG;57

Tue Mar 23 19:31:54 2004: PWIP Acp started

Attila

[Brad McCusker]

Attila,


SYS$SYSROOT:[SYSMGR]TCPIP$PWIPACP_DUNA4.LOG;62

Mon Apr 26 01:02:38 2004: PWIP Acp started


This tells me PWIP is running.

You also said this:


I think the restart of DECnet what helped


So, are you now saying that DECnet and other users of PWIP are working OK?

It sounds like you had a problem with PWIP, restarted it, but did not restart the applications that are layered above PWIP. Therefor, those applications were not working correctly. After you restarted PWIP, and then restarted the applications (DECnet), everything works OK.

Is that correct?

I wish I could tell you why PWIP failed in the first place, but, unfortunately, there isn't enough information in the log file.

It sounds like everything is OK now?

Brad

[Attila Fekete_1]

At the moment it is working. When the problem happen I cannot login via DECnet over IP and XOT doesn't work. The existing connections are working, but no new one accepted. I just think taht the restart of DECnet helped, since the other protocol was restarted.
I agree that this is not enough information, I just though that somebody has run into the same problem.

Thanks anyway,
Attila
(I was on holiday last week, that's the cause of my late answear.)