Beiträge von ChrisBuzz

ChrisBuzz · 28. Februar 2022

Hello,

I am running a paperess-ng docker on my odroid hc2 and figured out that the required Postgresql database is writing permanently on my HDD. So the HDD doesn't spin down.

Is this a normal behavior running a database on the HDD and not on a SSD or SD card?

Alternative for using the docker with Postgresql is using SQlite. Is this maybe a solution that would solve the issue of permanently writing on the HDD even there is currently no action at the docker?

Definitely need some help over here.

ChrisBuzz · 28. Februar 2022

Alright, just figured out that the reason is my Paperless-ng install from docker using Postgresql for the database.

Is this a normal behavior that Postgresql is writing permanently to my HDD?

Would it make sense to move the DB to my internal SD card or will there be a risk due to high writing activity?

ChrisBuzz · 27. Februar 2022

Hello everyone,

after upgrading from OMV 4 to 5 I am facing an issue that my HDD doesn't spin down anymore.

I tried to fix it first with setting the spin down timer using the following guide for my Odroid HC2:

How to use JMS578 Firmware updater under HC1/HC2

Unfortunately there wasn't any change. So I followed up trying hd-idle from this guide:

[How-To] Spin-down hard drives with hd-idle

But this one don't get the HDD to spin down, too.

Using the spin down script from the following guide I receive the following output:

My Guide to Debugging Disk Spin-ups

Spoiler anzeigen

Code

root@Speicher:~# ./find_culprit.sh
Putting the disk sda into standby...
Checking the status of sda.
Drive is still in standby.  Sleeping 45 seconds...
Drive is awake!
[ 1346.532519] postgres(2959): dirtied inode 3819570020 (db_0.tmp) on sda1
[ 1346.532543] postgres(2959): dirtied inode 3819570020 (db_0.tmp) on sda1
[ 1346.533004] postgres(2959): dirtied inode 3819570019 (global.tmp) on sda1
[ 1346.533022] postgres(2959): dirtied inode 3819570019 (global.tmp) on sda1
[ 1346.563382] postgres(2959): WRITE block 2932149069 on sda1 (9 sectors)
[ 1353.174465] postgres(2959): dirtied inode 3819570018 (db_16384.tmp) on sda1
[ 1353.174485] postgres(2959): dirtied inode 3819570018 (db_16384.tmp) on sda1
[ 1353.175731] postgres(2959): dirtied inode 3819570021 (db_0.tmp) on sda1
[ 1353.175749] postgres(2959): dirtied inode 3819570021 (db_0.tmp) on sda1
[ 1353.176097] postgres(2959): dirtied inode 3819570017 (global.tmp) on sda1
[ 1353.176114] postgres(2959): dirtied inode 3819570017 (global.tmp) on sda1
[ 1354.722210] kworker/6:1(7284): WRITE block 2932149078 on sda1 (9 sectors)
[ 1354.722402] xfsaild/sda1(430): WRITE block 2777860816 on sda1 (16 sectors)
[ 1376.503923] postgres(2959): dirtied inode 3819570020 (db_0.tmp) on sda1
[ 1376.503933] postgres(2959): dirtied inode 3819570020 (db_0.tmp) on sda1
[ 1376.504084] postgres(2959): dirtied inode 3819570019 (global.tmp) on sda1
[ 1376.504091] postgres(2959): dirtied inode 3819570019 (global.tmp) on sda1
[ 1376.524511] postgres(2959): WRITE block 2932149087 on sda1 (9 sectors)
[ 1376.553222] postgres(2959): dirtied inode 3819570021 (db_13445.tmp) on sda1
[ 1376.553232] postgres(2959): dirtied inode 3819570021 (db_13445.tmp) on sda1
[ 1376.553553] postgres(2959): dirtied inode 3819570022 (db_0.tmp) on sda1
[ 1376.553561] postgres(2959): dirtied inode 3819570022 (db_0.tmp) on sda1
[ 1376.553695] postgres(2959): dirtied inode 3819570017 (global.tmp) on sda1
[ 1376.553702] postgres(2959): dirtied inode 3819570017 (global.tmp) on sda1

Alles anzeigen

With the following command I get the HDD to spin down:

Code

hdparm -Y /dev/sda

Really don't know what happened over here and how to solve it.

So help is appreciated!

ChrisBuzz · 22. Februar 2022

Zitat von Zoki

If you google for the error, you will find it is related to an old ibseccomp2
and here is the tutorial: https://docs.linuxserver.io/fa…ntu-focal-and-alpine-3-13

OMG...thanks, now it works!

You made my day. Sorry for being such a newb.

ChrisBuzz · 22. Februar 2022

Zitat von Zoki

"Isn't working" is not much of a description of your problem.

Which containers are runningß
How do you see there is a problem?
Post the logs

Or buy me a new cystal ball.

So after the stack is deployed I have the following 3 containers:

-paperless_webserver_1

-paperless_db_1

-paperless_broker_1

After trying to run the console in the webserver I receive the error message:

"Failure

Container 92d3589638dddc10aa91b3de549abcf6359bbe4c0fa0db3efa04f9bd109abfe6 is restarting, wait until the container is running"

Also the container is shown as not healthy and there is no ip or ports shown.

Logs are shown the following:

Spoiler anzeigen

Code

Current thread 0xb6fa2010 (most recent call first):
<no Python frame>
Executing /usr/local/bin/supervisord -c /etc/supervisord.conf
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted

Current thread 0xb6f72010 (most recent call first):
<no Python frame>
Paperless-ng docker container starting...
Creating directory /tmp/paperless
Adjusting permissions of paperless files. This may take a while.
Waiting for PostgreSQL to start...
Apply database migrations...
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted

Current thread 0xb6f13010 (most recent call first):
<no Python frame>
Executing /usr/local/bin/supervisord -c /etc/supervisord.conf
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted

Current thread 0xb6f82010 (most recent call first):
<no Python frame>
Paperless-ng docker container starting...
Creating directory /tmp/paperless
Adjusting permissions of paperless files. This may take a while.
Waiting for PostgreSQL to start...
Apply database migrations...
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted

Current thread 0xb6f15010 (most recent call first):
<no Python frame>
Executing /usr/local/bin/supervisord -c /etc/supervisord.conf
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted

Current thread 0xb6f54010 (most recent call first):
<no Python frame>
Paperless-ng docker container starting...
Creating directory /tmp/paperless
Adjusting permissions of paperless files. This may take a while.
Waiting for PostgreSQL to start...
Apply database migrations...
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted

Current thread 0xb6f1b010 (most recent call first):
<no Python frame>
Executing /usr/local/bin/supervisord -c /etc/supervisord.conf
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted

Current thread 0xb6fdc010 (most recent call first):
<no Python frame>
Paperless-ng docker container starting...
Creating directory /tmp/paperless
Adjusting permissions of paperless files. This may take a while.
Waiting for PostgreSQL to start...
Apply database migrations...
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted

Current thread 0xb6fd6010 (most recent call first):
<no Python frame>
Executing /usr/local/bin/supervisord -c /etc/supervisord.conf
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted

Current thread 0xb6ef9010 (most recent call first):
<no Python frame>
Paperless-ng docker container starting...
Creating directory /tmp/paperless
Adjusting permissions of paperless files. This may take a while.
Waiting for PostgreSQL to start...
Apply database migrations...
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted

Current thread 0xb6f01010 (most recent call first):
<no Python frame>
Executing /usr/local/bin/supervisord -c /etc/supervisord.conf
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted

Current thread 0xb6f33010 (most recent call first):
<no Python frame>

Alles anzeigen

Maybe I have to switch to OMV 6 with a fresh install

ChrisBuzz · 22. Februar 2022

Thanks!

I now changed it to the following:

Spoiler anzeigen

But I still have the issue that the container isn't working.

Any further ideas?

ChrisBuzz · 22. Februar 2022

Zitat von Zoki
If you use this file as stack in portainer, you have to change the local volume definition or the files will end up inside the portainer_data volume somewhere:
Code
  volumes:
      - ./export:/usr/src/paperless/export     # change here
      - ./consume:/usr/src/paperless/consume   # change here
and the other definitions use named docker volumes. Make up your mind, if you want that.
What you need to put for the volumes depends how you set up docker on omv and where you want your data to live.

Which one of the containers is not working? In the stack there are three: broker, db and webserver and why can't you look into the logs?
Alles anzeigen

I changed the stack to the following:

Zitat

Code

# docker-compose file for running paperless from the Docker Hub.
# This file contains everything paperless needs to run.
# Paperless supports amd64, arm and arm64 hardware.
#
# All compose files of paperless configure paperless in the following way:
#
# - Paperless is (re)started on system boot, if it was running before shutdown.
# - Docker volumes for storing data are managed by Docker.
# - Folders for importing and exporting files are created in the same directory
#   as this file and mounted to the correct folders inside the container.
# - Paperless listens on port 8010.
#
# In addition to that, this docker-compose file adds the following optional
# configurations:
#
# - Instead of SQLite (default), PostgreSQL is used as the database server.
#
# To install and update paperless with this file, do the following:
#
# - Open portainer Stacks list and click 'Add stack'
# - Paste the contents of this file and assign a name, e.g. 'Paperless'
# - Click 'Deploy the stack' and wait for it to be deployed
# - Open the list of containers, select paperless_webserver_1
# - Click 'Console' and then 'Connect' to open the command line inside the container
# - Run 'python3 manage.py createsuperuser' to create a user
# - Exit the console
#
# For more extensive installation and update instructions, refer to the
# documentation.

version: "3.4"
services:
  broker:
    image: redis:6.0
    restart: unless-stopped

  db:
    image: postgres:13
    restart: unless-stopped
    volumes:
      - pgdata:/var/lib/postgresql/data
    environment:
      POSTGRES_DB: paperless
      POSTGRES_USER: paperless
      POSTGRES_PASSWORD: paperless

  webserver:
    image: jonaswinkler/paperless-ng:latest
    restart: unless-stopped
    depends_on:
      - db
      - broker
    ports:
      - 38010:8000
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8000"]
      interval: 30s
      timeout: 10s
      retries: 5
    volumes:
      - data:/usr/src/paperless/data
      - media:/usr/src/paperless/media
      - ./export:/srv/dev-disk-by-label-Backupintern/Backupintern/Eigene Dateien/Christoph/50 Dokumente/export
      - ./consume:/srv/dev-disk-by-label-Backupintern/Backupintern/Eigene Dateien/Christoph/50 Dokumente/consume
    environment:
      PAPERLESS_REDIS: redis://broker:6379
      PAPERLESS_DBHOST: db
# The UID and GID of the user used to run paperless in the container. Set this
# to your UID and GID on the host so that you have write access to the
# consumption directory.
      USERMAP_UID: 1000
      USERMAP_GID: 100
# Additional languages to install for text recognition, separated by a
# whitespace. Note that this is
# different from PAPERLESS_OCR_LANGUAGE (default=eng), which defines the
# language used for OCR.
# The container installs English, German, Italian, Spanish and French by
# default.
# See https://packages.debian.org/search?keywords=tesseract-ocr-&searchon=names&suite=buster
# for available languages.
      #PAPERLESS_OCR_LANGUAGES: tur ces
# Adjust this key if you plan to make paperless available publicly. It should
# be a very long sequence of random characters. You don't need to remember it.
      #PAPERLESS_SECRET_KEY: zuiewoouifhkjdshfuihwfjkbfhwj
# Use this variable to set a timezone for the Paperless Docker containers. If not specified, defaults to UTC.
      #PAPERLESS_TIME_ZONE: Europe/Amsterdam
# The default language to use for OCR. Set this to the language most of your
# documents are written in.
      #PAPERLESS_OCR_LANGUAGE: ger

volumes:
  data:
  media:
  pgdata:

Alles anzeigen

Does this one look correct?

The container "webserver" is shown as unhealthy in Portainer.

There is also no IP adress & publish ports for this container available?

Don't know what else I can do?!

Soma: Thanks for your help. Already thought about using Papermerge but it seems Paperless has some advantages compared to Merge.

ChrisBuzz · 22. Februar 2022

Hello,

unfortunately I am not very into using Dockers and this is the reason I need some support installing Paperless-NG with Portier.

I tried to install it with the following modified compose file: paperless-ng/docker/compose/docker-compose.portainer.yml

My file for the stack had the following input:

Spoiler anzeigen

Code

# docker-compose file for running paperless from the Docker Hub.
# This file contains everything paperless needs to run.
# Paperless supports amd64, arm and arm64 hardware.
#
# All compose files of paperless configure paperless in the following way:
#
# - Paperless is (re)started on system boot, if it was running before shutdown.
# - Docker volumes for storing data are managed by Docker.
# - Folders for importing and exporting files are created in the same directory
#   as this file and mounted to the correct folders inside the container.
# - Paperless listens on port 8010.
#
# In addition to that, this docker-compose file adds the following optional
# configurations:
#
# - Instead of SQLite (default), PostgreSQL is used as the database server.
#
# To install and update paperless with this file, do the following:
#
# - Open portainer Stacks list and click 'Add stack'
# - Paste the contents of this file and assign a name, e.g. 'Paperless'
# - Click 'Deploy the stack' and wait for it to be deployed
# - Open the list of containers, select paperless_webserver_1
# - Click 'Console' and then 'Connect' to open the command line inside the container
# - Run 'python3 manage.py createsuperuser' to create a user
# - Exit the console
#
# For more extensive installation and update instructions, refer to the
# documentation.

version: "3.4"
services:
  broker:
    image: redis:6.0
    restart: unless-stopped

  db:
    image: postgres:13
    restart: unless-stopped
    volumes:
      - pgdata:/var/lib/postgresql/data
    environment:
      POSTGRES_DB: paperless
      POSTGRES_USER: paperless
      POSTGRES_PASSWORD: paperless

  webserver:
    image: jonaswinkler/paperless-ng:latest
    restart: unless-stopped
    depends_on:
      - db
      - broker
    ports:
      - 8010:8000
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8000"]
      interval: 30s
      timeout: 10s
      retries: 5
    volumes:
      - data:/usr/src/paperless/data
      - media:/usr/src/paperless/media
      - ./export:/usr/src/paperless/export
      - ./consume:/usr/src/paperless/consume
    environment:
      PAPERLESS_REDIS: redis://broker:6379
      PAPERLESS_DBHOST: db
# The UID and GID of the user used to run paperless in the container. Set this
# to your UID and GID on the host so that you have write access to the
# consumption directory.
      USERMAP_UID: 1000
      USERMAP_GID: 100
# Additional languages to install for text recognition, separated by a
# whitespace. Note that this is
# different from PAPERLESS_OCR_LANGUAGE (default=eng), which defines the
# language used for OCR.
# The container installs English, German, Italian, Spanish and French by
# default.
# See https://packages.debian.org/search?keywords=tesseract-ocr-&searchon=names&suite=buster
# for available languages.
      #PAPERLESS_OCR_LANGUAGES: tur ces
# Adjust this key if you plan to make paperless available publicly. It should
# be a very long sequence of random characters. You don't need to remember it.
      #PAPERLESS_SECRET_KEY: jklqjdiejklqjdioekijde
# Use this variable to set a timezone for the Paperless Docker containers. If not specified, defaults to UTC.
      #PAPERLESS_TIME_ZONE: Germany/Berlin
# The default language to use for OCR. Set this to the language most of your
# documents are written in.
      #PAPERLESS_OCR_LANGUAGE: ger

volumes:
  data:
  media:
  pgdata:

Alles anzeigen

Unfortunately after the stack is deployed it shows me that the container is running but unhealthy in Portainer. I can't get access to the console, too.

Is there anything I have to change?

Would be great to get some support over here and get this Docker to work in OMV. Maybe there is even an easier was as with Portainer.

Thanks,

Chris

ChrisBuzz · 17. Dezember 2021

I am using xfs as filesystem on the drive i want to use for Time Machine.

Is it required to use btrfs to get the quota function working?

ChrisBuzz · 15. Dezember 2021

Hello folks,

I tried to integrate a quota to limit the space for my Time Machine Back Up via Mac.

For this I used the following description on Reddit and Threads out of the Forum that already described the solution:

HowTo make time machine backups on a samba fileserver without netatalk

Samba For Time Machine

My .com.apple.TimeMachine.quota.plist file has the following content:

Code

root@Speicher:/srv/dev-disk-by-label-Backupintern/Backupintern/TimeMachine/Christoph# cat .com.apple.TimeMachine.quota.plist 
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>GlobalQuota</key>
    <integer>300000000000</integer>
  </dict>
</plist>

After creating the file I made a SMB restart:

Code

systemctl restart smbd.service

and the file has the following rights: 644

But Time Machine on my Mac still shows me the whole 1.88TB. Of course I rebooted my Mac severals times and also connected the share again in the Time Machine settings.

Does anyone have an idea how to solve that?

Thanks...

ChrisBuzz · 10. Dezember 2021

Thanks, I think that solved my issues.

ChrisBuzz · 10. Dezember 2021

No, of course I ran the command in two seperate lines

I solved the FTP issues with the following commands:

Code

sudo apt-get install gnupg
sudo omv-salt deploy run omvextras

After a reboot I still receive some error messages which thought that I solved them already:

Spoiler anzeigen

Openmediavault, [10.12.2021, 19:38:35]:

Monitoring restart -- Connection failed nginx on the Tue, 07 Dec 2021 21:34:57 GMT

Tue, 07 Dec 2021 22:34:57

The system monitoring needs your attention.

Host: \Netzwerkspeicher

Date: Tue, 07 Dec 2021 22:34:57

Service: nginx

Event: Connection failed

Description: failed protocol test [HTTP] at [127.0.0.1]:80 [TCP/IP] -- HTTP error: Server returned status 500

This triggered the monitoring system to: restart

—

You have received this notification because you have enabled the system monitoring on this host.

To change your notification preferences, please go to the 'System | Notification' or 'System | Monitoring' page in the web interface.

Pending configuration changes on the Wed, 8 Dec 2021 08:35:51 +0100 (CET)

The configuration has been changed. You must apply the changes in order for them to take effect.

Monitoring alert -- Connection succeeded nginx on the Tue, 07 Dec 2021 21:37:43 GMT

Tue, 07 Dec 2021 22:37:43

The system monitoring needs your attention.

Host: \Netzwerkspeicher

Date: Tue, 07 Dec 2021 22:37:43

Service: nginx

Event: Connection succeeded

Description: connection succeeded to [127.0.0.1]:80 [TCP/IP]

This triggered the monitoring system to: alert

—

You have received this notification because you have enabled the system monitoring on this host.

To change your notification preferences, please go to the 'System | Notification' or 'System | Monitoring' page in the web interface.

CRON-APT error on Netzwerkspeicher [/etc/cron-apt/config] on the Wed, 8 Dec 2021 08:35:51 +0100 (CET)

CRON-APT RUN [/etc/cron-apt/config]: Wed Dec 8 07:37:24 CET 2021

CRON-APT SLEEP: 3492, Wed Dec 8 08:35:36 CET 2021

CRON-APT ACTION: 0-update

CRON-APT LINE: /usr/bin/apt-get update -o quiet=2

W: GPG error: http://ppa.launchpad.net/kyle1117/ppa/ubuntu cosmic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3028C3C96AD57103

E: The repository 'http://ppa.launchpad.net/kyle1117/ppa/ubuntu cosmic InRelease' is not signed.

Any ideas?

ChrisBuzz · 10. Dezember 2021

Code

sudo su - wget -O - https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install | bash

After using the command above I still get the error message after activating FTP

Any further ideas?

ChrisBuzz · 9. Dezember 2021

Sorry, but I don't know what to do.

Already installed omv-extras for OMV 5.

How can I move that to GitHub?

ChrisBuzz · 9. Dezember 2021

Hello folks,

seems that after upgrading to OMV 5 something went wrong with the FTP service.

I receive the follwing message after activating the service in the Web UI:

Code

Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color proftpd 2>&1' with exit code '1': Netzwerkspeicher:
----------
          ID: configure_proftpd_mod_core
    Function: file.managed
        Name: /etc/proftpd/proftpd.conf
      Result: True
     Comment: File /etc/proftpd/proftpd.conf updated
     Started: 22:22:27.477479
    Duration: 304.15 ms
     Changes:
              ----------
              diff:
                  ---
                  +++
                  @@ -43,56 +43,3 @@
                     </Limit>
                   </Directory>

                  -<IfModule mod_auth.c>
                  -  DefaultRoot /srv/ftp
                  -  MaxClients 5
                  -  MaxLoginAttempts 1
                  -  RequireValidShell on
                  -  # This option is useless because this is handled via the PAM
                  -  # pam_listfile.so module, so set it to 'off' by default.
                  -  UseFtpUsers off
                  -</IfModule>
                  -<IfModule mod_auth_pam.c>
                  -  AuthPAM on
                  -  AuthPAMConfig proftpd
                  -</IfModule>
                  -<IfModule mod_ban.c>
                  -  BanEngine off
                  -  BanControlsACLs all allow user root
                  -  BanLog /var/log/proftpd/ban.log
                  -  BanMessage Host %a has been banned
                  -  BanTable /run/proftpd/ban.tab
                  -</IfModule>
                  -<IfModule mod_ctrls.c>
                  -  ControlsEngine on
                  -  ControlsMaxClients 2
                  -  ControlsLog /var/log/proftpd/controls.log
                  -  ControlsInterval 5
                  -  ControlsSocket /run/proftpd/proftpd.sock
                  -</IfModule>
                  -<IfModule mod_ctrls_admin.c>
                  -  AdminControlsEngine off
                  -</IfModule>
                  -<IfModule mod_delay.c>
                  -  DelayEngine on
                  -</IfModule>
                  -<IfModule mod_facl.c>
                  -  FACLEngine on
                  -</IfModule>
                  -<IfModule mod_quotatab.c>
                  -  QuotaEngine off
                  -</IfModule>
                  -<IfModule mod_ratio.c>
                  -  Ratios off
                  -</IfModule>
                  -LoadModule mod_vroot.c
                  -<IfModule mod_vroot.c>
                  -  VRootEngine on
                  -  VRootLog /var/log/proftpd/vroot.log
                  -  VRootAlias "/srv/dev-disk-by-label-Backupintern/Backupintern/Eigene Dateien/Christoph/30 Back Ups/20 ioBroker/" "BackUpioBroker"
                  -</IfModule>
                  -<IfModule mod_wrap.c>
                  -  TCPAccessFiles /etc/hosts.allow /etc/hosts.deny
                  -  TCPAccessSyslogLevels info warn
                  -  TCPServiceName ftpd
                  -</IfModule>
----------
          ID: configure_proftpd_mod_core_default_login_msg
    Function: file.managed
        Name: /srv/ftp/welcome.msg
      Result: True
     Comment: File /srv/ftp/welcome.msg is in the correct state
     Started: 22:22:27.782040
    Duration: 5.262 ms
     Changes:
----------
          ID: prereq_proftpd_mod_tls_certificates
    Function: salt.state
      Result: True
     Comment: States ran successfully. Updating Netzwerkspeicher.
     Started: 22:22:27.795195
    Duration: 6094.319 ms
     Changes:
              Netzwerkspeicher:
              ----------
                        ID: remove_ssl_certificates_crt
                  Function: module.run
                    Result: True
                   Comment: file.find: []
                   Started: 22:22:28.543992
                  Duration: 83.025 ms
                   Changes:
                            ----------
                            file.find:

Alles anzeigen

Can anyone help me with this?

Thanks

ChrisBuzz · 9. Dezember 2021

Already done. But still have the issue with activating FTP service.

ChrisBuzz · 9. Dezember 2021

Sorry but there is no feedback from the command:

dpkg -l | grep cloudshell

But I see some old plugins. Is this maybe the reason for the error message?

Code

dpkg -l | grep openm
ii  openmediavault                                              5.6.21-2                            all          openmediavault - The open network attached storage solution
ic  openmediavault-backup                                       4.0.6                               all          backup plugin for OpenMediaVault.
ii  openmediavault-flashmemory                                  4.2.2                               all          folder2ram plugin for OpenMediaVault
ii  openmediavault-keyring                                      1.0                                 all          GnuPG archive keys of the OpenMediaVault archive
ii  openmediavault-omvextrasorg                                 5.6.5                               all          OMV-Extras.org Package Repositories for OpenMediaVault
ii  openmediavault-usbbackup                                    5.0.9-1                             all          openmediavault USB/eSATA backup plugin

ChrisBuzz · 9. Dezember 2021

Alright, that worked but I still have the issue with activating the FTP plugin.

ChrisBuzz · 8. Dezember 2021

Thanks, I see those files in /etc/apt/sources.list.d

Code

armbian.list             openmediavault-kernel-backports.list
armbian.list.disabled         openmediavault.list
armbian.list.save         openmediavault.list.save
kyle1117-ubuntu-ppa-cosmic.list  openmediavault-local.list
omv-extras-org.bak         openmediavault-os-security.list

How can I edit these files?

ChrisBuzz · 8. Dezember 2021

Could you please tell which command to use?

Beiträge von ChrisBuzz

Postgresql DB writes permanently on HDD [Paperless-ng Docker]

HDD spin down not working after upgrade

HDD spin down not working after upgrade

Setting Up Paperless-NG with Portainer

Setting Up Paperless-NG with Portainer

Setting Up Paperless-NG with Portainer

Setting Up Paperless-NG with Portainer

Setting Up Paperless-NG with Portainer

Quota for Mac Time Machine via SMB

Quota for Mac Time Machine via SMB

Error messages: Check updates in Web GUI

Error messages: Check updates in Web GUI

Error messages: Check updates in Web GUI

Error messages: Check updates in Web GUI

Error after upgrade to OMV 5 activating FTP

Error messages: Check updates in Web GUI

Error messages: Check updates in Web GUI

Error messages: Check updates in Web GUI

Error messages: Check updates in Web GUI

Error messages: Check updates in Web GUI