Minimserver start process

[simoncn]

The first step is to find out exactly what is causing this error. I don't think it is a good idea to change the MinimServer UI to work around an error condition unless there is no other way to resolve the error. Please do the following:

1) When running MinimServer from disk, set the MinimServer .logLevel property to debug
2) Check the files minimserver/data/default.profile and minimserver/data/minimserver.config to make sure they contain the line .logLevel = debug
3) Stop MinimServer completely
4) Boot the system with your RAM disk enabled
5) You should see the MinimServer license error 13 message
6) Make a copy of the minimserver/data/minimserver.log file
7) Zip or compress this file (this step is important) and attach it to a post here

I hope this log file will enable me to understand why the error is occurring.

[lafuente]

Hello Simon,

Here are 2 logs :

- The first one is only the first start-up with error 13
- The second also contain the minimserver restart per ssh and the full licence activation.

Hope this will help.

You didn't answer about the possibility to use a symbolic link ?

Regards,
Manu

[simoncn]

Thanks for posting these logs. After studying them carefully, I think the only way to make this work correctly and reliably is to ensure the RAM system is fully in place before the MinimServer service is started. Is this possible?

[lafuente]

(02-03-2025 23:07)simoncn Wrote:  Thanks for posting these logs. After studying them carefully, I think the only way to make this work correctly and reliably is to ensure the RAM system is fully in place before the MinimServer service is started. Is this possible?

It may be possible with adding :

Code:

[Unit]
After=local-fs.target
Requires=local-fs.target

in service script.

If you tell me the location of this file, I'll try and report

[lafuente]

Just to let you know : if I create a symlink to minimserver.licence to a "non RAM location", I still have the error.

[simoncn]

(03-03-2025 08:58)lafuente Wrote:  It may be possible with adding :

Code:

[Unit]
After=local-fs.target
Requires=local-fs.target

in service script.

This sounds like the correct solution. The logs you sent show that adding a symlink will not solve the startup problem.

Quote:If you tell me the location of this file, I'll try and report

The MinimServer service file is /usr/lib/systemd/system/minimserver.service.

[lafuente]

Hello Simon,

Thank you. Unfortunately I don't have the service file at the location you said.

From a find command I have :

Code:

/sys/fs/cgroup/system.slice/minimserver.service
/run/systemd/generator.late/minimserver.service
/run/systemd/generator.late/graphical.target.wants/minimserver.service
/run/systemd/generator.late/multi-user.target.wants/minimserver.service

Which don't sound like the one I have to change.

Do you have any idea about where I have to modify the required file ?

Thank you,
Manu

[lafuente]

From the command

systemctl status minimserver.service

it's look like the .Service file is generated per bash script located at

Code:

/etc/init.d/minimserver; generated)

If that can help.

[lafuente]

Here is the contain of one of the minimserver.service file :

Code:

# Automatically generated by systemd-sysv-generator

[Unit]
Documentation=man:systemd-sysv-generator(8)
SourcePath=/etc/init.d/minimserver
Description=LSB: Start and stop MinimServer
Before=multi-user.target
Before=multi-user.target
Before=multi-user.target
Before=graphical.target
After=all.target

[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
SuccessExitStatus=5 6
ExecStart=/etc/init.d/minimserver start
ExecStop=/etc/init.d/minimserver stop

Sound good, but I fear that it's generated at each boot since it's in the /run repertory

[simoncn]

From your last posts it sounds like the minimserver/bin/setup command has created an init.d startup file (/etc/init.d/minimserver) instead of a systemd startup file (minimserver.service). This is for backward compatibility with older Linux systems. MinimServer supports both init.d and systemd, choosing systemd if init.d is not available.

I will create a test build of MinimServer with an option to create a systemd startup file instead of an init.d startup file. When this test build is ready, I will send you a PM with details of how to access it.