Trouble creating a SQL Anywhere 17 service on linux

[former_SQLA_member1694873]

I'm trying to start a service on the demo database in SA17 with the command:

sudo /opt/sqlanywhere17/bin64/dbsvc -as -t network -s automatic -w demosvc -n demo /opt/sqlanywhere17/demo.db

This is substantially the same command I used successfully with SA16, but with SA17 I get the errors:

SQL Anywhere Service Utility 17.0.0.1062
Creating SQL Anywhere service: demosvc File: /etc/init.d/SA_demosvc
update-rc.d: warning:  start runlevel arguments (2 3 5 ) do not match SA_demosvc Default-Start values (2 3 5)
update-rc.d: error: expected runlevel [0-9S] (did you forget "." ?)
usage: update-rc.d [-n] [-f] <basename> remove
       update-rc.d [-n] <basename> defaults [NN | SS KK]
       update-rc.d [-n] <basename> start|stop NN runlvl [runlvl] [...] .
       update-rc.d [-n] <basename> disable|enable [S|2|3|4|5]
        -n: not really
        -f: force
The disable|enable API is not stable and might change in the future.

The 'dbsvc' command seems to be generating an invalid init script.

I'm running Ubuntu 14.04.1 LTS.

Has anyone else seen this?

[Former Member · Accepted solution]

We got the update-rc.d command line incorrect. The service script itself is not wrong, so you could run the udpate-rc.d script yourself as follows:

sudo /usr/sbin/update-rc.d SA_demosvc start 60 2 3 5 . stop 80 S 0 1 4 6 .

You should then be able to start and stop the service as normal.

I have created change request 788097 to track this issue and a fix will be included in a patch with build number at least 1235.

If you want the same behaviour as v16, you should also change your -as to -a root as the -as flag has been change to be more secure and it also matches the behaviour on Windows a little more closely. The server would be started as the daemon user, which probably has permission restrictions (which is usually a good thing).

[former_SQLA_member1694873 · Accepted solution]

Thanks for the quick response!!! And the work-around, ah ... worked 🙂