7.6.00.27 to 7.6.03.15 upgrade woes (SDBSETUP fails on linux)

[Former Member]

Hi,

I was very pleased reading that the security hole (exploit) that had forced me to close port 7210 was plugged in 7.6.03.15, and I therefore tried to upgrade my installation and db-instances from 7.6.00.27 using SDBSETUP.

After going through the motions of selecting an upgrade of server and client sw and upgrading sw and instances and supplying the DBADMIN name and password, SDBSETUP

pops up a window, saying it cannot start xserver: x_ping failed.

However: the database instance is running and x_ping, run manually confirms this. The x_ping binary is on the path when SDBSETUP is started (as root).

Does anybody have any pointers as to what is going wrong here ? (btw. this is not the first upgrade, upgrading with sdbsetup has worked before!).

regards,

-walt

[former_member229109 · Accepted solution]

Hello Walt,

1) The x_ping tool is also part of the database software & located in the directory /sapdb/programs/bin, or <IndepProgPath>/bin, where you have also the x_server tool.

Please check on the database server, if you are able to run on the database server::

/sapdb/programs/bin/x_ping -h

/sapdb/programs/bin/x_ping -n <HostName>

2) As I understood you was trying to run the upgrade of the database instance version from 7.6.00.27 to 7.6.03.15

using SDBSETUP. Please check first, that the software of the database instance is in the consistent status.

Logon as root & run:

cd /sapdb/programs/bin

./sdbverify

==> update with the results.

3) Please update with additional information:

-> Output of the following commands:

dbmcli inst_enum

dbmcli db_enum

sdbregview -l

xinstinfo <DB-name>

-> Please post the MAXDB installation log & xserver_<hostname>.prt located in

the <IndepDataPath>/wrk on the database server.

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Natalia,

thanks for the hints. The requested information is

attached below. Please note that I could ping the database

manually right after the upgrade had failed and that previous upgrades ran without a hitch.

regards,

-walt

0) pinging works:

./x_ping -n localhost

Checking connection to 'localhost' ... ok.

Version of Server is

-

---

X32/LINUX 7.6.0 Build 027-121-124-939

-

---

a) sdbverify runs OK

but sync-manager 7.6.00.12 is inconsistent:

Synchronization Manager 7.6.00.12 in /opt/sdb/programs

-

---

check files... failed

/opt/sdb/programs/bin/msgserver was modified

/opt/sdb/programs/app/syncman/example/createexampletables was modified

/opt/sdb/programs/bin/syncmanacc was modified

/opt/sdb/programs/bin/syncmanjconf was modified

/opt/sdb/programs/bin/syncmangui was modified

/opt/sdb/programs/bin/syncservice was modified

/opt/sdb/programs/app/syncman/example/createexampledatabases was modified

check dependencies... ok

package data is inconsistent

VERIFICATION SUMMARY:

*********************

INVALID PACKAGES: 0

VALID PACKAGES: 19

INCONSISTENT PACKAGES: 1 (sync manager)

TOTAL FILES: 635

MISSED FILES: 0

MODIFIED FILES: 7

FILES WITH MODIFIED PERMISSIONS: 0

./dbmcli inst_enum

OK

7.6.00.27 /opt/sdb/MAXDB1

./dbmcli db_enum

OK

MAXDB1 /opt/sdb/MAXDB1 7.6.00.27 fast running

MAXDB1 /opt/sdb/MAXDB1 7.6.00.27 quick offline

MAXDB1 /opt/sdb/MAXDB1 7.6.00.27 slow offline

MAXDB1 /opt/sdb/MAXDB1 7.6.00.27 test offline

./sdbregview -l

DB Analyzer /opt/sdb/programs 7.6.00.27 32 bit valid

Server Utilities /opt/sdb/programs 7.6.00.27 32 bit valid

PCR 7300 /opt/sdb/programs 7.3.00.54 valid

CPC Base /opt/sdb/programs 7.6.00.12 32 bit valid

PCR 7301 /opt/sdb/programs 7.3.01.18 valid

PCR 7500 /opt/sdb/programs 7.5.00.29 32 bit valid

Webtools /opt/sdb/programs/web 7.6.00.12 32 bit valid

Synchronization Manager /opt/sdb/programs 7.6.00.12 valid

Base /opt/sdb/programs 7.6.00.27 32 bit valid

Redist Python /opt/sdb/programs 7.6.00.27 32 bit valid

CPC SDK 7600 /opt/sdb/programs 7.6.00.12 32 bit valid

JDBC /opt/sdb/programs 7.6.00.24 valid

Messages /opt/sdb/programs MSG 0.3347 valid

ODBC /opt/sdb/programs 7.6.00.27 32 bit valid

Database Kernel /opt/sdb/MAXDB1 7.6.00.27 32 bit valid

Loader /opt/sdb/programs 7.6.00.27 32 bit valid

PCR 7600 /opt/sdb/programs 7.6.00.12 32 bit valid

SQLDBC /opt/sdb/programs 7.6.00.27 32 bit valid

PCR 7403 /opt/sdb/programs 7.4.03.39 32 bit valid

./xinstinfo MAXDB1

IndepData : /var/opt/sdb/data

IndepPrograms : /opt/sdb/programs

InstallationPath : /opt/sdb/MAXDB1

Kernelversion : KERNEL 7.6.00 BUILD 027-121-124-939

Rundirectory : /var/opt/sdb/data/wrk/MAXDB1

xserver_gulliver.prt:

-

---

Date Time PID Typ MsgID Label Message-Text

-

---

2008-04-04 17:04:01 4742 12902 XSERVER started, 'X32/LINUX 7.6.00 Build 027-121-124-939'

2008-04-04 17:04:01 4742 12904 XSERVER Service port is 7210

2008-04-04 17:04:01 4742 12922 ENVIRON Command line arguments

2008-04-04 17:04:01 4742 12924 ENVIRON [1] -Y

2008-04-04 17:04:01 4742 12924 ENVIRON [2] start

2008-04-04 17:04:01 4742 12923 ENVIRON Command line argument dump completed

2008-04-04 17:04:01 4742 12898 ENVIRON Resource limit dump start

2008-04-04 17:04:01 4742 12898 ENVIRON Started by user id 1001 group id 1000

2008-04-04 17:04:01 4742 12898 ENVIRON Current user id 1001 effective id 1001

2008-04-04 17:04:01 4742 12898 ENVIRON Current group id 1000 effective id 1000

2008-04-04 17:04:01 4742 12898 ENVIRON cpu time unlimited

2008-04-04 17:04:01 4742 12898 ENVIRON number of processes 8187

2008-04-04 17:04:01 4742 12898 ENVIRON number of open files 1024

2008-04-04 17:04:01 4742 12898 ENVIRON core size 0 KBytes

2008-04-04 17:04:01 4742 12898 ENVIRON file size unlimited

2008-04-04 17:04:01 4742 12898 ENVIRON heap memory size unlimited

2008-04-04 17:04:01 4742 12898 ENVIRON stack memory size 8192 KBytes

2008-04-04 17:04:01 4742 12898 ENVIRON lockable memory size 32 KBytes

2008-04-04 17:04:01 4742 12898 ENVIRON virtual memory size 1663760 KBytes

2008-04-04 17:04:01 4742 12898 ENVIRON resident set size 880175 KBytes

2008-04-04 17:04:01 4742 12898 ENVIRON Resource limit dump completed

2008-04-04 17:04:01 4742 12898 ENVIRON Environment dump start

2008-04-04 17:04:01 4742 12898 ENVIRON CONSOLE=/dev/console

2008-04-04 17:04:01 4742 12898 ENVIRON ROOTFS_FSTYPE=reiserfs

2008-04-04 17:04:01 4742 12898 ENVIRON SHELL=/bin/sh

2008-04-04 17:04:01 4742 12898 ENVIRON TERM=linux

2008-04-04 17:04:01 4742 12898 ENVIRON PROFILE=default

2008-04-04 17:04:01 4742 12898 ENVIRON ROOTFS_FSCK=0

2008-04-04 17:04:01 4742 12898 ENVIRON LC_ALL=POSIX

2008-04-04 17:04:01 4742 12898 ENVIRON INIT_VERSION=sysvinit-2.86

2008-04-04 17:04:01 4742 12898 ENVIRON REDIRECT=/dev/tty1

2008-04-04 17:04:01 4742 12898 ENVIRON COLUMNS=96

2008-04-04 17:04:01 4742 12898 ENVIRON PATH=/bin:/sbin:/usr/bin:/usr/sbin

2008-04-04 17:04:01 4742 12898 ENVIRON vga=0x314

2008-04-04 17:04:01 4742 12898 ENVIRON RUNLEVEL=5

2008-04-04 17:04:01 4742 12898 ENVIRON PWD=/

2008-04-04 17:04:01 4742 12898 ENVIRON SPLASHCFG=/etc/bootsplash/themes/SuSE/co

2008-04-04 17:04:01 4742 12898 ENVIRON nfig/bootsplash-800x600.cfg

2008-04-04 17:04:01 4742 12898 ENVIRON PREVLEVEL=N

2008-04-04 17:04:01 4742 12898 ENVIRON LINES=33

2008-04-04 17:04:01 4742 12898 ENVIRON HOME=/

2008-04-04 17:04:01 4742 12898 ENVIRON SHLVL=2

2008-04-04 17:04:01 4742 12898 ENVIRON splash=silent

2008-04-04 17:04:01 4742 12898 ENVIRON SPLASH=yes

2008-04-04 17:04:01 4742 12898 ENVIRON ROOTFS_BLKDEV=/dev/hda6

2008-04-04 17:04:01 4742 12898 ENVIRON _=/sbin/startproc

2008-04-04 17:04:01 4742 12898 ENVIRON DAEMON=/opt/sdb/programs/bin/x_server

2008-04-04 17:04:01 4742 12898 ENVIRON DBROOT=/opt/sdb/programs

2008-04-04 17:04:01 4742 12898 ENVIRON LD_LIBRARY_PATH=/opt/sdb/programs/lib

2008-04-04 17:04:01 4742 12898 ENVIRON Environment dump completed

-

---

current write position -

---

MaxDBUpdate_install-29.03.2008-21.14.log:

INSTALLER_INFO: Version = 7.6.03 Build 015-121-173-107

INSTALLER_INFO: Changelist = 173107

INSTALLER_INFO: MakeId = 282830

INSTALLER_INFO: Type = kit

SYS_INFO: Host name = gulliver

SYS_INFO: System = Linux

SYS_INFO: Architecture = I386

SYS_INFO: Version = 2.6.18.8

SYS_INFO: Subversion = 0.9-default

SYS_INFO: C Runtime = GLIBC 2.5

CALL: SDBUPD -INSTANCE -profile APO LiveCache

STDOUT:

MaxDB INSTANCE UPDATE

STDOUT: *********************

STDOUT: starting installation Sa, Mar 29, 2008 at 21:14:21

STDOUT: operating system: Linux I386 2.6.18.8 0.9-default GLIBC 2.5

STDOUT: callers working directory: /tmp/maxdb-all-linux-32bit-i386-7_6_03_15

STDOUT: installer directory: /tmp/maxdb-all-linux-32bit-i386-7_6_03_15

MSG: InstallRegistry: space check ok: 2429984 kb on / (23928032 kb total) available

MSG: install registry successfully locked

MSG: read 19 PACKAGES

MSG: net registry size = 178198 bytes

MSG: InstallRegistry: reserved 1024 kb disk space

STDOUT: archive directory: /tmp/maxdb-all-linux-32bit-i386-7_6_03_15

STDOUT:

debug package SDBKRN.SDB not found

MSG: no installation data to migrate

STDOUT: beginning to check sap db instances

STDOUT: existing instance:

STDOUT: 0: MAXDB1 "/opt/sdb/MAXDB1" 7.6.0.27

STDOUT: 1: none

STDOUT: please enter instance id:

STDIN: 0

STDOUT: please enter database manager operators name:

STDIN: DBADMIN

STDOUT: please enter database manager operators password: STDOUT:

STDIN:

STDOUT: start new instance update

x_server is not running

SYS: /opt/sdb/programs/bin/x_server start: 12916 XSERVER Found other running x_server with version 'X32/LINUX 7.6.00 Build 027-121-124-939'

SYS: /opt/sdb/programs/bin/x_server start: 12902 XSERVER started, 'already...'

x_server is not running

STDERR: cannot start x_server

STDERR:

STDERR: MaxDB instance update exited abnormally at Sa, Mar 29, 2008 at 21:14:51

MSG: don't need to write package registry

MSG: install registry successfully unlocked

[former_member229109 · Accepted solution]

Hello Walter,

1) Please check the /etc/services file and let me know if the port is entered in the services file:

UNIX/Linux: /etc/services ::

sql6 7210/tcp

See additional info at

http://maxdb.sap.com/doc/7_6/7e/c3fb0e72fcf84580f7ee9fcec672b7/frameset.htm ::

SAP MaxDB Library 7.6 -> Glossary

< Port -> Ports and Protocols of the X Server >

2) Please let me know how did you "close port 7210"?

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Hi Natalia,

1) port 7210 was not entered in

/etc/services (on the machine that I tried to upgrade).

I am wondering though, why earlier upgrades went without a problem.

2) on the production machine,

7210 is closed to the outside (firewall).

Thanks for your efforts.

[Former Member · Accepted solution]

Natalia,

I just added the

sql6 entry to /etc/services.

After that the upgrade went

through OK.

Only mystery remaining is why

previous updates worked without a

problem.

Thanks for your help,

-walt

[former_member229109 · Accepted solution]

Hello Walter,

-> Good to know that I was right with assumption that you have the missing entries

in the /etc/services for the needed port of the X_Server.

-> "I am wondering though, why earlier upgrades went without a problem."

I think that the /etc/services on the database server was changed after the

successful upgrades … and you failed to run the database next upgrade after that.

-> As you already checked the referred documents in the MAXDB library, the entry

"sql6 7210/tcp" in the /etc/services on UNIX/Linux machine added by the database

installation tool & should be not deleted manually.

Thank you and best regards, Natalia Khlopina