Koozali.org: home of the SME Server

Contribs.org Forums => General Discussion => Topic started by: cyberwatcher on June 12, 2009, 12:19:31 PM

Title: cannot find a valid baseurl for repo: base
Post by: cyberwatcher on June 12, 2009, 12:19:31 PM

My network has been down for over a week because we move our office. Now I am getting the following Errors each time the mail server checks for updates.

Cannot Find a valid baseurl for repo: base

I have tried to run the following:
grep -r check4updates /etc/cron*

Also we are seeing:
Clam update failed
Cant connect to port 80 of host database.clamav.net

Is it possible that all the Database IP addresses used to reach out for updates are missing?
Title: Re: cannot find a valid baseurl for repo: base
Post by: Stefano on June 12, 2009, 12:26:40 PM
hi

did you check if your server can connect to internet?
did you check server's gateway?

Ciao
Stefano
Title: Re: cannot find a valid baseurl for repo: base
Post by: armand on June 12, 2009, 01:43:35 PM
Hi there,

I don't know if this is the right place, but I have allmost the same error:

"Cannot find a valid baseurl for repo: smeaddons
Error: Cannot find a valid baseurl for repo: smeaddons"

Internet connection is okay.

I've had this before, but got rid of it after an update........

Server is working okay. I'm watching the logs.

Regards,

Armand
Title: Re: cannot find a valid baseurl for repo: base
Post by: cyberwatcher on June 12, 2009, 02:08:16 PM
Yes it is connected to the Internet. It is sending and receiving mail just find. I know that I only allowed the IP addresses that were in the BASE URL file in via a policy from my firewall. I have since changed that to allow any to see if that makes a difference. That way I can find out if it has anything to do with my policy or not.
Title: Re: cannot find a valid baseurl for repo: base
Post by: Stefano on June 12, 2009, 02:12:08 PM
Yes it is connected to the Internet. It is sending and receiving mail just find. I know that I only allowed the IP addresses that were in the BASE URL file in via a policy from my firewall. I have since changed that to allow any to see if that makes a difference. That way I can find out if it has anything to do with my policy or not.

are you saying that you have a policy in your fw to permit traffic to ONE ip?
repositories are hosted on many server.. you should permit outgoing traffic from SME directed to port 80

Ciao
Stefano
Title: Re: cannot find a valid baseurl for repo: base
Post by: cyberwatcher on June 12, 2009, 03:23:19 PM
No I am using 15 or so. I have changed it over to any for now. I will have to see what happens.
Title: Re: cannot find a valid baseurl for repo: base
Post by: cactus on June 12, 2009, 07:24:30 PM
No I am using 15 or so. I have changed it over to any for now. I will have to see what happens.
If that does not work you may try and restore the default settings for your repositories by following these instructions:
http://wiki.contribs.org/Adding_Software#Restoring_Default_Yum_Repositories
Title: Re: cannot find a valid baseurl for repo: base
Post by: cactus on June 12, 2009, 07:25:50 PM
Hi there,

I don't know if this is the right place, but I have allmost the same error:

"Cannot find a valid baseurl for repo: smeaddons
Error: Cannot find a valid baseurl for repo: smeaddons"

Internet connection is okay.

I've had this before, but got rid of it after an update........

Server is working okay. I'm watching the logs.

Regards,

Armand
Perhaps, you could also follow above instruction and see if that resolves your issue, furthermore you need to check if your SME Server traffic to the outside world is not obstructed by any other gateways/firewalls.

Also make sure you follow instructions after updates to execute the reconfigure procedure either through server-manager or when doing updates from the command line by executing:
Code: [Select]
signal-event post-upgrade
signal-event reboot

Next time please report issues like that in the bugtracker and if you have already done so add your remarks there and only there to keep all communication in one place. Thanks in advance.
Title: Re: cannot find a valid baseurl for repo: base
Post by: armand on June 14, 2009, 10:47:25 PM
Thanks for reply Cactus, was gone for the week-end...
Yes I did all that the same day, as I had this before.
That's why I was watching my logs. Seemes to be okay.

And yes I know I have to use the bug tracker, it won't happen again.

Cheers 'n beers.

Armand
Title: Re: cannot find a valid baseurl for repo: base
Post by: cyberwatcher on June 20, 2009, 02:30:19 PM
I have since allowed ANY for my mail server allowing in all updates from all mirrors. I am not getting any errors now however I see the the cron daemon used to email me logs daily and I have not received any since the 16th. BELOW

Cron
Cannot find a valid baseurl for repo: smeaddons
Error: Cannot find a valid baseurl for repo: smeaddons
Error in sys.exitfunc:
Traceback (most recent call last):
  File "/usr/lib/python2.3/atexit.py", line 20, in _run_exitfuncs
    func(*targs, **kargs)
  File "plugins.py", line 159, in run
  File "/usr/lib/yum-plugins/smeserver.py", line 69, in close_hook
    os.unlink('/var/run/yum.status')
OSError: [Errno 2] No such file or directory: '/var/run/yum.status'

*************************************************************
This is the Current YUM log
2009-06-13 13:06:21.017445500 yum list updates status 256
2009-06-13 13:09:30.455187500 Cannot find a valid baseurl for repo: smeaddons
2009-06-13 13:09:30.455195500 Error: Cannot find a valid baseurl for repo: smeaddons
2009-06-13 13:09:30.509153500 yum grouplist updates status 256
2009-06-14 04:04:29.464218500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2009-06-14 04:04:29.528892500 yum list available status 51200
2009-06-14 04:04:29.963751500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2009-06-14 04:04:30.018743500 yum grouplist available status 51200
2009-06-14 04:04:30.467257500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2009-06-14 04:04:30.522320500 yum list installed status 51200
2009-06-14 04:04:30.946885500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2009-06-14 04:04:31.004566500 yum grouplist installed status 51200
2009-06-14 04:04:31.430020500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2009-06-14 04:04:31.485257500 yum list updates status 51200
2009-06-14 04:04:31.909489500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2009-06-14 04:04:31.968092500 yum grouplist updates status 51200
2009-06-15 04:03:38.362489500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2009-06-15 04:03:38.422700500 yum list available status 51200
2009-06-15 04:03:38.847632500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2009-06-15 04:03:38.902415500 yum grouplist available status 51200
2009-06-15 04:03:39.376177500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2009-06-15 04:03:39.434609500 yum list installed status 51200
2009-06-15 04:03:39.856006500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2009-06-15 04:03:39.912353500 yum grouplist installed status 51200
2009-06-15 04:03:40.339588500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2009-06-15 04:03:40.399417500 yum list updates status 51200
2009-06-15 04:03:40.818657500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2009-06-15 04:03:40.877044500 yum grouplist updates status 51200
2009-06-16 04:03:39.275129500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2009-06-16 04:03:39.337281500 yum list available status 51200
2009-06-16 04:03:39.760343500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2009-06-16 04:03:39.815292500 yum grouplist available status 51200
2009-06-16 04:03:40.268680500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2009-06-16 04:03:40.326047500 yum list installed status 51200
2009-06-16 04:03:40.750616500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2009-06-16 04:03:40.805365500 yum grouplist installed status 51200
2009-06-16 04:03:41.233003500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2009-06-16 04:03:41.292842500 yum list updates status 51200
2009-06-16 04:03:41.714667500 Existing lock /var/run/yum.pid: another copy is running. Aborting.
2009-06-16 04:03:41.773292500 yum grouplist updates status 51200
2009-06-17 04:03:49.896483500 Error: No Groups on which to run command
2009-06-17 04:03:49.955764500 yum grouplist available status 256
2009-06-17 04:03:52.826868500 Error: No Groups on which to run command
2009-06-17 04:03:52.886373500 yum grouplist installed status 256
2009-06-17 04:03:57.542849500 Error: No Groups on which to run command
2009-06-17 04:03:57.602310500 yum grouplist updates status 256
2009-06-18 04:03:48.951823500 Error: No Groups on which to run command
2009-06-18 04:03:49.011273500 yum grouplist available status 256
2009-06-18 04:03:51.477701500 Error: No Groups on which to run command
2009-06-18 04:03:51.536355500 yum grouplist installed status 256
2009-06-18 04:03:55.444835500 Error: No Groups on which to run command
2009-06-18 04:03:55.503687500 yum grouplist updates status 256
2009-06-19 04:03:58.876532500 Error: No Groups on which to run command
2009-06-19 04:03:58.936061500 yum grouplist available status 256
2009-06-19 04:04:01.787475500 Error: No Groups on which to run command
2009-06-19 04:04:01.851224500 yum grouplist installed status 256
2009-06-19 04:04:06.589897500 Error: No Groups on which to run command
2009-06-19 04:04:06.648490500 yum grouplist updates status 256
2009-06-20 04:04:21.745031500 Error: No Groups on which to run command
2009-06-20 04:04:21.804278500 yum grouplist available status 256
2009-06-20 04:04:24.903578500 Error: No Groups on which to run command
2009-06-20 04:04:24.963979500 yum grouplist installed status 256
2009-06-20 04:04:30.249076500 Error: No Groups on which to run command
2009-06-20 04:04:30.310690500 yum grouplist updates status 256


*************************************************************

This is the sa-update.log4
http: request failed: 500 Can't connect to spamassassin.apache.org:80 (connect: timeout): 500 Can't connect to spamassassin.apache.org:80 (connect: timeout)
error: no mirror data available for channel updates.spamassassin.org
channel: MIRRORED.BY contents were missing, channel failed
http: request failed: 500 Can't connect to saupdates.openprotect.com:80 (connect: timeout): 500 Can't connect to saupdates.openprotect.com:80 (connect: timeout)
error: no mirror data available for channel saupdates.openprotect.com
channel: MIRRORED.BY contents were missing, channel failed
http: request failed: 500 Can't connect to spamassassin.apache.org:80 (connect: timeout): 500 Can't connect to spamassassin.apache.org:80 (connect: timeout)
error: no mirror data available for channel updates.spamassassin.org
channel: MIRRORED.BY contents were missing, channel failed
http: request failed: 500 Can't connect to saupdates.openprotect.com:80 (connect: timeout): 500 Can't connect to saupdates.openprotect.com:80 (connect: timeout)
error: no mirror data available for channel saupdates.openprotect.com
channel: MIRRORED.BY contents were missing, channel failed
http: request failed: 500 Can't connect to spamassassin.apache.org:80 (connect: timeout): 500 Can't connect to spamassassin.apache.org:80 (connect: timeout)
error: no mirror data available for channel updates.spamassassin.org
channel: MIRRORED.BY contents were missing, channel failed
http: request failed: 500 Can't connect to saupdates.openprotect.com:80 (connect: timeout): 500 Can't connect to saupdates.openprotect.com:80 (connect: timeout)
error: no mirror data available for channel saupdates.openprotect.com
channel: MIRRORED.BY contents were missing, channel failed
http: request failed: 500 Can't connect to spamassassin.apache.org:80 (connect: timeout): 500 Can't connect to spamassassin.apache.org:80 (connect: timeout)
error: no mirror data available for channel updates.spamassassin.org
channel: MIRRORED.BY contents were missing, channel failed
http: request failed: 500 Can't connect to saupdates.openprotect.com:80 (connect: timeout): 500 Can't connect to saupdates.openprotect.com:80 (connect: timeout)
error: no mirror data available for channel saupdates.openprotect.com
channel: MIRRORED.BY contents were missing, channel failed
http: request failed: 500 Can't connect to spamassassin.kluge.net:80 (connect: timeout): 500 Can't connect to spamassassin.kluge.net:80 (connect: timeout)
http: request failed: 500 Can't connect to daryl.dostech.ca:80 (connect: timeout): 500 Can't connect to daryl.dostech.ca:80 (connect: timeout)
http: request failed: 500 Can't connect to www.sa-update.pccc.com:80 (connect: timeout): 500 Can't connect to www.sa-update.pccc.com:80 (connect: timeout)
channel: could not find working mirror, channel failed
'spamassassin' is not a valid service name




I will be lookin into this in the meantime if anyone can help thanks.
Title: Re: cannot find a valid baseurl for repo: base
Post by: cyberwatcher on June 24, 2009, 12:28:54 PM
Okay I am not sure why but the cron daemon is emailing me again. It stopped for almost a week.now I am getting the "/sbin/e-smith/check4update -m" once again. Which I think is a good thing?

The error is:
Cannot find a valid baseurl for repo: smeaddons
Error: Cannot find a valid baseurl for repo: smeaddons
Error in sys.exitfunc:
Traceback (most recent call last):
  File "/usr/lib/python2.3/atexit.py", line 20, in _run_exitfuncs
    func(*targs, **kargs)
  File "plugins.py", line 159, in run
  File "/usr/lib/yum-plugins/smeserver.py", line 69, in close_hook
    os.unlink('/var/run/yum.status')
OSError: [Errno 2] No such file or directory: '/var/run/yum.status' 

Can someone tell me what this means? Thanks.
Title: Re: cannot find a valid baseurl for repo: base
Post by: chris burnat on June 27, 2009, 05:22:12 AM
I am experiencing similar issues and have open two two tickets at Bugzilla:
http://bugs.contribs.org/show_bug.cgi?id=5378  (about cannot find a valid baseurl for repo: xxx)
http://bugs.contribs.org/show_bug.cgi?id=5379  (about can't get information about db.local.clamav.net: )
You may wish to follow developments there.
Thanks
Title: Re: cannot find a valid baseurl for repo: base
Post by: cyberwatcher on June 27, 2009, 05:30:21 AM
Thanks I will take a look now and again.