[CentOS] ClamAV installation is OUTDATED! as reported by freshclam utility on CentOS Linux release 7.6.1810 (Core)

[Kaushal Shriyan]

Hi,

I am running CentOS Linux release 7.6.1810 (Core) with ClamAV installed.
When i am running freshclam i am seeing a Warning message and the details
are described below:-

# freshclam
ClamAV update process started at Thu Dec 13 11:49:18 2018
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.100.2 Recommended version: 0.101.0
DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder:
sigmgr)
nonblock_recv: recv timing out (30 secs)
WARNING: getfile: Download interrupted: Operation now in progress (IP:
104.16.189.138)
WARNING: Can't download daily.cvd from database.clamav.net
Trying again in 5 secs...
ClamAV update process started at Thu Dec 13 11:49:56 2018
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.100.2 Recommended version: 0.101.0
DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder:
sigmgr)
Trying host database.clamav.net (104.16.188.138)...
Downloading daily.cvd [100%]
daily.cvd updated (version: 25202, sigs: 2176766, f-level: 63, builder: neo)
bytecode.cvd is up to date (version: 327, sigs: 91, f-level: 63, builder:
neo)
Database updated (6743106 signatures) from database.clamav.net (IP:
104.16.188.138)
#

*OS Version*
# cat /etc/redhat-release
CentOS Linux release 7.6.1810 (Core)
# yum update
No packages marked for update
#

*EPEL Version*
# rpm -qa | grep epel
epel-release-7-11.noarch
#

*ClamAV Version*
# rpm -qa | grep clamav
clamav-lib-0.100.2-2.el7.x86_64
clamav-filesystem-0.100.2-2.el7.noarch
clamav-update-0.100.2-2.el7.x86_64
clamav-0.100.2-2.el7.x86_64
#

Please comment. Thanks in Advance. I look forward to hearing from you.

Best Regards,

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

Re: [CentOS] Running a command at startup

[Robert Moskowitz]

On 12/12/18 9:17 PM, Richard wrote:



Date: Wednesday, December 12, 2018 20:25:48 -0500
From: Robert Moskowitz 


On 12/12/18 7:11 PM, Leroy Tennison wrote:

Does your version of CentOS have the @reboot crontab option?  If
it does this is probably easier unless you want to learn how to
write systemd files.

CentOS 7.6.  I will have to google @reboot...


see: man -S5 crontab  -- the "extensions" section.



OK

I have had problems in the past with crontab parsing a command. Would I use:

@reboot root echo none | tee /sys/class/leds/blue\:heartbeat/trigger

?

Or do I have to make a script and run that?

thanks

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

Re: [CentOS] Running a command at startup

[Richard]

> Date: Wednesday, December 12, 2018 20:25:48 -0500
> From: Robert Moskowitz 
> 
> 
> On 12/12/18 7:11 PM, Leroy Tennison wrote:
>> Does your version of CentOS have the @reboot crontab option?  If
>> it does this is probably easier unless you want to learn how to
>> write systemd files.
> 
> CentOS 7.6.  I will have to google @reboot...


see: man -S5 crontab  -- the "extensions" section.


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

Re: [CentOS-docs] would you please approve KenDreyer to edit SIGGuide/* ?

[Ken Dreyer]

Whoops, thanks Akemi.

I mis-interpreted the message at
https://lists.centos.org/pipermail/centos-docs/2018-November/006312.html
to mean that my account was restricted to Storage/*

- Ken
On Wed, Dec 12, 2018 at 6:32 PM Akemi Yagi  wrote:
>
> On Wed, Dec 12, 2018 at 5:24 PM Ken Dreyer  wrote:
> >
> > Hi wiki admins,
> >
> > I would like to edit the content here:
> >
> > https://wiki.centos.org/SIGGuide/Content/BuildLogs
> > https://wiki.centos.org/SIGGuide/Content/Mirror
> >
> > Proposed edits:
> >
> > 1) The pages are really similar. At a glance, it's not clear whether
> > I'm viewing one or the other. Let's add text to clearly distinguish
> > them for newcomers.
> >
> > 2) The pages do not link back to each other, and they should, because
> > SIG members need to know how to distribute both test content
> > (buildlogs) and GA content (mirror).
> >
> > - Ken
>
> You should be able to edit any of the wiki pages. Please let us know
> should you find any issue.
>
> Akemi
> ___
> 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] would you please approve KenDreyer to edit SIGGuide/* ?

[Akemi Yagi]

On Wed, Dec 12, 2018 at 5:24 PM Ken Dreyer  wrote:
>
> Hi wiki admins,
>
> I would like to edit the content here:
>
> https://wiki.centos.org/SIGGuide/Content/BuildLogs
> https://wiki.centos.org/SIGGuide/Content/Mirror
>
> Proposed edits:
>
> 1) The pages are really similar. At a glance, it's not clear whether
> I'm viewing one or the other. Let's add text to clearly distinguish
> them for newcomers.
>
> 2) The pages do not link back to each other, and they should, because
> SIG members need to know how to distribute both test content
> (buildlogs) and GA content (mirror).
>
> - Ken

You should be able to edit any of the wiki pages. Please let us know
should you find any issue.

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

Re: [CentOS] Running a command at startup

[RC]

if it's Centos/RHEL 7,  you can turn it into a service that starts after 
boot too,  and cintrol it with systemctl.


On 12/12/18 5:04 PM, Robert Moskowitz wrote:

On a support forum, I was told that to turn off my board's blue led run:

echo none | sudo tee /sys/class/leds/blue\:heartbeat/trigger

Well, this does not survive a system reboot.  So I was told:

Add the off bit to

    /etc/rc.local

Add it above "exit 0"

So of course, CentOS is past using rc.local and recommends:

# It is highly advisable to create own systemd services or udev rules
# to run scripts during boot instead of using this fi

So can someone point me to how to make this into a simple systemd 
service?


thanks


___
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] Running a command at startup

[Robert Moskowitz]

On 12/12/18 7:11 PM, Leroy Tennison wrote:

Does your version of CentOS have the @reboot crontab option?  If it does this 
is probably easier unless you want to learn how to write systemd files.


CentOS 7.6.  I will have to google @reboot...




Leroy Tennison
Network Information/Cyber Security Specialist
E: le...@datavoiceint.com
2220 Bush Dr
McKinney, Texas
75070
www.datavoiceint.com
TThis message has been sent on behalf
of a company that is part of the Harris Operating Group of
Constellation Software Inc. These companies are listed
here
.
If you prefer not to be contacted by Harris
Operating Group
please notify us
.
This message is intended exclusively for the
individual or entity to which it is addressed. This communication
may contain information that is proprietary, privileged or
confidential or otherwise legally exempt from disclosure. If you are
not the named addressee, you are not authorized to read, print,
retain, copy or disseminate this message or any part of it. If you
have received this message in error, please notify the sender
immediately by e-mail and delete all copies of the
message.


From: CentOS  on behalf of Robert Moskowitz 

Sent: Wednesday, December 12, 2018 6:04 PM
To: CentOS mailing list
Subject: [EXTERNAL] [CentOS] Running a command at startup

On a support forum, I was told that to turn off my board's blue led run:

echo none | sudo tee /sys/class/leds/blue\:heartbeat/trigger

Well, this does not survive a system reboot.  So I was told:

Add the off bit to

  /etc/rc.local

Add it above "exit 0"

So of course, CentOS is past using rc.local and recommends:

# It is highly advisable to create own systemd services or udev rules
# to run scripts during boot instead of using this fi

So can someone point me to how to make this into a simple systemd service?

thanks


___
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



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

[CentOS-docs] would you please approve KenDreyer to edit SIGGuide/* ?

[Ken Dreyer]

Hi wiki admins,

I would like to edit the content here:

https://wiki.centos.org/SIGGuide/Content/BuildLogs
https://wiki.centos.org/SIGGuide/Content/Mirror

Proposed edits:

1) The pages are really similar. At a glance, it's not clear whether
I'm viewing one or the other. Let's add text to clearly distinguish
them for newcomers.

2) The pages do not link back to each other, and they should, because
SIG members need to know how to distribute both test content
(buildlogs) and GA content (mirror).

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

[CentOS] Running a command at startup

[Leroy Tennison]

Does your version of CentOS have the @reboot crontab option?  If it does this 
is probably easier unless you want to learn how to write systemd files.


Leroy Tennison
Network Information/Cyber Security Specialist
E: le...@datavoiceint.com
2220 Bush Dr
McKinney, Texas
75070
www.datavoiceint.com
TThis message has been sent on behalf
of a company that is part of the Harris Operating Group of
Constellation Software Inc. These companies are listed
here
.
If you prefer not to be contacted by Harris
Operating Group
please notify us
.
This message is intended exclusively for the
individual or entity to which it is addressed. This communication
may contain information that is proprietary, privileged or
confidential or otherwise legally exempt from disclosure. If you are
not the named addressee, you are not authorized to read, print,
retain, copy or disseminate this message or any part of it. If you
have received this message in error, please notify the sender
immediately by e-mail and delete all copies of the
message.


From: CentOS  on behalf of Robert Moskowitz 

Sent: Wednesday, December 12, 2018 6:04 PM
To: CentOS mailing list
Subject: [EXTERNAL] [CentOS] Running a command at startup

On a support forum, I was told that to turn off my board's blue led run:

echo none | sudo tee /sys/class/leds/blue\:heartbeat/trigger

Well, this does not survive a system reboot.  So I was told:

Add the off bit to

 /etc/rc.local

Add it above "exit 0"

So of course, CentOS is past using rc.local and recommends:

# It is highly advisable to create own systemd services or udev rules
# to run scripts during boot instead of using this fi

So can someone point me to how to make this into a simple systemd service?

thanks


___
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

[CentOS] Running a command at startup

[Robert Moskowitz]

On a support forum, I was told that to turn off my board's blue led run:

echo none | sudo tee /sys/class/leds/blue\:heartbeat/trigger

Well, this does not survive a system reboot.  So I was told:

Add the off bit to

    /etc/rc.local

Add it above "exit 0"

So of course, CentOS is past using rc.local and recommends:

# It is highly advisable to create own systemd services or udev rules
# to run scripts during boot instead of using this fi

So can someone point me to how to make this into a simple systemd service?

thanks


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

Re: [CentOS] SFTP - Private/Public Authentication Keysets Beyond The First Set

[Gary Braatz]

Inclusion of the -i flag and the location of the private key solved the
problem.

Thanks Steve!

-Original Message-
From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Steve Clark
Sent: Wednesday, December 12, 2018 2:38 PM
To: CentOS mailing list
Subject: Re: [CentOS] SFTP - Private/Public Authentication Keysets Beyond
The First Set

On 12/12/2018 03:32 PM, Steve Clark wrote:
> On 12/12/2018 03:28 PM, Gary Braatz wrote:
>> Thanks for responding so quickly!  No but I will try.  Are you saying the
>> first vendor connection worked because id_rsa and id_rsa.pub are the
>> defaults if not specified?  (I didn't use the -i flag for the first
vendor.)
>>
>>
>> -Original Message-
>> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Steve Clark
>> Sent: Wednesday, December 12, 2018 2:23 PM
>> To: CentOS mailing list
>> Subject: Re: [CentOS] SFTP - Private/Public Authentication Keysets Beyond
>> The First Set
>>
>> On 12/12/2018 03:13 PM, Gary Braatz wrote:
>>> I'm new to SFTP and using this mailing list was able to successfully
>> create
>>> my first Private/Public keyset for a vendor hosting the SFTP server (I'm
>> the
>>> client).  I created the keyset by typing this:
>>>
>>>  
>>>
>>> # ssh-keygen -t rsa
>>>
>>>  
>>>
>>> When asked for the password/passphrase I hit  and afterwards
>> "id_rsa"
>>> and "id_rsa.pub" were created in "/root/.ssh/".  I provided "id_rsa.pub"
>> to
>>> the vendor and when told they were ready I initiated an SFTP transfer.
>>> During the first connection I was asked for the vendor-provided password
>> and
>>> after entering it was successfully connected to the vendor's sftp
server.
>>> During successive connections I was not again asked for the password.
>> This
>>> allowed me to create fully automated batch file transfers.my objective.
>>> Setting up my second vendor is not going as smoothly.
>>>
>>>  
>>>
>>> I did exactly the same thing for my second vendor with the exception of
>>> typing "rsa_vendor2" during keyset generation (I assumed I had to use a
>>> different name for the new keyset).
>>>
>>>  
>>>
>>> # ssh-keygen -t rsa_vendor2
>>>
>>>  
>>>
>>> Files "id_rsa_vendor2" and "id_rsa_vendor2.pub" were created in
>>> "/root/.ssh/" and I gave "id_rsa_vendor2.pub" to the second vendor.  I
>>> initiated the first connection with the second vendor and was asked for
>> the
>>> vendor-provided password which I entered and a successful connection was
>>> made.  The problem is unlike with the first vendor I am asked for the
>>> password every time I connect to the second vendor's server.  Because I
am
>>> being asked for the password I am unable to create fully automated batch
>>> file transfers.
>>>
>>>  
>>>
>>> The second vendor is telling me they added the public key to their
server
>> as
>>> required.  Did I miss a step or do something wrong on my end?  Was I
>> correct
>>> using a different name for the new keyset or would the new keyset
>>> information have been appended to the information already in id_rsa and
>>> id_rsa.pub for the first vendor?
>>>
>>>  
>>>
>>> Any help you can provide will be greatly appreciated.
>>>
>>>  
>>>
>>> ___
>>> CentOS mailing list
>>> CentOS@centos.org
>>> https://lists.centos.org/mailman/listinfo/centos
>>>
>> Are using the -i flag in your invocation of sftp to the second vendor?
>> >From the sftp man page:
>>
>>  -i identity_file
>>  Selects the file from which the identity (private key) for
>> public key authentication is read.  This option
>>  is directly passed to ssh(1).
>>
> In my experience - Yes.
>
To expand on my response - generally there is system wide default ssh_config
file in
/etc/ssh/ssh_config

and by default:
#   IdentityFile ~/.ssh/identity
#   IdentityFile ~/.ssh/id_rsa
#   IdentityFile ~/.ssh/id_dsa


-- 
Stephen Clark
*NetWolves Managed Services, LLC.*
Sr. Applications Architect 
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.cl...@netwolves.com
http://www.netwolves.com
___
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] SFTP - Private/Public Authentication Keysets Beyond The First Set

[Gary Braatz]

Thank You Sir!  The vendor is working on this as well and I believe may have
just changed the password.  The one I was using is no longer working (it
worked a few minutes ago).  I'll update you later on my progress.


-Original Message-
From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Steve Clark
Sent: Wednesday, December 12, 2018 2:38 PM
To: CentOS mailing list
Subject: Re: [CentOS] SFTP - Private/Public Authentication Keysets Beyond
The First Set

On 12/12/2018 03:32 PM, Steve Clark wrote:
> On 12/12/2018 03:28 PM, Gary Braatz wrote:
>> Thanks for responding so quickly!  No but I will try.  Are you saying the
>> first vendor connection worked because id_rsa and id_rsa.pub are the
>> defaults if not specified?  (I didn't use the -i flag for the first
vendor.)
>>
>>
>> -Original Message-
>> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Steve Clark
>> Sent: Wednesday, December 12, 2018 2:23 PM
>> To: CentOS mailing list
>> Subject: Re: [CentOS] SFTP - Private/Public Authentication Keysets Beyond
>> The First Set
>>
>> On 12/12/2018 03:13 PM, Gary Braatz wrote:
>>> I'm new to SFTP and using this mailing list was able to successfully
>> create
>>> my first Private/Public keyset for a vendor hosting the SFTP server (I'm
>> the
>>> client).  I created the keyset by typing this:
>>>
>>>  
>>>
>>> # ssh-keygen -t rsa
>>>
>>>  
>>>
>>> When asked for the password/passphrase I hit  and afterwards
>> "id_rsa"
>>> and "id_rsa.pub" were created in "/root/.ssh/".  I provided "id_rsa.pub"
>> to
>>> the vendor and when told they were ready I initiated an SFTP transfer.
>>> During the first connection I was asked for the vendor-provided password
>> and
>>> after entering it was successfully connected to the vendor's sftp
server.
>>> During successive connections I was not again asked for the password.
>> This
>>> allowed me to create fully automated batch file transfers.my objective.
>>> Setting up my second vendor is not going as smoothly.
>>>
>>>  
>>>
>>> I did exactly the same thing for my second vendor with the exception of
>>> typing "rsa_vendor2" during keyset generation (I assumed I had to use a
>>> different name for the new keyset).
>>>
>>>  
>>>
>>> # ssh-keygen -t rsa_vendor2
>>>
>>>  
>>>
>>> Files "id_rsa_vendor2" and "id_rsa_vendor2.pub" were created in
>>> "/root/.ssh/" and I gave "id_rsa_vendor2.pub" to the second vendor.  I
>>> initiated the first connection with the second vendor and was asked for
>> the
>>> vendor-provided password which I entered and a successful connection was
>>> made.  The problem is unlike with the first vendor I am asked for the
>>> password every time I connect to the second vendor's server.  Because I
am
>>> being asked for the password I am unable to create fully automated batch
>>> file transfers.
>>>
>>>  
>>>
>>> The second vendor is telling me they added the public key to their
server
>> as
>>> required.  Did I miss a step or do something wrong on my end?  Was I
>> correct
>>> using a different name for the new keyset or would the new keyset
>>> information have been appended to the information already in id_rsa and
>>> id_rsa.pub for the first vendor?
>>>
>>>  
>>>
>>> Any help you can provide will be greatly appreciated.
>>>
>>>  
>>>
>>> ___
>>> CentOS mailing list
>>> CentOS@centos.org
>>> https://lists.centos.org/mailman/listinfo/centos
>>>
>> Are using the -i flag in your invocation of sftp to the second vendor?
>> >From the sftp man page:
>>
>>  -i identity_file
>>  Selects the file from which the identity (private key) for
>> public key authentication is read.  This option
>>  is directly passed to ssh(1).
>>
> In my experience - Yes.
>
To expand on my response - generally there is system wide default ssh_config
file in
/etc/ssh/ssh_config

and by default:
#   IdentityFile ~/.ssh/identity
#   IdentityFile ~/.ssh/id_rsa
#   IdentityFile ~/.ssh/id_dsa


-- 
Stephen Clark
*NetWolves Managed Services, LLC.*
Sr. Applications Architect 
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.cl...@netwolves.com
http://www.netwolves.com
___
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] SFTP - Private/Public Authentication Keysets Beyond The First Set

[Steve Clark]

On 12/12/2018 03:32 PM, Steve Clark wrote:
> On 12/12/2018 03:28 PM, Gary Braatz wrote:
>> Thanks for responding so quickly!  No but I will try.  Are you saying the
>> first vendor connection worked because id_rsa and id_rsa.pub are the
>> defaults if not specified?  (I didn't use the -i flag for the first vendor.)
>>
>>
>> -Original Message-
>> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Steve Clark
>> Sent: Wednesday, December 12, 2018 2:23 PM
>> To: CentOS mailing list
>> Subject: Re: [CentOS] SFTP - Private/Public Authentication Keysets Beyond
>> The First Set
>>
>> On 12/12/2018 03:13 PM, Gary Braatz wrote:
>>> I'm new to SFTP and using this mailing list was able to successfully
>> create
>>> my first Private/Public keyset for a vendor hosting the SFTP server (I'm
>> the
>>> client).  I created the keyset by typing this:
>>>
>>>  
>>>
>>> # ssh-keygen -t rsa
>>>
>>>  
>>>
>>> When asked for the password/passphrase I hit  and afterwards
>> "id_rsa"
>>> and "id_rsa.pub" were created in "/root/.ssh/".  I provided "id_rsa.pub"
>> to
>>> the vendor and when told they were ready I initiated an SFTP transfer.
>>> During the first connection I was asked for the vendor-provided password
>> and
>>> after entering it was successfully connected to the vendor's sftp server.
>>> During successive connections I was not again asked for the password.
>> This
>>> allowed me to create fully automated batch file transfers.my objective.
>>> Setting up my second vendor is not going as smoothly.
>>>
>>>  
>>>
>>> I did exactly the same thing for my second vendor with the exception of
>>> typing "rsa_vendor2" during keyset generation (I assumed I had to use a
>>> different name for the new keyset).
>>>
>>>  
>>>
>>> # ssh-keygen -t rsa_vendor2
>>>
>>>  
>>>
>>> Files "id_rsa_vendor2" and "id_rsa_vendor2.pub" were created in
>>> "/root/.ssh/" and I gave "id_rsa_vendor2.pub" to the second vendor.  I
>>> initiated the first connection with the second vendor and was asked for
>> the
>>> vendor-provided password which I entered and a successful connection was
>>> made.  The problem is unlike with the first vendor I am asked for the
>>> password every time I connect to the second vendor's server.  Because I am
>>> being asked for the password I am unable to create fully automated batch
>>> file transfers.
>>>
>>>  
>>>
>>> The second vendor is telling me they added the public key to their server
>> as
>>> required.  Did I miss a step or do something wrong on my end?  Was I
>> correct
>>> using a different name for the new keyset or would the new keyset
>>> information have been appended to the information already in id_rsa and
>>> id_rsa.pub for the first vendor?
>>>
>>>  
>>>
>>> Any help you can provide will be greatly appreciated.
>>>
>>>  
>>>
>>> ___
>>> CentOS mailing list
>>> CentOS@centos.org
>>> https://lists.centos.org/mailman/listinfo/centos
>>>
>> Are using the -i flag in your invocation of sftp to the second vendor?
>> >From the sftp man page:
>>
>>  -i identity_file
>>  Selects the file from which the identity (private key) for
>> public key authentication is read.  This option
>>  is directly passed to ssh(1).
>>
> In my experience - Yes.
>
To expand on my response - generally there is system wide default ssh_config 
file in
/etc/ssh/ssh_config

and by default:
#   IdentityFile ~/.ssh/identity
#   IdentityFile ~/.ssh/id_rsa
#   IdentityFile ~/.ssh/id_dsa


-- 
Stephen Clark
*NetWolves Managed Services, LLC.*
Sr. Applications Architect 
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.cl...@netwolves.com
http://www.netwolves.com
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] SFTP - Private/Public Authentication Keysets Beyond The First Set

[Steve Clark]

On 12/12/2018 03:28 PM, Gary Braatz wrote:
> Thanks for responding so quickly!  No but I will try.  Are you saying the
> first vendor connection worked because id_rsa and id_rsa.pub are the
> defaults if not specified?  (I didn't use the -i flag for the first vendor.)
>
>
> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Steve Clark
> Sent: Wednesday, December 12, 2018 2:23 PM
> To: CentOS mailing list
> Subject: Re: [CentOS] SFTP - Private/Public Authentication Keysets Beyond
> The First Set
>
> On 12/12/2018 03:13 PM, Gary Braatz wrote:
>> I'm new to SFTP and using this mailing list was able to successfully
> create
>> my first Private/Public keyset for a vendor hosting the SFTP server (I'm
> the
>> client).  I created the keyset by typing this:
>>
>>  
>>
>> # ssh-keygen -t rsa
>>
>>  
>>
>> When asked for the password/passphrase I hit  and afterwards
> "id_rsa"
>> and "id_rsa.pub" were created in "/root/.ssh/".  I provided "id_rsa.pub"
> to
>> the vendor and when told they were ready I initiated an SFTP transfer.
>> During the first connection I was asked for the vendor-provided password
> and
>> after entering it was successfully connected to the vendor's sftp server.
>> During successive connections I was not again asked for the password.
> This
>> allowed me to create fully automated batch file transfers.my objective.
>> Setting up my second vendor is not going as smoothly.
>>
>>  
>>
>> I did exactly the same thing for my second vendor with the exception of
>> typing "rsa_vendor2" during keyset generation (I assumed I had to use a
>> different name for the new keyset).
>>
>>  
>>
>> # ssh-keygen -t rsa_vendor2
>>
>>  
>>
>> Files "id_rsa_vendor2" and "id_rsa_vendor2.pub" were created in
>> "/root/.ssh/" and I gave "id_rsa_vendor2.pub" to the second vendor.  I
>> initiated the first connection with the second vendor and was asked for
> the
>> vendor-provided password which I entered and a successful connection was
>> made.  The problem is unlike with the first vendor I am asked for the
>> password every time I connect to the second vendor's server.  Because I am
>> being asked for the password I am unable to create fully automated batch
>> file transfers.
>>
>>  
>>
>> The second vendor is telling me they added the public key to their server
> as
>> required.  Did I miss a step or do something wrong on my end?  Was I
> correct
>> using a different name for the new keyset or would the new keyset
>> information have been appended to the information already in id_rsa and
>> id_rsa.pub for the first vendor?
>>
>>  
>>
>> Any help you can provide will be greatly appreciated.
>>
>>  
>>
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>>
> Are using the -i flag in your invocation of sftp to the second vendor?
> >From the sftp man page:
>
>  -i identity_file
>  Selects the file from which the identity (private key) for
> public key authentication is read.  This option
>  is directly passed to ssh(1).
>
In my experience - Yes.

-- 
Stephen Clark
*NetWolves Managed Services, LLC.*
Sr. Applications Architect 
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.cl...@netwolves.com
http://www.netwolves.com
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-docs] Cannot Delete my Name

[Alan Bartlett]

On Wed, 12 Dec 2018 at 19:37, G.S.  wrote:
>
> Hello guys, Please help.
>
> My name and surname are shown here: https://wiki.centos.org/GavriilSpiropoulos
>
> I may have some issues because of that. Could you please change my name to 
> something random or delete my account completely?
>
>
> --
> Best Regards,
> Gabriel

The above referenced page has now been deleted.

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

Re: [CentOS] SFTP - Private/Public Authentication Keysets Beyond The First Set

[Gary Braatz]

Thanks for responding so quickly!  No but I will try.  Are you saying the
first vendor connection worked because id_rsa and id_rsa.pub are the
defaults if not specified?  (I didn't use the -i flag for the first vendor.)


-Original Message-
From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Steve Clark
Sent: Wednesday, December 12, 2018 2:23 PM
To: CentOS mailing list
Subject: Re: [CentOS] SFTP - Private/Public Authentication Keysets Beyond
The First Set

On 12/12/2018 03:13 PM, Gary Braatz wrote:
> I'm new to SFTP and using this mailing list was able to successfully
create
> my first Private/Public keyset for a vendor hosting the SFTP server (I'm
the
> client).  I created the keyset by typing this:
>
>  
>
> # ssh-keygen -t rsa
>
>  
>
> When asked for the password/passphrase I hit  and afterwards
"id_rsa"
> and "id_rsa.pub" were created in "/root/.ssh/".  I provided "id_rsa.pub"
to
> the vendor and when told they were ready I initiated an SFTP transfer.
> During the first connection I was asked for the vendor-provided password
and
> after entering it was successfully connected to the vendor's sftp server.
> During successive connections I was not again asked for the password.
This
> allowed me to create fully automated batch file transfers.my objective.
> Setting up my second vendor is not going as smoothly.
>
>  
>
> I did exactly the same thing for my second vendor with the exception of
> typing "rsa_vendor2" during keyset generation (I assumed I had to use a
> different name for the new keyset).
>
>  
>
> # ssh-keygen -t rsa_vendor2
>
>  
>
> Files "id_rsa_vendor2" and "id_rsa_vendor2.pub" were created in
> "/root/.ssh/" and I gave "id_rsa_vendor2.pub" to the second vendor.  I
> initiated the first connection with the second vendor and was asked for
the
> vendor-provided password which I entered and a successful connection was
> made.  The problem is unlike with the first vendor I am asked for the
> password every time I connect to the second vendor's server.  Because I am
> being asked for the password I am unable to create fully automated batch
> file transfers.
>
>  
>
> The second vendor is telling me they added the public key to their server
as
> required.  Did I miss a step or do something wrong on my end?  Was I
correct
> using a different name for the new keyset or would the new keyset
> information have been appended to the information already in id_rsa and
> id_rsa.pub for the first vendor?
>
>  
>
> Any help you can provide will be greatly appreciated.
>
>  
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
Are using the -i flag in your invocation of sftp to the second vendor?
>From the sftp man page:

 -i identity_file
 Selects the file from which the identity (private key) for
public key authentication is read.  This option
 is directly passed to ssh(1).

-- 
Stephen Clark
*NetWolves Managed Services, LLC.*
Sr. Applications Architect 
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.cl...@netwolves.com
http://www.netwolves.com
___
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] SFTP - Private/Public Authentication Keysets Beyond The First Set

[Steve Clark]

On 12/12/2018 03:13 PM, Gary Braatz wrote:
> I'm new to SFTP and using this mailing list was able to successfully create
> my first Private/Public keyset for a vendor hosting the SFTP server (I'm the
> client).  I created the keyset by typing this:
>
>  
>
> # ssh-keygen -t rsa
>
>  
>
> When asked for the password/passphrase I hit  and afterwards "id_rsa"
> and "id_rsa.pub" were created in "/root/.ssh/".  I provided "id_rsa.pub" to
> the vendor and when told they were ready I initiated an SFTP transfer.
> During the first connection I was asked for the vendor-provided password and
> after entering it was successfully connected to the vendor's sftp server.
> During successive connections I was not again asked for the password.  This
> allowed me to create fully automated batch file transfers.my objective.
> Setting up my second vendor is not going as smoothly.
>
>  
>
> I did exactly the same thing for my second vendor with the exception of
> typing "rsa_vendor2" during keyset generation (I assumed I had to use a
> different name for the new keyset).
>
>  
>
> # ssh-keygen -t rsa_vendor2
>
>  
>
> Files "id_rsa_vendor2" and "id_rsa_vendor2.pub" were created in
> "/root/.ssh/" and I gave "id_rsa_vendor2.pub" to the second vendor.  I
> initiated the first connection with the second vendor and was asked for the
> vendor-provided password which I entered and a successful connection was
> made.  The problem is unlike with the first vendor I am asked for the
> password every time I connect to the second vendor's server.  Because I am
> being asked for the password I am unable to create fully automated batch
> file transfers.
>
>  
>
> The second vendor is telling me they added the public key to their server as
> required.  Did I miss a step or do something wrong on my end?  Was I correct
> using a different name for the new keyset or would the new keyset
> information have been appended to the information already in id_rsa and
> id_rsa.pub for the first vendor?
>
>  
>
> Any help you can provide will be greatly appreciated.
>
>  
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
Are using the -i flag in your invocation of sftp to the second vendor?
>From the sftp man page:

 -i identity_file
 Selects the file from which the identity (private key) for public 
key authentication is read.  This option
 is directly passed to ssh(1).

-- 
Stephen Clark
*NetWolves Managed Services, LLC.*
Sr. Applications Architect 
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.cl...@netwolves.com
http://www.netwolves.com
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] SFTP - Private/Public Authentication Keysets Beyond The First Set

[Gary Braatz]

I'm new to SFTP and using this mailing list was able to successfully create
my first Private/Public keyset for a vendor hosting the SFTP server (I'm the
client).  I created the keyset by typing this:

 

# ssh-keygen -t rsa

 

When asked for the password/passphrase I hit  and afterwards "id_rsa"
and "id_rsa.pub" were created in "/root/.ssh/".  I provided "id_rsa.pub" to
the vendor and when told they were ready I initiated an SFTP transfer.
During the first connection I was asked for the vendor-provided password and
after entering it was successfully connected to the vendor's sftp server.
During successive connections I was not again asked for the password.  This
allowed me to create fully automated batch file transfers.my objective.
Setting up my second vendor is not going as smoothly.

 

I did exactly the same thing for my second vendor with the exception of
typing "rsa_vendor2" during keyset generation (I assumed I had to use a
different name for the new keyset).

 

# ssh-keygen -t rsa_vendor2

 

Files "id_rsa_vendor2" and "id_rsa_vendor2.pub" were created in
"/root/.ssh/" and I gave "id_rsa_vendor2.pub" to the second vendor.  I
initiated the first connection with the second vendor and was asked for the
vendor-provided password which I entered and a successful connection was
made.  The problem is unlike with the first vendor I am asked for the
password every time I connect to the second vendor's server.  Because I am
being asked for the password I am unable to create fully automated batch
file transfers.

 

The second vendor is telling me they added the public key to their server as
required.  Did I miss a step or do something wrong on my end?  Was I correct
using a different name for the new keyset or would the new keyset
information have been appended to the information already in id_rsa and
id_rsa.pub for the first vendor?

 

Any help you can provide will be greatly appreciated.

 

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

[CentOS-docs] Cannot Delete my Name

[G.S.]

Hello guys, Please help.

My name and surname are shown here:
https://wiki.centos.org/GavriilSpiropoulos

I may have some issues because of that. Could you please change my name to
something random or delete my account completely?


-- 
Best Regards,
Gabriel
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS] CentOS 7.6 external USB dmesg issue

[Jerry Geis]

>I'm a tad confused: you said the USB drive was brand new - did you use
>them with C 7.5, or not? Can you try to do a b/u using whatever drive you
>used before?

All the equipment I had before... Motherboard, cable etc...   the drives
are new and this is the behaviour I was seeing...

I am currently running the badblock check - goign slow - 0 errors so far
and 40% done.
I will use an older 2.0 programmer that has an external supply and try
that...

Thanks everyone.

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

Re: [CentOS] CentOS 7.6 external USB dmesg issue

[Stephen John Smoogen]

On Wed, 12 Dec 2018 at 11:38, Jerry Geis  wrote:
>
> >What kind of solid state 2 TB drive is this and how is it 'powered'?
> >It is looking like the drives aren't getting completely written to
> >before being removed as the ext4 error is a 'oh wait this drive
> >doesn't have everything I expected too late to give up aah'
> >type oops
>
> This is a Samsung 860 EVO 2TB. my connection is a cable that provides both
> power and data to the device over the USB 3.1 connection.
>

OK the place where I have seen this before is when someone is trying
to do that. Usually the drive is not getting enough power and will
flake out. The only fix was to put them in an external case with a
separate power supply. The SSD drives seem to come up a lot. I don't
know if it is an amperage issue or something else, but they expect
something that the USB3.1 isn't delivering. I would try putting them
in a case which does accept external power and see if it works better.


> Jerry
> ___
> 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] CentOS 7.6 external USB dmesg issue

[mark]

Jerry Geis wrote:
>> Do you have any "history" with the adapter you connected them to?  If
>> not consider it as a possibility as well
>> (from bad experience of total filesystem/partition corruption on two
>> hard drives only to discover it was >something on the motherboard).
>
> Actually yes I used them many times back on C7.5   Both the motherboard
> and USB adapter.
>
I'm a tad confused: you said the USB drive was brand new - did you use
them with C 7.5, or not? Can you try to do a b/u using whatever drive you
used before?

  mark



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

Re: [CentOS] CentOS 7.6 external USB dmesg issue

[Jerry Geis]

>What kind of solid state 2 TB drive is this and how is it 'powered'?
>It is looking like the drives aren't getting completely written to
>before being removed as the ext4 error is a 'oh wait this drive
>doesn't have everything I expected too late to give up aah'
>type oops

This is a Samsung 860 EVO 2TB. my connection is a cable that provides both
power and data to the device over the USB 3.1 connection.

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

[CentOS-docs] lowering the barriers for wiki.centos.org

[Ken Dreyer]

Hi folks,

What would it take to make it easier for users to sign up and
immediately start contributing to the wiki without having their
accounts approved by hand?

I'd like to host more documentation for the storage SIG there, and I
want to make it easier for other users to contribute without the
manual gating process.

For example, today anyone can sign up for a GitHub account to edit
https://github.com/ktdreyer/storage-sig-utils/blob/master/new-major-release.rst
, and I'd like to have that on the CentOS Wiki instead.

My Ceph team all has GitHub accounts. Are we looking at hooking
MoinMoin into GitHub or accounts.centos.org ? Or moving away from
MoinMoin? What is the current direction?

If we could lower the barriers to entry, we'd set a great tone for the
CentOS project, and the CentOS wiki could have even better content.

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

Re: [CentOS] CentOS 7.6 external USB dmesg issue

[Stephen John Smoogen]

On Wed, 12 Dec 2018 at 09:14, Jerry Geis  wrote:
>
> >Do you have any "history" with the adapter you connected them to?  If not
> consider it as a possibility as well
> >(from bad experience of total filesystem/partition corruption on two hard
> drives only to discover it was >something on the motherboard).
>
> Actually yes I used them many times back on C7.5   Both the motherboard and
> USB adapter.
> Thanks,

What kind of solid state 2 TB drive is this and how is it 'powered'?
It is looking like the drives aren't getting completely written to
before being removed as the ext4 error is a 'oh wait this drive
doesn't have everything I expected too late to give up aah'
type oops.


-- 
Stephen J Smoogen.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 7.6 external USB dmesg issue

[Leon Fauster via CentOS]

> Am 12.12.2018 um 14:49 schrieb Jerry Geis :
> 
> Am I doing something wrong ? I find it hard to believe the SSD (both) are
> bad.
> 

I would check the integrity of this storage device:

# Notice: this destroys your data on the device

badblocks -c 10240 -s -w -t random -v /dev/sdxx

--
LF



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

Re: [CentOS] CentOS 7.6 external USB dmesg issue

[Jerry Geis]

>Do you have any "history" with the adapter you connected them to?  If not
consider it as a possibility as well
>(from bad experience of total filesystem/partition corruption on two hard
drives only to discover it was >something on the motherboard).

Actually yes I used them many times back on C7.5   Both the motherboard and
USB adapter.
Thanks,

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

[CentOS] CentOS 7.6 external USB dmesg issue

[Leroy Tennison]

Do you have any "history" with the adapter you connected them to?  If not 
consider it as a possibility as well (from bad experience of total 
filesystem/partition corruption on two hard drives only to discover it was 
something on the motherboard).


Leroy Tennison
Network Information/Cyber Security Specialist
E: le...@datavoiceint.com
2220 Bush Dr
McKinney, Texas
75070
www.datavoiceint.com
TThis message has been sent on behalf
of a company that is part of the Harris Operating Group of
Constellation Software Inc. These companies are listed
here
.
If you prefer not to be contacted by Harris
Operating Group
please notify us
.
This message is intended exclusively for the
individual or entity to which it is addressed. This communication
may contain information that is proprietary, privileged or
confidential or otherwise legally exempt from disclosure. If you are
not the named addressee, you are not authorized to read, print,
retain, copy or disseminate this message or any part of it. If you
have received this message in error, please notify the sender
immediately by e-mail and delete all copies of the
message.


From: CentOS  on behalf of Jerry Geis 

Sent: Wednesday, December 12, 2018 7:49 AM
To: CentOS mailing list
Subject: [EXTERNAL] [CentOS] CentOS 7.6 external USB dmesg issue

I have a brand new 2T external Samsung SSD disk. (two of them) for backup.

I tried the first one and had an issue, I tried the second one and got the
same issue.

Am I doing something wrong ? I find it hard to believe the SSD (both) are
bad.

I plugged in the USB 3.1 adapter, I fdisk /dev/sdd, n, p, default, default,
w.
then mkfs.ext4 -j /dev/sdd1, then just mount and rsync.

[ 1085.193710]  [] ? account_entity_dequeue+0xae/0xd0
[ 1085.193715]  [] schedule+0x29/0x70
[ 1085.193719]  [] schedule_timeout+0x221/0x2d0
[ 1085.193724]  [] ? __switch_to+0x151/0x580
[ 1085.193730]  [] ? ktime_get_ts64+0x52/0xf0
[ 1085.193735]  [] io_schedule_timeout+0xad/0x130
[ 1085.193740]  [] ? prepare_to_wait_exclusive+0x56/0x90
[ 1085.193744]  [] io_schedule+0x18/0x20
[ 1085.193750]  [] get_request+0x243/0x7d0
[ 1085.193756]  [] ? __radix_tree_create+0x11/0x360
[ 1085.193761]  [] ? wake_up_atomic_t+0x30/0x30
[ 1085.193767]  [] blk_queue_bio+0xfe/0x400
[ 1085.193772]  [] generic_make_request+0x147/0x380
[ 1085.193778]  [] submit_bio+0x70/0x150
[ 1085.193786]  [] ? bio_alloc_bioset+0x115/0x310
[ 1085.193791]  [] _submit_bh+0x127/0x160
[ 1085.193797]  [] submit_bh+0x10/0x20
[ 1085.193808]  []
ext4_read_block_bitmap_nowait+0x4c4/0x640 [ext4]
[ 1085.193828]  [] ext4_mb_init_cache+0x181/0x6e0 [ext4]
[ 1085.193834]  [] ? lru_cache_add+0xe/0x10
[ 1085.193840]  [] ? find_or_create_page+0x5e/0xa0
[ 1085.193858]  [] ext4_mb_init_group+0x126/0x230 [ext4]
[ 1085.193874]  [] ext4_mb_good_group+0x184/0x1a0 [ext4]
[ 1085.193889]  [] ext4_mb_regular_allocator+0x1c5/0x470
[ext4]
[ 1085.193906]  [] ? __ext4_journal_stop+0x3c/0xb0 [ext4]
[ 1085.193921]  [] ?
ext4_mb_normalize_request+0x20c/0x560 [ext4]
[ 1085.193936]  [] ext4_mb_new_blocks+0x65b/0xa20 [ext4]
[ 1085.193942]  [] ? __getblk+0x2d/0x300
[ 1085.193961]  [] ext4_ind_map_blocks+0xb9b/0xc20 [ext4]
[ 1085.193968]  [] ? hrtimer_cancel+0x28/0x40
[ 1085.193973]  [] ? zone_statistics+0x88/0xa0
[ 1085.193987]  [] ext4_map_blocks+0x295/0x6e0 [ext4]
[ 1085.193993]  [] ? do_select+0x73e/0x7c0
[ 1085.193999]  [] ? kmem_cache_alloc+0x1c2/0x1f0
[ 1085.194006]  [] ? alloc_buffer_head+0x21/0x60
[ 1085.194018]  [] _ext4_get_block+0x1df/0x220 [ext4]
[ 1085.194030]  [] ext4_get_block+0x16/0x20 [ext4]
[ 1085.194036]  [] __block_write_begin_int+0x198/0x5f0
[ 1085.194041]  [] ? kmem_cache_alloc+0x1c2/0x1f0
[ 1085.194053]  [] ? _ext4_get_block+0x220/0x220 [ext4]
[ 1085.194067]  [] ? ext4_write_begin+0x116/0x440 [ext4]
[ 1085.194073]  [] __block_write_begin+0x11/0x20
[ 1085.194085]  [] ext4_write_begin+0x18f/0x440 [ext4]
[ 1085.194091]  [] generic_file_buffered_write+0x124/0x2c0
[ 1085.194098]  [] __generic_file_aio_write+0x1e2/0x400
[ 1085.194105]  [] generic_file_aio_write+0x59/0xa0
[ 1085.194116]  [] ext4_file_write+0xd2/0x1e0 [ext4]
[ 1085.194121]  [] do_sync_write+0x93/0xe0
[ 1085.194127]  [] vfs_write+0xc0/0x1f0
[ 1085.194132]  [] SyS_write+0x7f/0xf0
[ 1085.194138]  [] system_call_fastpath+0x22/0x27

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

[CentOS] CentOS 7.6 external USB dmesg issue

[Jerry Geis]

I have a brand new 2T external Samsung SSD disk. (two of them) for backup.

I tried the first one and had an issue, I tried the second one and got the
same issue.

Am I doing something wrong ? I find it hard to believe the SSD (both) are
bad.

I plugged in the USB 3.1 adapter, I fdisk /dev/sdd, n, p, default, default,
w.
then mkfs.ext4 -j /dev/sdd1, then just mount and rsync.

[ 1085.193710]  [] ? account_entity_dequeue+0xae/0xd0
[ 1085.193715]  [] schedule+0x29/0x70
[ 1085.193719]  [] schedule_timeout+0x221/0x2d0
[ 1085.193724]  [] ? __switch_to+0x151/0x580
[ 1085.193730]  [] ? ktime_get_ts64+0x52/0xf0
[ 1085.193735]  [] io_schedule_timeout+0xad/0x130
[ 1085.193740]  [] ? prepare_to_wait_exclusive+0x56/0x90
[ 1085.193744]  [] io_schedule+0x18/0x20
[ 1085.193750]  [] get_request+0x243/0x7d0
[ 1085.193756]  [] ? __radix_tree_create+0x11/0x360
[ 1085.193761]  [] ? wake_up_atomic_t+0x30/0x30
[ 1085.193767]  [] blk_queue_bio+0xfe/0x400
[ 1085.193772]  [] generic_make_request+0x147/0x380
[ 1085.193778]  [] submit_bio+0x70/0x150
[ 1085.193786]  [] ? bio_alloc_bioset+0x115/0x310
[ 1085.193791]  [] _submit_bh+0x127/0x160
[ 1085.193797]  [] submit_bh+0x10/0x20
[ 1085.193808]  []
ext4_read_block_bitmap_nowait+0x4c4/0x640 [ext4]
[ 1085.193828]  [] ext4_mb_init_cache+0x181/0x6e0 [ext4]
[ 1085.193834]  [] ? lru_cache_add+0xe/0x10
[ 1085.193840]  [] ? find_or_create_page+0x5e/0xa0
[ 1085.193858]  [] ext4_mb_init_group+0x126/0x230 [ext4]
[ 1085.193874]  [] ext4_mb_good_group+0x184/0x1a0 [ext4]
[ 1085.193889]  [] ext4_mb_regular_allocator+0x1c5/0x470
[ext4]
[ 1085.193906]  [] ? __ext4_journal_stop+0x3c/0xb0 [ext4]
[ 1085.193921]  [] ?
ext4_mb_normalize_request+0x20c/0x560 [ext4]
[ 1085.193936]  [] ext4_mb_new_blocks+0x65b/0xa20 [ext4]
[ 1085.193942]  [] ? __getblk+0x2d/0x300
[ 1085.193961]  [] ext4_ind_map_blocks+0xb9b/0xc20 [ext4]
[ 1085.193968]  [] ? hrtimer_cancel+0x28/0x40
[ 1085.193973]  [] ? zone_statistics+0x88/0xa0
[ 1085.193987]  [] ext4_map_blocks+0x295/0x6e0 [ext4]
[ 1085.193993]  [] ? do_select+0x73e/0x7c0
[ 1085.193999]  [] ? kmem_cache_alloc+0x1c2/0x1f0
[ 1085.194006]  [] ? alloc_buffer_head+0x21/0x60
[ 1085.194018]  [] _ext4_get_block+0x1df/0x220 [ext4]
[ 1085.194030]  [] ext4_get_block+0x16/0x20 [ext4]
[ 1085.194036]  [] __block_write_begin_int+0x198/0x5f0
[ 1085.194041]  [] ? kmem_cache_alloc+0x1c2/0x1f0
[ 1085.194053]  [] ? _ext4_get_block+0x220/0x220 [ext4]
[ 1085.194067]  [] ? ext4_write_begin+0x116/0x440 [ext4]
[ 1085.194073]  [] __block_write_begin+0x11/0x20
[ 1085.194085]  [] ext4_write_begin+0x18f/0x440 [ext4]
[ 1085.194091]  [] generic_file_buffered_write+0x124/0x2c0
[ 1085.194098]  [] __generic_file_aio_write+0x1e2/0x400
[ 1085.194105]  [] generic_file_aio_write+0x59/0xa0
[ 1085.194116]  [] ext4_file_write+0xd2/0x1e0 [ext4]
[ 1085.194121]  [] do_sync_write+0x93/0xe0
[ 1085.194127]  [] vfs_write+0xc0/0x1f0
[ 1085.194132]  [] SyS_write+0x7f/0xf0
[ 1085.194138]  [] system_call_fastpath+0x22/0x27

Thanks,

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

[CentOS] CentOS-announce Digest, Vol 166, Issue 3

[centos-announce-request]

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. Announcing release of PHP 7.2 (Jan Stan?k)
   2. Announcing release of Varnish 6 (Jan Stan?k)
   3. Announcing release of NodeJS 10 (Jan Stan?k)
   4. Announcing release of nginx 1.14 (Jan Stan?k)
   5. Announcing release of MySQL 8.0 (Jan Stan?k)
   6. Announcing release of Git 2.18 (Jan Stan?k)


--

Message: 1
Date: Tue, 11 Dec 2018 16:23:26 +0100
From: Jan Stan?k 
To: centos-annou...@centos.org
Subject: [CentOS-announce] Announcing release of PHP 7.2
Message-ID: <5f81205f-1311-8186-44f3-12d6e89a2...@redhat.com>
Content-Type: text/plain; charset="windows-1252"

I am pleased to announce the immediate availability of PHP
in version 7.2 on CentOS Linux 7 x86_64,
delivered via a Software Collection (SCL) built by the SCLo Special
Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo).

QuickStart
--
You can get started in three easy steps:

  # 1. Install a package with repository for your system:
  $ sudo yum install centos-release-scl

  # 2. Install the collection:
  $ sudo yum install rh-php72

  # 3. Start using the software collection:
  $ scl enable rh-php72 bash

At this point you should be able to use php
just as a normal application. Examples of commands run might be:

  $ sudo systemctl start rh-php72-php-fpm
  $ php my-app.php
  $ sudo yum install rh-php72-php-devel
  $ sudo yum install libxml2-devel
  $ sudo pear install Cache_Lite
  $ sudo pecl install xmldiff


More information about this collection can be found at
https://www.softwarecollections.org/en/scls/rhscl/rh-php72/

This collections is CentOS-based rebuild built by SCLo SIG community,
and the packages have been available in Red Hat Software Collections 3.2
for RHEL:

https://access.redhat.com/documentation/en-us/red_hat_software_collections/3/html/3.2_release_notes/

So, for RHEL-based builds, follow the steps in the documentation above.

About Software Collections
--
Software Collections give you the power to build, install, and use
multiple versions of software on the same system, without affecting
system-wide installed packages. Each collection is delivered as a group
of RPMs, with the grouping being done using the name of the collection
as a prefix of all packages that are part of the software collection.

The SCLo SIG in CentOS
--
The Software Collections SIG group is an open community group
co-ordinating the development of the SCL technology, and helping curate
a reference set of collections. In addition to the collection NodeJS
being released here, we also build and deliver databases, web servers,
and language stacks including multiple versions of PostgreSQL, MariaDB,
Apache HTTP Server, Python, Ruby, Ruby on Rails and others.

You can learn more about Software Collections concepts at:
https://softwarecollections.org
You can find information on the SIG at
https://wiki.centos.org/SpecialInterestGroup/SCLo ;
this includes how to get involved and help with the effort.

Enjoy!
--
Jan Stanek
Associate Software Engineer, Brno
Red Hat Czech
jsta...@redhat.comIM: jstanek

-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: 


--

Message: 2
Date: Tue, 11 Dec 2018 16:23:39 +0100
From: Jan Stan?k 
To: centos-annou...@centos.org
Subject: [CentOS-announce] Announcing release of Varnish 6
Message-ID: 
Content-Type: text/plain; charset="windows-1252"

I am pleased to announce the immediate availability of Varnish
in version 6 on CentOS Linux 7 x86_64,
delivered via a Software Collection (SCL) built by the SCLo Special
Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo).

QuickStart
--
You can get started in three easy steps:

  # 1. Install a package with repository for your system:
  $ sudo yum install centos-release-scl

  # 2. Install the collection:
  $ sudo yum install rh-varnish6

  # 3. Start using software collections:
  $ scl enable rh-varnish6 bash

At this point you should be able to use varnish just as a normal
application.
Some usage examples follow:

$ sudo systemctl start rh-varnish6-varnish
$ varnishtop


More information about this collection can be found at