Segmentation fault

1st Official Post

    Hi all,

    I started getting these emails yesterday after updating to 7.4.3-1. Was 7.4.2-2

    I've searched around however those with a similar issue don't appear to have found a solution.

    It was previously 6.x and I successfully upgraded it a month or two ago.


    Running omv-upgrade returns:


    I didn't start getting the 'openmedivault-omvextrasorg' until after running 6 to 7 fix script.


    I've tried:

    • omv-upgrade
    • dpkg --configure -a
    • apt --fix-broken install
    • apt install -f
    • omv-aptclean
    • dpkg -l | grep openmedivault
      iF openmediavault 7.4.3-1 all openmediavault - The open network attached storage solution
      ii openmediavault-apttool 7.1.1 all apt tool plugin for OpenMediaVault.
      ii openmediavault-backup 7.1.4 all backup plugin for OpenMediaVault.
      ii openmediavault-diskstats 7.0-2 all openmediavault disk monitoring plugin
      ii openmediavault-filebrowser 7.0-4 all openmediavault File Browser plugin
      ii openmediavault-keyring 1.0.2-2 all GnuPG archive keys of the openmediavault archive
      iU openmediavault-omvextrasorg 7.0 all OMV-Extras.org Package Repositories for OpenMediaVault
      ii openmediavault-remotemount 7.0.2 all Remote mount plugin for OpenMediaVault.
      ii openmediavault-rsnapshot 7.0.1 all OpenMediaVault rsnapshot backup plugin.
    • apt install --reinstall openmedivault
      Reading package lists... Done
      Building dependency tree... Done
      Reading state information... Done
      0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
      2 not fully installed or removed.
      After this operation, 0 B of additional disk space will be used.
      E: Internal Error, No file name for openmediavault:amd64
    • dpkg -i openmediavault_7.4.3-1_all.deb

    If I try to change a setting on a SMB share, I get the following on trying tio apply the configuration change:


    Now if I run 'omv-release-upgrade' I get 'command not found'. Try to run 'omv-firstaid', I get 'Segmentation fault'.


    Lastly, 'cat /var/log/dpkg.log' shows this at the bottom:

    2024-07-28 14:09:53 startup archives install

    2024-07-28 14:09:53 upgrade openmediavault:all 7.4.3-1 7.4.3-1

    2024-07-28 14:09:53 status half-configured openmediavault:all 7.4.3-1

    2024-07-28 14:09:55 status unpacked openmediavault:all 7.4.3-1

    2024-07-28 14:09:55 status half-installed openmediavault:all 7.4.3-1

    2024-07-28 14:09:55 status triggers-pending rsyslog:amd64 8.2302.0-1

    2024-07-28 14:09:58 status unpacked openmediavault:all 7.4.3-1

    2024-07-28 14:10:00 configure openmediavault:all 7.4.3-1 7.4.3-1

    2024-07-28 14:10:10 status half-configured openmediavault:all 7.4.3-1

    2024-07-28 14:10:25 trigproc rsyslog:amd64 8.2302.0-1 <none>

    2024-07-28 14:10:25 status half-configured rsyslog:amd64 8.2302.0-1

    2024-07-28 14:10:25 status installed rsyslog:amd64 8.2302.0-1

    2024-07-28 14:14:47 startup packages configure

    2024-07-28 14:14:47 configure openmediavault:all 7.4.3-1 <none>

    2024-07-28 14:14:47 status half-configured openmediavault:all 7.4.3-1

    2024-07-28 14:38:14 startup packages configure

    2024-07-28 14:38:14 configure openmediavault:all 7.4.3-1 <none>

    2024-07-28 14:38:14 status half-configured openmediavault:all 7.4.3-1

    2024-07-28 14:38:52 startup packages configure

    2024-07-28 14:38:52 configure openmediavault:all 7.4.3-1 <none>

    2024-07-28 14:38:52 status half-configured openmediavault:all 7.4.3-1


    If someone was able to point me to what to look for &/or request logs, etc. that would be great.

    BTW, I have another on the same version and updated the same way yesterday...no issues.


    Cheers.

    If it helps, below is part of the logs related to the update/upgrade for the OMV with the issues:

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

    Log started: 2024-07-27 10:16:39

    (Reading database ...

    (Reading database ... 5%

    (Reading database ... 10%

    (Reading database ... 15%

    (Reading database ... 20%

    (Reading database ... 25%

    (Reading database ... 30%

    (Reading database ... 35%

    (Reading database ... 40%

    (Reading database ... 45%

    (Reading database ... 50%

    (Reading database ... 55%

    (Reading database ... 60%

    (Reading database ... 65%

    (Reading database ... 70%

    (Reading database ... 75%

    (Reading database ... 80%

    (Reading database ... 85%

    (Reading database ... 90%

    (Reading database ... 95%

    (Reading database ... 100%

    (Reading database ... 46629 files and directories currently installed.)

    Preparing to unpack .../jellyfin-ffmpeg6_6.0.1-8-bullseye_amd64.deb ...

    Unpacking jellyfin-ffmpeg6 (6.0.1-8-bullseye) over (6.0.1-7-bullseye) ...

    Preparing to unpack .../openmediavault_7.4.3-1_all.deb ...

    Unpacking openmediavault (7.4.3-1) over (7.4.2-2) ...

    Setting up openmediavault (7.4.3-1) ...

    Creating configuration database ...

    Migrating configuration database ...

    Setting up Salt environment ...

    Traceback (most recent call last):

    File "/usr/bin/salt-call", line 33, in <module>

    sys.exit(load_entry_point('salt==3007.0', 'console_scripts', 'salt-call')())

    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

    File "/usr/lib/python3/dist-packages/salt/scripts.py", line 438, in salt_call

    import salt.cli.call

    File "/usr/lib/python3/dist-packages/salt/cli/call.py", line 3, in <module>

    import salt.cli.caller

    File "/usr/lib/python3/dist-packages/salt/cli/caller.py", line 12, in <module>

    import salt.channel.client

    File "/usr/lib/python3/dist-packages/salt/channel/client.py", line 13, in <module>

    import salt.crypt

    File "/usr/lib/python3/dist-packages/salt/crypt.py", line 25, in <module>

    import salt.ext.tornado.gen

    File "/usr/lib/python3/dist-packages/salt/ext/tornado/gen.py", line 1299, in <module>

    import salt.ext.tornado.platform.asyncio

    File "/usr/lib/python3/dist-packages/salt/ext/tornado/platform/asyncio.py", line 34, in <module>

    import asyncio # type: ignore

    ^^^^^^^^^^^^^^

    File "/usr/lib/python3.11/asyncio/__init__.py", line 45, in <module>

    from .unix_events import * # pragma: no cover

    ^^^^^^^^^^^^^^^^^^^^^^^^^^

    File "/usr/lib/python3.11/asyncio/unix_events.py", line 23, in <module>

    from . import selector_events

    File "<frozen importlib._bootstrap>", line 1178, in _find_and_load

    File "<frozen importlib._bootstrap>", line 1149, in _find_and_load_unlocked

    File "<frozen importlib._bootstrap>", line 690, in _load_unlocked

    File "<frozen importlib._bootstrap_external>", line 936, in exec_module

    File "<frozen importlib._bootstrap_external>", line 1069, in get_code

    File "<frozen importlib._bootstrap_external>", line 729, in _compile_bytecode

    ValueError: bad marshal data (unknown type code)

    [ERROR ] An un-handled exception was caught by Salt's global exception handler:

    ValueError: bad marshal data (unknown type code)

    Traceback (most recent call last):

    File "/usr/bin/salt-call", line 33, in <module>

    sys.exit(load_entry_point('salt==3007.0', 'console_scripts', 'salt-call')())

    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

    File "/usr/lib/python3/dist-packages/salt/scripts.py", line 438, in salt_call

    import salt.cli.call

    File "/usr/lib/python3/dist-packages/salt/cli/call.py", line 3, in <module>

    import salt.cli.caller

    File "/usr/lib/python3/dist-packages/salt/cli/caller.py", line 12, in <module>

    import salt.channel.client

    File "/usr/lib/python3/dist-packages/salt/channel/client.py", line 13, in <module>

    import salt.crypt

    File "/usr/lib/python3/dist-packages/salt/crypt.py", line 25, in <module>

    import salt.ext.tornado.gen

    File "/usr/lib/python3/dist-packages/salt/ext/tornado/gen.py", line 1299, in <module>

    import salt.ext.tornado.platform.asyncio

    File "/usr/lib/python3/dist-packages/salt/ext/tornado/platform/asyncio.py", line 34, in <module>

    import asyncio # type: ignore

    ^^^^^^^^^^^^^^

    File "/usr/lib/python3.11/asyncio/__init__.py", line 45, in <module>

    from .unix_events import * # pragma: no cover

    ^^^^^^^^^^^^^^^^^^^^^^^^^^

    File "/usr/lib/python3.11/asyncio/unix_events.py", line 23, in <module>

    from . import selector_events

    File "<frozen importlib._bootstrap>", line 1178, in _find_and_load

    File "<frozen importlib._bootstrap>", line 1149, in _find_and_load_unlocked

    File "<frozen importlib._bootstrap>", line 690, in _load_unlocked

    File "<frozen importlib._bootstrap_external>", line 936, in exec_module

    File "<frozen importlib._bootstrap_external>", line 1069, in get_code

    File "<frozen importlib._bootstrap_external>", line 729, in _compile_bytecode

    ValueError: bad marshal data (unknown type code)

    dpkg: error processing package openmediavault (--configure):

    installed openmediavault package post-installation script subprocess returned error exit status 1

    Setting up jellyfin-ffmpeg6 (6.0.1-8-bullseye) ...

    Processing triggers for rsyslog (8.2302.0-1) ...

    Processing triggers for libc-bin (2.36-9+deb12u7) ...

    Errors were encountered while processing:

    openmediavault

    Log ended: 2024-07-27 10:18:55

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


    Below is what was on the OMV that didn't have any issues:

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

    Log started: 2024-07-27 10:16:28

    (Reading database ...

    (Reading database ... 5%

    (Reading database ... 10%

    (Reading database ... 15%

    (Reading database ... 20%

    (Reading database ... 25%

    (Reading database ... 30%

    (Reading database ... 35%

    (Reading database ... 40%

    (Reading database ... 45%

    (Reading database ... 50%

    (Reading database ... 55%

    (Reading database ... 60%

    (Reading database ... 65%

    (Reading database ... 70%

    (Reading database ... 75%

    (Reading database ... 80%

    (Reading database ... 85%

    (Reading database ... 90%

    (Reading database ... 95%

    (Reading database ... 100%

    (Reading database ... 41928 files and directories currently installed.)

    Preparing to unpack .../openmediavault_7.4.3-1_all.deb ...

    Unpacking openmediavault (7.4.3-1) over (7.4.2-2) ...

    Setting up openmediavault (7.4.3-1) ...

    Creating configuration database ...

    Migrating configuration database ...

    Setting up Salt environment ...

    Processing system modifications ...

    Processing triggers for rsyslog (8.2302.0-1) ...

    Processing triggers for openmediavault (7.4.3-1) ...

    Restarting engine daemon ...

    Updating workbench configuration files ...

    Log ended: 2024-07-27 10:16:50

  • macom

    Approved the thread.

    votdev - h/w used in just a simple HP ProDesk 400 SFF. 8GB RAM, 1TB SATA (sda1) used for media and backups ... OS and SWAP is on a 32GB USB3 stick. OMV Extras are installed and the following plugins:

    • openmediavault-apttool 7.1.1
    • openmediavault-backup 7.1.4
    • openmediavault-diskstats 7.0-2
    • openmediavault-filebrowser 7.0-4
    • openmediavault-omvextrasorg 7.0
    • openmediavault-remotemount 7.0.2
    • openmediavault-rsnapshot 7.0.1

    Just the one shared folder which is listed in SMB/CIFS shares.


    The other almost identical OMV which doesn't have this issue has 2x 1TB SATA drives mirrored. Same shared setup as well as OS/SWAP drive.

    It has the following plugins:

    • openmediavault-backup 7.1.4
    • openmediavault-diskclone 7.0
    • openmediavault-omvextrasorg 7.0
    • openmediavault-rsnapshot 7.0.1
    • openmediavault-sharerootfs 7.0-1
    • openmediavault-timeshift 7.0
    • openmediavault-wetty 7.0-2
    • openmediavault-wol 7.0.1

    I see the "faulty" OMV has "openmediavault-apttool 7.1.1", "openmediavault-diskstats 7.0-2", "openmediavault-filebrowser 7.0-4" and "openmediavault-remotemount 7.0.2" whereas the "working" OMV doesn't have these. Has anyone experienced any issues with these? I might uninstall them to see however I suspect it won't fix things.


    Hope this helps?

    petrus - think you're onto something.

    python3 -v gives:

    ---------

    However 'python3 --version' gives "Python 3.11.2"

    For the code above, on my "working" OMV, it continues much further before being prompted to type "help", etc. The following 6 lines are what follows the above on the "working" OMV:

    votdev - below is the output from: dpkg -l | grep python


    Trying to reinstall the 2x "3.9" packages both return:

    is not available, but is referred to by another package.

    This may mean that the package is missing, has been obsoleted, or

    is only available from another source

    ...and:

    package has no installation candidate.


    I did try reinstalling a number (above) however after the packages were fetched, this (below) is what shows:

    Quote

    Segmentation fault

    E: Sub-process /usr/bin/apt-listchanges --apt | | test $? -lt 10 returned an error code (1)

    E: Failure running script /usr/bin/apt-listchanges --apt | | test $? -lt 10

    ....don't have this issue on the working OMV. Instead of 'Segmentation Fault' (on the "good" OMV) it shows that it reads the database, preparing to unpack, etc.

    Any thoughts?

    Also, tried removing 'libpython3.9-minimal:amd64' and 'python3.9-minimal' - both returned:

    Quote

    dpkg: warning: ignoring request to remove python3.9-minimal, only the config

    files of which are on the system; use --purge to remove them too

    dpkg: warning: ignoring request to remove libpython3.9-minimal:amd64, only the config

    files of which are on the system; use --purge to remove them too

    Forgot to mention 'python3-gi' and 'python3-llfuse:amd64' are installed on the working OMV.

    Trying to install either returns:

    Quote

    Segmentation fault

    E: Sub-process /usr/bin/apt-listchanges --apt | | test $? -lt 10 returned an error code (1)

    E: Failure running script /usr/bin/apt-listchanges --apt | | test $? -lt 10

    Hope this helps?

    • Official Post

    bloke

    If you must reinstall from scratch, you can use omv-regen to preserve the system configuration starting from a clean installation.

    One more thing:

    ....and:

    chente - 'omv-regen' is handy to know.


    I did some Goolgling about 'apt-listchanges' and found references to the file 'etc/apt/apt.conf.d/20listchanges' and removing the first line:

    Quote

    DPkg::Pre-Install-Pkgs { "/usr/bin/apt-listchanges --apt | | test $? -lt 10"; };

    DPkg::Tools::Options::/usr/bin/apt-listchanges::Version "2";

    DPkg::Tools::Options::/usr/bin/apt-listchanges::InfoFD "20";

    Dir::Etc::apt-listchanges-main "listchanges.conf";

    Dir::Etc::apt-listchanges-parts "listchanges.conf.d";

    I was then able to run the following successfully:

    Quote

    # apt-get install --reinstall python3.11-minimal

    # apt-get install --reinstall apt-listchanges

    The latter took a while (5-10min) but did complete successfully.

    I also noticed:

    Quote

    N: Repository 'Debian bookworm' changed its 'non-free component' value from 'non-free' to 'non-free non-free-firmware'

    N: More information about this can be found online in the Release notes at: https://www.debian.org/release…ation.html#non-free-split

    Compared with the working OMV, needed to make two changes to "/etc/apt/sources.list" - remarked out the top two lines, added lines three and four:

    ....now running 'omv-upgrade' completes successfully and 'omv-firstaid' runs.

    BTW, I readded the first line in 'etc/apt/apt.conf.d/20listchanges' prior to running 'omv-upgrade'.

    Well, I tried reinstalling 'python3.11' and 'python3' - no good!

    I then tried reinstalling 'libpython3.11:amd64':

    votdev - I was beginning the thing the same,

    I have actually fixed this by doing the following (based on the last post here:(


    Code
    # apt-get download python3 python3.11 python3-minimal python3.11-minimal libpython3.11-minimal libpython3.11-stdlib
# dpkg -i *python3*.deb

# apt --fix-broken install
# omv-upgrade

    Once this all finished....all was good again.

    Thinks everyone for putting in their thoughts.

    Hopefully this can help someone else.

    • New

    Hello,


    I've got a similar issue after an update. Specifically:

    - Attempts to upgrade packages result in Segmentation fault while configuring openmediavault (7.7.9-1).

    - The Web UI returned 500 on an authorization attempt. Logs (nginx) show connect() to unix:/run/php/php8.2-fpm-openmediavault-webgui.sock failed (2: No such file or directory).


    Though, after reading many threads about Segmentation fault here, mostly claiming hardware malfunction, this one showed promising. So, I confirmed the issue was related to php in my case (php -v returned Segmentation fault). then reinstalled php packages using the similar procedure:

    Code
    apt list --installed | cut -d'/' -f1 | grep php | xargs apt-get download
dpkg -i *php*.deb
apt --fix-broken install

    Now it all works again.

    Thank you.

Participate now!

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

Register Yourself Login