update not possible anymore

mutosan · 8. Dezember 2015

Hello

I dont know why I get this error. Can anyone tell me what to do, because I cant update OMV anymore.
Failed to execute command 'export LANG=C; apt-get update 2>&1': E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable) E: Unable to lock directory /var/lib/apt/lists/

thx

mutosan · 8. Dezember 2015

root@ghostmedia:/media/9d489468-f1f8-4361-b933-5d17efe0e1a0/plexmediaserver# dpkg -l | grep ssh
ii libssh2-1:amd64 1.4.2-1.1+deb7u1 amd64 SSH2 client-side library
ii openssh-blacklist-extra 0.4.1+nmu1 all list of non-default blacklisted OpenSSH RSA and DSA keys
ii openssh-client 1:6.0p1-4+deb7u2 amd64 secure shell (SSH) client, for secure access to remote machines
ii openssh-server 1:6.0p1-4+deb7u2 amd64 secure shell (SSH) server, for secure access from remote machines
ii sshfs 2.4-1 amd64 filesystem client based on SSH File Transfer Protocol

and:

Code

root@ghostmedia:/media/9d489468-f1f8-4361-b933-5d17efe0e1a0/plexmediaserver# cat /etc/init.d/ssh
#! /bin/sh


### BEGIN INIT INFO
# Provides:             sshd
# Required-Start:       $remote_fs $syslog
# Required-Stop:        $remote_fs $syslog
# Default-Start:        2 3 4 5
# Default-Stop:
# Short-Description:    OpenBSD Secure Shell server
### END INIT INFO


set -e


# /etc/init.d/ssh: start and stop the OpenBSD "secure shell(tm)" daemon


test -x /usr/sbin/sshd || exit 0
( /usr/sbin/sshd -\? 2>&1 | grep -q OpenSSH ) 2>/dev/null || exit 0


umask 022


if test -f /etc/default/ssh; then
    . /etc/default/ssh
fi


. /lib/lsb/init-functions


if [ -n "$2" ]; then
    SSHD_OPTS="$SSHD_OPTS $2"
fi


# Are we running from init?
run_by_init() {
    ([ "$previous" ] && [ "$runlevel" ]) || [ "$runlevel" = S ]
}


check_for_no_start() {
    # forget it if we're trying to start, and /etc/ssh/sshd_not_to_be_run exists
    if [ -e /etc/ssh/sshd_not_to_be_run ]; then
        if [ "$1" = log_end_msg ]; then
            log_end_msg 0 || true
        fi
        if ! run_by_init; then
            log_action_msg "OpenBSD Secure Shell server not in use (/etc/ssh/sshd_not_to_be_run)" || true
        fi
        exit 0
    fi
}


check_dev_null() {
    if [ ! -c /dev/null ]; then
        if [ "$1" = log_end_msg ]; then
            log_end_msg 1 || true
        fi
        if ! run_by_init; then
            log_action_msg "/dev/null is not a character device!" || true
        fi
        exit 1
    fi
}


check_privsep_dir() {
    # Create the PrivSep empty dir if necessary
    if [ ! -d /var/run/sshd ]; then
        mkdir /var/run/sshd
        chmod 0755 /var/run/sshd
    fi
}


check_config() {
    if [ ! -e /etc/ssh/sshd_not_to_be_run ]; then
        /usr/sbin/sshd $SSHD_OPTS -t || exit 1
    fi
}


export PATH="${PATH:+$PATH:}/usr/sbin:/sbin"


case "$1" in
  start)
        check_privsep_dir
        check_for_no_start
        check_dev_null
        log_daemon_msg "Starting OpenBSD Secure Shell server" "sshd" || true
        if start-stop-daemon --start --quiet --oknodo --pidfile /var/run/sshd.pid --exec /usr/sbin/sshd -- $SSHD_OPTS; then
            log_end_msg 0 || true
        else
            log_end_msg 1 || true
        fi
        ;;
  stop)
        log_daemon_msg "Stopping OpenBSD Secure Shell server" "sshd" || true
        if start-stop-daemon --stop --quiet --oknodo --pidfile /var/run/sshd.pid; then
            log_end_msg 0 || true
        else
            log_end_msg 1 || true
        fi
        ;;


  reload|force-reload)
        check_for_no_start
        check_config
        log_daemon_msg "Reloading OpenBSD Secure Shell server's configuration" "sshd" || true
        if start-stop-daemon --stop --signal 1 --quiet --oknodo --pidfile /var/run/sshd.pid --exec /usr/sbin/sshd; then
            log_end_msg 0 || true
        else
            log_end_msg 1 || true
        fi
        ;;


  restart)
        check_privsep_dir
        check_config
        log_daemon_msg "Restarting OpenBSD Secure Shell server" "sshd" || true
        start-stop-daemon --stop --quiet --oknodo --retry 30 --pidfile /var/run/sshd.pid
        check_for_no_start log_end_msg
        check_dev_null log_end_msg
        if start-stop-daemon --start --quiet --oknodo --pidfile /var/run/sshd.pid --exec /usr/sbin/sshd -- $SSHD_OPTS; then
            log_end_msg 0 || true
        else
            log_end_msg 1 || true
        fi
        ;;


  try-restart)
        check_privsep_dir
        check_config
        log_daemon_msg "Restarting OpenBSD Secure Shell server" "sshd" || true
        RET=0
        start-stop-daemon --stop --quiet --retry 30 --pidfile /var/run/sshd.pid || RET="$?"
        case $RET in
            0)
                # old daemon stopped
                check_for_no_start log_end_msg
                check_dev_null log_end_msg
                if start-stop-daemon --start --quiet --oknodo --pidfile /var/run/sshd.pid --exec /usr/sbin/sshd -- $SSHD_OPTS; then
                    log_end_msg 0 || true
                else
                    log_end_msg 1 || true
                fi
                ;;
            1)
                # daemon not running
                log_progress_msg "(not running)" || true
                log_end_msg 0 || true
                ;;
            *)
                # failed to stop
                log_progress_msg "(failed to stop)" || true
                log_end_msg 1 || true
                ;;
        esac
        ;;


  status)
        status_of_proc -p /var/run/sshd.pid /usr/sbin/sshd sshd && exit 0 || exit $?
        ;;


  *)
        log_action_msg "Usage: /etc/init.d/ssh {start|stop|reload|force-reload|restart|try-restart|status}" || true
        exit 1
esac


exit 0

Alles anzeigen

I also tried apt-get autoclean and clean and then apt-get update but no luck.

jroch74 · 8. Dezember 2015

Code

rm /var/lib/apt/lists/lock

mutosan · 8. Dezember 2015

Thanks for your answer. can you tell me, why it happened? removed it and tried to update over the omv gui. its searching now for about 5mins, ans still is searching.

mutosan · 8. Dezember 2015

seams there is more locked:

Code

root@ghostmedia:/var/lib/apt/lists# apt-get update
E: cant get lock /var/lib/apt/lists/lock - open (11: Die Ressource is not available)
E: the list /var/lib/apt/lists/ cant be locked.
root@ghostmedia:/var/lib/apt/lists#

rebooting and trying again

ryecoaaron · 8. Dezember 2015

Don't remove the lock. OMV checks for updates and pre-downloads the updates automatically. You can't have two apt processes running at the same time. Hence the lock. Rebooting or just waiting a while should solve the problem. Sometimes the lock is around for a while if there is a lot of large downloads needed.

mutosan · 8. Dezember 2015

still the same, cant update omv

ryecoaaron · 8. Dezember 2015

What is the output of: ps aux | grep apt

mutosan · 8. Dezember 2015

Code

root@ghostmedia:/# ps aux | grep apt
root      5613  0.0  0.0   4180   580 ?        S    13:40   0:00 sh -c export LANG=C; apt-get update 2>&1
root      5614  0.0  0.0  23860  2392 ?        S    13:40   0:00 apt-get update
root      5623  0.0  0.0  34100  2160 ?        S    13:40   0:00 /usr/lib/apt/methods/http
root      5624  0.0  0.0  23540  1748 ?        S    13:40   0:00 /usr/lib/apt/methods/file
root      5625  0.0  0.0  34008  2140 ?        S    13:40   0:00 /usr/lib/apt/methods/http
root      5626  0.0  0.0  34008  2148 ?        S    13:40   0:00 /usr/lib/apt/methods/http
root      5627  0.0  0.0  34100  2160 ?        S    13:40   0:00 /usr/lib/apt/methods/http
root      5628  0.0  0.0  34100  2160 ?        S    13:40   0:00 /usr/lib/apt/methods/http
root      5629  0.0  0.0  34100  2156 ?        S    13:40   0:00 /usr/lib/apt/methods/http
root      5631  0.0  0.0  23540  1720 ?        S    13:40   0:00 /usr/lib/apt/methods/copy
root     13199  0.0  0.0  10156   912 pts/0    S+   14:05   0:00 grep apt

Alles anzeigen

I can install OMV without losing my data right? just as a last option. Its a raid5

ryecoaaron · 8. Dezember 2015

You don't need to reinstall (hopefully). As root, execute the following:

kill -9 5613 5614 5623 5624 5625 5626 5627 5628 5629 5631
apt-get update

Is OMV installed on flash media?

mutosan · 8. Dezember 2015

no its normal 500GB momentus XT which has 2 or 4gb extra flash. a hybrid hd. Do you think that could be a problem? It wasnt in the past.
going to kill the numbers now thx for your help

mutosan · 8. Dezember 2015

thats strange. why cant my omv server resolve the names? I have not change anything concerning hostname or network.

ryecoaaron · 8. Dezember 2015

Do you have a static IP setup? If so, did you set a dns server?

mutosan · 8. Dezember 2015

internaly on my DHCP server, yes it has a static IP and yes I also put in the DNS server. In the past I never had such problems with resolving and so on.
OMV is in my DMZ, which runs on opnsense. im no pro in network setups and so on but I thought until today I did it right looks like I did not ill check on opensense if there is something wrong or changed.

mutosan · 8. Dezember 2015

Zitat von ryecoaaron

Don't remove the lock. OMV checks for updates and pre-downloads the updates automatically. You can't have two apt processes running at the same time. Hence the lock. Rebooting or just waiting a while should solve the problem. Sometimes the lock is around for a while if there is a lot of large downloads needed.

Concerning the locks. I did see your message far to late. allready deleted .../lock

ryecoaaron · 8. Dezember 2015

That's ok. I just wanted to say deleting the lock in general is a bad idea.

mutosan · 8. Dezember 2015

out of my eyes the setup is still okey (DHCP and dns forwarder). I started the update on the omv gui now, to see if it works there. its running now since about 20mins without any change think im going to reinstall omv.

ryecoaaron · 8. Dezember 2015

I wouldn't use the web interface until it is fixed. Did you try apt-get update after killing the processes?

mutosan · 8. Dezember 2015

Zitat von mutosan

thats strange. why cant my omv server resolve the names? I have not change anything concerning hostname or network.

I actually did but a bit cryptic. Right now there is only one process running but I still have the resolving issue, when trying to make apt-get update.
But I checked all settings and they should be right I think.

ryecoaaron · 8. Dezember 2015

Try echo "nameserver 8.8.8.8" > /etc/resolv.conf and try apt-get update again. Yes, this will change your resolv.conf but a reboot will reset it.

Jetzt mitmachen!