cannot rename /etc/apt/sedMN0SH3: Operation not permitted

    • Resolved
    • Upgrade 0.5 -> 1.0

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

    • cannot rename /etc/apt/sedMN0SH3: Operation not permitted

      hi,

      I get the upgrade an error.

      Source Code

      1. ​root@Nas:~# omv-release-upgrade
      2. Upgrading system to 1.0 (Kralizec) ...
      3. sed: cannot rename /etc/apt/sedMN0SH3: Operation not permitted
      4. run-parts: /tmp/tmp.Gki71ASsaj/pre.d/20-apt-update-source-list exited with return code 4
      5. root@Nas:~#



      what am I doing wrong?
    • hello,

      i have the same error from 0.5.59 to 1.0:

      Source Code

      1. Upgrading system to 1.0 (Kralizec) ...
      2. sed: cannot rename /etc/apt/sedx2pnvz: Operation not permitted
      3. run-parts: /tmp/tmp.ccXBjyEI1d/pre.d/20-apt-update-source-list exited with return code 4

      thanks for you support and great product.
      The Power of the Power Button!
      OMV 2.x // Hardware: HP N36L Microserver (BIOS mod), 4GB RAM, 2x1TB WD Red + 2x2TB ST, 160GB for system
    • Thanks Jetiman for the feedback - hunt3rus i also sent you a PM how to do it.

      We are already working on a fix to prevent further issues while using omv-release-upgrade
      OMV stoneburner | HP Microserver | 256GB Samsung 830 SSD for system | 4x 2TB in a RAID5
      OMV erasmus| Odroid XU4 | 5TB Data drive | 500GB Backup drive
    • Wrote with both guys via PM, this is the history:

      Jetiman wrote:

      came at the end

      Source Code

      1. ​[ ok ] Restarting PHP5 FastCGI Process Manager: php5-fpm.
      2. ...
      3. Errors were encountered while processing:
      4. postfix
      5. bsd-mailx
      6. openmediavault
      7. E: Sub-process /usr/bin/dpkg returned an error code (1)
      8. root@Nas:~#


      After a apt-get upgrade:

      Jetiman wrote:

      Source Code

      1. ​root@Nas:~# apt-get upgrade
      2. Paketlisten werden gelesen... Fertig
      3. Abhängigkeitsbaum wird aufgebaut.
      4. Statusinformationen werden eingelesen.... Fertig
      5. Die folgenden Pakete sind zurückgehalten worden:
      6. libboost-date-time-dev libboost-dev libboost-filesystem-dev libboost-python-dev libboost-thread-dev
      7. 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 5 nicht aktualisiert.
      8. 3 nicht vollständig installiert oder entfernt.
      9. Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
      10. Möchten Sie fortfahren [J/n]? j
      11. postfix (2.9.6-2) wird eingerichtet ...
      12. Postfix configuration was untouched. If you need to make changes, edit
      13. /etc/postfix/main.cf (and others) as needed. To view Postfix configuration
      14. values, see postconf(1).
      15. After modifying main.cf, be sure to run '/etc/init.d/postfix reload'.
      16. Running newaliases
      17. [ ok ] Stopping Postfix Mail Transport Agent: postfix.
      18. [ ok ] Starting Postfix Mail Transport Agent: postfix.
      19. bsd-mailx (8.1.2-0.20111106cvs-1) wird eingerichtet ...
      20. openmediavault (1.0.21) wird eingerichtet ...
      21. Konfigurationsdatei »/etc/default/openmediavault«
      22. ==> Modifiziert (von Ihnen oder von einem Skript) seit der Installation.
      23. ==> Paketverteiler hat eine aktualisierte Version herausgegeben.
      24. Wie möchten Sie vorgehen? Ihre Wahlmöglichkeiten sind:
      25. Y oder I : Die Version des Paket-Betreuers installieren
      26. N oder O : Die momentan installierte Version beibehalten
      27. D : Die Unterschiede zwischen den Versionen anzeigen
      28. Z : Eine Shell starten, um die Situation zu begutachten
      29. Der Standardweg ist das Beibehalten der momentanen Version.
      30. *** openmediavault (Y/I/N/O/D/Z) [Vorgabe=N] ? N
      31. Neue Version der Konfigurationsdatei /etc/pam.d/openmediavault wird installiert ...
      32. Neue Version der Konfigurationsdatei /etc/openmediavault/php.ini wird installiert ...
      33. Neue Version der Konfigurationsdatei /etc/init.d/openmediavault-engined wird installiert ...
      34. Neue Version der Konfigurationsdatei /etc/init.d/openmediavault-beep wird installiert ...
      35. Updating configuration ...
      36. monit: action failed -- There is no service by that name
      37. Reloading daemon monitor configuration: monit.
      38. Stopping web server: apache2
      39. The apache2 configtest failed, so we are trying to kill it manually. This is almost certainly suboptimal, so please make sure your system is working as you'd expect now! ... (warning).
      40. ... waiting .
      41. update-rc.d: using dependency based boot sequencing
      42. Reloading PHP5 FastCGI Process Manager: php5-fpm.
      43. Restarting nginx: nginx.
      44. Reloading daemon monitor configuration: monit.
      45. Reloading ftp server: proftpd.
      46. Reloading ftp server: proftpd.
      47. Trigger für openmediavault werden verarbeitet ...
      48. Restarting engine daemon ...
      49. Updating locale files ...
      50. Updating file permissions ...
      51. root@Nas:~#
      Display All


      And at least an omv-update

      Jetiman wrote:

      Webinterface geht

      Source Code

      1. ​root@Nas:~# omv-update
      2. ....
      3. Building dependency tree
      4. Reading state information... Done
      5. Calculating upgrade... Done
      6. The following packages will be REMOVED:
      7. libboost-date-time1.42-dev libboost-filesystem1.42-dev libboost-python1.42-dev libboost-serialization1.42-dev libboost-system1.42-dev libboost-thread1.42-dev
      8. libboost1.42-dev
      9. The following NEW packages will be installed:
      10. libboost-date-time1.49-dev libboost-filesystem1.49-dev libboost-python1.49-dev libboost-serialization1.49-dev libboost-system1.49-dev libboost-thread1.49-dev
      11. libboost1.49-dev
      12. The following packages will be upgraded:
      13. libboost-date-time-dev libboost-dev libboost-filesystem-dev libboost-python-dev libboost-thread-dev
      14. 5 upgraded, 7 newly installed, 7 to remove and 0 not upgraded.
      15. Need to get 10.2 MB of archives.
      16. After this operation, 24.7 MB of additional disk space will be used.
      17. WARNING: The following packages cannot be authenticated!
      18. libboost-filesystem-dev libboost-system1.49-dev libboost-filesystem1.49-dev libboost-python-dev libboost-python1.49-dev libboost-thread-dev libboost-thread1.49-dev
      19. libboost-dev libboost-date-time-dev libboost1.49-dev libboost-serialization1.49-dev libboost-date-time1.49-dev
      20. Authentication warning overridden.
      21. Get:1 http://ftp.de.debian.org/debian/ wheezy/main libboost-filesystem-dev i386 1.49.0.1 [2756 B]
      22. Get:2 http://ftp.de.debian.org/debian/ wheezy/main libboost-system1.49-dev i386 1.49.0-3.2 [34.4 kB]
      23. Get:3 http://ftp.de.debian.org/debian/ wheezy/main libboost-filesystem1.49-dev i386 1.49.0-3.2 [99.7 kB]
      24. Get:4 http://ftp.de.debian.org/debian/ wheezy/main libboost-python-dev i386 1.49.0.1 [3118 B]
      25. Get:5 http://ftp.de.debian.org/debian/ wheezy/main libboost-python1.49-dev i386 1.49.0-3.2 [474 kB]
      26. Get:6 http://ftp.de.debian.org/debian/ wheezy/main libboost-thread-dev i386 1.49.0.1 [2748 B]
      27. Get:7 http://ftp.de.debian.org/debian/ wheezy/main libboost-thread1.49-dev i386 1.49.0-3.2 [66.3 kB]
      28. Get:8 http://ftp.de.debian.org/debian/ wheezy/main libboost-dev i386 1.49.0.1 [3032 B]
      29. Get:9 http://ftp.de.debian.org/debian/ wheezy/main libboost-date-time-dev i386 1.49.0.1 [2728 B]
      30. Get:10 http://ftp.de.debian.org/debian/ wheezy/main libboost1.49-dev i386 1.49.0-3.2 [9203 kB]
      31. Get:11 http://ftp.de.debian.org/debian/ wheezy/main libboost-serialization1.49-dev i386 1.49.0-3.2 [298 kB]
      32. Get:12 http://ftp.de.debian.org/debian/ wheezy/main libboost-date-time1.49-dev i386 1.49.0-3.2 [47.7 kB]
      33. Fetched 10.2 MB in 8s (1196 kB/s)
      34. (Reading database ... 56708 files and directories currently installed.)
      35. Preparing to replace libboost-filesystem-dev 1.42.0.1 (using .../libboost-filesystem-dev_1.49.0.1_i386.deb) ...
      36. Unpacking replacement libboost-filesystem-dev ...
      37. (Reading database ... 56707 files and directories currently installed.)
      38. Removing libboost-filesystem1.42-dev ...
      39. Removing libboost-system1.42-dev ...
      40. Selecting previously unselected package libboost-system1.49-dev.
      41. (Reading database ... 56690 files and directories currently installed.)
      42. Unpacking libboost-system1.49-dev (from .../libboost-system1.49-dev_1.49.0-3.2_i386.deb) ...
      43. Selecting previously unselected package libboost-filesystem1.49-dev.
      44. Unpacking libboost-filesystem1.49-dev (from .../libboost-filesystem1.49-dev_1.49.0-3.2_i386.deb) ...
      45. Preparing to replace libboost-python-dev 1.42.0.1 (using .../libboost-python-dev_1.49.0.1_i386.deb) ...
      46. Unpacking replacement libboost-python-dev ...
      47. (Reading database ... 56707 files and directories currently installed.)
      48. Removing libboost-python1.42-dev ...
      49. Processing triggers for python-support ...
      50. Selecting previously unselected package libboost-python1.49-dev.
      51. (Reading database ... 56666 files and directories currently installed.)
      52. Unpacking libboost-python1.49-dev (from .../libboost-python1.49-dev_1.49.0-3.2_i386.deb) ...
      53. Preparing to replace libboost-thread-dev 1.42.0.1 (using .../libboost-thread-dev_1.49.0.1_i386.deb) ...
      54. Unpacking replacement libboost-thread-dev ...
      55. (Reading database ... 56756 files and directories currently installed.)
      56. Removing libboost-thread1.42-dev ...
      57. Selecting previously unselected package libboost-thread1.49-dev.
      58. (Reading database ... 56748 files and directories currently installed.)
      59. Unpacking libboost-thread1.49-dev (from .../libboost-thread1.49-dev_1.49.0-3.2_i386.deb) ...
      60. Preparing to replace libboost-dev 1.42.0.1 (using .../libboost-dev_1.49.0.1_i386.deb) ...
      61. Unpacking replacement libboost-dev ...
      62. Preparing to replace libboost-date-time-dev 1.42.0.1 (using .../libboost-date-time-dev_1.49.0.1_i386.deb) ...
      63. Unpacking replacement libboost-date-time-dev ...
      64. (Reading database ... 56756 files and directories currently installed.)
      65. Removing libboost-date-time1.42-dev ...
      66. Removing libboost-serialization1.42-dev ...
      67. Removing libboost1.42-dev ...
      68. Selecting previously unselected package libboost1.49-dev.
      69. (Reading database ... 48973 files and directories currently installed.)
      70. Unpacking libboost1.49-dev (from .../libboost1.49-dev_1.49.0-3.2_i386.deb) ...
      71. Selecting previously unselected package libboost-serialization1.49-dev.
      72. Unpacking libboost-serialization1.49-dev (from .../libboost-serialization1.49-dev_1.49.0-3.2_i386.deb) ...
      73. Selecting previously unselected package libboost-date-time1.49-dev.
      74. Unpacking libboost-date-time1.49-dev (from .../libboost-date-time1.49-dev_1.49.0-3.2_i386.deb) ...
      75. Setting up libboost1.49-dev (1.49.0-3.2) ...
      76. Setting up libboost-system1.49-dev (1.49.0-3.2) ...
      77. Setting up libboost-filesystem1.49-dev (1.49.0-3.2) ...
      78. Setting up libboost-filesystem-dev (1.49.0.1) ...
      79. Setting up libboost-python1.49-dev (1.49.0-3.2) ...
      80. Setting up libboost-python-dev (1.49.0.1) ...
      81. Setting up libboost-serialization1.49-dev (1.49.0-3.2) ...
      82. Setting up libboost-date-time1.49-dev (1.49.0-3.2) ...
      83. Setting up libboost-thread1.49-dev (1.49.0-3.2) ...
      84. Setting up libboost-thread-dev (1.49.0.1) ...
      85. Setting up libboost-dev (1.49.0.1) ...
      86. Setting up libboost-date-time-dev (1.49.0.1) ...
      87. Creating index of upgradeable packages ...
      88. Creating index of OpenMediaVault plugins ...
      89. root@Nas:~#
      Display All


      now working on both systems. And as I already said - working on a fix to prevent future issues.

      Set so solved ;)
      OMV stoneburner | HP Microserver | 256GB Samsung 830 SSD for system | 4x 2TB in a RAID5
      OMV erasmus| Odroid XU4 | 5TB Data drive | 500GB Backup drive