Solved: Update-notifier cannot contact default repository.

[lfever]

About a week ago update-notifier started giving me the following:

https://www.dropbox.com/s/w9vncu3tkrajow3/update_notifier.jpg

Running update-notifier in a terminal gives me this output:

Code: [Select]

[msswanson@linuxlover ~]$ update-notifier-launcher
10 seconds wait to connect repositories
/home/msswanson/.update-notifier-launcher/NUT directory found



Removed this instance of update-notifier from the log (pid 4488)


The following notifier processes will be killed and removed from the log:
        3664 /usr/bin/update-notifier-launcher: line 35: kill: (3664) - No such process




All pre-existing notifier processes have been killed and removed from the log



This instance of update-notifier-launcher has been logged (pid 4488)
Starting update-notifier..
pop-ups=true
4
/home/msswanson/.update-notifier-launcher/PID directory found


pid 4516 has been logged for this instance of update-notifier
pop-ups=true
apt-force-yes=false
4
Next update time is Saturday the 28. Apr at 7:05PM
update refresh status=true
Active repo: ftp.vim.org
PING ftp.nluug.nl (192.87.102.43) 56(84) bytes of data.

--- ftp.nluug.nl ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms



No connection to repository; trying google..


PING 64.233.161.99 (64.233.161.99) 56(84) bytes of data.

--- 64.233.161.99 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms



Internet connection working, but failed to contact software repository.  Please select a different repository.


Active repo: ftp.vim.org
PING ftp.nluug.nl (192.87.102.42) 56(84) bytes of data.

--- ftp.nluug.nl ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms



No connection to repository; trying google..


PING 64.233.161.99 (64.233.161.99) 56(84) bytes of data.

--- 64.233.161.99 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms



Internet connection working, but failed to contact software repository.  Please select a derent repository.




Starting exit processes from PID 4516..


The following processes exist in the log:
        4488
        4516

Removed this instance of update-notifier from the log (pid 4516)
Killing yad pid 4488: Killing yad pid 4516: Killed
[msswanson@linuxlover ~]$

Updating with Synaptic works fine.
I am running pclinuxos-kde-2012.02
kernel 2.6.38.8-pclos3.bfs

I would appreciate any help in solving this problem.  

Thanks
lfever

[daniel]

Which repo do you using?

[lfever]

Hi Leiche

Using these repos:
# Package repository URL's, working as of 03/29/2012
#===============================================
# Please enable only ONE (1) entry apart from the megagames repo!!!
#===============================================
rpm http://ftp.vim.org/ibiblio/distributions/pclinuxos/megagames/apt/ pclinuxos/2010 megagames
rpm http://ftp.heanet.ie/pub/pclinuxos/apt/ pclinuxos/2010 main updates nonfree kde4 games xfce4

lfever

[daniel]

You are up to date?

[lfever]

Yes system is up to date.

[daniel]

What is happen if you change your current repo (not megagames) ?

[lfever]

I have tried several of the repos all with the same result.

Well maybe a good hot shower a nice breakfast and a few cups of
coffee and something will come to lite! 

[rogaven]

Hi Leiche

Using these repos:
# Package repository URL's, working as of 03/29/2012
#===============================================
# Please enable only ONE (1) entry apart from the megagames repo!!!
#===============================================
rpm http://ftp.vim.org/ibiblio/distributions/pclinuxos/megagames/apt/ pclinuxos/2010 megagames
rpm http://ftp.heanet.ie/pub/pclinuxos/apt/ pclinuxos/2010 main updates nonfree kde4 games xfce4

lfever

from the log:

Code: [Select]

Active repo: ftp.vim.org
PING ftp.nluug.nl (192.87.102.43) 56(84) bytes of data.

--- ftp.nluug.nl ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
when the active repo is vim.org and ftp.heanet.ie why ping to ftp.nluug.nl?  

[djohnston]

Yes system is up to date.

I have tried several of the repos all with the same result.

lfever,

Please look in Synaptic and see if you have the package apt-sources-list installed, or simply open a terminal and enter:

rpm -qa apt-sources-list

[lfever]

lfever,

Please look in Synaptic and see if you have the package apt-sources-list installed, or simply open a terminal and enter:

rpm -qa apt-sources-list

Here are the results:

[msswanson@linuxlover ~]$ rpm -qa apt-sources-list
apt-sources-list-1.0.1-2pclos2012
[msswanson@linuxlover ~]$

lfever

[djohnston]

Here are the results:

[msswanson@linuxlover ~]$ rpm -qa apt-sources-list
apt-sources-list-1.0.1-2pclos2012
[msswanson@linuxlover ~]$

lfever

That's correct. So much for that theory. Are you having any problems reaching some websites?

[lfever]

That's correct. So much for that theory. Are you having any problems reaching some websites?

No problems with any websites.

[djohnston]

Quit update-notifier. If you have a process viewer installed like htop, look to see if all instances of update-notifier are gone. Open your file browser to your home folder. Select the option to show hidden files. There are two hidden folders named .update-notifier and .update-notifier-launcher. Rename them to -old or something similar. Start update-notifier again from the menu. Your settings will be gone and you'll need to give your preferred options. After saving them, follow the instructions to quit update-notifier and start it again. See if that helps.

[lfever]

Quit update-notifier. If you have a process viewer installed like htop, look to see if all instances of update-notifier are gone. Open your file browser to your home folder. Select the option to show hidden files. There are two hidden folders named .update-notifier and .update-notifier-launcher. Rename them to -old or something similar. Start update-notifier again from the menu. Your settings will be gone and you'll need to give your preferred options. After saving them, follow the instructions to quit update-notifier and start it again. See if that helps.

No help. 

[lfever]

Changed security settings in Xfinity (Comcast) modem/router, now update-notifier is working.
Enough for tonight, tomorrow I will sort out what went wrong as I don't
remember changing any settings in the router.

Maybe the old age is starting to set in. 
First this goes then that, etc. 

Thanks to all for your help.
lfever