panic / segfault on boot

    • OMV 3.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • panic / segfault on boot


      I'm new to OMV and not really a Linux expert, so maybe someone can help me.
      I shutdown my server (3.0.40) at midnight by using the AutoShutdown plugin and as soon as the device is getting rebootet by rtc/wol ini the morning, I'll receive this:

      Source Code

      1. The Samba 'panic action' script, /usr/share/samba/panic-action,
      2. was called for PID 4261 (/usr/sbin/smbd).
      3. This means there was a problem with the program, such as a segfault.
      4. Below is a backtrace for this process generated with gdb, which shows
      5. the state of the program at the time the error occurred. The Samba log
      6. files may contain additional information about the problem.
      7. If the problem persists, you are encouraged to first install the
      8. samba-dbg package, which contains the debugging symbols for the Samba
      9. binaries. Then submit the provided information as a bug report to
      10. Debian. For information about the procedure for submitting bug reports,
      11. please see or the reportbug(1)
      12. manual page.
      13. [Thread debugging using libthread_db enabled]
      14. Using host libthread_db library "/lib/i386-linux-gnu/".
      15. 0xb6a8a041 in waitpid () from /lib/i386-linux-gnu/
      16. #0 0xb6a8a041 in waitpid () from /lib/i386-linux-gnu/
      17. #1 0xb6a24ace in ?? () from /lib/i386-linux-gnu/
      18. #2 0xb77446cb in system () from /lib/i386-linux-gnu/
      19. #3 0xb6fdc688 in smb_panic_s3 () from /usr/lib/i386-linux-gnu/
      20. #4 0xb771f71b in smb_panic () from /usr/lib/i386-linux-gnu/
      21. #5 0xb74a2239 in ?? () from /usr/lib/i386-linux-gnu/samba/
      22. #6 0xb74a262e in smbd_exit_server_cleanly () from /usr/lib/i386-linux-gnu/samba/
      23. #7 0xb6f80b42 in exit_server_cleanly () from /usr/lib/i386-linux-gnu/samba/
      24. #8 0xb746853b in ?? () from /usr/lib/i386-linux-gnu/samba/
      25. #9 0xb6b62c70 in tevent_common_check_signal () from /usr/lib/i386-linux-gnu/
      26. #10 0xb6fff046 in run_events_poll () from /usr/lib/i386-linux-gnu/
      27. #11 0xb6fff3ca in ?? () from /usr/lib/i386-linux-gnu/
      28. #12 0xb6b5f3d8 in _tevent_loop_once () from /usr/lib/i386-linux-gnu/
      29. #13 0xb6b5f58a in tevent_common_loop_wait () from /usr/lib/i386-linux-gnu/
      30. #14 0xb6b5f611 in _tevent_loop_wait () from /usr/lib/i386-linux-gnu/
      31. #15 0xb746fd1d in smbd_process () from /usr/lib/i386-linux-gnu/samba/
      32. #16 0xb7789da5 in ?? ()
      33. #17 0xb6fff170 in run_events_poll () from /usr/lib/i386-linux-gnu/
      34. #18 0xb6fff3ca in ?? () from /usr/lib/i386-linux-gnu/
      35. #19 0xb6b5f3d8 in _tevent_loop_once () from /usr/lib/i386-linux-gnu/
      36. #20 0xb6b5f58a in tevent_common_loop_wait () from /usr/lib/i386-linux-gnu/
      37. #21 0xb6b5f611 in _tevent_loop_wait () from /usr/lib/i386-linux-gnu/
      38. #22 0xb7785f53 in main ()
      39. A debugging session is active.
      40. Inferior 1 [process 4261] will be detached.
      41. Quit anyway? (y or n) [answered Y; input not from terminal]
      Display All

      Can somebody point me in the right direction?
    • Having the same issue here since I updated to OMV 3 just yesterday. Besides this, everything seems fine so far.

      A few minutes ago, I removed the current config and generated a new one with omv-mkconfig samba. So far no error with clients connected, but I have to retest without clients this evening...

      Edit: Nope, false alarm...error also persists with clients connected and config regenerated...

      Any way to "safely" but completely purge samba with all associated stuff and regenerate the omv-configs?

      Edit2: Ok, maybe I fixed it somehow, now I got 3-4 reboots and shutdowns without the panic...Steps included reinstalling samba and fixing an issue with my nut-client for remote UPS on the way...I also regenerated the smb.conf once again....I will report back if the panic keeps popping up the next days...

      The post was edited 3 times, last by stone49th ().