Jump to content

assert failed osfile.cpp:1508


Recommended Posts

Had to rebuild a server that was running utserver latest linux. Now utserver dies after a few seconds but no real indicators what its missing. Does it required 32 bit libs as well?

Went from Opensuse 13.1 to 13.2 (both x64)

Installed libssl and libcrypto (64bit ) and laster added 32bit to see if it was looking for those libs for some reason



Starting Utorrent Server..
/opt/utorrent/utserver: /lib64/libcrypto.so.1.0.0: no version information available (required by /opt/utorrent/utserver)
/opt/utorrent/utserver: /lib64/libssl.so.1.0.0: no version information available (required by /opt/utorrent/utserver)
assert failed osfile.cpp:1508 (30470)
/opt/utorrent/utserver: /lib64/libcrypto.so.1.0.0: no version information availa                                                                                                                      ble (required by /opt/utorrent/utserver)
/opt/utorrent/utserver: /lib64/libssl.so.1.0.0: no version information available                                                                                                                       (required by /opt/utorrent/utserver)
        linux-vdso.so.1 (0x00007fff47dfc000)
        libssl.so.1.0.0 => /lib64/libssl.so.1.0.0 (0x00007fa64bd15000)
        libcrypto.so.1.0.0 => /lib64/libcrypto.so.1.0.0 (0x00007fa64b8f3000)
        libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fa64b6db000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fa64b4be000)
        librt.so.1 => /lib64/librt.so.1 (0x00007fa64b2b6000)
        libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fa64afad000)
        libm.so.6 => /lib64/libm.so.6 (0x00007fa64acac000)
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fa64aa95000)
        libc.so.6 => /lib64/libc.so.6 (0x00007fa64a6ec000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fa64bfa0000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007fa64a4e8000)
        libz.so.1 => /lib64/libz.so.1 (0x00007fa64a2d2000)


Link to comment
Share on other sites

This assertion indicates that uTorrent Server could not open a file.  It would have been better if the process generated a log message for this failure (it does in debug builds...).


Hopefully that's some sort of clue to work with; you could reduce the number of torrents being seeded or downloaded, or check where they are being stored, or check what you've got as a temporary directory (change dir_temp_files parameter in utserver.conf if necessary).  Also, could check dir_autoload, dir_torrent_files, dir_completed, dir_request, and entries for dir_download.  Also check the settings directory.  This is in case you've changed your file system or drive setup at the same time you upgraded the OS.


Could also check the version of OpenSSL on your system, although I would think loading would fail if a compatible version wasn't available.

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...