Results 1 to 6 of 6

Thread: Zypper failing?

  1. #1

    Default Zypper failing?

    I was looking through the logs with Grafana/Loki, and I keep getting this every few seconds in the zypper.log:

    Code:
    021-11-22 12:54:44    
    2021-11-22 11:16:47 <5> localhost(8921) [DEFINE_LOGGROUP] Exception.cc(log):166 MediaCurl.cc(evaluateCurlCode):641 THROW:    File '/media.1/media' not found on medium 'http://download.opensuse.org/update/leap/15.3/non-oss/'
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media] MediaCurl.cc(doGetDoesFileExist):803 perform code: 22 [ HTTP response code said error ]
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media++] MediaCurl.cc(doGetDoesFileExist):722 URL: http://download.opensuse.org/update/leap/15.3/non-oss/media.1/media
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media++] MediaCurl.cc(doGetDoesFileExist):712 /media.1/media
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media++] MediaCurl.cc(doGetFileCopyFile):1018 URL: http://download.opensuse.org/update/leap/15.3/non-oss/repodata/repomd.xml
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media++] MediaCurl.cc(doGetFileCopyFile):1008 /repodata/repomd.xml
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media] MediaCurl.cc(doGetDoesFileExist):803 perform code: 0 [ No error ]
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media++] MediaCurl.cc(doGetDoesFileExist):722 URL: http://download.opensuse.org/update/leap/15.3/non-oss/repodata/repomd.xml
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media++] MediaCurl.cc(doGetDoesFileExist):712 /repodata/repomd.xml
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media++] MediaCurl.cc(setupEasy):351 Proxy: libcurl may look into the environment
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media++] MediaCurl.cc(setupEasy):350 Proxy: not explicitly set
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media] MediaCurl.cc(MediaCurl):77 MediaCurl::MediaCurl(http://download.opensuse.org/update/leap/15.3/non-oss/, )
    Looks like something is going wrong with the Zypper update(?) How can I fix it? Thanks.

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    30,990

    Default Re: Zypper failing?

    Do you mean that you are not even running any zypper command and nevertheless are getting these logs?
    Henk van Velden

  3. #3
    Join Date
    Jun 2008
    Location
    East of Podunk
    Posts
    33,260
    Blog Entries
    15

    Default Re: Zypper failing?

    Quote Originally Posted by ElToro66 View Post
    I was looking through the logs with Grafana/Loki, and I keep getting this every few seconds in the zypper.log:

    Code:
    021-11-22 12:54:44    
    2021-11-22 11:16:47 <5> localhost(8921) [DEFINE_LOGGROUP] Exception.cc(log):166 MediaCurl.cc(evaluateCurlCode):641 THROW:    File '/media.1/media' not found on medium 'http://download.opensuse.org/update/leap/15.3/non-oss/'
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media] MediaCurl.cc(doGetDoesFileExist):803 perform code: 22 [ HTTP response code said error ]
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media++] MediaCurl.cc(doGetDoesFileExist):722 URL: http://download.opensuse.org/update/leap/15.3/non-oss/media.1/media
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media++] MediaCurl.cc(doGetDoesFileExist):712 /media.1/media
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media++] MediaCurl.cc(doGetFileCopyFile):1018 URL: http://download.opensuse.org/update/leap/15.3/non-oss/repodata/repomd.xml
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media++] MediaCurl.cc(doGetFileCopyFile):1008 /repodata/repomd.xml
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media] MediaCurl.cc(doGetDoesFileExist):803 perform code: 0 [ No error ]
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media++] MediaCurl.cc(doGetDoesFileExist):722 URL: http://download.opensuse.org/update/leap/15.3/non-oss/repodata/repomd.xml
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media++] MediaCurl.cc(doGetDoesFileExist):712 /repodata/repomd.xml
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media++] MediaCurl.cc(setupEasy):351 Proxy: libcurl may look into the environment
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media++] MediaCurl.cc(setupEasy):350 Proxy: not explicitly set
        
    2021-11-22 12:54:44    
    2021-11-22 11:16:47 <1> localhost(8921) [zypp::media] MediaCurl.cc(MediaCurl):77 MediaCurl::MediaCurl(http://download.opensuse.org/update/leap/15.3/non-oss/, )
    Looks like something is going wrong with the Zypper update(?) How can I fix it? Thanks.
    Hi
    Can you log into the container and run the command `zypper ref -f` does it really need to have the non-oss repo active?
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  4. #4

    Default Re: Zypper failing?

    Quote Originally Posted by hcvv View Post
    Do you mean that you are not even running any zypper command and nevertheless are getting these logs?
    Yes. Well, I am running automatic updates as per https://www.michelebologna.net/2019/...an-and-ubuntu/, but not zypper from the command line.

  5. #5
    Join Date
    Jun 2008
    Location
    East of Podunk
    Posts
    33,260
    Blog Entries
    15

    Default Re: Zypper failing?

    Quote Originally Posted by ElToro66 View Post
    Yes. Well, I am running automatic updates as per https://www.michelebologna.net/2019/...an-and-ubuntu/, but not zypper from the command line.
    Hi
    I suspect a repository key has changed and needs accepting, hence the need to log in and check.....
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  6. #6

    Thumbs up Re: Zypper failing?

    Quote Originally Posted by malcolmlewis View Post
    Hi
    Can you log into the container and run the command `zypper ref -f` does it really need to have the non-oss repo active?
    It's a bare-metal installation. Fixed a wrong link and a missing key to a repository, ran an update and did a reboot. Running `zypper ref -f`, I now get:

    Code:
    > sudo zypper ref -f
    Forcing raw metadata refresh
    Retrieving repository 'Grafana OSS' metadata .......................................................[done]
    Forcing building of repository cache
    Building repository 'Grafana OSS' cache ............................................................[done]
    Forcing raw metadata refresh
    Retrieving repository 'Non-OSS Repository' metadata ................................................[done]
    Forcing building of repository cache
    Building repository 'Non-OSS Repository' cache .....................................................[done]
    Forcing raw metadata refresh
    Retrieving repository 'Main Repository' metadata ...................................................[done]
    Forcing building of repository cache
    Building repository 'Main Repository' cache ........................................................[done]
    Forcing raw metadata refresh
    Retrieving repository 'Main Update Repository' metadata ............................................[done]
    Forcing building of repository cache
    Building repository 'Main Update Repository' cache .................................................[done]
    Forcing raw metadata refresh
    Retrieving repository 'Update Repository (Non-Oss)' metadata .......................................[done]
    Forcing building of repository cache
    Building repository 'Update Repository (Non-Oss)' cache ............................................[done]
    Forcing raw metadata refresh
    Retrieving repository 'Tools for log analysis (openSUSE_Leap_15.3)' metadata .......................[done]
    Forcing building of repository cache
    Building repository 'Tools for log analysis (openSUSE_Leap_15.3)' cache ............................[done]
    All repositories have been refreshed.
    I am not getting any more errors in the log, so it seems that was it. Thanks for the input.

    As for non-oss; I am not sure whether non-oss is needed. I suppose it was added to the repos for a reason...

Tags for this Thread

Posting Permissions

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