Re: [CentOS-docs] Artwork localization
That's cool Timo! On May 23, 2019 5:39 AM, "Alain Reguera Delgado" wrote: > Hi Timothy, > > On Thu, 2019-05-23 at 14:03 +1000, Timothy Lee wrote: > > I can provide zh-CN, zh-HK and zh-TW translations of the content. > > That's awesome! > > The files you need to edit are the following: > > - Rolling notes of CentOS installer > > https://git.centos.org/centos/Artwork/blob/c8/f/rnotes/PO/zh-CN.po > https://git.centos.org/centos/Artwork/blob/c8/f/rnotes/PO/zh-HK.po > https://git.centos.org/centos/Artwork/blob/c8/f/rnotes/PO/zh-TW.po > > - Test page of Apache HTTP web server and Default browser web page > > https://git.centos.org/centos/Artwork/blob/c8/f/html/PO/zh-CN.po > https://git.centos.org/centos/Artwork/blob/c8/f/html/PO/zh-HK.po > https://git.centos.org/centos/Artwork/blob/c8/f/html/PO/zh-TW.po > > To make the changes, you probably want to clone the repo, fill them > with translations and push the changes back to the repository. In case > you don't have push access, you can send me the files directly to me > and request push access to Fabian so you can take care of these files > yourself in the future. > > Very exciting to see artwork translated to zh! :) > > Thank you Timothy, > -- > Alain Reguera Delgado > > ___ > CentOS-docs mailing list > CentOS-docs@centos.org > https://lists.centos.org/mailman/listinfo/centos-docs > > ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] Artwork localization
Hi Timothy, On Thu, 2019-05-23 at 14:03 +1000, Timothy Lee wrote: > I can provide zh-CN, zh-HK and zh-TW translations of the content. That's awesome! The files you need to edit are the following: - Rolling notes of CentOS installer https://git.centos.org/centos/Artwork/blob/c8/f/rnotes/PO/zh-CN.po https://git.centos.org/centos/Artwork/blob/c8/f/rnotes/PO/zh-HK.po https://git.centos.org/centos/Artwork/blob/c8/f/rnotes/PO/zh-TW.po - Test page of Apache HTTP web server and Default browser web page https://git.centos.org/centos/Artwork/blob/c8/f/html/PO/zh-CN.po https://git.centos.org/centos/Artwork/blob/c8/f/html/PO/zh-HK.po https://git.centos.org/centos/Artwork/blob/c8/f/html/PO/zh-TW.po To make the changes, you probably want to clone the repo, fill them with translations and push the changes back to the repository. In case you don't have push access, you can send me the files directly to me and request push access to Fabian so you can take care of these files yourself in the future. Very exciting to see artwork translated to zh! :) Thank you Timothy, -- Alain Reguera Delgado signature.asc Description: This is a digitally signed message part ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS] system unresponsive
On Wed, May 22, 2019 at 10:22 AM mark wrote: > It seems unlikely. It's a 4U server, with 36 disks (and the dual root > disks), in a machine room, and ipmitool sel list shows nada, nor are there > any warnings, as I've seen on other systems occasionally, that the CPU is > overheating, and is being throttled. If this is a recent sever (ivybridge/haswell/broadwell) then I’ve seen the “edac” kernel module prevent SEL from showing faults when a MCE/machine-check-exception occurs. Disable edac and poof server stops crashing and/or SEL shows something useful(ECC/MCE). Did you check /var/log/mcelog? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS-docs] Artwork localization
Hi Alain, I can provide zh-CN, zh-HK and zh-TW translations of the content. Regards, Timothy On 23/5/19 1:45 pm, Alain Reguera Delgado wrote: Hello everyone, What do you think about having localized the following CentOS components: - Rolling notes in CentOS installer. These images are shown during the installation process, once the configuration is done and you are waiting for packages to be installed. Rolling notes are a great place to promote CentOS. If they are not localized, they are shown in English language by default. Examples: https://wiki.centos.org/ArtWork/Motifs/CentOS8/Sketch4#head-02a69ab732144b3fe18ca49d624f380ec291dd7c - Test page for Apache HTTP web server This is the web page you see on a recently installed Apache HTTP web sever and no index file is found at /var/www/html/, just to test the proper operation of the web server. If it is not localized, it is shown in English language by default. Examples: https://wiki.centos.org/ArtWork/Motifs/CentOS8/Sketch4#head-4db19ac219c065be719a6daf8fa93d1b857a3cfa - Default browser web page This is the web page you see when you open the web browser. If it is not localized, it is shown in English language by default. Examples: https://wiki.centos.org/ArtWork/Motifs/CentOS8/Sketch4#head-bfdac511aad81b2276fc7d70167544bf8df2995c Is there any translator interested aboard? Best regards, ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
[CentOS-docs] Artwork localization
Hello everyone, What do you think about having localized the following CentOS components: - Rolling notes in CentOS installer. These images are shown during the installation process, once the configuration is done and you are waiting for packages to be installed. Rolling notes are a great place to promote CentOS. If they are not localized, they are shown in English language by default. Examples: https://wiki.centos.org/ArtWork/Motifs/CentOS8/Sketch4#head-02a69ab732144b3fe18ca49d624f380ec291dd7c - Test page for Apache HTTP web server This is the web page you see on a recently installed Apache HTTP web sever and no index file is found at /var/www/html/, just to test the proper operation of the web server. If it is not localized, it is shown in English language by default. Examples: https://wiki.centos.org/ArtWork/Motifs/CentOS8/Sketch4#head-4db19ac219c065be719a6daf8fa93d1b857a3cfa - Default browser web page This is the web page you see when you open the web browser. If it is not localized, it is shown in English language by default. Examples: https://wiki.centos.org/ArtWork/Motifs/CentOS8/Sketch4#head-bfdac511aad81b2276fc7d70167544bf8df2995c Is there any translator interested aboard? Best regards, -- Alain Reguera Delgado signature.asc Description: This is a digitally signed message part ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS] system unresponsive
On 5/22/19 6:57 AM, Scott Silverman wrote: In the past I've found that the console may have blanked (due to time) and when the system locked up/hung it won't unblank. Booting with "consoleblank=0" on the kernel command line will ensure that whatever is printed to the console (oops, panic, etc) will be there for you to see when you connect. I would definitely start here. If the system locks and there's no oops printed to the screen, then you almost certainly have a hardware issue. If there *is* an oops printed, you might still have a hardware issue, but the oops will probably give you some direction on tracking it down. At some point, you'll probably want to schedule as many hours of down time as possible and run memtest86+ I've had intermittent success in that type of situation with the SysRq key(s), seehttps://en.wikipedia.org/wiki/Magic_SysRq_key . If the console isn't coming back on keyboard activity, then the system is probably hard-locked, and sysrq keys aren't going to work. Probably. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Bypassing 'A stop job is running' when rebooting CentOS 7
On Wed, May 22, 2019 at 03:41:24PM -0400, Jon LaBadie wrote: > On Wed, May 22, 2019 at 09:07:32AM -0600, James Szinger wrote: > > On Wed, May 22, 2019 at 7:44 AM mark wrote: > > > > > > The joys of systemd > > > > I'm not sure it's right to blame systemd. Systemd asked nicely for > > the service to shutdown. > > But we can blame systemd for the cryptic message > > A stop job is running I didn't read this thread all that carefully, but has anyone mentioned editing /etc/systemd/system.conf and changing DefaultTimeoutStartSec and DefaultTimeoutStopSec to a lower value? -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Bypassing 'A stop job is running' when rebooting CentOS 7
On Wed, May 22, 2019 at 09:07:32AM -0600, James Szinger wrote: > On Wed, May 22, 2019 at 7:44 AM mark wrote: > > > > The joys of systemd > > I'm not sure it's right to blame systemd. Systemd asked nicely for > the service to shutdown. But we can blame systemd for the cryptic message A stop job is running Surely systemd knows what service it is waiting for, why doesn't it tell us? The stop job XYZ is running jon -- Jon H. LaBadie j...@jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C) ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] how to find out the number of updates for a system
Chris Adams wrote: > Once upon a time, mark said: > >> Ralf Prengel wrote: >> >>> Hallo, >>> I need the information how many updates are available for a system. >>> What is the best way to find it out in a one line bash script. >>> >>> >> yum check-update, perhaps? > > Note that "yum check-update" or "yum list updates" won't tell you how > many packages would be installed with "yum update"... dependencies and such > are not resolved for check-update/list updates. > Ok, you want it all, fine: echo "n" | yum update | egrep "Install|Upgrade" mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] how to find out the number of updates for a system
Nice one, -q However that command will still count an empty line that yum outputs, even with -q; it could also create problems due to stderr. I'd use something like: yum -q check-update 2>/dev/null|grep -c -v ^$ -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "SternData" > To: "CentOS mailing list" > Sent: Wednesday, 22 May, 2019 16:03:39 > Subject: Re: [CentOS] how to find out the number of updates for a system > maybe > yum -q check-update | wc -l > > On 5/22/19 8:42 AM, Ralf Prengel wrote: >> Hallo, >> I need the information how many updates are available for a system. >> What is the best way to find it out in a one line bash script. >> >> Von meinem iPad gesendet >> ___ >> CentOS mailing list >> CentOS@centos.org >> https://lists.centos.org/mailman/listinfo/centos >> > > > -- > -- Steve > ___ > 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] Bypassing 'A stop job is running' when rebooting CentOS 7
Once upon a time, James Szinger said: > On Wed, May 22, 2019 at 7:44 AM mark wrote: > > The joys of systemd > > I'm not sure it's right to blame systemd. Systemd asked nicely for > the service to shutdown. The service didn't, probably because the > update change something and pulled the rug out from beneath it. Right - before systemd, any old init script could also block shutdown. > This hasn't happened to me recently, but I think I've tried Ctl-C and > Ctl-Alt-Del without much success. That leaves the Big Red Switch > (which is mostly small and black these days). There's a "magic" thing systemd does now - hit C-A-D seven times in two seconds and it'll stop what it is waiting for and just go ahead and reboot. Will kill anything not shut down, but at least it'll still try to cleanly unmount filesystems and such I believe. -- Chris Adams ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Bypassing 'A stop job is running' when rebooting CentOS 7
On Wed, May 22, 2019 at 7:44 AM mark wrote: > > The joys of systemd I'm not sure it's right to blame systemd. Systemd asked nicely for the service to shutdown. The service didn't, probably because the update change something and pulled the rug out from beneath it. Systemd then waited a bit to make sure the service wasn't just being slow, and finally gave up and forcibly killed it. I think this is a reasonable approach to killing a misbehaving service while trying to minimize data-loss, and the timeout can be configured. This hasn't happened to me recently, but I think I've tried Ctl-C and Ctl-Alt-Del without much success. That leaves the Big Red Switch (which is mostly small and black these days). Jim ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] how to find out the number of updates for a system
maybe yum -q check-update | wc -l On 5/22/19 8:42 AM, Ralf Prengel wrote: > Hallo, > I need the information how many updates are available for a system. > What is the best way to find it out in a one line bash script. > > Von meinem iPad gesendet > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > -- -- Steve ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] how to find out the number of updates for a system
Once upon a time, John Pierce said: > otoh, its pretty rare that an update has a new dependency...if the > package is installed, its existing dependencies are also installed, and if > they have updates, check-update would show them all, would it not? It's not as rare as you might think, especially at point-release time. There are often new dependencies when packages get updates beyond just bug patching, sometimes an installed package might get obsoleted by a different package (can't remember if that shows up in check-update), etc. -- Chris Adams ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] system unresponsive
Noam Bernstein via CentOS wrote: > Out of memory? We’ve definitely seen similar symptoms (it’s been a > while, so I’m not sure they were identical) for compute nodes running > large memory jobs. That seems unlikely. Foe one, I've seen that... but I *always* see entries in the log about the oom-killer being invoked. For another, this isn't a compute node, it's *only* a fileserver, serving projects, home directories, and backups (home-grown b/u, uses rsync), and backups don't start until well after midnight, and as we're business-hours only, there was less usage, and it does have 256G RAM mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] how to find out the number of updates for a system
On Wed, May 22, 2019 at 7:49 AM Chris Adams wrote: > Once upon a time, mark said: > > Ralf Prengel wrote: > > > Hallo, > > > I need the information how many updates are available for a system. > > > What is the best way to find it out in a one line bash script. > > > > > yum check-update, perhaps? > > Note that "yum check-update" or "yum list updates" won't tell you how > many packages would be installed with "yum update"... dependencies and > such are not resolved for check-update/list updates. otoh, its pretty rare that an update has a new dependency...if the package is installed, its existing dependencies are also installed, and if they have updates, check-update would show them all, would it not? -- -john r pierce recycling used bits in santa cruz ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] how to find out the number of updates for a system
You might want to increase 1000 if you expect to have more than that number of updates :) -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Nux!" > To: "CentOS mailing list" > Sent: Wednesday, 22 May, 2019 15:48:00 > Subject: Re: [CentOS] how to find out the number of updates for a system > yum check-updates 2>/dev/null|grep -A1000 "^$"|grep -vc "^$" > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > - Original Message - >> From: "Ralf Prengel" >> To: "CentOS mailing list" >> Sent: Wednesday, 22 May, 2019 14:42:53 >> Subject: [CentOS] how to find out the number of updates for a system > >> Hallo, >> I need the information how many updates are available for a system. >> What is the best way to find it out in a one line bash script. >> >> Von meinem iPad gesendet >> ___ >> 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] how to find out the number of updates for a system
Once upon a time, mark said: > Ralf Prengel wrote: > > Hallo, > > I need the information how many updates are available for a system. > > What is the best way to find it out in a one line bash script. > > > yum check-update, perhaps? Note that "yum check-update" or "yum list updates" won't tell you how many packages would be installed with "yum update"... dependencies and such are not resolved for check-update/list updates. -- Chris Adams ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] how to find out the number of updates for a system
yum check-updates 2>/dev/null|grep -A1000 "^$"|grep -vc "^$" -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Ralf Prengel" > To: "CentOS mailing list" > Sent: Wednesday, 22 May, 2019 14:42:53 > Subject: [CentOS] how to find out the number of updates for a system > Hallo, > I need the information how many updates are available for a system. > What is the best way to find it out in a one line bash script. > > Von meinem iPad gesendet > ___ > 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] Bypassing 'A stop job is running' when rebooting CentOS 7
mark wrote: > James Pearson wrote: >> James Pearson wrote: >> >>> >>> I'm currently trying to reboot a CentOS 7.5 workstation (to complete an >>> upgrade to 7.6), but it is 'stuck' while shutting down with 'A stop >>> job is running for ...' - the counter initially gave a limit of '1min >>> 30s' - >>> but each time it reaches that limit, it just adds on ~90 seconds to the >>> limit ... >>> >>> Currently the limit is '25min 33s' >>> >>> >>> I'm in no hurry to have this workstation operational, but I guess at >>> some point I will have to power cycle it ... >>> >>> Does anyone know how to bypass this? - or at least stop it increasing >>> the limit each time it is reached? >>> >>> It does seems rather pointless to keep increasing the limit like this >>> ... >>> >> It _finally_ gave up at 30 mins and rebooted > > One question: did it have a mounted nfs filesystem? All our boxes have NFS mounted files systems - and usually this isn't a problem - reboots work without an issue In this case, it appeared to be 'stuck' on a local file bind mounted over a file on an NFS mounted file system But that isn't really the point - I don't really want to have to wait a maximum of 30 minutes for the reboot to give up waiting for 'whatever' Poking about a bit, I see that /usr/lib/systemd/system/reboot.target has the line: JobTimeoutSec=30min (there is a similar JobTimeoutSec=30min in poweroff.target) I'm guessing I could create something like /etc/systemd/system/reboot.target.d/override.conf containing something like: [Unit] JobTimeoutSec=3min Now I need to see if I can reproduce the issue and see if this setting works ... James Pearson ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] how to find out the number of updates for a system
Hey Mark,
one quick and dirty possibility:
a=`yum check-updates | awk '{ print $2 }' |grep -v ":" |grep -v mirror |wc
-l` ; echo $(($a - 1))
Best regards
Steffen
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] system unresponsive
Out of memory? We’ve definitely seen similar symptoms (it’s been a while, so I’m not sure they were identical) for compute nodes running large memory jobs. Noam ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] system unresponsive
Scott Silverman wrote: > In the past I've found that the console may have blanked (due to time) > and when the system locked up/hung it won't unblank. Booting with > "consoleblank=0" on the kernel command line will ensure that whatever is > printed to the console (oops, panic, etc) will be there for you to see > when you connect. > > I've had intermittent success in that type of situation with the SysRq > key(s), see https://en.wikipedia.org/wiki/Magic_SysRq_key . They do > require that you have it configured/enabled ahead of time. If you access > the console over a BMC/IPMI KVM session it can be very difficult, if not > impossible, to enter the keystroke as well. > Hmmm... thanks. I'm sure I've heard about the magic sysreq, but had forgotten, never used it. I'll try that if this happens again. mark > Good luck, > Scott > > > > > > > On Wed, May 22, 2019 at 8:46 AM Stephen John Smoogen > wrote: > > >> On Wed, 22 May 2019 at 09:30, mark wrote: >> >> >>> Ok, we used to get this occasionally on cluster nodes, and we just >>> got it on a fileserver (very bad). The system is discovered to be >>> unresponsive: >>> it doesn't ping, and plugging a console in, you can see that it's not >>> dead, but there nothing at all on the screen, nor does it respond to >>> even . The only answer is to power cycle it; it comes up >>> fine. >>> >>> Nothing in /var/log/dmesg or /var/log/messages. No abrts I can find. >>> sar tells me it went unredponsive between 18:10 and 10:20 yesterday. >>> Note >>> >> that >>> there are no further entries in sar, either, for yesterday, after the >>> event, and nothing till I power cycled it. >>> >>> >> From the above description, I would normally say it sounds like >> hardware. However, why do you say the system is not dead when you plug >> in a console.. but there is nothing on the screen and it doesn't respond >> to control-alt-delete. To me that sounds like 'dead'. Usually the cpu is >> hardlocked or the hardware went into 'over-heat' and put everything in >> a deep sleep hoping it would cool down but never wake up. >> >> >> >>> Has anyone else seen this - I can't imagine it's only us - or have >>> any thoughts? >>> >>> C 7, 7.6.1810 >>> >>> >>> mark >>> >>> >>> ___ >>> CentOS mailing list >>> CentOS@centos.org >>> https://lists.centos.org/mailman/listinfo/centos >>> >>> >> >> >> -- >> Stephen J Smoogen. >> ___ >> CentOS mailing list >> CentOS@centos.org >> https://lists.centos.org/mailman/listinfo/centos >> >> > > -- > DISCLAIMER: NOTICE REGARDING PRIVACY AND CONFIDENTIALITY > > > The information > contained in and/or accompanying this communication is intended only for > use by the addressee(s) named herein and may contain legally privileged > and/or confidential information. If you are not the intended recipient of > this e-mail, you are hereby notified that any dissemination, > distribution or copying of this information, and any attachments thereto, > is strictly prohibited. If you have received this e-mail in error, please > immediately notify the sender and permanently delete the original and any > copy of any e-mail and any printout thereof. Electronic transmissions > cannot be guaranteed to be secure or error-free. The sender therefore does > not accept liability for any errors or omissions in the contents of this > message which arise as a result of e-mail transmission. Simplex Trading, > LLC and its > affiliates reserves the right to intercept, monitor, and retain electronic > communications to and from its system as permitted by law. Simplex > Trading, > LLC is a registered Broker Dealer with CBOE and a Member of SIPC. > ___ > 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] system unresponsive
Stephen John Smoogen wrote: > On Wed, 22 May 2019 at 09:30, mark wrote: > >> Ok, we used to get this occasionally on cluster nodes, and we just got >> it on a fileserver (very bad). The system is discovered to be >> unresponsive: >> it doesn't ping, and plugging a console in, you can see that it's not >> dead, but there nothing at all on the screen, nor does it respond to >> even . The only answer is to power cycle it; it comes up >> fine. >> >> Nothing in /var/log/dmesg or /var/log/messages. No abrts I can find. >> sar tells me it went unredponsive between 18:10 and 10:20 yesterday. >> Note that >> there are no further entries in sar, either, for yesterday, after the >> event, and nothing till I power cycled it. >> > From the above description, I would normally say it sounds like hardware. > However, why do you say the system is not dead when you plug in a > console.. but there is nothing on the screen and it doesn't respond to > control-alt-delete. To me that sounds like 'dead'. Usually the cpu is > hardlocked or the hardware went into 'over-heat' and put everything in a > deep sleep hoping it would cool down but never wake up. > It seems unlikely. It's a 4U server, with 36 disks (and the dual root disks), in a machine room, and ipmitool sel list shows nada, nor are there any warnings, as I've seen on other systems occasionally, that the CPU is overheating, and is being throttled. > > >> Has anyone else seen this - I can't imagine it's only us - or have any >> thoughts? >> >> C 7, 7.6.1810 >> >> >> mark >> >> >> ___ >> CentOS mailing list >> CentOS@centos.org >> https://lists.centos.org/mailman/listinfo/centos >> >> > > > -- > Stephen J Smoogen. > ___ > 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] how to find out the number of updates for a system
Ralf Prengel wrote: > Hallo, > I need the information how many updates are available for a system. > What is the best way to find it out in a one line bash script. > yum check-update, perhaps? mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] system unresponsive
> Ok, we used to get this occasionally on cluster nodes, and we just got it > on a fileserver (very bad). The system is discovered to be unresponsive: > it doesn't ping, and plugging a console in, you can see that it's not > dead, but there nothing at all on the screen, nor does it respond to even > . The only answer is to power cycle it; it comes up fine. > > Nothing in /var/log/dmesg or /var/log/messages. No abrts I can find. sar > tells me it went unredponsive between 18:10 and 10:20 yesterday. Note that > there are no further entries in sar, either, for yesterday, after the > event, and nothing till I power cycled it. > > Has anyone else seen this - I can't imagine it's only us - or have any > thoughts? > > C 7, 7.6.1810 I saw such an issue recently and never found out what happened and why. Regards, Simon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Bypassing 'A stop job is running' when rebooting CentOS 7
On 22/05/2019 14:43, mark wrote: > James Pearson wrote: >> James Pearson wrote: >> >>> >>> I'm currently trying to reboot a CentOS 7.5 workstation (to complete an >>> upgrade to 7.6), but it is 'stuck' while shutting down with 'A stop >>> job is running for ...' - the counter initially gave a limit of '1min >>> 30s' - >>> but each time it reaches that limit, it just adds on ~90 seconds to the >>> limit ... >>> >>> Currently the limit is '25min 33s' >>> >>> >>> I'm in no hurry to have this workstation operational, but I guess at >>> some point I will have to power cycle it ... >>> >>> Does anyone know how to bypass this? - or at least stop it increasing >>> the limit each time it is reached? >>> >>> It does seems rather pointless to keep increasing the limit like this >>> ... >>> >> It _finally_ gave up at 30 mins and rebooted > > One question: did it have a mounted nfs filesystem? > > The joys of systemd > > mark > > mark > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > "Anything Windows can do, systemd can do better" (with apologies to Irving Berlin). -- J Martin Rushton MBCS signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] PHP 7.3 and IUS repo
On 5/22/19 6:47 AM, SternData wrote: Does anyone know if PHP 7.3 is coming to the IUS repo soon? I'd rather upgrade from 7.2 than tear out IUS and replace with Remi. Looks like: https://github.com/iusrepo/wishlist/issues/219#issuecomment-488876644 might be relevant? I recall seeing sometime back the need to either update the ius-release RPM, or manually update the repo location, probably due to the new CDN setup they're using. -Greg ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] system unresponsive
In the past I've found that the console may have blanked (due to time) and when the system locked up/hung it won't unblank. Booting with "consoleblank=0" on the kernel command line will ensure that whatever is printed to the console (oops, panic, etc) will be there for you to see when you connect. I've had intermittent success in that type of situation with the SysRq key(s), see https://en.wikipedia.org/wiki/Magic_SysRq_key . They do require that you have it configured/enabled ahead of time. If you access the console over a BMC/IPMI KVM session it can be very difficult, if not impossible, to enter the keystroke as well. Good luck, Scott On Wed, May 22, 2019 at 8:46 AM Stephen John Smoogen wrote: > On Wed, 22 May 2019 at 09:30, mark wrote: > > > Ok, we used to get this occasionally on cluster nodes, and we just got it > > on a fileserver (very bad). The system is discovered to be unresponsive: > > it doesn't ping, and plugging a console in, you can see that it's not > > dead, but there nothing at all on the screen, nor does it respond to even > > . The only answer is to power cycle it; it comes up fine. > > > > Nothing in /var/log/dmesg or /var/log/messages. No abrts I can find. sar > > tells me it went unredponsive between 18:10 and 10:20 yesterday. Note > that > > there are no further entries in sar, either, for yesterday, after the > > event, and nothing till I power cycled it. > > > > > From the above description, I would normally say it sounds like hardware. > However, why do you say the system is not dead when you plug in a console.. > but there is nothing on the screen and it doesn't respond to > control-alt-delete. To me that sounds like 'dead'. Usually the cpu is > hardlocked or the hardware went into 'over-heat' and put everything in a > deep sleep hoping it would cool down but never wake up. > > > > > Has anyone else seen this - I can't imagine it's only us - or have any > > thoughts? > > > > C 7, 7.6.1810 > > > > mark > > > > > > ___ > > CentOS mailing list > > CentOS@centos.org > > https://lists.centos.org/mailman/listinfo/centos > > > > > -- > Stephen J Smoogen. > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > -- DISCLAIMER: NOTICE REGARDING PRIVACY AND CONFIDENTIALITY The information contained in and/or accompanying this communication is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this information, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy of any e-mail and any printout thereof. Electronic transmissions cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. Simplex Trading, LLC and its affiliates reserves the right to intercept, monitor, and retain electronic communications to and from its system as permitted by law. Simplex Trading, LLC is a registered Broker Dealer with CBOE and a Member of SIPC. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Bypassing 'A stop job is running' when rebooting CentOS 7
> James Pearson wrote: >> James Pearson wrote: >> >>> >>> I'm currently trying to reboot a CentOS 7.5 workstation (to complete an >>> upgrade to 7.6), but it is 'stuck' while shutting down with 'A stop >>> job is running for ...' - the counter initially gave a limit of '1min >>> 30s' - >>> but each time it reaches that limit, it just adds on ~90 seconds to the >>> limit ... >>> >>> Currently the limit is '25min 33s' >>> >>> >>> I'm in no hurry to have this workstation operational, but I guess at >>> some point I will have to power cycle it ... >>> >>> Does anyone know how to bypass this? - or at least stop it increasing >>> the limit each time it is reached? >>> >>> It does seems rather pointless to keep increasing the limit like this >>> ... >>> >> It _finally_ gave up at 30 mins and rebooted > > One question: did it have a mounted nfs filesystem? > > The joys of systemd Yes, NFS integration with systemd is broken by default, at least it was still the case when I last checked. If you want it to work correctly, you have to add 'x-systemd.requires=network-online.target' as NFS mount option. Clearly, how should systemd know that NFS won't work without network? I knew you agree :-) Regards, Simon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] PHP 7.3 and IUS repo
Does anyone know if PHP 7.3 is coming to the IUS repo soon? I'd rather upgrade from 7.2 than tear out IUS and replace with Remi. -- -- Steve ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] system unresponsive
On Wed, 22 May 2019 at 09:30, mark wrote: > Ok, we used to get this occasionally on cluster nodes, and we just got it > on a fileserver (very bad). The system is discovered to be unresponsive: > it doesn't ping, and plugging a console in, you can see that it's not > dead, but there nothing at all on the screen, nor does it respond to even > . The only answer is to power cycle it; it comes up fine. > > Nothing in /var/log/dmesg or /var/log/messages. No abrts I can find. sar > tells me it went unredponsive between 18:10 and 10:20 yesterday. Note that > there are no further entries in sar, either, for yesterday, after the > event, and nothing till I power cycled it. > > >From the above description, I would normally say it sounds like hardware. However, why do you say the system is not dead when you plug in a console.. but there is nothing on the screen and it doesn't respond to control-alt-delete. To me that sounds like 'dead'. Usually the cpu is hardlocked or the hardware went into 'over-heat' and put everything in a deep sleep hoping it would cool down but never wake up. > Has anyone else seen this - I can't imagine it's only us - or have any > thoughts? > > C 7, 7.6.1810 > > mark > > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > -- Stephen J Smoogen. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Bypassing 'A stop job is running' when rebooting CentOS 7
James Pearson wrote: > James Pearson wrote: > >> >> I'm currently trying to reboot a CentOS 7.5 workstation (to complete an >> upgrade to 7.6), but it is 'stuck' while shutting down with 'A stop >> job is running for ...' - the counter initially gave a limit of '1min >> 30s' - >> but each time it reaches that limit, it just adds on ~90 seconds to the >> limit ... >> >> Currently the limit is '25min 33s' >> >> >> I'm in no hurry to have this workstation operational, but I guess at >> some point I will have to power cycle it ... >> >> Does anyone know how to bypass this? - or at least stop it increasing >> the limit each time it is reached? >> >> It does seems rather pointless to keep increasing the limit like this >> ... >> > It _finally_ gave up at 30 mins and rebooted One question: did it have a mounted nfs filesystem? The joys of systemd mark mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] how to find out the number of updates for a system
Hallo, I need the information how many updates are available for a system. What is the best way to find it out in a one line bash script. Von meinem iPad gesendet ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] system unresponsive
Ok, we used to get this occasionally on cluster nodes, and we just got it on a fileserver (very bad). The system is discovered to be unresponsive: it doesn't ping, and plugging a console in, you can see that it's not dead, but there nothing at all on the screen, nor does it respond to even . The only answer is to power cycle it; it comes up fine. Nothing in /var/log/dmesg or /var/log/messages. No abrts I can find. sar tells me it went unredponsive between 18:10 and 10:20 yesterday. Note that there are no further entries in sar, either, for yesterday, after the event, and nothing till I power cycled it. Has anyone else seen this - I can't imagine it's only us - or have any thoughts? C 7, 7.6.1810 mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Bypassing 'A stop job is running' when rebooting CentOS 7
James Pearson wrote: > > I'm currently trying to reboot a CentOS 7.5 workstation (to complete an > upgrade to 7.6), but it is 'stuck' while shutting down with 'A stop job > is running for ...' - the counter initially gave a limit of '1min 30s' - > but each time it reaches that limit, it just adds on ~90 seconds to the > limit ... > > Currently the limit is '25min 33s' > > I'm in no hurry to have this workstation operational, but I guess at > some point I will have to power cycle it ... > > Does anyone know how to bypass this? - or at least stop it increasing > the limit each time it is reached? > > It does seems rather pointless to keep increasing the limit like this ... It _finally_ gave up at 30 mins and rebooted James Pearson ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Bypassing 'A stop job is running' when rebooting CentOS 7
I'm currently trying to reboot a CentOS 7.5 workstation (to complete an upgrade to 7.6), but it is 'stuck' while shutting down with 'A stop job is running for ...' - the counter initially gave a limit of '1min 30s' - but each time it reaches that limit, it just adds on ~90 seconds to the limit ... Currently the limit is '25min 33s' I'm in no hurry to have this workstation operational, but I guess at some point I will have to power cycle it ... Does anyone know how to bypass this? - or at least stop it increasing the limit each time it is reached? It does seems rather pointless to keep increasing the limit like this ... Thanks James Pearson ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS-announce Digest, Vol 171, Issue 6
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. CESA-2019:1235 Important CentOS 7 ruby Security Update
(Johnny Hughes)
2. CESA-2019:1228 Important CentOS 7 wget Security Update
(Johnny Hughes)
--
Message: 1
Date: Tue, 21 May 2019 21:25:00 +
From: Johnny Hughes
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2019:1235 Important CentOS 7 ruby
SecurityUpdate
Message-ID: <20190521212500.ga23...@bstore1.rdu2.centos.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2019:1235 Important
Upstream details at : https://access.redhat.com/errata/RHSA-2019:1235
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
9e0846fdebaef8c4624eda4c19bff666ea4745e9ea1d14f6024ed9f21d8360dd
ruby-2.0.0.648-35.el7_6.x86_64.rpm
abfac4241ae505c169b749a2719697253cab914596a009a8c3d6438eb6ae9e33
ruby-devel-2.0.0.648-35.el7_6.x86_64.rpm
a320ee8f92e04451a3e13e004c3bb97c566c3fc33816ccf3dacbd64af6f08aad
ruby-doc-2.0.0.648-35.el7_6.noarch.rpm
74bbfd1e5e60ccdbb21780321d43f1e0c47db34875456abd836322a230ff1248
rubygem-bigdecimal-1.2.0-35.el7_6.x86_64.rpm
b34883cec12846fe857de72f80202795efabf621a6ac6169635c06258b2bc2a9
rubygem-io-console-0.4.2-35.el7_6.x86_64.rpm
a7d83c6e48dd574d2d1c2cb2e0ff5ae10ac6ee6503e75565aa7e7261a45abdd8
rubygem-json-1.7.7-35.el7_6.x86_64.rpm
6f1e9282b3299eae0cdde3f4a58b344cc209a454bbb98713d8621dd26a2a0017
rubygem-minitest-4.3.2-35.el7_6.noarch.rpm
b589ee6e6951b615aa47d6f42fc5cfd59ece39afe50928f15414c0bfe5fcbfb2
rubygem-psych-2.0.0-35.el7_6.x86_64.rpm
628fe45f582dc592dad49bee6dda4592d0f8cf808d57d23547ab742da7cadad7
rubygem-rake-0.9.6-35.el7_6.noarch.rpm
acdcf1bc892a7a4b067c9450a3bea0dffea32fed9fc4306f85e91cb13b9584c2
rubygem-rdoc-4.0.0-35.el7_6.noarch.rpm
881976d81db3d5cd5d4f7e2ee5340a48347f28641de758f3b58c812ff72b19dc
rubygems-2.0.14.1-35.el7_6.noarch.rpm
4a467ce67316850ef445366eaba5829dd2c17d5d133e2960a69a8b8b81199b2c
rubygems-devel-2.0.14.1-35.el7_6.noarch.rpm
7e92adc7435f71f15f6a7b903244b28bb241c63f9936bb09792f017fef66
ruby-irb-2.0.0.648-35.el7_6.noarch.rpm
cce7722f237440d4b287ac48f803e58f4e58792a1b3517bb0947c52741880080
ruby-libs-2.0.0.648-35.el7_6.i686.rpm
8ad4f163c76e641b1b0d9c62da22dcc03283c8a4966ebfb8e9e4306f0e36775b
ruby-libs-2.0.0.648-35.el7_6.x86_64.rpm
bc769ba399cd0ce49b9ed31a294b3c363642e5501346680c3792ae1ee58e10e2
ruby-tcltk-2.0.0.648-35.el7_6.x86_64.rpm
Source:
b1b6bd22e0b3b3c038fc285a88166d145ddcaadbef794dfbd0df44b93a703715
ruby-2.0.0.648-35.el7_6.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS
--
Message: 2
Date: Tue, 21 May 2019 21:26:07 +
From: Johnny Hughes
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2019:1228 Important CentOS 7 wget
SecurityUpdate
Message-ID: <20190521212607.ga23...@bstore1.rdu2.centos.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2019:1228 Important
Upstream details at : https://access.redhat.com/errata/RHSA-2019:1228
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
229d6e173f22a647c8db9c8e7d0b21c8f86dd4e270abb96548aa40d84457c99a
wget-1.14-18.el7_6.1.x86_64.rpm
Source:
cc8cdc081e138d9291e6801891912da67e4274d4d964d1a0f531e247c9d557ae
wget-1.14-18.el7_6.1.src.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 171, Issue 6
***
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
[CentOS-docs] [centos/centos.org] branch master updated: Modified eukhost.com logo
This is an automated email from the git hooks/post-receive script. unknown user pushed a commit to branch master in repository centos/centos.org. The following commit(s) were added to refs/heads/master by this push: new e94df72 Modified eukhost.com logo e94df72 is described below commit e94df7271bffc18e2b3bf6ae09e01886c5a39223 Author: Fabian Arrotin AuthorDate: Wed May 22 13:34:42 2019 +0200 Modified eukhost.com logo Signed-off-by: Fabian Arrotin --- static/images/sponsors/eukhost.png | Bin 5058 -> 15159 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/static/images/sponsors/eukhost.png b/static/images/sponsors/eukhost.png index 16ad80c..e2c70f4 100644 Binary files a/static/images/sponsors/eukhost.png and b/static/images/sponsors/eukhost.png differ -- To stop receiving notification emails like this one, please contact the administrator of this repository. ___ CentOS-docs mailing list CentOS-docs@centos.org https://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-virt] CentOS 7 Xen 4.12 libvirt/virt-manager wrong path for qemu-system-i386
On Sun, May 05, 2019 at 02:23:22PM +0300, Pasi Kärkkäinen wrote:
> Hello,
Thanks for the bug report.
> While testing Virt-SIG Xen 4.12 rpms on CentOS7 I noticed the following
> problem with libvirt/virt-manager when manually installing a new HVM guest
> from virt-manager GUI.. basicly the VM installation won't start, because
> libvirt/virt-manager is not able to start the VM, due to "missing"
> qemu-system-i386 binary:
>
> Unable to complete install: 'unsupported configuration: emulator
> '/usr/lib/xen/bin/qemu-system-i386' not found'
>
> Traceback (most recent call last):
> File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in
> cb_wrapper
> callback(asyncjob, *args, **kwargs)
> File "/usr/share/virt-manager/virtManager/create.py", line 2553, in
> _do_async_install
> guest.start_install(meter=meter)
> File "/usr/share/virt-manager/virtinst/guest.py", line 498, in start_install
> doboot, transient)
> File "/usr/share/virt-manager/virtinst/guest.py", line 434, in _create_guest
> domain = self.conn.createXML(install_xml or final_xml, 0)
> File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3725, in
> createXML
> if ret is None:raise libvirtError('virDomainCreateXML() failed',
> conn=self)
> libvirtError: unsupported configuration: emulator
> '/usr/lib/xen/bin/qemu-system-i386' not found
Starting a guest with libvirt works fine, libvirt is able to find the
qemu binary. (Well, libxl can...)
Here is an osstest flight starting an HVM guest with libvirt:
http://logs.test-lab.xenproject.org/osstest/logs/136701/test-amd64-amd64-libvirt-qemuu-debianhvm-amd64/info.html
Maybe the issue is that I need to rebuild `libvirt-python' and
`virt-manager' packages?
> Quick'n'dirty fix is to create a symlink:
>
> ln -s /usr/lib64/xen/bin/qemu-system-i386
> /usr/lib/xen/bin/qemu-system-i386
>
> .. after creating that symlink the VM can be started just fine and works OK.
>
> We need to fix that default directory path for qemu-system-i386 to be correct
> out-of-the-box..
I can certainly move the binary from "/usr/lib64" to "/usr/lib", and
hope it doesn't break anything, with Xen 4.10 packages the qemu binary
is in /usr/lib64. But to be honest I don't know which is best for CentOS
between "lib64" and "lib".
Thanks,
--
Anthony PERARD
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt
