Pinned "Welcome to nignx" or "It works!"

    • OMV 1.0
    • Update

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

    • "Welcome to nignx" or "It works!"

      Source Code

      1. omv-mkconf nginx
      2. omv-mkconf php5fpm
      3. service apache2 stop
      4. service php5-fpm restart
      5. update-rc.d -f apache2 remove
      6. service nginx restart

      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • Hi,

      how can I update Nginx package to a stable release?

      I have created a repository list according to Nginx homepage:
      deb codename nginx
      deb-src codename nginx

      I could now install stable release 1.8:

      Source Code

      1. root@vm104-nas:~# apt-cache policy nginx
      2. nginx:
      3. Installiert: 1.2.1-2.2+wheezy3
      4. Installationskandidat: 1.8.0-1~wheezy
      5. Versionstabelle:
      6. 1.8.0-1~wheezy 0
      7. 500 wheezy/nginx amd64 Packages
      8. 1.6.2-5~bpo70+1 0
      9. 100 wheezy-backports/main amd64 Packages
      10. *** 1.2.1-2.2+wheezy3 0
      11. 500 wheezy/main amd64 Packages
      12. 500 wheezy/updates/main amd64 Packages
      13. 100 /var/lib/dpkg/status[font='courier new,courier,monospace']
      Display All

      Source Code

      1. root@vm104-nas:~# apt-get install nginx
      2. Paketlisten werden gelesen... Fertig
      3. Abhängigkeitsbaum wird aufgebaut.
      4. Statusinformationen werden eingelesen.... Fertig
      5. Die folgenden Pakete werden aktualisiert (Upgrade):
      6. nginx
      7. 1 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
      8. Es müssen noch 0 B von 527 kB an Archiven heruntergeladen werden.
      9. Nach dieser Operation werden 1.021 kB Plattenplatz zusätzlich benutzt.
      10. (Lese Datenbank ... 48517 Dateien und Verzeichnisse sind derzeit installiert.)
      11. Vorbereitung zum Ersetzen von nginx 1.2.1-2.2+wheezy3 (durch .../nginx_1.8.0-1~wheezy_amd64.deb) ...
      12. Ersatz für nginx wird entpackt ...
      13. dpkg: Fehler beim Bearbeiten von /var/cache/apt/archives/nginx_1.8.0-1~wheezy_amd64.deb (--unpack):
      14. Versuch, »/etc/init.d/nginx« zu überschreiben, welches auch in Paket nginx-common 1.2.1-2.2+wheezy3 ist
      15. dpkg-deb: Fehler: Unterprozess einfügen wurde durch Signal (Datenübergabe unterbrochen (broken pipe)) getötet
      16. Fehler traten auf beim Bearbeiten von:
      17. /var/cache/apt/archives/nginx_1.8.0-1~wheezy_amd64.deb
      18. Creating index of upgradeable packages ...
      19. Creating index of openmediavault plugins ...
      20. E: Sub-process /usr/bin/dpkg returned an error code (1)[font='courier new,courier,monospace']
      Display All

      So, what prevents me from upgrading Nginx to release 1.8?

    • Hm... the problem is related to the dependency of package "nginx-common".
      However, I can neither remove this package nor update it.

      Wouldn't it make sense to decouple OpenMediaVault configuration files in Nginx from the common files provided by the Nginx package in order to allow the package update to a recent release.

      The update to latest Owncloud release is working.

    • OMV needs it. The debian packaging is different than the nginx repo. Another reason to not use it.

      The OMV config files are "decoupled" from the package but OMV needs nginx to serve the pages. It writes the config files assuming it will be serving pages using nginx 1.2. If you update to 1.8, the nginx config changes and may not work.
      omv 3.0.87 erasmus | 64 bit | 4.9 backport kernel | omvextrasorg 3.4.26 plugins source code and issue tracker -

      Please don't PM for support... Too many PMs!
    • I managed to install Nginx from wheezy-backports repository.
      Before installation I created a backup of /etc/nginx and recovered this backup after the installation completed.

      Now I'm running updated Nginx binary with original configuration files in /etc/nginx.

      Source Code

      1. ​root@vm104-nas:~# nginx -v
      2. nginx version: nginx/1.6.2
    • I knew 1.6 from the Debian Wheezy repo would be ok but you wanted to install 1.8 from a non-Debian Wheezy repo. Why do you want to upgrade? OMV 3.x will use 1.6.
      omv 3.0.87 erasmus | 64 bit | 4.9 backport kernel | omvextrasorg 3.4.26 plugins source code and issue tracker -

      Please don't PM for support... Too many PMs!
    • Hello, I have been running omv for a couple of years now, but did never fiddle too much with it. Never fiddled too much with Linux in general, but I know my way (the very basic stuff) around the CLI. I upgraded from 0.5 something, to 1.0 - or so I think... Anyway, I'm stuck with this message (from the title of the thread) when trying to access the webgui. Apparently my server seems to work fine - it has all the samba shares up and running, my plex server webgui is fine etc...

      I have tried the steps on top of the this thread with no luck. Rebooted the box also, no luck. I assume I am to write these lines in the CLI?

      Is there any solution to this? Yeah, ino... it doesn't take me many words here to expose that I'm a total noob when it comes to linux stuff. Hope I don't ask some stupid questions, or ask questions already answered - was not my intent at all, I just don't seem to get how to fix this...

      Also, if it is a solution - rather than spend time trying to fix this manually - can I just pull my storage HDDs from the system, reinstall from a usb stick or CD, and insert the HDDs again. What steps are required to actually get the HDDs up and running after a system rebuild like that?

      Ino.... ino... lots of questions here. It all comes down to the fact that I know very little of how linux and open media vault works other than on the "outside"

      I don't have any hurry getting the thing up and running again, as it seems it works fine just without a webgui - but if I need to reinstall the system somehow, I would appreciate very much an explaination how to deal with the RAID setup I have now, and how that can be put into a new system. Ooof, I'm not good at explaining - but I hope some of you gurus and other who have relevant advices understand what I'm trying to ask / say :)

      Thanks in advance for any good info in this!