Many thanx Ryecoaaron! I took the third option cause I don't have a backup and I don't want to reinstall everything. It took some time figuring out how to rebuild a version of util-linux that would work and eventually I ended up with the version originally included in OMV: 2.20.1.
So everything is fine again! Thnx!
--
Henri.
Hello,
I updated util-linux to 2.26 and now omv won't mount my drives. The error during boot is:
/lib/x86_64-linux-gnu/libmount.so.1: version 'MOUNT_2.24' not found (required by mountpoint)
The error repeats many times and the version varies from 2.22 till 2.25.
It started after manually building and installing util-linux-2.26 because I needed a newer version of rtcwake.
How can I repair this mistake? The root filesystem is mount ro so I can't do much with it.
Any help?
Hi,
In Update manager I see there's an update for Plex Mediaserver. Curious about what changed I click on 'Changelog'. Instead of the changelog I get this message:
Zitat
Failed to execute command 'export LANG=C; apt-get --yes --force-yes --download-only --reinstall install 'plexmediaserver' 2>&1': Reading package lists... Building dependency tree... Reading state information... The following packages will be upgraded: plexmediaserver 1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. E : Could not get lock /var/cache/apt/archives/lock - open (11: Resource temporarily unavailable) E : Unable to lock directory /var/cache/apt/archives/
When I click on 'Details' for the error I get:
ZitatAlles anzeigen
Error #4000:
exception 'OMVException' with message 'Failed to execute command 'export LANG=C; apt-get --yes --force-yes --download-only --reinstall install 'plexmediaserver' 2>&1': Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be upgraded:
plexmediaserver
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
E
:
Could not get lock /var/cache/apt/archives/lock - open (11: Resource temporarily unavailable)
E
:
Unable to lock directory /var/cache/apt/archives/
' in /usr/share/openmediavault/engined/rpc/apt.inc:392
Stack trace:
#0 [internal function]: OMVRpcServiceApt->getChangeLog(Array, Array)
#1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#2 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('getChangeLog', Array, Array)
#3 /usr/sbin/omv-engined(500): OMVRpc::exec('Apt', 'getChangeLog', Array, Array, 1)
#4 {main}
I've seen this before but didn't think much about it. Now it's annoying a bit and I'd like to see it fixed. It's possible this only occurs on de Plex updates. I see two other updates of which I can see the changelog without problem.
You were right, I had that enabled.
I remember enabeling every option on that page because some other update wasn't coming through. It's unchecked now, like it should be. Thnx!
The keyserver doesn't seem to respond sometime. I include most of the keys in omv-extras for this reason but the zfs key is just too big especially since most won't use zfs.
I don't use zfs... I use xfs though...
I managed to fix this myself:
apt-get install debian-keyring
gpg --keyserver pgp.mit.edu --recv-keys 7DFFA34D
gpg --armor --export 7DFFA34D | apt-key add -Answer found here: http://www.jamesrobertson.eu/b…ng-the-public-key-is.html
Thnx
(still don't understand what caused the problem)
This is the result: Oops...
Pakketlijsten worden ingelezen... Klaar
W: Er is een fout opgetreden bij de handtekeningcontrole. De pakketbron is niet bijgewerkt en de oude indexbestanden zullen worden gebruikt. GPG-fout: http://archive.zfsonlinux.org wheezy Release: De volgende ondertekeningen konden niet geverifieerd worden omdat de publieke sleutel niet beschikbaar is: NO_PUBKEY 8E234FB17DFFA34D
W: Ophalen van http://archive.zfsonlinux.org/debian/dists/wheezy/Release is mislukt
W: Some index files failed to download. They have been ignored, or old ones used instead.Want me to translate or can you figure it's something to do with signature, GPG and public keys...
Hope it makes sence to you 
================================================================================
= OpenMediaVault information
================================================================================
Release: 1.0.29
Codename: Kralizec
I have /etc/apt/apt.conf.d/99openmediavault-mkaptids so it should run.
Latest output is from 2 days ago though:
root@openmediavault:/etc# ls -al /var/lib/openmediavault/apt/
totaal 100
drwxr-xr-x 2 root root 4096 sep 19 16:35 .
drwxr-xr-x 6 root root 4096 okt 24 08:45 ..
-rw-r--r-- 1 root root 88099 okt 22 20:20 pluginsindex.json
-rw-r--r-- 1 root root 2 okt 22 20:20 upgradeindex.json
root@openmediavault:/etc#Sorry but it happened again. Seems omv-mkaptidx isn't a permanent fix for this.
I got notified of an update again but webgui doesn't show the updates.
Anybody else with this problem?
Tssss... Great! That fixed it! Thnx!
(awsome product btw...)
Hi,
I noticed this problem before. CRON-APT notifies me of available updates but when I go to Update Manager in webgui there is nothing there. Not even when I press 'Check' . Running the update in cli works thou. What could be wrong? Can't find anything in the logs 
that might indicate a problem...
Thanx!
Henri.
I'll migrate OMV 1.0 when it's officially released and look into putting together a plugin for Spotweb 
Hi Ben,
I had the same problems and solved it by putting Fietspomp's solutions together in the following spotweb.conf file:
Alias /spotweb /var/www/spotweb
<Directory /var/www/spotweb/>
Options FollowSymLinks
<FilesMatch \.php$>
FcgidWrapper /var/www/openmediavault/php-fcgi .php
SetHandler fcgid-script
Options +ExecCGI
</FilesMatch>
RewriteEngine on
RewriteCond %{REQUEST_URI} !api/
RewriteRule ^api/?$ index.php?page=newznabapi [QSA,L]
Options Indexes FollowSymLinks Multiviews
AllowOverride None
Order allow,deny
allow from all
</Directory>Like Fietspomp said: Save this file as spotweb.conf and place it in /etc/apache2/openmediavault-webgui.d, restart apache2 and you're done!
Well... not quite because OpenMediaVault web interface still crashes... Anybody any idea why that is?