SELKS upgrades

Peter Manev edited this page May 4, 2018 · 13 revisions

Regular upgrade

SELKS supports its own generic and standard Debian 64 bit packaging repositories. All SELKS packages by Stamus Networks are using the Debian packaging standard and routines.

For regular SELKS upgrades you can run the upgrade from the wrapper script located in:

/opt/selks/Scripts/Setup/selks-upgrade_stamus.sh

For major SELKS upgrades - for example SELKS 3 to SELKS 4 you can follow the instructions for SELKS Major Upgrades

It is recommended to use SELKS provided version of configuration files as they will guarantee you that the system will work correctly. So answer Y if/when you are asked what you would like to do about configuration file differences during the upgrade. This will be ideal in most cases.

Known upgrade errors and fixes

Desktop base

If you encounter the following error during an upgrade:

 Setting up desktop-base (9.0.2+deb9u1) ...
update-alternatives: error: cannot stat file '/etc/alternatives/desktop-background': Invalid argument
dpkg: error processing package desktop-base (--configure):
subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
desktop-base
E: Sub-process /usr/bin/dpkg returned an error code (1)

The proper way to fix this is:

yes | cp -rf /etc/alternatives/desktop-background /usr/share/images/desktop-base/desktop-background-selks
rm /etc/alternatives/desktop-background
update-alternatives --install  /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/images/desktop-base/desktop-background-selks 75
update-alternatives --set desktop-background /usr/share/images/desktop-base/desktop-background-selks

then run again:

opt/selks/Scripts/Setup/selks-upgrade_stamus.sh

Logstash 5.6.9+ breaking upgrade

During a 5.6.9 upgrade and above you may experience the similar to the following error:

[2018-04-19T08:27:00,017][ERROR][logstash.pipeline ] Exception in pipelineworker, the pipeline stopped processing
new events, please check your filter configuration and restart Logstash. {"exception"=>"undefined method tr' for
-73.6992:Float", "backtrace"=>["/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-filter-mutate-
3.3.1/lib/logstash/filters/mutate.rb:344:inconvert_float'", "org/jruby/RubyMethod.java:120:in call'",
"/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-filter-mutate-
3.3.1/lib/logstash/filters/mutate.rb:309:inconvert'", "org/jruby/RubyArray.java:2414:in map'",
"/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-filter-mutate-
3.3.1/lib/logstash/filters/mutate.rb:309:inconvert'", "org/jruby/RubyHash.java:1342:in each'",
"/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-filter-mutate-
3.3.1/lib/logstash/filters/mutate.rb:299:inconvert'",
....

The fix is explained here

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.