Re: [CentOS] VNC question
On 12/19/18 4:36 AM, isdtor wrote: We have run into the infamous black screen problem with tigervnc under CentOS7, which prompted me to look into how vnc is configured here. https://access.redhat.com/solutions/966063 Am I reading this correctly - root needs to set up a systemd vnc service for every user and display individually? Compared to e.g. CentOS before 7, or indeed any other Linux/Unix system where vnc is completely under user control? I have always run an instance of vnc-server for each user. I never gave the user control, just assigned the port number for the user. I have been doing this at least since CentOS4. Now the fun comes in as to what GUI you are using. The install is for Gnome, and if you want any other GUI, you have work in front of you. I have it working for Xfce. I have a separate systemd service file for each user. And I enable them all, just the way I run things. I suppose there are ways you can have the user start his specific systemd service from their ssh shell. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS-announce] CEBA-2018:3847 CentOS 7 pacemaker BugFix Update
CentOS Errata and Bugfix Advisory 2018:3847
Upstream details at : https://access.redhat.com/errata/RHBA-2018:3847
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
2e35900146ccf77ab81cb32e8a7957c10aa678bae36c55744e9b18f1750a95e8
pacemaker-1.1.19-8.el7_6.2.x86_64.rpm
5b54875eaccb9c93054e5eef35caf5ff46e2f0cfbd2acb859b813cb3f473301f
pacemaker-cli-1.1.19-8.el7_6.2.x86_64.rpm
e2312c85fc1373cf28748db20cfee3135a390b48b9c0abce874e9939af9377fb
pacemaker-cluster-libs-1.1.19-8.el7_6.2.i686.rpm
302e43e36b0262d23fb2cd34f393eb5834c7f82944d79d3e46923f9d6544cb54
pacemaker-cluster-libs-1.1.19-8.el7_6.2.x86_64.rpm
a7b495377398e9c514391716bc0a34c66287be8fbad4b47c4d6ff48c9edfa1b0
pacemaker-cts-1.1.19-8.el7_6.2.x86_64.rpm
e295d5e858815ad9b39d2498e24de56a7c4aef479f04dedc0e86cee13aaf1727
pacemaker-doc-1.1.19-8.el7_6.2.x86_64.rpm
3d8ca4d2a12878da0d49541b27c8266d6d7e01f8c984b66443f8b1a87b55c004
pacemaker-libs-1.1.19-8.el7_6.2.i686.rpm
a19e6555225e34aed04e981aad4925a85c67452b92cece2000e76d03fce500dc
pacemaker-libs-1.1.19-8.el7_6.2.x86_64.rpm
65952d9647e01febadc9e68a438e2ca1cf4ab15deaace176761edcbe094ec380
pacemaker-libs-devel-1.1.19-8.el7_6.2.i686.rpm
bfa7aa216dab27e96169eb2b63ed0e233eaba1368dd2bbb00e22eaa52348f321
pacemaker-libs-devel-1.1.19-8.el7_6.2.x86_64.rpm
db71a78725c41b66642e5ed756d0b7bfeee2ca1230cbf9433ee1cfbc27d245f0
pacemaker-nagios-plugins-metadata-1.1.19-8.el7_6.2.x86_64.rpm
51f9cbc0b8ccf236667e2b6bf057b662a44abdb4633efa58c4961362a9e3bf6a
pacemaker-remote-1.1.19-8.el7_6.2.x86_64.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS
___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce
[CentOS-announce] CESA-2018:3854 Low CentOS 6 ntp Security Update
CentOS Errata and Security Advisory 2018:3854 Low
Upstream details at : https://access.redhat.com/errata/RHSA-2018:3854
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
8d4c7f5edb0fb14af55ff6f74ee15349e69f5a8ff180b39b2fbbd01d99c0199a
ntp-4.2.6p5-15.el6.centos.i686.rpm
a9a5283906f361f4b2d85be307eb8c7574bc749ec6e9d03988831b628e2bd273
ntpdate-4.2.6p5-15.el6.centos.i686.rpm
18edea5cb7d5a13afc34464fd4cef7cbd46e6d6a7b91acbf1a6dd58a9997a411
ntp-doc-4.2.6p5-15.el6.centos.noarch.rpm
ba4d8eff03ce5ffdd42025c0aa9e21ca1429f02909e2e0f39a2d838c22e04eae
ntp-perl-4.2.6p5-15.el6.centos.i686.rpm
x86_64:
b6ee6afaf3ff4b90b3a3f0077e111362a9ce6912384799b4798cfba3984a60ec
ntp-4.2.6p5-15.el6.centos.x86_64.rpm
0bd3608f6a5a0935529f9e16de6b875ac810e89f25fc03a034e1e11e763b9bf9
ntpdate-4.2.6p5-15.el6.centos.x86_64.rpm
18edea5cb7d5a13afc34464fd4cef7cbd46e6d6a7b91acbf1a6dd58a9997a411
ntp-doc-4.2.6p5-15.el6.centos.noarch.rpm
c638a5e57e7895b4c605f63077902c141ada8a26bf2a94272dc0d11f0a35bc30
ntp-perl-4.2.6p5-15.el6.centos.x86_64.rpm
Source:
b41d310c7c14b58374dfd75e55b5b9b9f7105ca983e0a3ac4cf43be95e47da8b
ntp-4.2.6p5-15.el6.centos.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS
___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce
[CentOS] grpc packages
Is there any repository/location where we can grab prebuilt grpc packages for CentOS? Any pointers appreciated. Thanks. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] how to implement rate-limiting measures on interfaces using IPTables?
--On Wednesday, December 19, 2018 12:07 PM -0500 Sean Son wrote: I have been tasked to implement rate-limiting measures on interfaces using IPTables in RHEL 7. I know that in order to implement it using FirewallD, I will need to run the following command: firewall-cmd --direct --add-rule ipv4 filter IN_public_allow 0 -p tcp -m limit --limit 25/minute --limit-burst 100 -j ACCEPT How would I do the same using IPtables? firewalld uses iptables under the hood. So just snoop on what rules firewalld created. Use "iptables-save > /tmp/firewalld-iptables.dump" and inspect the result. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Cgroups : memory.limit_in_bytes and memory.usage_in_bytes includes file cache?
Hello All, We were under the assumption that Cgroups memory controller, limits memory based on just the RSS size of the process. However, i see that the process is getting killed even when the RSS size is very low compared to the limit in bytes. For example: cat memory.stat cache 85880266752 rss 2441216 rss_huge 0 mapped_file 8192 swap 0 pgpgin 29265847812 pgpgout 29244880354 pgfault 48530374728 pgmajfault 20 inactive_anon 0 active_anon 2441216 inactive_file 85879496704 active_file 770048 unevictable 0 hierarchical_memory_limit 85899345920 hierarchical_memsw_limit 85899345920 total_cache 85880266752 total_rss 2441216 total_rss_huge 0 total_mapped_file 8192 total_swap 0 total_pgpgin 29265847812 total_pgpgout 29244880354 total_pgfault 48530374728 total_pgmajfault 20 total_inactive_anon 0 total_active_anon 2441216 total_inactive_file 85879496704 total_active_file 770048 total_unevictable 0 cat memory.usage_in_bytes 85885800448 cat memory.limit_in_bytes 85899345920 What is confusing is that , why is memory.usage_in_bytes being shown as 85885800448, when the RSS is just 2441216? Is it true that memory.usage_in_bytes/memory.limit_in_bytes takes files cache into consideration when calculating the usage? Regards, Lohit ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Out of memory
Yan Li wrote: > On 12/19/18 5:05 AM, Jerry Geis wrote: > >> I have three machines running CentOS 7.6 in desktop mode. 2 are fine. >> 1 of them is having a memory issue that is Out of memory >> [17878] 1000 17878 206999142311 118988800 0 >> gnome-shell >> >> This gnome-shell looking at /var/log/messages after reboot - is the >> HIGHEST >> amount of memory. Looking at "top" now - it certainly does not use that >> amount of ram at this time. >> >> These are the gnome-shell packages installed. >> rpm -qa | grep gnome-shell >> gnome-shell-extension-alternate-tab-3.28.1-5.el7.noarch >> gnome-shell-extension-top-icons-3.28.1-5.el7.noarch >> gnome-shell-extension-window-list-3.28.1-5.el7.noarch >> gnome-shell-extension-launch-new-instance-3.28.1-5.el7.noarch >> gnome-shell-extension-apps-menu-3.28.1-5.el7.noarch >> gnome-shell-extension-common-3.28.1-5.el7.noarch >> gnome-shell-extension-user-theme-3.28.1-5.el7.noarch >> gnome-shell-extension-places-menu-3.28.1-5.el7.noarch >> gnome-shell-3.28.3-6.el7.x86_64 >> >> Why is gnome-shell eating my memory? What can I do? >> > > /rant: gnome-shell has always been this resource hog in the past few > years, maybe after they started using JavaScript for almost everything. > There are countless memory leaks that are being patched. 3.29 and 3.30 > both have important fixes that are not in the 3.28 shipped by Red Hat for > RHEL 7.6. > > >> Basically - the machine isn't even doing anything. Boots up and shows >> one static web page. At this time that is all. Then about 24 hours later >> its out of memory. The other 2 machines that seem fine - are showing the >> same web page. But not out of memory. > > On workstations, I have to hit Alt-F2 and type "r" to restart > gnome-shell every morning to keep its memory use at bay. For long running > sessions, I'd switch away from GNOME. Maybe to Cinnamon, XFCE, or any > other lightweight desktop environments. Fixing the memory leaks of > gnome-shell is not trivial. > On the one hand, KDE *used* to be a memory hog and bloatware... a number of years ago. Now, it's lean and mean, compared to... they're using JAVASCRIPT for the bloody GUI? On the other hand, I almost never have problems. Of course, my manager thinks I go overboard, because I log out, fully, every night. And I do the same at home mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] upgrading 7.5 ==> 7.6
hI ALL! There have been a large enough number of people posting here about difficulties when upgrading from 7. to 7.6 that I'm being somewhat paranoid about it. I have several machines to upgrade, but so far the only one I've dared to work on (least critical if it goes bad) is my new-to-me-but-used laptop. First I did a 'dd' backup of the whole drive onto an external USB drive then did the upgrade. Since I use the Mate desktop, I enabled the epel testing repo (per postings on Mate troubles at the time of the upgrade). Result: Boots to GDM just fine, but Mate is a black screen. Switching to Gnome, works fine, but I can't stand Gnome. Not knowing what else to try I restored the dd backup. Later I inserted a spare HD and did a new install from the DVD media. This installed without issue, but now no desktop works. Switching to a console (CTRL-ALT-F2) I did a full "yum update", which installed quite a few packages, but upon reboot nothing had improved. So I added the epel repo (and testing) and installed Mate. Ditto, nothing had changed. This laptop is fairly old, and according to lshw, has a RV635/M86 [Mobility Radeon HD 3650]I] video chipset, in case it matters. CPU is identified as: Intel(R) Core(TM)2 Duo CPU T9400 @ 2.53GHz Having previously installed 7.5 on it without trouble, on which Mate works just fine, I wonder what could have become so broken that neither an upgrade nor a fresh install works. I have, as I said, several other machines to upgrade, too, some of them have Nvidia grahics (esp. my main desktop box, which also uses Linux software RAID-1) and all run Mate. Then there is a netbook (low priority) a couple of VMs (in virtualbox) and at work several other VMS as well as bare-metal on a Lenovo deskside machine, and I'm afraid to do an update on all of them because I need them to be in usable condition. The Lenovo box in my office is somewhat urgent, as I am about to retire and turn it over to someone else who doesn't know much about Linux. I'd appreciate any advice I can get on how to get these systems upgraded without breaking them. thanks in advance for your help! Fred -- --- Under no circumstances will I ever purchase anything offered to me as the result of an unsolicited e-mail message. Nor will I forward chain letters, petitions, mass mailings, or virus warnings to large numbers of others. This is my contribution to the survival of the online community. --Roger Ebert, December, 1996 - The Boulder Pledge - ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Spamassassin + Postfix : delete spam mail on the server ?
Am 19.12.2018 um 14:49 schrieb Nux!: Absolutely, never reject spam at MTA level! Usually I put it in a spam folder, then add a cronjob that deletes messages older than 6 months, ymmv. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro Sorry, I see it totally different. But do what you like to do as your own postmaster. There are good reasons to reject SPAM messages instead of initially accepting them. Alexander ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS-CR-announce] CEBA-2018:3060 CentOS 7 man-db BugFix Update
CentOS Errata and Bugfix Advisory 2018:3060
Upstream details at : https://access.redhat.com/errata/RHBA-2018:3060
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
4160544cbe441161c6262b8a3b1417807ab88e3f5ab5acf4d38f2548aa0d88ad
man-db-2.6.3-11.el7.x86_64.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS
___
CentOS-CR-announce mailing list
CentOS-CR-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-cr-announce
Re: [CentOS] Out of memory
On 12/19/18 5:05 AM, Jerry Geis wrote: I have three machines running CentOS 7.6 in desktop mode. 2 are fine. 1 of them is having a memory issue that is Out of memory [17878] 1000 17878 206999142311 118988800 0 gnome-shell This gnome-shell looking at /var/log/messages after reboot - is the HIGHEST amount of memory. Looking at "top" now - it certainly does not use that amount of ram at this time. These are the gnome-shell packages installed. rpm -qa | grep gnome-shell gnome-shell-extension-alternate-tab-3.28.1-5.el7.noarch gnome-shell-extension-top-icons-3.28.1-5.el7.noarch gnome-shell-extension-window-list-3.28.1-5.el7.noarch gnome-shell-extension-launch-new-instance-3.28.1-5.el7.noarch gnome-shell-extension-apps-menu-3.28.1-5.el7.noarch gnome-shell-extension-common-3.28.1-5.el7.noarch gnome-shell-extension-user-theme-3.28.1-5.el7.noarch gnome-shell-extension-places-menu-3.28.1-5.el7.noarch gnome-shell-3.28.3-6.el7.x86_64 Why is gnome-shell eating my memory? What can I do? /rant: gnome-shell has always been this resource hog in the past few years, maybe after they started using JavaScript for almost everything. There are countless memory leaks that are being patched. 3.29 and 3.30 both have important fixes that are not in the 3.28 shipped by Red Hat for RHEL 7.6. Basically - the machine isn't even doing anything. Boots up and shows one static web page. At this time that is all. Then about 24 hours later its out of memory. The other 2 machines that seem fine - are showing the same web page. But not out of memory. On workstations, I have to hit Alt-F2 and type "r" to restart gnome-shell every morning to keep its memory use at bay. For long running sessions, I'd switch away from GNOME. Maybe to Cinnamon, XFCE, or any other lightweight desktop environments. Fixing the memory leaks of gnome-shell is not trivial. -- Yan Li ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] how to implement rate-limiting measures on interfaces using IPTables?
Hello all I have been tasked to implement rate-limiting measures on interfaces using IPTables in RHEL 7. I know that in order to implement it using FirewallD, I will need to run the following command: firewall-cmd --direct --add-rule ipv4 filter IN_public_allow 0 -p tcp -m limit --limit 25/minute --limit-burst 100 -j ACCEPT How would I do the same using IPtables? Thanks!! Sean ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] kickstart install
In changing from a 7.5 to 7.6 automated install. 7.6 is not happy and the install process stops and shows the screen where the "Install Source" is not happy. I enter 3 to see what its set for, I select network, I select http and I see my URL that my kickstart file has. It looks right - but its not happy. I tried looking in other consoles (text mode) to see any error and nothing is showing. How do I see what the error is about the install source ? Thanks, Jerry ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] VNC question
> No. Users can run vncserver and attach to them like you could before, > or you can run Xvnc -inetd, just as a systemd service/socket pair > instead of out of xinetd. > > The black screen problem that you mentioned does sound familiar -- > I've seen it with VNC clients that don't support OpenGL, with the > GNOME desktop (which uses a compositing display manager), it just > crashes when you log in. Looked at this a bit more. There is a crash, but for a different reason: Dec 19 07:59:31 host dbus-daemon: YPBINDPROC_DOMAIN: Domain not bound Dec 19 07:59:31 host dbus-daemon: YPBINDPROC_DOMAIN: Domain not bound Dec 19 07:59:31 host gnome-session-binary[12324]: ERROR: Failed to connect to system bus: Exhausted all available authentication mechanisms (tried: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS) (available: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS)#012aborting... Dec 19 07:59:31 host gnome-session: gnome-session-binary[12324]: ERROR: Failed to connect to system bus: Exhausted all available authentication mechanisms (tried: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS) (available: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS) Dec 19 07:59:31 host gnome-session: aborting... I've seen this before, and the solution was to make sure that the NISDOMAIN is defined in /etc/sysconfig/network. https://marc.info/?l=centos=152806243921469=2 NIS setup is correct and working, question is why it is being ignored by dbus. After restarting dbus, there is still a crash, but a different log. Dec 19 08:22:30 host org.a11y.Bus: Activating service name='org.a11y.atspi.Registry' Dec 19 08:22:31 host org.a11y.Bus: Successfully activated service 'org.a11y.atspi.Registry' Dec 19 08:22:31 host org.a11y.atspi.Registry: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Dec 19 08:22:31 host dbus[25267]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' Dec 19 08:22:56 host gnome-session-binary[28570]: WARNING: Failed to connect to systemd: Error calling StartServiceByName for org.freedesktop.login1: Timeout was reached Dec 19 08:22:56 host kernel: gnome-session-b[28570]: segfault at 8 ip 004216f1 sp 7ffdfcfc77b0 error 4 in gnome-session-binary[40+45000] Dec 19 08:22:56 host gnome-session: gnome-session-binary[28570]: WARNING: Failed to connect to systemd: Error calling StartServiceByName for org.freedesktop.login1: Timeout was reached Dec 19 08:22:56 host gnome-session: gnome-session-binary[28570]: GLib-GObject-WARNING: invalid (NULL) pointer instance Dec 19 08:22:56 host gnome-session: gnome-session-binary[28570]: GLib-GObject-CRITICAL: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed Dec 19 08:22:56 host gnome-session: gnome-session-binary[28570]: GLib-GIO-CRITICAL: g_dbus_proxy_call_sync_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed Dec 19 08:22:56 host gnome-session-binary[28570]: GLib-GObject-WARNING: invalid (NULL) pointer instance Dec 19 08:22:56 host gnome-session-binary[28570]: GLib-GObject-CRITICAL: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed Dec 19 08:22:56 host gnome-session-binary[28570]: GLib-GIO-CRITICAL: g_dbus_proxy_call_sync_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed Dec 19 08:22:56 host dbus[25267]: [system] Failed to activate service 'org.freedesktop.login1': timed out Dec 19 08:22:56 host abrt-hook-ccpp: Process 28570 (gnome-session-binary) of user 14728 killed by SIGSEGV - dumping core ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Spamassassin + Postfix : delete spam mail on the server ?
Absolutely, never reject spam at MTA level! Usually I put it in a spam folder, then add a cronjob that deletes messages older than 6 months, ymmv. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "CentOS mailing list" > To: "CentOS mailing list" > Sent: Wednesday, 19 December, 2018 04:59:21 > Subject: Re: [CentOS] Spamassassin + Postfix : delete spam mail on the server > ? >> Am 18.12.2018 um 08:08 schrieb Nicolas Kovacs: >>> The problem with this setup is that spam mail is still delivered, and I >>> need Thunderbird's filters to weed out incoming mail. And when I'm using >>> my webmail (running SquirrelMail), my inbox is a tsunami of unread >>> [SPAM] messages. >>> >>> So I'd like to go a step further and delete all messages flagged [SPAM] >>> directly on the server. It doesn't look like Spamassassin provides this >>> functionality. >> >> What's the point of delivering identified SPAM and then deleting it? >> Reject SPAM at SMTP level on your MTA. Easy to do with amavisd-new in a >> smtp proxy setup with Postfix. > > There are good reasons to not reject detected SPAM because your SPAM > filter could be wrong and you reject legitimate mail. > > For businesses depending on email communication that's a no go, because > you may lose customers that way. > > Regards, > Simon > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] VNC question
Jonathan Billings writes: > On Wed, Dec 19, 2018 at 11:56:11AM +, isdtor wrote: > > What you describe doesn't make much sense to me either. > > > > In this case, there are no user logins on the console, this is meant > > to be a remote login server. Anyone logging in via vnc gets the > > black screen treatment. There is no login screen, only the vnc > > password prompt. > > How are they 'logging in via vnc'? How did you set up the VNC server? They are logging in through ssh to manually start vncserver, then connect to it. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] VNC question
On Wed, Dec 19, 2018 at 11:56:11AM +, isdtor wrote: > What you describe doesn't make much sense to me either. > > In this case, there are no user logins on the console, this is meant > to be a remote login server. Anyone logging in via vnc gets the > black screen treatment. There is no login screen, only the vnc > password prompt. How are they 'logging in via vnc'? How did you set up the VNC server? -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] VNC question
On Wed, Dec 19, 2018 at 09:36:44AM +, isdtor wrote: > We have run into the infamous black screen problem with tigervnc > under CentOS7, which prompted me to look into how vnc is configured > here. > > https://access.redhat.com/solutions/966063 > > Am I reading this correctly - root needs to set up a systemd vnc > service for every user and display individually? Compared to > e.g. CentOS before 7, or indeed any other Linux/Unix system where > vnc is completely under user control? No. Users can run vncserver and attach to them like you could before, or you can run Xvnc -inetd, just as a systemd service/socket pair instead of out of xinetd. The black screen problem that you mentioned does sound familiar -- I've seen it with VNC clients that don't support OpenGL, with the GNOME desktop (which uses a compositing display manager), it just crashes when you log in. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Out of memory
Hi, I have three machines running CentOS 7.6 in desktop mode. 2 are fine. 1 of them is having a memory issue that is Out of memory [17878] 1000 17878 206999142311 118988800 0 gnome-shell This gnome-shell looking at /var/log/messages after reboot - is the HIGHEST amount of memory. Looking at "top" now - it certainly does not use that amount of ram at this time. These are the gnome-shell packages installed. rpm -qa | grep gnome-shell gnome-shell-extension-alternate-tab-3.28.1-5.el7.noarch gnome-shell-extension-top-icons-3.28.1-5.el7.noarch gnome-shell-extension-window-list-3.28.1-5.el7.noarch gnome-shell-extension-launch-new-instance-3.28.1-5.el7.noarch gnome-shell-extension-apps-menu-3.28.1-5.el7.noarch gnome-shell-extension-common-3.28.1-5.el7.noarch gnome-shell-extension-user-theme-3.28.1-5.el7.noarch gnome-shell-extension-places-menu-3.28.1-5.el7.noarch gnome-shell-3.28.3-6.el7.x86_64 Why is gnome-shell eating my memory? What can I do? Basically - the machine isn't even doing anything. Boots up and shows one static web page. At this time that is all. Then about 24 hours later its out of memory. The other 2 machines that seem fine - are showing the same web page. But not out of memory. Thanks, Jerry ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS-announce Digest, Vol 166, Issue 5
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org
You can reach the person managing the list at
centos-announce-ow...@centos.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."
Today's Topics:
1. CEBA-2018:3832 CentOS 7 resource-agents BugFixUpdate
(Johnny Hughes)
2. CESA-2018:3834 Important CentOS 7 ghostscript Security Update
(Johnny Hughes)
--
Message: 1
Date: Wed, 19 Dec 2018 03:21:52 +
From: Johnny Hughes
To: centos-annou...@centos.org
Subject: [CentOS-announce] CEBA-2018:3832 CentOS 7 resource-agents
BugFix Update
Message-ID: <20181219032152.ga...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Bugfix Advisory 2018:3832
Upstream details at : https://access.redhat.com/errata/RHBA-2018:3832
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
79aa7b8a924f66da70481041e131df1d717800eeb0e11f9ffe9a7ace6e3a9d2c
resource-agents-4.1.1-12.el7_6.7.x86_64.rpm
b36f781db6ae516889a79178393d14200ab4bdeffce8ca9d159abee4ac25a19b
resource-agents-aliyun-4.1.1-12.el7_6.7.x86_64.rpm
134ad788dcf01a4d360e4afef1b60b9f0fc2e443ad3d0565a54e44659628c36b
resource-agents-gcp-4.1.1-12.el7_6.7.x86_64.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS
--
Message: 2
Date: Wed, 19 Dec 2018 03:22:11 +
From: Johnny Hughes
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2018:3834 Important CentOS 7
ghostscript Security Update
Message-ID: <20181219032211.ga...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2018:3834 Important
Upstream details at : https://access.redhat.com/errata/RHSA-2018:3834
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
b02281b3f40e29efcc842714d9704763bce7f21f0b358a4246074513ec71da18
ghostscript-9.07-31.el7_6.6.i686.rpm
94a6c73acd88ad8c61fae422a2557f25d016c8301a5904ad416794934512af1e
ghostscript-9.07-31.el7_6.6.x86_64.rpm
1a986c609ec1e7b11daeae3052847fabee509bfb40fe6188011673d990441223
ghostscript-cups-9.07-31.el7_6.6.x86_64.rpm
16c32cdf0ba38d3e109b5855a735c4d23d0cf11c2775a4dff31934a4c6c183fa
ghostscript-devel-9.07-31.el7_6.6.i686.rpm
1ff0115fd9a2c9479bf9d1e490786303e53253d0aaa6b508728e671a19abfd0f
ghostscript-devel-9.07-31.el7_6.6.x86_64.rpm
896fdf02ca354030aad6e2e71ffbcd49eb5a9d285d19e9f18ef03a5241e9a9be
ghostscript-doc-9.07-31.el7_6.6.noarch.rpm
08a063cfd502e270eb11bee7c13b68c7d1a1fed4b13f0a8060490c704d75f3c7
ghostscript-gtk-9.07-31.el7_6.6.x86_64.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS
--
Subject: Digest Footer
___
CentOS-announce mailing list
centos-annou...@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce
--
End of CentOS-announce Digest, Vol 166, Issue 5
***
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] VNC question
Mike McCarthy, W1NR writes: > > On 12/19/18 4:36 AM, isdtor wrote: > > We have run into the infamous black screen problem with tigervnc under > > CentOS7, which prompted me to look into how vnc is configured here. > > > > https://access.redhat.com/solutions/966063 > > > > Am I reading this correctly - root needs to set up a systemd vnc service > > for every user and display individually? Compared to e.g. CentOS before 7, > > or indeed any other Linux/Unix system where vnc is completely under user > > control? > > > > openSUSE always spawned VNC sessions for each user through xinetd. The > user did not have "control" of the sessions. Noted. > Do you get a login screen? Does the screen go "black" after login? If > so, in my experience, the user logging in already has a desktop session > running (usually on the console). Make sure to try logging in with a > user that is not already logged in. Linux can deal with multiple > DIFFERENT users logged in but the desktops can only deal with one login > and home directory per user. What you describe doesn't make much sense to me either. In this case, there are no user logins on the console, this is meant to be a remote login server. Anyone logging in via vnc gets the black screen treatment. There is no login screen, only the vnc password prompt. For this type of machine, multi-user.target should be sufficient, although it is set to graphical.target right now. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] VNC question
On 12/19/18 4:36 AM, isdtor wrote: > We have run into the infamous black screen problem with tigervnc under > CentOS7, which prompted me to look into how vnc is configured here. > > https://access.redhat.com/solutions/966063 > > Am I reading this correctly - root needs to set up a systemd vnc service for > every user and display individually? Compared to e.g. CentOS before 7, or > indeed any other Linux/Unix system where vnc is completely under user control? > openSUSE always spawned VNC sessions for each user through xinetd. The user did not have "control" of the sessions. Do you get a login screen? Does the screen go "black" after login? If so, in my experience, the user logging in already has a desktop session running (usually on the console). Make sure to try logging in with a user that is not already logged in. Linux can deal with multiple DIFFERENT users logged in but the desktops can only deal with one login and home directory per user. Mike, W1NR ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] VNC question
We have run into the infamous black screen problem with tigervnc under CentOS7, which prompted me to look into how vnc is configured here. https://access.redhat.com/solutions/966063 Am I reading this correctly - root needs to set up a systemd vnc service for every user and display individually? Compared to e.g. CentOS before 7, or indeed any other Linux/Unix system where vnc is completely under user control? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
