• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Panic or segfault in Samba

AdelM

Basic Pleskian
Hello

Since 2 months I'm getting (sometimes) the following message by mail :


Panic or segfault in Samba

The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 11350 ().

This means there was a problem with the program, such as a segfault.
However, the executable could not be found for process 11350.
It may have died unexpectedly, or you may not have permission to debug
the process.


Any idea on this error and how to fix it ?

Thanks for any suggestion.

-------------------------------------------------

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

CPU GenuineIntel, Intel(R) Xeon(R)CPU L5640 @ 2.27GHz
Version Parallels Plesk Panel v11.0.9_build110120608.16 os_Debian 6.0
OS Debian 6.0.7
Panel version 11.0.9 Update #58
 
Last edited:
I am trying to figure out how that error is related to plesk ...However my recommendation would be post that in the suse forums, they should have better answers ...

You could also provide us with more details by looking at the logs, ie what process is the panic action triggered to kill.. and etc
 
Hi

Thanks for answering.

In which log can I find some answers ?

Why do recommand a post in suse forums as my os is debian ?

Best regards
 
Am so sorry, I am not sure why I typed Suse when that error is very common on Ubuntu & Debian! I must have been thinking about something else ..
However, somewhere someone resolved it with:

deleting the samba config generated by the gui stored at

/var/lib/samba/usershares

and creating own vanilla config at

/etc/samba/smb.conf

Here's a link to seting up vanilla configs

http://www.jonathanmoeller.com/screed/?p=1590

The errors went away with the above ...
 
Back
Top