Mailinglist Archive: opensuse-bugs (4297 mails)

< Previous Next >
[Bug 1041125] New: dnsmasq does not start after update with "enable-tftp" option
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Sun, 28 May 2017 08:42:40 +0000
  • Message-id: <bug-1041125-21960@http.bugzilla.suse.com/>
http://bugzilla.suse.com/show_bug.cgi?id=1041125


Bug ID: 1041125
Summary: dnsmasq does not start after update with "enable-tftp"
option
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.2
Hardware: Other
OS: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Basesystem
Assignee: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
Reporter: seife@xxxxxxxxxxxxxxxxxxxx
QA Contact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---

I got the following configuration:
server:/srv/tftpboot # grep dnsmasq.d /etc/dnsmasq.conf
conf-dir=/etc/dnsmasq.d

and in /etc/dnsmasq.d/tftp:
/etc/dnsmasq.d/tftp:enable-tftp
/etc/dnsmasq.d/tftp:tftp-root=/srv/tftpboot

This causes dnsmasq to refuse restart after every update:

20170528-10:31:44.9 systemd[1]: Starting DNS caching server....
20170528-10:31:44.9 dnsmasq[21075]: dnsmasq: syntax check OK.
20170528-10:31:44.9 systemd[1]: Started DNS caching server..
20170528-10:31:44.9 dnsmasq[21079]: TFTP directory /srv/tftpboot inaccessible:
Permission denied
20170528-10:31:44.9 systemd[1]: dnsmasq.service: Main process exited,
code=exited, status=3/NOTIMPLEMENTED
20170528-10:31:44.9 dnsmasq[21079]: FAILED to start up
20170528-10:31:44.9 systemd[1]: dnsmasq.service: Unit entered failed state.
20170528-10:31:44.9 systemd[1]: dnsmasq.service: Failed with result
'exit-code'.
20170528-10:32:49.6 systemd[1]: Stopped DNS caching server..

The reason is this:

server:/srv/tftpboot # rpm -qlv dnsmasq |grep tftpboot
drwxr-x--- 2 tftp tftp 0 Mai 16 12:06
/srv/tftpboot

Even though dnsmasq user is in group tftp:
server:/srv/tftpboot # id dnsmasq
uid=106(dnsmasq) gid=116(tftp) groups=116(tftp)

this seems to be not enough.
After every update I have to chmod 755 /srv/tftpboot to get dnsmasq starting up
again.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
This Thread
  • No further messages