Troubleshooting¶
Start with sudo ows status and sudo ows logs. Most problems show up there.
OWS doesn’t start¶
sudo ows prints why. If the message scrolled away, see /opt/osop/ows/log/run.log.
Message |
What to do |
|---|---|
|
Install Docker Engine (Installation), or start it: |
|
Run |
|
Use |
|
Another program uses port 16032. Stop it, or set another |
A license message |
See License messages below. |
License messages¶
Message |
What to do |
|---|---|
|
Save the license from OSOP as |
|
The license was made for another machine ID. Check |
|
Contact OSOP to renew it. |
|
The file is the license of another OSOP program. Each program has its own license file. |
|
The file was changed (for example by an editor or a copy that altered line endings) or is a license for an older OWS version. Save the original file again; if it is from an older version, see License. |
|
The file’s content was changed. Save the original file again, unchanged. |
|
Contact OSOP. |
|
Contact OSOP and include the diagnostic lines OWS prints. On WSL 2 or Docker Desktop, use a Linux computer or a Linux virtual machine instead (Installation). |
Clients can’t connect, or wait forever¶
Is OWS running?
sudo ows status.Can OWS reach the SeedLink server? OWS only starts answering clients once it has reached the SeedLink server. If it can’t,
sudo ows statusstill says running, but clients get no answer and nothing new appears in the log. Checksources.seedlink.hostandsources.seedlink.port:SeedLink on the same computer: use
host.docker.internal, not127.0.0.1orlocalhost. The SeedLink server must also accept connections from Docker’s network, not only from127.0.0.1.SeedLink on another computer: check that this computer can reach it, for example with
nc -vz <host> 18000.
To test OWS without SeedLink, set
sources.seedlinktofalseandsudo ows restart.Firewall. Clients on other computers need TCP port 16032 (your
LISTEN_PORT) open on the OWS computer.Same computer works, others don’t? Try
getmenu localhost:16032on the OWS computer (Check that it works). If that works, the problem is the network or firewall between the computers.
Channels are missing¶
A station from SeedLink is missing. OWS uses the station list it saved when it first connected. Delete the saved list (New stations on the SeedLink server).
A station from the archive is missing. Check that its files follow the SDS layout (SDS archive layout) and that
ARCHIVE_DIRpoints at the archive’s root folder (the folder that contains the year folders). OWS finds new channels in the archive within about 30 seconds.Nothing at all. Check both
sources.seedlinkandsources.sds, andsudo ows logs.
Helicorders show only the last few minutes¶
Live data from SeedLink covers only the last 5 minutes (sources.seedlink.ring_size). Everything older
comes from the archive. Check that sources.sds is true and ARCHIVE_DIR points at an
archive that is being written, for example by SeisComP’s slarchive.
Known limitations¶
Channel time range. For channels that exist only in the archive, the channel list (Earthworm
getmenu, ObsPy’sget_availability()) can show the same start and end time. The data itself is served correctly.Log lines
[ERROR] CachingReader: ... std::invalid_argument ... stoi. They appear when OWS reads from the archive and are harmless: the data is read and served correctly.Many clients. See Running OWS, Capacity.
Still stuck?¶
Contact OSOP (Support) with:
the output of
sudo ows status,sudo ows checkandsudo ows logs 200;/opt/osop/ows/config/ows.confandows-host.conf;what you tried and what happened.