Sorry!
Fixed now.
Sorry!
Fixed now.
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:
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
May 25 08:20:15 conquest01 conquest-server[34653]: Monitoring for files in: /conquest/data/incoming/
May 25 08:20:15 conquest01 conquest-server[34653]: DGATE (1.5.0c, build Sat May 25 07:39:47 2024, bits 64) is running as threaded server
May 25 08:20:15 conquest01 systemd[1]: /etc/systemd/system/conquest.service:9: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, a>
May 25 08:20:15 conquest01 systemd[1]: /etc/systemd/system/conquest.service:10: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, >
May 25 08:24:06 conquest01 systemd[1]: /etc/systemd/system/conquest.service:5: Neither a valid executable name nor an absolute path: ${CONQUEST}/dgate
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
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:
and it appears I do have this installed:
I still get this error:
May 25 08:20:15 conquest01 conquest-server[34653]: Monitoring for files in: /conquest/data/incoming/
May 25 08:20:15 conquest01 conquest-server[34653]: DGATE (1.5.0c, build Sat May 25 07:39:47 2024, bits 64) is running as threaded server
May 25 08:20:15 conquest01 systemd[1]: /etc/systemd/system/conquest.service:9: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider remo>
May 25 08:20:15 conquest01 systemd[1]: /etc/systemd/system/conquest.service:10: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider rem>
May 25 08:24:06 conquest01 systemd[1]: /etc/systemd/system/conquest.service:5: Neither a valid executable name nor an absolute path: ${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
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
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
/usr/bin/install: cannot create regular file '/usr/local/man/man1/cjpeg.1': No such file or directory
[Regen] /conquest/data/0009703828/1.3.46.670589.5.2.10.2156913941.892665339.860724_0001_003000_14579035620001.dcm -SUCCESS
[Regen] /conquest/data/0009703828/1.3.46.670589.5.2.10.2156913941.892665339.860724_0001_002000_14579035620000.dcm -SUCCESS
May 25 22:55:55 conquest01 conquest-server[43938]: Monitoring for files in: /conquest/data/incoming/
May 25 22:55:55 conquest01 conquest-server[43938]: DGATE (1.5.0d, build Sat May 25 22:55:49 2024, bits 64) is running as threaded server
May 25 22:55:55 conquest01 systemd[1]: /etc/systemd/system/conquest.service:9: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider remo>
May 25 22:55:55 conquest01 systemd[1]: /etc/systemd/system/conquest.service:10: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider rem>
Hm,
can you post file conquest.service?
Marcel
Yes, thank you again for being so helpful with this. I know you're a busy person. --Tim
Contents of conquest.service:
Hi, you need to replace the {} with the path of where the server is. This should have been done automatically
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:
no $. Greetings Marcel
🥳 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
Great!
will share the setup if you shaer it with me.
Marcel
Hi Marcel,
I have been setting up a few Veterinary Clinics with earlier versions of Conquest.
Haven't updated to the latest version as yet.
So what to test first.
Cheers Peter
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
Hi Ken,
Links on the forum work.
Marcel
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
Don’t have an account yet? Register yourself now and be a part of our community!