Minimserver start process

[lafuente]

Thank you

[lafuente]

Hello Simon,

I tried your script to use "systemd" as a launcher, but it's look like it don't operate well.
I had disabled the old method (initd), then enable the "systemd" one.
Without modifying the minimserver.service file I do :

Code:

systemctl daemon-reload
systemctl enable minimserver.service
systemctl start minimserver.service
systemctl list-units --type=service --state=running

And I don't see Minimserver in the running services, while Minim is really running, and is displayed in "ps -aux" command.

Code:

root@audio-nas:~# systemctl list-units --type=service --state=running
  UNIT                      LOAD   ACTIVE SUB     DESCRIPTION
  cron.service              loaded active running Regular background program processing daemon
  dbus.service              loaded active running D-Bus System Message Bus
  ES.service                loaded active running ExerciceStabilizer daemon
  getty@tty1.service        loaded active running Getty on tty1
  nfs-blkmap.service        loaded active running pNFS block layout mapping daemon
  rpc-statd.service         loaded active running NFS status monitor for NFSv2/3 locking.
  rpcbind.service           loaded active running RPC bind portmap service
  ssh.service               loaded active running OpenBSD Secure Shell server
  systemd-journald.service  loaded active running Journal Service
  systemd-logind.service    loaded active running User Login Management
  systemd-timesyncd.service loaded active running Network Time Synchronization
  systemd-udevd.service     loaded active running Rule-based Manager for Device Events and Files
  user@0.service            loaded active running User Manager for UID 0

Legend: LOAD   → Reflects whether the unit definition was properly loaded.
        ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
        SUB    → The low-level unit activation state, values depend on unit type.

13 loaded units listed.

BUT GREAT NEWS,
Minimserver now operate in Full License mode and in RAM mode without any need to do tricks. No more error at startup. I added the lines I describe before in the minimserver.service file and all is good.

Thank you very much.
Manu

[simoncn]

(05-03-2025 17:58)lafuente Wrote:  Hello Simon,

I tried your script to use "systemd" as a launcher, but it's look like it don't operate well.
I had disabled the old method (initd), then enable the "systemd" one.

If init.d is disabled, there is no difference between the old setup and the new setup. In this case, both of these automatically use systemd for startup.

Quote:Without modifying the minimserver.service file I do :

Code:

systemctl daemon-reload
systemctl enable minimserver.service
systemctl start minimserver.service
systemctl list-units --type=service --state=running

And I don't see Minimserver in the running services, while Minim is really running, and is displayed in "ps -aux" command.

This is because minimserver.service is used only at system startup to start the MinimServer daemon process. After this, minimserver.service exits. You will see it if you run this command:

Code:

systemctl list-units --type=service --state=exited

Quote:BUT GREAT NEWS,
Minimserver now operate in Full License mode and in RAM mode without any need to do tricks. No more error at startup. I added the lines I describe before in the minimserver.service file and all is good.

I am pleased to hear this problem is solved. To prevent other problems, I recommend that you create a persistent symlink for the minimserver/data directory so that any changes to files in this directory while MinimServer is running are not lost when the system is rebooted.

[simoncn]

(05-03-2025 17:58)lafuente Wrote:  I had disabled the old method (initd), then enable the "systemd" one.

How did you do this? It seems a better approach than replacing the setup script with a new version.

[lafuente]

(06-03-2025 10:20)simoncn Wrote:  

(05-03-2025 17:58)lafuente Wrote:  I had disabled the old method (initd), then enable the "systemd" one.

How did you do this? It seems a better approach than replacing the setup script with a new version.

With your script of course !

[simoncn]

Thanks for clarifying. I thought you meant you had competely disabled init.d in your system.

[lafuente]

Hello Simon,

(05-03-2025 20:37)simoncn Wrote:  To prevent other problems, I recommend that you create a persistent symlink for the minimserver/data directory so that any changes to files in this directory while MinimServer is running are not lost when the system is rebooted.

This don't operate. If I do this, I get an error when minimserver start, in the web GUI :

Code:

Incorrect target for symbolic link /usr/minimserver/data

While the symbolic link is good :

Code:

lrwxrwxrwx 1 root root   23  8 mars  09:19 data -> /home/minimserver/data/

I can list the files in this folder from any location, using any symlink I create.

If I just move files in data folder and link them each after each. At the end, at Minimserver start, some files will be created again in /minimserver/data folder, anyway
(removing the symlink an create a new file in the original folder) :



FIY,
Manu

[simoncn]

I have tried this and I see the same error message. I will post back here when I have more information.

[simoncn]

I have found the cause of this problem. The directory /tmp/.minimserver holds cached information which becomes invalid when the MinimServer data directory is changed to a symbolic link. The solution is to stop all running instances of MinimServer and run this command:

rm -rf /tmp/.minimserver

This must be done after creating the symbolic link. It should not need to be done again unless you later remove the symbolic link.

[lafuente]

Hello Simon,

I'm sorry to come back again about this issue, but at the end it seem to not operate. I'll post a log again soon.

Thank you,
Manu