Mity CPU Platforms » MityDSP-L138 (ARM9 Based Platforms)

Hello,

I have a server to launch at system boot time using the Yocto compatible FS from ALPHA Release 2016.01 on DBRIC hardware. The server uses a template unit file, and I am having trouble getting it enabled. We use the template to supply a full path name of a sqlite database file the server uses. Here is the template unit file in /lib/systemd/system/TDI_DataServer@.service:

[Unit]
    Description=NDC Technologies Data Server application (with DB=%I)
    After=syslog.target

[Service]
    Type=simple
    ExecStart=/opt/ndc/DataServer --DEBUG --databaseFile=%I
    Restart=always
    RestartSec=2

[Install]
    WantedBy=multi-user.target

The database file is in /var/lib/ndc/DataServer.DB, so I created a symbolic link in /lib/systemd/system:
TDI_DataServer@-var-lib-ndc-DataServer.DB.service -> TDI_DataServer@.service

When I run:

$ systemctl start TDI_DataServer@-var-lib-ndc-DataServer.DB

The server launches with the correct parameter, finds the database, and executes. So I tried to enable the service template so that it will run on system boot:

$ systemctl enable TDI_DataServer@-var-lib-ndc-DataServer.DB
    Failed to execute operation: No such file or directory

I've seen some posts online that this should work, but there was a bug in systemd preventing it from succeeding.

Are you aware of this bug?
Is there a fix that can be applied to the Yocto FS?

Since that failed, I tried enabling the template file itself:

$ systemctl enable TDI_DataServer@
    ln -s '/lib/systemd/system/TDI_DataServer@.service' '/etc/systemd/system/multi-user.target.wants/TDI_DataServer@.service'

On the surface, the system seems happy, but at boot time, systemd does not execute the launch of TDI_DataServer correctly. It seems to supply the "multi-user" parameter (maybe from the WantedBy target in the unit file?) to the unit file.

Here is the systemctl status:

$ systemctl status -l TDI*
    ● TDI_DataServer@multi-user.service - NDC Technologies Data Server application (with DB=multi/user)
       Loaded: loaded (/lib/systemd/system/TDI_DataServer@.service; enabled)
       Active: activating (auto-restart) (Result: signal) since Sat 2000-02-05 20:41:05 UTC; 1s ago
      Process: 2951 ExecStart=/opt/ndc/DataServer --DEBUG --databaseFile=%I (code=killed, signal=ABRT)
     Main PID: 2951 (code=killed, signal=ABRT)

Feb 05 20:41:05 mityomapl138 DataServer[2951]: [949783265:2047] NOTICE:  per-conn mem: 136 + 2140 headers + protocol rx buf
    Feb 05 20:41:05 mityomapl138 DataServer[2951]: [949783265:2056] NOTICE:  Listening on port 4243
    Feb 05 20:41:05 mityomapl138 systemd[1]: TDI_DataServer@multi-user.service: main process exited, code=killed, status=6/ABRT
    Feb 05 20:41:05 mityomapl138 systemd[1]: Unit TDI_DataServer@multi-user.service entered failed state.
    Feb 05 20:41:05 mityomapl138 DataServer[2951]: 2000:02:05 20:41:05: WSServer connected on socket tcp://localhost:5556
    Feb 05 20:41:05 mityomapl138 DataServer[2951]: 2000:02:05 20:41:05:  bound to socket inproc://clients
    Feb 05 20:41:05 mityomapl138 DataServer[2951]: 2000:02:05 20:41:05: DatabaseWorker using database multi/user
    Feb 05 20:41:05 mityomapl138 DataServer[2951]: unable to open database file
    Feb 05 20:41:05 mityomapl138 DataServer[2951]: terminate called after throwing an instance of 'SQLite::Exception'
    Feb 05 20:41:05 mityomapl138 DataServer[2951]: what():  unable to open database file

● TDI_DataServer.service
       Loaded: loaded (/etc/init.d/TDI_DataServer)
       Active: inactive (dead)

Am I missing something? As I said earlier, I've seen some posts about a systemd bug for enabling unit template files, but I'm not sure if it applies here.

Thanks for your help.

Regards,

Ben