Re: [CentOS] ThinkStation with BIOS RAID and disk error messages in gparted

2020-11-02 Thread H 
On 10/23/2020 10:07 AM, Chris Adams wrote:
> Once upon a time, Simon Matter  said:
>> I'm a bit confused what you have here. Did you mix pseudo hardware RAID
>> (BIOS RAID 0) with software RAID here? Because /dev/md126 clearly is part
>> of a software RAID.
> IIRC the old dmraid support for motherboard RAID has been phased out,
> but mdraid has grown support for Intel (and maybe some other?) common
> motherboard RAID.  So, /dev/md doesn't inherently mean "Linux
> software RAID" for a while now.
Today LibreOffice locked my computer solid and I had to cycle power to start up 
again. Unfortunately it failed booting and I ended up in the dracut shell with 
which I am wholly unfamiliar... Although this could be considered a learning 
experience it is one I could have been without since I was also running a long 
job that had already run for 10 days and needed another four days to complete...

Anyway, after googling and fiddling around I think I identified the culprit as 
the command line in grub menu. I have a ThinkStation where two identical SSDs 
are configured as RAID in BIOS (see above) and the grub command line has two 
rd.md.uuid= statements with the UUIDs of the two disks, further complicated by 
the fact that the disk is encrypted.

After fiddling I discovered that if I removed the rd.md.uuid= statements in the 
grub command line and replaced it with one single rd.md.=0, I could boot. 
However, it seems that only one of the disks is decrypted and used, not the 
second one. I also tried rd.md.auto with the same outcome as with rd.md=0.

I was not able to boot any of the three older kernels, nor the rescue option, 
they all failed for the same reason.

Does anyone have a suggestion on how I can modify the grub boot option so that: 
(1) the system will boot /and/ (2) use the two identical SSDs as the BIOS RAID 
as it did before this happened?
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] LibreOffice locking up

2020-11-02 Thread H 
On 05/25/2020 07:13 PM, H wrote:
> On 05/25/2020 02:15 AM, hw wrote:
>> On Sun, 2020-05-24 at 19:56 -0400, H wrote:
>>> I am running LibreOffice 5.3.6.1 under the latest update of CentOS 7 and
>>> the Mate desktop. Not infrequently LibreOffice Calc locks up and I have
>>> to force close the application. Altough the spreadsheet is rather large I
>>> would not consider it complex.
>>>
>>> This has been going on for some time and I am curious if the bug might be
>>> in LibreOffice or if there is some interaction with the Mate desktop that
>>> might be responsible. Both CentOS, LibreOffice and Mate have been
>>> regularly updated from the standard repositories for a long time.
>>>
>>> Does anyone else have the same problem?
>> Yes, libreoffice sometimes locks up when trying to open a file.  The same
>> problem was there with Debian, and now it's the same with Fedora.
>>
>> I have made a bug report about it, and the response was that there is
>> insufficient information to do anyhing.  Unfortunately, I don't have
>> sufficient information I could give because it just happens sometimes to
>> users who have been so far unable to tell me if particular types of files
>> are affected or if there are any discerninable circumstances that could
>> help to figure this out.
>>
>> Here's the bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1809771
>>
>>
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
> For some reason I could not enter a new bug for LibreOffice since the package 
> is missing from the the list of Fedora apps. I thus added information to your 
> bug report above.
>
> I encourage other users encountering similar bugs in LO to add information.
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
LibreOffice locked my CentOS 7 hard today, I could not close the application, 
nor could I reboot the computer by any other mean than turning the computer off 
and then on again. The lockup happened while loading one of my spreadsheets.

First, I do not understand why a wayward application can lock my computer so 
hard that I have to cycle power.

Second, I cannot understand why this bug is not fixed. LibreOffice is obviously 
one of the key applications users will run. It should not be that hard to put 
out a debug version that those of us who have this problem - at least once a 
week in my case - that a debug log could help the developers fix this serious 
bug.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Odd issue happening CentOS 7

2020-11-02 Thread Jerry Geis 
Hi All - Your correct... There was a typo in the address -  Can I plame
that on a super small screen...
Thanks

Jerry
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Odd issue happening CentOS 7

2020-11-02 Thread Bernstein, Noam CIV USN NRL (6393) Washington DC (USA) via CentOS 
On Nov 2, 2020, at 12:51 PM, Patrick Bégou 
mailto:patrick.be...@legi.grenoble-inp.fr>> 
wrote:

Did you notice the address ? It is not the same IP.

Right - this doesn't look like a web server issue, if the quoted text has no 
typos. the real question is why doing "host" on the name returns 192.168.1.8 
but doing "curl -v" with the name appears to return 198.168.1.8 (note 198, not 
192, for the first of the dotted quad) (according to the text below).

Also, I'm not sure that a FQDN in the .com domain should ever resolve to a 
non-routable address (192,168.x.x).  It's at least weird.


Patrick

Le 02/11/2020 à 17:48, Jerry Geis a écrit :
So I have two CentOS 7 machines running.

if I am on my server and I do "curl  http://192.168.1.8"; I get data.
If I do "host 
devgeis.LayeredSolutionsInc.com" I get 
the correct address
192.168.1.8

if I goto another machine with CentOS 7.
I do "curl http://192.168.1.8"; I get data.
I do "host 
devgeis.LayeredSolutionsInc.com" I get 
the correct address
*192.*168.1.8

BUT then I do "curl http://devgeis.LayeredSolutionsinc.com"; I get "nothing"
BUt then doing the -v with "curl -v http://devgeis.LayeredSolutionsinc.com";
* About to connect() to 
devgeis.LayeredSolutionsinc.com port 80 
(#0)
*  *Trying 198.*168.1.8...


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Odd issue happening CentOS 7

2020-11-02 Thread Patrick Bégou 
Did you notice the address ? It is not the same IP.

Patrick

Le 02/11/2020 à 17:48, Jerry Geis a écrit :
> So I have two CentOS 7 machines running.
>
> if I am on my server and I do "curl  http://192.168.1.8"; I get data.
> If I do "host devgeis.LayeredSolutionsInc.com" I get the correct address
> 192.168.1.8
>
> if I goto another machine with CentOS 7.
> I do "curl http://192.168.1.8"; I get data.
> I do "host devgeis.LayeredSolutionsInc.com" I get the correct address
> *192.*168.1.8
>
> BUT then I do "curl http://devgeis.LayeredSolutionsinc.com"; I get "nothing"
> BUt then doing the -v with "curl -v http://devgeis.LayeredSolutionsinc.com";
> * About to connect() to devgeis.LayeredSolutionsinc.com port 80 (#0)
> *  *Trying 198.*168.1.8...
>
> So why when using the name is it not giving me the index.html page ?
>
> Should not be a firewall issue - as the actual address worked. Also I tried
> stopping the firewall - and all the above is the exact same.
>
> What is possibly happening here ?
>
> Thanks
>
> Jerry
> ___
> 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] Odd issue happening CentOS 7

2020-11-02 Thread Simon Matter 
> So I have two CentOS 7 machines running.
>
> if I am on my server and I do "curl  http://192.168.1.8"; I get data.
> If I do "host devgeis.LayeredSolutionsInc.com" I get the correct address
> 192.168.1.8
>
> if I goto another machine with CentOS 7.
> I do "curl http://192.168.1.8"; I get data.
> I do "host devgeis.LayeredSolutionsInc.com" I get the correct address
> 192.168.1.8
>
> BUT then I do "curl http://devgeis.LayeredSolutionsinc.com"; I get
> "nothing"
> BUt then doing the -v with "curl -v
> http://devgeis.LayeredSolutionsinc.com";
> * About to connect() to devgeis.LayeredSolutionsinc.com port 80 (#0)
> *   Trying 198.168.1.8...
>
> So why when using the name is it not giving me the index.html page ?

I guess you have an apache listening on 192.168.1.8:80? What do the apache
logs say? Does your apache know that he's responsible for
devgeis.LayeredSolutionsInc.com?

Regards,
Simon

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Odd issue happening CentOS 7

2020-11-02 Thread Jerry Geis 
So I have two CentOS 7 machines running.

if I am on my server and I do "curl  http://192.168.1.8"; I get data.
If I do "host devgeis.LayeredSolutionsInc.com" I get the correct address
192.168.1.8

if I goto another machine with CentOS 7.
I do "curl http://192.168.1.8"; I get data.
I do "host devgeis.LayeredSolutionsInc.com" I get the correct address
192.168.1.8

BUT then I do "curl http://devgeis.LayeredSolutionsinc.com"; I get "nothing"
BUt then doing the -v with "curl -v http://devgeis.LayeredSolutionsinc.com";
* About to connect() to devgeis.LayeredSolutionsinc.com port 80 (#0)
*   Trying 198.168.1.8...

So why when using the name is it not giving me the index.html page ?

Should not be a firewall issue - as the actual address worked. Also I tried
stopping the firewall - and all the above is the exact same.

What is possibly happening here ?

Thanks

Jerry
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cuentos live cd

2020-11-02 Thread Johnny Hughes 
On 10/23/20 4:50 PM, Leonardo Cuyar Morales wrote:
> Hi list, sorry about my autocomplete. I asked about any documentation on
> build a centos livecd with my custome utities and applications.
> 
> On Saturday, October 17, 2020, Leonardo Cuyar Morales 
> wrote:
>> If there any guide / howto yo Bulls a vernos live cd?
>>
>> --
>> Imagination is more important than knowledge
>>
> 

If you do a git checkout of this repo:

https://git.centos.org/centos/livemedia

The go to the kickstarts directory .. there are example kickstarts I use
to create live isos

You need to modify a kickstart to install the packages you want .. then
run this command to create the iso:

sudo livecd-creator --config= --fslabel=

You need the livecd-creator from epel.

(For CentOS 7 or 6)



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos