On Thu, Apr 26, 2018 at 6:45 AM, Elita Lobo <loboelita@xxxxxxxxx> wrote:
> Hi,
>
> We re-tried installing the latest version of Ceph from source and got
> several dependency issues while running ./do_cmake.sh command ( lz4
> library not found, CMake Error at
> /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108
> (message):
> Could NOT find CURL (missing: CURL_LIBRARY CURL_INCLUDE_DIR) ).
>
> Can you please tell us which version of Ubuntu is the latest version
> of Ceph compatible with? We are currently trying to install it on
> Ubuntu 16.04.
16.04 is compatible with the latest version of Ceph.
>
> Also install_deps.sh throws an error - ceph-build package not found
> while it was trying to run the following command which we have now
> commented out.
> $SUDO env DEBIAN_FRONTEND=noninteractive apt-get -y remove ceph-build-deps
>
> Can you please let us know which script installs this package so that
> we can accordingly check why it is missing in our system.
>
install_deps.sh installs that package:
# make a metapackage that expresses the build dependencies,
# install it, rm the .deb; then uninstall the package as its
# work is done
$SUDO env DEBIAN_FRONTEND=noninteractive mk-build-deps --install
--remove --tool="apt-get -y --no-install-recommends $backports"
$control || exit 1
I am guessing you are seeing failures before that.
>
> Thanks,
> Elita
>
> On Thu, Apr 12, 2018 at 1:48 PM, Ma, Jianpeng <jianpeng.ma@xxxxxxxxx> wrote:
>>
>> Hi,
>> Based on 032d3b53fb40e978148326a4ed397b9c1b24f855(latest). I run your commands many times and didn't meet any error.
>> Is the same as my ceph master?
>>
>> Thanks
>> Jianpeng.
>>
>> -----Original Message-----
>> From: ceph-devel-owner@xxxxxxxxxxxxxxx [mailto:ceph-devel-owner@xxxxxxxxxxxxxxx] On Behalf Of Myna V
>> Sent: Thursday, April 12, 2018 3:17 PM
>> To: ceph-devel <ceph-devel@xxxxxxxxxxxxxxx>
>> Cc: Vinayak Ramkumar <vinram93@xxxxxxxxx>; Elita Lobo <loboelita@xxxxxxxxx>
>> Subject: Crash during rados put
>>
>> Hello Guys,
>>
>> I see the following crash during a rados put command on the latest ceph master. Did the rados put command change?
>>
>> OSD=8 MON=1 MDS=0 ../src/vstart.sh -n -d -x -l ceph osd erasure-code-profile set rs_jerasure k=4 m=2 plugin=jerasure crush-failure-domain=osd ceph osd pool create rs_jerasure_pool 1 1 erasure rs_jerasure rados --pool rs_jerasure_pool put rs_jerasure_obj test1MB.txt
>>
>>
>> 1: (()+0x56832) [0x562d393ae832]
>> 2: (()+0x11390) [0x7f307dca7390]
>> 3: (gsignal()+0x38) [0x7f307ce55428]
>> 4: (abort()+0x16a) [0x7f307ce5702a]
>> 5: (__gnu_cxx::__verbose_terminate_handler()+0x135) [0x7f307d79c0d5]
>> 6: (()+0x8fcc6) [0x7f307d799cc6]
>> 7: (()+0x8fd11) [0x7f307d799d11]
>> 8: (()+0x8ff54) [0x7f307d799f54]
>> 9: (entity_addr_t::decode(ceph::buffer::list::iterator&)+0x33a)
>> [0x7f307e0e89aa]
>> 10: (void decode<entity_addr_t,
>> std::allocator<std::shared_ptr<entity_addr_t> >
>> >(std::vector<std::shared_ptr<entity_addr_t>,
>> std::allocator<std::shared_ptr<entity_addr_t> > >&,
>> ceph::buffer::list::iterator&)+0x8f) [0x7f307e2e5fff]
>> 11: (OSDMap::decode(ceph::buffer::list::iterator&)+0x2a8) [0x7f307e2dac98]
>> 12: (OSDMap::decode(ceph::buffer::list&)+0x2e) [0x7f307e2dcd4e]
>> 13: (Objecter::handle_osd_map(MOSDMap*)+0x22a3) [0x7f3086e0d743]
>> 14: (Objecter::ms_dispatch(Message*)+0x22f) [0x7f3086e0e4df]
>> 15: (DispatchQueue::entry()+0xf4a) [0x7f307e1d14aa]
>> 16: (DispatchQueue::DispatchThread::entry()+0xd) [0x7f307e26c5bd]
>> 17: (()+0x76ba) [0x7f307dc9d6ba]
>> 18: (clone()+0x6d) [0x7f307cf2741d]
>>
>> Any help on this will be appreciated.
>>
>> Thanks
>> Myna.
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
