Il 22/03/2015 21:21, Colin Close ha scritto:
Luca,
Cracked it. There's a typo in the EnvironmentFile= entry in all the samba
related systemd service files. There's a stray '-'
Best,
Colin
And is not the only one:
[ilprof@Omvvboxxx system]$ grep "\=\-" *.service
alsa-restore.service:ExecStart=-/usr/sbin/alsactl restore
alsa-state.service:ExecStart=-/usr/sbin/alsactl -s -n 19 -c rdaemon
alsa-state.service:ExecStop=-/usr/sbin/alsactl -s rkill save_and_quit
[email protected]:ExecStart=-/sbin/agetty --noclear %I
chronyd.service:EnvironmentFile=-/etc/sysconfig/chronyd
console-getty.service:ExecStart=-/sbin/agetty --noclear -s console
115200,38400,9600
console-shell.service:ExecStart=-/sbin/sulogin
console-shell.service:ExecStopPost=-/bin/systemctl poweroff
dbus.service:OOMScoreAdjust=-900
dm-event.service:OOMScoreAdjust=-1000
dracut-cmdline.service:ExecStart=-/bin/dracut-cmdline
dracut-initqueue.service:ExecStart=-/bin/dracut-initqueue
dracut-mount.service:ExecStart=-/bin/dracut-mount
dracut-pre-mount.service:ExecStart=-/bin/dracut-pre-mount
dracut-pre-pivot.service:ExecStart=-/bin/dracut-pre-pivot
dracut-pre-trigger.service:ExecStart=-/bin/dracut-pre-trigger
dracut-pre-udev.service:ExecStart=-/bin/dracut-pre-udev
emergency.service:ExecStartPre=-/bin/plymouth quit
emergency.service:ExecStartPre=-/bin/echo -e 'Welcome to emergency mode!
After logging in, type "journalctl -xb" to view\\nsystem logs,
"systemctl reboot" to reboot, "systemctl default" or ^D to\\ntry again
to boot into default mode.'
emergency.service:ExecStart=-/bin/sh -c "/sbin/sulogin; /bin/systemctl
--fail --no-block default"
fedora-autorelabel-mark.service:ExecStart=-/bin/touch /.autorelabel
firewalld.service:EnvironmentFile=-/etc/sysconfig/firewalld
[email protected]:ExecStart=-/sbin/agetty --noclear %I
initrd-parse-etc.service:ExecStart=-/bin/systemctl --no-block start
initrd-fs.target
initrd-udevadm-cleanup-db.service:ExecStart=-/bin/udevadm info --cleanup-db
lm_sensors.service:ExecStart=-/sbin/modprobe -qab $BUS_MODULES
$HWMON_MODULES
lm_sensors.service:ExecStop=-/sbin/modprobe -qabr $BUS_MODULES
$HWMON_MODULES
mandriva-everytime.service:ExecStart=-/etc/init.d/mandrake_everytime
mandriva-save-dmesg.service:ExecStart=-/lib/systemd/mandriva-save-dmesg
mdadm.service:EnvironmentFile=-/etc/sysconfig/mdmonitor
mdmonitor.service:EnvironmentFile=-/etc/sysconfig/mdmonitor
messagebus.service:OOMScoreAdjust=-900
nfs-blkmap.service:EnvironmentFile=-/etc/sysconfig/nfs
nfs-idmap.service:EnvironmentFile=-/etc/sysconfig/nfs
nfs-lock.service:EnvironmentFile=-/etc/sysconfig/nfs
nfs-lock.service:ExecStopPost=-/sbin/sysctl -w fs.nfs.nlm_tcpport=0
fs.nfs.nlm_udpport=0
nfs-mountd.service:EnvironmentFile=-/etc/sysconfig/nfs
nfs-rquotad.service:EnvironmentFile=-/etc/sysconfig/nfs
nfs-rquotad.service:ExecStart=-/usr/sbin/rpc.rquotad $RPCRQUOTADOPTS
nfs-secure-server.service:EnvironmentFile=-/etc/sysconfig/nfs
nfs-secure.service:EnvironmentFile=-/etc/sysconfig/nfs
nfs-server.service:EnvironmentFile=-/etc/sysconfig/nfs
nfs-server.service:ExecStartPost=-/usr/lib/nfs-utils/scripts/nfs-server.postconfig
nmb.service:EnvironmentFile=-/etc/sysconfig/samba
nscd.service:EnvironmentFile=-/etc/sysconfig/nscd
plymouth-halt.service:ExecStartPost=-/bin/plymouth show-splash
plymouth-kexec.service:ExecStartPost=-/bin/plymouth show-splash
plymouth-poweroff.service:ExecStartPost=-/bin/plymouth show-splash
plymouth-quit.service:ExecStart=-/bin/plymouth quit
plymouth-quit-wait.service:ExecStart=-/bin/plymouth --wait
plymouth-read-write.service:ExecStart=-/bin/plymouth update-root-fs
--read-write
plymouth-reboot.service:ExecStartPost=-/bin/plymouth show-splash
plymouth-start.service:ExecStartPost=-/bin/plymouth show-splash
plymouth-switch-root.service:ExecStart=-/bin/plymouth update-root-fs
--new-root-dir=/sysroot
postfix.service:EnvironmentFile=-/etc/sysconfig/network
postfix.service:ExecStartPre=-/etc/postfix/aliasesdb
postfix.service:ExecStartPre=-/etc/postfix/chroot-update
rescue.service:ExecStartPre=-/bin/plymouth quit
rescue.service:ExecStartPre=-/bin/echo -e 'Welcome to emergency mode!
After logging in, type "journalctl -xb" to view\\nsystem logs,
"systemctl reboot" to reboot, "systemctl default" or ^D to\\nboot into
default mode.'
rescue.service:ExecStart=-/bin/sh -c "/sbin/sulogin; /bin/systemctl
--fail --no-block default"
samba.service:EnvironmentFile=-/etc/sysconfig/samba
sensord.service:EnvironmentFile=-/etc/sysconfig/sensord
[email protected]:ExecStart=-/sbin/agetty --keep-baud %I
115200,38400,9600
smb.service:EnvironmentFile=-/etc/sysconfig/samba
[email protected]:EnvironmentFile=-/etc/sysconfig/sshd
[email protected]:ExecStart=-/usr/sbin/sshd -i $OPTIONS
systemd-ask-password-wall.service:ExecStartPre=-/bin/systemctl stop
systemd-ask-password-console.path systemd-ask-password-console.service
systemd-ask-password-plymouth.path systemd-ask-password-plymouth.service
systemd-udevd.service:OOMScoreAdjust=-1000
udev.service:OOMScoreAdjust=-1000
[email protected]:ExecStart=-/lib/systemd/systemd --user
winbind.service:EnvironmentFile=-/etc/sysconfig/samba
wpa_supplicant.service:EnvironmentFile=-/etc/sysconfig/wpa_supplicant.conf
On Sunday 22 Mar 2015 20:11:38 Colin Close wrote:
Hi Luca,
Some progress; _TPG hinted that maybe the options are not set correctly in
/etc/sysconfig/samba. I took a look and they are set correctly. So I tried a
test I hardcoded the -D option in the three systemd files that control the
three services. Lo and behold samba starts up fine from boot. So what is
happening is that the variables needed by systemd are not being exported from
/etc/sysconfig/samba are not being made available to the systemd process. What
aspect of the boot process deals with this I have no idea but it would appear
that this is the source of the issue.
Best,
Colin
On Sunday 22 Mar 2015 16:44:58 luca pedrielli wrote:
Hi Colin,
but with the same systemd, samba 4.1.6-1.3 works great
Il 22/03/2015 14:48, Colin Close ha scritto:
Luca,
This seems to confirm a systemd problem as you were able to start with the -D
option without issue.
The extra rpms are there only because I was lazy and did urpmi *.rpm from my
build directory. :)
Best,
Colin
On Saturday 21 Mar 2015 19:58:20 luca pedrielli wrote:
Hi Colin,
yes is present
cd /run
[ilprof@Omvvboxxx run]$ ls
avahi-daemon/ hplip/ log/ openvpn/ systemd/ udev/ utmp
console/ initramfs/ mdadm/ resolvconf/ tmpfiles.d/ udisks2/ uuidd/
dhclient/ lock/ mount/ samba/ tuned/ user/ vnstat/
[ilprof@Omvvboxxx run]$ rpm -qa | grep samba
lib64samba-util0-4.1.17-2-omv2014.0.x86_64
lib64samba-hostconfig0-4.1.17-2-omv2014.0.x86_64
lib64samba-credentials0-4.1.17-2-omv2014.0.x86_64
samba-libs-4.1.17-2-omv2014.0.x86_64
lib64samba-policy0-4.1.17-2-omv2014.0.x86_64
samba-python-4.1.17-2-omv2014.0.x86_64
samba-common-4.1.17-2-omv2014.0.x86_64
samba-client-4.1.17-2-omv2014.0.x86_64
samba-server-4.1.17-2-omv2014.0.x86_64
samba-winbind-4.1.17-2-omv2014.0.x86_64
I have no
samba-pidl-4.1.17-2-omv2014.0.x86_64
samba-test-4.1.17-2-omv2014.0.x86_64
Il 21/03/2015 19:42, Colin Close ha scritto:
Luca,
It's odd it is working for me, do you have a directory /run/samba?
[root@localhost /]# rpm -qa | grep samba
lib64samba-util0-4.1.17-2-omv2014.0.x86_64
lib64samba-hostconfig0-4.1.17-2-omv2014.0.x86_64
lib64samba-credentials0-4.1.17-2-omv2014.0.x86_64
samba-libs-4.1.17-2-omv2014.0.x86_64
lib64samba-policy0-4.1.17-2-omv2014.0.x86_64
samba-python-4.1.17-2-omv2014.0.x86_64
samba-common-4.1.17-2-omv2014.0.x86_64
samba-server-4.1.17-2-omv2014.0.x86_64
samba-client-4.1.17-2-omv2014.0.x86_64
samba-winbind-4.1.17-2-omv2014.0.x86_64
samba-pidl-4.1.17-2-omv2014.0.x86_64
samba-test-4.1.17-2-omv2014.0.x86_64
[root@localhost /]# ps -e | grep mb
3997 ? 00:00:00 nmbd
4055 ? 00:00:04 smbd
4058 ? 00:00:00 smbd
Can you start it by hand using the -D option?
# /usr/sbin/smbd -D
[root@Omvvboxxx run]# ps -ef | grep smb
root 4101 1 0 19:57 ? 00:00:00 /usr/sbin/smbd -D
root 4102 4101 0 19:57 ? 00:00:00 /usr/sbin/smbd -D
root 4104 4067 0 19:57 pts/2 00:00:00 grep --color smb
Best,
Colin
On Friday 20 Mar 2015 17:00:37 luca pedrielli wrote:
Hi Colin,
considers that in cooker samba 4.1.17-1 has some problems:
https://issues.openmandriva.org/show_bug.cgi?id=1089#c2
Luca.
Il 20/03/2015 16:43, Colin Close ha scritto:
It is proving a long winded business to backport 4.17.1 which has the fix to
2014.1 it will take a while longer but is is in progress.
Best,
Colin
On Wednesday 25 Feb 2015 12:13:12 Blackcrack wrote:
Hy,
we have an Security issue in Samba
https://securityblog.redhat.com/tag/smbd/
https://securityblog.redhat.com/feed/
http://planet.fedoraproject.org/security/
https://www.samba.org/samba/history/security.html
https://git.samba.org/?p=samba.git;a=patch;h=8eb981c90a6094b15d4b71cc14fee4f23c713cf8
please update 2014&2014
because 2014 should be save also..
best regards
Blacky
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
--
Saluti, Luca Pedrielli
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
