[Bug 269979] net/megacmd: v1.5.0 broken (core dump during start)

From: <bugzilla-noreply_at_freebsd.org>
Date: Sun, 11 Jun 2023 10:06:48 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269979

--- Comment #8 from Riccardo Torrini <riccardo@torrini.org> ---
(In reply to Riccardo Torrini from comment #7)

mega answer:

Our developers have reviewed your issue and tried to reproduce the issue.
The issue was replicated in 1.5.0 however it works fine in 1.6.3.


Not too bad. But I still have error 500 during sync, runned rclone with
--log-level=DEBUG and --dump headers, updated mega ticket with this (here you
can see a modified log for readability)

{date} DEBUG : PROPFIND /{webdav_path}/data/52/ HTTP/1.1
{date} DEBUG : HTTP/1.1 207 Multi-Status
{date} DEBUG : MKCOL /{webdav_path}/data/52/ HTTP/1.1
{date} DEBUG : HTTP/1.1 405 Unknown Error
{date} DEBUG : MKCOL /{webdav_path}/data/52/ HTTP/1.1
{date} DEBUG : HTTP/1.1 405 Unknown Error
{date} DEBUG : PUT /{webdav_path}/data/52/{sha256-file_1} HTTP/1.1
{date} DEBUG : PUT /{webdav_path}/data/52/{sha256-file_2} HTTP/1.1
{date} DEBUG : HTTP/1.1 500 Internal Server Error
{date} DEBUG : HTTP/1.1 500 Internal Server Error
{date} DEBUG : DELETE /{webdav_path}/data/52/{sha256-file_1} HTTP/1.1
{date} DEBUG : HTTP/1.1 404 Not Found
{date} DEBUG : {sha256-file_1}: Received error: HTTP/1.1 500 Internal Server
Error
{date} DEBUG : MKCOL /{webdav_path}/data/52/ HTTP/1.1
{date} DEBUG : HTTP/1.1 405 Unknown Error
{date} DEBUG : DELETE /{webdav_path}/data/52/{sha256-file_2} HTTP/1.1
{date} DEBUG : HTTP/1.1 404 Not Found
{date} DEBUG : {sha256-file_2}: Received error: HTTP/1.1 500 Internal Server
Error
{date} DEBUG : MKCOL /{webdav_path}/data/52/ HTTP/1.1
{date} DEBUG : HTTP/1.1 405 Unknown Error
{date} DEBUG : PUT /{webdav_path}/data/52/{sha256-file_1} HTTP/1.1
{date} DEBUG : HTTP/1.1 500 Internal Server Error
{date} DEBUG : PUT /{webdav_path}/data/52/{sha256-file_2} HTTP/1.1
{date} DEBUG : HTTP/1.1 500 Internal Server Error

(identical config and same rclone version but megacmd 1.4.1 works like a charm)

I don't think that the problem is on my machine but if you have any hint to
better debug this issue will be greatly appreciated.

-- 
You are receiving this mail because:
You are the assignee for the bug.