zypper: "bad media attach point" - all repositories

English Applications
#1

opensuse v12.1

I have searched for a solution to this problem and posted earlier here (http://forums.opensuse.org/english/get-technical-help-here/applications/471374-all-repositories-bad.html). So far no one has offered a working solution to this issue, here or elsewhere.

I have tried all of the suggestions made anywhere. For instance, removing and adding a repository is useless.

For some reason zypper is blocked on one computer here; no problem with the other computers, same OS version. I can access the repositories just fine with a browser, wget, ftp, etc. I have looked at the zypper conf files, <zypp.conf> and <zypper.conf>; both are completely default settings.

Big Repo Issues... :(
#2

I did a wild and crazy thing: I studied the zypper.log file. It was attempting to create and attach point in /var/adm/mount or /var/tmp. The wild and crazy part is that I deleted all of the “AP_" and "zypp.” directories in /var/tmp; there were 1000s.

After that online updates started working again.

Shouldn’t there be something to purge dead temporary directories?

#3

On 2012-02-19 22:26, jimoe666 wrote:
> Shouldn’t there be something to purge dead temporary directories?

Report bug in bugzilla.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#4

On 2012-02-19 21:56, jimoe666 wrote:
>
> opensuse v12.1
>
> I have searched for a solution to this problem and posted earlier here
> (http://tinyurl.com/773a9bd). So far no one has offered a working
> solution to this issue, here or elsewhere.

Well, I told you to look at the logs, you did not.
Now you did and found the cause.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#5

Well, I told you to look at the logs, you did not.
Now you did and found the cause.

I did. The logs did not tell me what the problem was, then or now. I still do not know.

I cleaned out a sh-tload of cruft in /var/tmp on the basis that “all this cr-p can’t be good (and I hope I don’t break anything)” and it started working.

I had done a similar cleanup of /var/adm/mount, the other directory mentioned in the logs, and it made no difference.

#6

Thanks! I was having the same error and following your advice also found tons of dir’s in /var/tmp. After doing a rm -rf in /var/tmp zypper started working. I was reluctantly considering a clean reinstall.

#7

On 2012-02-21 07:26, famewolf wrote:

> Thanks! I was having the same error and following your advice also
> found tons of dir’s in /var/tmp. After doing a rm -rf in /var/tmp
> zypper started working. I was reluctantly considering a clean reinstall.

You two should consider doing a bug report in Bugzilla.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#8

>> Thanks! I was having the same error and following your advice also
>> found tons of dir’s in /var/tmp. After doing a rm -rf in /var/tmp
>> zypper started working. I was reluctantly considering a clean reinstall.

>You two should consider doing a bug report in Bugzilla.

I think the real underlaying problem is easy – /var is full – hence if you clean out /var/tmp and if on the same fs als /var
it solves the issue.

What I generally at least do when troubleshooting is:

  1. check disk space - if full, see what logging van be deleted and clean /var/tmp if you know what you do.
  2. check logs

it’s not a bug. It’s system administration. I tested it by puttig a large file in /var/log so that 1% (reserved space) is left over.

/dev/mapper/system-var 1015704 980756 10700 99% /var
zypper fails with bad media attach point (it says – I cannot put my files, help me)

[now cleaned the fs by deleting the large testfile]

/dev/mapper/system-var 1015704 914640 76816 93% /var
zypper works again