Ubuntu 18 support
152 views
Skip to first unread message
Dave
Jul 4, 2019, 12:01:15 AM7/4/19
to Orthanc Users
I appreciate that as yet, Orthanc doesn't support Ubuntu 18 and wondered if this would be looked at any time soon?
I've recently posted a script that takes the compiled binaries and installs them onto U14 and U16 so that one doesn't have to compile everything. With the 1.5.7 version now released, I've tested that again but it fails with a "segmentation fault"
So I compiled my own version, using -DSTATIC_BUILD=ON and I get the exact same result. Considering I'm not a developer, maybe I'm doing something right for once!
So then I tried following the notes from here {https://bitbucket.org/sjodogne/orthanc/src/default/LinuxCompilation.txt} and everything worked just fine.
However, when I take the compiled binaries (same as those listed {http://lsb.orthanc-server.com/orthanc/1.5.7}} and move them to another server and try installing them without compilation, I start getting missing library files (jsoncpp, libboost_filesystem) etc. I guess that's to be expected as (my limited understanding being) when you assign a STATIC_BUILD, all those extra libraries are included in the compiled binaries, which makes them portable.
So - is there any movement anywhere to get those statically linked libraries working on Ubuntu 18? I don't even mind installing additional libraries if that would help (the jsoncpp can be installed with "apt-get install libjsoncpp1" but I didn't go through all the lists as I wondered if there was a "better" way of doing things?
Alain Mazy
Jul 4, 2019, 8:25:35 AM7/4/19
to Dave, Orthanc Users
Hi Dave,
LSB binaries seems to work on my ubuntu 18.10:
amazy@alain-ubuntu-18:~$ sudo chmod +x /usr/bin/Orthanc
amazy@alain-ubuntu-18:~$ Orthanc
W0704 14:22:03.791190 main.cpp:1442] Orthanc version: 1.5.7
...
W0704 14:22:04.348937 main.cpp:714] Orthanc has started
amazy@alain-ubuntu-18:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="18.10 (Cosmic Cuttlefish)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.10"
VERSION_ID="18.10"
NAME="Ubuntu"
VERSION="18.10 (Cosmic Cuttlefish)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.10"
VERSION_ID="18.10"
--
You received this message because you are subscribed to the Google Groups "Orthanc Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orthanc-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/orthanc-users/b522f87d-865b-4061-b643-4a0ae6fc4a80%40googlegroups.com.
Alain Mazy / Software Developer
a...@osimis.io / +32 494 31 67 27
| OSIMIS S.A.
|
Alain Mazy
Jul 4, 2019, 9:24:29 AM7/4/19
to Dave, Orthanc Users
Hi Dave,
Sorry, since my machine is a dev machine, it had a few package installed already that made it work....
I'll try to isolate the minimum packages to install
Alain Mazy
Jul 4, 2019, 10:35:19 AM7/4/19
to Dave, Orthanc Users
Hi,
Here's a Dockerfile to run Orthanc on an ubuntu:18.10 image. You shall be able to run the same commands (without the 'RUN') on a real ubuntu machine.
FROM ubuntu:18.10
RUN apt-get update
RUN apt-get install -y wget
RUN apt-get install -y lsb-core
RUN apt-get install -y locales
RUN wget http://lsb.orthanc-server.com/orthanc/1.5.7/Orthanc --output-document /usr/sbin/Orthanc --quiet
RUN chmod +x /usr/sbin/Orthanc
RUN locale-gen en_US en_US.UTF-8
RUN ln -s /lib64/ld-linux-x86-64.so.2 /lib/ld-linux-x86-64.so.2
RUN export DEBIAN_FRONTEND=noninteractive && apt-get -y install tzdata
# after that, you must run 'dpkg-reconfigure tzdata' once to enter real time zone ! Let's automate it !
RUN ln -fs /usr/share/zoneinfo/Europe/Brussels /etc/localtime
RUN dpkg-reconfigure -f noninteractive tzdata
ENTRYPOINT Orthanc
RUN apt-get update
RUN apt-get install -y wget
RUN apt-get install -y lsb-core
RUN apt-get install -y locales
RUN wget http://lsb.orthanc-server.com/orthanc/1.5.7/Orthanc --output-document /usr/sbin/Orthanc --quiet
RUN chmod +x /usr/sbin/Orthanc
RUN locale-gen en_US en_US.UTF-8
RUN ln -s /lib64/ld-linux-x86-64.so.2 /lib/ld-linux-x86-64.so.2
RUN export DEBIAN_FRONTEND=noninteractive && apt-get -y install tzdata
# after that, you must run 'dpkg-reconfigure tzdata' once to enter real time zone ! Let's automate it !
RUN ln -fs /usr/share/zoneinfo/Europe/Brussels /etc/localtime
RUN dpkg-reconfigure -f noninteractive tzdata
ENTRYPOINT Orthanc
Dave
Jul 5, 2019, 7:33:29 PM7/5/19
to Orthanc Users
Alain,
I really appreciate the feedback here and I believe that I've found a bug in 1.5.7 related to setting the server's environment to UTC... The following was tested on an Ubuntu 18.04.2 VM (which is configured, by default, to UTC) without anything more than LAMP installed (ie, it would appear that lsb-core and locales isn't required but I've tested with these installed as well and the results are the same). Using my original script (updated to use the 1.5.7 binaries)
- cd /etc/orthanc
- ./Orthanc ./orthanc.json --verbose
- Segmentation fault (core dumped)
- ln -fs /usr/share/zoneinfo/America/Los_Angeles /etc/localtime
- dpkg-reconfigure -f noninteractive tzdata
- cd /etc/orthanc
- ./Orthanc ./orthanc.json --verbose
- Orthanc starts without any issues at all (champagne corks are heard popping in Southern California)
- Ctrl + C (Orthanc shuts down)
- ln -fs /usr/share/zoneinfo/UTC /etc/localtime
- dpkg-reconfigure -f noninteractive tzdata
- ./Orthanc ./orthanc.json --verbose
- Segmentation fault (core dumped)
So it appears if the server is set to UTC, Orthanc has a problem? Would you be able to double-check this please? I can change to (seemingly) any timezone (including London, Brussels etc) and Orthanc starts up just fine, but when it's set to UTC that's when the fault appears.
Sébastien Jodogne
Jul 6, 2019, 5:56:10 AM7/6/19
to Orthanc Users
Hello,
Maybe your problem has already been discussed and solved in this thread:
Please could you test whether the fact of installing the "tzdata" package from Ubuntu 18.04 solves your issue?
This problem comes from Boost, that assumes the "/etc/localtime" to be present:
If this is not sufficient, please follow this FAQ to send us an useful backtrace:
HTH,
Sébastien-
Message has been deleted
Message has been deleted
Dave
Jul 7, 2019, 5:26:26 PM7/7/19
to Orthanc Users
Sebastien,
I installed tzdata and the problem persists. I also check that /etc/localtime exists, which it does.
The segmentation fault exists with any "Etc/" timezone (Greenwich, UCT, UTC, Universal and Zulu). At this point I created a snapshot of the VM ("BinaryInstall").
I then set my VM back to the snapshot prior to BinaryInstall, and built Orthanc, created the crash.so file as per the backtrace page, and then placed it on my host. I also snapshot at this point called "Build".
I then set my VM back to the BinaryInstall snapshot and copied crash.so from my host to the VMs /usr/share/orthanc/plugins/ folder. Starting up Orthanc in the same manner ("Orthanc /etc/orthanc --verbose) I see that it registered the plugin 'crash' and dumped the core.
Question is: where's the core file that it creates? I performed a "find / -name core -print" on the VM and it came up with a bunch of results:
/proc/sys/net/core
/dev/core
/snap/core
/snap/core/6350/dev/core
/snap/core/6350/var/lib/initramfs-tools/core
/snap/core/7270/dev/core
/snap/core/7270/var/lib/initramfs-tools/core
/var/snap/core
/lib/modules/4.15.0-54-generic/kernel/net/core
/lib/modules/4.15.0-54-generic/kernel/drivers/mmc/core
/lib/modules/4.15.0-54-generic/kernel/drivers/memstick/core
/lib/modules/4.15.0-54-generic/kernel/drivers/net/ethernet/mellanox/mlx5/core
/lib/modules/4.15.0-54-generic/kernel/drivers/infiniband/core
/lib/modules/4.15.0-54-generic/kernel/drivers/video/fbdev/core
/lib/modules/4.15.0-54-generic/kernel/drivers/gpu/drm/tinydrm/core
/lib/modules/4.15.0-54-generic/kernel/drivers/usb/core
/lib/modules/4.15.0-54-generic/kernel/sound/core
/usr/src/linux-headers-4.15.0-54/net/core
/usr/src/linux-headers-4.15.0-54/drivers/mmc/core
/usr/src/linux-headers-4.15.0-54/drivers/memstick/core
/usr/src/linux-headers-4.15.0-54/drivers/net/ethernet/mellanox/mlx5/core
/usr/src/linux-headers-4.15.0-54/drivers/infiniband/core
/usr/src/linux-headers-4.15.0-54/drivers/video/fbdev/core
/usr/src/linux-headers-4.15.0-54/drivers/gpu/drm/tinydrm/core
/usr/src/linux-headers-4.15.0-54/drivers/gpu/drm/nouveau/nvkm/core
/usr/src/linux-headers-4.15.0-54/drivers/usb/core
/usr/src/linux-headers-4.15.0-54/sound/aoa/core
/usr/src/linux-headers-4.15.0-54/sound/core
/usr/src/linux-headers-4.15.0-54-generic/include/config/mlx5/core
/usr/src/linux-headers-4.15.0-54-generic/include/config/mlxsw/core
/usr/src/linux-headers-4.15.0-54-generic/include/config/mlx4/core
/usr/src/linux-headers-4.15.0-54-generic/include/config/serial/core
/usr/src/linux-headers-4.15.0-54-generic/include/config/core
I was under the impression that the core file is created in the current working directory, (which is /home/dave) but that file didn't exist, so I then went and installed lsb-core as perhaps that's why I didn't get the file I was looking for, in the folder I was expecting, but even after that, the file didn't exist (and a "find" produced the same results as before I installed lsb-core). I also went back to the build instructions and installed all of the required packages in order to build Orthanc ... and afterwards, the additional core files found were those related to boost:
/proc/sys/net/core
/dev/core
/snap/core
/snap/core/6350/dev/core
/snap/core/6350/var/lib/initramfs-tools/core
/snap/core/7270/dev/core
/snap/core/7270/var/lib/initramfs-tools/core
/var/snap/core
/lib/modules/4.15.0-54-generic/kernel/net/core
/lib/modules/4.15.0-54-generic/kernel/drivers/mmc/core
/lib/modules/4.15.0-54-generic/kernel/drivers/memstick/core
/lib/modules/4.15.0-54-generic/kernel/drivers/net/ethernet/mellanox/mlx5/core
/lib/modules/4.15.0-54-generic/kernel/drivers/infiniband/core
/lib/modules/4.15.0-54-generic/kernel/drivers/video/fbdev/core
/lib/modules/4.15.0-54-generic/kernel/drivers/gpu/drm/tinydrm/core
/lib/modules/4.15.0-54-generic/kernel/drivers/usb/core
/lib/modules/4.15.0-54-generic/kernel/sound/core
/usr/src/linux-headers-4.15.0-54/net/core
/usr/src/linux-headers-4.15.0-54/drivers/mmc/core
/usr/src/linux-headers-4.15.0-54/drivers/memstick/core
/usr/src/linux-headers-4.15.0-54/drivers/net/ethernet/mellanox/mlx5/core
/usr/src/linux-headers-4.15.0-54/drivers/infiniband/core
/usr/src/linux-headers-4.15.0-54/drivers/video/fbdev/core
/usr/src/linux-headers-4.15.0-54/drivers/gpu/drm/tinydrm/core
/usr/src/linux-headers-4.15.0-54/drivers/gpu/drm/nouveau/nvkm/core
/usr/src/linux-headers-4.15.0-54/drivers/usb/core
/usr/src/linux-headers-4.15.0-54/sound/aoa/core
/usr/src/linux-headers-4.15.0-54/sound/core
/usr/src/linux-headers-4.15.0-54-generic/include/config/mlx5/core
/usr/src/linux-headers-4.15.0-54-generic/include/config/mlxsw/core
/usr/src/linux-headers-4.15.0-54-generic/include/config/mlx4/core
/usr/src/linux-headers-4.15.0-54-generic/include/config/serial/core
/usr/src/linux-headers-4.15.0-54-generic/include/config/core
/usr/include/boost/hana/fwd/core
/usr/include/boost/hana/core
/usr/include/boost/geometry/multi/core
/usr/include/boost/geometry/core
/usr/include/boost/spirit/home/classic/core
/usr/include/boost/spirit/home/x3/core
/usr/include/boost/core
/usr/include/boost/phoenix/core
/usr/include/boost/xpressive/detail/core
/usr/include/boost/log/core
Once I know which one I'm supposed to send you, I will more than happily do so!
Sébastien Jodogne
Jul 9, 2019, 8:48:14 AM7/9/19
to Orthanc Users
Dear Dave,
The problem was extremely low-level... After a day of investigation, I think I finally managed to fix the issue thanks to the following changeset:
Please could you give a try to this new version with UTC? As usual, precompiled binaries are available at:
HTH,
Sébastien-
On Saturday, July 6, 2019 at 1:33:29 AM UTC+2, Dave wrote:
Dave
Jul 9, 2019, 12:09:31 PM7/9/19
to Orthanc Users
Sebastien,
Yes, thank you so much sir! Using the mainline versions, all /Etc timezones certainly appear to be working, no segmentation fault at startup.
Can I ask at this point - mainline is the "cutting edge" version, whereas 1.5.7 is the current "release" version, is that correct? If so, it would be fair to say that the latest "release" version should be used unless an issue is experienced, which may already be addressed in the "mainline" version, is that correct?
Kindest regards, and thank you for being patient with me!
Dave
Sébastien Jodogne
Jul 10, 2019, 2:36:51 AM7/10/19
to Orthanc Users
Glad to read that your issue is solved!
Can I ask at this point - mainline is the "cutting edge" version, whereas 1.5.7 is the current "release" version, is that correct?
Yes, this is correct. The "mainline" is where Orthanc core developers make their modifications.
If so, it would be fair to say that the latest "release" version should be used unless an issue is experienced, which may already be addressed in the "mainline" version, is that correct?
Yes, official releases should always be used, especially in production environments. The "mainline" version is unstable (it might change on a hourly basis, possibly introducing transient incompatibilities/issues), and no systematic quality control is achieved (contrarily to official releases).
Regards,
Sébastien-
Alain Mazy
Jul 12, 2019, 3:39:35 AM7/12/19
to Sébastien Jodogne, Orthanc Users
For the record, I do confirm that these are now the minimal steps to install Orthanc LSB on ubuntu18:
FROM ubuntu:18.10
RUN apt-get update
RUN apt-get -y install locales
RUN apt-get -y install wget
RUN export DEBIAN_FRONTEND=noninteractive && apt-get -y install tzdata
RUN locale-gen en_US en_US.UTF-8
RUN wget http://lsb.orthanc-server.com/orthanc/mainline/Orthanc --output-document /usr/sbin/Orthanc --quiet
RUN chmod +x /usr/sbin/Orthanc
ENTRYPOINT /usr/sbin/Orthanc
--
You received this message because you are subscribed to the Google Groups "Orthanc Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orthanc-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/orthanc-users/4a9c164e-a7d7-43ce-af7d-2e96ce6eabe1%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages