One day I will need to enable repeating those messages: [WayBack] linux – Is there a way to remove “Last message repeated x times” from logs? – Server Fault
–jeroen
Posted by jpluimers on 2018/12/17
One day I will need to enable repeating those messages: [WayBack] linux – Is there a way to remove “Last message repeated x times” from logs? – Server Fault
–jeroen
Posted in *nix, *nix-tools, Linux, Power User | Leave a Comment »
Posted by jpluimers on 2018/12/13
For my link archive:
Non-stable repos:
–jeroen
Posted in *nix, Linux, Monitoring, Nagios, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »
Posted by jpluimers on 2018/12/05
A (long!) while ago, I wrote about list date with seconds from ls command – Dev Shed that showed how to list the full ISO timestamp (including seconds) of files.
This is an update.
The previous post showed that you could use this statement to list all files with their full ISO timestamps (and therefore get both the seconds and milliseconds) on (open)SuSE Linux, Mac OS X and Cygwin:
ls -l --time-style=full-iso
What Linux and displaying dates in ISO 8601 format… : Little Green Delusions proposes are two solutions to make this more permanent:
alias ls='ls -l --time-style=long-iso'
or edit one of your profile files (he prefers /etc/profile.local, but that is system wide, so I usually prefer ~/.bash_profile) to add this line:
export TIME_STYLE=long-iso
The thing is: I do not always want to have ls -l show ISO 8601 dates. I like the way that ls-l lists timestamps for very old or future files: Read the rest of this entry »
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux | Leave a Comment »
Posted by jpluimers on 2018/11/30
From a long time ago:
[WayBack] how can I free up space on /boot as “openSUSE-2014-462” fails to install on openSUSE 12.3 (x86_64):
Installation of kernel-desktop-3.7.10-1.40.1 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: installing package kernel-desktop-3.7.10-1.40.1.x86_64 needs 16MB on the /boot filesystem
Based on that thread, I figured out the steps:
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux | Leave a Comment »
Posted by jpluimers on 2018/11/22
One occasion I had SSH throw a Connection Reset by Peer on my when was the SD-card of a Raspberry Pi started failing and the ext4 filesystem got mounted in read-only mode.
Then sshd was still listening on port 22, but since it could not write to disk any more, it threw a Connection Reset by Peer to the client.
It was on OpenSuSE Tumbleweed, but would failed just as well using Raspbian.
Lessons learned:
ext4 breaks when the hardware breaks.–jeroen
Reference:
Posted in *nix, *nix-tools, Debian, Development, Hardware Development, IoT Internet of Things, Linux, Network-and-equipment, openSuSE, Power User, Raspberry Pi, Raspbian, SuSE Linux, Tumbleweed | Leave a Comment »
Posted by jpluimers on 2018/10/29
Interesting: [Archive.is] Install on openSUSE / SLES – Zabbix.org is possible and there are packages for this on the OpenSuSE site itself for the various kinds of distributions.
For instance, Tumbleweed is at http://download.opensuse.org/repositories/server:/monitoring/openSUSE_Tumbleweed/
Good introductions on Zabbix are via [WayBack] Stephen Fritz on Systems Engineering: Installing and Configuring Basic Zabbix Functionality on Debian Wheezy who has a [Archive.is] zabbix tag.
Other links are at Welcome to workaround.org – tips around open source and Linux stuff.
And there is www.zabbix.com/documentation
–jeroen
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »
Posted by jpluimers on 2018/10/11
Hopefully I get this to work after fixing
The first part of the fix was to
The second part is getting the USB web cameras to work.
I’ve got two types, but the label on them doesn’t list their common name, only their P/N sometimes with M/N:
The MotionEyeOS web interface didn’t list any working cameras so I had to do some digging.
Luckily [WayBack] Webcam software and driver support for Windows has a table of part and model numbers combined with product names, so they got revealed them as these:
Both are supported by motion according to [WayBack] Logitech < Motion < Foswiki though the Quick Cam Messenger needs [WayBack] Quickcam Messenger & Communicate driver for Linux which I should try to cross-compile one day.
The latter works fine. Below are some settings I used.
Posted in *nix, Development, Hardware Development, Linux, Odroid, Power User | Leave a Comment »
Posted by jpluimers on 2018/09/28
A while ago, I documented some links for In case I ever need to record calls on my Fritz!Box devices.
By now, I’ve done a bit more investigation: I’ve enabled the call monitor, did some port scans, installed domoticz and got deeper into fritzcap.
Oh and I got packet capturing to work too: Fritz!Box – capture network packets in Wireshark format or ISDN in dtrace format.
A small recap so I don’t forget what I did and what the effects were.
[WayBack] Fritzbox – Domoticz showed how to enable the CallMonitor option in your Fritz!Box
Posted in *nix, Fritz!, Fritz!Box, Internet, Linux, openSuSE, Power User, SuSE Linux | Leave a Comment »
Posted by jpluimers on 2018/09/15
Not sure in which changeset this happened, but here is one example:
1:b8:27:eb:1a:b1:ecff:eb:78:a9:4:0:1:0:1:22:6:67:49:b8:27:eb:78:a9:4The first one was marked static in the DHCP server, which means the Raspberry Pi now did get a different IP address.
This messes up a few places that cannot do proper address resolution.
Anyone who knows where this has changed / is configured?
These did not help finding the cause:
As commented by Leen below, this is about
Wicked changed its defaults to use this DHCPv6 compatible RFC4361 client-id in favour of the older RFC2132 client-id. However, this has caused some issues with older DHCPv4 servers and existing setups where the client-id stored by the server is used to assign a (static) address. It is recommended to fix this server-side, but still, wicked provides several ways of addressing this issue
So here are some links:
2018-02-02 - mt@suse.de - version 0.6.44 - dhcp4: use rfc4361 client-id as new default for ethernet on sle15 (fate#323576). It can be also enabled/disabled in wicked-config(5). - client: fixed broken wicked arp utility command (bsc#1078245) - cleanup: add mising/explicit designated field initializers - pkgconfig: fix to request libnl3 instead of libnl1 - dbus: add missing DBUS_ERROR_FAILED type to a dbus_set_error call and enforce formatting input as string when an extension did not returned any error message. - Removed patch included in the source archive [- 0001-wickedd-explicitly-unbind-slaves-on-deletion.patch]
The traditionally used RFC 2132 DHCPv4
client-idon Ethernet is constructed from the hardware type (01for Ethernet) and followed by the hardware address (the MAC address), for example:01:52:54:00:02:c2:67The RFC 4361
client-idstarts with0xff(instead of the hardware type), followed by the DHCPv6 IAID (the interface-address association ID that describes the interface on the machine), followed by the DHCPv6 DUID (client-idwhich identifies the machine).Using the above hardware type-based and hardware address-based DUID (LLT type used by default), the new RFC 4361 DHCPv4
client-idwould be:
- Using the last bytes of the MAC address as the IAID:
ff:00:02:c2:67:00:01:xx:xx:xx:xx:52:54:00:02:c2:67- When the IAID is a simple incremented number:
ff:00:00:00:01:00:01:xx:xx:xx:xx:52:54:00:02:c2:67
–jeroen
Posted in *nix, Hardware Development, Linux, openSuSE, Power User, Raspberry Pi, SuSE Linux, Tumbleweed | 6 Comments »
Posted by jpluimers on 2018/09/07
Too bad most of them are very picky to the Linux distributions they run on.
–jeroen
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux | Leave a Comment »