Topic: "cannot find a valid baseurl for repo: smeaddons"

[DragonDon]

Ok, I posted this topic earlier today, it was a rather large one detailing everything I did and it took a decent amount of time to put it all together.  Now it does not even show up at all.  So I'm going to keep this short without any of the steps I did.  You can safely assume that I tried them all, which is the truth.

Error message I get when I try to update yum

 "cannot find a valid baseurl for repo: smeaddons"

I scoured google and the SME wiki as well as the forums and not a single one of the proposed solutions worked.

I tried browsing the ibiblio link listed in the update file and it will not show in my browser.

So, why is the default url not work?  Meaning is there another url to use for updates?

[janet]

DragonDon

Please DO NOT create new threads on the same topic, it only spreads the information out and makes it difficult for "us" to follow what you have done etc.

Please give a link to the other thread.

You could try
yum clean all

[DragonDon]

Oh I wouldn't create a second thread thread if the first thread existed.  It somehow did not get posted to the board.  So there is no link.

I have tried that and no change.

[janet]

DragonDon

Click on the FAQ link at top of forums and read the Yum Updates section. Work through the info provided and report your results.
Please give a db output for that repository in question. Also provide the full command you use and the full error message.

We cannot read your mind to know everything you did, you have to tell us one by one each "fix" that you try, and quote all commands used verbatim please.

What version SME ?

[DragonDon]

Hi Mary,

You must be the mother of <insert favourite deity/saint> for the patience that you bring

Going with the 'general' section (as this specific error was not listed) I followed the "Yum doesn't seem to be working correctly. What do I do now?" section.

[root@chronias ~]# yum clean metadata
Loading "installonlyn" plugin
Loading "fastestmirror" plugin
Loading "protect-packages" plugin
Loading "smeserver" plugin
Cleaning up xml metadata
0 metadata files removed

[root@chronias ~]# yum clean all
Loading "installonlyn" plugin
Loading "fastestmirror" plugin
Loading "protect-packages" plugin
Loading "smeserver" plugin
Cleaning up Everything
0 headers removed
0 packages removed
0 metadata files removed
0 cache files removed
0 cache files removed

[root@chronias ~]# yum update
Loading "installonlyn" plugin
Loading "fastestmirror" plugin
Loading "protect-packages" plugin
Loading "smeserver" plugin
Setting up Update Process
Setting up repositories
Cannot find a valid baseurl for repo: smeaddons
Error: Cannot find a valid baseurl for repo: smeaddon

And the problem persists.

My question is should the 'baseurl' listed be browseable by a web browser?

Follwing said document mentioned earlier, I proceeded to the next listed step:

"To flush the up stream proxies, using wget, run:"


[root@chronias ~]# wget --cache=off http://apt.sw.be/fedora/3/en/i386/dag/repodata/filelists.xml.gz
--14:44:12--  http://apt.sw.be/fedora/3/en/i386/dag/repodata/filelists.xml.gz
           => `filelists.xml.gz'
Resolving apt.sw.be... 193.1.193.67
Connecting to apt.sw.be|193.1.193.67|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2,094,612 (2.0M) [application/x-gzip]

100%[====================================>] 2,094,612    365.23K/s    ETA 00:00

14:44:26 (279.59 KB/s) - `filelists.xml.gz' saved [2094612/2094612]

(to save this from being an overly lengthy quote, the wget commands were successful)

wget --cache=off http://apt.sw.be/fedora/3/en/i386/dag/repodata/filelists.xml.gz
wget --cache=off http://apt.sw.be/fedora/3/en/i386/dag/repodata/primary.xml.gz
wget --cache=off http://apt.sw.be/fedora/3/en/i386/dag/repodata/repomd.xml

I then ran the yum update.

[root@chronias ~]# yum update
Loading "installonlyn" plugin
Loading "fastestmirror" plugin
Loading "protect-packages" plugin
Loading "smeserver" plugin
Setting up Update Process
Setting up repositories
Cannot find a valid baseurl for repo: smeaddons
Error: Cannot find a valid baseurl for repo: smeaddon

Also, can you be more specific in the request you state.  Saying "Please give a db output for that repository in question" is too generic for me to be able to know exactly what you are asking.  Good thing I know how to use a search.  The problem with stating it the way you did is that it gave me zero clue about how to do exactly what you wanted.  If you has said 'use the show command', THAT is more useful and I can learn how to construct the proper syntax.  This is a classic case of someone who knows a product but automatically assuming that another person understands the slang used when dealing with details of said product.

And yes, I have read the article, but I have a LONG way to go before memorizing such things.

[root@chronias ~]# db yum_repositories show smecontribs
smecontribs=repository
    EnableGroups=yes
    GPGCheck=yes
    MirrorList=http://distro.ibiblio.org/pub/linux/distributions/smeserver/mirrorlist/smecontribs-7
    Name=SME Server - contribs
    Visible=no
    status=disabled

My SME version is 7.5.1

[janet]

DragonDon

The problem with stating it the way you did is that it gave me zero clue about how to do exactly what you wanted.  If you has said 'use the show command', THAT is more useful and I can learn how to construct the proper syntax.  This is a classic case of someone who knows a product but automatically assuming that another person understands the slang used when dealing with details of said product.

It was a deliberate choice on my part NOT to quote the exact command syntax, so that you would be prompted to go look for it and learn something in the process. I was sure you would find it in the various documentation available. I steered you in the right direction and made you think for yourself to solve the db command syntax, good !

chronias
 db yum_repositories show smecontribs
smecontribs=repository
    EnableGroups=yes
    GPGCheck=yes
    MirrorList=http://distro.ibiblio.org/pub/linux/distributions/smeserver/mirrorlist/smecontribs-7
    Name=SME Server - contribs
    Visible=no
    status=disabled

OK on my SME 7.5.1 server I get the following, which shows that your db entry is missing the BaseURL, so it is understandable you get the error that you do.

db yum_repositories show smecontribs

smecontribs=repository
    BaseURL=http://mirror.contribs.org/pub/smeserver/releases/7/smecontribs/$basearch
    EnableGroups=yes
    GPGCheck=yes
    MirrorList=http://distro.ibiblio.org/pub/linux/distributions/smeserver/mirrorlist/smecontribs-7
    Name=SME Server - contribs
    Visible=no
    status=disabled

You can manually add it or delete that whole db entry for smecontribs, and then instruct SME to rebuild/recreate the default yum repository database entries. Again I'm sure there are instructions published re how to do that, so no need for me to tell you.

[haliparotin]

i have same error... please tell me what can i do?

[janet]

DragonDon & haliparotin

OK, this command will replace the missing entry (this command should be entered all on one line)

db yum_repositories setprop smecontribs BaseURL 'http://mirror.contribs.org/pub/smeserver/releases/7/smecontribs/$basearch'

followed by

signal-event yum-modify

Please review the output of the following command to understand how to use the db command syntax, and also read the various Howtos on the topic (link at top of forum) & the FAQ.

db

(Note - post edited to add single quotes)

[DragonDon]

Aww....just when I was enjoying my stress and found this:

http://ftp.surfnet.nl/ftp/pub/os/Linux/distr/smeserver/contribs/gordonr/devguide/html/devguide.html#SME-INTERNALS

Thanks Mary

[DragonDon]

Hi Mary,

Ok, so I followed your 'here's the answer' instructions and that still did not work.  I checked the smecontribs property and saw something that caught my eye.  Following your instructions, I noticed that the BaseURL showed as

[root@chronias ~]# db yum_repositories show smecontribs
smecontribs=repository
    BaseURL=http://mirror.contribs.org/pub/smeserver/releases/7/smecontribs/
    EnableGroups=yes
    GPGCheck=yes
    MirrorList=http://distro.ibiblio.org/pub/linux/distributions/smeserver/mirrorlist/smecontribs-7
    Name=SME Server - contribs
    Visible=no
    status=disabled

I noted that it was missing the "$basearch"

I decided to try something else.  Yes, dangerous I know but I am enjoying learning so why not experiment a little :O

I redid the setprop command but this time left out the "/$basearch" part.

[root@chronias ~]# db yum_repositories show smecontribs
smecontribs=repository
    BaseURL=http://mirror.contribs.org/pub/smeserver/releases/7/smecontribs
    EnableGroups=yes
    GPGCheck=yes
    MirrorList=http://distro.ibiblio.org/pub/linux/distributions/smeserver/mirrorlist/smecontribs-7
    Name=SME Server - contribs
    Visible=no
    status=disabled

This too failed.

I think that trying your " manually add it or delete that whole db entry for smecontribs, and then instruct SME to rebuild/recreate the default yum repository database entries" is probably a better way to go at this point.

Looking for those instructions now.

[haliparotin]

thank you for help... its that ok im using SME server 8 beta 6? i try to follow the command its still the same error?

[DragonDon]

Hi Mary,

Well, I found this previous example of the same thing:

http://forums.contribs.org/index.php?topic=44039.0

Very annoying that it didn't come up in any regular searches but at least it's here now

I followed:

To reset all your repos to correct default values do the following:

cd /home/e-smith/db/
mv yum_repositories yum_repositories.po
/etc/e-smith/events/actions/initialize-default-databases
expand-template /etc/yum.conf
signal-event post-upgrade; signal-event reboo

After I ran /etc/e-smith/events/actions/initialize-default-databases  I got the following response:

[root@chronias db]# /etc/e-smith/events/actions/initialize-default-databases
Migrating existing database yum_available
Migrating existing database accounts
Migrating existing database configuration
Migrating existing database yum_updates
Migrating existing database hosts
Migrating existing database networks
Migrating existing database mailpatterns
Migrating existing database domains
Migrating existing database yum_installed
Migrating existing database yum_repositories
WARNING in /etc/e-smith/db/yum_repositories/migrate//10GPG_and_Groups: Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/site_perl/esmith/config.pm line 263.
WARNING: Template processing succeeded for /: 1 fragment generated warnings
 at /usr/lib/perl5/site_perl/esmith/DB.pm line 459
Migrating existing database backups
Migrating existing database spamassassin

Event after a post-upgrade and reboot, the same error remains.

Wow...just, wow.....this setting is just not taking.  It seems that the "$basearch" will not stay in the config file.

[janet]

DragonDon

If it is not working as supposed to, even after following recommended procedures, then I suggest you lodge a bug report at bugzilla.
Put all the pertinent information in that bug report rather than just linking to this forum post.
The devs are busy and the least work possible you give them, then the better chance you have of getting this resolved.
Thanks

[janet]

haliparotin

its that ok im using SME server 8 beta 6?

Please refer to the SME 8 pages for specific details re SME 8 beta, linked from the main contribs.org page.

[CharlieBrady]

OK on my SME 7.5.1 server I get the following, which shows that your db entry is missing the BaseURL, so it is understandable you get the error that you do.

No, this is not true. If MirrorList appears, then BaseURL is ignored. "cannot find a valid baseurl' means that the mirror url was not reachable, or did not produce usable output.

Moreover, you are looking at 'smecontribs' settings, when the error message reports an issue with 'smeaddons'.

[CharlieBrady]

OK, this command will replace the missing entry

db yum_repositories setprop smecontribs BaseURL http://mirror.contribs.org/pub/smeserver/releases/7/smecontribs/$basearch

No, that command will not do what you want it to do. Because you do not have the URL enclosed in single quotes '', the shell will replace '$basearch' with the value of the 'basearch' shell variable - IOW, with nothing. So BaseURL will be set to http://mirror.contribs.org/pub/smeserver/releases/7/smecontribs/. But as previously noted, BaseURL will be ignored anyway.

[haliparotin]

i think maybe the site is DOWN? i try to search this link "http://mirror.contribs.org/pub/smeserver/releases/7/smecontribs/" the error is 404 Not Found..

[DragonDon]

Charlie,

You have helped point us in the right direction but being part of the dev team, you have not made any suggestions on how to go forward.

Are you in agreement with Mary for filing a bug report on this?  Or do you have anything else we can try?

[janet]

DragonDon,
 
Thanks Charlie

DragonDon
Try this (with single quotes)

db yum_repositories setprop smecontribs BaseURL 'http://mirror.contribs.org/pub/smeserver/releases/7/smecontribs/$basearch'
followed by
signal-event yum-modify

[DragonDon]

Done but the results are the same.

I guess you figured it out that by now, I have this knack for finding problems that tend to be unique and despite 99% of the rest of the solutions working, it doesn't for me

What is the difference between smeaddons and smecontribs?

[CharlieBrady]

You have helped point us in the right direction but being part of the dev team, you have not made any suggestions on how to go forward.

The dev team identifies and fixes problems which are reported via the bug tracker.

[cactus]

i think maybe the site is DOWN? i try to search this link "http://mirror.contribs.org/pub/smeserver/releases/7/smecontribs/" the error is 404 Not Found..

That is because you are using the wrong URL. Why did you put /pub/ in there? It is not supposed to be there.

If you not already did so, you should restore your default repository settings using the instruction in the wiki: http://wiki.contribs.org/Adding_Software#Restoring_Default_Yum_Repositories

After that you should be OK. If that does not work as expected or you observer strange things as you seem to do you should file a bug report instead of keep posting over and over in the forums.

[DragonDon]

That is because you are using the wrong URL. Why did you put /pub/ in there? It is not supposed to be there.

If you not already did so, you should restore your default repository settings using the instruction in the wiki: http://wiki.contribs.org/Adding_Software#Restoring_Default_Yum_Repositories

After that you should be OK. If that does not work as expected or you observer strange things as you seem to do you should file a bug report instead of keep posting over and over in the forums.

Two things:

1/ WE as users don't PUT anything there.  Whoever programed the software did.

2/  "If that does not work as expected or you observer strange things"  Until we ask here to verify that it is NOT something we have done, questions will be kept on being asked.  It is ludicrous to ask to file a bug report at every little thing.  Especially if using SME is new and the behaviour isn't as expected because the behaviour isn't documented.

So, to be clear.  How should we proceed?  Should we just file a bug report every time 'something doesn't work', or ask here first and possibly get an answer that wasn't obvious from a Google Search?

[cactus]

1/ WE as users don't PUT anything there.  Whoever programed the software did.

No, wrong, users do install contribs and modify configuration settings, they also influence functionality and file configuration content by this.

2/  "If that does not work as expected or you observer strange things"  Until we ask here to verify that it is NOT something we have done, questions will be kept on being asked.  It is ludicrous to ask to file a bug report at every little thing.  Especially if using SME is new and the behaviour isn't as expected because the behaviour isn't documented.

Diagnosis of functionality that is not behaving as expected is done in the bugtracker as it is a far better suitable tool for the developers to do that. If you want something fixed or diagnosed and are adviced to take it to the bugtracker, please do so, instead of writing posts like the previous.

So, to be clear.  How should we proceed?  Should we just file a bug report every time 'something doesn't work', or ask here first and possibly get an answer that wasn't obvious from a Google Search?

No, but you should file a bug for this particular issue and all other problems with SME Server that causes the software installed from a CD-ROM to malfunction. A message instructiong you to do so is displayed at the top every time you post a message:

Don't report problems here - Please report bugs and potential bugs in the bug tracker

The forums are meant for discussion, best practices and social contact, the bugtracker is for diagnosing issues, documenting fixes and the like.

[DragonDon]

No, wrong, users do install contribs and modify configuration settings, they also influence functionality and file configuration content by this.

I didn't and guess what, that /pub/ is there.  So, a bug report on that then?

Diagnosis of functionality that is not behaving as expected is done in the bugtracker as it is a far better suitable tool for the developers to do that. If you want something fixed or diagnosed and are adviced to take it to the bugtracker, please do so, instead of writing posts like the previous.

Duly noted.

No, wrong, users do install contribs and modify configuration settings, they also influence functionality and file configuration content by this.

I didn't and guess what, that /pub/ is there.  So, a bug report on that then?

No, but you should file a bug for this particular issue and all other problems with SME Server that causes the software installed from a CD-ROM to malfunction. A message instructiong you to do so is displayed at the top every time you post a message:

The forums are meant for discussion, best practices and social contact, the bugtracker is for diagnosing issues, documenting fixes and the like.

Understood but until posts back and forth go far enough to understand that it's actually a bug and not simply 'just click here' to fix, sometimes it takes a few posts.  Thanks for the reply.