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
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) wi
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 ser
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
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"
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
- Origin
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 ru
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
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
> __
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, espec
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-ki
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, perhap
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: [Cen
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 y
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 n
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'
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/cent
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
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 fo
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
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:
> 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
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 li
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 sometim
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.
> 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 eac
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
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
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
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
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 on
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
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
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.
34 matches
Mail list logo
