Update for release Jakarta 2018.327


#1

Dear users,

we have tagged an updated 2018.327 release on Github [1]. The main change is the addition of the caps_plugin to Seedlink which allows to acquire data from our CAPS waveform server, e.g. data from the RaspberryShake network.

Additionally two minor bugs were fixed with a contribution from Luca Scarabello / ETHZ. Thanks a lot.

In scolv amplitude review window you can now decide whether to use the configured minimum SNR from the bindings or the value set in the GUI. The default is to use the bindings parameter to be able to reproduce the automatic processing. In case you want to override the configured minimum SNR, check the override option (left to the SNR spin box) and set the value as desired.

More documentation has been added for e.g. sccnv and many parameters descriptions received a description of their unit.

Thanks to Andres Heinloo a bug was fixed in inv2dlsv when writing FIR continuation blockettes.

Regards,
Jan

[1] https://github.com/SeisComP3/seiscomp3/archive/release/jakarta/2018.327.04.zip


#2

Dear all,

I need yo add several stations MY (ahttp://ds.iris.edu/mda/MY/) nd MS (http://ds.iris.edu/mda/MS/) in GFZ_inventory.xml. Help me. please how to do that? Many thanks.

Best regards,

Madlazim


#3

what about master branch… which version is it?


#4

sorry if double post it…

I have not update my sc since the beginning 2018 i guess, so today I compiled master branch.

It compiled well, but my sc won’t connect to database.

how to fix it?

======================= EDIT ===================

okay, my bad…

I miss the thing that I have to migrate my database from 0.10 to 0.11 LOL


#5

Can you please elaborate how to migrate from 0.10 to 0.11.

There is a instruction on the 0.8 to 0.9 in the cahngelog (2016.333 version) but I cannot find what has to change to 0.11

kind regards


#6

To migrate, see what instructed after you run seiscomp update-config

≠===============

Dear jan, I used latest master branch, but everytime i create event from scrttv, suddenly scolv is crashed and killed.

Is this a bug?


#7

Thanks a lot for spotting that. Yes, it is a bug and I have pushed a fix. Please give it a try and I will create a new patch release. Unfortunately this is a regression from a recent change.

Regards,
Jan


#8

Great thanks!:+1:


#9

Thanks jan,
Anyway, when I compile new version and install, it updated some settings to default, such as scheli and cities.xml

How to keep it as it is after install new version?


#10

Does the commit fix the crash for you?

Which settings does the installation overwrite? You should never modify files which are shipped with the distribution. If you want your own version of cities.xml, put it under ~/.seiscomp3/cities.xml.

Regards,
Jan


#11

Yes, absolutely fixed.


#12

Dear users,

When i try to update seiscomp with the last release the scmaster stops run. In the past i never have the similar problem. The SO is the OpenSuse 13.1. Is there any step that i need to do before?
I would appreciate your help

Regards,

Jose

  • starting kernel modules
    spread is already running
    starting scmaster
  • configure kernel
  • configure spread
    using configuration template in /home/sysop/seiscomp3/share/templates/spread.conf.tpl
  • configure scmaster
    • check database write access … OK
    • database schema version is 0.10
    • last migration version is 0.11
    • migration to the current version is required. apply the following
      scripts in exactly the given order:
      • /home/sysop/seiscomp3/share/db/migrations/mysql/0_10_to_0_11.sql
        error: updating configuration for scmaster failed

master.log

2019/03/18 15:14:20 [warning/DbPlugin] Database schema v0.10 is older than schema v0.11 currently supported. Information will be lost when saving objects to the databas
e! This should be fixed!
2019/03/18 15:14:20 [error/DbPlugin] Strict version check is enabled and schema versions do not match.
2019/03/18 15:14:20 [error/MASTER_COM_MODULE] Plugin dbplugin not operational. Bailing out


#13

Dear users,

When i try to update seiscomp with the last release the scmaster stops
run. In the past i never have the similar problem. The SO is the
OpenSuse 13.1. Is there any step that i need to do before?

I would appreciate your help

Regards,

Jose

  • starting kernel modules
    spread is already running
    starting scmaster
  • configure kernel
  • configure spread
    using configuration template in
    /home/sysop/seiscomp3/share/templates/spread.conf.tpl
  • configure scmaster
    • check database write access … OK
    • database schema version is 0.10
    • last migration version is 0.11
    • migration to the current version is required. apply the following
      scripts in exactly the given order:
      • /home/sysop/seiscomp3/share/db/migrations/mysql/0_10_to_0_11.sql
        error: updating configuration for scmaster failed

master.log

2019/03/18 15:14:20 [warning/DbPlugin] Database schema v0.10 is older
than schema v0.11 currently supported. Information will be lost when
saving objects to the databas
e! This should be fixed!
2019/03/18 15:14:20 [error/DbPlugin] Strict version check is enabled and
schema versions do not match.
2019/03/18 15:14:20 [error/MASTER_COM_MODULE] Plugin dbplugin not
operational. Bailing out

Às 13:45 de 01/03/2019, Jan Becker via SeisComP3 escreveu:


#14

Sounds like you need to update the database schema before you can proceed.


#15

You just need to upgrade your database schema

Login your mysql

mysql -u sysop -p

Enter your password when you’re asked,

Then

use seiscomp3;

source /home/sysop/seiscomp3/share/db/migrations/mysql/0_10_to_0_11.sql

That’s it.

You re done.

Mustafa


#16

Dear Mustafa, I thank you for your help/advice. Best regards. Jose


#18

Dear users,

After installing the last SC3 version, released Jakarta 2018.327, we are
experiencing problems with the scvoice module.

From the scvoice.log file we can confirm that configuration is ok, once
it reports correctly the path do the “event.sh” script:

Manually when we run the script it works perfectly as before. However
when events are created and updated, the scripts is not invoked by the
scvoice module.

Do you have any guess where the problem might be?

Best regards,
Jose

Às 16:06 de 18/03/2019, Stefan Lisowski via SeisComP3 escreveu:


#19

You added an agencyID filter for “IPMA”. Is the agencyID of the preferred origin for that event from agency “IPMA”? If not then it will be filtered out.

You can remove the filter if you remove agencyIDs from your config.


#20

Hi @Jan Becker,

Thank you for the help
.
Yes, we use with preferency the designated agency, as in last years at all older versions we did it.
In one second server that we have also the seicomp Jakarta, running OpenSuse, we have back to the anterior version and installed again the jakarta 2017.334, and scvoice runs again calling the scrip to send emails.
So I don´t undesrtand whats happen with this last version.

Best regards,
Jose


#21

Can you check line 252 in scvoice.py and maybe add some debug print output? Not sure if it is related to this. You can also add some prints in notifiyEvent and check if that ever gets called.