Web Dav on CP76 library problem
Hello,
It seems with the recent cPanel 76 update, the web dav implementation was broken. I have tried a few things already such as running upcp, checking permissions, and restarting the cpdavd service. I don't think this is something I can easily fix.
The file does in-fact exist, and permissions seems to be ok.
The exception directory also seems to have appropriate permissions.
Assistance in this issue would be appreciated. Thank you, James Coleman
[2018-11-27 15:39:13 -0600] Starting PID 22554: /usr/local/cpanel/libexec/cpdavd-dormant
PROPFIND: / -> 400 'Bad Request' {Can't locate Cpanel/Exception/CORE.pm in @INC (you may need to install the Cpanel::Exception::CORE module) (@INC contains:) at /usr/local/cpanel/Cpanel/Exception.pm line 63. }The file does in-fact exist, and permissions seems to be ok.
# ls -lah /usr/local/cpanel/Cpanel/Exception/CORE.pm
-rw-r--r-- 1 root root 28K Nov 7 03:45 /usr/local/cpanel/Cpanel/Exception/CORE.pmThe exception directory also seems to have appropriate permissions.
# ls -lah /usr/local/cpanel/Cpanel/
...
drwxr-xr-x 28 root root 8.0K Nov 7 03:45 ExceptionAssistance in this issue would be appreciated. Thank you, James Coleman
-
Hi @James Coleman That error may actually be a red herring from what I've been reading on similar issues. What's the WebDav path you're using? We do have some cases open involving special characters in the path as well as the file names. CPANEL-22710 and CPANEL-22713 Below is a description of both cases: CPANEL-22710: Newlines, and other characters (literally anything except null and '/'), are allowed in file/folder names in Linux. They work perfectly fine on the command line, so long as you are careful to escape things properly. However, I found that making a newline file or folder breaks the file manager and webdav interfaces. Files with newlines cannot be edited or viewed, and you can't change directory into folders with newlines. CPANEL-22713 If a WebDAV path exists with certain iterations of special characters (i.e., ") in a filename under that path, the path can be inaccessible when using a WebDAV client to connect (i.e., Windows network folders). When using OSX's native WebDAV implementation, any file with an offending special character will not appear in the directory when accessed. I have found that accessing an affected path via a browser (Firefox or Chrome) will show the file, but the special character will be replaced with the default '?' symbol due to the character being unknown. --While the second wouldn't produce the errors with the connection you're seeing the first one would. 0 -
Hello, This does not appear to be the case here. I tried a few searches within the directory I'm trying to access, and it does not seem to have any unicode file names. # LC_ALL=C find . -name '*[! -~]*' # LC_ALL=C find . -name '*[![:print:]]*' | cat #
The program I am testing this with is cyberduck, I'm connecting as follows:0 -
Hi @James Coleman The information you're providing is very helpful, thank you - I want to clarify, are you not able to access the directory or you can access it but you get the error when doing so? Thanks! 0 -
In a web browser, I'm able to login fine and see the directory. However, in a WebDAV client such as Mac OS X Finder or CyberDuck, it returns a 400 bad request and logs to cpdavd_error_log with the exception. 0 -
In a web browser, I'm able to login fine and see the directory. However, in a WebDAV client such as Mac OS X Finder or CyberDuck, it returns a 400 bad request and logs to cpdavd_error_log with the exception.
Ok just wanted to make sure the 400 bad request is displaying when attempting to view it. Can you please open a ticket using the link in my signature? I'll also update the ticket with all the data we've collected in this thread once open just reply with the Ticket ID here. I'll update this thread with the resolution once the ticket is resolved. Thanks!0 -
Hello, The ticket id is 10848687 Thank you, 0
Please sign in to leave a comment.
Comments
6 comments