This might be helpful. here's what I get with I run the 'showserver'
script.

************************************************** *****************
bash-2.05a$ ./ASE/install/showserver
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
bash-2.05a$
************************************************** **************

After updating the DISPLAY env var to it correct setting
DISPLAY=localhost:0

I now get a new error when trying to run isql

************************************************** ********
bash-2.05a$ isql -Usa -Slocalhost
Password:
CT-LIBRARY error:
ct_connect(): network packet layer: internal net library error:
Net-Lib protocol driver call to connect two endpoints failed
************************************************** *************

Here's the contents of the 'interfaces' file if it helps.
localhost
master tcp ether localhost 4100
query tcp ether localhost 4100

Justins_Server
master tcp ether localhost 4100
query tcp ether localhost 4100


Thanks,
Justin

Justin Birtwell wrote:
Hi,

Ken is referring to ASE's errorlog, which is located in here:
$SYBASE/ASE-12_5/install/server_name.log (this is the default path).

Looking at the other posts you've sent, it seems that you have
two servers, one named localhost, second as Justins_Server. Both of
them seem to be using port 4100(which is not a good idea, btw).

To log into your server, The server must first be started by executing
the RUN_servername script in directory $SYBASE/ASE-12_5/install/. In
this case your RUN* file should be named as RUN_Justins_Server.

After that you can verify that the server got up by executing the
'showserver' -command. Or do an 'ps -ef | grep dataserver' to see if the
dataserver is listed in the process list...

To log into this server you would execute command :
isql -Usa -P -SJustins_Server
(which would return the 1> prompt.)

BTW:

As isql is cmdline tool, the $DISPLAY variable has no use in
this scenario.

The first errormessage says that it can't find the entry in
the interfaces file for server "Justins_Server" and the second
errormessage you got tells that the server "localhost" is not up...

If you find *.krg file in the $SYBASE directory and the ASE is
not running, you can delete this file....

Hope this helps...

regards,
-mika-

Mika,

Thanks for your explicit instruction. when I went to execute the
RUN_localhost command I get the following error.

**********************************8
[root@localhost install]# RUN_localhost
00:00000:00000:2003/08/28 13:46:14.92 kernel Checked out license ASE_DEV
00:00000:00000:2003/08/28 13:46:15.10 kernel Adaptive Server Enterprise
Developer Edition.
00:00000:00000:2003/08/28 13:46:15.15 kernel Attempt to open device
/opt/sybase-12.5/master/master.dat failed.
00:00000:00000:2003/08/28 13:46:15.15 kernel dopen: open
'/opt/sybase-12.5/master/master.dat', No such file or directory
[root@localhost install]#
********************************************

The reason why there is no master.dat is because when I go to create a
server it fails. for example using the 'asecfg' utility to 'Configure a
New Server' I try creating an Adapter Server called 'localhost' with all
defaults and
'Master Device Path' = /opt/sybase-12.5/master/master.dat
'Sybsystemprocs device path:'=/opt sybase-12.5/data/sybsystemprocs.dat

however the svrbuild service when trying to start the newly created server
reports the following:

********************************************88
Building Adaptive Server 'localhost':

Writing entry into directory services... Directory services entry complete.
Building master device... Master device complete.
Writing RUN_localhost file...
RUN_localhost file complete.
Starting server... Task failed
Unable to boot server 'localhost'.
Server 'localhost' was not created.
************************************************** **

Here's what errors are reported in the
/opt/sybase-12.5/ASE-12.5/install/localhost.log file


************************************************** *
00:00000:00000:2003/08/28 14:26:52.36 kernel Checked out license ASE_DEV
00:00000:00000:2003/08/28 14:26:52.36 kernel Adaptive Server Enterprise
Developer Edition.
00:00000:00000:2003/08/28 14:26:52.38 kernel Using config area from primary
master device.
00:00000:00000:2003/08/28 14:26:52.38 server Configuration Error:
Configuration file, '/opt/sybase-12.5/localhost.cfg', does not exist.
00:00000:00000:2003/08/28 14:26:52.38 kernel Warning: A configuration file
was not specified and the default file '/opt/sybase-12.5/localhost.cfg'
does not exist. SQL Server creates the default file with the default
configuration.
00:00000:00000:2003/08/28 14:26:52.40 kernel Warning: Using default file
'/opt/sybase-12.5/localhost.cfg' since a configuration file was not
specified. Specify a configuration file name in the RUNSERVER file to avoid
this message.
00:00000:00000:2003/08/28 14:26:52.42 kernel os_create_region: can't
allocate 37076992 bytes
00:00000:00000:2003/08/28 14:26:52.42 kernel kbcreate: couldn't create
kernel region.
00:00000:00000:2003/08/28 14:26:52.42 kernel kistartup: could not create
shared memory
00:00000:00000:2003/08/28 14:26:52.51 kernel Checked out license ASE_DEV
00:00000:00000:2003/08/28 14:26:52.51 kernel Adaptive Server Enterprise
Developer Edition.
00:00000:00000:2003/08/28 14:26:52.51 kernel The configuration area in
device '/opt/sybase-12.5/master/master.dat' appears to be corrupt. The
server needs this data to boot, and so cannot continue. The server will
shut down.

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

I don't know why I would be getting some of these errors. I have plenty of
space on the partition. the localhost.cfg file exists.

Lastly, the data server is listed in the process list: See what follows:
bash-2.05a$ ps -ef | grep dataserver
sybase 2807 2667 0 14:37 pts/3 00:00:00 grep dataserver


Please help. Thanks,
Justin

I'm thinking it's time to try the install again from the
beginning. The log error is complaining about a possible
corrupted master device. Double check all your pre-install
checklists and available resources.

The "ps" command shows that the server is not running. What
you are seeing is the process running "grep". To not see
this you can use:
"ps -ef | grep dataserver | grep -v grep".

Ken

Justin,

This sounds like you haven't adjusted your shared memory settings on
your Linux box? You should increase the amount of available shared
memory by tuning the shmmax kernel parameter... usually ~70% from
total physical memory is still safe to allocate for shared memory.
(this ofcourse assumes that you have more than 64Megs of RAM...)

Ken is probably right by saying that perhaps you should try to clean
up the current servers, and then try again to create ASE server...
so here we go:

Here's how you can delete the current servers:

-delete interfaces file
-delete the RUN_servername files
-delete the servername.cfg, servername.krg file(if exists)
and the servername.xxx files(xxx is number value like 001, 002,etc)
which are located in the $SYBASE dir.
-delete the database files master.dat, sysprocsdev.dat, etc...

Then check that nothing is using the port 4100 by running
'netstat -a'. If the port is on the list, then you must
allocate another port for ASE.

After these tasks start the asecfg again and see if it finishes
correctly this time =)

HTH

regards,
-mika-





Ken wrote: