setup a new service

[Chris Werner]

Hi Experts,

being new to ASA version 11 and ASA under Linux I wonder
how to setup a new service. I'm used to use Sybase Centrals
Adaptive Server Anywhere plugin, opening the "Services" tab
and choose "New" from the context menu. How to do that in
ASA 11 under Linux?

TIA

Chris Werner
f+s software gmbh

[Kory Hodgson (Sybase iAnywhere)]

You could use our dbsvc utility.

Check out this page in our docs:
http://dcx.sybase.com/index.php#http%3A%2F%2Fdcx.sybase.com%2F1101en%2Fdbadmin_en11%2Fdbsvc-service-dbutilities-linux.html%23d5e48495

[Chris Werner]

Hi Kory,

thanks a lot for your answer! I was able to setup a service
using the following command line :

dbsvc -as -s automatic -t network -w <serviceName> -n <serverName> -o
<outputfileName> -x tcpip -c 32m <DBFileName>

I can start the server either with

dbsvc -u <serviceName>

or with

/etc/init.d/SA_<serviceName> start

After doing so I can connect to the server as expected. Great!
(I was thinking I'd never gain my old fashioned UNIX shell
experience again).

A remaining problem is the intendent autostart of the service which
is intended by the option -s automatic. After restarting Linux I'd
expect the server to be running but that isn't the case. I've to start
it like mentioned above. Any ideas?

TIA

Chris Werner
f+s software gmbh

dbsvc -as -a automatic -t network -w <serviceName> -n <servername> -o
<outputfileName> -x tcpip -c 32m <DBFileName>

"Kory Hodgson (Sybase iAnywhere)" <khodgson@A_SPAM_FREE_sybase.com> schrieb
im Newsbeitrag news:4ab78f0b$1@forums-1-dub...

[Kory Hodgson (Sybase iAnywhere)]

It sounds like the daemon account might not have appropriate permissions
on the SQL Anywhere directory and executables, or your database and log
file.

[Phil Mitchell [Sybase iAnywhere]]

Check /var/log/messages to see if there are any error messages (or
anything at all) from your service.

The service is in /etc/init.d/ as required. However, check the
appropriate runlevel directory. Depending on your distro, there should
be something like /etc/rcX.d/ where X is the runlevel (use who -r to
check). For example, on RedHat-based systems, runlevel 5 is the
default. There should be a symbolic link to
/etc/init.d/SA_<serviceName> in that directory. If there is not, then
the service will not start.

If you'd like to use the GUI to configure service start up, try the
System->Administration->Services app (or the equivalent for your distro).

Be sure to let us know what the problem is. There may be something we
need to fix.

Cheers,
Phil

[Chris Werner]

Hi Phil,

that's interesting I didn't know about that runlevel directories. To
check that I've done the following:

cd /etc
ls -l rc*.d/* | grep SA_WIM2LINUXSRVC

to find wether there is a symbolic link to SA_WIM2LINUXSRVC
in any of this directories. Guess what I found? There is a symbolic
link to SA_WIM2LINUXSRVC in any of this directories (rc0.d ... rc6.d
and rcS.d). It looks like follows:

lrwxrwxrwx 1 root root 26 2009-09-22 rc0.d/K80SA_WIM2LINUXSRVC
-> ../init.d/SA_WIM2LINUXSRVC

I've no clue what that means.

I have checked /var/log/messages for SQL Anywhere error messages regarding
the service start or anything like that but found nothing.

Best regards

Chris Werner
f+s software gmbh

"Phil Mitchell [Sybase iAnywhere]" <firstname...@sybase.com> schrieb
im Newsbeitrag news:4ab8dd57$1@forums-1-dub...

[Chris Werner]

Hi Kory,

thanks for your answer. I've checked the permissions and made
them rw respective rwx for owner, group and all. After restarting
the machine the service didn't run either. To be honest I'm not
sure how I can check exactly if the daemon account have enough
permissions to start the service. I would expect to see some
appropriate error message in /var/log/messages if there are
such problems but there isn't any message regarding SQL Anywhere
or the service name in question.

Thaks again

Chris Werner
f+s software gmbh

"Kory Hodgson (Sybase iAnywhere)" <khodgson@A_SPAM_FREE_sybase.com> schrieb
im Newsbeitrag news:4ab8d5e1@forums-1-dub...

[Phil Mitchell [Sybase iAnywhere]]

Interesting. I see one thing that should be addressed here, but that's
not related to your problem.

The "K80" on the start of the symlink is there because services are
started in alphabetical order. So, it's normal to put some prefix on
the service name to impose the desired ordering.

What runlevel are you using (who -r)?

Can you adjust the name on the symlink in the appropriate runlevel
directory so that your SA service starts later (maybe start with V01 or
something similar)? If there's a dependent service not started yet, I
can see why there might be problems.

Thanks,

[Phil Mitchell [Sybase iAnywhere]]

Apparently, if you use the latest EBF, there should be fixes in place to
make it work. A workaround to try is to name the symlink
S99SA_WIM2LINUXSRVC and see if that works.

Thanks,
Phil

[Chris Werner]

Hi Phil,

thanks you for all the help. Finally I got that working. I've
downloaded and installed build 2279, deleted the service
using dbsvc -d <sName> and created a new one. After
rebooting Linux the service is started and I can connect
to the server.

One thing to note is some language mixture in the dbsvc
tool. When it askes a Yes/No question it shows the
language specific options (J/N for German) but it expects
an Y to take it as Yes.

Best regards

Chris Werner
f+s software gmbh

"Phil Mitchell [Sybase iAnywhere]" <firstname...@sybase.com> schrieb

im Newsbeitrag news:4aba5a0c$1@forums-1-dub...

[Phil Mitchell [Sybase iAnywhere]]

Thanks for the report. I've let the appropriate person know.

I'm glad you've got your setup working.

[Chris Werner]

Hi Phil,

there is another observation which MAY worth mentioning
because it costs me some time to solve that when I was
intalling the server on the customers machine:

The file system on the ASA11 server setup CD for Linux
behaves in a way that on Windows machines all file and
directory names are uppercase. When the CD is copied from
this Windows machine to a Linux machine it remains uppercase
so that the setup script doesn't work because it calls other scripts
in lowercase and this is a difference under Linux. Of course one
can avoid that mounting the CD direct under Linux. That wasn't
able for some technical reasons so we had to twiddle for a while
there.

Best regards

Chris Werner
f+s software gmbh

"Phil Mitchell [Sybase iAnywhere]" <firstname...@sybase.com> schrieb

im Newsbeitrag news:4abbacca$1@forums-1-dub...

[Phil Mitchell [Sybase iAnywhere]]

Hi Chris,

Thanks for the observation. I'm not sure how much we can do about that,
but I can at least have a look to see what's being done improperly
during the CD manufacture. I suspect it's not dissimilar to an issue I
ran into with mounting a VFAT disk on Linux a while back...there was a
special mount option I had to use to ensure case was handled properly.