Skip to content

zfs-snap-manager and "Got invalid schema for dataset" or not deleted old snapshots or not created new snapshots

I am using the zfs-snap-manager for such a long time that I never ever had a look on it since years.

I've just created zfs pools and zfs snap manager configurations without thinking or checking it for a while now. But once upon a time I wanted to check the behaviour and found out that some configured snapshots where not made.

After a while I saw that my assumption was false, so the error was in front of the display :-).

My configuration for the section schema was simplified to 7d because all I wanted for a dataset was that I can go back the last seven days. After finding the log file (/var/log/zfs-snap-manager.log) and tailing it, I quickly saw the log message Got invalid schema for dataset .... Just a bit more investigation and I found out that I have to provide a fully defined schema like 7d0w0m0y. After adapting all available configuration files on all hosts, the zfs-snap-manager is working as expected.

I found an existing feature request to "relaxed" the schema interpretion and stumpled over another feature request asking for creating unittests. So I've forked it and will try to learn python by fixing the issue on my own.

  • migrate code to python3
  • write unittests
  • implement relaxed handling of schema with default values

Do you want to join? Contact me if you want to.

Translate to de es fr it pt ja

Nextcloud Client 3.0.1 on Linx >> there are unresolved conflicts<<

As written in the official issue ticket, following the way how to solve your conflict locally.

A quick update to figure out the conflicted files. cd into your nextcloud synchronized path

#list conflicted files 
find . -iname *conflic* -type f

You can than decide which file is the one you want to keep foo.bar or foo (conflicted copy 2020-09-09 083407).bar.

See also here and here.

Translate to de es fr it pt ja

How to set a proxy for Signal-Desktop on Windows

If you want to use signal behind a cooperate proxy, you have to write a little bat script to set some proxy variables in the environment before starting signal. Copy and paste the following code into a file like set_proxy_and_start_signal.bat.

:: ####
:: # Sets http and https proxy variables and starts signal.
:: ####
:: # @see: https://github.com/signalapp/Signal-Desktop/issues/1430#issuecomment-397229333
:: # @since: 2020-02-14
:: # @author: stev leibelt <artodeto@bazzline.net>
:: ####

set HTTP_PROXY=<your proxy>
set HTTPS_PROXY=%HTTP_PROXY%
start %LOCALAPPDATA%\Programs\signal-desktop\Signal.exe

If you want to know more here is the thread for this issue.

Translate to de es fr it pt ja

Migration from Windows Outlook 2007 to Linux Thunderbird

It is doable!

All you need to do is to read this and this migration guides from mozilla.

Or, you just do my step-by-step list.

  • Download Thunderbird version 31.8
  • Download Mail PassView
  • Run mailpass view and note down all important informations
  • Install Thunderbird
  • Open thunderbird and import things (tools->import) - important import each single stuff (mails, contacts)
  • Add your mail accounts
  • Upgrade thunderbird
  • Copy the thunderbird profile (c:\Users\\AppData ...) to your linux pc
  • Edit and update ~.mozilla-thunderbird|thunderbird/profiles.ini
    Translate to de es fr it pt ja