My server hung yesterday. I did not notice it; at this stage in the game, I should be much more aware...
I looked into /var/log/messages and my last entry was:
Feb 5 15:03:46 medon kernel: conntrack: generic helper won't handle protocol 47 . Please consider loading the specific helper module.
So I don't know if someone knocked me over with a GRE based attack, if the drive is bad, if the board is bad, or the OS has a problem.
So simple things to start with. I see an earlier GRE warning in messages:
Feb 5 03:29:49 medon kernel: conntrack: generic helper won't handle protocol 47. Please consider loading the specific helper module.
So it is probably not a stack problem with attacking GRE bots. BTW, is there some 'easy' way to just block these?
As to the drive: Is there some way to run a SMART? check on the drive?
Can't really tell too well if it is a board problem other than to watch more closely to see how things go, is there anywhere else I should look to find the problem?
thanks
On 02/06/2017 03:16 PM, Robert Moskowitz wrote:
My server hung yesterday. I did not notice it; at this stage in the game, I should be much more aware...
I looked into /var/log/messages and my last entry was:
Feb 5 15:03:46 medon kernel: conntrack: generic helper won't handle protocol 47 . Please consider loading the specific helper module.
So I don't know if someone knocked me over with a GRE based attack, if the drive is bad, if the board is bad, or the OS has a problem.
So simple things to start with. I see an earlier GRE warning in messages:
Feb 5 03:29:49 medon kernel: conntrack: generic helper won't handle protocol 47. Please consider loading the specific helper module.
So it is probably not a stack problem with attacking GRE bots. BTW, is there some 'easy' way to just block these?
$IPTABLES -A INPUT -i $EXTERNAL_INTERFACE -p gre -j REJECT
On 02/06/2017 08:44 AM, Manuel Wolfshant wrote:
On 02/06/2017 03:16 PM, Robert Moskowitz wrote:
My server hung yesterday. I did not notice it; at this stage in the game, I should be much more aware...
I looked into /var/log/messages and my last entry was:
Feb 5 15:03:46 medon kernel: conntrack: generic helper won't handle protocol 47 . Please consider loading the specific helper module.
So I don't know if someone knocked me over with a GRE based attack, if the drive is bad, if the board is bad, or the OS has a problem.
So simple things to start with. I see an earlier GRE warning in messages:
Feb 5 03:29:49 medon kernel: conntrack: generic helper won't handle protocol 47. Please consider loading the specific helper module.
So it is probably not a stack problem with attacking GRE bots. BTW, is there some 'easy' way to just block these?
$IPTABLES -A INPUT -i $EXTERNAL_INTERFACE -p gre -j REJECT
Thanks, but how do I do that in firewall-cmd?
# firewall-cmd --list-all public (active) target: default icmp-block-inversion: no interfaces: eth0 sources: services: dhcpv6-client http https ports: 1234/tcp protocols: masquerade: no forward-ports: sourceports: icmp-blocks: rich rules:
Hello
On my side I got a lot of freezes when I use a 4.4 kernel.. maybe the same for you ?
Le 6 février 2017 14:16:46 GMT+01:00, Robert Moskowitz rgm@htt-consult.com a écrit :
My server hung yesterday. I did not notice it; at this stage in the game, I should be much more aware...
I looked into /var/log/messages and my last entry was:
Feb 5 15:03:46 medon kernel: conntrack: generic helper won't handle protocol 47 . Please consider loading the specific helper module.
So I don't know if someone knocked me over with a GRE based attack, if the drive is bad, if the board is bad, or the OS has a problem.
So simple things to start with. I see an earlier GRE warning in messages:
Feb 5 03:29:49 medon kernel: conntrack: generic helper won't handle protocol 47. Please consider loading the specific helper module.
So it is probably not a stack problem with attacking GRE bots. BTW, is
there some 'easy' way to just block these?
As to the drive: Is there some way to run a SMART? check on the drive?
Can't really tell too well if it is a board problem other than to watch
more closely to see how things go, is there anywhere else I should look
to find the problem?
thanks
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Looks like I am running 4.4.34-201
Dec 05 15:56:36 Installed: kernel-4.4.34-201.el7.armv7hl
back on 1/29 there was an email about 4.4.42-202, but not how to upgrade to this kernel...
On 02/06/2017 08:52 AM, Nicolas Repentin wrote:
Hello
On my side I got a lot of freezes when I use a 4.4 kernel.. maybe the same for you ?
Le 6 février 2017 14:16:46 GMT+01:00, Robert Moskowitz rgm@htt-consult.com a écrit :
My server hung yesterday. I did not notice it; at this stage in the game, I should be much more aware... I looked into /var/log/messages and my last entry was: Feb 5 15:03:46 medon kernel: conntrack: generic helper won't handle protocol 47 . Please consider loading the specific helper module. So I don't know if someone knocked me over with a GRE based attack, if the drive is bad, if the board is bad, or the OS has a problem. So simple things to start with. I see an earlier GRE warning in messages: Feb 5 03:29:49 medon kernel: conntrack: generic helper won't handle protocol 47. Please consider loading the specific helper module. So it is probably not a stack problem with attacking GRE bots. BTW, is there some 'easy' way to just block these? As to the drive: Is there some way to run a SMART? check on the drive? Can't really tell too well if it is a board problem other than to watch more closely to see how things go, is there anywhere else I should look to find the problem? thanks ------------------------------------------------------------------------ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev-- Nicolas
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Looks like it ran for 3 hours before hanging. This time the last message was:
Feb 6 11:01:02 medon systemd: Removed slice user-0.slice. Feb 6 11:01:02 medon systemd: Stopping user-0.slice.
Someone please chime in on how to upgrade the kernel. It has not been pushed to the kernel repo,,,
On 02/06/2017 09:01 AM, Robert Moskowitz wrote:
Looks like I am running 4.4.34-201
Dec 05 15:56:36 Installed: kernel-4.4.34-201.el7.armv7hl
back on 1/29 there was an email about 4.4.42-202, but not how to upgrade to this kernel...
On 02/06/2017 08:52 AM, Nicolas Repentin wrote:
Hello
On my side I got a lot of freezes when I use a 4.4 kernel.. maybe the same for you ?
Le 6 février 2017 14:16:46 GMT+01:00, Robert Moskowitz rgm@htt-consult.com a écrit :
My server hung yesterday. I did not notice it; at this stage in the game, I should be much more aware... I looked into /var/log/messages and my last entry was: Feb 5 15:03:46 medon kernel: conntrack: generic helper won't handle protocol 47 . Please consider loading the specific helper module. So I don't know if someone knocked me over with a GRE based attack, if the drive is bad, if the board is bad, or the OS has a problem. So simple things to start with. I see an earlier GRE warning in messages: Feb 5 03:29:49 medon kernel: conntrack: generic helper won't handle protocol 47. Please consider loading the specific helper module. So it is probably not a stack problem with attacking GRE bots. BTW, is there some 'easy' way to just block these? As to the drive: Is there some way to run a SMART? check on the drive? Can't really tell too well if it is a board problem other than to watch more closely to see how things go, is there anywhere else I should look to find the problem? thanks ------------------------------------------------------------------------ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev-- Nicolas
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Hello
If a newer package exists for kernel, you should have it with yum update.
For my part I don't have freezes using 4.2 from the original image. With pcduino3 nano, or bananapi, I always got freezes on 4.4, with no more info like you.
Le 06/02/2017 à 18:17, Robert Moskowitz a écrit :
Looks like it ran for 3 hours before hanging. This time the last message was:
Feb 6 11:01:02 medon systemd: Removed slice user-0.slice. Feb 6 11:01:02 medon systemd: Stopping user-0.slice.
Someone please chime in on how to upgrade the kernel. It has not been pushed to the kernel repo,,,
On 02/06/2017 09:01 AM, Robert Moskowitz wrote:
Looks like I am running 4.4.34-201
Dec 05 15:56:36 Installed: kernel-4.4.34-201.el7.armv7hl
back on 1/29 there was an email about 4.4.42-202, but not how to upgrade to this kernel...
On 02/06/2017 08:52 AM, Nicolas Repentin wrote:
Hello
On my side I got a lot of freezes when I use a 4.4 kernel.. maybe the same for you ?
Le 6 février 2017 14:16:46 GMT+01:00, Robert Moskowitz rgm@htt-consult.com a écrit :
My server hung yesterday. I did not notice it; at this stage in the game, I should be much more aware... I looked into /var/log/messages and my last entry was: Feb 5 15:03:46 medon kernel: conntrack: generic helper won't handle protocol 47 . Please consider loading the specific helper module. So I don't know if someone knocked me over with a GRE based attack, if the drive is bad, if the board is bad, or the OS has a problem. So simple things to start with. I see an earlier GRE warning in messages: Feb 5 03:29:49 medon kernel: conntrack: generic helper won't handle protocol 47. Please consider loading the specific helper module. So it is probably not a stack problem with attacking GRE bots. BTW, is there some 'easy' way to just block these? As to the drive: Is there some way to run a SMART? check on the drive? Can't really tell too well if it is a board problem other than to watch more closely to see how things go, is there anywhere else I should look to find the problem? thanks ------------------------------------------------------------------------ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev-- Nicolas
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
yum update does not pick up the new 4.4.42 kernel. Fabian Arrotin put it at:
https://armv7.dev.centos.org/repodir/arm-kernels/4.4.42-202/
Ah, I figured it out. Add this as the baseurl in the CentOS-armhfp-kernel.repo.
So I will reboot with the new kernel and see how it goes.
On 02/06/2017 12:19 PM, Nicolas Repentin wrote:
Hello
If a newer package exists for kernel, you should have it with yum update.
For my part I don't have freezes using 4.2 from the original image. With pcduino3 nano, or bananapi, I always got freezes on 4.4, with no more info like you.
Le 06/02/2017 à 18:17, Robert Moskowitz a écrit :
Looks like it ran for 3 hours before hanging. This time the last message was:
Feb 6 11:01:02 medon systemd: Removed slice user-0.slice. Feb 6 11:01:02 medon systemd: Stopping user-0.slice.
Someone please chime in on how to upgrade the kernel. It has not been pushed to the kernel repo,,,
On 02/06/2017 09:01 AM, Robert Moskowitz wrote:
Looks like I am running 4.4.34-201
Dec 05 15:56:36 Installed: kernel-4.4.34-201.el7.armv7hl
back on 1/29 there was an email about 4.4.42-202, but not how to upgrade to this kernel...
On 02/06/2017 08:52 AM, Nicolas Repentin wrote:
Hello
On my side I got a lot of freezes when I use a 4.4 kernel.. maybe the same for you ?
Le 6 février 2017 14:16:46 GMT+01:00, Robert Moskowitz rgm@htt-consult.com a écrit :
My server hung yesterday. I did not notice it; at this stage in the game, I should be much more aware... I looked into /var/log/messages and my last entry was: Feb 5 15:03:46 medon kernel: conntrack: generic helper won't handle protocol 47 . Please consider loading the specific helper module. So I don't know if someone knocked me over with a GRE based attack, if the drive is bad, if the board is bad, or the OS has a problem. So simple things to start with. I see an earlier GRE warning in messages: Feb 5 03:29:49 medon kernel: conntrack: generic helper won't handle protocol 47. Please consider loading the specific helper module. So it is probably not a stack problem with attacking GRE bots. BTW, is there some 'easy' way to just block these? As to the drive: Is there some way to run a SMART? check on the drive? Can't really tell too well if it is a board problem other than to watch more closely to see how things go, is there anywhere else I should look to find the problem? thanks ------------------------------------------------------------------------ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev-- Nicolas
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Oh, yes, this link is not a standard repo. You can pick up the rpm file and install it with "yum install <path to rpm file>.
Le 06/02/2017 à 18:27, Robert Moskowitz a écrit :
yum update does not pick up the new 4.4.42 kernel. Fabian Arrotin put it at:
https://armv7.dev.centos.org/repodir/arm-kernels/4.4.42-202/
Ah, I figured it out. Add this as the baseurl in the CentOS-armhfp-kernel.repo.
So I will reboot with the new kernel and see how it goes.
On 02/06/2017 12:19 PM, Nicolas Repentin wrote:
Hello
If a newer package exists for kernel, you should have it with yum update.
For my part I don't have freezes using 4.2 from the original image. With pcduino3 nano, or bananapi, I always got freezes on 4.4, with no more info like you.
Le 06/02/2017 à 18:17, Robert Moskowitz a écrit :
Looks like it ran for 3 hours before hanging. This time the last message was:
Feb 6 11:01:02 medon systemd: Removed slice user-0.slice. Feb 6 11:01:02 medon systemd: Stopping user-0.slice.
Someone please chime in on how to upgrade the kernel. It has not been pushed to the kernel repo,,,
On 02/06/2017 09:01 AM, Robert Moskowitz wrote:
Looks like I am running 4.4.34-201
Dec 05 15:56:36 Installed: kernel-4.4.34-201.el7.armv7hl
back on 1/29 there was an email about 4.4.42-202, but not how to upgrade to this kernel...
On 02/06/2017 08:52 AM, Nicolas Repentin wrote:
Hello
On my side I got a lot of freezes when I use a 4.4 kernel.. maybe the same for you ?
Le 6 février 2017 14:16:46 GMT+01:00, Robert Moskowitz rgm@htt-consult.com a écrit :
My server hung yesterday. I did not notice it; at this stage in the game, I should be much more aware... I looked into /var/log/messages and my last entry was: Feb 5 15:03:46 medon kernel: conntrack: generic helper won't handle protocol 47 . Please consider loading the specific helper module. So I don't know if someone knocked me over with a GRE based attack, if the drive is bad, if the board is bad, or the OS has a problem. So simple things to start with. I see an earlier GRE warning in messages: Feb 5 03:29:49 medon kernel: conntrack: generic helper won't handle protocol 47. Please consider loading the specific helper module. So it is probably not a stack problem with attacking GRE bots. BTW, is there some 'easy' way to just block these? As to the drive: Is there some way to run a SMART? check on the drive? Can't really tell too well if it is a board problem other than to watch more closely to see how things go, is there anywhere else I should look to find the problem? thanks ------------------------------------------------------------------------ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev-- Nicolas
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
The adding the baseurl to the repo file, and turning off gpg check nicely updates the needed files.
On 02/06/2017 12:31 PM, Nicolas Repentin wrote:
Oh, yes, this link is not a standard repo. You can pick up the rpm file and install it with "yum install <path to rpm file>.
Le 06/02/2017 à 18:27, Robert Moskowitz a écrit :
yum update does not pick up the new 4.4.42 kernel. Fabian Arrotin put it at:
https://armv7.dev.centos.org/repodir/arm-kernels/4.4.42-202/
Ah, I figured it out. Add this as the baseurl in the CentOS-armhfp-kernel.repo.
So I will reboot with the new kernel and see how it goes.
On 02/06/2017 12:19 PM, Nicolas Repentin wrote:
Hello
If a newer package exists for kernel, you should have it with yum update.
For my part I don't have freezes using 4.2 from the original image. With pcduino3 nano, or bananapi, I always got freezes on 4.4, with no more info like you.
Le 06/02/2017 à 18:17, Robert Moskowitz a écrit :
Looks like it ran for 3 hours before hanging. This time the last message was:
Feb 6 11:01:02 medon systemd: Removed slice user-0.slice. Feb 6 11:01:02 medon systemd: Stopping user-0.slice.
Someone please chime in on how to upgrade the kernel. It has not been pushed to the kernel repo,,,
On 02/06/2017 09:01 AM, Robert Moskowitz wrote:
Looks like I am running 4.4.34-201
Dec 05 15:56:36 Installed: kernel-4.4.34-201.el7.armv7hl
back on 1/29 there was an email about 4.4.42-202, but not how to upgrade to this kernel...
On 02/06/2017 08:52 AM, Nicolas Repentin wrote:
Hello
On my side I got a lot of freezes when I use a 4.4 kernel.. maybe the same for you ?
Le 6 février 2017 14:16:46 GMT+01:00, Robert Moskowitz rgm@htt-consult.com a écrit :
My server hung yesterday. I did not notice it; at this stage in the game, I should be much more aware... I looked into /var/log/messages and my last entry was: Feb 5 15:03:46 medon kernel: conntrack: generic helper won't handle protocol 47 . Please consider loading the specific helper module. So I don't know if someone knocked me over with a GRE based attack, if the drive is bad, if the board is bad, or the OS has a problem. So simple things to start with. I see an earlier GRE warning in messages: Feb 5 03:29:49 medon kernel: conntrack: generic helper won't handle protocol 47. Please consider loading the specific helper module. So it is probably not a stack problem with attacking GRE bots. BTW, is there some 'easy' way to just block these? As to the drive: Is there some way to run a SMART? check on the drive? Can't really tell too well if it is a board problem other than to watch more closely to see how things go, is there anywhere else I should look to find the problem? thanks ------------------------------------------------------------------------ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev-- Nicolas
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
-
Manuel Wolfshant -
Nicolas Repentin -
Robert Moskowitz