mathjax

Tuesday, October 24, 2017

Stop IPTables and Other Kernel Messages From Flooding Your Console

The Problem

Console gets flooded with messages like this:

[1909322.686129] SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx SRC=xxx.xxx.xxx.xxx DST=xxx.xxx.xxx.xxx LEN=60 TOS=0x00 PREC=0x00
TTL=39 ID=30338 PROTO=TCP SPT=33453 DPT=22 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX)



Solutions

They all rely on something similar to writing to /proc/sys/kernel/printk:

  1. echo "3 4 1 3" > /proc/sys/kernel/printk
  2. $ sysctl -w kernel.printk="3 4 1 3"
  3. $ dmesg -n 4
  4. Create the file /etc/sysctl.d/50-stop-dmesg-flood.conf and put the following line in it: kernel.printk = 3       4       1       3


To check:
  1. $ cat /proc/sys/kernel/printk
  2. $ sysctl kernel.printk

References

Friday, October 20, 2017

Google chrome version 62.0.3202.62 is not working for me

The Problem

Google chrome version 62.0.3202.62 starts but is not working in several linux distributions. It shows lots of sad faces in each open tab, all of the chrome extensions crash. Not even "Help -> About Google Chrome" works.

The "Not Really Good Solution"

You are able to start it if you run:
$ google-chrome --no-sandbox &
At least you can quickly see some important information you left in a tab before you did the upgrade.

The Slightly Better Solution

This one works too:
google-chrome --disable-namespace-sandbox &
Better than no sandbox, I guess...

Good links for information

I'll try to keep them here:
  1. https://bugs.chromium.org/p/chromium/issues/detail?id=776359
  2. https://forums.opensuse.org/showthread.php/527688-Google-Chrome-not-working-after-update
  3. https://www.reddit.com/r/SolusProject/comments/778gcf/google_chrome_stable_busted_after_update_to_62/

Google Chrome Legacy Versions, no RPMS unfortunately