[SOLVED] Turnkey-Fileserver - nach Installation kein Webdienst erreichbar

C

crally

Member
Aug 9, 2020
17
9
23
31
Hallo zusammen,

ich hoffe hier hat jemand etwas Erfahrung mit dem Turnkey File-Server.

Ich habe das Template heruntergeladen und in einen lxc installiert (privilegiert und unpriviligiert)

Installation und Erstinbetriebnahme klappen auch immer. Dann kommt die Anzeige, dass der Zugriff Webserver über Port 443 und das Webmin Panel über 12320/12321 erreichbar sind.
Aber das ist es leider nicht.... Es scheint gar kein Webserver mitinstalliert zu werden. Port 22, 139 und 445 für SMB sind offen. Aber sonst nichts.

Dachte eigtl. es wird alles mitinstalliert. Es war das Turnkey File-Server Template 16.0.1


Danke im Voraus


Code: 
root@Fileserver ~# ps -aux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.2 177636 10036 ?        Ss   13:10   0:01 /sbin/init
root        61  0.0  0.2  29576 11124 ?        Ss   13:10   0:00 /lib/systemd/systemd-journald
root        68  0.0  0.0   7684   216 ?        Ss   13:10   0:00 /usr/sbin/blkmapd
root        76  0.0  0.0   2460   800 ?        Ss   13:10   0:02 /usr/sbin/jitterentropy-rngd
_rpc       141  0.0  0.0   6820  3708 ?        Ss   13:10   0:00 /sbin/rpcbind -f -w
root       144  0.0  0.0 225820  3596 ?        Ssl  13:10   0:00 /usr/sbin/rsyslogd -n -iNONE
root       174  0.0  0.4 249920 19636 ?        Ssl  13:10   0:00 /usr/bin/python3 /usr/bin/fail2ban-server -xf start
root       175  0.0  0.3  34036 12676 ?        Ss   13:10   0:00 /usr/sbin/nmbd --foreground --no-process-group
root       214  0.0  0.0   8472  2632 ?        Ss   13:10   0:00 /usr/sbin/cron -f
root       227  0.0  0.0   5380  2012 console  Ss+  13:10   0:00 /sbin/agetty -o -p -- \u --noclear --keep-baud console 115200,38400,9600 l
root       228  0.0  0.0   5380  2028 pts/1    Ss+  13:10   0:00 /sbin/agetty -o -p -- \u --noclear --keep-baud tty2 115200,38400,9600 linu
root       262  0.0  0.1  15848  6628 ?        Ss   13:10   0:00 /usr/sbin/sshd -D
root       396  0.0  0.1  43468  4324 ?        Ss   13:10   0:00 /usr/lib/postfix/sbin/master -w
postfix    397  0.0  0.1  43488  7144 ?        S    13:10   0:00 pickup -l -t unix -u -c
postfix    398  0.0  0.1  43540  7288 ?        S    13:10   0:00 qmgr -l -t unix -u
root       405  0.0  0.4  49816 20940 ?        Ss   13:10   0:00 /usr/sbin/smbd --foreground --no-process-group
root       407  0.0  0.1  46664  5992 ?        S    13:10   0:00 /usr/sbin/smbd --foreground --no-process-group
root       408  0.0  0.1  46672  6008 ?        S    13:10   0:00 /usr/sbin/smbd --foreground --no-process-group
root       409  0.0  0.1  49800  6632 ?        S    13:10   0:00 /usr/sbin/smbd --foreground --no-process-group
root       419  0.0  0.0   9272  3460 pts/0    Ss   13:10   0:00 /bin/login -p --
root       436  0.0  0.1   5028  4368 pts/0    S    13:12   0:00 -bash
root       652  0.0  0.0   7636  2628 pts/0    R+   13:27   0:00 ps -aux
Click to expand...


EDIT:

Ist mit installiert.... aber startet nicht. Bin als root angemeldet, aber mir sollen Rechte fehlen. Bin noch nicht so 100% fit mit Linux.... kann mir da einer helfen?

Code: 
root@Fileserver /etc/init.d# /etc/init.d/apache2 start
[....] Starting apache2 (via systemctl): apache2.serviceJob for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.
failed!
root@Fileserver /etc/init.d# systemctl status apache2.service
* apache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2020-08-09 13:33:33 UTC; 5s ago
     Docs: https://httpd.apache.org/docs/2.4/
  Process: 1013 ExecStart=/usr/sbin/apachectl start (code=exited, status=226/NAMESPACE)

Aug 09 13:33:33 Fileserver systemd[1]: Starting The Apache HTTP Server...
Aug 09 13:33:33 Fileserver systemd[1013]: apache2.service: Failed to set up mount namespacing: Permission denied
Aug 09 13:33:33 Fileserver systemd[1013]: apache2.service: Failed at step NAMESPACE spawning /usr/sbin/apachectl: Permission denied
Aug 09 13:33:33 Fileserver systemd[1]: apache2.service: Control process exited, code=exited, status=226/NAMESPACE
Aug 09 13:33:33 Fileserver systemd[1]: apache2.service: Failed with result 'exit-code'.
Aug 09 13:33:33 Fileserver systemd[1]: Failed to start The Apache HTTP Server.
root@Fileserver /etc/init.d# journalctl -xe
-- Subject: A start job for unit apache2.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit apache2.service has begun execution.
--
-- The job identifier is 881.
Aug 09 13:33:33 Fileserver systemd[1013]: apache2.service: Failed to set up mount namespacing: Permission denied
Aug 09 13:33:33 Fileserver systemd[1013]: apache2.service: Failed at step NAMESPACE spawning /usr/sbin/apachectl: Permission denied
-- Subject: Process /usr/sbin/apachectl could not be executed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The process /usr/sbin/apachectl could not be executed and failed.
--
-- The error number returned by this process is ERRNO.
Aug 09 13:33:33 Fileserver systemd[1]: apache2.service: Control process exited, code=exited, status=226/NAMESPACE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit apache2.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 226.
Aug 09 13:33:33 Fileserver systemd[1]: apache2.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Aug 09 13:33:33 Fileserver systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: A start job for unit apache2.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit apache2.service has finished with a failure.
--
-- The job identifier is 881 and the job result is failed.
Click to expand...
 
Last edited:
Turnkey templates sind für privilegierte Container gedacht - immer als privilegiert erstellen.

Sonst für das Problem - versuch mal das 'Nesting' Feature zu aktivieren (in der GUI, Container auswählen, Options anklicken, Features)

Ich hoffe das hilft!
 
  • Like
Reactions: crally
Dankeschön, hatte dasselbe Problem. Das Nesting Feature war auch bei mir das Problem. Kann man irgendwo nachlesen, was das Feature bei Containern bewirkt?
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom