When the Packman server was rebuild I tried around with different mirrors. Now I get the following:
localhost:~ # zypper se falkon
Refreshing service 'service'.
Problem retrieving the repository index file for service 'service':
File './repo/repoindex.xml' not found on medium 'http://mirrors.hust.edu.cn/packman/suse/openSUSE_Leap_15.2/?cookies=0'
Check if the URI is valid and accessible.
localhost:~ # zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
---+---------------------------+------------------------------------+---------+-----------+---------+----------+--------+--------------------------------------------------+--------
1 | libdvdcss | libdvdcss | No | ---- | ---- | 99 | rpm-md | http://opensuse-guip_15.2/ |
2 | openSUSE-Leap-15.2-1 | openSUSE-Leap-15.2-1 | No | ---- | ---- | 99 | rpm-md | hd:/?device=/dev/di_070326B92223F774-0:0-part2 |
3 | openSUSE_Leap_15.2 | Packman | Yes | (r ) Yes | Yes | 99 | rpm-md | https://ftp.halifaxsuse/openSUSE_Leap_15.2/ |
4 | repo-debug | Debug Repository | No | ---- | ---- | 99 | NONE | http://download.opetion/leap/15.2/repo/oss/ |
5 | repo-debug-non-oss | Debug Repository (Non-OSS) | No | ---- | ---- | 99 | NONE | http://download.opetion/leap/15.2/repo/non-oss/ |
6 | repo-debug-update | Update Repository (Debug) | No | ---- | ---- | 99 | NONE | http://download.opeeap/15.2/oss/ |
7 | repo-debug-update-non-oss | Update Repository (Debug, Non-OSS) | No | ---- | ---- | 99 | NONE | http://download.opeeap/15.2/non-oss/ |
8 | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opeeap/15.2/repo/non-oss/ |
9 | repo-oss | Main Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opeeap/15.2/repo/oss/ |
10 | repo-source | Source Repository | No | ---- | ---- | 99 | NONE | http://download.opeution/leap/15.2/repo/oss/ |
11 | repo-source-non-oss | Source Repository (Non-OSS) | No | ---- | ---- | 99 | NONE | http://download.opeution/leap/15.2/repo/non-oss/ |
12 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.ope.2/oss |
13 | repo-update-non-oss | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.ope.2/non-oss/ |
localhost:~ #
As you can see the zypper se command is interrupted by an error in URL http://mirrors.hust.edu.cn/packman/suse/openSUSE_Leap_15.2/ although this is no longer listed as packman repo. What is going on there and how can I fix this?
I have had strange results. Presumably, information is saved elsewhere – either in “/var/lib/zypp” or in “/var/cache/zypp”.
I have occasionally found it useful to remove all files for a repo from subdirectories of “/var/cache/zypp”, and then refresh the repo.
Thanks, nrickert. I must say I am at a loss. in /var/cache/zypp are 3 folders with the same subfolders:
inux:/var/cache/zypp # ls
packages raw solv
linux:/var/cache/zypp # cd packages
linux:/var/cache/zypp/packages #ls
libdvdcss openSUSE-Leap-15.2-1 repo-oss repo-update repo-update-non-oss
linux:/var/cache/zypp/packages #
The folder “raw” has additional openSUSE-Leap-15.2-1 and repo-non-oss. Nowhere is anything about packman. The other /var/lib/zypp:
linux:/var/lib/zypp # ls
AnonymousUniqueId AutoInstalled LastDistributionFlavor RequestedLocales
linux:/var/lib/zypp #
I tried the following:
linux:~ # locate repos| more
/etc/apparmor.d/abstractions/svn-repositories
/etc/zypp/repos.d
/etc/zypp/repos.d/libdvdcss.repo
/etc/zypp/repos.d/openSUSE-Leap-15.2-1.repo
/etc/zypp/repos.d/packman.repo
/etc/zypp/repos.d/repo-debug-non-oss.repo
/etc/zypp/repos.d/repo-debug-update-non-oss.repo
/etc/zypp/repos.d/repo-debug-update.repo
/etc/zypp/repos.d/repo-debug.repo
/etc/zypp/repos.d/repo-non-oss.repo
/etc/zypp/repos.d/repo-oss.repo
/etc/zypp/repos.d/repo-source-non-oss.repo
/etc/zypp/repos.d/repo-source.repo
/etc/zypp/repos.d/repo-update-non-oss.repo
/etc/zypp/repos.d/repo-update.repo
...
But when I go into /etc/zypp/repos.d the packman repo is not there:
linux:/etc/zypp/repos.d # ls
libdvdcss.repo repo-debug-update.repo repo-source.repo
openSUSE-Leap-15.2-1.repo repo-debug.repo repo-update-non-oss.repo
openSUSE_Leap_15.2.repo repo-non-oss.repo repo-update.repo
repo-debug-non-oss.repo repo-oss.repo
repo-debug-update-non-oss.repo repo-source-non-oss.repo
linux:/etc/zypp/repos.d #
I have no idea what next.
OK - the problem seems to be solved. In my first post here I have the line:
Problem retrieving the repository index file for service 'service'
so I went into the folder /etc/zypp/services.d:
localhost:~ # cd /etc/zypp/services.d/
localhost:/etc/zypp/services.d # ls
service.service
localhost:/etc/zypp/services.d # cat service.service
[service]
name=service
enabled=1
autorefresh=1
url = http://mirrors.hust.edu.cn/packman/suse/openSUSE_Leap_15.2/
type = ris
localhost:/etc/zypp/services.d # rm service.service
localhost:/etc/zypp/services.d # ls
localhost:/etc/zypp/services.d #
Now zypper works again as normal.
I’ve never really understood that “services” thing. I’m under the impression that it is mainly for SLE.
My “services.d” directory is empty.
Basically services are groups of repos; compare it to patterns and packages. A pristine Leap installation doesn’t use services. Zypper configuration files typically are:
**Leap:~ #** find /etc/zypp/ -type f
/etc/zypp/repos.d/openSUSE-Leap-15.2-1.repo
/etc/zypp/repos.d/repo-non-oss.repo
/etc/zypp/repos.d/repo-oss.repo
/etc/zypp/repos.d/repo-update-non-oss.repo
/etc/zypp/repos.d/repo-update.repo
/etc/zypp/repos.d/repo-debug.repo
/etc/zypp/repos.d/repo-debug-non-oss.repo
/etc/zypp/repos.d/repo-debug-update.repo
/etc/zypp/repos.d/repo-debug-update-non-oss.repo
/etc/zypp/repos.d/repo-source.repo
/etc/zypp/repos.d/repo-source-non-oss.repo
/etc/zypp/repos.d/packman.repo
/etc/zypp/repos.d/packman1.repo
/etc/zypp/repos.d/Kernel_stable.repo
/etc/zypp/repos.d/multimedia_libs.repo
/etc/zypp/repos.d/mozilla.repo
/etc/zypp/systemCheck
/etc/zypp/zypper.conf
/etc/zypp/zypp.conf
/etc/zypp/needreboot
**Leap:~ #**
All subfolders but repos.d are empty.
hcvv
March 11, 2021, 11:44am
#8
If I remember correctly, this is the second time that we encounter the phenomenon ‘service’. In both cases people (including me) did not see that the problem was about a service and not about a repo. Now I am getting curious where the services came from. How are they introduced in an openSUSE system where they normally are never used? Is this something that is buggy somewhere and that we should identify to get it fixed?
Hi
ls /etc/zypp/services.d/
Basesystem_Module_15_SP3_x86_64.service Python_2_Module_15_SP3_x86_64.service SUSE_Linux_Enterprise_Workstation_Extension_15_SP3_x86_64.service
Desktop_Applications_Module_15_SP3_x86_64.service SUSE_Linux_Enterprise_Desktop_15_SP3_x86_64.service
cat /etc/zypp/services.d/Basesystem_Module_15_SP3_x86_64.service
[Basesystem_Module_15_SP3_x86_64]
name=Basesystem_Module_15_SP3_x86_64
enabled=1
autorefresh=1
url = https://scc.suse.com/access/services/2130?credentials=Basesystem_Module_15_SP3_x86_64
type = ris
ttl_sec = 86400
lrf_dat = 1615364777
repo_1=Basesystem_Module_15_SP3_x86_64:SLE-Module-Basesystem15-SP3-Debuginfo-Pool
repo_1_enabled=0
repo_1_autorefresh=0
repo_2=Basesystem_Module_15_SP3_x86_64:SLE-Module-Basesystem15-SP3-Debuginfo-Updates
repo_2_enabled=0
repo_2_autorefresh=1
repo_3=Basesystem_Module_15_SP3_x86_64:SLE-Module-Basesystem15-SP3-Pool
repo_3_enabled=1
repo_3_autorefresh=0
repo_4=Basesystem_Module_15_SP3_x86_64:SLE-Module-Basesystem15-SP3-Source-Pool
repo_4_enabled=0
repo_4_autorefresh=0
repo_5=Basesystem_Module_15_SP3_x86_64:SLE-Module-Basesystem15-SP3-Updates
repo_5_enabled=1
repo_5_autorefresh=1
Quite a few more answers overnight to my thread. Since I deleted the service everything works OK again and I tried several zypper commands (zypper se, zypper up, etc) which before did not work before and which are working now again. And like nrickert writes - now my services.d folder too is empty. I thought the thread is closed. Nevertheless it would be good to know how this came about. All I can say is that I tried a few mirrors from packman and did a refresh. As I remember vaguely this Chinese repo did not work so I replaced it with the repo from Aachen. May be there is something in a log file I can look at - although I would not know which log file and what to look for. So I would need some further instruction. Since I started another thread here (update error) at least I have the exact date and time frame to look for.
hcvv
March 11, 2021, 10:05pm
#11
Now you say so, I belive I remeber the other case was also a service URL from China.
As you see from my post #8 above, I am also curious how such a service can enter into a set-up.