[opensuse] smbd errors

newer
[opensuse] Obscure http -> https...

older
[opensuse] Email error Seamonkey...

lynn

11 Jan 2014 11 Jan '14

19:45

Hi everyone. The latest zypper up has thrown up this more errors when starting smbd. Even with apparmor disabled we still get: smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled) Active: active (running) since Sat 2014-01-11 20:38:20 CET; 35s ago Process: 6674 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=0/SUCCESS) Main PID: 6675 (smbd) CGroup: /system.slice/smb.service ├─6675 /usr/sbin/smbd └─6678 /usr/sbin/smbd Jan 11 20:38:19 altea smbd[6674]: [2014/01/11 20:38:19.962335, 0] ../source3/smbd/server.c:1278(main) Jan 11 20:38:19 altea smbd[6674]: standard input is not a socket, assuming -D option Jan 11 20:38:19 altea systemd[1]: PID file /run/samba/smbd.pid not readable (yet?) after start. Jan 11 20:38:20 altea systemd[1]: Started Samba SMB Daemon. Please can we have an error free smbd? Details. This is a fileserver in a AD domain. Does anyone have it working error free in this situation? I believe SuSE have this set up for testing sles. Anyone there read this list? Thanks. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Show replies by date

John Andersen

11 Jan 11 Jan

20:55

On 01/11/2014 11:45 AM, lynn wrote:

...

Hi everyone. The latest zypper up has thrown up this more errors when starting smbd. Even with apparmor disabled we still get:

smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled) Active: active (running) since Sat 2014-01-11 20:38:20 CET; 35s ago Process: 6674 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=0/SUCCESS) Main PID: 6675 (smbd) CGroup: /system.slice/smb.service ├─6675 /usr/sbin/smbd └─6678 /usr/sbin/smbd

Jan 11 20:38:19 altea smbd[6674]: [2014/01/11 20:38:19.962335, 0] ../source3/smbd/server.c:1278(main) Jan 11 20:38:19 altea smbd[6674]: standard input is not a socket, assuming -D option Jan 11 20:38:19 altea systemd[1]: PID file /run/samba/smbd.pid not readable (yet?) after start. Jan 11 20:38:20 altea systemd[1]: Started Samba SMB Daemon.

Please can we have an error free smbd?

Details. This is a fileserver in a AD domain. Does anyone have it working error free in this situation? I believe SuSE have this set up for testing sles. Anyone there read this list? Thanks. L x

Does it work? Is smbd started? Some of these are just info and not meant to be seen. Seems systemd is a bit impatient waiting for the pid, or your smb.conf is kicking out errors and failing to run. -- Explain again the part about rm -rf / -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

lynn

12 Jan 12 Jan

13:42

On Sat, 2014-01-11 at 12:55 -0800, John Andersen wrote:

...

On 01/11/2014 11:45 AM, lynn wrote:

...
Hi everyone. The latest zypper up has thrown up this more errors when starting smbd. Even with apparmor disabled we still get:

smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled) Active: active (running) since Sat 2014-01-11 20:38:20 CET; 35s ago Process: 6674 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=0/SUCCESS) Main PID: 6675 (smbd) CGroup: /system.slice/smb.service ├─6675 /usr/sbin/smbd └─6678 /usr/sbin/smbd

Esos aparecen en rojo. These appear in red: <red>

...

...
Jan 11 20:38:19 altea smbd[6674]: [2014/01/11 20:38:19.962335, 0] ../source3/smbd/server.c:1278(main) Jan 11 20:38:19 altea smbd[6674]: standard input is not a socket, assuming -D option Jan 11 20:38:19 altea systemd[1]: PID file /run/samba/smbd.pid not readable (yet?) after start.

...

...
Jan 11 20:38:20 altea systemd[1]: Started Samba SMB Daemon.

Please can we have an error free smbd?

Details. This is a fileserver in a AD domain. Does anyone have it working error free in this situation? I believe SuSE have this set up for testing sles. Anyone there read this list? Thanks. L x

Does it work? Is smbd started?

Hi Yes, it works and smbd is started. However my boss doesn't like error messages. Especially when they are in red as outlined above. Before the latest samba update, it was starting cleanly. I'd like to be able to switch to openSUSE file servers and have an easy upgrade via rpm. Currently I have to build samba from source.

...

Some of these are just info and not meant to be seen. Seems systemd is a bit impatient waiting for the pid, or your smb.conf is kicking out errors and failing to run.

OK. But still. I wonder whether it's possible for us to have: - an apparmor profile for smbd in AD - a clean startup log I'm almost certain that SUSE have this working. If they could share it with us, that would be great. Thanks, L x

...

-- Explain again the part about rm -rf /

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

James Knott

15:12

lynn wrote:

...

Yes, it works and smbd is started. However my boss doesn't like error messages. Especially when they are in red as outlined above.

Before the latest samba update, it was starting cleanly.

With some of the problems I've seen in openSUSE, I often wonder if anyone bothers to test to make things still work, after making changes. Years ago, I used to work at IBM Canada, on the team that built standard desktop systems for IBM employees. I would have been fired, had I released things that were as broken as this. Back then, I supported OS/2 and several apps on OS/2 and Windows. Every time a change was made, I had to go through my testing to ensure everything still worked properly. If it didn't, it wasn't released. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

lynn

13 Jan 13 Jan

12:17

On Sun, 2014-01-12 at 10:12 -0500, James Knott wrote:

...

lynn wrote:

...
Yes, it works and smbd is started. However my boss doesn't like error messages. Especially when they are in red as outlined above.

Before the latest samba update, it was starting cleanly.

With some of the problems I've seen in openSUSE, I often wonder if anyone bothers to test to make things still work, after making changes.

Years ago, I used to work at IBM Canada, on the team that built standard desktop systems for IBM employees. I would have been fired, had I released things that were as broken as this. Back then, I supported OS/2 and several apps on OS/2 and Windows. Every time a change was made, I had to go through my testing to ensure everything still worked properly. If it didn't, it wasn't released.

Thanks for your interest. I know how you feel. I'm not allowed to put anything into production, even a script which only I am going to use, unless I can show it will not affect the system, or (and of course far more importantly) the people who employ me. However you at IBM and I currently are paid to make damn sure it's error free. It make it hard for me to level blame at our volunteer openSUSE at openSUSE. Having said that, I'm very surprised that the the (paid) Samba developers at SuSE have let Samba slip to it's current state. A few years ago, SuSE and openSUSE were the distro of choice for reliable servers in windows domains. OK, currently, it works, but every new release and upgrade brings with it new errors. Conclusion: It is quicker for me to build Samba4 from source than go to bugzilla and wait for openSUSE to get it error free. I shall however maintain AD + cifs boxes in the lab to test anything the devs would like to throw at me that we may get it error free. Thanks, L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Lars Müller

13:39

On Mon, Jan 13, 2014 at 01:17:19PM +0100, lynn wrote: [ 8< ]

...

Conclusion: It is quicker for me to build Samba4 from source than go to bugzilla and wait for openSUSE to get it error free. I shall however maintain AD + cifs boxes in the lab to test anything the devs would like to throw at me that we may get it error free.

Please file bug reports if you think the Samba package we offer for openSUSE are broken. See bnc#857454 for the particular issue. What you see in the log is a warning. It's an ongoing discussion if we set -D in /etc/sysconfig/samba or if we have to modify the debug level from 0 to 3 or 5 for example. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

lynn

14:10

On Mon, 2014-01-13 at 14:39 +0100, Lars Müller wrote:

...

On Mon, Jan 13, 2014 at 01:17:19PM +0100, lynn wrote: [ 8< ]

...
Conclusion: It is quicker for me to build Samba4 from source than go to bugzilla and wait for openSUSE to get it error free. I shall however maintain AD + cifs boxes in the lab to test anything the devs would like to throw at me that we may get it error free.

Please file bug reports if you think the Samba package we offer for openSUSE are broken.

See bnc#857454 for the particular issue.

What you see in the log is a warning. It's an ongoing discussion if we set -D in /etc/sysconfig/samba or if we have to modify the debug level from 0 to 3 or 5 for example.

Cheers,

Lars

Lars OK. So the blame passes to systemd messages being based on the debug level set in smb.conf? So why then, after the latest update do we now have warnings when before we didn't? Have you tested it in an AD domain? If so, could you please share your apparmor profile? I know this isn't easy, so thanks for your time. Cheers, Steve -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Lars Müller

14:45

On Mon, Jan 13, 2014 at 03:10:15PM +0100, lynn wrote:

...

On Mon, 2014-01-13 at 14:39 +0100, Lars Müller wrote:

...
On Mon, Jan 13, 2014 at 01:17:19PM +0100, lynn wrote: [ 8< ]

...
Conclusion: It is quicker for me to build Samba4 from source than go to bugzilla and wait for openSUSE to get it error free. I shall however maintain AD + cifs boxes in the lab to test anything the devs would like to throw at me that we may get it error free.

Please file bug reports if you think the Samba package we offer for openSUSE are broken.

See bnc#857454 for the particular issue.

What you see in the log is a warning. It's an ongoing discussion if we set -D in /etc/sysconfig/samba or if we have to modify the debug level from 0 to 3 or 5 for example.

OK. So the blame passes to systemd messages being based on the debug level set in smb.conf?

These aren't systemd messages. These are Samba daemon startup messages. They're at the moment at level 0 and therefore it's not possible to suppress them. The log/ debug level of this particular statement should better be 3 or 5.

...

So why then, after the latest update do we now have warnings when before we didn't?

Cause before there had not been native systemd support. And in the old init script files we started the daemons with the option -D by default.

...

Have you tested it in an AD domain? If so, could you please share your apparmor profile?

Regarding AppArmor see bnc#856651 If this still isn't fixed you have to consider to file a bug report. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

lynn

15:41

On Mon, 2014-01-13 at 15:45 +0100, Lars Müller wrote:

...

On Mon, Jan 13, 2014 at 03:10:15PM +0100, lynn wrote:

...
On Mon, 2014-01-13 at 14:39 +0100, Lars Müller wrote:

...
On Mon, Jan 13, 2014 at 01:17:19PM +0100, lynn wrote: [ 8< ]

...
Conclusion: It is quicker for me to build Samba4 from source than go to bugzilla and wait for openSUSE to get it error free. I shall however maintain AD + cifs boxes in the lab to test anything the devs would like to throw at me that we may get it error free.

Please file bug reports if you think the Samba package we offer for openSUSE are broken.

See bnc#857454 for the particular issue.

What you see in the log is a warning. It's an ongoing discussion if we set -D in /etc/sysconfig/samba or if we have to modify the debug level from 0 to 3 or 5 for example.

OK. So the blame passes to systemd messages being based on the debug level set in smb.conf?

These aren't systemd messages. These are Samba daemon startup messages. They're at the moment at level 0 and therefore it's not possible to suppress them. The log/ debug level of this particular statement should better be 3 or 5.

Lars, they weren't there before the last update. What have you changed to make them appear now?

...

...
So why then, after the latest update do we now have warnings when before we didn't?

Cause before there had not been native systemd support. And in the old init script files we started the daemons with the option -D by default.

...
Have you tested it in an AD domain? If so, could you please share your apparmor profile?

Regarding AppArmor see bnc#856651 If this still isn't fixed you have to consider to file a bug report.

I am simply asking whether you have a working apparmor profile against AD. This involves kerberos too of course, not just the pid in 856651. If you are not allowed to share it or do not have facilities to test it then fine. Just tell us! Thanks L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Lars Müller

16:05

On Mon, Jan 13, 2014 at 04:41:22PM +0100, lynn wrote:

...

On Mon, 2014-01-13 at 15:45 +0100, Lars Müller wrote: [ 8< ]

...
Regarding AppArmor see bnc#856651 If this still isn't fixed you have to consider to file a bug report.

I am simply asking whether you have a working apparmor profile against AD. This involves kerberos too of course, not just the pid in 856651. If you are not allowed to share it or do not have facilities to test it then fine. Just tell us!

If you still have trouble with openSUSE 13.1, Samba and AppArmor please be this nice to file a defect report against bugzilla. Else Christian Boltz as the AppArmor maintainer will not be able to enhance the profiles of the Samba daemons. It's up to you to file such a report. Only then the openSUSE project is able to document the defect and to track the resolution too. It doens't help the openSUSE community if I provide you a working AppArmor profile. Report the bug ID back to this thread, please. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

James Knott

12 Jan 12 Jan

15:01

lynn wrote:

...

Jan 11 20:38:19 altea smbd[6674]: [2014/01/11 20:38:19.962335, 0] ../source3/smbd/server.c:1278(main) Jan 11 20:38:19 altea smbd[6674]: standard input is not a socket, assuming -D option Jan 11 20:38:19 altea systemd[1]: PID file /run/samba/smbd.pid not readable (yet?) after start. Jan 11 20:38:20 altea systemd[1]: Started Samba SMB Daemon.

I'm also getting this -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Mariusz Fik

15 Jan 15 Jan

12:40

Dnia sobota, 11 stycznia 2014 20:45:49 lynn pisze:

...

Hi everyone. The latest zypper up has thrown up this more errors when starting smbd. Even with apparmor disabled we still get:

smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled) Active: active (running) since Sat 2014-01-11 20:38:20 CET; 35s ago Process: 6674 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=0/SUCCESS) Main PID: 6675 (smbd) CGroup: /system.slice/smb.service ├─6675 /usr/sbin/smbd └─6678 /usr/sbin/smbd

Jan 11 20:38:19 altea smbd[6674]: [2014/01/11 20:38:19.962335, 0] ../source3/smbd/server.c:1278(main) Jan 11 20:38:19 altea smbd[6674]: standard input is not a socket, assuming -D option Jan 11 20:38:19 altea systemd[1]: PID file /run/samba/smbd.pid not readable (yet?) after start. Jan 11 20:38:20 altea systemd[1]: Started Samba SMB Daemon.

This is known issue, bnc#856651. Fix is posted in comment #4: https://bugzilla.novell.com/show_bug.cgi?id=856651#c4 -- Pozdrawiam / Best regards, Mariusz Fik openSUSE Community Member GPG: 5FCE 7241 B3B9 32FD 455B C30E 42D6 6C88 9E83 7C3D

lynn

16 Jan 16 Jan

16:13

On Wed, 2014-01-15 at 13:40 +0100, Mariusz Fik wrote:

...

Dnia sobota, 11 stycznia 2014 20:45:49 lynn pisze:

...
Hi everyone. The latest zypper up has thrown up this more errors when starting smbd. Even with apparmor disabled we still get:

smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled) Active: active (running) since Sat 2014-01-11 20:38:20 CET; 35s ago Process: 6674 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=0/SUCCESS) Main PID: 6675 (smbd) CGroup: /system.slice/smb.service ├─6675 /usr/sbin/smbd └─6678 /usr/sbin/smbd

Jan 11 20:38:19 altea smbd[6674]: [2014/01/11 20:38:19.962335, 0] ../source3/smbd/server.c:1278(main) Jan 11 20:38:19 altea smbd[6674]: standard input is not a socket, assuming -D option Jan 11 20:38:19 altea systemd[1]: PID file /run/samba/smbd.pid not readable (yet?) after start. Jan 11 20:38:20 altea systemd[1]: Started Samba SMB Daemon.

This is known issue, bnc#856651. Fix is posted in comment #4: https://bugzilla.novell.com/show_bug.cgi?id=856651#c4

Unfortunately, it doesn't help and introduces another error: 1. with apparmor: systemctl status smb -l smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled) Active: active (running) since Thu 2014-01-16 17:07:53 CET; 7s ago Process: 1780 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=0/SUCCESS) Main PID: 1781 (smbd) CGroup: /system.slice/smb.service ├─1781 /usr/sbin/smbd └─1784 /usr/sbin/smbd Jan 16 17:07:53 altea smbd[1780]: [2014/01/16 17:07:53.160551, 0] ../source3/smbd/server.c:1278(main) Jan 16 17:07:53 altea smbd[1780]: standard input is not a socket, assuming -D option Jan 16 17:07:53 altea systemd[1]: Started Samba SMB Daemon. Jan 16 17:07:56 altea smbd[1781]: [2014/01/16 17:07:56.385087, 0] ../source3/printing/nt_printing.c:164(nt_printing_init) Jan 16 17:07:56 altea smbd[1781]: nt_printing_init: error checking published printers: WERR_ACCESS_DENIED 2. without systemctl status smb -l smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled) Active: active (running) since Thu 2014-01-16 17:12:56 CET; 2s ago Process: 1907 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=0/SUCCESS) Main PID: 1908 (smbd) CGroup: /system.slice/smb.service └─1908 /usr/sbin/smbd Jan 16 17:12:56 altea systemd[1]: Starting Samba SMB Daemon... Jan 16 17:12:56 altea smbd[1907]: [2014/01/16 17:12:56.254332, 0] ../source3/smbd/server.c:1278(main) Jan 16 17:12:56 altea smbd[1907]: standard input is not a socket, assuming -D option Jan 16 17:12:56 altea systemd[1]: PID file /run/samba/smbd.pid not readable (yet?) after start. Jan 16 17:12:56 altea systemd[1]: Started Samba SMB Daemon. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Patrick Shanahan

16:29

* lynn [01-16-14 11:16]:

...

On Wed, 2014-01-15 at 13:40 +0100, Mariusz Fik wrote:

...
Dnia sobota, 11 stycznia 2014 20:45:49 lynn pisze:

...
Hi everyone. The latest zypper up has thrown up this more errors when starting smbd. Even with apparmor disabled we still get: [...] This is known issue, bnc#856651. Fix is posted in comment #4: https://bugzilla.novell.com/show_bug.cgi?id=856651#c4

Unfortunately, it doesn't help and introduces another error:

1. with apparmor: [...] Jan 16 17:12:56 altea systemd[1]: Starting Samba SMB Daemon... Jan 16 17:12:56 altea smbd[1907]: [2014/01/16 17:12:56.254332, 0] ../source3/smbd/server.c:1278(main) Jan 16 17:12:56 altea smbd[1907]: standard input is not a socket, assuming -D option Jan 16 17:12:56 altea systemd[1]: PID file /run/samba/smbd.pid not readable (yet?) after start. Jan 16 17:12:56 altea systemd[1]: Started Samba SMB Daemon.

I am having similar probs: 10:57 wahoo: ~ # journalctl -xn -- Logs begin at Thu 2014-01-09 21:30:20 EST, end at Thu 2014-01-16 -- 10:57:11 EST. -- Jan 16 10:56:02 wahoo smbd[22999]: standard input is not a socket, assuming -D option Jan 16 10:56:02 wahoo smbd[23000]: [2014/01/16 10:56:02.711245, 0] ../lib/util/pidfile.c:117(pidfile_create) Jan 16 10:56:02 wahoo smbd[23000]: ERROR: can't open /var/run/samba/smbd.pid: Error was No such file or directory Jan 16 10:56:02 wahoo kernel: type=1400 audit(1389887762.710:43): apparmor="DENIED" operation="mkdir" parent=1 profile="/usr/sbin/smbd" Jan 16 10:56:02 wahoo systemd[1]: PID file /run/samba/smbd.pid not readable (yet?) after start. Jan 16 10:56:02 wahoo systemd[1]: Failed to start Samba SMB Daemon. -- Subject: Unit smb.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: -- http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40... -- -- Unit smb.service has failed. -- -- The result is failed. Jan 16 10:56:02 wahoo systemd[1]: Unit smb.service entered failed state. Jan 16 10:56:58 wahoo kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:04:5a:55:39:c8:c0:c1:c0:b4:ea:1e:08:00 SRC=192.168.1.1 DST=192.168. Jan 16 10:56:58 wahoo kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:04:5a:55:39:c8:c0:c1:c0:b4:ea:1e:08:00 SRC=192.168.1.1 DST=192.168. Jan 16 10:57:11 wahoo systemd[1]: [/usr/lib/systemd/system/klog.service:26] Unknown lvalue 'Names' in section 'Unit' -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Lars Müller

17:13

On Thu, Jan 16, 2014 at 11:29:32AM -0500, Patrick Shanahan wrote:

...

* lynn [01-16-14 11:16]:

...
On Wed, 2014-01-15 at 13:40 +0100, Mariusz Fik wrote:

...
Dnia sobota, 11 stycznia 2014 20:45:49 lynn pisze:

...
Hi everyone. The latest zypper up has thrown up this more errors when starting smbd. Even with apparmor disabled we still get: [...] This is known issue, bnc#856651. Fix is posted in comment #4: https://bugzilla.novell.com/show_bug.cgi?id=856651#c4

Unfortunately, it doesn't help and introduces another error:

These are two independent issues. Only the access limiting AppArmor profile lead to an error. The 'standard input is not a socket, assuming -D option' is a warning only. It was reported as 857454 to bnc. As a side effect we'll get a clean /etc/sysconfig/samba prepared with the help of a rpm macro (fillup_only) as soon as we published 4.1.3 or 4.1.4 as an official update for openSUSE 13.1 Further testing of the package from the openSUSE Build Service repository network:samba:STABLE is welcome. But you have to have bnc 857454 (standard input is not a socket, assuming -D option) and 856651 in mind.

...

...
1. with apparmor: [...] Jan 16 17:12:56 altea systemd[1]: Starting Samba SMB Daemon... Jan 16 17:12:56 altea smbd[1907]: [2014/01/16 17:12:56.254332, 0] ../source3/smbd/server.c:1278(main) Jan 16 17:12:56 altea smbd[1907]: standard input is not a socket, assuming -D option Jan 16 17:12:56 altea systemd[1]: PID file /run/samba/smbd.pid not readable (yet?) after start. Jan 16 17:12:56 altea systemd[1]: Started Samba SMB Daemon.

I am having similar probs:

10:57 wahoo: ~ # journalctl -xn -- Logs begin at Thu 2014-01-09 21:30:20 EST, end at Thu 2014-01-16 -- 10:57:11 EST. -- Jan 16 10:56:02 wahoo smbd[22999]: standard input is not a socket, assuming -D option

As written before here, this is informational only. We'll either set -D for {NMB,SMB,WINDIND}DOPTIONS in /etc/sysconfig/samba or we modify the log level for 0 to 3 or 5. That's not yet decided.

...

Jan 16 10:56:02 wahoo smbd[23000]: [2014/01/16 10:56:02.711245, 0] ../lib/util/pidfile.c:117(pidfile_create)

That's tracked by bnc#856651 see in particular https://bugzilla.novell.com/show_bug.cgi?id=856651#c4 if you like to get this solved immediately. This fix isn't yet published. Feel free to add your comment as Mariusz did yesterday. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

Patrick Shanahan

19:01

* Lars Müller [01-16-14 12:16]:

...

On Thu, Jan 16, 2014 at 11:29:32AM -0500, Patrick Shanahan wrote:

...
I am having similar probs:

10:57 wahoo: ~ # journalctl -xn -- Logs begin at Thu 2014-01-09 21:30:20 EST, end at Thu 2014-01-16 -- 10:57:11 EST. -- Jan 16 10:56:02 wahoo smbd[22999]: standard input is not a socket, assuming -D option

As written before here, this is informational only. We'll either set -D for {NMB,SMB,WINDIND}DOPTIONS in /etc/sysconfig/samba or we modify the log level for 0 to 3 or 5. That's not yet decided.

...
Jan 16 10:56:02 wahoo smbd[23000]: [2014/01/16 10:56:02.711245, 0] ../lib/util/pidfile.c:117(pidfile_create)

That's tracked by bnc#856651 see in particular https://bugzilla.novell.com/show_bug.cgi?id=856651#c4 if you like to get this solved immediately. This fix isn't yet published. Feel free to add your comment as Mariusz did yesterday.

added the line, /{,var/}run/samba/ w, in the position indicated in the bug report 856651 but still fails: 13:45 wahoo: ~ # systemctl status smb smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled) Active: failed (Result: resources) since Thu 2014-01-16 13:44:45 EST; 43s ago Process: 25687 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=0/SUCCESS) Jan 16 13:44:45 wahoo systemd[1]: PID file /run/samba/smbd.pid not readable (yet?) after start. Jan 16 13:44:45 wahoo systemd[1]: smb.service never wrote its PID file. Failing. Jan 16 13:44:45 wahoo systemd[1]: Failed to start Samba SMB Daemon. Jan 16 13:44:45 wahoo systemd[1]: Unit smb.service entered failed state. 13:50 wahoo: ~ # journalctl -xn -- Logs begin at Thu 2014-01-09 21:30:20 EST, end at Thu 2014-01-16 -- 13:50:13 EST. -- Jan 16 13:50:13 wahoo systemd[1]: Starting Samba SMB Daemon... -- Subject: Unit smb.service has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit smb.service has begun starting up. Jan 16 13:50:13 wahoo smbd[25795]: [2014/01/16 13:50:13.425986, 0] ../source3/smbd/server.c:1278(main) Jan 16 13:50:13 wahoo smbd[25795]: standard input is not a socket, assuming -D option Jan 16 13:50:13 wahoo smbd[25796]: [2014/01/16 13:50:13.429260, 0] ../lib/util/pidfile.c:117(pidfile_create) Jan 16 13:50:13 wahoo smbd[25796]: ERROR: can't open /var/run/samba/smbd.pid: Error was No such file or directory Jan 16 13:50:13 wahoo systemd[1]: PID file /run/samba/smbd.pid not readable (yet?) after start. Jan 16 13:50:13 wahoo kernel: type=1400 audit(1389898213.428:46): apparmor="DENIED" operation="mkdir" parent=1 profile="/usr/sbin/smbd" Jan 16 13:50:13 wahoo systemd[1]: smb.service never wrote its PID file. Failing. Jan 16 13:50:13 wahoo systemd[1]: Failed to start Samba SMB Daemon. -- Subject: Unit smb.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: -- http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40... -- -- Unit smb.service has failed. -- -- The result is failed. Jan 16 13:50:13 wahoo systemd[1]: Unit smb.service entered failed state. added comment to bug 856651 about failure tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Patrick Shanahan

19:08

* Patrick Shanahan [01-16-14 14:04]: [...]

...

-- The result is failed. Jan 16 13:50:13 wahoo systemd[1]: Unit smb.service entered failed state.

added comment to bug 856651 about failure

but further reading of the present thread, I see requirements: logprof systemctl restart apparmor systemctl restart smb and success tks and I added successful comment to bug 856651 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Mariusz Fik

16:40

Dnia czwartek, 16 stycznia 2014 17:13:40 lynn pisze:

...

Unfortunately, it doesn't help and introduces another error:

After editing this file, did You do as root: 1. `logprof`. 2. `systemctl restart apparmor` 3. `systemctl restart smb` This completely solved issue with PID file here, on 2 systems with openSUSE 13.1. -- Pozdrawiam / Best regards, Mariusz Fik openSUSE Community Member GPG: 5FCE 7241 B3B9 32FD 455B C30E 42D6 6C88 9E83 7C3D

lynn

17:05

On Thu, 2014-01-16 at 17:40 +0100, Mariusz Fik wrote:

...

Dnia czwartek, 16 stycznia 2014 17:13:40 lynn pisze:

...
Unfortunately, it doesn't help and introduces another error:

After editing this file, did You do as root: 1. `logprof`. 2. `systemctl restart apparmor` 3. `systemctl restart smb`

Yes.

...

This completely solved issue with PID file here, on 2 systems with openSUSE 13.1.

According to the devs, the pid issue is a warning. smbd starts but the warning persists. But it's not just this error/warning. Our file server is part of a domain. I don't think the devs can test bugs under those conditions so it is no use sending a bug report. Thanks for your interest. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Lars Müller

17:29

On Thu, Jan 16, 2014 at 06:05:19PM +0100, lynn wrote:

...

On Thu, 2014-01-16 at 17:40 +0100, Mariusz Fik wrote: [ 8< ]

...
This completely solved issue with PID file here, on 2 systems with openSUSE 13.1.

According to the devs, the pid issue is a warning. smbd starts but the warning persists. But it's not just this error/warning. Our file server is part of a domain. I don't think the devs can test bugs under those conditions so it is no use sending a bug report.

Please check the instructions given already some days back. See http://lists.opensuse.org/opensuse/2014-01/msg00593.html and be this nice to file a bug report and provide the requested details. If no bug gets reported Christian Boltz as the AppArmor maintainer will not be able to enhance the profiles of the Samba daemons. The AppArmor profiles for the Samba daemons are part of the apparmor-profiles package and are not part of Samba. Without a bug report this issue will not get addressed. Even if you write vague mails again and again. Please follow Christian' instructions from http://en.opensuse.org/openSUSE:Bugreport_AppArmor and attach the information details listed at the end of the page to the bug report. He needs such a bug report as he'll else not be able to decide which changes to apply. After you filed a defect report, be this nice and report the bug ID back to this list, please. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

lynn

17:52

On Thu, 2014-01-16 at 18:29 +0100, Lars Müller wrote:

...

Without a bug report this issue will not get addressed. Even if you write vague mails again and again. Please follow Christian' instructions from http://en.opensuse.org/openSUSE:Bugreport_AppArmor and attach the information details listed at the end of the page to the bug report. He needs such a bug report as he'll else not be able to decide which changes to apply.

After you filed a defect report, be this nice and report the bug ID back to this list, please.

Lars, please. . . How many bug reports do you want before you will do anything? You already have my bug report: https://bugzilla.novell.com/show_bug.cgi?id=846586 In it, Christian has asked you a direct question. If you are unable to answer it then please say so so that we can get on with it. It is now almost 2 months. Thank you L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Lars Müller

19:47

On Thu, Jan 16, 2014 at 06:52:14PM +0100, lynn wrote:

...

On Thu, 2014-01-16 at 18:29 +0100, Lars Müller wrote:

...
Without a bug report this issue will not get addressed. Even if you write vague mails again and again. Please follow Christian' instructions from http://en.opensuse.org/openSUSE:Bugreport_AppArmor and attach the information details listed at the end of the page to the bug report. He needs such a bug report as he'll else not be able to decide which changes to apply.

After you filed a defect report, be this nice and report the bug ID back to this list, please.

Lars, please. . . How many bug reports do you want before you will do anything?

You already have my bug report: https://bugzilla.novell.com/show_bug.cgi?id=846586

In it, Christian has asked you a direct question. If you are unable to answer it then please say so so that we can get on with it. It is now almost 2 months.

That simply slipped through. Thanks for the reminder. Now it's up to you to do your homework. Please feed bugzilla as described by this mail http://lists.opensuse.org/opensuse/2014-01/msg00593.html and report the resulting bug report ID back to this thread. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

lynn

19:56

On Thu, 2014-01-16 at 20:47 +0100, Lars Müller wrote:

...

On Thu, Jan 16, 2014 at 06:52:14PM +0100, lynn wrote:

...
On Thu, 2014-01-16 at 18:29 +0100, Lars Müller wrote:

...
Without a bug report this issue will not get addressed. Even if you write vague mails again and again. Please follow Christian' instructions from http://en.opensuse.org/openSUSE:Bugreport_AppArmor and attach the information details listed at the end of the page to the bug report. He needs such a bug report as he'll else not be able to decide which changes to apply.

After you filed a defect report, be this nice and report the bug ID back to this list, please.

Lars, please. . . How many bug reports do you want before you will do anything?

You already have my bug report: https://bugzilla.novell.com/show_bug.cgi?id=846586

In it, Christian has asked you a direct question. If you are unable to answer it then please say so so that we can get on with it. It is now almost 2 months.

That simply slipped through. Thanks for the reminder.

Mmm.

...

Now it's up to you to do your homework. Please feed bugzilla as described by this mail http://lists.opensuse.org/opensuse/2014-01/msg00593.html and report the resulting bug report ID back to this thread.

Thanks,

Lars

I think we'll wait to see how the Samba Developers respond to your comments on that topic on samba-technical first. Thank you. L -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Lars Müller

21:19

On Thu, Jan 16, 2014 at 08:56:24PM +0100, lynn wrote:

...

On Thu, 2014-01-16 at 20:47 +0100, Lars Müller wrote: [ 8< ]

...
Now it's up to you to do your homework. Please feed bugzilla as described by this mail http://lists.opensuse.org/opensuse/2014-01/msg00593.html and report the resulting bug report ID back to this thread.

I think we'll wait to see how the Samba Developers respond to your comments on that topic on samba-technical first.

Your homework has no dependency to the suggestion made with https://lists.samba.org/archive/samba-technical/2014-January/097304.html which is about systemd and the message we write at startup of a daemon (nmbd, smbd, winbindd). Oranges are even in 2014 not growing on apple trees. A short refresh for you: you complained about AppArmor causing trouble as soon as you joined a domain which is driven by a Microsoft Server and Active Directory. Go and file the bug and assign it to Chritian. Without such a bug report it's unlikely up to impossible that an update gets published for openSUSE 13.1. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

lynn

23:47

On Thu, 2014-01-16 at 22:19 +0100, Lars Müller wrote:

...

A short refresh for you: you complained about AppArmor causing trouble as soon as you joined a domain which is driven by a Microsoft Server and Active Directory.

Please refresh yourself before refreshing. For a start we do not, nor shall ever, join, 'a domain which is driven by a Microsoft Server'. Thank you for your renewed interest. L -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

3766

Age (days ago)

3771

Last active (days ago)

List overview

Download

24 comments

6 participants

participants (6)

James Knott
John Andersen
Lars Müller
lynn
Mariusz Fik
Patrick Shanahan