Project

General

Profile

Bug #27470

smbd filling security log after update to 11.1

Added by Ian Campbell over 2 years ago. Updated over 2 years ago.

Status:
Closed: User Config Issue
Priority:
Important
Assignee:
Timur Bakeyev
Category:
OS
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

A couple weeks ago, I updated from 11.0 to 11.1. Since then, my daily security emails look something like this:

freenas.local kernel log messages:
pid 77025 (smbd), uid 0: exited on signal 6 (core dumped)
pid 77038 (smbd), uid 0: exited on signal 6 (core dumped)
pid 77066 (smbd), uid 0: exited on signal 6 (core dumped)
pid 79519 (smbd), uid 0: exited on signal 6 (core dumped)
pid 81895 (smbd), uid 0: exited on signal 6 (core dumped)
pid 89116 (smbd), uid 0: exited on signal 6 (core dumped)
pid 1357 (smbd), uid 0: exited on signal 6 (core dumped)
pid 57976 (smbd), uid 0: exited on signal 6 (core dumped)
pid 76908 (smbd), uid 0: exited on signal 6 (core dumped)
pid 77116 (smbd), uid 0: exited on signal 6 (core dumped)
pid 78266 (smbd), uid 0: exited on signal 6 (core dumped)
pid 80707 (smbd), uid 0: exited on signal 6 (core dumped)

-- End of security output --

Forum users suggested I submit a bug report.

History

#1 Updated by Ian Campbell over 2 years ago

  • File debug-freenas-20171228143407.txz added
  • Private changed from No to Yes

#2 Updated by Ian Campbell over 2 years ago

  • File smb4.conf added

#3 Avatar?id=14398&size=24x24 Updated by Kris Moore over 2 years ago

  • Assignee changed from Release Council to Timur Bakeyev
  • Priority changed from No priority to Important
  • Target version set to 11.3

#4 Updated by Timur Bakeyev over 2 years ago

  • Status changed from Unscreened to 15

Hi, Ian!

Can you, please, check configuration of all your shares and remove from the list of enabled modules aio_fork?

I see in the config:

vfs objects = shadow_copy2 zfs_space zfsacl readahead aio_fork streams_xattr

Seems it's the one that create troubles.

  ../source3/modules/vfs_aio_fork.c:229: Type mismatch: name[struct aio_fork_config] expected[struct aio_child_list]
[2017/12/27 23:00:31.709532,  0] ../source3/lib/util.c:804(smb_panic_s3)
  PANIC (pid 16431): ../source3/modules/vfs_aio_fork.c:229: Type mismatch: name[struct aio_fork_config] expected[struct aio_child_list]

Next question is - why it is enabled in your configuration? I believe it's not in the default set of enabled modules.

From that prospective the usefulness of readahead module is also questionable, but at least it's harmless.

#5 Updated by Dru Lavigne over 2 years ago

  • Status changed from 15 to Closed: User Config Issue
  • Target version changed from 11.3 to N/A
  • Private changed from Yes to No
  • Seen in changed from Unspecified to 11.1

#6 Updated by Dru Lavigne over 2 years ago

  • File deleted (debug-freenas-20171228143407.txz)

#7 Updated by Dru Lavigne over 2 years ago

  • File deleted (smb4.conf)

#8 Updated by Ian Campbell over 2 years ago

Apologies for the slow response over the holidays. I've just disabled aio_fork and will see what the log looks like overnight. I believe that one got enabled years ago when I was trying to use rsync to back up a bunch of files from a Linux system to a SMB share while preserving folder "last modified" dates. That task is long since completed, so it's not a problem to disable this--it was vestigial at this point.

Thanks for the info! I'll follow up once I get the log for tomorrow.

#9 Updated by Ian Campbell over 2 years ago

I have not had any new smbd errors in over 24 hours, so it looks like removing aio_fork was indeed the solution. Thanks for your help!

Also available in: Atom PDF