38 emails saying the same thing within the course of less then 60 seconds.

1st Official Post

    Lets not get into the error right now (I will create a thread for that elsewhere) But is this not nuts? I think I have asked about something like this before, but is there a way to limit these? If it happen 38 times in the same minute, I don't need to be told 38 times and an e-mail.

    In each e-mail the information was exactly the same, just the PID changed. Each e-mail beyond the 2nd (or maybe even 3rd) provides no additional useful information, so is there a way to say "Yea, if it happens more then 3 times in a given period of time, stop sending the e-mails please."

    • Official Post

    Based on your description it sounds like monit monitoring daemon is the sender of the emails. I don't think it is possible to do what you request with that software. I also don't think it is possible with postfix which is responsible for submitting the emails. The only thing you can do is to disable the monitoring emails in the notification settings page.

    https://mmonit.com/monit/documentation/monit.html

    Would you not consider this a bug? Or at least something that should be corrected? 38 e-mails to tell me the same thing? (Point made? Sorry, couldn't resist.)

    • Official Post

    Are you really still on OMV 6.x? If you are, are you sure OMV 7.x still does the same thing?

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    38 emails sounds like a lot at first.


    Quote from Shadow Wizard

    In each e-mail the information was exactly the same, just the PID changed.

    But if there are 38 different processes for which a warning is issued, then that is exactly what the software is there for.


    You have to tell us more information about the error and the process which is monitored to do more analysis. You should also become familar with monit to understand how it works.

    Quote from ryecoaaron

    Are you really still on OMV 6.x? If you are, are you sure OMV 7.x still does the same thing?

    You do have a fair point. I guess I should have asked "If this is not fixed in OMV 7 don't you think it should be?" I think we have had the discussion about upgrading, and I think I am gonna try and do it next weekend, at least to one of my servers. I understand asking for it to be fixed on 6.x is not reasonable.

    • Official Post
    Quote from Shadow Wizard

    You do have a fair point. I guess I should have asked "If this is not fixed in OMV 7 don't you think it should be?" I think we have had the discussion about upgrading, and I think I am gonna try and do it next weekend, at least to one of my servers. I understand asking for it to be fixed on 6.x is not reasonable.

    I don't know that it is fixed on 7. I have never received that many emails but that doesn't mean anything is changed on OMV 7.

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Quote from votdev

    38 emails sounds like a lot at first.


    But if there are 38 different processes for which a warning is issued, then that is exactly what the software is there for.


    You have to tell us more information about the error and the process which is monitored to do more analysis.

    Sure, since I don't need help resolving it, I can post the cause here. I just didn't want to turn this thread into a "lets fix 2 errors in 1 thread" thread.

    The message was as follows:

    Code
    The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 1660763 (/usr/sbin/smbd).

This means there was a problem with the program, such as a segfault.
However, gdb was not found on your system, so the error could not be
debugged.  Please install the gdb package so that debugging information
is available the next time such a problem occurs.

    So I did the first thing you should do when you have an issue. I rebooted. It forced me to do a fschk before it would boot on the system drive, so I did that (It was the 4th time I have had to do it in the last coupel of years on this system btw. Was told in a previous thread not to worry about it) and its fixed.. I hope. I had the same thing yesterday (only 8 messages) but all worked, but when it happened again today, I thought I should reboot. So far as is well.

    • Official Post
    Quote from Shadow Wizard

    Sure, since I don't need help resolving it, I can post the cause here. I just didn't want to turn this thread into a "lets fix 2 errors in 1 thread" thread.

    The message was as follows:

    Code
    The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 1660763 (/usr/sbin/smbd).

This means there was a problem with the program, such as a segfault.
However, gdb was not found on your system, so the error could not be
debugged.  Please install the gdb package so that debugging information
is available the next time such a problem occurs.

    So I did the first thing you should do when you have an issue. I rebooted. It forced me to do a fschk before it would boot on the system drive, so I did that (It was the 4th time I have had to do it btw. Was told in a previous thread not to worry about it) and its fixed.. I hope. I had the same thing yesterday (only 8 messages) but all worked, but when it happened again today, I thought I should reboot. So far as is well.

    Hmmm, ok, monit is out for Samba. TBH, i don't know who sends the emails, but monit does not monitor Samba in OMV.

    Any hint in the email who is sending it?

    SO setting my e-mail information in the notification settings in OMV results in other things sending me e-mails as well? That is good/interesting to know. So then I guess that asks the question, what installed/designed this script? Is it something that gets installed with Linux Samba? With OMV Samba? Something else? Basically who's "responsibility" is it to decide if this is an issue and to correct it if it is I suppose I am asking. I use "responsibility" in quotes because I know a lot of this is open source and don't feel its right for anyone to expect issues to be fixed in open source projects.

    And as far as the system being in bad shape. After the forced fschk on boot, all seems fine. Thats what happened the last 3 times as well. For some reason I rebooted, it demanded a fschk, I did it, and it all worked. Last time I posted about it in this forum asking if I should be concerned because it has happened a few times and was told not to be worried about it. Are you saying I should be?

    I'm having the same problem with "Panic or segfault in Samba" in Emails but on two similar systems running OMV 6 :


    One mini-PC has been running smoothly (24/7) since around 2023, and I upgraded the other (desktop PC) from 5 to 6 around the end of last year. Both send this warning via email every time a file is copied in File Explorer - regardless of whether it's Linux or Windows. If 100 files are copied, 100 emails arrive! This problem started around January - I don't know exactly...

    I've been waiting for an update to fix this - but nothing...

    There are further hints here in the forum, but no solution.

    1x OMV 6 , 1x OMV 7

    komm wir essen Opa --------- Satzzeichen retten Leben :!:

    • Official Post
    Quote from mirada

    I'm having the same problem with "Panic or segfault in Samba" in Emails but on two similar systems running OMV 6 :


    One mini-PC has been running smoothly (24/7) since around 2023, and I upgraded the other (desktop PC) from 5 to 6 around the end of last year. Both send this warning via email every time a file is copied in File Explorer - regardless of whether it's Linux or Windows. If 100 files are copied, 100 emails arrive! This problem started around January - I don't know exactly...

    I've been waiting for an update to fix this - but nothing...

    There are further hints here in the forum, but no solution.

    Don't expect any more updates; OMV6 is end of life, same applies to Debian 11 which is the base of OMV. You need to upgrade to OMV7.

    Quote from votdev

    You need to upgrade to OMV7.

    I've now upgraded to OMV7. But that didn't solve the problem.

    When I copy a folder with 10 files from the OMV server (shared folder) using Linux Mint, I receive this email with the error message 10 times. A different PID is displayed each time. No errors can be detected when copying the files.

    If no one here can find the cause, is there a way to stop this error message from being sent?

    1x OMV 6 , 1x OMV 7

    komm wir essen Opa --------- Satzzeichen retten Leben :!:

    Quote from votdev

    Try to set panic action = in the extra options field in the settings page.

    missing an Operator behind '=' ?



    Edit :

    it's not a clean solution - but it seems to work.

    will continue to monitor it...

    I also entered it into my OMV6 - it seems to work there too.

    thx !

    1x OMV 6 , 1x OMV 7

    komm wir essen Opa --------- Satzzeichen retten Leben :!:

    Edited 3 times, last by mirada ().

  • votdev

    Added the Label resolved

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login