on 06-01-2009 1:09 AM
I login to N4S testdrive client 001 as "developer" user.
After accepting the login credentials I get a shortdump on screen. I am pasting the first screen contents of shortdump below
<br />
-
<br />
Runtime Errors DBIF_RSQL_INVALID_REQUEST <br />
Date and Time 31.05.2009 18:55:06 <br />
<br />
Short text <br />
Invalid request. <br />
<br />
What happened? <br />
<br />
The current ABAP/4 program had to be terminated because the <br />
ABAP/4 processor detected an internal system error. <br />
<br />
Error analysis <br />
<br />
An invalid request was made to the database interface <br />
when accessing table "DOKTL ". <br />
Last error logged in SAP kernel <br />
<br />
Component............ "NI (network interface)" <br />
Place................ "SAP-Server linux-mtl1_N4S_01 on host linux-mtl1 (wp 0)" <br />
Version.............. 38 <br />
Error code........... "-16" <br />
Error text........... "verify own hostname '198.168.1.100:0' failed" <br />
Description.......... "NiIBindSocket" <br />
System call.......... "bind" <br />
Module............... "nixxi.cpp" <br />
Line................. 3168 <br />
<br />
The error reported by the operating system is: <br />
Error number..... 99 <br />
Error text....... "Cannot assign requested address" <br />
<br />
Trigger Location of Runtime Error <br />
<br />
Program SAPLSDOC <br />
Include LSDOCU09 <br />
Row 249 <br />
Module (FUNCTION) <br />
Module Name DOCU_GET <br />
-
<br />
<br />
If I try to scroll further down the system is freezing after a couple of clicks and not able to scroll any further.
<br />
Also on the terminal window from which I start the script file containing environment parms and guilogon has the following output
<br />
linux-mtl1:~/Documents # bash StartGUI<br />
ERROR #############################<br />
31.05. 19:03:09.147 ERROR: JniAgComAdaptor.write failed<br />
ERROR #############################<br />
ERROR #############################<br />
31.05. 19:03:09.163 ERROR: GuiNiWriter: write failed<br />
ERROR #############################<br />
<br />
Dear Ashok,
I suspect, that there is an error in the file /etc/hosts. Could you please paste the content? It seems that n4shost has the same ip address then linux-mtl1, which should not be the case.
Thanks,
Hannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Hannes,
As requested pls find the /etc/hosts contents below
#
hosts This file describes a number of hostname-to-address
mappings for the TCP/IP subsystem. It is mostly
used at boot time, when no name servers are running.
On small systems, this file can be used instead of a
"named" name server.
Syntax:
IP-Address Full-Qualified-Hostname Short-Hostname
#
127.0.0.1 localhost
198.168.1.100 linux-mtl1.mymach.org linux-mtl1
special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts
192.168.155.1 n4shost
192.168.155.1 n4shost
-
Thanks,
Ashok
Dear Ashok,
your /etc/hosts file looks good. The issue must be somewhere else. When you are logged in as user n4sadm, how do you start the N4S system? The command has to be
startsap n4shost
It is very curious, because the error message says
Place................ "SAP-Server linux-mtl1_N4S_01 on host linux-mtl1 (wp 0)"
Error text........... "verify own hostname '198.168.1.100:0' failed"
The error does not give the correct hostname and not the correct ip address. This is very strange ...
Can you post the result of the command:
ls -la /usr/sap/N4S/SYS/profile/
Maybe the SAP profiles are broken ...
Thanks,
Hannes
Dear Hannes,
I start the N4S system with the command "startsap n4shost" from user n4sadm.
I am pasting the "ls" command output below as requested
linux-mtl1:~/Desktop # ls -la /usr/sap/N4S/SYS/profile/
total 28
drwxr-xr-x 2 n4sadm sapsys 4096 2009-05-25 20:57 .
drwxr-xr-x 5 n4sadm sapsys 4096 2009-05-22 17:05 ..
-rw-rr 1 n4sadm sapsys 816 2006-06-12 08:38 DEFAULT.PFL
-rw-rr 1 n4sadm sapsys 1537 2006-06-23 10:05 N4S_DVEBMGS01_n4shost
-rw-rr 1 n4sadm sapsys 701 2006-06-12 17:13 N4S_SCS00_n4shost
-rw-rr 1 n4sadm sapsys 2707 2006-06-12 17:14 START_DVEBMGS01_n4shost
-rw-rr 1 n4sadm sapsys 1446 2006-06-12 17:13 START_SCS00_n4shost
linux-mtl1:~/Desktop #
Thanks,
Ashok
Dear Hannes,
I run into the same shortdump within Adobe Interactive forms when selecting "Layout" tab in transaction SFP.
In earlier reply you mentioned that host name & ip is not shown correctly in the shortdump. Can you tell how this one should normally look.
Pasting the ifconfig output below.
-
ifconfig output -
linux-mtl1:~/Desktop # ifconfig
eth0 Link encap:Ethernet HWaddr 00:23:5A:29:57:22
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::223:5aff:fe29:5722/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1106 errors:0 dropped:0 overruns:0 frame:0
TX packets:1210 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:797862 (779.1 Kb) TX bytes:277263 (270.7 Kb)
Interrupt:251 Base address:0x4000
eth0:0 Link encap:Ethernet HWaddr 00:23:5A:29:57:22
inet addr:192.168.155.1 Bcast:192.168.155.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:251 Base address:0x4000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:340 (340.0 b) TX bytes:340 (340.0 b)
wlan0 Link encap:Ethernet HWaddr 00:24:2B:7B:A9:FE
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wmaster0 Link encap:UNSPEC HWaddr 00-24-2B-7B-A9-FE-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Thanks,
Ashok
Dear Ashok,
well, I'm out of clues. You provided all the information I asked for and everything looks okay.
Maybe someone else has a clue?
Additionally, you might want to check the SAP on MaxDB/DB2 forum (depending on your database under the N4S) and ask your question there?
Thanks,
Hannes
Edited by: Hannes Kuehnemund on Jun 2, 2009 11:37 PM
The shortdump problem seem to be resolved if I adopt the following approach.
1) Do NOT start the virtual host eth0:0
2) In the /etc/hosts I change the ip address to match the ip address of eth0
Would like your expert opinion if this is okay or the above approach will trigger new problems elsewhere
Thanks,
Ashok
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.