Webinterface von Max2play nicht mehr erreichbar, stattdessen „Welcome to nginx“

Max2Play Home 2016 (en) Forums Max2Play on Raspberry PI Webinterface von Max2play nicht mehr erreichbar, stattdessen „Welcome to nginx“

This topic contains 1 reply, has 2 voices, and was last updated by  Heiner Moderator 3 weeks, 5 days ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • 26. October 2017 at 23:22 #32135

    Hallo,
    seit heute habe ich keinen Zugriff mehr auf das Webinterface von Max2play. Immer wenn ich es unter der bisher immer funktionierenden IP-Adresse öffnen möchte, erscheint nur „Welcome to nginx!“ auf einer ansonsten leeren Seite. Dasselbe Verhalten zeigen auch die unter /public eingereichteten eigenen Ebookserver COPS und BBS.
    Das System läuft ansonsten offenbar normal. Ich habe nichts geändert und bin ziemlich ratlos…

    Hier als Ergänzung noch die Einträge der error logs von apache:
    Error log:
    [Sun Oct 22 06:25:04 2017] [notice] Apache/2.2.22 (Debian) PHP/5.4.45-0+deb7u11 configured — resuming normal operations
    No LSB modules are available.
    /opt/max2play/dynamic_script.sh: line 3: echo: write error: Device or resource busy
    cat: /sys/class/gpio/gpio35/value: No such file or directory
    No LSB modules are available.
    /opt/max2play/dynamic_script.sh: line 3: echo: write error: Device or resource busy
    cat: /sys/class/gpio/gpio35/value: No such file or directory
    No LSB modules are available.
    /opt/max2play/dynamic_script.sh: line 3: echo: write error: Device or resource busy
    cat: /sys/class/gpio/gpio35/value: No such file or directory
    [Sun Oct 22 17:24:07 2017] [notice] caught SIGTERM, shutting down

    Und error log1:

    [Sun Oct 15 06:25:04 2017] [notice] Apache/2.2.22 (Debian) PHP/5.4.45-0+deb7u11 configured — resuming normal operations
    [Wed Oct 18 18:17:11 2017] [notice] Apache/2.2.22 (Debian) PHP/5.4.45-0+deb7u11 configured — resuming normal operations
    dpkg-query: package ‘dnsmasq’ is not installed and no information is available
    Use dpkg –info (= dpkg-deb –info) to examine archive files,
    and dpkg –contents (= dpkg-deb –contents) to list their contents.
    amixer: invalid option — ‘M’
    Invalid switch or option needs an argument.
    amixer: invalid option — ‘M’
    Invalid switch or option needs an argument.
    amixer: invalid option — ‘M’
    Invalid switch or option needs an argument.
    dpkg-query: package ‘dnsmasq’ is not installed and no information is available
    Use dpkg –info (= dpkg-deb –info) to examine archive files,
    and dpkg –contents (= dpkg-deb –contents) to list their contents.
    debconf: unable to initialize frontend: Dialog
    debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
    debconf: falling back to frontend: Readline
    debconf: unable to initialize frontend: Readline
    debconf: (This frontend requires a controlling tty.)
    debconf: falling back to frontend: Teletype
    dpkg-preconfigure: unable to re-open stdin:
    debconf: unable to initialize frontend: Dialog
    debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
    debconf: falling back to frontend: Readline
    debconf: unable to initialize frontend: Readline
    debconf: (This frontend requires a controlling tty.)
    debconf: falling back to frontend: Teletype
    insserv: script gmediarenderer: service gmediarender already provided!
    insserv: script gmediarenderer: service gmediarender already provided!
    Segmentation fault
    insserv: script gmediarenderer: service gmediarender already provided!
    insserv: script gmediarenderer: service gmediarender already provided!
    ioctl[RTL_IOCTL_HOSTAPD]: Invalid argument
    No LSB modules are available.
    /opt/max2play/dynamic_script.sh: line 3: echo: write error: Device or resource busy
    cat: /sys/class/gpio/gpio35/value: No such file or directory
    [Sun Oct 22 06:25:04 2017] [notice] Graceful restart requested, doing restart
    apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName

    • This topic was modified 3 weeks, 6 days ago by  ulip.
    27. October 2017 at 9:51 #32146

    Hi ulip,

    Hast du schon versucht, den Namen des Geräts zu ändern und damit drauf zuzugreifen?

    Bitte versuche den gmedia renderer zu deaktivieren um diesen als Fehlerquelle auszuschließen.

    Versuche außerdem, die genannten Server kurzzeitig auszuschalten, um diese als Fehlerquelle auszuschließen.

    Du kannst zudem noch die Maßnahmen durchführen, die hier genannt werden:

    https://www.nginx.com/blog/welcome-to-nginx-on-my-favourite-website/

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

Register here