Re: [CentOS] can't boot after volume rename

2020-01-07 Thread Paul Amaral via CentOS 
I actually renamed it back to the original vg name after I passed Dracut and 
regenerated the initramfa img and it did the trick. I guess it doesn’t like “-“ 
on volume group names. 

 

Thank you, 

 

Paul 

 

From: Paul Amaral  
Sent: Tuesday, January 07, 2020 12:45 PM
To: 'Strahil Nikolov' ; 'centos@centos.org' 

Subject: RE: [CentOS] can't boot after volume rename

 

Strahil, thanks for your reply, I ended up getting the server to boot under 
Dracut only, it’s still not booting from the boot menu. It goes to Dracut where 
it complaints it can’t find any of the lvms. However, when I do lvm vgchange 
-ay it boots upon exit from Dracut. I did notice that the UUIDs from lvm 
lvdisplay and blkid are different. Could this be the cause of the problem? I 
did generate the intiramfs img various times. My volume is named volume-group-1 
and I think having the the “-“ on the name is making things worse.

 

Thank you for your reply. 

Paul  

 

From: Strahil Nikolov mailto:hunter86...@yahoo.com> > 
Sent: Tuesday, January 07, 2020 3:58 AM
To: centos@centos.org  ; Paul Amaral 
mailto:ra...@meganet.net> >
Subject: Re: [CentOS] can't boot after volume rename

 

Get a CentOS Install media , boot from it and select troubleshoot.

Then mount your root LV, boot lv , /proc/, /sys, /dev & /run (last 4 with 
"bind" mount option).

Then chroot into the root LV's mount point and then change grub menu and run 
"dracut -f --regenerate-all"

 

last step is to reboot and test.

 

Best Regards,

Strahil Nikolov

 

В понеделник, 6 януари 2020 г., 17:05:54 ч. Гринуич-5, Paul Amaral via CentOS 
mailto:centos@centos.org> > написа: 

 

 

I renamed my volume with vgrename however I didn't complete the other steps.

Mainly update fstab and intiramfs. Once I booted, I was dropped on the

Dracut shell. From here I can see the newly rename VG and I can lvm lvscan

as well as activate it, lvm vgchange -ay. 

 

 

 

However I can't figure out what to do next, I'm assuming I need to

regenerate the initramfs and then boot to change grub? Could someone point

me in the right direction to recovering a FS from Dracut, or other means,

once the volume group name was changed.

 

 

 

TIA,

 

Paul 

 

___

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] can't boot after volume rename

2020-01-07 Thread Paul Amaral via CentOS 
Strahil, thanks for your reply, I ended up getting the server to boot under 
Dracut only, it’s still not booting from the boot menu. It goes to Dracut where 
it complaints it can’t find any of the lvms. However, when I do lvm vgchange 
-ay it boots upon exit from Dracut. I did notice that the UUIDs from lvm 
lvdisplay and blkid are different. Could this be the cause of the problem? I 
did generate the intiramfs img various times. My volume is named volume-group-1 
and I think having the the “-“ on the name is making things worse.

 

Thank you for your reply. 

Paul  

 

From: Strahil Nikolov  
Sent: Tuesday, January 07, 2020 3:58 AM
To: centos@centos.org; Paul Amaral 
Subject: Re: [CentOS] can't boot after volume rename

 

Get a CentOS Install media , boot from it and select troubleshoot.

Then mount your root LV, boot lv , /proc/, /sys, /dev & /run (last 4 with 
"bind" mount option).

Then chroot into the root LV's mount point and then change grub menu and run 
"dracut -f --regenerate-all"

 

last step is to reboot and test.

 

Best Regards,

Strahil Nikolov

 

В понеделник, 6 януари 2020 г., 17:05:54 ч. Гринуич-5, Paul Amaral via CentOS 
mailto:centos@centos.org> > написа: 

 

 

I renamed my volume with vgrename however I didn't complete the other steps.

Mainly update fstab and intiramfs. Once I booted, I was dropped on the

Dracut shell. From here I can see the newly rename VG and I can lvm lvscan

as well as activate it, lvm vgchange -ay. 

 

 

 

However I can't figure out what to do next, I'm assuming I need to

regenerate the initramfs and then boot to change grub? Could someone point

me in the right direction to recovering a FS from Dracut, or other means,

once the volume group name was changed.

 

 

 

TIA,

 

Paul 

 

___

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] Using shared printers in CentOS 8

2020-01-07 Thread Leon Fauster via CentOS 

Am 07.01.20 um 06:06 schrieb Robert Nichols:

On 1/6/20 10:00 PM, Robert Nichols wrote:

On 1/6/20 7:52 PM, Leon Fauster via CentOS wrote:

Am 06.01.20 um 22:44 schrieb Robert Nichols:
How do I let a CentOS 8 client make use of the shared printers 
advertised by CUPS on the network? In CentOS 6, this was just a 
matter in a checkbox "Show printers shared by other systems" on the 
CUPS Admin page. Is this function still available somehow? Manually 
adding all the shared printers on every client would be painful.




I used:

http://localhost:631/


Yes, that's how I'm getting to the CUPS Admin page, which is lacking 
the option to use printers that the print server is sharing.



Is the print server running CentOS6?


Yes, and other systems make use of its shared printers just fine. It's 
the CentOS 8 CUPS client that doesn't offer to use shared printers.  
Does CUPS 2.x perhaps have some hidden setting to operate as a client 
vs. as a server?  I've never had to configure that before.


OK, I've found a workaround of not bothering with cupsd service locally 
and just putting a ServerName in /etc/cups/client.conf . That means 
there is no local spool to accept jobs if the print server or network is 
down temporarily, but for my use that's acceptable. End of story.




I didn't spent to much time on this but it was necessary to infer the 
printer name on the remote site (well i know it but a ordinary user 
would not).


So to compile the URI check first the remote site via browser:

My spool name is HP_LaserJet (serverside), substitute it.

http://yourprintserver:631/printers/HP_LaserJet

If you get a printer page then your URI for the client is:

ipp://yourprintserver/printers/HP_LaserJet?version=1.1=never

this can be used to configure a local "raw" spool on the client via 
localhost:631 UI ... the key-values version and encryption are necessary 
because CentOS6 cupsd is quite "old".


--
Leon




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

[CentOS-docs] [centos/centos.org] branch master updated (4760934 -> 6239f3c)

2020-01-07 Thread git 
This is an automated email from the git hooks/post-receive script.

rbowen pushed a change to branch master
in repository centos/centos.org.

from 4760934  Removed yourname.nl from sponsors
 add 6239f3c  Update news items

No new revisions were added by this update.

Summary of changes:
 content/index.erb | 26 +-
 1 file changed, 5 insertions(+), 21 deletions(-)

-- 
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] Network Diagnostics

2020-01-07 Thread Stephen John Smoogen 
On Tue, 7 Jan 2020 at 08:22, Chris Olson via CentOS  wrote:
>
> In our smallest office, we have a Dell CentOS 7 system, a
> Windows system and an HP 8610 printer, all hard-wire Ethernet
> connected with a Linksys router. The router provides Internet
> connection. All of the network-connected systems get their
> IP address from the router at power up.
>
> Successful network connection of the printer at power up
> has recently started taking much longer than usual.  The
> display on the front of the printer indicates that it is
> initially attempting wireless connection even though this
> feature is turned off.  Ethernet connection is eventually
> achieved and the printer functions normally on the network
> but just for a few minutes.
>
> After about five minutes, the printer drops its Ethernet
> connection and appears to be attempting wireless connection
> once again.  During this period, network connectivity is
> disrupted for the other systems on the network. They are
> not able to communicate with each other or access the
> Internet through the router.  Turning off the printer
> restores network connection for the other systems.
>
> One of our personnel at another office suggested using
> Wireshark to check out the network when the printer is
> having difficulty.  Wireshark was apparently not on this
> system so we installed it using yum install.  The tail
> end of the apparently successful installation process
> is shown below.  Unfortunately, we cannot seem to find
> Wireshark on the system.
>
> Is it possible that Wireshark was not actually installed
> or do we just not know how to locate and use it?
>
> Is this printer networking issue a known problem and is
> Wireshark the right tool to diagnose the problem?
>
> Thanks.
>
>
> Installed:
>   wireshark.x86_64 0:1.10.14-16.el7
>

The wireshark package by itself only comes with the text tools: tshark
and similar. The wireshark-gnome comes with the wireshark video item

[smooge@xanadu Packages]$ rpm -qlp wireshark-1.10.14-16.el7.x86_64.rpm
 | grep bin
/usr/sbin/capinfos
/usr/sbin/dftest
/usr/sbin/dumpcap
/usr/sbin/editcap
/usr/sbin/mergecap
/usr/sbin/randpkt
/usr/sbin/rawshark
/usr/sbin/reordercap
/usr/sbin/text2pcap
/usr/sbin/tshark
/usr/share/wireshark/radius/dictionary.bintec
[smooge@xanadu Packages]$ rpm -qlp
wireshark-gnome-1.10.14-16.el7.x86_64.rpm  | grep bin
/usr/sbin/wireshark

I will say from the problems in the start of this email that I am not
sure wireshark is going to help show what is wrong. I am expecting
that the printer's network card is broken in some way and is spewing
hardware errors to the network. The linksys switch is a 'dumb' switch
and will go into a hardware reset mode to try and clear it up. I would
try the following:

1. Hardware reset the printer to factory settings and see if it comes
back sane after reset up. If it does not then the problem is a
hardware issue with the printer and either buy a new one or get it
fixed.
2. If the hardware reset works, then I would run whatever Windows
software configures and updates the printer BIOS and drivers to the
newest from HP. Printers are now a vector for cyber-crime infection
and the problems you are describing are also what one sees in a system
which was sort of taken over.



> Dependency Installed:
>   libsmi.x86_64 0:0.4.8-13.el7
>
> Complete!
> [user@computer ~]$
> [user@computer ~]$ which wireshark
> /usr/bin/which: no wireshark in 
> (/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/home/user/.local/bin:/home/user/bin)
> [user@computer ~]$
>
>
> Recent successful installations:
> 
>
> [user@computer ~]$
> [user@computer ~]$ which mplayer
> /usr/bin/mplayer
> [user@computer ~]$ which ffmpeg
> /usr/bin/ffmpeg
> [user@computer ~]$
>
>
> ___
> 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] Network Diagnostics

2020-01-07 Thread Michel van Deventer 
On Tue, 2020-01-07 at 13:21 +, Chris Olson via CentOS wrote:
> 
> One of our personnel at another office suggested using
> Wireshark to check out the network when the printer is
> having difficulty.  Wireshark was apparently not on this
> system so we installed it using yum install.  The tail
> end of the apparently successful installation process
> is shown below.  Unfortunately, we cannot seem to find
> Wireshark on the system.
> 
> Is it possible that Wireshark was not actually installed
> or do we just not know how to locate and use it?
> 
> Is this printer networking issue a known problem and is
> Wireshark the right tool to diagnose the problem?
> 
> Thanks.
> 
> 
> Installed:
>   wireshark.x86_64 0:1.10.14-
> 16.el7 
> 
> Dependency Installed:
>   libsmi.x86_64 0:0.4.8-
> 13.el7   
>
> 
> Complete!
> [user@computer ~]$
> [user@computer ~]$ which wireshark
> /usr/bin/which: no wireshark in
> (/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/home/u
> ser/.local/bin:/home/user/bin)
> [user@computer ~]$ 
> 
the package wireshark does not contain the 'wireshark' binary, you
should use 'tshark' on the commandline.
The 'wireshark' binary is in the wireshark-gnome package and requires a
graphical interface.

tshark takes most of the same parameters as wireshark (if not all)

   Regards,

Michel



--

De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is
uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onterecht
ontvangt, wordt u verzocht de inhoud niet te gebruiken en de afzender direct
te informeren door het bericht te retourneren. Het Universitair Medisch
Centrum Utrecht is een publiekrechtelijke rechtspersoon in de zin van de W.H.W.
(Wet Hoger Onderwijs en Wetenschappelijk Onderzoek) en staat geregistreerd bij
de Kamer van Koophandel voor Midden-Nederland onder nr. 30244197.

Denk s.v.p aan het milieu voor u deze e-mail afdrukt.

--

This message may contain confidential information and is intended exclusively
for the addressee. If you receive this message unintentionally, please do not
use the contents but notify the sender immediately by return e-mail. University
Medical Center Utrecht is a legal person by public law and is registered at
the Chamber of Commerce for Midden-Nederland under no. 30244197.

Please consider the environment before printing this e-mail.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Network Diagnostics

2020-01-07 Thread Chris Olson via CentOS 
In our smallest office, we have a Dell CentOS 7 system, a
Windows system and an HP 8610 printer, all hard-wire Ethernet
connected with a Linksys router. The router provides Internet
connection. All of the network-connected systems get their
IP address from the router at power up.

Successful network connection of the printer at power up
has recently started taking much longer than usual.  The
display on the front of the printer indicates that it is
initially attempting wireless connection even though this
feature is turned off.  Ethernet connection is eventually
achieved and the printer functions normally on the network
but just for a few minutes.

After about five minutes, the printer drops its Ethernet
connection and appears to be attempting wireless connection
once again.  During this period, network connectivity is
disrupted for the other systems on the network. They are
not able to communicate with each other or access the
Internet through the router.  Turning off the printer
restores network connection for the other systems.

One of our personnel at another office suggested using
Wireshark to check out the network when the printer is
having difficulty.  Wireshark was apparently not on this
system so we installed it using yum install.  The tail
end of the apparently successful installation process
is shown below.  Unfortunately, we cannot seem to find
Wireshark on the system.

Is it possible that Wireshark was not actually installed
or do we just not know how to locate and use it?

Is this printer networking issue a known problem and is
Wireshark the right tool to diagnose the problem?

Thanks.


Installed:
  wireshark.x86_64 0:1.10.14-16.el7 
    

Dependency Installed:
  libsmi.x86_64 0:0.4.8-13.el7  
    

Complete!
[user@computer ~]$
[user@computer ~]$ which wireshark
/usr/bin/which: no wireshark in 
(/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/home/user/.local/bin:/home/user/bin)
[user@computer ~]$ 


Recent successful installations:


[user@computer ~]$ 
[user@computer ~]$ which mplayer
/usr/bin/mplayer
[user@computer ~]$ which ffmpeg
/usr/bin/ffmpeg
[user@computer ~]$ 


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

Re: [CentOS] can't boot after volume rename

2020-01-07 Thread Strahil Nikolov via CentOS 
 Get a CentOS Install media , boot from it and select troubleshoot.Then mount 
your root LV, boot lv , /proc/, /sys, /dev & /run (last 4 with "bind" mount 
option).Then chroot into the root LV's mount point and then change grub menu 
and run "dracut -f --regenerate-all"
last step is to reboot and test.
Best Regards,Strahil Nikolov

В понеделник, 6 януари 2020 г., 17:05:54 ч. Гринуич-5, Paul Amaral via 
CentOS  написа:  
 
 I renamed my volume with vgrename however I didn't complete the other steps.
Mainly update fstab and intiramfs. Once I booted, I was dropped on the
Dracut shell. From here I can see the newly rename VG and I can lvm lvscan
as well as activate it, lvm vgchange -ay. 

 

However I can't figure out what to do next, I'm assuming I need to
regenerate the initramfs and then boot to change grub? Could someone point
me in the right direction to recovering a FS from Dracut, or other means,
once the volume group name was changed.

 

TIA,

Paul 

___
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