helpdavfs2 - Support: sr #109626, mount.davfs crashes after...

 
 

sr #109626: mount.davfs crashes after `systemctl start mnt.mount`

Submitted by:  None
Submitted on:  Wed 16 Jan 2019 07:50:58 PM UTC  
 
Category:  None Priority:  5 - Normal
Severity:  3 - Normal Status:  Done
Privacy:  Public Assigned to:  Werner Baumann <wbaumann>
Originator Email:  -email is unavailable- Open/Closed:  Open
Operating System:  None

Add a New Comment (Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

( Jump to the original submission)

Wed 16 Jan 2019 07:50:58 PM UTC, comment #6: 

This item has been reassigned from the project davfs2 bugs tracker to your tracker.

The original report is still available at bugs #55285

Following are the information included in the original report:

[field #0]                  Item ID: 55285

[field #1]                 Group ID: 10199

[field #2]              Open/Closed: Open

[field #3]                 Severity: 3 - Normal

[field #4]                  Privacy: Public

[field #7]                         : Unknown bugs Field Display Type

[field #8]                         : Unknown bugs Field Display Type

[field #9]                 Category: None

[field #10]             Submitted by: None

[field #11]              Assigned to: wbaumann

[field #12]             Submitted on: Wed 26 Dec 2018 03:12:50 PM UTC

[field #13]                  Summary: mount.davfs crashes after `systemctl start mnt.mount`

[field #14]      Original Submission: I have the following entry in my /etc/fstab

https://server.com/remote.php/dav/files/user /mnt davfs defaults,x-systemd.automount 0 0

If I try to mount using systemctl:

sudo systemctl start cloud.mount

I get the following error in `journalctl -xe`

 Process 2995 (mount.davfs) of user 0 dumped core.

Stack trace of thread 2995:
#0  0x00007fee59d16d7f raise (libc.so.6)
#1  0x00007fee59d01672 abort (libc.so.6)
#2  0x0000556e4c72c04a n/a (mount.davfs)
#3  0x0000556e4c72d6fd n/a (mount.davfs)
#4  0x00007fee59d03223 __libc_start_main (libc.so.6)
#5  0x0000556e4c72deae n/a (mount.davfs)

If I can provide more details, please let me know.

[field #16]               Item Group: None

[field #17]                   Status: Need Info

[field #18]        Component Version: None

[field #19]         Operating System: None

[field #20]          Reproducibility: None

[field #21]               Size (loc): None

[field #22]            Fixed Release: None

[field #23]          Planned Release: None

[field #24]                   Effort: 0.00

[field #28]                 Priority: 5 - Normal

[field #31]         Percent Complete: 0%

[field #33]                  Release: None

[field #58]     Custom Select Box #1: None

[field #59]     Custom Select Box #2: None

[field #60]     Custom Select Box #3: None

[field #61]     Custom Select Box #4: None

[field #62]     Custom Select Box #5: None

[field #63]     Custom Select Box #6: None

[field #64]     Custom Select Box #7: None

[field #65]     Custom Select Box #8: None

[field #66]     Custom Select Box #9: None

[field #67]    Custom Select Box #10: None

Werner Baumann <wbaumann>
Project AdministratorIn charge of this item.
Wed 16 Jan 2019 07:50:23 PM UTC, comment #5: 

I will move this item to the support tracker (it is not a davfs2 bug).

uid and gid are about the user that owns the files and the group they belong to.

dav_user and dav_group are about the userid and the group of the davfs2 daemon. They are importont for security.

You will find details in the man pages for mount.davfs and davfs2.conf.

Werner

Werner Baumann <wbaumann>
Project AdministratorIn charge of this item.
Sun 13 Jan 2019 10:00:23 AM UTC, comment #4: 

audit is probably related to SELinux. A ANOM_ABEND message is triggered when a processes ends abnormally [1].

Good point with /etc/davfs2/secrets. Normally I use this file, but for debugging I had removed all the additional configuration including secrets. After I activated the secret for the DAV share, I do not have this error anymore. The automount also works (`cd /mnt` mounts the share). Probably systemctl has problems in forwarding the username-password prompt to the user.

Regarding dav_user+dav_group: I use Archlinux. Davfs logs differentiate between dav_user+dav_group and uid+gid. What is the difference?

Regarding use_proxy: You are right, this is unnecessary—my fault.

Regarding initiating the mounting from the command line: Yes, the following command generates the error log that I have sent:

sudo systemctl start mnt.mount

[1] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/security_guide/sec-audit_record_types

Gökçe <goekce>
Wed 09 Jan 2019 05:32:56 PM UTC, comment #3: 

When davfs2 aborts during startup it sends an error message to the error output. Unfortunately I can't find this message. Instead there is a message from "audit" that I don't understand.

"sudo mount /mnt
... username and password prompt"
You enter username and password on the commandline. How will davfs2 get them when mounted by systemd? Why don't you use the secrets file?

dav_user and dav_group are different from the defaults of the orignal package. If you did not change them then probably your distribution did it. Please tell me where you got davfs2 from.

In the original package the default value of use_proxy is 0. You don't need to set this option.

If you initiate mounting from the command line with systemctl: does it fail without any error message on the command line?

Werner

Werner Baumann <wbaumann>
Project AdministratorIn charge of this item.
Wed 09 Jan 2019 01:46:28 PM UTC, comment #2: 

Werner, thank you for your support.

Manually mounting works:

sudo mount /mnt
... username and password prompt

I attached a more detailed log, where the configuration options are included. In the config file, I only set the following options and leave others default:

use_proxy 0
use_locks 0
debug most

I tried to test the behavior without x-systemd.automount by removing the option and rebooting the system, but my system could not start without an internet connection, because systemctl tried to mount the davfs path during boot.

My second try was by:

sudo systemctl daemon-reload
sudo systemctl start mnt.mount

I got the same error, in the second try without x-systemd.automount

(file #45914)

Gökçe <goekce>
Fri 28 Dec 2018 09:34:03 AM UTC, comment #1: 

What happens when you remove that option "x-systemd.automount" from fstab and mount the resource manually. Please include all messages from davfs2 as well as any configuration options you set and the version of davfs2.

Werner

Werner Baumann <wbaumann>
Project AdministratorIn charge of this item.
Wed 16 Jan 2019 07:50:58 PM UTC, original submission:  

I have the following entry in my /etc/fstab

https://server.com/remote.php/dav/files/user /mnt davfs defaults,x-systemd.automount 0 0

If I try to mount using systemctl:

sudo systemctl start cloud.mount

I get the following error in `journalctl -xe`

 Process 2995 (mount.davfs) of user 0 dumped core.

Stack trace of thread 2995:
#0  0x00007fee59d16d7f raise (libc.so.6)
#1  0x00007fee59d01672 abort (libc.so.6)
#2  0x0000556e4c72c04a n/a (mount.davfs)
#3  0x0000556e4c72d6fd n/a (mount.davfs)
#4  0x00007fee59d03223 __libc_start_main (libc.so.6)
#5  0x0000556e4c72deae n/a (mount.davfs)

If I can provide more details, please let me know.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #45914:  2019-01-09-davfs2.log added by goekce (6KiB - text/x-log)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by goekce (Updated the item)
  • -email is unavailable- added by wbaumann (Posted a comment)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

     

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-01-16 wbaumann StatusNone => Done
        Assigned toNone => wbaumann
    2019-01-16 wbaumann Reassign itemdavfs2, bug #55285 => davfs2, sr #109626

    Back to the top


    Powered by Savane 3.5