omv-release-upgrade via CLI.
omv-release-upgrade via CLI.
What about updating debian?
Is it better to do a fresh install or does it matter? I'm more accustomed to windows, and I always do fresh windows installs. IME updating windows OS is just asking for problems.. But I don't know how Linux handles OS updates. Recreating users and re-installing plugins is a bit of a pain, but doesn't really take that long so if the system will be more stable w/ a fresh install I'd be fine doing that.
Is it a better to wait for the official release, or is OMV 1.0 basically at release-state now?
Debian will be updated too with that command.
OpenMediaVault 1.0 is near release and already in a stable state.
I would upgrade first, and if you detect any errors that may relate to the upgrade reinstall the system. But in the actual state there should be no errors, unless you have some heavy custimizations.
Greetings
David
I did the Upgrade to days ago. It worked, but in mx. Opinion you should wait a few more days. There have been some errors during the debian update. And that has been a bit tricky to fix them.
Hi,
David's comment about OMV being very close to release made me update my machine. Also I I injured my leg last weeks and I will be on crutches for at least the weekend, so the thought that I'll have alll the time in the world to fix issues.
In the end the update seems to have went by without major problems. However it did not go trough everything automatically, so here a few lines that caught my attention. I would be glad to get your opinion on this.
omv-release-update finished with the following lines:
Errors were encountered while processing:
postfix
bsd-mailx
openmediavault
E: Sub-process /usr/bin/dpkg returned an error code (1)I fired up an apt-get upgrade and got:
[...]
3 not fully installed or removed.I continued and got greeted by the Postfix ncurses setup wizard, which I canceled.
apt-get upgrade continued with the following output. Line 19 and 22 show some "interesting" warnings:
Postfix configuration was untouched. If you need to make changes, edit
/etc/postfix/main.cf (and others) as needed. To view Postfix configuration
values, see postconf(1).
After modifying main.cf, be sure to run '/etc/init.d/postfix reload'.
Running newaliases
[ ok ] Stopping Postfix Mail Transport Agent: postfix.
[ ok ] Starting Postfix Mail Transport Agent: postfix.
Setting up bsd-mailx (8.1.2-0.20111106cvs-1) ...
Setting up openmediavault (1.0.14) ...
Installing new version of config file /etc/default/openmediavault ...
Installing new version of config file /etc/pam.d/openmediavault-webgui ...
Installing new version of config file /etc/pam.d/openmediavault ...
Installing new version of config file /etc/openmediavault/php.ini ...
Installing new version of config file /etc/init.d/openmediavault-engined ...
Installing new version of config file /etc/init.d/openmediavault-beep ...
Updating configuration ...
monit: action failed -- There is no service by that name
Reloading daemon monitor configuration: monit.
Stopping web server: apache2
The apache2 configtest failed, so we are trying to kill it manually. This is almost certainly suboptimal, so please make sure your system is working as you'd expect now! ... (warning).
... waiting .
update-rc.d: using dependency based boot sequencing
Reloading PHP5 FastCGI Process Manager: php5-fpm.
Restarting nginx: nginx.
Reloading daemon monitor configuration: monit.
Reloading ftp server: proftpd.
Processing triggers for openmediavault ...
Restarting engine daemon ...
Updating locale files ...
Updating file permissions ...I am unsure if using the old 0.5 postfix config has something to do with the monit error. However I send out a few test-messages by setting the HDD monitoring temperature to 25°C. Monitoring and email notifications worked fine.
So again: The update seems to have worked out alright, but whats your opinion on using the old postfix config? Since postfix is an wheezy package (not using a specific omv configuration), would you recommend to pull the wheezy config with a "apt-get --reinstall install postfix"?
Greets!
You need to remove the cd-rom line from your sources.list. PM sent.
Hi,
My upgrade to 1.0 didn't work:
1) omv-release-upgrade give me several errors:
Running newaliases
[ ok ] Stopping Postfix Mail Transport Agent: postfix.
[FAIL] Starting Postfix Mail Transport Agent: postfix[....] failure copying certificates ... failed!
invoke-rc.d: initscript postfix, action "restart" failed.
dpkg: error processing postfix (--configure):
subprocess installed post-installation script returned error exit status 1
....
dpkg: error processing bsd-mailx (--configure):
dependency problems - leaving unconfigured
....
dpkg: dependency problems prevent configuration of openmediavault:
openmediavault depends on postfix; however:
Package postfix is not configured yet.
openmediavault depends on bsd-mailx; however:
Package bsd-mailx is not configured yet.
....
dpkg: error processing openmediavault (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of openmediavault-omvextrasorg:
openmediavault-omvextrasorg depends on openmediavault (>= 1.0); however:
Package openmediavault is not configured yet.
...
dpkg: error processing openmediavault-omvextrasorg (--configure):
dependency problems - leaving unconfigured
Setting up usbutils (1:005-3) ...
...
Creating config file /etc/php5/fpm/php.ini with new version
Setting up php5-cgi (5.4.4-14+deb7u14) ...
Replacing config file /etc/php5/cgi/php.ini with new version
Action 'configtest' failed.
The Apache error log may have more information.
...
[....] Starting web server: apache2Syntax error on line 15 of /etc/apache2/openmediavault-webgui.d/default.conf:
Wrapper /var/www/openmediavault/php-fcgi cannot be accessed: (2)No such file or directory
Action 'start' failed.
The Apache error log may have more information.
failed!
...
Errors were encountered while processing:
postfix
bsd-mailx
openmediavault
openmediavault-omvextrasorg
E: Sub-process /usr/bin/dpkg returned an error code (1)2) after rebooting I have no GUI, only get: "Welcome to nginx!".
3) tried apt-get upgrade, and get:
Linux NAS5 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Sep 5 12:29:35 2014 from mouse.local
root@NAS5:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]?
Setting up postfix (2.9.6-2) ...
Postfix configuration was untouched. If you need to make changes, edit
/etc/postfix/main.cf (and others) as needed. To view Postfix configuration
values, see postconf(1).
After modifying main.cf, be sure to run '/etc/init.d/postfix reload'.
Running newaliases
[ ok ] Stopping Postfix Mail Transport Agent: postfix.
[ ok ] Starting Postfix Mail Transport Agent: postfix.
Setting up bsd-mailx (8.1.2-0.20111106cvs-1) ...
Setting up openmediavault (1.0.14) ...
Installing new version of config file /etc/default/openmediavault ...
Installing new version of config file /etc/pam.d/openmediavault ...
Installing new version of config file /etc/openmediavault/php.ini ...
Installing new version of config file /etc/init.d/openmediavault-engined ...
Installing new version of config file /etc/init.d/openmediavault-beep ...
Updating configuration ...
monit: action failed -- There is no service by that name
Reloading daemon monitor configuration: monit.
Stopping web server: apache2.
update-rc.d: using dependency based boot sequencing
Reloading PHP5 FastCGI Process Manager: php5-fpm.
Restarting nginx: nginx.
Reloading daemon monitor configuration: monit.
Reloading ftp server: proftpd.
Processing triggers for openmediavault ...
Restarting engine daemon ...
Updating locale files ...
Updating file permissions ...
Setting up openmediavault-omvextrasorg (1.0.4) ...
OK
OK
OK
OK
OK
OK
gpg: WARNING: digest algorithm MD5 is deprecated
gpg: please see http://www.gnupg.org/faq/weak-digest-algos.html for more information
OK
OK
OK
OK
Agent pid 8154
Identity added: /root/.ssh/id_rsa (/root/.ssh/id_rsa)
Identity added: /root/.ssh/id_dsa (/root/.ssh/id_dsa)
Processing triggers for openmediavault ...
Updating locale files ...
Updating file permissions ...
Restarting engine daemon ...
monit: action failed -- Other action already in progress -- please try again later
Restarting OpenMediaVault engine daemon: .omv-engined.
root@NAS5:~#4) Still no GUI, with the same message "Welcome to nginx!".
Any help would be appreciated and many thanks for a great NAS software.
Hi,
I have webGUI now, with:
apt-get install libapache2-mod-authnz-external
a2enmod authnz_external
service apache2 restart
After a SMB restart, everything seems to work fine.
Very strange since OMV 1.x uses nginx instead of apache.
Oops! I have fallowed a tip that came out of the forum search ([RESOLVED] apache won't start after sw upgrade), it was for OMV previous to 1.0.
I already fix this with:
service apache2 stop
update-rc.d -f apache2 remove
service nginx restart
It is working now with nginx, I have checked in the running processes, no apache now.
Should I run omv-firstaid to guarantee everything is fine? Or do you have any other suggestion?
Thanks for you help
If it is working, no need to use omv-firstaid.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!