Problem upgrading from 3.1.8 to 6.1.1

[Stephan]

Hi,

so after the problems with the new server are solved, I tried to upgrade an old 3.1.8 installation to 6.1.1 and ran into a somewhat odd problem.


I followed the upgade instructions and when I execute ./Setup.exe I'm getting no output at all, just a floating point exception. When I try to execute install.sh to upgrade to 6.1.1, I get the following floating point exception:

[root@localhost pacsone]# ./install.sh
Checking for pre-requisites...
OK.
Configuring PacsOne Server Startup Scripts...
Done.
Configuring MySql Libraries...
/usr/bin/install -c .libs/libmysqlpp.so.2.3.2 /usr/local/lib/libmysqlpp.so.2.3.2
(cd /usr/local/lib && rm -f libmysqlpp.so.2 && ln -s libmysqlpp.so.2.3.2 libmysqlpp.so.2)
(cd /usr/local/lib && rm -f libmysqlpp.so && ln -s libmysqlpp.so.2.3.2 libmysqlpp.so)
/usr/bin/install -c .libs/libmysqlpp.lai /usr/local/lib/libmysqlpp.la
PATH="$PATH:/sbin" ldconfig -n /usr/local/lib
----------------------------------------------------------------------
Libraries have been installed in:
/usr/local/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
Done.
Configuring ImageMagick Libraries...
/usr/bin/install -c .libs/libMagick-5.5.6-Q16.so.0.0.0 /usr/local/lib/libMagick-5.5.6-Q16.so.0.0.0
(cd /usr/local/lib && rm -f libMagick-5.5.6-Q16.so.0 && ln -s libMagick-5.5.6-Q16.so.0.0.0 libMagick-5.5.6-Q16.so.0)
(cd /usr/local/lib && rm -f libMagick.so && ln -s libMagick-5.5.6-Q16.so.0.0.0 libMagick.so)
/usr/bin/install -c .libs/libMagick.lai /usr/local/lib/libMagick.la
PATH="$PATH:/sbin" ldconfig -n /usr/local/lib
----------------------------------------------------------------------
Libraries have been installed in:
/usr/local/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
PATH="$PATH:/sbin" ldconfig -n /usr/local/lib
----------------------------------------------------------------------
Libraries have been installed in:
/usr/local/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------

dcm.la
gif.la
jpeg.la
ttf.la
Done.

Configuring PacsOne Server...
/usr/bin/ldd: line 124: 19358 Gleitkomma-Ausnahme LD_TRACE_LOADED_OBJECTS=1 LD_WARN= LD_BIND_NOW= LD_LIBRARY_VERSION=$verify_out LD_VERBOSE= "$@"
./install.sh: line 164: 19360 Gleitkomma-Ausnahme $basedir/Setup.exe
PacsOne Server Installation Complete.

PacsOne 3.1.8 was running fine, no problem when I installed it about 2 years ago. The OS is Fedora Core 4, Kernel version 2.6.11-1.1369.

The recently installed backup server is running 6.1.1 just fine under Fedora Core 7, Kernel 2.6.21-13194.

Any ideas what could cause the floating point exception and how to solve it?

Thanks and all the best,
Stephan

[Stephan]

As a little side note, after the upgrade procedure didn't work, I tried to go back to version 3.1.8 (which I backed up). Something was screwed while trying to apply the upgrade. I started to have trouble with mysql, which I solved and now the license files (the original for version 3.1.8 and the new one for 6.1.1) don't work anymore accoring to the log.

I'd like to solve the floating point issue first though, so I can upgrade to 6.1.1. Then the license problem can be solved.

I hope it can be solved without having to install FC7, which would mean a complete new server installation.

[pacsone]

A couple of users have reported similar exception error when running the latest version 6.1.1 executables. The root cause of the problem was the dynamic linker (ld) on some of the older Linux platforms (e.g., like the FC4 you are running) do not recognize the GNU hash encoded in the Linux ELF header of the executables build by the newer compilers. The details of of the issue can be found from the following discussion forum:

http://forums.fedoraforum.org/printthread.php?t=137590

While we wish the GNU compiler developers had done a better job in backward compatibility, the workaround is to force the compiler to encode the SYSV hash instead of the GNU hash in the ELF header of the linked executables. You can download the SYSV hash version of the 6.1.1 package from the URL below:

http://www.rainbowfishsoftware.com/pacs ... ash.tar.gz

This package should run fine with the dynamic linker on the older platforms, so you should not need to upgrade to FC6 or later releases if you don't want to.

[Stephan]

Thank you, downloaded it already to the server and will try to install it later. I also got rid of the license error by applying the following command to the database:

Code: Select all

update patient set lastaccess=NOW();

I'll report back later, once I tried to install 6.1.1.

Thanks again.

[Stephan]

The SYSV hash version did indeed work. I ran into a ton of library dependency problems due to the old version lampp (1.4.9) though. So I kept Fedora Core 4 and installed the latest Lampp 1.6.6, did a fresh install of PacsOne 6.1.1 and started an import job on all the files on the raid partition (over 2TB again). Everything seems to work now. The import job of the backup archive took a few days, so I should know if everything worked later this week.

Thanks again for the help.

All the best,
Stephan