Beiträge von jc-59
-
-
Hello,
Its's the first time I use Dockerfile to create my own docker image :OMV version : 6.9.10-4 (Shaitan)
openmediavaul-compose 6.11.3
DockerFROM nextcloud:apache RUN set -ex; \ \ apt update; \ apt install -y --no-install-recommends \ ffmpeg \ ; \ rm -rf /var/lib/apt/lists/*
But it failled
Code
Alles anzeigen#0 building with "default" instance using docker driver #1 [internal] load build definition from Dockerfile #1 transferring dockerfile: #1 transferring dockerfile: 439B done #1 DONE 0.6s #2 [internal] load .dockerignore #2 transferring context: 2B done #2 DONE 0.6s #3 [internal] load metadata for docker.io/library/nextcloud:apache #3 DONE 0.0s #4 [1/2] FROM docker.io/library/nextcloud:apache #4 CACHED #5 [2/2] RUN set -ex; apt update; apt install -y --no-install-recommends ffmpeg ; rm -rf /var/lib/apt/lists/* #5 0.653 + apt update #5 0.780 #5 0.780 WARNING: apt does not have a stable CLI interface. Use with caution in scripts. #5 0.780 #5 0.844 Ign:1 http://deb.debian.org/debian bookworm InRelease #5 0.845 Ign:2 http://deb.debian.org/debian bookworm-updates InRelease #5 0.846 Ign:3 http://deb.debian.org/debian-security bookworm-security InRelease #5 1.846 Ign:1 http://deb.debian.org/debian bookworm InRelease #5 1.846 Ign:2 http://deb.debian.org/debian bookworm-updates InRelease #5 1.847 Ign:3 http://deb.debian.org/debian-security bookworm-security InRelease #5 3.846 Ign:1 http://deb.debian.org/debian bookworm InRelease #5 3.846 Ign:2 http://deb.debian.org/debian bookworm-updates InRelease #5 3.847 Ign:3 http://deb.debian.org/debian-security bookworm-security InRelease #5 7.848 Err:1 http://deb.debian.org/debian bookworm InRelease #5 7.848 Temporary failure resolving 'deb.debian.org' #5 7.848 Err:2 http://deb.debian.org/debian bookworm-updates InRelease #5 7.848 Temporary failure resolving 'deb.debian.org' #5 7.849 Err:3 http://deb.debian.org/debian-security bookworm-security InRelease #5 7.849 Temporary failure resolving 'deb.debian.org' #5 7.853 Reading package lists... #5 7.881 Building dependency tree... #5 7.884 Reading state information... #5 7.887 All packages are up to date. #5 7.888 W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease Temporary failure resolving 'deb.debian.org' #5 7.888 W: Failed to fetch http://deb.debian.org/debian/dists/bookworm-updates/InRelease Temporary failure resolving 'deb.debian.org' #5 7.889 W: Failed to fetch http://deb.debian.org/debian-security/dists/bookworm-security/InRelease Temporary failure resolving 'deb.debian.org' #5 7.889 W: Some index files failed to download. They have been ignored, or old ones used instead. #5 7.891 + apt install -y --no-install-recommends ffmpeg #5 7.898 #5 7.898 WARNING: apt does not have a stable CLI interface. Use with caution in scripts. #5 7.898 #5 7.902 Reading package lists... #5 7.935 Building dependency tree... #5 7.938 Reading state information... #5 7.940 E: Unable to locate package ffmpeg
-
port 53 is the DNS port
-
I've stopped all other containers.
Portainer is the only one running
-
I've just followed NEXTCLOUD AIO WITHOUT PROXY guide
Of course i've stopped my nginx container
I have the same issue ...
Code
Alles anzeigen-1 }">Trying to fix docker.sock permissions internally... -1 }">Creating docker group internally with id 995 -1 }">Initial startup of Nextcloud All-in-One complete! -1 }">You should be able to open the Nextcloud AIO Interface now on port 8080 of this server! -1 }">E.g. https://internal.ip.of.this.server:8080 -1 }">If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via: -1 }">https://your-domain-that-points-to-this-server.tld:8443 -1 }">[Tue Dec 12 19:50:05.977747 2023] [mpm_event:notice] [pid 108:tid 140140975696712] AH00489: Apache/2.4.58 (Unix) OpenSSL/3.1.4 configured -- resuming normal operations -1 }">[Tue Dec 12 19:50:05.978351 2023] [core:notice] [pid 108:tid 140140975696712] AH00094: Command line: 'httpd -D FOREGROUND' -1 }">INF ts=1702410605.990367 msg=using provided configuration config_file=/Caddyfile config_adapter= -1 }">[12-Dec-2023 19:50:05] NOTICE: fpm is running, pid 113 -1 }">[12-Dec-2023 19:50:05] NOTICE: ready to handle connections -1 }">Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address -1 }">INF ts=1702410608.296198 msg=using provided configuration config_file=/Caddyfile config_adapter= -1 }">Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address -1 }">INF ts=1702410610.3765018 msg=using provided configuration config_file=/Caddyfile config_adapter= -1 }">Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address -1 }">INF ts=1702410612.459268 msg=using provided configuration config_file=/Caddyfile config_adapter=
-
-
Hello,
I followed NEXTCLOUD AIO WITH PROXY guideWhen I access to https://[SERVER_IP]:8080 , I have the following error
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request
Reason: DNS lookup failure for: localhost
Apache/2.4.58 (Unix) Server at 192.168.1.37 Port 8080
I'm searching since hours without any progress ...
Any hint ?Code
Alles anzeigenTrying to fix docker.sock permissions internally... Creating docker group internally with id 995 .+....+.....................+.....+++++++++++++++++++++++++++++++++++++++++++++*......+...+.+...........+.+..+...+...+.+.....+....+..............+.+......+........+.+.....+.+...+...+...+...........+.+.........+......+...+.....+.......+.....+...+.+.....+......+...+....+..+....+.........+..+....+............+..+.+++++++++++++++++++++++++++++++++++++++++++++*.+...+..........+...............+.........+...+............+..+....+.....+.......+..+.+.................+....+...............+...+...+..+......................+...+..+.............+..+...................+..+............+...+...+.......+.................+.+.....+.......+........+.+.....+.+..+......+.......+...+..............+..........+........+....+........+.......+++++ ...........+.+...+...........+....+...+.....+.......+..+.........+++++++++++++++++++++++++++++++++++++++++++++*...+++++++++++++++++++++++++++++++++++++++++++++*.....+............+...+.......+........+......+......+..................+................+......+.........+.....+.+...+..+.+.......................+....+..+.........+....+...+...+..+.........+....+......+...+........+...+....+.....+.+.........+..+.+..+.+............+.........+......+..+.............+........................+.........+..+...........................+.......+........+.......+......+.....+...+.+.....+......+.............+..+.........+...+...............+.+..+.............+......+.....+.........+.+...+..+.........+....+...........................+..................+...+..+.+................................+...+.........+...+...+.+...+...+........+....+..+........................+.+........+..............................+.+..............+...+....+.........+.....+....+++++ ----- Initial startup of Nextcloud All-in-One complete! You should be able to open the Nextcloud AIO Interface now on port 8080 of this server! E.g. https://internal.ip.of.this.server:8080 If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via: https://your-domain-that-points-to-this-server.tld:8443 INF ts=1702399161.3201852 msg=using provided configuration config_file=/Caddyfile config_adapter= Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address [Tue Dec 12 16:39:21.818691 2023] [mpm_event:notice] [pid 106:tid 140636202498888] AH00489: Apache/2.4.58 (Unix) OpenSSL/3.1.4 configured -- resuming normal operations [Tue Dec 12 16:39:21.818767 2023] [core:notice] [pid 106:tid 140636202498888] AH00094: Command line: 'httpd -D FOREGROUND' [12-Dec-2023 16:39:21] NOTICE: fpm is running, pid 112 [12-Dec-2023 16:39:21] NOTICE: ready to handle connections INF ts=1702399162.9584458 msg=using provided configuration config_file=/Caddyfile config_adapter= Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address INF ts=1702399165.159842 msg=using provided configuration config_file=/Caddyfile config_adapter= Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address INF ts=1702399166.261351 msg=using provided configuration config_file=/Caddyfile config_adapter= Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address INF ts=1702399168.5083659 msg=using provided configuration config_file=/Caddyfile config_adapter= Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address INF ts=1702399169.593769 msg=using provided configuration config_file=/Caddyfile config_adapter= Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address INF ts=1702399171.6911216 msg=using provided configuration config_file=/Caddyfile config_adapter= Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address INF ts=1702399174.7734778 msg=using provided configuration config_file=/Caddyfile config_adapter= Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address INF ts=1702399176.8854048 msg=using provided configuration config_file=/Caddyfile config_adapter= Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address INF ts=1702399177.9729917 msg=using provided configuration config_file=/Caddyfile config_adapter= Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address INF ts=1702399180.0512474 msg=using provided configuration config_file=/Caddyfile config_adapter= Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address INF ts=1702399183.1499505 msg=using provided configuration config_file=/Caddyfile config_adapter= Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address [Tue Dec 12 16:40:50.187040 2023] [proxy:error] [pid 125:tid 140636192271160] [client 192.168.1.144:54170] AH00898: DNS lookup failure for: localhost returned by / [Tue Dec 12 16:40:55.302920 2023] [proxy:error] [pid 125:tid 140636191136568] [client 192.168.1.144:54170] AH00898: DNS lookup failure for: localhost returned by /favicon.ico, referer: https://192.168.1.37:8080/ [Tue Dec 12 16:58:25.465817 2023] [proxy:error] [pid 125:tid 140636191566648] [client 192.168.1.144:54949] AH00898: DNS lookup failure for: localhost returned by / [Tue Dec 12 16:58:30.544355 2023] [proxy:error] [pid 125:tid 140636190849848] [client 192.168.1.144:54949] AH00898: DNS lookup failure for: localhost returned by /favicon.ico, referer: https://192.168.1.37:8080/
-
Hello,
I followed this thread to upgrade : Is there a guide to in place upgrade?
So i did
sudo omv-salt stage run deploy --> No error message
sudo omv-upgrade --> No error message
sudo omv-release-upgrade --> No error message
reboot
sudo omv-upgrade --> the upgrade stops with the following message
Setting up libnsl2:amd64 (1.3.0-2) ...
(Reading database ... 106284 files and directories currently installed.)
Preparing to unpack .../libpam-modules_1.4.0-9+deb11u1_amd64.deb ...
Redundant argument in sprintf at /usr/share/perl5/Debconf/Element/Noninteractive/Error.pm line 54, <GEN1> line 3.
Configuring libpam-modules
--------------------------
you are using pam_tally or pam_tally2 in your configuration
The pam_tally and pam_tally2 modules have been removed from PAM. You are
using one of these modules in your PAM configuration in /etc/pam.d. You must
remove the uses of these modules before PAM can be upgraded; including these
modules in your PAM configuration after the upgrade will stop users from
being able to log into the system.
Consider the pam_faillock module as a replacement for pam_tally.
dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.4.0-9+deb11u1_amd64.deb (--unpack):
new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2
Errors were encountered while processing:
/var/cache/apt/archives/libpam-modules_1.4.0-9+deb11u1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Now I can not relauch omv-upgrade ... command is unknown
What can I do ?
-
Thank you very much
-
That would mean the user doesn't exist. What about grep myuser /etc/passwd
I made a mistake while typing
getent passwd myuser
myuser:x:1005:100::/srv/dev-disk-by-label-save/home/myuser:/bin/sh
-
before
Bashls -la / total 72 drwxrwxr-x 20 root root 4096 févr. 5 10:28 . drwxrwxr-x 20 root root 4096 févr. 5 10:28 ..
after
Bashls -la / total 72 drwxr-xr-x 20 root root 4096 févr. 5 10:28 . drwxr-xr-x 20 root root 4096 févr. 5 10:28 ..
now I can open a sftp session for myuser
Thank you for your help
-
for the last command
getent passwd myuser
nothing is displayed
-
Code
sudo grep sftp /var/log/syslog ... Feb 6 16:23:15 OMV-SAVE systemd[1]: Started /bin/systemctl restart omv-sftp.service. Feb 6 16:23:15 OMV-SAVE systemd[1]: Stopping openmediavault sftp plugin service... Feb 6 16:23:15 OMV-SAVE systemd[1]: omv-sftp.service: Succeeded. Feb 6 16:23:15 OMV-SAVE systemd[1]: Stopped openmediavault sftp plugin service. Feb 6 16:23:15 OMV-SAVE systemd[1]: Started openmediavault sftp plugin service.
-
Code
sudo journalctl -u omv-sftp -- Logs begin at Sat 2022-02-05 11:10:49 CET, end at Sun 2022-02-06 16:54:48 CET. -- ... févr. 06 16:49:13 OMV-SAVE sshd[20529]: Accepted password for myuser from 192.168.1.37 port 43996 ssh2 févr. 06 16:49:13 OMV-SAVE sshd[20529]: pam_unix(sshd:session): session opened for user myuser by (uid=0) févr. 06 16:49:13 OMV-SAVE sshd[20537]: fatal: bad ownership or modes for chroot directory component "/" févr. 06 16:49:13 OMV-SAVE sshd[20529]: pam_unix(sshd:session): session closed for user myuser
-
Code
Alles anzeigensudo systemctl status omv-sftp ● omv-sftp.service - openmediavault sftp plugin service Loaded: loaded (/lib/systemd/system/omv-sftp.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2022-02-06 16:23:15 CET; 28min ago Main PID: 10850 (sshd) Tasks: 1 (limit: 4464) Memory: 2.0M CGroup: /system.slice/omv-sftp.service └─10850 /usr/sbin/sshd -D -f /etc/ssh/omv_sftp_config févr. 06 16:32:16 OMV-SAVE sshd[14213]: fatal: bad ownership or modes for chroot directory component "/" févr. 06 16:32:16 OMV-SAVE sshd[14151]: pam_unix(sshd:session): session closed for user myuser févr. 06 16:48:32 OMV-SAVE sshd[20278]: Accepted password for myuser from 192.168.1.149 port 64886 ssh2 févr. 06 16:48:32 OMV-SAVE sshd[20278]: pam_unix(sshd:session): session opened for user myuser by (uid=0) févr. 06 16:48:32 OMV-SAVE sshd[20294]: fatal: bad ownership or modes for chroot directory component "/" févr. 06 16:48:32 OMV-SAVE sshd[20278]: pam_unix(sshd:session): session closed for user myuser févr. 06 16:49:13 OMV-SAVE sshd[20529]: Accepted password for myuser from 192.168.1.37 port 43996 ssh2 févr. 06 16:49:13 OMV-SAVE sshd[20529]: pam_unix(sshd:session): session opened for user myuser by (uid=0) févr. 06 16:49:13 OMV-SAVE sshd[20537]: fatal: bad ownership or modes for chroot directory component "/" févr. 06 16:49:13 OMV-SAVE sshd[20529]: pam_unix(sshd:session): session closed for user myuser
-
groups myuser
myuser: users sftp-access
-
-
XML
Alles anzeigen<sftp> <enable>1</enable> <port>222</port> <passwordauthentication>1</passwordauthentication> <pubkeyauthentication>0</pubkeyauthentication> <allowgroups>1</allowgroups> <rsyslog>1</rsyslog> <extraoptions></extraoptions> <shares> <share> <uuid>cd3fc02a-936e-4c9f-baa3-4cf7b5bb7334</uuid> <sharedfolderref>51d4e22f-e755-45b3-a09d-4fa45b6bc876</sharedfolderref> <username>myuser</username> </share> </shares> </sftp>
-
I'am able to connect to the server but only with root ...
with myuser, it's not working ...
any suggestions ?
-
I made a test to create a file in my shared folder ... I can see it also in /sftp/myfolder/myfolder directory
so the 2 folder are bind.
Ok know I have to find how to connect to the server