Conquest 1.5.0d released

    Hi Marcel! I'm installing the newest version of conquest on ubuntu server and this is my second time through. Both times, I've gotten to this point and it seems to fail each time for me:

    Code
    tim@conquest01:/conquest$ sudo systemctl start conquest.service
Failed to start conquest.service: Unit conquest.service has a bad unit file setting.
See system logs and 'systemctl status conquest.service' for details.

    I'm not sure why I'm getting this error. I've followed the how-to for installing this on linux. Then, as directed by the error above, I ran the systemctl status command and it's indicating that there's a bad unit file setting. Do you have any suggestions? --Tim

    Hi,

    I think you are missing envsubst that is used to replace {$CONQUEST} with the actual path. Did you install all the prerequisites? Or maybe you need additional ones on your version of Ubuntu

    Marcel

    Marcel van Herk is developer of the Conquest DICOM server together with Lambert Zijp.

    Thank you for your response Marcel. All pre-requisites were installed verbatim according to the conquest linux manual. I don't see anything about envsubst in the linux manual. I'm using Ubuntu 24.04 LTS for my server OS. Is this something I need to install? --Tim

    I ran this command:

    Code
    dpkg -L gettext-base

    and it appears I do have this installed:

    Code
    /usr/share/man/man1/envsubst.1.gz

    I still get this error:

    Code
    ${CONQUEST}/dgate

    Has not been substituted in Conquest.Service.

    [Unit]

    Description=conquest dicom server service

    After=network.target

    [Service]

    ExecStart=${CONQUEST}/dgate -w${CONQUEST} -v

    KillMode=process

    Restart=always

    RestartSec=10

    SyslogIdentifier=conquest-server

    [Install]

    WantedBy=multi-user.target

    Marcel van Herk is developer of the Conquest DICOM server together with Lambert Zijp.

    Here is should happen in maklinux.sh:

    envsubst <conquest.service >t.t

    read -p "Install as service?" -r

    echo $REPLY

    if [[ $REPLY =~ ^[Yy]$ ]]

    then

    sudo systemctl stop conquest.service

    sudo cp t.t /etc/systemd/system/conquest.service

    sudo systemctl daemon-reload

    sudo systemctl start conquest.service

    sudo systemctl enable conquest.service

    sudo systemctl status conquest.service

    fi

    Marcel van Herk is developer of the Conquest DICOM server together with Lambert Zijp.

    Hi Marcel, I did confirm what happens when I re-ran the ./maklinux command. I don't believe that fixed it. This is a head-scratcher. I followed the install linux manual instructions and ensured all the prerequisites were installed. --Tim

    Yes, thank you again for being so helpful with this. I know you're a busy person. --Tim

    Contents of conquest.service:

    Thanks for your response!

    Changing it from this:

    ExecStart=${CONQUEST}/dgate -w${CONQUEST} -v

    To:

    ExecStart=$/conquest/dgate -w$/conquest -v

    Does that look correct?

    After the update, I still get an error:

    Code
    root@conquest01:/conquest# nano conquest.service
root@conquest01:/conquest# systemctl daemon-reload
root@conquest01:/conquest# systemctl start conquest.service
Failed to start conquest.service: Unit conquest.service has a bad unit file setting.
See system logs and 'systemctl status conquest.service' for details.

    ? Success! I have several more servers to build. I'll report back if this seems to be a common behavior with the combination of Conquest and Ubuntu versions that I'm using.

    Thank you marcelvanherk for being so patient with me. I'm going to build a 4-conquest server cluster from scratch, using IPVS to create a load balanced setup. I'm happy to share all configs once it's all working if that might be useful to someone else. --Tim

    What do you need to achieve? The lightest update is just replace dgate64.exe and conquestdicomserver.exe and the dlls. Of you can setup a new server and point it a the old data, this allows a full test. Marcel

    Marcel van Herk is developer of the Conquest DICOM server together with Lambert Zijp.

    Hello! Please help! I tried to log into the web server control panel and received the error "dicom error connect failed on socket level (called not running)". After that, I foolishly launched the linux.sh script. The control panel of course started working, but the files that were on the hard drive are now inaccessible. How can I fix this problem? Thank you!

    Hi,

    linux.sh starts a web-based installer, nothing more. It does not do anything by itself apart from building dgatesmall and setting up app/service web folder. What control panel and files are you talking about?

    Marcel

    Marcel van Herk is developer of the Conquest DICOM server together with Lambert Zijp.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login