Results 1 to 7 of 7

Thread: Error Yast

  1. #1

    Default Error Yast

    Hi,

    It seems that my package manager doesn't work well. When I start a software managing option out of the list from Software in Yast, I get an error all the time. It says (translated)

    'Cannot get access tot the Software Repositories

    Another process has access to your package database. The Package Manager is therefore unavailable.'

    Can someone help me further?

    Thanks!

  2. #2

    Default Re: Error Yast

    Normally that's just the updater applet being busy and tieing up the system.

    Solutions:

    1) Delete said applet. Real linux users don't need to be badgered for updates

    2) Wait till it's finished.

    3) In that error message, it probably gave you a process ID number. Open a terminal and type "sudo kill [that number]". Note that this option is potentially hazardous - blindly killing processes without finding out what they are first is silly. I'm sure someone can tell you how to find out what something is from its PID, but sadly, that person isn't me.

    Go for option one.

  3. #3
    Join Date
    Nov 2008
    Location
    India
    Posts
    122

    Default Re: Error Yast

    In terminal type
    Code:
    ps -A | grep update
    It'll give you output if the applet mentioned by confuseling is running. It's name as far I remember is something like 'gpk-update-icon'. The ouput will contain the PID of it also. Just kill the process from terminal as stated.

  4. #4

    Default Re: Error Yast

    Thank you for your support

    When I run the command in the terminal I get the following output

    leeuwtjes@linux-b8nf:~/Desktop/zooi> ps -A | grep update
    3463 ? 00:00:04 gpk-update-icon
    leeuwtjes@linux-b8nf:~/Desktop/zooi> help kill
    kill: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
    Send the processes named by PID (or JOBSPEC) the signal SIGSPEC. If
    SIGSPEC is not present, then SIGTERM is assumed. An argument of `-l'
    lists the signal names; if arguments follow `-l' they are assumed to
    be signal numbers for which names should be listed. Kill is a shell
    builtin for two reasons: it allows job IDs to be used instead of
    process IDs, and, if you have reached the limit on processes that
    you can create, you don't have to start a process to kill another one.
    leeuwtjes@linux-b8nf:~/Desktop/zooi> kill 3463
    leeuwtjes@linux-b8nf:~/Desktop/zooi> ps -A | grep update
    leeuwtjes@linux-b8nf:~/Desktop/zooi>

    So the process seems to be terminated. Unfortunately, I still get the same message - without a error code by the way.

    Got another idea?

  5. #5

    Default Re: Error Yast

    Without an error code, or without a PID?

    What happens when you run

    Code:
    su -
    zypper up

  6. #6

    Default Re: Error Yast

    I'am sorry but where does PID stand for? I get the message described earlier.

    Let me try your suggestion
    leeuwtjes@linux-b8nf:~> su -
    Wachtwoord:
    linux-b8nf:~ # zypper up
    A ZYpp transaction is already in progress. This means, there is another application using the libzypp library for package management running. All such applications must be closed before using this command.
    linux-b8nf:~ #
    linux-b8nf:~ # ps -A | grep update
    3427 ? 00:00:00 gpk-update-icon
    linux-b8nf:~ # kill 3427
    linux-b8nf:~ # zypper up
    A ZYpp transaction is already in progress. This means, there is another application using the libzypp library for package management running. All such applications must be closed before using this command.
    linux-b8nf:~ #

    So, what's next?

    I very much appreciate your support, thanks!

  7. #7
    Andy Sipowicz NNTP User

    Default Re: Error Yast

    > So, what's next?

    i GUESS there is a lock or temp file somewhere that is not getting
    deleted..

    you can consider this (may work, may not...might make it worse, i do
    not know):

    1. do the same grep & kill of update routine

    2. search /tmp for and delete (move or rename, depending on the level
    of caution you wish to exercise--this MAY break something) all files
    with "yast" in the title..

    3. give YaST another try

    if that works, it could be that your /tmp is hanging on to stuff that
    it should not...it is pretty easy to make sure it gets cleaned out
    correctly...use this forums advanced search to find several ways to do
    it safely (going into /tmp and manually deleting files willie-nillie
    on a running system is NOT the right way--i THINK just deleting all
    files with yast in the title will be safe once update has been killed..)

    --
    Andy Sipowicz

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •