Gday guys. I’ve done some repo adjustments lately, and now they’re all back to normal, and when i do ‘zypper refresh’ i get lots of these messages.
** (process:7478): WARNING **: The connection is closed
That number isn’t the only one that shows, but they all say the same thing. What’s causing this warning?
Please post the output of
zypper lr -d
Best regards,
Greg
Thanks Greg, here’s my repos.
# | Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
--+------------------------------------+------------------------------------+---------+---------+----------+--------+-----------------------------------------------------------------+--------
1 | Updates-for-openSUSE-12.1-12.1-1.4 | Updates for openSUSE 12.1 12.1-1.4 | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/12.1/ |
2 | libdvdcss | DVD Repository | Yes | No | 99 | rpm-md | http://opensuse-guide.org/repo/12.1/ |
3 | packman | Packman repository (openSUSE_12.1) | Yes | No | 99 | rpm-md | http://packman.inode.at/suse/openSUSE_12.1 |
4 | repo-debug | openSUSE-12.1-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/12.1/repo/oss/ |
5 | repo-debug-update | openSUSE-12.1-Update-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/update/12.1/ |
6 | repo-non-oss | openSUSE-12.1-Non-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/12.1/repo/non-oss/ |
7 | repo-oss | openSUSE-12.1-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/12.1/repo/oss/ |
8 | repo-source | openSUSE-12.1-Source | No | Yes | 99 | NONE | http://download.opensuse.org/source/distribution/12.1/repo/oss/ |
Please disable repo 2 and try again. The URL seems to be forbidden.
Best regards,
Greg
glistwan wrote:
>
> Please disable repo 2 and try again. The URL seems to be forbidden.
>
> Best regards,
> Greg
>
>
Ummm…
Repo 2 is not browsable, you do know that?
The repos look OK except I’d have Packman refreshing
knightron wrote:
>
> Gday guys. I’ve done some repo adjustments lately, and now they’re all
> back to normal, and when i do ‘zypper refresh’ i get lots of these
> messages.
>
> Code:
> --------------------
> ** (process:7478): WARNING **: The connection is closed
> --------------------
>
>
> That number isn’t the only one that shows, but they all say the same
> thing. What’s causing this warning?
>
My gues would be that you run zypper up in gnome-terminal using the su
command to change to the user root.
Type su - instead of just su and you wont see the warning messages.
I cna’t remember what the difference is between su and su - but for some
reason gnome-terminal needs this.
In konsole i can do just su without any problems.
Not to say that su doesn’t work in gnome-terminal, you’ll just get all these
warning messages.
–
Chris Maaskant
On Sat, 07 Apr 2012 14:53:53 +0530, Chris Maaskant <gch2@quicknet.nl>
wrote:
> knightron wrote:
>
>>
>> Gday guys. I’ve done some repo adjustments lately, and now they’re all
>> back to normal, and when i do ‘zypper refresh’ i get lots of these
>> messages.
>>
>> Code:
>> --------------------
>> ** (process:7478): WARNING **: The connection is closed
>> --------------------
>>
>>
>> That number isn’t the only one that shows, but they all say the same
>> thing. What’s causing this warning?
>>
> My gues would be that you run zypper up in gnome-terminal using the su
> command to change to the user root.
>
> Type su - instead of just su and you wont see the warning messages.
> I cna’t remember what the difference is between su and su - but for some
> reason gnome-terminal needs this.
> In konsole i can do just su without any problems.
> Not to say that su doesn’t work in gnome-terminal, you’ll just get all
> these
> warning messages.
>
in short, “su -” gives you the actual root user’s environment and PATH,
while “su” only gives you root’s permissions.
this is explained in more detail here:
http://forums.opensuse.org/forums/english/get-technical-help-here/how-faq-forums/unreviewed-how-faq/424498-become-su-terminal-howto.html
–
phani.
phanisvara das wrote:
> in short, “su -” gives you the actual root user’s environment and PATH,
> while “su” only gives you root’s permissions.
>
> this is explained in more detail here:
> http://forums.opensuse.org/forums/english/get-technical-help-here/how-faq-
forums/unreviewed-how-faq/424498-become-su-terminal-howto.html
Chris Maaskant
I think that the name of the process would be more informative than only the number/ID of the process (PID).
I guess something like
ps -p 7478
would give you the name (but the number will probably not be the same the next time).
Maybe it is just an other conflicting software management process like packagekitd/PackageKit/apper or something alike.
Regards
Martin
I’ve removed that repo, but all the other repos are still giving out warnings. done a refresh in both the gnome terminal and the kde konsole, and they both do it.
Here is the complete result of zypper refresh after removing the second rep.
** (process:4730): WARNING **: The connection is closed
** (process:4730): WARNING **: The connection is closed
** (process:4730): WARNING **: The connection is closed
** (process:4730): WARNING **: The connection is closed
** (process:4730): WARNING **: The connection is closed
Repository 'Updates for openSUSE 12.1 12.1-1.4' is up to date.
** (process:4735): WARNING **: The connection is closed
** (process:4735): WARNING **: The connection is closed
** (process:4735): WARNING **: The connection is closed
** (process:4735): WARNING **: The connection is closed
** (process:4735): WARNING **: The connection is closed
Repository 'Packman repository (openSUSE_12.1)' is up to date.
** (process:4738): WARNING **: The connection is closed
** (process:4738): WARNING **: The connection is closed
** (process:4738): WARNING **: The connection is closed
** (process:4738): WARNING **: The connection is closed
Repository 'openSUSE-12.1-Non-Oss' is up to date.
** (process:4741): WARNING **: The connection is closed
** (process:4741): WARNING **: The connection is closed
** (process:4741): WARNING **: The connection is closed
** (process:4741): WARNING **: The connection is closed
** (process:4741): WARNING **: The connection is closed
Repository 'openSUSE-12.1-Oss' is up to date.
All repositories have been refreshed.
The result of ‘ps -p 4741’
PID TTY TIME CMD
On 2012-04-08 02:36, knightron wrote:
> I’ve removed that repo, but all the other repos are still giving out
> warnings.
And you did not forget the dash?
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
The automatic GNOME updater was and is telling me today: “Update: An important software update is available [Install updates]”.
During that I could reproduce the warnings with my openSUSE 12.1 GNOME 64 bit system and gather some information.
I opened a terminal emulator (GNOME terminal) became root including new login console with
su -
and produced a list of the (active and inactive) processes with
ps -Af
. I repeated that action - sometimes even during 2) .
In a second window of GNOME terminal I stayed being a normal user but got privileges only for the command to run a (D=dry=test) update with
su -c "zypper up -D"
I aborted with n for no and repeated the action.
If I got in 2) something like
...]
** (process:5830): WARNING **: The connection is closed
** (process:5830): WARNING **: The connection is closed
** (process:5830): WARNING **: The connection is closed
** (process:5830): WARNING **: The connection is closed
** (process:5830): WARNING **: The connection is closed
** (process:5833): WARNING **: The connection is closed
** (process:5833): WARNING **: The connection is closed
** (process:5833): WARNING **: The connection is closed
** (process:5833): WARNING **: The connection is closed
** (process:5833): WARNING **: The connection is closed
** (process:5836): WARNING **: The connection is closed
** (process:5836): WARNING **: The connection is closed
** (process:5836): WARNING **: The connection is closed
** (process:5836): WARNING **: The connection is closed
** (process:5836): WARNING **: The connection is closed
** (process:5839): WARNING **: The connection is closed
** (process:5839): WARNING **: The connection is closed
** (process:5839): WARNING **: The connection is closed
** (process:5839): WARNING **: The connection is closed
** (process:5839): WARNING **: The connection is closed
** (process:5842): WARNING **: The connection is closed
** (process:5842): WARNING **: The connection is closed
** (process:5842): WARNING **: The connection is closed
** (process:5842): WARNING **: The connection is closed
** (process:5842): WARNING **: The connection is closed
** (process:5845): WARNING **: The connection is closed
** (process:5845): WARNING **: The connection is closed
** (process:5845): WARNING **: The connection is closed
** (process:5845): WARNING **: The connection is closed
** (process:5845): WARNING **: The connection is closed
** (process:5848): WARNING **: The connection is closed
** (process:5848): WARNING **: The connection is closed
** (process:5848): WARNING **: The connection is closed
** (process:5848): WARNING **: The connection is closed
** (process:5848): WARNING **: The connection is closed
** (process:5852): WARNING **: The connection is closed
** (process:5852): WARNING **: The connection is closed
** (process:5852): WARNING **: The connection is closed
** (process:5852): WARNING **: The connection is closed
** (process:5852): WARNING **: The connection is closed
** (process:5855): WARNING **: The connection is closed
** (process:5855): WARNING **: The connection is closed
** (process:5855): WARNING **: The connection is closed
** (process:5855): WARNING **: The connection is closed
** (process:5855): WARNING **: The connection is closed
** (process:5859): WARNING **: The connection is closed
** (process:5859): WARNING **: The connection is closed
** (process:5859): WARNING **: The connection is closed
** (process:5859): WARNING **: The connection is closed
** (process:5859): WARNING **: The connection is closed
** (process:5862): WARNING **: The connection is closed
** (process:5862): WARNING **: The connection is closed
** (process:5862): WARNING **: The connection is closed
** (process:5862): WARNING **: The connection is closed
** (process:5862): WARNING **: The connection is closed
** (process:5865): WARNING **: The connection is closed
** (process:5865): WARNING **: The connection is closed
** (process:5865): WARNING **: The connection is closed
** (process:5865): WARNING **: The connection is closed
** (process:5865): WARNING **: The connection is closed
** (process:5868): WARNING **: The connection is closed
** (process:5868): WARNING **: The connection is closed
** (process:5868): WARNING **: The connection is closed
** (process:5868): WARNING **: The connection is closed
** (process:5868): WARNING **: The connection is closed
** (process:5871): WARNING **: The connection is closed
** (process:5871): WARNING **: The connection is closed
** (process:5871): WARNING **: The connection is closed
** (process:5871): WARNING **: The connection is closed
** (process:5871): WARNING **: The connection is closed
...]
the list of the processes from 1) included something like:
ps -Af
UID PID PPID C STIME TTY TIME CMD
...]
root 5818 3209 0 15:02 pts/0 00:00:00 su -c zypper up -D
root 5819 2 0 15:02 ? 00:00:00 [kworker/0:0]
root 5824 5818 5 15:02 pts/0 00:00:01 zypper up -D
root 5830 5824 0 15:02 pts/0 00:00:00 [pxgsettings] <defunct>
root 5833 5824 0 15:02 pts/0 00:00:00 [pxgsettings] <defunct>
root 5836 5824 0 15:02 pts/0 00:00:00 [pxgsettings] <defunct>
root 5839 5824 0 15:02 pts/0 00:00:00 [pxgsettings] <defunct>
root 5842 5824 0 15:02 pts/0 00:00:00 [pxgsettings] <defunct>
root 5845 5824 0 15:02 pts/0 00:00:00 [pxgsettings] <defunct>
root 5848 5824 0 15:02 pts/0 00:00:00 [pxgsettings] <defunct>
root 5852 5824 0 15:02 pts/0 00:00:00 [pxgsettings] <defunct>
root 5855 5824 0 15:02 pts/0 00:00:00 [pxgsettings] <defunct>
root 5859 5824 0 15:03 pts/0 00:00:00 [pxgsettings] <defunct>
root 5862 5824 0 15:03 pts/0 00:00:00 [pxgsettings] <defunct>
root 5865 5824 0 15:03 pts/0 00:00:00 [pxgsettings] <defunct>
root 5868 5824 0 15:03 pts/0 00:00:00 [pxgsettings] <defunct>
root 5871 5824 0 15:03 pts/0 00:00:00 [pxgsettings] <defunct>
If ps from 1) listed no processes with “pxgsettings” before beginning the update (1) ) there were also no warnings during 1).
So I guess that the processes were ended by zypper and so it will be difficult to list them after the zypper update (2) ).
Searching for “pxgsettings” Google gave me as first hit:
packages: libproxy/libproxy.spec - pxgsettings helper belongs to -gnome module
with
- pxgsettings - A helper binary to query gsettings
- Copyright (C) 2006 Nathaniel McCallum <nathaniel@natemccallum.com>
- Copyright (C) 2011 Dominique Leuenberger <dominique@leuenberger.net>
…]
Searching for gsettings gave me:
GNOME Library Help: GSettings
with
GSettings — High-level API for application settings …]
Maybe someone else will be able to make a more educated guess what those “pxgsettings” are doing there (conflicting with zypper or trying to solve an conflict or …?)
Regards
Martin
This has also been described in the dutch forums. I don’t have the issue, so I hadn’t seen the pxgsettings processes. Not good, so many <defunct> ones.
Martin, could this be a proxy problem? My settings in GNOME and KDE are “None” for proxy, AFAIK the default is “Automatic”. Could you try setting proxy to “None”, then try to refresh the repos?
I could not jet reproduce it with zypper up as root (with su --login or equivalents of making the shell a login shell).
But now I could provoce the warnings with zypper up without real root - even without the GNOME graphical updater/information stuff popped up and without any pxgsettings processes before starting the zypper up.
And if I understood knightron the right way these warings are also happening under KDE, are they?
So like the other members suggested it might be connected with becoming no really root before starting zypper up.
Regards
Martin
Thanks, Gertjan.
But my settings in GNOME seems to be the same:
Username > System Settings > Hardware: Network > Network Proxy [None]
I have also LXDE installed but I think I have never used it with this useraccount.
Regards Martin
On Tue, 10 Apr 2012 20:16:02 +0530, pistazienfresser
<pistazienfresser@no-mx.forums.opensuse.org> wrote:
>
> Knurpht;2455159 Wrote:
>> This has also been described in the dutch forums. I don’t have the
>> issue, so I hadn’t seen the pxgsettings processes. Not good, so many
>> <defunct> ones.
>
> I could not jet reproduce it with -zypper up- as root (with -su
> --login- or equivalents of making the shell a login shell).
> But now I could provoce the warnings with zypper up without real root
> - even without the GNOME graphical updater/information stuff popped up
> and without any pxgsettings processes before starting the zypper up.
>
> And if I understood knightron the right way these warings are also
> happening under KDE, are they?
> So like the other members suggested it might be connected with becoming
> no really root before starting zypper up.
>
i tried “zypper up” after getting root permissions via “su”, not “su -” as
i habitually do, and there’s still no errors for me. (oS 12.1 / KDE 4.8.2)
–
phani.
On 2012-04-10 16:06, pistazienfresser wrote:
> 2)
> In a second window of GNOME terminal I stayed being a normal user but
> got privileges only for the command to run a (D=dry=test) update with
>
> Code:
> --------------------
> su -c “zypper up -D”
> --------------------
Notice that this one is not equivalent to “su -”, and some of the errors
you get might be related to that. There are differences between “su -” and
“su” that you should be aware of.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 2012-04-10 16:56, phanisvara das wrote:
> i tried “zypper up” after getting root permissions via “su”, not “su -” as
> i habitually do, and there’s still no errors for me. (oS 12.1 / KDE 4.8.2)
But the OP might have user settings that affect the behaviour.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
I am not able to reproduce the warnings every time with substitute user without a login shell but til now never with a login shell. So I guess the behavior that knightron described is connected not only to using substitute user without a login shell but also to an other process/program. I would be interested to know to what PID described processes the other users warnings (of the original poster knightron here and OpenM there are connected) .
And I tried again with another account (also GNOME).
As expected/hoped I could reproduce the warnings like knightron described
with substitute user without a login shell and zypper up
even if used in two command lines.
terminal 1:
~> su
Passwort:
/home/username # zypper up -D
** (process:3566): WARNING **: The connection is closed
...]
** (process:3828): WARNING **: The connection is closed
and
terminal 2 (pts/0 ?):
# ps -fA
UID PID PPID C STIME TTY TIME CMD
...]
root 3542 3501 0 20:53 pts/1 00:00:00 su
root 3546 3542 0 20:53 pts/1 00:00:00 bash
root 3560 3546 4 20:53 pts/1 00:00:01 zypper up -D
root 3566 3560 0 20:53 pts/1 00:00:00 [pxgsettings] <defunct>
root 3570 3560 0 20:53 pts/1 00:00:00 [pxgsettings] <defunct>
root 3573 3560 0 20:53 pts/1 00:00:00 [pxgsettings] <defunct>
root 3576 3560 0 20:53 pts/1 00:00:00 [pxgsettings] <defunct>
root 3628 3560 0 20:53 pts/1 00:00:00 [pxgsettings] <defunct>
root 3633 3560 0 20:53 pts/1 00:00:00 [pxgsettings] <defunct>
root 3638 3560 0 20:53 pts/1 00:00:00 [pxgsettings] <defunct>
root 3643 3560 0 20:53 pts/1 00:00:00 [pxgsettings] <defunct>
root 3648 3560 0 20:53 pts/1 00:00:00 [pxgsettings] <defunct>
root 3694 3560 0 20:53 pts/1 00:00:00 [pxgsettings] <defunct>
root 3697 3560 0 20:53 pts/1 00:00:00 [pxgsettings] <defunct>
root 3700 3560 0 20:53 pts/1 00:00:00 [pxgsettings] <defunct>
root 3703 3560 0 20:53 pts/1 00:00:00 [pxgsettings] <defunct>
root 3706 3560 0 20:53 pts/1 00:00:00 [pxgsettings] <defunct>
root 3709 3560 0 20:53 pts/1 00:00:00 [pxgsettings] <defunct>
root 3712 3560 0 20:53 pts/1 00:00:00 [pxgsettings] <defunct>
root 3716 3560 0 20:54 pts/1 00:00:00 [pxgsettings] <defunct>
root 3720 3560 0 20:54 pts/1 00:00:00 [pxgsettings] <defunct>
root 3763 2 0 20:54 ? 00:00:00 [kworker/1:0]
root 3816 3560 0 20:54 pts/1 00:00:00 [pxgsettings] <defunct>
root 3819 3560 0 20:54 pts/1 00:00:00 [pxgsettings] <defunct>
root 3822 3560 0 20:54 pts/1 00:00:00 [pxgsettings] <defunct>
root 3825 3560 0 20:54 pts/1 00:00:00 [pxgsettings] <defunct>
root 3828 3560 0 20:54 pts/1 00:00:00 [pxgsettings] <defunct>
root 3831 3462 0 20:54 pts/0 00:00:00 ps -fA
It may be also interesting that all the ‘defunct’ processes got the process ID of zypper up -D (3560) as parent process ID.
Regards
Martin