SeisComP 5.0.0

Dear SeisComP community,

We are happy to finally provide you with the second major SeisComP release version 5.

In contrast to the major release of version 4 this version does not introduce breaking changes. As announced with SeisComP 4.x a new major version will be released when at least the binary compatibility of libraries cannot be guaranteed. This is the case right now. You can continue using your operational database and you can continue using your configuration. A migration to schema 0.12 is required though.

One exception: the VS (virtual seismologist) modules have been removed from the distribution and will be shipped as part of the SED EEW addon, available as source at https://github.com/SED-EEW/SED-EEW-SeisComP-contributions and as pre-compiled package at Index of /packages/Public/sed-eew/.

Changes are summarized at Release 5.0.0 · SeisComP/seiscomp · GitHub. Packages to download will be available at SeisComP seismological software and Index of /packages/Public/seiscomp/5/.

We hope you will benefit from our developments and enjoy the new features. Thank you for supporting us in advancing SeisComP!

Have fun,
Jan on behalf of the SeisComP development team

Dear Jan and Seiscomp dev team,
Thanks for this new version.

I just try to upgrade a dedicated machine from 4.X.X to 5.0.0.

I encountered this error while upgrading the database scheme :

mysql -u sysop -h localhost -p seiscomp3 < /home/sysop/seiscomp/share/db/migrations/mysql/0_11_to_0_12.sql
Enter password:

Add Origin.confidenceLevel
ERROR 1118 (42000) at line 2: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs

Regards

Mickael.

Which MYSQL/MariaDB version are you using? We have tested that on several operating systems and it worked. It seems to be a limitation of the innodb storage engine of MYSQL.

mariadb Ver 15.1 Distrib 10.5.15-MariaDB, for debian-linux-gnu (x86_64) using EditLine wrapper

50-server.cnf:innodb_buffer_pool_size = 64M

It is under Debian 11

This may be related no so much to software version, but database format version (if you upgraded from older MariaDB or MySQL) and specific configuration.

There are some potential solutions on MariaDB website: https://mariadb.com/kb/en/troubleshooting-row-size-too-large-errors-with-innodb/

Hi Andres,
Yes my database structure is quite old (since 2013). I have looking and the tables are in compact config.

But I am not very fluent in DB management…it will takes me a long time to change the tables types from compact to dynamic…

Let you know when it is finished.

Regards
Mickael.

Hi Andres,

The issue was the one you pointed. I have RowFormat from compact to dynamics and then the upgrade of the scheme works.

Thanks !

Mickael.

Great news to see SeisComP 5 release, and move to Python 3. Thanks for all the hard work :+1:

Will you be adding a build for the recently released RHEL 9 for SeisComP 5.x in the future?

I am interested to see if the dependencies will be much different to RHEL 8.

Actually, we have moved to Python 3 already with SeisComP version 4.0.0 but now we are dropping maintenance support for Python 2.

gempa will provide software packages [1] for RHEL 9 after RockyLinux has been released in this version.

[1] Index of /packages/Public/seiscomp/

good day, seiscomp community.
I am using seiscomp5 version…
scrttv & scolv work
Screenshot from 2022-06-24 12-08-48
.
but :
scmv shows black triangles (confgs. connected correctly)…
scqcv is not working.
by the way, can you give any details about created difference between sc4 and sc5???

scmv shows black triangles (confgs. connected correctly)…

After upgrading to 5.0 the triangles turned black? Check the logs or run with --debug.

scqcv is not working.

What exactly is not working?

can you give any details about created difference between sc4 and sc5???

You might want to open the link I have posted with the changes. Furthermore you might want to read gempa GmbH - SeisComP released in version 5.0.0.

You might have noticed that we are not able to solve issues if there are reports like “something is not working, please help”. Please be specific as possible and provide all information you have that could help us to solve the issue. Although I am trying hard to get my crystal ball working I am not yet there.

From the screenshot I see that the configuration of DetecLocid and detecStream are inverted. DetecLocid should be 00 and detecStream BHZ.

thank you mr. Becker, for your hard global work…
I can get add. info. from the link, which you mentioned…

you are right, mr Boussoufa , changing inverted config gave correct result…